CVE-2017-5053 Memory corruption in Google Chrome prior to 57.0.2987.133 for Linux, Windows and Mac, and 57.0.2987.132 for Android

Critical 9.6 Published Updated

A remote attacker can execute arbitrary code inside the sandbox via a crafted HTML page exploiting an out-of-bounds read 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-5053?

CVE-2017-5053 is a critical 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

An out-of-bounds read in V8 in Google Chrome prior to 57.0.2987.133 for Linux, Windows, and Mac, and 57.0.2987.132 for Android, allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page, related to Array.prototype.indexOf.

Weakness: CWE-125

Which versions are affected by CVE-2017-5053?

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

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

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

All Google Chrome vulnerabilities

Sources

Also known as GHSA-g4p8-ffff-6w4m, UBUNTU-CVE-2017-5053.

Is CVE-2017-5053 in your software?

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

Check your SBOMs for free