Buffer overflow in Google Chrome
CVE-2024-8193
- CVSS v3
- 8.8 High
- Public exploits
- 1 repository
- EPSS
- 0.006 · 49.3th percentile
- Published
- 2024-08-28
Heap buffer overflow in Skia in Google Chrome prior to 128.0.6613.113 allowed a remote attacker who had compromised the renderer process to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
Vulnerability class: Buffer Overflow
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.8 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
- Attack Vector
- Network
AV:N - Attack Complexity
- Low
AC:L - Privileges Required
- None
PR:N - User Interaction
- Required
UI:R - Scope
- Unchanged
S:U - Confidentiality
- High
C:H - Integrity
- High
I:H - Availability
- High
A:H
EPSS exploit prediction
EPSS 0.006, 49.3th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Google Chrome — versions 128.0.6613.113
Weakness classification (CWE)
Public exploits and proof-of-concept code
1 public repository with exploit or proof-of-concept code for this CVE:
- HyHy100/Chrome-Skia-CVE-2024-8193 (last pushed 2025-07-02): PoC for a Chrome integer overflow -> OOB write vulnerability I reported to Google in Skia.
Also mentioned in 5 other repositories (fkie-cad/nvd-json-data-feeds, nomi-sec/PoC-in-GitHub, plzheheplztrying/cve_monitor, …). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- chromereleases.googleblog.com/2024/08/stable-channel-update-for-desktop_28.html (Release Notes)
- issues.chromium.org/issues/360265320 (Permissions Required)