First published: Wed Mar 07 2018(Updated: )
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.
Credit: cve-coordination@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
debian/chromium-browser | ||
redhat/chromium-browser | <65.0.3325.146 | 65.0.3325.146 |
Google Chrome (Trace Event) | <65.0.3325.146 | |
Red Hat Enterprise Linux Desktop | =6.0 | |
Red Hat Enterprise Linux Server | =6.0 | |
Red Hat Enterprise Linux Workstation | =6.0 | |
Debian | =9.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2018-6063 is critical due to the potential for a remote attacker to exploit the vulnerability for arbitrary code execution.
To fix CVE-2018-6063, update Google Chrome or the affected Chromium browser to version 65.0.3325.146 or later.
CVE-2018-6063 affects Chromium versions prior to 65.0.3325.146.
Yes, CVE-2018-6063 could potentially allow an attacker to conduct out of bounds memory writes, leading to data breaches.
Users of the affected versions of Google Chrome and Chromium, particularly those who visit malicious HTML pages, are vulnerable to CVE-2018-6063.