ChromeWeb browser · Google
CVE-2017-5117
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 · uneditedUse of an uninitialized value in Skia in Google Chrome prior to 61.0.3163.79 for Linux and Windows allowed a remote attacker to obtain potentially sensitive information from process memory 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 confidenceUse of an uninitialized value in Skia (Google's graphics library) in Google Chrome versions prior to 61.0.3163.79 allows a remote attacker to read potentially sensitive information from process memory when processing a crafted HTML page. The vulnerability stems from Skia failing to initialize memory before using it in graphics operations.
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
< 61.0.3163.79
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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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.
-
Determine installed Google Chrome versionOpen Chrome, click the three-dot menu > Help > About Google Chrome, or navigate to chrome://settings/helpAffected if The displayed version number is lower than 61.0.3163.79
-
Verify Chrome version via command lineOn Windows, check Registry key HKEY_CURRENT_USER\Software\Google\Chrome\BLBeacon\version or run 'chrome --version' in command prompt. On macOS, run '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --version'. On Linux, run 'google-chrome --version' or 'chromium-browser --version'Affected if The reported version is earlier than 61.0.3163.79
-
Confirm Skia graphics library is in useThe vulnerability exists in the Skia graphics engine which is enabled by default in Google Chrome. No additional configuration check is required - if Chrome is running with default rendering settings, Skia is activeAffected if Chrome is running with default graphics settings (no software rendering flags or alternate GPU settings that disable Skia)
-
Check for Chrome on Debian Linux 9.0If running Debian 9.0, verify Chrome installation with 'dpkg -l | grep chrome' or check /opt/google/chrome/ directory. Note: Google Chrome support on Debian was limited; ensure the installed package version is capturedAffected if Google Chrome is installed on Debian 9.0 at any version (Debian 9.0 is listed as affected)
A user is affected if they are running any version of Google Chrome earlier than 61.0.3163.79, or have Google Chrome installed on Debian Linux 9.0, as the uninitialized Skia memory flaw can be triggered by visiting a crafted HTML page.
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 data61.0.3163.79
Update Google Chrome to version 61.0.3163.79 or later. Deploy via standard enterprise patch management processes (e.g., WSUS, SCCM, Group Policy) to ensure all affected endpoints receive the update.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5117 — 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-5117 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