CVE-2016-1660 Memory corruption in n/a

High 8.8 Published Updated

Remote attackers can cause denial of service or potential code execution via crafted websites due to mishandled assertions in Blink.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2016-1660?

CVE-2016-1660 is a high-severity memory corruption vulnerability in Google Chrome, published on 14 May 2016. An attacker can exploit it over the internet without logging in, 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, mishandles assertions in the WTF::BitArray and WTF::double_conversion::Vector classes, which allows remote attackers to cause a denial of service (out-of-bounds write) or possibly have unspecified other impact via a crafted web site.

Weakness: CWE-20

Which versions are affected by CVE-2016-1660?

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-1660?

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-1660 being exploited?

There is no known exploitation of CVE-2016-1660 in the wild and no public exploit code.

All Google Chrome vulnerabilities

Sources

Also known as GHSA-vgv8-6pg5-qxmf, UBUNTU-CVE-2016-1660.

Is CVE-2016-1660 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free