CVE-2018-6038: Heap buffer overflow in WebGL
A heap buffer overflow flaw was found in the WebGL component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=774174
External References:
https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop24.html
Other sources
Heap buffer overflow in WebGL in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page.
Credit
Affected Software
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-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-6038?
CVE-2018-6038 has been assigned a high severity rating due to the heap buffer overflow vulnerability in the Chromium browser's WebGL component.
How do I fix CVE-2018-6038?
To fix CVE-2018-6038, update your Chromium browser or Google Chrome to version 64.0.3282.119 or later.
Which software is affected by CVE-2018-6038?
CVE-2018-6038 affects the Chromium browser and Google Chrome versions before 64.0.3282.119.
What types of attacks can exploit CVE-2018-6038?
CVE-2018-6038 can be exploited to execute arbitrary code or cause a denial of service through crafted content that triggers heap buffer overflow.
Is CVE-2018-6038 present in Debian or Red Hat distributions?
Yes, CVE-2018-6038 is present in Debian 8.0 and 9.0 as well as Red Hat Enterprise Linux 6.0.