GitHub token disclosure via uncensored request headers
Published Mar 19, 2020 · Updated Aug 4, 2024
Sensitive-data exposure in EasyBuild Framework before 4.1.2 allows local users to obtain a GitHub token from an accessible debug log. The REST client writes the full request-header dictionary, including the Authorization token, to the top-level log before sending GitHub API requests. Exposure requires a GitHub integration option and nondefault debug logging; the temporary log is normally mode 700, limiting disclosure to the account holder or recipients of a manually shared log.
Summary
What happened
Sensitive-data exposure in EasyBuild Framework before 4.1.2 allows local users to obtain a GitHub token from an accessible debug log. The REST client writes the full request-header dictionary, including the Authorization token, to the top-level log before sending GitHub API requests. Exposure requires a GitHub integration option and nondefault debug logging; the temporary log is normally mode 700, limiting disclosure to the account holder or recipients of a manually shared log.
The record
- CVE
- CVE-2020-5262
- Published
- Mar 19, 2020
- Updated
- Aug 4, 2024
- Vendor
- EasyBuild
- Product
- EasyBuild Framework
- Classifications
- CWE-532, CWE-922, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 19, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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=< 4.1.2
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