ChromeWeb browser · Google
CVE-2017-5052
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 incorrect assumption about block structure in Blink in Google Chrome prior to 57.0.2987.133 for Mac, Windows, and Linux, and 57.0.2987.132 for Android, allowed a remote attacker to potentially exploit memory corruption via a crafted HTML page that triggers improper casting.
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 · moderate confidenceMemory corruption vulnerability in Google Chrome's Blink rendering engine caused by incorrect assumptions about HTML block structure, leading to improper type casting when processing crafted HTML pages. This type confusion can be exploited to achieve arbitrary memory read/write, potentially allowing remote code execution.
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
- 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 installedOn Windows, look for Google Chrome in Program Files or check Start menu. On Linux, run 'which google-chrome' or 'which chromium-browser'. On macOS, check /Applications for Google Chrome.appAffected if Google Chrome or Chromium is present on the system
-
Determine installed Chrome versionOpen Chrome, click the three-dot menu, select Help, then About Google Chrome. Alternatively, run 'google-chrome --version' or 'chromium-browser --version' from command line on LinuxAffected if Version number is displayed for comparison
-
Compare version against vulnerability thresholdCompare the installed version to the affected range: versions prior to 57.0.2987.133 (desktop) or 57.0.2987.132 (Android) are vulnerable. Note: 57.0.2987.133 is the fixed versionAffected if Installed version is less than 57.0.2987.133 (or less than 57.0.2987.132 for Android)
-
Check Red Hat Enterprise Linux version if applicableRun 'cat /etc/redhat-release' or 'cat /etc/os-release' to identify the RHEL versionAffected if System is running RHEL 6.0 Desktop, Server, or Workstation
The environment is affected if Google Chrome (or Chromium) version is below 57.0.2987.133, or if the system is RHEL 6.0 with the vulnerable Chrome version installed
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 data57.0.2987.13257.0.2987.133
Update Google Chrome to version 57.0.2987.133 or later (57.0.2987.132 for Android) to patch the vulnerability. Ensure automatic updates are enabled or deploy the update via enterprise management tools.
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-5052 — 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-5052 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