Arbitrary command execution via unsanitized blame arguments
Published Mar 10, 2020 · Updated Aug 4, 2024
OS command injection in Andrey Kucherenko blamer before 1.0.1 allows attackers to execute arbitrary commands through crafted blame arguments. The Git and Subversion adapters concatenate supplied arguments and a file name into shell command strings passed to child_process.exec without neutralization. Exploitation requires an application to pass attacker-controlled constructor or blameByFile arguments; commands run with the application's privileges.
Summary
What happened
OS command injection in Andrey Kucherenko blamer before 1.0.1 allows attackers to execute arbitrary commands through crafted blame arguments. The Git and Subversion adapters concatenate supplied arguments and a file name into shell command strings passed to child_process.exec without neutralization. Exploitation requires an application to pass attacker-controlled constructor or blameByFile arguments; commands run with the application's privileges.
The record
- CVE
- CVE-2019-10807
- Published
- Mar 10, 2020
- Updated
- Aug 4, 2024
- Vendor
- Andrey Kucherenko
- Product
- blamer
- Classifications
- CWE-78, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 10, 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=All versions prior to 1.0.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
- Snyk blamer command-injection proof of conceptproof 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