CVE-2020-6399: Input Validation
First published: Mon Feb 10 2020(Updated: )
An insufficient policy enforcement flaw was found in the AppCache component of the Chromium browser. Upstream bug(s): <a href="https://code.google.com/p/chromium/issues/detail?id=1039869">https://code.google.com/p/chromium/issues/detail?id=1039869</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 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://security-tracker.debian.org/tracker/CVE-2020-6399
- http://lists.opensuse.org/opensuse-security-announce/2020-02/msg00015.html
- http://lists.opensuse.org/opensuse-security-announce/2020-02/msg00025.html
- https://access.redhat.com/errata/RHSA-2020:0514
- https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop.html
- https://crbug.com/1039869
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6IOHSO6BUKC6I66J5PZOMAGFVJ66ZS57/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/X3B5RWJQD5LA45MYLLR55KZJOJ5NVZGP/
- https://security.gentoo.org/glsa/202003-08
- https://www.debian.org/security/2020/dsa-4638
- https://code.google.com/p/chromium/issues/detail?id=1039869
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1801839
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1801838
- https://access.redhat.com/security/cve/cve-2020-6399
- https://bugzilla.redhat.com/show_bug.cgi?id=1801175
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/X3B5RWJQD5LA45MYLLR55KZJOJ5NVZGP/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6IOHSO6BUKC6I66J5PZOMAGFVJ66ZS57/
Frequently Asked Questions
What is the severity of CVE-2020-6399?
CVE-2020-6399 is classified as a high severity vulnerability due to its potential impact on browser security.
How do I fix CVE-2020-6399?
To fix CVE-2020-6399, update your Chromium browser or the affected package to the latest versions as recommended by your distribution.
Which versions of Chromium are affected by CVE-2020-6399?
CVE-2020-6399 affects multiple versions of Chromium, including versions prior to 90.0.4430.212 and earlier versions such as 80.0.3987.87.
What component of the Chromium browser does CVE-2020-6399 affect?
CVE-2020-6399 affects the AppCache component of the Chromium browser.
Is CVE-2020-6399 specific to a certain operating system?
CVE-2020-6399 is not specific to an operating system and can impact Chromium browsers across various platforms.
- collector/security-tracker-debian
- agent/type
- agent/softwarecombine
- agent/first-publish-date
- agent/author
- agent/severity
- agent/weakness
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2020-6399
- agent/software-canonical-lookup
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/references
- agent/description
- agent/event
- agent/trending
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- package-manager/debian
- package-manager/redhat
- vendor/google
- canonical/google chrome
- vendor/opensuse
- canonical/opensuse backports
- version/opensuse backports/15.0-sp1