Arbitrary command execution via unescaped filename
Published Aug 2, 2022 · Updated Sep 16, 2024
Command injection in Jamund Ferguson gitblame 0.1.1 and earlier allows attackers to execute arbitrary commands via crafted file paths. The exported function in lib/gitblame.js passes path.basename(file) into a shell command through direct string concatenation without escaping. Exploitation requires a consuming application to supply attacker-controlled path input, and injected commands run with the Node.js process's privileges.
Summary
What happened
Command injection in Jamund Ferguson gitblame 0.1.1 and earlier allows attackers to execute arbitrary commands via crafted file paths. The exported function in lib/gitblame.js passes path.basename(file) into a shell command through direct string concatenation without escaping. Exploitation requires a consuming application to supply attacker-controlled path input, and injected commands run with the Node.js process's privileges.
The record
- CVE
- CVE-2020-28434
- Published
- Aug 2, 2022
- Updated
- Sep 16, 2024
- Vendor
- Jamund Ferguson
- Product
- gitblame
- Classifications
- CWE-77, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 2, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 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 <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.
Weakness, pattern, technique
Public exploit references
- Snyk gitblame filename-injection proof of conceptproof of concept · unverified
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