CVE-2020-6482: Medium severity google chrome vulnerability
Published 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.
Affected Software
8 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<83.0.4103.61
openSUSE Backports SLE=15.0-sp1
openSUSE Leap=15.1
Fedoraproject Fedora=31
Fedoraproject Fedora=32
Debian Debian Linux=9.0
Debian Debian Linux=10.0
Event History
May 21, 2020
CVE Published
via MITRE·03:46 AM
Data Sourced
via MITRE·03:46 AM
DescriptionWeakness
Frequently Asked Questions
1
What is the severity of CVE-2020-6482?
CVE-2020-6482 is considered a medium severity vulnerability due to its impact on user data security when exploited through malicious extensions.
2
How do I fix CVE-2020-6482?
To fix CVE-2020-6482, users should update Google Chrome to version 83.0.4103.61 or later.
3
What are the potential impacts of CVE-2020-6482?
CVE-2020-6482 can allow an attacker to bypass navigation restrictions by exploiting a malicious Chrome extension.
4
Which versions of Chrome are affected by CVE-2020-6482?
CVE-2020-6482 affects all versions of Google Chrome prior to 83.0.4103.61.
5
Can CVE-2020-6482 be exploited through third-party extensions?
Yes, CVE-2020-6482 can be exploited if a user installs a malicious third-party Chrome extension.