CVE-2018-6032: Same orig in bypass in Shared Worker
A same origin bypass flaw was found in the Shared Worker component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=787103
External References:
https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop24.html
Other sources
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.
Credit
Affected Software
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2018-6031
- CVE-2018-6033
- CVE-2018-6034
- CVE-2018-6035
- CVE-2018-6036
- CVE-2018-6037
- CVE-2018-6038
- CVE-2018-6039
- CVE-2018-6040
- CVE-2018-6041
- CVE-2018-6042
- CVE-2018-6043
- CVE-2018-6045
- CVE-2018-6046
- CVE-2018-6047
- CVE-2018-6048
- CVE-2017-15420
- CVE-2018-6049
- CVE-2018-6050
- CVE-2018-6051
- CVE-2018-6052
- CVE-2018-6053
- CVE-2018-6054
Frequently Asked Questions
What is the severity of CVE-2018-6032?
CVE-2018-6032 is classified as a medium severity vulnerability affecting the Chromium browser.
How do I fix CVE-2018-6032?
To fix CVE-2018-6032, users should update their Chromium browser to version 64.0.3282.119 or later.
Which software is affected by CVE-2018-6032?
CVE-2018-6032 affects several versions of Chromium and Google Chrome, specifically versions prior to 64.0.3282.119.
What type of vulnerability is CVE-2018-6032?
CVE-2018-6032 is a same origin bypass vulnerability located in the Shared Worker component of the Chromium browser.
Can CVE-2018-6032 lead to data breaches?
Yes, CVE-2018-6032 has the potential to allow attackers to bypass same-origin policy restrictions, which could lead to data exposure.