Remote code execution via NTFS path confusion
Published Apr 27, 2020 · Updated Aug 4, 2024
Improper input validation in libgit2 before 0.28.4 and 0.99.0 allows remote attackers to execute code via a crafted repository clone. The path.c validation logic treats NTFS Alternate Data Stream-equivalent names as distinct and permits writes into the .git directory during cloning. Exploitation requires cloning an attacker-controlled repository on a filesystem that interprets these names; no authentication is required.
Summary
What happened
Improper input validation in libgit2 before 0.28.4 and 0.99.0 allows remote attackers to execute code via a crafted repository clone. The path.c validation logic treats NTFS Alternate Data Stream-equivalent names as distinct and permits writes into the .git directory during cloning. Exploitation requires cloning an attacker-controlled repository on a filesystem that interprets these names; no authentication is required.
The record
- CVE
- CVE-2020-12278
- Published
- Apr 27, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 27, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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