CVE-2016-1661 Memory corruption in n/a
Remote attackers can cause denial of service or potential code execution via crafted websites due to missing renderer process checks in Chrome.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2016-1661?
CVE-2016-1661 is a high-severity memory corruption vulnerability in Google Chrome, published on 14 May 2016. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
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.
Weakness: CWE-20
Which versions are affected by CVE-2016-1661?
It affects 6 products.
Products include Google Chrome, Opensuse Opensuse, Redhat Enterprise Linux Desktop Supplementary, Redhat Enterprise Linux Server Supplementary, Redhat Enterprise Linux Server Supplementary Eus, Redhat Enterprise Linux Workstation Supplementary.
How do I fix CVE-2016-1661?
Upgrade to a fixed version.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2016-1661 being exploited?
There is no known exploitation of CVE-2016-1661 in the wild and no public exploit code.
Other vulnerabilities in Google Chrome
Sources
Also known as GHSA-9mh6-hg57-hhmw, UBUNTU-CVE-2016-1661.