CVE-2018-6152: Local file write in DevTools

Published Jan 24, 2018
·
Updated

A local file write flaw was found in the DevTools component of the Chromium browser.

Upstream bug(s):

https://code.google.com/p/chromium/issues/detail?id=805445

External References:

https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html

Other sources

The implementation of the Page.downloadBehavior backend unconditionally marked downloaded files as safe, regardless of file type in Google Chrome prior to 66.0.3359.117 allowed an attacker who convinced a user to install a malicious extension to potentially perform a sandbox escape via a crafted HTML page and user interaction.

Credit

Rob Wu

Affected Software

8 affected componentsFixes available
debian/chromium-browser
redhat/chromium-browser<68.0.3440.75
68.0.3440.75
Google Chrome<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

Event History

Jan 24, 2018
CVE Published
12:00 AM
Dec 4, 2018
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
DescriptionWeakness

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2018-6152?

The severity of CVE-2018-6152 is critical with a CVSS score of 9.6.

2

How can an attacker exploit CVE-2018-6152?

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.

3

Which software versions are affected by CVE-2018-6152?

The affected software versions include Google Chrome prior to 66.0.3359.117 and Redhat Enterprise Linux Desktop, Server, and Workstation 6.0.

4

Is there a fix available for CVE-2018-6152?

Yes, the fix for CVE-2018-6152 is available in Google Chrome version 68.0.3440.75.

5

Where can I find more information about CVE-2018-6152?

You can find more information about CVE-2018-6152 on the Debian Security Tracker, Chromium Issue Tracker, and Google Chrome Releases Blog.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203