First published: Sat May 14 2016(Updated: )
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.
Credit: cve-coordination@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat Enterprise Linux Desktop | =6.0 | |
Red Hat Enterprise Linux Server Supplementary | =6.0 | |
Red Hat Enterprise Linux Server Supplementary EUS | =6.7z | |
Red Hat Enterprise Linux Workstation Supplementary | =6.0 | |
Google Chrome (Trace Event) | <=50.0.2661.87 | |
SUSE Linux | =13.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-1661 has been classified as a high severity vulnerability due to its potential to cause denial of service and memory corruption.
To remediate CVE-2016-1661, update Google Chrome to version 50.0.2661.94 or later.
CVE-2016-1661 affects Google Chrome versions up to 50.0.2661.87 and specific versions of Red Hat and openSUSE.
The potential impacts of CVE-2016-1661 include memory corruption and resulting denial of service attacks.
Yes, users of older systems running affected versions of Google Chrome or specific Red Hat and openSUSE distributions should address CVE-2016-1661.