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

High 8.8 Published Updated

A remote attacker can exploit memory corruption in Chrome's Blink engine via a crafted HTML page, potentially leading to code execution.

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

CVE-2017-5052 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

An incorrect assumption about block structure in Blink in Google Chrome prior to 57.0.2987.133 for Mac, Windows, and Linux, and 57.0.2987.132 for Android, allowed a remote attacker to potentially exploit memory corruption via a crafted HTML page that triggers improper casting.

Weakness: CWE-119

Which versions are affected by CVE-2017-5052?

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

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

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

All Google Chrome vulnerabilities

Sources

Also known as GHSA-r5q6-cwh6-gh94, UBUNTU-CVE-2017-5052.

Is CVE-2017-5052 in your software?

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

Check your SBOMs for free