Token disclosure via visible command-line argument
Published May 25, 2021 · Updated Aug 3, 2024
Sensitive-information exposure in GitHub CodeQL runner before codeql-bundle-20210304 allows local users to read GitHub access tokens. The runner accepts a token through --github-auth as a process argument, leaving the secret visible in the operating system's process list. Exposure requires third-party CI/CD to use that flag and a local process or published process output to inspect the argument; GitHub Actions users are not affected.
Summary
What happened
Sensitive-information exposure in GitHub CodeQL runner before codeql-bundle-20210304 allows local users to read GitHub access tokens. The runner accepts a token through --github-auth as a process argument, leaving the secret visible in the operating system's process list. Exposure requires third-party CI/CD to use that flag and a local process or published process output to inspect the argument; GitHub Actions users are not affected.
The record
- CVE
- CVE-2021-32638
- Published
- May 25, 2021
- Updated
- Aug 3, 2024
- Vendor
- Product
- CodeQL Action
- Classifications
- CWE-200, CWE-214, T1552
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 25, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=< codeql-bundle-20210304
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