ChromeWeb browser · Google
CVE-2017-5053
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 · uneditedAn out-of-bounds read in V8 in Google Chrome prior to 57.0.2987.133 for Linux, Windows, and Mac, and 57.0.2987.132 for Android, allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page, related to Array.prototype.indexOf.
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 read vulnerability in V8 JavaScript engine's Array.prototype.indexOf implementation in Google Chrome prior to 57.0.2987.133 (desktop) and 57.0.2987.132 (Android). Allows remote arbitrary code execution via 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
< 57.0.2987.133< 57.0.2987.132
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 Google Chrome desktop versionOpen Chrome, click the menu icon (three dots), select Help, then About Google Chrome. The version number is displayed on this page.Affected if Version shown is less than 57.0.2987.133
-
Check Google Chrome version via command line (desktop)On Linux or macOS, run 'google-chrome --version' or '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' respectively in a terminal.Affected if Version output is less than 57.0.2987.133
-
Check Google Chrome version on AndroidOpen the Google Chrome app on Android, tap the three-dot menu, select Settings, then scroll to About Chrome to view the version.Affected if Version shown is less than 57.0.2987.132
-
Check for Chrome bundled with Red Hat Enterprise Linux 6.0On RHEL 6.0 Desktop, Server, or Workstation, run 'rpm -q google-chrome-stable' or check /usr/bin/google-chrome for version information.Affected if Chrome is installed on RHEL 6.0 and version is below 57.0.2987.133
You are affected if Google Chrome (desktop) version is below 57.0.2987.133, Chrome for Android is below 57.0.2987.132, or Chrome is installed on RHEL 6.0 systems.
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.
dbcve · scoped57.0.2987.13257.0.2987.133
Upgrade Google Chrome to version 57.0.2987.133 or later for desktop platforms, and 57.0.2987.132 or later for Android.
Chrome 57.0.2987.133 (desktop) / 57.0.2987.132 (Android) or later stable release
- Check current Chrome version by navigating to chrome://settings/help
- Download Chrome 57.0.2987.133 or later from google.com/chrome or use system package manager
- Install the updated Chrome version
- Restart the Chrome browser to apply the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5053 — 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-5053 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