CVE-2018-6091: Medium severity google chrome (trace event) vulnerability
Service Workers can intercept any request made by an <embed> or <object> tag in Fetch API in Google Chrome prior to 66.0.3359.117 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
Other sources
The following flaw was identified in the Chromium browser: Incorrect handling of plug-ins by Service Worker.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=771933
External References:
https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html
— Red Hat
Credit
Affected Software
Remediation
Patch Available
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2018-6085
- CVE-2018-6086
- CVE-2018-6087
- CVE-2018-6088
- CVE-2018-6089
- CVE-2018-6090
- CVE-2018-6092
- CVE-2018-6093
- CVE-2018-6152
- CVE-2018-6094
- CVE-2018-6095
- CVE-2018-6150
- CVE-2018-6096
- CVE-2018-6097
- CVE-2018-6151
- CVE-2018-6098
- CVE-2018-6099
- CVE-2018-6100
- CVE-2018-6101
- CVE-2018-6102
- CVE-2018-6103
- CVE-2018-6104
- CVE-2018-6105
- CVE-2018-6106
- CVE-2018-6107
- CVE-2018-6108
- CVE-2018-6109
- CVE-2018-6110
- CVE-2018-6111
- CVE-2018-6112
- CVE-2018-6113
- CVE-2018-6114
- CVE-2018-6115
- CVE-2018-6116
- CVE-2018-6117
- CVE-2018-6084
Frequently Asked Questions
What is the severity of CVE-2018-6091?
CVE-2018-6091 has been classified as a medium severity vulnerability.
How do I fix CVE-2018-6091?
To fix CVE-2018-6091, upgrade your Chrome browser to version 66.0.3359.117 or later.
Which versions of Chrome are affected by CVE-2018-6091?
CVE-2018-6091 affects Chrome versions prior to 66.0.3359.117.
Is CVE-2018-6091 exploitable in all environments?
CVE-2018-6091 can potentially be exploited in any environment using affected versions of Chrome.
What kind of data can be leaked due to CVE-2018-6091?
CVE-2018-6091 may allow remote attackers to leak sensitive cross-origin data.