Command execution via unsanitized run input
Published Dec 21, 2022 · Updated Apr 16, 2025
Command injection in p4 before 0.0.7 allows local users to execute arbitrary commands through the run() function. The vulnerable runCommand implementation concatenates command and arguments into a shell string passed to child_process.exec, allowing metacharacters such as '&' to start attacker-selected commands. Exploitation requires local code to invoke run() with attacker-controlled input and can compromise confidentiality, integrity, and availability.
Summary
What happened
Command injection in p4 before 0.0.7 allows local users to execute arbitrary commands through the run() function. The vulnerable runCommand implementation concatenates command and arguments into a shell string passed to child_process.exec, allowing metacharacters such as '&' to start attacker-selected commands. Exploitation requires local code to invoke run() with attacker-controlled input and can compromise confidentiality, integrity, and availability.
The record
- CVE
- CVE-2022-25171
- Published
- Dec 21, 2022
- Updated
- Apr 16, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-78, T1059
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 21, 2022CVE publishedPublication date reported by the CVE source.
- Apr 16, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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 proof-of-concept for p4 run() command injectionproof 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