CVE-2020-6473: Google Chrome vulnerability
Google · Chrome
Vendor fix available · Affected: Google Chrome · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 78% of scored CVEs
Not scored yet. The CVE record carries no CVSS score.
DescriptionCVE.org
Insufficient policy enforcement in Blink in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Google · Chromebefore 83.0.4103.61
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
CoverageNo articles yet
No CyberSIXT article names CVE-2020-6473 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-203cwe.mitre.org
- Vendor advisorysecurity.gentoo.org
- Vendor advisorylists.opensuse.org
- Vendor advisorylists.opensuse.org
- Vendor advisorylists.fedoraproject.org
- Vendor advisorydebian.org
- Vendor advisorylists.fedoraproject.org
- Vendor advisorysecurity.gentoo.org
- chromereleases.googleblog.com/2020/05/stable-channel-update-for-chromereleases.googleblog.com
- crbug.com/1049510crbug.com