CVE-2018-6101: Insufficient protection of remote debugging prototol in DevTools
A lack of host validation in DevTools in Google Chrome prior to 66.0.3359.117 allowed a remote attacker to execute arbitrary code via a crafted HTML page, if the user is running a remote DevTools debugging server.
Other sources
An insufficient protection of remote debugging prototol flaw was found in the DevTools component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=813540
External References:
https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html
— Red Hat
Credit
Affected Software
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-6091
- 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-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 CVE-2018-6101?
CVE-2018-6101 is a vulnerability in Google Chrome that allows a remote attacker to execute arbitrary code.
How does CVE-2018-6101 work?
CVE-2018-6101 works by exploiting a lack of host validation in DevTools in Google Chrome.
What is the severity of CVE-2018-6101?
The severity of CVE-2018-6101 is high, with a CVSS score of 7.5.
Which versions of Google Chrome are affected by CVE-2018-6101?
Versions of Google Chrome prior to 66.0.3359.117 are affected by CVE-2018-6101.
How can I fix CVE-2018-6101?
To fix CVE-2018-6101, update Google Chrome to version 66.0.3359.117 or later.