Arbitrary command execution via unsanitized buildCommand input
Published Jul 25, 2022 · Updated Sep 16, 2024
Command injection in the exports function in nisaacson git-archive 0.1.4 and earlier allows local users to execute arbitrary commands. The exports path passes user-controlled options to buildCommand, which assembles a shell command without neutralizing command separators before execution. Local access and influence over archive arguments are required; injected commands run with the invoking Node.js application's privileges.
Summary
What happened
Command injection in the exports function in nisaacson git-archive 0.1.4 and earlier allows local users to execute arbitrary commands. The exports path passes user-controlled options to buildCommand, which assembles a shell command without neutralizing command separators before execution. Local access and influence over archive arguments are required; injected commands run with the invoking Node.js application's privileges.
The record
- CVE
- CVE-2020-28422
- Published
- Jul 25, 2022
- Updated
- Sep 16, 2024
- Vendor
- nisaacson
- Product
- git-archive
- Classifications
- CWE-77, CAPEC-248, T1059
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 25, 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?
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