CVE-2020-6389: High severity Google Chrome vulnerability
An out of bounds write flaw was found in the WebRTC component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=1042933
External References:
https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop.html
Other sources
Out of bounds write in WebRTC in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to potentially exploit heap corruption via a crafted video stream.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- 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.87 - Upgrade
Upgrade
chromium/WebRTC (Google Chrome)to a version that resolves this vulnerability.Fixed in 80.0.3987.87 - Compensating control
If WebRTC is not required for your use case, disable or restrict WebRTC functionality at the application/browser policy level to reduce exposure to crafted video streams.
Event History
Frequently Asked Questions
What is the severity of CVE-2020-6389?
CVE-2020-6389 is classified as a high severity vulnerability due to its potential to allow an out of bounds write in the WebRTC component.
How do I fix CVE-2020-6389?
To fix CVE-2020-6389, update to the latest version of Chromium browser or Google Chrome, specifically versions later than 80.0.3987.87.
What systems are affected by CVE-2020-6389?
CVE-2020-6389 affects Google Chrome and Chromium versions prior to 80.0.3987.87.
What are the potential impacts of CVE-2020-6389?
The potential impact of CVE-2020-6389 includes exploitation that can lead to data corruption or a possible breach of user privacy.
What is the nature of the vulnerability in CVE-2020-6389?
CVE-2020-6389 is an out of bounds write vulnerability, which means it allows writing data outside the intended memory buffer.