CVE-2018-6168: CORS bypass in Blink
A cors bypass flaw was found in the Blink component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=828265
External References:
https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html
Other sources
Information leak in media engine in Google Chrome prior to 68.0.3440.75 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page.
Credit
Affected Software
Remediation
Patch Available
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2018-6153
- CVE-2018-6154
- CVE-2018-6155
- CVE-2018-6156
- CVE-2018-6157
- CVE-2018-6158
- CVE-2018-6159
- CVE-2018-6160
- CVE-2018-6161
- CVE-2018-6162
- CVE-2018-6163
- CVE-2018-6164
- CVE-2018-6165
- CVE-2018-6166
- CVE-2018-6167
- CVE-2018-6169
- CVE-2018-6170
- CVE-2018-6171
- CVE-2018-6172
- CVE-2018-6173
- CVE-2018-6174
- CVE-2018-6175
- CVE-2018-6176
- CVE-2018-6177
- CVE-2018-6178
- CVE-2018-6179
- CVE-2018-6044
- CVE-2018-4117
- CVE-2018-17460
- CVE-2018-17461
- CVE-2018-6150
- CVE-2018-6151
- CVE-2018-6152
Frequently Asked Questions
What is CVE-2018-6168?
CVE-2018-6168 is a vulnerability that allows a remote attacker to obtain potentially sensitive information from process memory in Google Chrome prior to version 68.0.3440.75.
How does CVE-2018-6168 work?
CVE-2018-6168 works by bypassing the Cross-Origin Resource Sharing (CORS) mechanism in the Blink engine, leading to an information leak in the media engine.
What is the severity of CVE-2018-6168?
CVE-2018-6168 has a severity of 6.5 out of 10, which is considered medium.
Which software versions are affected by CVE-2018-6168?
Google Chrome versions prior to 68.0.3440.75 are affected by CVE-2018-6168.
How can I fix CVE-2018-6168?
To fix CVE-2018-6168, update Google Chrome to version 68.0.3440.75 or later.