CVE-2018-6032

Description

Insufficient policy enforcement in Blink in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to potentially leak user cross-origin data via a crafted HTML page.

Category

6.5
CVSS
Severity: Medium
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.84% Top 30%
Vendor Advisory debian.org Vendor Advisory redhat.com
Affected: Google Chrome
Published at:
Updated at:

References

Link Tags
https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html
https://www.debian.org/security/2018/dsa-4103 vendor advisory
http://www.securityfocus.com/bid/102797 vdb entry
http://www.securitytracker.com/id/1040282 vdb entry
https://access.redhat.com/errata/RHSA-2018:0265 vendor advisory
https://crbug.com/787103

Frequently Asked Questions

What is the severity of CVE-2018-6032?
CVE-2018-6032 has been scored as a medium severity vulnerability.
How to fix CVE-2018-6032?
To fix CVE-2018-6032, 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-6032 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2018-6032 is being actively exploited. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2018-6032?
CVE-2018-6032 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.