dbcve.org
ChromeWeb browser · Google

CVE-2018-17479

HIGH · 8.8 CVSS v3.0 Published 2019-06-27
Fix available
A fix is available. Upgrade to 70.0.3538.110 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
Incorrect object lifetime calculations in GPU code in Google Chrome prior to 70.0.3538.110 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

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

This is a use-after-free vulnerability in Google Chrome's GPU rendering code caused by incorrect object lifetime calculations. The flaw allows a remote attacker to corrupt heap memory through a specially crafted HTML page, potentially enabling arbitrary code execution.

MitigationUpdate Google Chrome to version 70.0.3538.110 or later to address the object lifetime calculation error in the GPU code.

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:< 70.0.3538.110

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.0/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 if Google Chrome is installed
    Look for the chrome executable in standard locations (e.g., C:\Program Files\Google\Chrome\Application\chrome.exe on Windows, /Applications/Google Chrome.app on macOS, or via 'which google-chrome' command on Linux)
    Affected if Google Chrome is not installed on the system
  2. Determine the installed Chrome version
    Launch Chrome and navigate to chrome://version, or run 'google-chrome --version' from command line. The version number is displayed at the top of the page or in the command output
    Affected if The installed version is lower than 70.0.3538.110 (for example, 70.0.3538.100 or earlier)
  3. Check if GPU hardware acceleration is enabled
    In Chrome, navigate to chrome://settings and verify that Hardware Acceleration is enabled under System settings, or check chrome://gpu for GPU-related status information
    Affected if GPU hardware acceleration is enabled - the vulnerability exists in the GPU rendering code path, so this is required for the flaw to be reachable

The user is affected if Google Chrome is installed with a version lower than 70.0.3538.110 AND GPU hardware acceleration is enabled, allowing the specially crafted HTML page to trigger the use-after-free in GPU rendering code.

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.

From vendor data
Upgrade available Upgrade to 70.0.3538.110 or later
Fixed in 70.0.3538.110
Interim mitigation

Update Google Chrome to version 70.0.3538.110 or later to address the object lifetime calculation error in the GPU code.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-17479 — 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-2018-17479 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