CVE-2018-6168: CORS bypass in Blink
First published: Tue Apr 03 2018(Updated: )
A cors bypass flaw was found in the Blink component of the Chromium browser. Upstream bug(s): <a href="https://code.google.com/p/chromium/issues/detail?id=828265">https://code.google.com/p/chromium/issues/detail?id=828265</a> External References: <a href="https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html">https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html</a>
Credit: Gunes Acar Princeton UniversityDanny Y. Huang Princeton UniversityFrank Li UC Berkeley cve-coordination@google.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/chromium-browser | <68.0.3440.75 | 68.0.3440.75 |
| debian/chromium-browser | ||
| Google Chrome | <68.0.3440.75 | |
| Google Chrome | <68.0.3440.75 | 68.0.3440.75 |
Remedy
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html (Advisory)
- https://crbug.com/828265
- https://code.google.com/p/chromium/issues/detail?id=828265
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1608211
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1608210
- https://access.redhat.com/errata/RHSA-2018:2282
- https://bugzilla.redhat.com/show_bug.cgi?id=1608192
- https://security-tracker.debian.org/tracker/CVE-2018-6168
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.
- collector/security-tracker-debian
- agent/type
- agent/last-modified-date
- agent/softwarecombine
- agent/first-publish-date
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/title
- agent/remedy
- agent/severity
- agent/references
- agent/weakness
- agent/author
- agent/description
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2018-6168
- agent/software-canonical-lookup
- collector/chrome-releases
- agent/tags
- agent/event
- collector/mitre-cve
- source/MITRE
- package-manager/debian
- vendor/google
- canonical/google chrome
- package-manager/redhat