CVE-2023-2724
Memory Safety in Fedoraproject Fedora 37 … 38
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2023-2724 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 2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
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-2023-2724 is a type confusion vulnerability in the V8 JavaScript engine within Google Chrome versions prior to 113.0.5672.126. The flaw, assigned CWE-843, permits heap corruption when a victim visits a specially crafted HTML page and carries a CVSS 3.1 base score of 8.8 reflecting high impact on confidentiality, integrity, and availability.
A remote attacker can exploit the issue without authentication by serving the malicious page, which triggers the type confusion and subsequent memory corruption. Successful exploitation could allow arbitrary code execution or other damaging actions within the browser process.
Chrome stable-channel updates released on 16 May 2023 address the vulnerability by advancing the browser to version 113.0.5672.126 or later; corresponding Fedora package advisories likewise direct users to apply the patched Chrome builds.
EPSS scores for the CVE reached a peak of 0.1522 after disclosure before settling at the current value of 0.1042, indicating that exploitation interest increased measurably in the weeks following public release.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-34188
Vulnerability Data
Type confusion in V8 in Google Chrome prior to 113.0.5672.126 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.2V3.2.3V15.3.5
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.
Security testing in development can detect type-confusion vulnerabilities through fuzzing and static analysis.
Secure SDLC mandates type-safe design and review that can catch type-confusion flaws.
Application security requirements can specify strong typing and interface contracts that reduce type confusion.
Secure architecture principles promote type-safe languages and memory-safety mechanisms that mitigate type confusion.
Secure coding standards directly forbid unsafe type casts and require static-analysis checks for type confusion.