ChromeWeb browser · Google
CVE-2017-5098
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 · uneditedA use after free in V8 in Google Chrome prior to 60.0.3112.78 for Mac, Windows, Linux, and 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 confidenceA use-after-free vulnerability in Google Chrome's V8 JavaScript engine (versions prior to 60.0.3112.78) allows a remote attacker to perform out-of-bounds memory reads via a crafted HTML page. The vulnerability occurs when memory allocated for a JavaScript object is freed but a reference to that memory is still retained, leading to potential information disclosure or memory corruption.
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.78
Debian LinuxOperating system
= 9.0
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 if Google Chrome is installedOpen a terminal and run: google-chrome --version or chromium --version. On Windows, check Program Files/Google/Chrome/Application/chrome.exe. On macOS, check /Applications/Google Chrome.appAffected if Chrome or Chromium browser is found on the system
-
Determine the installed Google Chrome versionRun: google-chrome --version (Linux) or right-click Chrome shortcut and choose Properties to view version (Windows)Affected if The displayed version number is 60.0.3112.78 or lower
-
Check Debian package version if using Debian Linux 9.0Run: dpkg -l | grep google-chrome or apt-cache policy google-chrome-stableAffected if The installed package version is 60.0.3112.78-1 or lower
-
Check Red Hat Enterprise Linux browser package versionRun: rpm -qa | grep -i chrome (RHEL systems)Affected if The chrome package version corresponds to the vulnerable Chrome release <= 60.0.3112.78
-
Verify JavaScript is enabled (required for exploitation)Open Chrome, navigate to chrome://settings/content, or inspect browser settings. JavaScript is enabled by default.Affected if JavaScript is enabled in the browser settings (this is the default state and required for the exploit to trigger)
You are affected if Google Chrome (or Chromium) version 60.0.3112.78 or lower is installed and JavaScript is enabled, which is the default configuration.
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 dataUpdate Google Chrome to version 60.0.3112.78 or later. Organizations should ensure endpoint management policies enforce automatic browser updates or distribute the patched version to all users.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5098 — 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-5098 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