dbcve.org
ChromeWeb browser · Google

CVE-2017-5131

HIGH · 8.8 CVSS v3.0 Published 2018-02-07
Fix available
A fix is available. Upgrade to 62.0.3202.62 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
An integer overflow in Skia in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page, aka an out-of-bounds write.

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 an integer overflow vulnerability in the Skia graphics rendering library embedded in Google Chrome. The overflow occurs when processing crafted HTML page content, leading to heap corruption via an out-of-bounds write. A remote attacker can exploit this to potentially execute arbitrary code on the victim's system.

MitigationUpdate Google Chrome to version 62.0.3202.62 or later to obtain the patched Skia library. Organizations should ensure automated browser update mechanisms are enabled or push the update via enterprise deployment tools.

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:< 62.0.3202.62
Debian LinuxOperating system
Affected:= 8.0= 9.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.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 installed Google Chrome version
    Navigate to chrome://settings/help in the Chrome browser, or run 'google-chrome --version' or 'chromium --version' from command line
    Affected if Version is below 62.0.3202.62 (e.g., 62.0.3202.0 or earlier)
  2. Verify Chrome package on Debian systems
    Run 'dpkg -l | grep -i chrom' or 'apt-cache policy google-chrome-stable chromium-browser' to list installed Chrome/Chromium packages and versions
    Affected if Package version is below 62.0.3202.62-1 or the installed version is older than the fixed release
  3. Confirm Chrome is in use
    Check for running Chrome processes with 'ps aux | grep -i chrom' or check browser usage logs
    Affected if Chrome versions below 62.0.3202.62 are actively being used to browse untrusted web content

You are affected if Google Chrome or Chromium installed on the system is version 62.0.3202.62 or earlier, and users browse web content with 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.

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

Update Google Chrome to version 62.0.3202.62 or later to obtain the patched Skia library. Organizations should ensure automated browser update mechanisms are enabled or push the update via enterprise deployment tools.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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