CVE-2020-15962: Insufficient policy enforcement in serial
Published Aug 26, 2020
·Updated
Insufficient policy validation in serial 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
Leecraso(360 Alpha Lab working with 360 BugCloud), Guang Gong(360 Alpha Lab working with 360 BugCloud)
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
Aug 26, 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-15962?
CVE-2020-15962 has been rated as high severity due to its potential for remote exploitation and memory access issues.
2
How do I fix CVE-2020-15962?
To fix CVE-2020-15962, update Google Chrome to version 85.0.4183.121 or later.
3
What versions of Google Chrome are affected by CVE-2020-15962?
CVE-2020-15962 affects Google Chrome versions prior to 85.0.4183.121.
4
Can CVE-2020-15962 be exploited remotely?
Yes, CVE-2020-15962 can be exploited remotely through a crafted HTML page.
5
Which operating systems are impacted by CVE-2020-15962?
CVE-2020-15962 impacts multiple operating systems including Debian, openSUSE, and Fedora due to the affected Chromium-based browsers.