Ubuntu LinuxOperating system · Canonical
CVE-2016-1692
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 · uneditedWebKit/Source/core/css/StyleSheetContents.cpp in Blink, as used in Google Chrome before 51.0.2704.63, permits cross-origin loading of CSS stylesheets by a ServiceWorker even when the stylesheet download has an incorrect MIME type, which allows remote attackers to bypass the Same Origin Policy via a crafted web 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 · high confidenceA Same Origin Policy bypass vulnerability in Blink's StyleSheetContents.cpp allows ServiceWorkers to load cross-origin CSS stylesheets even when they have incorrect MIME types. This permits attackers on crafted websites to bypass MIME type validation and load malicious content as CSS from other origins.
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
Ubuntu LinuxOperating system
= 14.04= 15.10= 16.04
Debian LinuxOperating system
= 8.0
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux WorkstationOperating system
= 6.0
ChromeWeb browser
<= 50.0.2661.102= 42.1= 13.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Identify if Google Chrome is installedRun 'google-chrome --version' or 'chromium-browser --version' in terminal, or check /usr/bin/google-chrome or /usr/bin/chromium-browserAffected if Chrome or Chromium browser is present on the system
-
Check the installed Chrome versionRun 'google-chrome --version' and compare the version number to 50.0.2661.102Affected if The installed version is 50.0.2661.102 or earlier (any version <= 50.0.2661.102)
-
Verify ServiceWorkers are enabledIn Chrome, navigate to chrome://settings/privacy, scroll to Content, click Content settings, search for ServiceWorkers, or visit chrome://serviceworker-internals/Affected if ServiceWorkers are enabled (this is the feature that must be active for the vulnerability to be exploitable)
-
Check Linux distribution versionRun 'cat /etc/os-release' or 'lsb_release -a' to identify the OSAffected if Running Ubuntu 14.04, 15.10, or 16.04, Debian 8.0, RHEL 6.0, or openSUSE 42.1/13.2 with the affected Chrome version
A user is affected if they are running Google Chrome version 50.0.2661.102 or earlier on a supported Linux distribution or Windows, with ServiceWorkers enabled in their browser settings.
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 51.0.2704.63 or later. Organizations should ensure browser update policies are in place to push this patch to all endpoints.
Fix this in Ubuntu Linux
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-2016-1692 — 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-2016-1692 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