CVE-2020-6417: High severity Google Chrome vulnerability
An inappropriate implementation flaw was found in the installer component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=1033824
External References:
https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop.html
Other sources
Inappropriate implementation in installer in Google Chrome prior to 80.0.3987.87 allowed a local attacker to execute arbitrary code via a crafted registry entry.
— MITRE
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 80.0.3987.87 - Upgrade
Upgrade
chromium/google chrome installerto a version that resolves this vulnerability.Fixed in 80.0.3987.87
Event History
Frequently Asked Questions
What is the severity of CVE-2020-6417?
CVE-2020-6417 is classified as a medium severity vulnerability due to the potential for arbitrary code execution by local attackers.
How do I fix CVE-2020-6417?
To remedy CVE-2020-6417, users should update Google Chrome to version 80.0.3987.87 or later.
Who is affected by CVE-2020-6417?
CVE-2020-6417 affects users of Google Chrome versions earlier than 80.0.3987.87.
What type of attack does CVE-2020-6417 enable?
CVE-2020-6417 enables local attackers to execute arbitrary code via a crafted registry entry.
When was CVE-2020-6417 disclosed?
CVE-2020-6417 was disclosed in February 2020.