Repository token disclosure via symlinked input files
Published Sep 9, 2021 · Updated Aug 3, 2024
Information disclosure in check-spelling before 0.0.19 allows remote authenticated users to expose a GITHUB_TOKEN via a crafted pull request. The action follows attacker-controlled symlinks while reading configuration and word-list files without ensuring that resolved paths remain inside GITHUB_WORKSPACE. A repository must run the affected action on pull_request_target or schedule; the exposed token enables unapproved commits and subsequent repository-secret theft.
Summary
What happened
Information disclosure in check-spelling before 0.0.19 allows remote authenticated users to expose a GITHUB_TOKEN via a crafted pull request. The action follows attacker-controlled symlinks while reading configuration and word-list files without ensuring that resolved paths remain inside GITHUB_WORKSPACE. A repository must run the affected action on pull_request_target or schedule; the exposed token enables unapproved commits and subsequent repository-secret theft.
The record
- CVE
- CVE-2021-32724
- Published
- Sep 9, 2021
- Updated
- Aug 3, 2024
- Vendor
- Check Spelling
- Product
- check-spelling
- Classifications
- CWE-532, T1552
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 9, 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=< 0.0.19
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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