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

CVE-2021-32272 has a CVSS 3.1 base score of 7.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 1.2%.

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

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

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

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

Faad2 CVE-2021-32272

HIGH

Out-of-bounds Write (CWE-787)

2021-09-20 cve@mitre.org

Buffer Overflow RCE Memory Corruption Faad2 Debian Linux

7.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.8 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Sep 20, 2021 - 16:15 nvd

HIGH 7.8

DescriptionNVD

An issue was discovered in faad2 before 2.10.0. A heap-buffer-overflow exists in the function stszin located in mp4read.c. It allows an attacker to cause Code Execution.

AnalysisAI

An issue was discovered in faad2 before 2.10.0. Rated high severity (CVSS 7.8), this vulnerability is 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. An issue was discovered in faad2 before 2.10.0. A heap-buffer-overflow exists in the function stszin located in mp4read.c. It allows an attacker to cause Code Execution. Affected products include: Faad2 Project Faad2, Debian Debian Linux. Version information: before 2.10.0..

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