dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 22 Jun 2022.
ChromeWeb browser · Google

CVE-2017-5070

HIGH · 8.8 CVSS v3.1 Published 2017-10-27
Fix available
A fix is available. Upgrade to 59.0.3071.86 / 59.0.3071.92 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Public exploit 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
Type confusion in V8 in Google Chrome prior to 59.0.3071.86 for Linux, Windows, and Mac, and 59.0.3071.92 for Android, allowed a remote attacker to execute arbitrary code inside a sandbox 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

Type confusion vulnerability in the V8 JavaScript engine in Google Chrome allows a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. The vulnerability stems from improper type handling in V8 that can be exploited to achieve code execution.

MitigationUpdate Google Chrome to version 59.0.3071.86 or later for desktop platforms, or 59.0.3071.92 or later for Android. This is a critical security update that patches the type confusion vulnerability.

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:< 59.0.3071.86< 59.0.3071.92
Enterprise Linux DesktopOperating system
Affected:= 6.0
Enterprise Linux ServerOperating system
Affected:= 6.0
Enterprise Linux WorkstationOperating system
Affected:= 6.0

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 Google Chrome version on desktop (Windows, Mac, Linux)
    Open Chrome, click the three-dot menu > Help > About Google Chrome, or navigate to chrome://settings/help. Note the version number shown.
    Affected if Version is earlier than 59.0.3071.86 (e.g., 59.0.3071.85 or lower)
  2. Check Google Chrome version on Android
    Open Chrome on Android, tap the three-dot menu > Settings > About Chrome, or navigate to chrome://version. Note the version number shown.
    Affected if Version is earlier than 59.0.3071.92 (e.g., 59.0.3071.91 or lower)
  3. Check if Chrome is the default browser on Red Hat Enterprise Linux 6.0
    On RHEL 6.0 systems, verify if Google Chrome is installed by running 'google-chrome --version' or checking the package manager for chrome-browser. This applies to Desktop, Server, and Workstation variants.
    Affected if Chrome version is earlier than 59.0.3071.86 (the version bundled with RHEL 6.0 is affected if below this)
  4. Confirm V8 JavaScript engine is in use
    This vulnerability exists in the V8 engine which is built into Chrome. No configuration check is needed; any Chrome installation with JavaScript enabled is potentially affected.
    Affected if Using Chrome with JavaScript enabled (the default state) on an affected version

You are affected if Google Chrome version is below 59.0.3071.86 on desktop/Linux/Mac, or below 59.0.3071.92 on Android.

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 59.0.3071.86 / 59.0.3071.92 or later
Fixed in 59.0.3071.8659.0.3071.92
Interim mitigation

Update Google Chrome to version 59.0.3071.86 or later for desktop platforms, or 59.0.3071.92 or later for Android. This is a critical security update that patches the type confusion vulnerability.

Recommended fix High confidence

Chrome 59.0.3071.86 (Linux/Windows/Mac) or 59.0.3071.92 (Android)

  1. Open Chrome browser and navigate to Chrome menu > Help > About Google Chrome
  2. Click 'Check for updates' or wait for automatic update check
  3. Allow Chrome to download and install version 59.0.3071.86 or later
  4. Restart the browser when prompted to complete the update
  5. For Enterprise Linux systems, run 'sudo yum update google-chrome-stable' to apply the security update

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

Fix this in Chrome Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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