CVE-2018-6070

Description

Lack of CSP enforcement on WebUI pages in Bink in Google Chrome prior to 65.0.3325.146 allowed an attacker who convinced a user to install a malicious extension to bypass content security policy via a crafted Chrome Extension.

Category

6.1
CVSS
Severity: Medium
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.31%
Vendor Advisory redhat.com Vendor Advisory debian.org
Affected: Google Chrome
Published at:
Updated at:

References

Link Tags
https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html
http://www.securityfocus.com/bid/103297 vdb entry
https://access.redhat.com/errata/RHSA-2018:0484 vendor advisory
https://crbug.com/668645
https://www.debian.org/security/2018/dsa-4182 vendor advisory

Frequently Asked Questions

What is the severity of CVE-2018-6070?
CVE-2018-6070 has been scored as a medium severity vulnerability.
How to fix CVE-2018-6070?
To fix CVE-2018-6070, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2018-6070 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2018-6070 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2018-6070?
CVE-2018-6070 affects Google Chrome.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.