Arbitrary file overwrite via injected git option
Published Sep 19, 2023 · Updated Sep 25, 2024
Argument injection in blamer before 1.0.4 allows remote attackers to overwrite arbitrary files through a crafted blameByFile() path. The git backend passes that path as an operand without rejecting option-like input or separating it from git options with --. Exploitation requires an application to pass attacker-controlled data to the API and permits file overwrite through git's --output option.
Summary
What happened
Argument injection in blamer before 1.0.4 allows remote attackers to overwrite arbitrary files through a crafted blameByFile() path. The git backend passes that path as an operand without rejecting option-like input or separating it from git options with --. Exploitation requires an application to pass attacker-controlled data to the API and permits file overwrite through git's --output option.
The record
- CVE
- CVE-2023-26143
- Published
- Sep 19, 2023
- Updated
- Sep 25, 2024
- Vendor
- Andrey Kucherenko
- Product
- blamer
- Classifications
- CWE-88, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 19, 2023CVE publishedPublication date reported by the CVE source.
- Sep 25, 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=0 <1.0.4
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
- Argument Injection vulnerability in blamer 1.0.1proof of concept · demonstrated
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