Cyber Resilience

CVE-2024-2887

Memory Safety in Fedoraproject Fedora 38 … 40

Public PoCMemory Safety
Published
26 March 2024
Modified
17 June 2026
CVSS Score v3.1 7.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
EPSS Score 0.20 97th percentile
Risk Priority 67 floored blend · peak EPSS

Summary

CVE-2024-2887 is a high-severity Type Confusion (CWE-843) vulnerability in Fedoraproject Fedora. Its CVSS base score is 7.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-2887 is a type confusion vulnerability in the WebAssembly component of Google Chrome versions prior to 123.0.6312.86. The flaw carries a CVSS 3.1 score of 7.7 and is tracked under CWE-843.

A remote attacker can exploit the issue by serving a crafted HTML page to a victim, achieving arbitrary code execution within the browser process. The attack requires user interaction via the rendered page and involves high attack complexity under a local access vector.

Chrome stable channel updates released on 26 March 2024 address the vulnerability by correcting the type confusion in WebAssembly. Downstream distributions such as Fedora have issued corresponding package updates that pull in the patched Chrome release.

EPSS for the CVE rose from lower values to a peak of 0.1253 on 2026-05-22 before receding to the current score of 0.0876, indicating measurable post-disclosure exploitation interest.

EU & UK References

Vulnerability Data

Type Confusion in WebAssembly in Google Chrome prior to 123.0.6312.86 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: High)

CWE(s)
CWE-843

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-5838Same product: Fedoraproject Fedora
CVE-2024-5833Same product: Fedoraproject Fedora
CVE-2024-1938Same product: Fedoraproject Fedora
CVE-2021-30551Same product: Fedoraproject Fedora
CVE-2023-5346Same product: Fedoraproject Fedora
CVE-2024-5274Same product: Fedoraproject Fedora
CVE-2024-5837Same product: Fedoraproject Fedora
CVE-2024-4058Same product: Fedoraproject Fedora
CVE-2024-5843Same product: Fedoraproject Fedora
CVE-2024-1939Same product: Fedoraproject Fedora

Affected Assets

google
chrome
≤ 123.0.6312.86
fedoraproject
fedora
38, 39, 40

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.5.2
  • V3.2.3
  • V15.3.5

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation (including fuzzing and type-aware analysis) directly finds type-confusion flaws before deployment.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can require use of type-safe languages, static typing, and runtime type checks that structurally avoid allocating one type and accessing another.

SI-16 Memory Protection partial match

Memory-protection controls limit the blast radius when a type-confusion access occurs but do not stop the flaw itself.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent type-confusion flaws via safe typing, static analysis, and code review while the control itself addresses many additional weaknesses.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect type-confusion vulnerabilities through fuzzing and static analysis.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates type-safe design and review that can catch type-confusion flaws.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify strong typing and interface contracts that reduce type confusion.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles promote type-safe languages and memory-safety mechanisms that mitigate type confusion.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly forbid unsafe type casts and require static-analysis checks for type confusion.

References