ChromeWeb browser · Google
CVE-2017-5077
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 59.0.3071.86 for Linux, Windows, and Mac, and 59.0.3071.92 for Android, 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 confidenceAn out-of-bounds memory read vulnerability in Google Chrome's Skia graphics library caused by insufficient validation of untrusted input. A remote attacker could exploit this by tricking users into visiting a crafted HTML page, allowing the browser to read memory outside intended boundaries.
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
< 59.0.3071.86< 59.0.3071.92
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux WorkstationOperating system
= 6.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.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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Google Chrome versionOpen Chrome, go to Settings > About Chrome, or navigate to chrome://version, or run 'google-chrome --version' or 'chrome --version' from command lineAffected if Version is earlier than 59.0.3071.86 (or 59.0.3071.92 for Android)
-
Verify Chrome is used for browsingConfirm Google Chrome browser is installed and used as a web browser on the systemAffected if Chrome is present and running with a vulnerable version number
-
Check Skia library version (if accessible)On Linux, run 'ldd /opt/google/chrome/chrome | grep skia' or examine the Skia library file in the Chrome installation directoryAffected if Skia library version corresponds to Chrome versions prior to 59.0.3071.86
-
Identify Red Hat Enterprise Linux Chrome packageOn RHEL 6.0 systems, check if Chrome was installed via Red Hat packages using 'rpm -qa | grep -i chrome' or 'yum list installed google-chrome*'Affected if Red Hat Enterprise Linux 6.0 with Chrome package installed from RHEL repositories
-
Confirm vulnerable Skia feature is in useThe vulnerability triggers when processing untrusted input in the Skia graphics library; ensure Chrome is used for rendering HTML content from untrusted sourcesAffected if Chrome with vulnerable version processes web content
A user is affected if Google Chrome version is below 59.0.3071.86 (or 59.0.3071.92 for Android), or if using Chrome on RHEL 6.0 from Red Hat packages, and the browser is used to visit untrusted web pages.
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 data59.0.3071.8659.0.3071.92
Update Google Chrome to version 59.0.3071.86 or later (59.0.3071.92 for Android) to incorporate the patched Skia library with proper input validation.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5077 — 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-5077 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