First published: Wed Jan 24 2018(Updated: )
A local file write flaw was found in the DevTools component of the Chromium browser. Upstream bug(s): <a href="https://code.google.com/p/chromium/issues/detail?id=805445">https://code.google.com/p/chromium/issues/detail?id=805445</a> External References: <a href="https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html">https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html</a>
Credit: Rob Wu cve-coordination@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/chromium-browser | <68.0.3440.75 | 68.0.3440.75 |
Google Chrome | <66.0.3359.106 | |
Redhat Enterprise Linux Desktop | =6.0 | |
Redhat Enterprise Linux Server | =6.0 | |
Redhat Enterprise Linux Workstation | =6.0 | |
Debian Debian Linux | =9.0 | |
debian/chromium-browser | ||
Google Chrome | <68.0.3440.75 | 68.0.3440.75 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Found alongside the following vulnerabilities)
The severity of CVE-2018-6152 is critical with a CVSS score of 9.6.
An attacker can exploit CVE-2018-6152 by convincing a user to install a malicious extension and perform a sandbox escape via a crafted HTML file.
The affected software versions include Google Chrome prior to 66.0.3359.117 and Redhat Enterprise Linux Desktop, Server, and Workstation 6.0.
Yes, the fix for CVE-2018-6152 is available in Google Chrome version 68.0.3440.75.
You can find more information about CVE-2018-6152 on the Debian Security Tracker, Chromium Issue Tracker, and Google Chrome Releases Blog.