ChromeWeb browser · Google
CVE-2017-15427
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 socially engineered user to XSS themselves by dragging and dropping a javascript: URL into the URL bar.
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 confidenceInsufficient policy enforcement in Google Chrome's Omnibox (URL bar) allowed a socially engineered user to trigger XSS by dragging and dropping a javascript: URL into the URL bar. This self-XSS vulnerability existed because Chrome did not properly sanitize or block javascript: URLs when dropped into the omnibox, allowing script execution in the context of the page.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 versionOpen Chrome, navigate to chrome://settings/help, or run 'google-chrome --version' or 'chrome --version' in terminalAffected if Version is below 63.0.3239.84
-
Verify Red Hat Enterprise Linux version (if applicable)Run 'cat /etc/redhat-release' or 'hostnamectl' to check OS versionAffected if Running RHEL Desktop/Server/Workstation version 6.0 with Chrome below 63.0.3239.84
-
Verify Debian version (if applicable)Run 'cat /etc/debian_version' to check OS versionAffected if Running Debian Linux 9.0 with Chrome below 63.0.3239.84
-
Test drag-and-drop javascript: URL behavior (proof-of-concept)Create a test page with a draggable javascript:alert('XSS') link. Attempt to drag it into the Chrome omnibox. Observe if the URL bar accepts it and if script executes upon pressing Enter.Affected if The javascript: URL is accepted in the omnibox after drag-and-drop and executes JavaScript when the user presses Enter
A user is affected if they are running Google Chrome version below 63.0.3239.84 (or the specific RHEL 6.0/Debian 9.0 distributions mentioned) and can be tricked into dragging a javascript: URL into the omnibox.
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. Implement endpoint management policies to ensure browsers remain updated.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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-15427 — 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-15427 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