Debian LinuxOperating system · Debian
CVE-2014-3160
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 · uneditedThe ResourceFetcher::canRequest function in core/fetch/ResourceFetcher.cpp in Blink, as used in Google Chrome before 36.0.1985.125, does not properly restrict subresource requests associated with SVG files, which allows remote attackers to bypass the Same Origin Policy via a crafted file.
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 confidenceThe ResourceFetcher::canRequest function in Blink's ResourceFetcher.cpp fails to properly restrict subresource requests associated with SVG files, allowing a crafted SVG file to make requests to origins other than its own, thereby bypassing the Same Origin Policy.
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
Debian LinuxOperating system
= 7.0= 8.0
ChromeWeb browser
= 36.0.1985.1= 36.0.1985.2= 36.0.1985.3= 36.0.1985.4= 36.0.1985.5= 36.0.1985.6= 36.0.1985.8= 36.0.1985.12= 36.0.1985.13= 36.0.1985.14= 36.0.1985.15= 36.0.1985.16CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 the browser typeCheck if the installed browser uses Blink rendering engine (Google Chrome, Chromium, or Chromium-based browsers like Opera, Edge legacy). On Linux, run: which chromium-browser chrome google-chrome or check the browser's about/version page.Affected if The browser is Google Chrome or any Chromium-based browser using the vulnerable Blink engine
-
Check Google Chrome versionOpen chrome://version or go to Settings > About Chrome. Note the full version number (e.g., 36.0.1985.125).Affected if The version is 36.0.1985.1 through 36.0.1985.16 (any 36.x build before 36.0.1985.125)
-
Check Chromium version on DebianOn Debian 7 or 8, run: dpkg -l | grep -i chromium or apt-cache policy chromium. This shows installed chromium package version.Affected if Chromium package version is within the 36.x series before the security patch
-
Verify SVG subresource loading behaviorLoad a locally hosted SVG file that contains references to external resources (e.g., <image href='https://other-domain.com/image.png'>). Monitor network requests to see if the browser makes cross-origin requests.Affected if The SVG file successfully loads external subresources from different origins, indicating the Same Origin Policy bypass is present
A user is affected if they are running Google Chrome or a Chromium-based browser with Blink engine version 36.0.1985.1 through 36.0.1985.16, where crafted SVG files can bypass Same Origin Policy to make unauthorized cross-origin requests.
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 or Chromium-based browsers to version 36.0.1985.125 or later, which contains the fix for this Same Origin Policy bypass in SVG subresource loading.
Fix this in Debian Linux
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-2014-3160 — 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-2014-3160 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