CVE-2024-1939
Memory Safety in Fedoraproject Fedora 38 … 40
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-1939 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 Junk Data (T1001.001); ranked in the top 17% 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.
Type Confusion in the V8 JavaScript engine of Google Chrome versions prior to 122.0.6261.94 enables heap corruption. The flaw is tracked as CWE-843 and received a CVSS 3.1 base score of 8.8, reflecting network attack vector, low complexity, and no required privileges beyond a user visiting a malicious page.
A remote attacker can deliver a crafted HTML page that triggers the type confusion, potentially allowing arbitrary code execution or memory corruption within the renderer process. Successful exploitation could compromise confidentiality, integrity, and availability of the affected browser instance.
Chrome stable channel updates released on 27 February 2024 upgraded V8 to version 122.0.6261.94 and later, closing the issue. Corresponding packages were issued for Fedora systems to facilitate deployment of the fixed Chrome builds.
EPSS scores have remained near 0.46 with only minor fluctuation since disclosure, indicating no pronounced post-release surge in observed exploitation interest.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-17661
Vulnerability Data
Type Confusion in V8 in Google Chrome prior to 122.0.6261.94 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.5.2V15.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.
Engineering principles can require use of type-safe languages, static typing, and runtime type checks that structurally avoid allocating one type and accessing another.
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.
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.