CVE-2018-6033: Input Validation
Insufficient data validation in Downloads in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to potentially run arbitrary code outside sandbox via a crafted Chrome Extension.
Other sources
The following flaw was identified in the Chromium browser: race when opening downloaded files.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=793620
External References:
https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop24.html
— Red Hat
Credit
Affected Software
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2018-6031
- CVE-2018-6032
- 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-6046
- 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-6033?
CVE-2018-6033 has a high severity rating due to the potential for arbitrary code execution.
How do I fix CVE-2018-6033?
To fix CVE-2018-6033, users should upgrade to Google Chrome version 64.0.3282.119 or later.
Which versions of Google Chrome are affected by CVE-2018-6033?
CVE-2018-6033 affects all versions of Google Chrome prior to 64.0.3282.119.
Can CVE-2018-6033 be exploited remotely?
Yes, CVE-2018-6033 can be exploited remotely through a crafted Chrome Extension.
What types of systems are affected by CVE-2018-6033?
CVE-2018-6033 affects systems running affected versions of Google Chrome on various operating systems, including Windows and Linux.