Arbitrary code execution via current-directory Git binary
Published Mar 22, 2021 · Updated Aug 3, 2024
Uncontrolled search path in git-bug before 0.7.2 allows remote attackers to execute arbitrary code through a crafted repository. When git-bug invokes Git, the process search can prefer a repository-supplied git.bat in the current directory over the intended binary. Exploitation requires Windows or another host whose PATH searches the working directory first, plus use of git-bug inside the malicious repository.
Summary
What happened
Uncontrolled search path in git-bug before 0.7.2 allows remote attackers to execute arbitrary code through a crafted repository. When git-bug invokes Git, the process search can prefer a repository-supplied git.bat in the current directory over the intended binary. Exploitation requires Windows or another host whose PATH searches the working directory first, plus use of git-bug inside the malicious repository.
The record
- CVE
- CVE-2021-28955
- Published
- Mar 22, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-427, T1574.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 22, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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