Arbitrary code execution via current-directory executable search
Published Apr 25, 2023 · Updated Feb 3, 2025
Uncontrolled search path handling in Git CMD before 2.40.1 allows local users to execute arbitrary code through a planted doskey.exe. Git CMD startup resolves doskey.exe from the current working directory before a trusted system location, so an attacker-controlled executable is launched silently. Exploitation requires the victim to start Git CMD in an attacker-writable directory, and the planted code runs with that victim's account privileges.
Summary
What happened
Uncontrolled search path handling in Git CMD before 2.40.1 allows local users to execute arbitrary code through a planted doskey.exe. Git CMD startup resolves doskey.exe from the current working directory before a trusted system location, so an attacker-controlled executable is launched silently. Exploitation requires the victim to start Git CMD in an attacker-writable directory, and the planted code runs with that victim's account privileges.
The record
- CVE
- CVE-2023-29012
- Published
- Apr 25, 2023
- Updated
- Feb 3, 2025
- Vendor
- Git for Windows
- Product
- Git for Windows
- Classifications
- CWE-427, T1574.007
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 25, 2023CVE publishedPublication date reported by the CVE source.
- Feb 3, 2025Record 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.40.1
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