Cyber Resilience

CVE-2024-7965

Memory Safety in Google Chrome ≤ 128.0.6613.84

CISA KEVActive ExploitationEUVD ExploitedMemory Safety
Published
21 August 2024
Modified
24 October 2025
KEV Added
28 August 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.18 97th percentile
Risk Priority 90 floored blend · peak EPSS

Summary

CVE-2024-7965 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Google Chrome. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Downgrade Attack (T1689); ranked in the top 3% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities 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-7965 is an inappropriate implementation flaw in the V8 JavaScript engine that affects Google Chrome versions prior to 128.0.6613.84. The issue stems from insufficient bounds checking that can lead to heap corruption when processing a specially crafted HTML page, corresponding to CWE-787 and CWE-358. It carries a CVSS 3.1 base score of 8.8 reflecting network attack vector, low complexity, and no required privileges.

An unauthenticated remote attacker can exploit the vulnerability by convincing a user to visit a malicious web page, after which successful exploitation may allow arbitrary code execution within the renderer process with the potential to compromise confidentiality, integrity, and availability of the browser.

The official Chrome stable channel update released on 21 August 2024 upgrades V8 to a fixed version; administrators are advised to ensure all desktop and mobile instances are updated promptly. The vulnerability is also tracked in CISA’s Known Exploited Vulnerabilities catalog, confirming active exploitation in the wild.

EPSS scores rose from low values at disclosure to a peak of 0.2753 on 23 September 2024 before receding to the current 0.2280, indicating measurable post-disclosure exploitation interest that warrants continued monitoring.

EU & UK References

Vulnerability Data

Inappropriate implementation in V8 in Google Chrome prior to 128.0.6613.84 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

CWE(s)
CWE-787CWE-358
KEV Date Added
28 August 2024

Related Threats

MITRE ATT&CK Enterprise Techniques

T1689 Downgrade Attack Defense Impairment
Adversaries may downgrade or use a version of system features that may be outdated, vulnerable, and/or does not support updated security controls.
attack.mitre.org →
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 →
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-5419Same product: Google Chromeboth on KEV
CVE-2022-4135Same product: Google Chromeboth on KEV
CVE-2019-5825Same product: Google Chromeboth on KEV
CVE-2020-16013Same product: Google Chromeboth on KEV
CVE-2024-6772Same product: Google Chrome
CVE-2020-16010Same product: Google Chromeboth on KEV
CVE-2024-4761Same product: Google Chromeboth on KEV
CVE-2021-21220Same product: Google Chromeboth on KEV
CVE-2021-30632Same product: Google Chromeboth on KEV
CVE-2023-1217Same product: Google Chrome

Affected Assets

google
chrome
≤ 128.0.6613.84
microsoft
edge chromium
≤ 128.0.2739.42

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)
  • V17.2.8

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation (including fuzzing and bounds checks) finds out-of-bounds write flaws before deployment.

SA-15 Development Process, Standards, and Tools partial match

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

SI-10 Information Input Validation partial match

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

SI-16 Memory Protection partial match

Memory-protection mechanisms limit the exploitability and blast radius of a successful out-of-bounds write.

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-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.

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.

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

Security testing in development and acceptance can detect and prevent out-of-bounds write defects.

A.8.24 Use of cryptography partial match
prevents

Use of cryptography control depends on correct implementation of standardized cryptographic checks.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates practices that prevent out-of-bounds writes.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify bounds-checking and safe memory handling.

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

Secure architecture and engineering principles reduce the likelihood of buffer overflows.

A.8.28 Secure coding partial match
prevents

Secure coding directly addresses out-of-bounds writes through language choice and coding standards.

References