CVE-2018-6161: Same orig in policy bypass in WebAudio
A same origin policy bypass flaw was found in the WebAudio component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=826552
External References:
https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html
Other sources
Insufficient policy enforcement in Blink in Google Chrome prior to 68.0.3440.75 allowed a remote attacker to bypass same origin policy via a crafted HTML page.
Credit
Affected Software
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-6162
- CVE-2018-6163
- CVE-2018-6164
- CVE-2018-6165
- CVE-2018-6166
- CVE-2018-6167
- CVE-2018-6168
- 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-6161?
CVE-2018-6161 is a vulnerability in Google Chrome that allows a remote attacker to bypass the same origin policy.
What is the severity of CVE-2018-6161?
CVE-2018-6161 has a severity rating of 8.8, which is considered high.
How does CVE-2018-6161 affect Google Chrome?
CVE-2018-6161 affects Google Chrome versions up to 68.0.3440.75.
How can I fix CVE-2018-6161 in Google Chrome?
To fix CVE-2018-6161, you need to update Google Chrome to version 68.0.3440.75 or later.
Where can I find more information about CVE-2018-6161?
You can find more information about CVE-2018-6161 at the following references: [1] https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html [2] https://crbug.com/826552 [3] https://security-tracker.debian.org/tracker/CVE-2018-6161