Cyber Resilience

CVE-2024-5830

Memory Safety in Fedoraproject Fedora 39 … 40

Published
11 June 2024
Modified
21 November 2024
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0092 57th percentile
Risk Priority 73 floored blend · peak EPSS

Summary

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

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

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — 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-5830 is a type confusion vulnerability in the V8 JavaScript engine within Google Chrome versions prior to 126.0.6478.54. The flaw, tracked under CWEs 843 and 787, permits an out-of-bounds memory write when a victim visits a specially crafted HTML page. It carries a CVSS 3.1 base score of 8.8 and was rated High severity by the Chromium project.

A remote attacker can exploit the issue without authentication by serving malicious web content that triggers the type confusion during JavaScript execution. Successful exploitation grants the ability to corrupt memory outside intended bounds, which can be leveraged to achieve arbitrary code execution or other high-impact effects on the confidentiality, integrity, and availability of the browser process.

Chrome stable channel updates released on 11 June 2024 advise users to upgrade immediately to version 126.0.6478.54 or later; downstream distributions such as Fedora have published corresponding package advisories directing administrators to apply the patched builds. The EPSS score has remained flat at 0.0976 with no material increase observed after disclosure.

EU & UK References

Vulnerability Data

Type Confusion in V8 in Google Chrome prior to 126.0.6478.54 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: High)

CWE(s)

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.
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.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-4761Same product: Fedoraproject Fedora
CVE-2021-21220Same product: Fedoraproject Fedora
CVE-2024-0517Same product: Fedoraproject Fedora
CVE-2024-5844Same product: Fedoraproject Fedora
CVE-2024-5499Same product: Fedoraproject Fedora
CVE-2024-2173Same product: Fedoraproject Fedora
CVE-2024-0223Same product: Fedoraproject Fedora
CVE-2023-1529Same product: Fedoraproject Fedora
CVE-2021-30632Same product: Fedoraproject Fedora
CVE-2024-3157Same product: Fedoraproject Fedora

Affected Assets

google
chrome
≤ 126.0.6478.54
fedoraproject
fedora
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

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

Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.

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

Input validation can structurally reject or sanitize data that would otherwise trigger an out-of-bounds write.

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.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.

PR.PS-02 partial match
prevents

Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.

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.

finds

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

prevents

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

prevents

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

prevents

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

prevents

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

prevents

Change management can enforce review gates that catch unsafe memory operations before deployment.

References