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

CVE-2022-29806 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: 67.1%.

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

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

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

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

Zoneminder CVE-2022-29806

CRITICAL

Path Traversal (CWE-22)

2022-04-26 cve@mitre.org

RCE Path Traversal Zoneminder

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

Apr 26, 2022 - 04:15 nvd

CRITICAL 9.8

DescriptionNVD

ZoneMinder before 1.36.13 allows remote code execution via an invalid language. Ability to create a debug log file at an arbitrary pathname contributes to exploitability.

AnalysisAI

ZoneMinder before 1.36.13 allows remote code execution via an invalid language. 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 Path Traversal (CWE-22), which allows attackers to access files and directories outside the intended path. ZoneMinder before 1.36.13 allows remote code execution via an invalid language. Ability to create a debug log file at an arbitrary pathname contributes to exploitability. Affected products include: Zoneminder. Version information: before 1.36.13.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Validate and canonicalize file paths. Use chroot or sandboxing. Reject input containing path separators or '../' sequences.