First published: Thu May 21 2020(Updated: )
Insufficient policy enforcement in developer tools in Google Chrome prior to 83.0.4103.61 allowed an attacker who convinced a user to install a malicious extension to bypass navigation restrictions via a crafted Chrome Extension.
Credit: chrome-cve-admin@google.com
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 | <83.0.4103.61 | |
openSUSE Backports | =15.0-sp1 | |
openSUSE | =15.1 | |
Fedora | =31 | |
Fedora | =32 | |
Debian | =9.0 | |
Debian | =10.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-6482 is considered a medium severity vulnerability due to its impact on user data security when exploited through malicious extensions.
To fix CVE-2020-6482, users should update Google Chrome to version 83.0.4103.61 or later.
CVE-2020-6482 can allow an attacker to bypass navigation restrictions by exploiting a malicious Chrome extension.
CVE-2020-6482 affects all versions of Google Chrome prior to 83.0.4103.61.
Yes, CVE-2020-6482 can be exploited if a user installs a malicious third-party Chrome extension.