ChromeWeb browser · Google
CVE-2017-5035
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 · uneditedGoogle Chrome prior to 57.0.2987.98 for Windows and Mac had a race condition, which could cause Chrome to display incorrect certificate information for a site.
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 confidenceA race condition in Google Chrome prior to version 57.0.2987.98 for Windows and Mac could cause the browser to display incorrect SSL/TLS certificate information for websites. This could mislead users about the identity of the site they're connecting to, potentially enabling man-in-the-middle attacks where users cannot verify they're on the legitimate site.
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.75
Debian LinuxOperating system
= 8.0= 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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.
-
Identify your operating systemDetermine if the system is running Windows, macOS, Debian Linux, or Red Hat Enterprise Linux. The race condition affects only Windows and macOS versions of Google Chrome.Affected if The system runs Windows or macOS with Google Chrome installed and the version is at or below 57.0.2987.75
-
Check installed Google Chrome version on WindowsOpen Google Chrome, click the menu icon (three dots), select Help, then About Google Chrome. The version number will be displayed on this page.Affected if The displayed version is 57.0.2987.75 or earlier
-
Check installed Google Chrome version on macOSOpen Google Chrome, click Chrome in the menu bar, select About Google Chrome. The version number will be displayed.Affected if The displayed version is 57.0.2987.75 or earlier
-
Check Chrome package version on Debian LinuxOpen a terminal and run: dpkg -l | grep chrome or check the installed package version through your package manager.Affected if Google Chrome or Chromium is installed and the package version corresponds to the browser version 57.0.2987.75 or earlier
-
Check Chrome package version on RHEL 6Open a terminal and run: rpm -qa | grep -i chrome or check via your system's package management tool.Affected if Google Chrome or Chromium is installed and the package version corresponds to the browser version 57.0.2987.75 or earlier
You are affected if Google Chrome (or Chromium) is installed on the system and the installed version number is 57.0.2987.75 or lower, particularly on Windows or macOS where the race condition manifests.
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 57.0.2987.98 or later. In enterprise environments, use patch management tools to ensure all clients receive the update.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5035 — 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-5035 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