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

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

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

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

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

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

Stackvector CVE-2021-29939

HIGH

Out-of-bounds Write (CWE-787)

2021-04-01 cve@mitre.org

Buffer Overflow Memory Corruption Stackvector

7.3

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.3 HIGH

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

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:L/I:L/A:L

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

Low

Lifecycle Timeline

CVE Published

Apr 01, 2021 - 05:15 nvd

HIGH 7.3

DescriptionNVD

An issue was discovered in the stackvector crate through 2021-02-19 for Rust. There is an out-of-bounds write in StackVec::extend if size_hint provides certain anomalous data.

AnalysisAI

An issue was discovered in the stackvector crate through 2021-02-19 for Rust. Rated high severity (CVSS 7.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch 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 the stackvector crate through 2021-02-19 for Rust. There is an out-of-bounds write in StackVec::extend if size_hint provides certain anomalous data. Affected products include: Stackvector Project Stackvector. Version information: through 2021.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Validate write boundaries, use memory-safe languages, enable compiler protections (ASLR, stack canaries).