What is the CVSS score of CVE-2024-25431?

CVE-2024-25431 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: 0.6%.

Is there a public PoC exploit available for CVE-2024-25431?

Yes, a public proof-of-concept exploit is available for CVE-2024-25431. Prioritise patching immediately. EPSS: 0.6%.

Is there a patch available for CVE-2024-25431?

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

Webassembly Micro Runtime CVE-2024-25431

HIGH

Out-of-bounds Read (CWE-125)

2024-11-08 cve@mitre.org

Buffer Overflow Information Disclosure Webassembly Micro Runtime

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

Nov 08, 2024 - 17:15 nvd

HIGH 7.8

DescriptionNVD

AnalysisAI

An issue in bytecodealliance wasm-micro-runtime before v.b3f728c and fixed in commit 06df58f allows a remote attacker to escalate privileges via a crafted file to the check_was_abi_compatibility. 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 Read (CWE-125), which allows attackers to read data from memory outside the intended buffer boundaries. An issue in bytecodealliance wasm-micro-runtime before v.b3f728c and fixed in commit 06df58f allows a remote attacker to escalate privileges via a crafted file to the check_was_abi_compatibility function. Affected products include: Bytecodealliance Webassembly Micro Runtime.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Validate array indices and buffer lengths. Use memory-safe languages. Enable AddressSanitizer during testing.