dbcve.org
ChromeWeb browser · Google

CVE-2024-8198

HIGH · 8.8 CVSS v3.1 Published 2024-08-28
Fix available
A fix is available. Upgrade to 128.0.6613.113 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Heap buffer overflow vulnerability in Skia's graphics rendering code in Google Chrome. A remote attacker who has already compromised the renderer process can exploit this via a specially crafted HTML page to achieve heap corruption, potentially leading to arbitrary code execution.

MitigationUpgrade Google Chrome to version 128.0.6613.113 or later. Organizations should ensure Chrome is updated via their patch management processes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChromeWeb browser
Affected:< 128.0.6613.113

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Chrome version
    Open Chrome and navigate to chrome://version, or go to Help > About Google Chrome. Alternatively, run 'google-chrome --version' from command line on Linux, or check the application properties on Windows/Mac.
    Affected if The displayed version is lower than 128.0.6613.113 (for example, 128.0.6613.84, 127.0.6xx.xxxx, etc.)
  2. Verify Chrome's renderer process availability
    This vulnerability requires the renderer process to be accessible. In standard Chrome usage, the renderer processes handle all web page content. There is no configuration to disable this for normal browsing.
    Affected if Chrome is used for web browsing - the renderer process is always active for web content
  3. Confirm Chrome update status
    Navigate to chrome://settings/help in the browser. This shows both the current version and whether the browser is up to date.
    Affected if The page shows an update is available or the version listed is below 128.0.6613.113
  4. Check Chrome channel and update mechanism
    In enterprise environments, check group policy settings for Chrome update management, or inspect the registry key HKLM\Software\Google\Update\Clients\{Google Chrome\Application} on Windows for the version field.
    Affected if The version field shows a build number below 6613.113 or the update channel is set to a version older than 128.0.6613.113

You are affected if the installed Google Chrome version is any build lower than 128.0.6613.113, as the heap buffer overflow in Skia's rendering code exists in all earlier versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 128.0.6613.113 or later
Fixed in 128.0.6613.113
Interim mitigation

Upgrade Google Chrome to version 128.0.6613.113 or later. Organizations should ensure Chrome is updated via their patch management processes.

Recommended fix High confidence

Chrome 128.0.6613.113 or later

  1. 1. Open Google Chrome browser
  2. 2. Navigate to Chrome Menu > Help > About Google Chrome
  3. 3. The browser will automatically check for updates
  4. 4. If version 128.0.6613.113 or later is available, click 'Update Google Chrome'
  5. 5. Restart the browser to apply the update
  6. 6. Verify the version by returning to Help > About Google Chrome and confirm the version is 128.0.6613.113 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8198 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-8198 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data