CVE-2016-1661
What it is
Blink, as used in Google Chrome before 50.0.2661.94, does not ensure that frames satisfy a check for the same renderer process in addition to a Same Origin Policy check, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via a crafted web site, related to BindingSecurity.cpp and DOMWindow.cpp.
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account, but needs a user to act. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 1.2% 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.2% in the next 30 days (EPSS).
- Severity: 8.0 HIGH (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 1.2% · EPSS, next 30 days
- Weakness
- CWE-20 · Improper input validation
- Record status
- Modified
Affected
- Redhat Enterprise Linux Desktop Supplementary 6.0
- Redhat Enterprise Linux Server Supplementary 6.0
- Redhat Enterprise Linux Server Supplementary Eus 6.7z
- Redhat Enterprise Linux Workstation Supplementary 6.0
- Google Chrome ≤ 50.0.2661.87
- Opensuse 13.1
Attack profile CVSS 3.0 · 8.0
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
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-1661.md and follow it. Check whether this project is affected by CVE-2016-1661. 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/04/stable-channel-update_28.html
- http://lists.opensuse.org/opensuse-security-announce/2016-05/msg00002.html
- http://lists.opensuse.org/opensuse-security-announce/2016-05/msg00003.html
- http://lists.opensuse.org/opensuse-security-announce/2016-05/msg00004.html
- http://lists.opensuse.org/opensuse-security-announce/2016-06/msg00048.html
- http://rhn.redhat.com/errata/RHSA-2016-0707.html
- http://www.debian.org/security/2016/dsa-3564
- http://www.securityfocus.com/bid/89106
- http://www.ubuntu.com/usn/USN-2960-1
- https://codereview.chromium.org/1887553002/
- https://crbug.com/601629
- https://security.gentoo.org/glsa/201605-02
- http://googlechromereleases.blogspot.com/2016/04/stable-channel-update_28.html
- http://lists.opensuse.org/opensuse-security-announce/2016-05/msg00002.html
- http://lists.opensuse.org/opensuse-security-announce/2016-05/msg00003.html
- http://lists.opensuse.org/opensuse-security-announce/2016-05/msg00004.html
- http://lists.opensuse.org/opensuse-security-announce/2016-06/msg00048.html
- http://rhn.redhat.com/errata/RHSA-2016-0707.html
- http://www.debian.org/security/2016/dsa-3564
- http://www.securityfocus.com/bid/89106
- http://www.ubuntu.com/usn/USN-2960-1
- https://codereview.chromium.org/1887553002/
- https://crbug.com/601629
- https://security.gentoo.org/glsa/201605-02