Arbitrary file overwrite via backslash symlink escape
Published Jan 24, 2020 · Updated Aug 4, 2024
Arbitrary file overwrite in Git for Microsoft Visual Studio 2017 and 2019 allows remote attackers to write files via a crafted repository. Checkout path handling accepts backslashes in tracked tree entries and follows malicious symlinks, allowing writes to escape the work tree. Exploitation requires a user to clone or check out the crafted repository; the overwrite can lead to code execution in that user's context.
Summary
What happened
Arbitrary file overwrite in Git for Microsoft Visual Studio 2017 and 2019 allows remote attackers to write files via a crafted repository. Checkout path handling accepts backslashes in tracked tree entries and follows malicious symlinks, allowing writes to escape the work tree. Exploitation requires a user to clone or check out the crafted repository; the overwrite can lead to code execution in that user's context.
The record
- CVE
- CVE-2019-1354
- Published
- Jan 24, 2020
- Updated
- Aug 4, 2024
- Vendor
- Microsoft
- Product
- Microsoft Visual Studio 2019
- Classifications
- CWE-20, T1204.002
- 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=16.0
- Affected versionversion=unspecified
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.
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