CVE-2017-5088 Memory corruption in Google Chrome prior to 59.0.3071.104 for Mac, Windows and Linux, and 59.0.3071.117 for Android

High 8.8 Published Updated

Remote attackers can trigger out-of-bounds memory access in Chrome's V8 engine via crafted HTML, potentially leading to code execution or crashes.

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

CVE-2017-5088 is a high-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.104 for Mac, Windows, and Linux, and 59.0.3071.117 for Android, allowed a remote attacker to perform out of bounds memory access via a crafted HTML page.

Weakness: CWE-125

Which versions are affected by CVE-2017-5088?

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

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

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

All Google Chrome vulnerabilities

Sources

Also known as GHSA-r64f-38v8-w4ff, UBUNTU-CVE-2017-5088.

Is CVE-2017-5088 in your software?

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

Check your SBOMs for free