CVE-2018-6117: Infoleak
Confusing settings in Autofill in Google Chrome prior to 66.0.3359.117 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page.
Other sources
The following flaw was identified in the Chromium browser: Confusing autofill settings.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=822465
External References:
https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html
— Red Hat
Credit
Affected Software
Remediation
Patch Available
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-6101
- 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-6084
Frequently Asked Questions
What is the severity of CVE-2018-6117?
CVE-2018-6117 is classified as a high severity vulnerability due to its potential to expose sensitive information.
How do I fix CVE-2018-6117?
To fix CVE-2018-6117, update Google Chrome or Chromium to version 66.0.3359.117 or later.
What type of vulnerability is CVE-2018-6117?
CVE-2018-6117 is a vulnerability related to confusing autofill settings that allows remote attackers to read process memory.
Which versions of Chrome are affected by CVE-2018-6117?
CVE-2018-6117 affects Google Chrome versions prior to 66.0.3359.117.
Can CVE-2018-6117 be exploited remotely?
Yes, CVE-2018-6117 can be exploited remotely via a crafted HTML page to access sensitive information.