CVE-2017-5071 Memory corruption in Google Chrome prior to 59.0.3071.86 for Linux, Windows and Mac, and 59.0.3071.92 for Android

Medium 6.3 Published Updated

Remote attackers can read out-of-bounds memory in Chrome via crafted HTML pages due to insufficient input validation in V8.

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-2017-5071?

CVE-2017-5071 is a medium-severity memory corruption vulnerability in Google Chrome, published on 27 Oct 2017. 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

Insufficient validation of untrusted input in V8 in Google Chrome prior to 59.0.3071.86 for Linux, Windows and Mac, and 59.0.3071.92 for Android allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page.

Weakness: CWE-20

Which versions are affected by CVE-2017-5071?

It affects 4 products.

Products include Google Chrome, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Workstation.

How do I fix CVE-2017-5071?

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-2017-5071 being exploited?

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

All Google Chrome vulnerabilities

Sources

Also known as GHSA-wwmg-4r3v-8382, UBUNTU-CVE-2017-5071.

Is CVE-2017-5071 in your software?

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

Check your SBOMs for free