ChromeWeb browser · Google
CVE-2017-5066
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 consistency checks in signature handling in the networking stack in Google Chrome prior to 58.0.3029.81 for Mac, Windows, and Linux, and 58.0.3029.83 for Android, allowed a remote attacker to incorrectly accept a badly formed X.509 certificate 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 confidenceThis vulnerability in Google Chrome's networking stack involved insufficient consistency checks during X.509 certificate signature validation. A remote attacker could craft a malicious HTML page containing a badly formed X.509 certificate that Chrome would incorrectly accept, potentially enabling man-in-the-middle attacks or site impersonation.
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
< 58.0.3029.81< 58.0.3029.83
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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.
-
Check if Google Chrome is installedInspect the system for Chrome binaries: On Windows look for chrome.exe in Program Files or Program Files (x86); on macOS check /Applications/Google Chrome.app; on Linux check for /usr/bin/google-chrome or query the package manager (rpm -q google-chrome-stable or dpkg -l | grep chrome)Affected if Chrome is installed on the system
-
Determine installed Google Chrome versionRun the Chrome binary with version flag: 'google-chrome --version' or 'chrome --version' on Linux; on Windows right-click chrome.exe and view Properties > Details > File version; on macOS open Google Chrome and navigate to Chrome > About Google ChromeAffected if The version returned is less than 58.0.3029.81 for desktop platforms or less than 58.0.3029.83 for Android
-
Check Red Hat Enterprise Linux version (if Chrome on RHEL)On RHEL systems, run 'cat /etc/redhat-release' or 'hostnamectl' to identify the exact RHEL version; for browsers installed via RHN or yum, query the package: 'rpm -q google-chrome-stable'Affected if The RHEL version equals 6.0 specifically (Desktop, Server, or Workstation) and Google Chrome is in use
A user is affected if Google Chrome version is below 58.0.3029.81 (desktop) or 58.0.3029.83 (Android), or if running Chrome on RHEL version 6.0 exactly.
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 data58.0.3029.8158.0.3029.83
Update Google Chrome to version 58.0.3029.81 or later for desktop platforms, or 58.0.3029.83 or later for Android. Organizations should deploy the browser update through their standard patch management processes.
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-5066 — 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-5066 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