CVE-2020-6408: Medium severity Google Chrome vulnerability

Published Feb 10, 2020
·
Updated

An insufficient policy enforcement flaw was found in the CORS component of the Chromium browser.

Upstream bug(s):

https://code.google.com/p/chromium/issues/detail?id=1026546

External References:

https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop.html

Other sources

Insufficient policy enforcement in CORS in Google Chrome prior to 80.0.3987.87 allowed a local attacker to obtain potentially sensitive information via a crafted HTML page.

Affected Software

15 affected componentsFixes available
debian/chromium
90.0.4430.212-1~deb10u1116.0.5845.180-1~deb11u1120.0.6099.129-1~deb11u1119.0.6045.199-1~deb12u1120.0.6099.129-1~deb12u1120.0.6099.129-1
redhat/chromium-browser<80.0.3987.87
80.0.3987.87
Google Chrome<80.0.3987.87
openSUSE Backports SLE=15.0-sp1
Fedoraproject Fedora=30
Fedoraproject Fedora=31
Debian Debian Linux=9.0
Debian Debian Linux=10.0
SUSE Package Hub
SUSE Linux Enterprise=12.0
redhat Enterprise Linux Desktop=6.0
redhat Enterprise Linux Server=6.0
redhat Enterprise Linux Workstation=6.0
All of the following
SUSE Package Hub
SUSE Linux Enterprise=12.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/chromium to 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
  2. Upgrade

    Upgrade redhat/chromium-browser to a version that resolves this vulnerability.

    Fixed in 80.0.3987.87
  3. Upgrade

    Upgrade chromium/google chrome to a version that resolves this vulnerability.

    Fixed in 80.0.3987.87
  4. Compensating control

    Mitigate exposure by preventing untrusted/crafted HTML pages from being loaded in the browser (e.g., restrict browsing to trusted sources) until all Chromium/Chrome installations are updated to address the CORS policy enforcement flaw.

Event History

Feb 11, 2020
CVE Published
via MITRE·02:42 PM
Data Sourced
via MITRE·02:42 PM
DescriptionWeakness
Data Sourced
via NVD·03:15 PM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the vulnerability ID for this issue?

The vulnerability ID for this issue is CVE-2020-6408.

2

What is the title of this vulnerability?

The title of this vulnerability is 'Insufficient policy enforcement in CORS in Google Chrome prior to 80.0.3987.87 allowed a local attacker to obtain potentially sensitive information via a crafted HTML page.'

3

What is the severity of CVE-2020-6408?

The severity of CVE-2020-6408 is medium with a score of 6.5.

4

What software versions are affected by this vulnerability?

Google Chrome prior to 80.0.3987.87, chromium-browser (remedy version 80.0.3987.87), chromium, and some other Linux distributions are affected by this vulnerability.

5

How can I fix CVE-2020-6408?

To fix CVE-2020-6408, update your Google Chrome browser to version 80.0.3987.87 or higher.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203