ChromeWeb browser · Google
CVE-2017-15425
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 63.0.3239.84 allowed a remote attacker to perform domain spoofing via IDN homographs in 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 confidenceThis is an IDN (Internationalized Domain Name) homograph attack vulnerability in Google Chrome's Omnibox (address bar). The browser failed to properly enforce policies preventing domain spoofing when displaying IDN domains with look-alike characters from different scripts (e.g., Cyrillic letters that resemble Latin characters). This allowed attackers to craft URLs that appeared legitimate to users but led to malicious sites.
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
< 63.0.3239.84
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux WorkstationOperating system
= 6.0
Debian LinuxOperating system
= 9.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.0/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 installedOn Windows: Look for Chrome in Program Files or check registry. On Linux: Run 'which google-chrome' or 'which chromium-browser'. On Mac: Check /Applications for Google Chrome.appAffected if Chrome is not installed on the system
-
Determine the installed Chrome versionOn Windows: Right-click Chrome shortcut, select Properties, look at 'Details' tab for version, or run 'chrome://version' in address bar. On Linux: Run 'google-chrome --version' or 'chromium-browser --version'. On Mac: Right-click Google Chrome.app, select Get InfoAffected if Unable to retrieve a version number means Chrome may not be properly installed
-
Compare installed version against the vulnerable rangeCompare the version number found to 63.0.3239.84. The version is displayed as a four-part number (e.g., 62.0.3202.94)Affected if Installed version is less than 63.0.3239.84 (e.g., 62.x, 61.x, etc.)
-
Verify the exact version on Red Hat or Debian systemsOn RHEL 6.0: Run 'rpm -qa | grep -i chrome'. On Debian 9.0: Run 'dpkg -l | grep -i chrome'Affected if Package shows a version lower than 63.0.3239.84
The system is affected if Google Chrome or Chromium is installed with a version number lower than 63.0.3239.84.
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 data63.0.3239.84
Update Google Chrome to version 63.0.3239.84 or later. For enterprise environments, deploy the updated browser version organization-wide using 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-15425 — 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-15425 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