chromium-browser: Wildcard matching issue in CSP
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 6 Supplementary | |||
| chromium-browser-0:47.0.2526.73-1.el6 | cpe:/a:redhat:rhel_extras:6 | RHSA-2015:2545 | 2015-12-03T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-3415-1 | chromium-browser security update |
EUVD |
EUVD-2015-6722 | The CSPSource::hostMatches function in WebKit/Source/core/frame/csp/CSPSource.cpp in the Content Security Policy (CSP) implementation in Google Chrome before 47.0.2526.73 accepts an x.y hostname as a match for a *.x.y pattern, which might allow remote attackers to bypass intended access restrictions in opportunistic circumstances by leveraging a policy that was intended to be specific to subdomains. |
Ubuntu USN |
USN-2825-1 | Oxide vulnerabilities |
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.7% (1.721% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.