CVE-2020-15963: Insufficient policy enforcement in extensions
Published Aug 6, 2020
·Updated
Insufficient policy enforcement in extensions in Google Chrome prior to 85.0.4183.121 allowed an attacker who convinced a user to install a malicious extension to potentially perform a sandbox escape via a crafted Chrome Extension.
Credit
David Erceg
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 6, 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-15963?
CVE-2020-15963 is rated as high severity due to its potential for sandbox escape via malicious Chrome extensions.
2
How do I fix CVE-2020-15963?
To fix CVE-2020-15963, update Google Chrome to version 85.0.4183.121 or later.
3
What versions of Chrome are affected by CVE-2020-15963?
CVE-2020-15963 affects Google Chrome versions prior to 85.0.4183.121.
4
Can CVE-2020-15963 affect Chromium browsers as well?
Yes, CVE-2020-15963 can affect Chromium browsers that are based on versions prior to 85.0.4183.121.
5
What is the attack vector for CVE-2020-15963?
CVE-2020-15963 can be exploited through the installation of a malicious Chrome extension by a user.