First published: Wed Mar 07 2018(Updated: )
Lack of special casing of Android ashmem in Google Chrome prior to 65.0.3325.146 allowed a remote attacker who had compromised the renderer process to bypass inter-process read only guarantees 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.
CVE-2018-6057 has been classified with a high severity due to its potential to allow remote attackers to bypass inter-process read only guarantees.
To fix CVE-2018-6057, update Google Chrome or Chromium to version 65.0.3325.146 or later.
CVE-2018-6057 affects Google Chrome versions prior to 65.0.3325.146.
CVE-2018-6057 impacts various environments including Debian GNU/Linux 9.0 and Red Hat Enterprise Linux 6.0.
In CVE-2018-6057, the attacker is a remote individual who can compromise the renderer process through a crafted HTML page.