Code execution via unprotected NTFS path aliases
Published Jan 24, 2020 · Updated Aug 4, 2024
Code execution in affected Microsoft Git releases allows remote attackers to run code during a clone from a crafted repository. The path validator leaves core.protectNTFS disabled outside native Windows, so NTFS short names such as git~1 or alternate data streams can alias protected .git paths. Exploitation requires cloning an untrusted repository in WSL on a Windows drive with short names enabled, or on macOS through an SMB share; code runs with the cloning user's privileges.
Summary
What happened
Code execution in affected Microsoft Git releases allows remote attackers to run code during a clone from a crafted repository. The path validator leaves core.protectNTFS disabled outside native Windows, so NTFS short names such as git~1 or alternate data streams can alias protected .git paths. Exploitation requires cloning an untrusted repository in WSL on a Windows drive with short names enabled, or on macOS through an SMB share; code runs with the cloning user's privileges.
The record
- CVE
- CVE-2019-1353
- Published
- Jan 24, 2020
- Updated
- Aug 4, 2024
- Vendor
- Microsoft
- Product
- Microsoft Git
- Classifications
- T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 24, 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=Before 2.24.1, 2.23.1, 2.22.2, 2.21.1, 2.20.2, 2.19.3, 2.18.2, 2.17.3, 2.16.6, 2.15.4, 2.14.6
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