CVE-2016-1617
What it is
The CSPSource::schemeMatches function in WebKit/Source/core/frame/csp/CSPSource.cpp in the Content Security Policy (CSP) implementation in Blink, as used in Google Chrome before 48.0.2564.82, does not apply http policies to https URLs and does not apply ws policies to wss URLs, which makes it easier for remote attackers to determine whether a specific HSTS web site has been visited by reading a CSP report.
At a glance
- Exploitability
- Can be exploited over the network without logging in, but needs a user to act. Limited direct impact.
- Exploit odds
- 1.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 1.3% in the next 30 days (EPSS).
- Severity: 4.3 MEDIUM (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 1.3% · EPSS, next 30 days
- Weakness
- CWE-200 · Information exposure
- Record status
- Modified
Affected
- Google Chrome ≤ 47.0.2526.106
Attack profile CVSS 3.0 · 4.3
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Raw vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2016-1617.md and follow it. Check whether this project is affected by CVE-2016-1617. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- http://googlechromereleases.blogspot.com/2016/01/stable-channel-update_20.html
- http://lists.opensuse.org/opensuse-security-announce/2016-01/msg00035.html
- http://lists.opensuse.org/opensuse-security-announce/2016-01/msg00036.html
- http://lists.opensuse.org/opensuse-security-announce/2016-01/msg00046.html
- http://rhn.redhat.com/errata/RHSA-2016-0072.html
- http://www.debian.org/security/2016/dsa-3456
- http://www.securityfocus.com/bid/81430
- http://www.securitytracker.com/id/1034801
- http://www.ubuntu.com/usn/USN-2877-1
- https://code.google.com/p/chromium/issues/detail?id=544765
- https://codereview.chromium.org/1455973003
- https://security.gentoo.org/glsa/201603-09
- http://googlechromereleases.blogspot.com/2016/01/stable-channel-update_20.html
- http://lists.opensuse.org/opensuse-security-announce/2016-01/msg00035.html
- http://lists.opensuse.org/opensuse-security-announce/2016-01/msg00036.html
- http://lists.opensuse.org/opensuse-security-announce/2016-01/msg00046.html
- http://rhn.redhat.com/errata/RHSA-2016-0072.html
- http://www.debian.org/security/2016/dsa-3456
- http://www.securityfocus.com/bid/81430
- http://www.securitytracker.com/id/1034801
- http://www.ubuntu.com/usn/USN-2877-1
- https://code.google.com/p/chromium/issues/detail?id=544765
- https://codereview.chromium.org/1455973003
- https://security.gentoo.org/glsa/201603-09