This weekExploitable · Confirmed
p4: p4 vulnerable to Command Injection due to improper input sanitization
There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.
Does it affect what I run?
p4 (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- p4 (npm): every version, before 0.0.7
The fix
p4 (npm) fixed in 0.0.7
npmnpm install p4@0.0.7pnpmpnpm add p4@0.0.7yarnyarn add p4@0.0.7bunbun add p4@0.0.7Check what is installednpm ls p4Paste into Cursor, Lovable or Claude CodeUpgrade the npm dependency p4 to 0.0.7 or the nearest later release, to fix CVE-2022-25171. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
Exploitable · Confirmed
CISA's assessment in the CVE record says a proof of concept is public.
CISA Vulnrichment (SSVC and KEV fields inside CVE records)Stated
Timeline
- First published here, as "For your digest".
- Level changed from "For your digest" to "This week".
- Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))