What is the CVSS score of CVE-2022-25171?

CVE-2022-25171 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 2.4%.

Is there a public PoC exploit available for CVE-2022-25171?

Yes, a public proof-of-concept exploit is available for CVE-2022-25171. Prioritise patching immediately. EPSS: 2.4%.

Is there a patch available for CVE-2022-25171?

Yes, a patch is available for CVE-2022-25171. Update the affected software to the latest version immediately.

P4 CVE-2022-25171

CRITICAL

OS Command Injection (CWE-78)

2022-12-20 report@snyk.io

Command Injection P4

9.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Dec 20, 2022 - 05:15 nvd

CRITICAL 9.8

DescriptionNVD

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

AnalysisAI

The package p4 before 0.0.7 are vulnerable to Command Injection via the run() function due to improper input sanitization. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified as OS Command Injection (CWE-78), which allows attackers to execute arbitrary operating system commands on the host. The package p4 before 0.0.7 are vulnerable to Command Injection via the run() function due to improper input sanitization Affected products include: P4 Project P4. Version information: before 0.0.7.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Avoid passing user input to shell commands. Use language-specific APIs instead of shell execution. Apply strict input validation with allowlists.