CVE-2020-15960: Out of bounds read in storage
Published Jun 28, 2020
·Updated
Heap buffer overflow in storage in Google Chrome prior to 85.0.4183.121 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page.
Credit
Anonymous
Affected Software
11 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
Google Chrome<85.0.4183.121
85.0.4183.121
Google Chrome<85.0.4183.121
openSUSE Backports SLE=15.0-sp1
openSUSE Backports SLE=15.0-sp2
openSUSE Leap=15.1
openSUSE Leap=15.2
Fedoraproject Fedora=31
Fedoraproject Fedora=32
Fedoraproject Fedora=33
Debian Debian Linux=10.0
Remediation
Patch Available
Event History
Jun 28, 2020
CVE Published
12:00 AM
Sep 21, 2020
CVE Published
via MITRE·07:06 PM
Data Sourced
via MITRE·07:06 PM
DescriptionWeakness
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
1
What is the severity of CVE-2020-15960?
CVE-2020-15960 has a high severity rating due to the potential for remote exploitation via crafted HTML.
2
How do I fix CVE-2020-15960?
To fix CVE-2020-15960, update your Chrome or Chromium version to at least 85.0.4183.121.
3
Which software is affected by CVE-2020-15960?
CVE-2020-15960 affects Google Chrome versions prior to 85.0.4183.121 and various versions of Chromium.
4
What type of vulnerability is CVE-2020-15960?
CVE-2020-15960 is a heap buffer overflow vulnerability.
5
Can CVE-2020-15960 lead to system compromise?
Yes, CVE-2020-15960 could allow an attacker to perform out of bounds memory access, potentially leading to system compromise.