CVE-2018-6063 Memory corruption in Chrome

High 8.8 Published Updated

A remote attacker with compromised renderer access can perform out-of-bounds memory writes via crafted HTML, 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-2018-6063?

CVE-2018-6063 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 14 Nov 2018. 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

Incorrect use of mojo::WrapSharedMemoryHandle in Mojo in Google Chrome prior to 65.0.3325.146 allowed a remote attacker who had compromised the renderer process to perform an out of bounds memory write via a crafted HTML page.

Weakness: CWE-787

Which versions are affected by CVE-2018-6063?

It affects 5 products.

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

How do I fix CVE-2018-6063?

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-2018-6063 being exploited?

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

All Debian Debian Linux vulnerabilities

Sources

Also known as GHSA-783c-hx3w-69j5, UBUNTU-CVE-2018-6063.

Is CVE-2018-6063 in your software?

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

Check your SBOMs for free