p4 vulnerable to Command Injection due to improper input sanitizationGHSA-jfm8-hwhg-r6gg
HIGHFix: natelong/p4@ae42e25GHSA-jfm8-hwhg-r6gg is a high-severity (CVSS 7.4) OS Command Injection vulnerability in p4. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for p4 — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-jfm8-hwhg-r6gg.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
p4npmDescription
The package p4 before 0.0.7 are vulnerable to Command Injection via the run() function due to improper input sanitization
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | p4 | all versions | 0.0.7npm install p4@0.0.7 |
Affected Products
p4p4_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for p4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update p4 to 0.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jfm8-hwhg-r6gg is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is GHSA-jfm8-hwhg-r6gg in your dependencies?
Find it across npm, including transitive dependencies.