CVE-2018-6046: Input Validation
Insufficient data validation in DevTools in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to potentially leak user cross-origin data via a crafted Chrome Extension.
Other sources
The following flaw was identified in the Chromium browser: insufficient isolation of devtools from extensions.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=798163
External References:
https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop24.html
— Red Hat
Credit
Affected Software
Remediation
Patch Available
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2018-6031
- CVE-2018-6032
- 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-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-6046?
CVE-2018-6046 has been classified as a high severity vulnerability due to the potential for a remote attacker to leak user cross-origin data.
How do I fix CVE-2018-6046?
To mitigate CVE-2018-6046, users should update Google Chrome to version 64.0.3282.119 or later.
What versions of Google Chrome are affected by CVE-2018-6046?
CVE-2018-6046 affects Google Chrome versions prior to 64.0.3282.119.
Can CVE-2018-6046 be exploited through a Chrome Extension?
Yes, CVE-2018-6046 can be exploited by a remote attacker using a crafted Chrome Extension.
What is the main cause of CVE-2018-6046?
The main cause of CVE-2018-6046 is insufficient data validation and isolation of DevTools from extensions in earlier versions of Google Chrome.