Code execution via unchecked backslash path equivalence
Published Apr 29, 2021 · Updated Aug 3, 2024
Path-equivalence flaws in Cygwin Git before 2.31.1-2 allow remote attackers to execute arbitrary code through a crafted repository. The checkout path validator in read-cache.c rejects backslashes only for GIT_WINDOWS_NATIVE builds, not CYGWIN, allowing backslash names and symlinks to overwrite arbitrary files, including Git hooks. Exploitation requires a user to clone or check out an untrusted repository, after which attacker-controlled hook contents run as that user.
Summary
What happened
Path-equivalence flaws in Cygwin Git before 2.31.1-2 allow remote attackers to execute arbitrary code through a crafted repository. The checkout path validator in read-cache.c rejects backslashes only for GIT_WINDOWS_NATIVE builds, not CYGWIN, allowing backslash names and symlinks to overwrite arbitrary files, including Git hooks. Exploitation requires a user to clone or check out an untrusted repository, after which attacker-controlled hook contents run as that user.
The record
- CVE
- CVE-2021-29468
- Published
- Apr 29, 2021
- Updated
- Aug 3, 2024
- Vendor
- me-and
- Product
- Cygwin Git
- Classifications
- CWE-41, CWE-1289, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 29, 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=< 2.31.1-2
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