CVE-2020-6482
published 2020-05-21CVE-2020-6482: 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…
PriorityP429medium6.5CVSS 3.1
AVNACLPRNUIRSUCNIHAN
EPSS
1.34%
68.4th percentile
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
14 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| chromium | chromium | >= 0 < 83.0.4103.83-1 | 83.0.4103.83-1 |
| chromium | chromium | >= 0 < 83.0.4103.83-1 | 83.0.4103.83-1 |
| chromium | chromium | >= 0 < 83.0.4103.83-1 | 83.0.4103.83-1 |
| chromium | chromium | >= 0 < 83.0.4103.83-1 | 83.0.4103.83-1 |
| debian | chromium | < chromium 83.0.4103.83-1 (bookworm) | chromium 83.0.4103.83-1 (bookworm) |
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| fedoraproject | fedora | — | — |
| fedoraproject | fedora | — | — |
| chrome | < 83.0.4103.61 | 83.0.4103.61 | |
| chrome | >= unspecified < 83.0.4103.61 | 83.0.4103.61 | |
| chrome_chrome | — | — | |
| opensuse | backports_sle | — | — |
| opensuse | leap | — | — |
CVSS provenance
nvdv3.16.5MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:N/I:P/A:N
osv6.5MEDIUM
vendor_debian6.5MEDIUM
vendor_redhat6.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
chromium-browser: Insufficient policy enforcement in developer tools
vendor_redhat·2020-05-19·CVSS 6.5
CVE-2020-6482 [MEDIUM] chromium-browser: Insufficient policy enforcement in developer tools
chromium-browser: Insufficient policy enforcement in developer tools
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.
Chrome
Stable Channel Update for Desktop: CVE-2020-6482
vendor_chrome·2020-05-19·CVSS 6.5
CVE-2020-6482 [MEDIUM] Stable Channel Update for Desktop: CVE-2020-6482
Stable Channel Update for Desktop
CVE-2020-6482: Insufficient policy enforcement in developer tools. Reported by Abdulrahman Alqabandi (@qab) on 2017-12-17
[$TBD][ 966507 ] Medium CVE-2020-6483: Insufficient policy enforcement in payments
Reported by Jun Kokatsu, Microsoft Browser Vulnerability Research on 2019-05-23
Severity: medium
Debian
CVE-2020-6482: chromium - Insufficient policy enforcement in developer tools in Google Chrome prior to 83....
vendor_debian·2020·CVSS 6.5
CVE-2020-6482 [MEDIUM] CVE-2020-6482: chromium - Insufficient policy enforcement in developer tools in Google Chrome prior to 83....
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.
Scope: local
bookworm: resolved (fixed in 83.0.4103.83-1)
bullseye: resolved (fixed in 83.0.4103.83-1)
forky: resolved (fixed in 83.0.4103.83-1)
sid: resolved (fixed in 83.0.4103.83-1)
trixie: resolved (fixed in 83.0.4103.83-1)
GHSA
GHSA-w96j-c32h-cgq7: Insufficient policy enforcement in developer tools in Google Chrome prior to 83
ghsa_unreviewed·2022-05-24
CVE-2020-6482 [MEDIUM] CWE-276 GHSA-w96j-c32h-cgq7: Insufficient policy enforcement in developer tools in Google Chrome prior to 83
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.
OSV
CVE-2020-6482: Insufficient policy enforcement in developer tools in Google Chrome prior to 83
osv·2020-05-21·CVSS 6.5
CVE-2020-6482 [MEDIUM] CVE-2020-6482: Insufficient policy enforcement in developer tools in Google Chrome prior to 83
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.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2020-6465 CVE-2020-6466 CVE-2020-6467 CVE-2020-6468 CVE-2020-6470 CVE-2020-6471 CVE-2020-6472 CVE-2020-6473 CVE-2020-6474 CVE-2020-6475 CVE-2020-6477 CVE-2020-6478 CVE-2020-6480 CVE-2020-6481 CVE-
bugzilla·2020-05-20·CVSS 9.6
CVE-2020-6465 [CRITICAL] CVE-2020-6465 CVE-2020-6466 CVE-2020-6467 CVE-2020-6468 CVE-2020-6470 CVE-2020-6471 CVE-2020-6472 CVE-2020-6473 CVE-2020-6474 CVE-2020-6475 CVE-2020-6477 CVE-2020-6478 CVE-2020-6480 CVE-2020-6481 CVE-
CVE-2020-6465 CVE-2020-6466 CVE-2020-6467 CVE-2020-6468 CVE-2020-6470 CVE-2020-6471 CVE-2020-6472 CVE-2020-6473 CVE-2020-6474 CVE-2020-6475 CVE-2020-6477 CVE-2020-6478 CVE-2020-6480 CVE-2020-6481 CVE-2020-6482 ... chromium: various flaws [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the releva
Bugzilla
CVE-2020-6465 CVE-2020-6466 CVE-2020-6467 CVE-2020-6468 CVE-2020-6470 CVE-2020-6471 CVE-2020-6472 CVE-2020-6473 CVE-2020-6474 CVE-2020-6475 CVE-2020-6477 CVE-2020-6478 CVE-2020-6480 CVE-2020-6481 CVE-
bugzilla·2020-05-20·CVSS 9.6
CVE-2020-6465 [CRITICAL] CVE-2020-6465 CVE-2020-6466 CVE-2020-6467 CVE-2020-6468 CVE-2020-6470 CVE-2020-6471 CVE-2020-6472 CVE-2020-6473 CVE-2020-6474 CVE-2020-6475 CVE-2020-6477 CVE-2020-6478 CVE-2020-6480 CVE-2020-6481 CVE-
CVE-2020-6465 CVE-2020-6466 CVE-2020-6467 CVE-2020-6468 CVE-2020-6470 CVE-2020-6471 CVE-2020-6472 CVE-2020-6473 CVE-2020-6474 CVE-2020-6475 CVE-2020-6477 CVE-2020-6478 CVE-2020-6480 CVE-2020-6481 CVE-2020-6482 ... chromium: various flaws [epel-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant t
Bugzilla
CVE-2020-6482 chromium-browser: Insufficient policy enforcement in developer tools
bugzilla·2020-05-20·CVSS 6.5
CVE-2020-6482 [MEDIUM] CVE-2020-6482 chromium-browser: Insufficient policy enforcement in developer tools
CVE-2020-6482 chromium-browser: Insufficient policy enforcement in developer tools
An insufficient policy enforcement flaw was found in the developer tools component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=795595
External References:
https://chromereleases.googleblog.com/2020/05/stable-channel-update-for-desktop_19.html
Discussion:
Created chromium tracking bugs for this issue:
Affects: epel-all [bug 1837905]
Affects: fedora-all [bug 1837904]
---
This issue has been addressed in the following products:
Red Hat Enterprise Linux 6 Supplementary
Via RHSA-2020:2544 https://access.redhat.com/errata/RHSA-2020:2544
---
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):
https://a
http://lists.opensuse.org/opensuse-security-announce/2020-06/msg00034.htmlhttp://lists.opensuse.org/opensuse-security-announce/2020-06/msg00038.htmlhttps://chromereleases.googleblog.com/2020/05/stable-channel-update-for-desktop_19.htmlhttps://crbug.com/795595https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OQYH5OK7O4BU6E37WWG5SEEHV65BFSGR/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WLFZ5N4EK6I4ZJP5YSKLLVN3ELXEB4XT/https://security.gentoo.org/glsa/202006-02https://security.gentoo.org/glsa/202101-30https://www.debian.org/security/2020/dsa-4714http://lists.opensuse.org/opensuse-security-announce/2020-06/msg00034.htmlhttp://lists.opensuse.org/opensuse-security-announce/2020-06/msg00038.htmlhttps://chromereleases.googleblog.com/2020/05/stable-channel-update-for-desktop_19.htmlhttps://crbug.com/795595https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OQYH5OK7O4BU6E37WWG5SEEHV65BFSGR/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WLFZ5N4EK6I4ZJP5YSKLLVN3ELXEB4XT/https://security.gentoo.org/glsa/202006-02https://security.gentoo.org/glsa/202101-30https://www.debian.org/security/2020/dsa-4714
2020-05-21
Published