First published: Mon Feb 10 2020(Updated: )
An insufficient policy enforcement flaw was found in the Safe Browsing component of the Chromium browser. Upstream bug(s): <a href="https://code.google.com/p/chromium/issues/detail?id=1021855">https://code.google.com/p/chromium/issues/detail?id=1021855</a> External References: <a href="https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop.html">https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop.html</a>
Credit: chrome-cve-admin@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
debian/chromium | 90.0.4430.212-1~deb10u1 116.0.5845.180-1~deb11u1 120.0.6099.129-1~deb11u1 119.0.6045.199-1~deb12u1 120.0.6099.129-1~deb12u1 120.0.6099.129-1 | |
redhat/chromium-browser | <80.0.3987.87 | 80.0.3987.87 |
Google Chrome | <80.0.3987.87 | |
openSUSE Backports | =15.0-sp1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-6414 has been classified as a high severity vulnerability due to inadequate policy enforcement in the Chromium browser's Safe Browsing component.
To fix CVE-2020-6414, users should update their Chromium or Chrome browser to the latest patched version as specified in the security advisories.
CVE-2020-6414 affects specific versions of Chromium including versions prior to 90.0.4430.212 and 80.0.3987.87 for certain distributions.
CVE-2020-6414 may still be exploitable if users have not updated to the recommended patched versions of Chromium or Chrome.
CVE-2020-6414 impacts multiple operating systems that run affected versions of the Chromium browser, including Debian, Red Hat, and openSUSE.