First published: Thu Aug 06 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: chrome-cve-admin@google.com David Erceg
Affected Software | Affected Version | How to fix |
---|---|---|
debian/chromium | 90.0.4430.212-1~deb10u1 116.0.5845.180-1~deb11u1 120.0.6099.129-1~deb11u1 119.0.6045.199-1~deb12u1 120.0.6099.129-1~deb12u1 120.0.6099.129-1 | |
Google Chrome (Trace Event) | <85.0.4183.121 | 85.0.4183.121 |
Google Chrome | <85.0.4183.121 | |
openSUSE Backports | =15.0-sp1 | |
openSUSE Backports | =15.0-sp2 | |
SUSE Linux | =15.1 | |
SUSE Linux | =15.2 | |
Red Hat Fedora | =31 | |
Red Hat Fedora | =32 | |
Red Hat Fedora | =33 | |
Debian Linux | =10.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Found alongside the following vulnerabilities)
CVE-2020-15963 is rated as high severity due to its potential for sandbox escape via malicious Chrome extensions.
To fix CVE-2020-15963, update Google Chrome to version 85.0.4183.121 or later.
CVE-2020-15963 affects Google Chrome versions prior to 85.0.4183.121.
Yes, CVE-2020-15963 can affect Chromium browsers that are based on versions prior to 85.0.4183.121.
CVE-2020-15963 can be exploited through the installation of a malicious Chrome extension by a user.