ChromeWeb browser · Google
CVE-2017-5097
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 · uneditedInsufficient validation of untrusted input in Skia in Google Chrome prior to 60.0.3112.78 for Linux allowed a remote attacker to perform an out of bounds memory read 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 confidenceOut-of-bounds memory read vulnerability in Skia graphics library within Google Chrome for Linux. Insufficient validation of untrusted input in the Skia component allows a remote attacker to read arbitrary memory via a specially crafted HTML page.
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
<= 60.0.3112.76
Debian LinuxOperating system
= 9.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Google Chrome for Linux is installedRun 'google-chrome --version' or 'google-chrome-stable --version' in terminal, or open chrome://version in the browser address barAffected if No Chrome installation found means not affected by this specific Chrome vulnerability
-
Identify the exact Chrome version numberExamine the output from the version check command - it will display a numeric version like 60.0.3112.xAffected if Version number cannot be determined - vulnerability status is unclear
-
Compare installed version against the affected rangeCheck if the version number is 60.0.3112.76 or earlier (any version up to and including 60.0.3112.76)Affected if Installed version is 60.0.3112.76 or lower - the environment falls within the vulnerable version range
-
Verify the operating system is LinuxRun 'uname -a' or check that the Chrome package was installed via a Linux package manager (dpkg/rpm)Affected if Not running Linux - this CVE specifically targets Google Chrome for Linux only
-
Confirm Skia graphics component is in useThis is implicit in Chrome's rendering pipeline; no direct config check required - all Chrome builds with Skia enabled are potentially affectedAffected if Skia is disabled or not compiled into the Chrome build (uncommon in standard installations)
A user is affected if they are running Google Chrome for Linux version 60.0.3112.76 or earlier, where the Skia component can be triggered by malicious HTML content to read out-of-bounds memory.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Google Chrome for Linux to version 60.0.3112.78 or later to address the insufficient input validation in Skia.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5097 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-5097 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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