Arbitrary command execution via unsanitized log limit
Published Apr 2, 2020 · Updated Aug 4, 2024
Command injection in get-git-data 1.3.1 and earlier allows attackers to execute arbitrary OS commands through the log limit argument. The log method appends its limit parameter directly to a git log command string and passes the result to child_process.exec without validation or escaping. Exploitation requires a consuming application to pass attacker-controlled data to log(), after which commands run with the Node.js process's privileges.
Summary
What happened
Command injection in get-git-data 1.3.1 and earlier allows attackers to execute arbitrary OS commands through the log limit argument. The log method appends its limit parameter directly to a git log command string and passes the result to child_process.exec without validation or escaping. Exploitation requires a consuming application to pass attacker-controlled data to log(), after which commands run with the Node.js process's privileges.
The record
- CVE
- CVE-2020-7619
- Published
- Apr 2, 2020
- Updated
- Aug 4, 2024
- Vendor
- get-git-data Project
- Product
- get-git-data
- Classifications
- CWE-78, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 2, 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 including 1.3.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 get-git-data log limit 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