ChromeWeb browser · Google
CVE-2017-15420
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 · uneditedIncorrect handling of back navigations in error pages in Navigation in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) 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 confidenceIn Google Chrome versions prior to 63.0.3239.84, improper handling of back navigation on error pages allowed a remote attacker to manipulate the Omnibox (URL bar) to display a spoofed URL while the user was actually viewing a different (potentially malicious) page. This URL spoofing vulnerability could facilitate phishing attacks by tricking users into believing they are on a legitimate website.
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
= 8.0= 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.
-
Confirm Google Chrome is installedOn Windows, look for Chrome in Program Files/Google/Chrome/Application folder or check via Settings > Apps. On Linux, run 'which google-chrome' or 'rpm -q google-chrome' (RHEL) or 'dpkg -l google-chrome' (Debian). On macOS, check /Applications for Google Chrome.appAffected if Google Chrome browser is present on the system
-
Determine installed Chrome version numberOpen Chrome, click the three-dot menu, select Help, then About Google Chrome. Alternatively, run 'google-chrome --version' in terminal (Linux/macOS) or check the chrome.exe properties (Windows)Affected if Unable to retrieve version information
-
Compare version against vulnerable rangeCompare the installed version to 63.0.3239.84. Any version below this number (such as 63.0.3239.83, 62.x.x.x, 61.x.x.x, etc.) is within the vulnerable rangeAffected if Installed version is less than 63.0.3239.84 (for example: 63.0.3239.83, 62.0.2924.76, 61.0.3163.100)
-
Check browser auto-update status (optional)In Chrome, go to chrome://settings/help and look for update status under 'Update Chrome' section. The browser should show 'Chrome is up to date' when fully patchedAffected if Update status shows an outdated version or update failed
You are affected if Google Chrome is installed and its version number is 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 to remediate this vulnerability. Organizations should ensure end-user browsers are patched through their patch management processes.
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-15420 — 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-15420 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