How severe is CVE-2022-25171?

CVE-2022-25171 has a CVSS 3.x base score of 7.4, rated high severity. It is exploitable over local access with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2022-25171 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (82nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2022-25171?

CVE-2022-25171 affects P4 Project P4. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2022-25171?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2022-25171 published?

CVE-2022-25171 was published on 2022-12-20 and last updated on 2026-06-17.

CVE-2022-25171

CVE-2022-25171 is a high-severity vulnerability in P4 Project P4 with a CVSS 3.x base score of 7.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-78.

Key facts

Severity: High (CVSS 3.x base score 7.4)
EPSS exploit prediction: 2% (82nd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-78
Affected product: P4 Project P4
Published: 2022-12-20
Last modified: 2026-06-17

Description

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

Frequently asked questions

What is CVE-2022-25171?: The package p4 before 0.0.7 are vulnerable to Command Injection via the run() function due to improper input sanitization
How severe is CVE-2022-25171?: CVE-2022-25171 has a CVSS 3.x base score of 7.4, rated high severity. It is exploitable over local access with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2022-25171 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (82nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-25171?: CVE-2022-25171 affects P4 Project P4. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2022-25171?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2022-25171 published?: CVE-2022-25171 was published on 2022-12-20 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:p4_project:p4:*:*:*:*:*:node.js:*:*

Other CWE-78 (OS Command Injection) vulnerabilities

CVE-2026-56004 — Critical (CVSS 10.0): A shellcode injection in the mercurial handler of the obs tar_scm source service before version 0.12.4 could be used by…
CVE-2026-56415 — Critical (CVSS 10.0): Storage Concentrator (SC & SCVM) contains a command injection vulnerability within the debug.pl script that is…
CVE-2026-56413 — Critical (CVSS 10.0): Storage Concentrator (SC & SCVM) contains a command injection vulnerability in the ms_service.pl service, which listens…
CVE-2026-49869 — Critical (CVSS 10.0): Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, AuthenticationFilter in…
CVE-2026-49261 — Critical (CVSS 10.0): MariaDB server is a community developed fork of MySQL server. Versions 10.6.1 through 10.6.26, 10.11.1 through…
CVE-2026-10520 — Critical (CVSS 10.0): An OS Command Injection vulnerability in Ivanti Sentry before the R10.5.2, R10.6.2 and R10.7.1 versions allows a…

Browse all CWE-78 (OS Command Injection) vulnerabilities →