CVE-2015-6786
chromium-browser: Scheme bypass in CSP
Overview
Description
The CSPSourceList::matches function in WebKit/Source/core/frame/csp/CSPSourceList.cpp in the Content Security Policy (CSP) implementation in Google Chrome before 47.0.2526.73 accepts a blob:, data:, or filesystem: URL as a match for a * pattern, which allows remote attackers to bypass intended scheme restrictions in opportunistic circumstances by leveraging a policy that relies on this pattern.
Source: OX vulnerability database
Severity
4.3 · MEDIUM
CVSS 2.0 base score, scored by NVD.
- Access vector
- Network
- Access complexity
- Medium
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:N/I:P/A:N
Weakness: CWE-264
Affected packages · 0
No registry package. This ID affects operating system packages only.
Operating systems · 2 fixes
openSUSE 1 release · 2 packages
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Tumbleweed | ungoogled-chromium +1 | 113.0.5672.92-1.1 | openSUSE-SU-2024:12948-1 |
| Tumbleweed | chromedriver +1 | 55.0.2883.75-3.1 | openSUSE-SU-2024:10171-1 |
References
- googlechromereleases.blogspot.com http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html
- lists.opensuse.org http://lists.opensuse.org/opensuse-security-announce/2015-12/msg00016.html
- lists.opensuse.org http://lists.opensuse.org/opensuse-security-announce/2015-12/msg00017.html
- www.debian.org http://www.debian.org/security/2015/dsa-3415
- www.securityfocus.com http://www.securityfocus.com/bid/78416
- www.securitytracker.com http://www.securitytracker.com/id/1034298
- www.ubuntu.com http://www.ubuntu.com/usn/USN-2825-1
- access.redhat.com https://access.redhat.com/security/cve/CVE-2015-6786
- code.google.com https://code.google.com/p/chromium/issues/detail?id=534570
- codereview.chromium.org https://codereview.chromium.org/1361763005/
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.