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-5030

HIGH · 8.8 CVSS v3.1 Published 2017-04-24
Fix available
A fix is available. Upgrade to 57.0.2987.98 / 57.0.2987.108 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
Incorrect handling of complex species in V8 in Google Chrome prior to 57.0.2987.98 for Linux, Windows, and Mac and 57.0.2987.108 for Android allowed a remote attacker to execute arbitrary code 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

A memory corruption vulnerability in Google Chrome's V8 JavaScript engine allowed remote code execution through a crafted HTML page. The flaw involved incorrect handling of 'complex species' (certain JavaScript objects/arrays) in the JIT compilation process, potentially enabling an attacker to escape the sandbox and execute arbitrary code.

MitigationUpdate Google Chrome to version 57.0.2987.98 or later for desktop platforms, and 57.0.2987.108 or later for Android. Organizations should deploy the update via their patch management systems.

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:< 57.0.2987.98< 57.0.2987.108
Debian LinuxOperating system
Affected:= 8.0= 9.0
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 if Google Chrome is installed
    On Windows: Open Control Panel > Programs and look for Google Chrome, or run 'chrome --version' from command line. On macOS: Run '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' or check in Applications folder. On Linux: Run 'google-chrome --version' or 'chromium-browser --version' in terminal.
    Affected if Google Chrome is not installed on the system
  2. Determine the installed Chrome version number
    Run 'google-chrome --version' on Linux, 'chrome --version' on Windows in command prompt, or on macOS run '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' in Terminal.
    Affected if Unable to determine the installed Chrome version
  3. Compare version against vulnerable thresholds
    Compare the installed version to 57.0.2987.98. The version string format is typically '57.0.2987.xx' where xx is the patch number. For Android Chrome, compare to 57.0.2987.108.
    Affected if Installed version is less than 57.0.2987.98 (or less than 57.0.2987.108 for Android Chrome)
  4. Verify the V8 JavaScript engine is in use
    This vulnerability exists in Chrome's V8 engine which is always active when Chrome processes JavaScript. No manual check needed - simply using Chrome to browse the web triggers the vulnerable component.
    Affected if Using Chrome to process any JavaScript-containing web content

The environment is affected if Google Chrome is installed with a version lower than 57.0.2987.98 (or 57.0.2987.108 for Android), and the user processes untrusted JavaScript content through the browser.

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 57.0.2987.98 / 57.0.2987.108 or later
Fixed in 57.0.2987.9857.0.2987.108
Interim mitigation

Update Google Chrome to version 57.0.2987.98 or later for desktop platforms, and 57.0.2987.108 or later for Android. Organizations should deploy the update via their patch management systems.

Recommended fix High confidence

Chrome 57.0.2987.98 or later for desktop, Chrome 57.0.2987.108 or later for Android; or use distribution-provided package updates

  1. For Chrome desktop (Linux, Windows, Mac): Navigate to chrome://settings/help and click 'Update Google Chrome', or download the latest version from https://www.google.com/chrome/
  2. For Chrome on Android: Update through the Google Play Store
  3. For Debian Linux systems: Run 'apt-get update && apt-get upgrade' or 'apt-get update && apt-get install chromium' to get the patched version
  4. For RHEL/CentOS Enterprise Linux 6.0: Run 'yum update' or 'yum update chromium-browser' to apply the security update
Caveat None expected - this is a security patch update within the same major version branch

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

Fix this in Chrome Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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