GitHub App JWT disclosure via refresh errors
Published Dec 20, 2022 · Updated Apr 16, 2025
Information disclosure in ghinstallation before 2.0.0 allows local users to obtain a GitHub App JWT through token-refresh errors. Transport.refreshToken formats the complete failed HTTP request into its non-2xx error, including the Authorization bearer token. Exposure requires a failed installation-token refresh and access to the propagated error; the JWT remains valid for no more than 10 minutes.
Summary
What happened
Information disclosure in ghinstallation before 2.0.0 allows local users to obtain a GitHub App JWT through token-refresh errors. Transport.refreshToken formats the complete failed HTTP request into its non-2xx error, including the Authorization bearer token. Exposure requires a failed installation-token refresh and access to the propagated error; the JWT remains valid for no more than 10 minutes.
The record
- CVE
- CVE-2022-39304
- Published
- Dec 20, 2022
- Updated
- Apr 16, 2025
- Vendor
- Bradley Falzon
- Product
- ghinstallation
- Classifications
- CWE-209, T1528
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 20, 2022CVE publishedPublication date reported by the CVE source.
- Apr 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.0.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo