CVE-2020-6386: Use After Free
An use after free flaw was found in the speech component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=1043603
External References:
https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop18.html
Other sources
Use after free in speech in Google Chrome prior to 80.0.3987.116 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/chromium-browserto a version that resolves this vulnerability.Fixed in 0:80.0.3987.122-1.el6_10 - Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 90.0.4430.212-1~deb10u1Fixed in 116.0.5845.180-1~deb11u1Fixed in 120.0.6099.129-1~deb11u1Fixed in 119.0.6045.199-1~deb12u1Fixed in 120.0.6099.129-1~deb12u1Fixed in 120.0.6099.129-1 - Upgrade
Upgrade
redhat/chromium-browserto a version that resolves this vulnerability.Fixed in 80.0.3987.116 - Upgrade
Upgrade
chromium/browserto a version that resolves this vulnerability.Fixed in 80.0.3987.116Patch 1043603
Event History
Frequently Asked Questions
What is CVE-2020-6386?
CVE-2020-6386 is a vulnerability in Google Chrome that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.
What is the severity of CVE-2020-6386?
CVE-2020-6386 has a severity rating of 8.8 (high).
How does CVE-2020-6386 affect Google Chrome?
CVE-2020-6386 affects Google Chrome versions prior to 80.0.3987.116.
How can I fix CVE-2020-6386?
To fix CVE-2020-6386, update Google Chrome to version 80.0.3987.116 or higher.
Where can I find more information about CVE-2020-6386?
You can find more information about CVE-2020-6386 at the following references: [link 1](https://code.google.com/p/chromium/issues/detail?id=1043603), [link 2](https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop_18.html), [link 3](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1807504).