What is the CVSS score of CVE-2021-37232?

CVE-2021-37232 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.2%.

Is there a public PoC exploit available for CVE-2021-37232?

Yes, a public proof-of-concept exploit is available for CVE-2021-37232. Prioritise patching immediately. EPSS: 2.2%.

Is there a patch available for CVE-2021-37232?

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

Atomicparsley CVE-2021-37232

CRITICAL

Out-of-bounds Write (CWE-787)

2021-08-04 cve@mitre.org

Buffer Overflow Memory Corruption Atomicparsley

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

Aug 04, 2021 - 10:15 nvd

CRITICAL 9.8

DescriptionNVD

AnalysisAI

A stack overflow vulnerability occurs in Atomicparsley 20210124.204813.840499f through APar_read64() in src/util.cpp due to the lack of buffer size of uint32_buffer while reading more bytes in. 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 stack overflow vulnerability occurs in Atomicparsley 20210124.204813.840499f through APar_read64() in src/util.cpp due to the lack of buffer size of uint32_buffer while reading more bytes in APar_read64. Affected products include: Atomicparsley Project Atomicparsley.

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).