What is the CVSS score of CVE-2019-6991?

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

Is there a public PoC exploit available for CVE-2019-6991?

Yes, a public proof-of-concept exploit is available for CVE-2019-6991. Prioritise patching immediately. EPSS: 3.3%.

Is there a patch available for CVE-2019-6991?

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

Zoneminder CVE-2019-6991

CRITICAL

Out-of-bounds Write (CWE-787)

2019-01-28 cve@mitre.org

Buffer Overflow Memory Corruption Zoneminder

9.8

CVSS 3.0 · 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.0/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

Jan 28, 2019 - 20:29 nvd

CRITICAL 9.8

DescriptionNVD

AnalysisAI

A classic Stack-based buffer overflow exists in the zmLoadUser() function in zm_user.cpp of the zmu binary in ZoneMinder through 1.32.3, allowing an unauthenticated attacker to execute code via a. 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 Out-of-bounds Write (CWE-787), which allows attackers to write data beyond allocated buffer boundaries leading to code execution or crashes. A classic Stack-based buffer overflow exists in the zmLoadUser() function in zm_user.cpp of the zmu binary in ZoneMinder through 1.32.3, allowing an unauthenticated attacker to execute code via a long username. Affected products include: Zoneminder. Version information: through 1.32.3.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Validate write boundaries, use memory-safe languages, enable compiler protections (ASLR, stack canaries).