ChromeWeb browser · Google
CVE-2017-5089
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 Policy Enforcement in Omnibox in Google Chrome prior to 59.0.3071.104 for Mac allowed a remote attacker to perform domain spoofing via a crafted domain name.
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 domain spoofing vulnerability existed in Google Chrome's Omnibox (address bar) component. The browser failed to properly enforce policy when rendering certain crafted domain names, allowing the address bar to display a fraudulent domain while the user was actually visiting a different site. This could enable phishing attacks by making malicious sites appear to be legitimate.
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
< 59.0.3071.104
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 Google Chrome version on desktop systemsOpen Chrome, click the three-dot menu, select Help, then About Google Chrome. The version number is displayed on that page.Affected if The displayed version is earlier than 59.0.3071.104 (for example, 59.0.3071.75 or lower)
-
Check Google Chrome version via command line (if available)Run 'google-chrome --version' or 'chrome --version' in a terminal window.Affected if The output shows a version number less than 59.0.3071.104
-
Verify Chrome version on Red Hat Enterprise Linux 6.0Use the package manager: 'rpm -q google-chrome' or 'yum list installed google-chrome' to check if Chrome is installed and its version.Affected if Chrome is installed and the version is earlier than 59.0.3071.104 on an RHEL 6.0 system
-
Inspect Omnibox behavior with crafted URLsManually navigate to a URL with unusual characters (such as mixed scripts or homograph characters) and observe whether the address bar displays a different domain than the actual navigation target.Affected if The displayed domain in the address bar does not match the actual domain being visited
You are affected if Google Chrome version is earlier than 59.0.3071.104, or if the address bar displays a different domain than the site actually being visited.
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 data59.0.3071.104
Update Google Chrome for Mac to version 59.0.3071.104 or later to patch the vulnerability. Users should also be educated to verify site certificates and be cautious of unexpected address bar behavior.
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-5089 — 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-5089 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