CVE-2020-6393
published 2020-02-11CVE-2020-6393: Insufficient policy enforcement in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
PriorityP431medium6.5CVSS 3.1
AVNACLPRNUIRSUCHINAN
EPSS
1.85%
76.8th percentile
Insufficient policy enforcement in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
Affected
16 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| chromium | chromium | >= 0 < 80.0.3987.106-1 | 80.0.3987.106-1 |
| chromium | chromium | >= 0 < 80.0.3987.106-1 | 80.0.3987.106-1 |
| chromium | chromium | >= 0 < 80.0.3987.106-1 | 80.0.3987.106-1 |
| chromium | chromium | >= 0 < 80.0.3987.106-1 | 80.0.3987.106-1 |
| debian | chromium | < chromium 80.0.3987.106-1 (bookworm) | chromium 80.0.3987.106-1 (bookworm) |
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| fedoraproject | fedora | — | — |
| fedoraproject | fedora | — | — |
| chrome | < 80.0.3987.87 | 80.0.3987.87 | |
| chrome | >= unspecified < 80.0.3987.87 | 80.0.3987.87 | |
| chrome_chrome | — | — | |
| opensuse | backports_sle | — | — |
| redhat | enterprise_linux_desktop | — | — |
| redhat | enterprise_linux_server | — | — |
| redhat | enterprise_linux_workstation | — | — |
CVSS provenance
nvdv3.16.5MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:P/I:N/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.
GHSA
GHSA-p389-vcjc-h255: Insufficient policy enforcement in Blink in Google Chrome prior to 80
ghsa_unreviewed·2022-05-24
CVE-2020-6393 [MEDIUM] CWE-20 GHSA-p389-vcjc-h255: Insufficient policy enforcement in Blink in Google Chrome prior to 80
Insufficient policy enforcement in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
OSV
CVE-2020-6393: Insufficient policy enforcement in Blink in Google Chrome prior to 80
osv·2020-02-11·CVSS 6.5
CVE-2020-6393 [MEDIUM] CVE-2020-6393: Insufficient policy enforcement in Blink in Google Chrome prior to 80
Insufficient policy enforcement in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
Chrome
Stable Channel Update for Desktop: CVE-2020-6393
vendor_chrome·2020-02-04·CVSS 6.5
CVE-2020-6393 [MEDIUM] Stable Channel Update for Desktop: CVE-2020-6393
Stable Channel Update for Desktop
CVE-2020-6393: Insufficient policy enforcement in Blink. Reported by Mark Amery on 2019-12-17
[$5000][ 999001 ] Medium CVE-2020-6499: Inappropriate implementation in AppCache
Reported by Kevin Higgs (@themalwareman) on 2019-08-29
Severity: medium
Red Hat
chromium-browser: Insufficient policy enforcement in Blink
vendor_redhat·2020-02-04·CVSS 6.5
CVE-2020-6393 [MEDIUM] chromium-browser: Insufficient policy enforcement in Blink
chromium-browser: Insufficient policy enforcement in Blink
Insufficient policy enforcement in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
Debian
CVE-2020-6393: chromium - Insufficient policy enforcement in Blink in Google Chrome prior to 80.0.3987.87 ...
vendor_debian·2020·CVSS 6.5
CVE-2020-6393 [MEDIUM] CVE-2020-6393: chromium - Insufficient policy enforcement in Blink in Google Chrome prior to 80.0.3987.87 ...
Insufficient policy enforcement in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
Scope: local
bookworm: resolved (fixed in 80.0.3987.106-1)
bullseye: resolved (fixed in 80.0.3987.106-1)
forky: resolved (fixed in 80.0.3987.106-1)
sid: resolved (fixed in 80.0.3987.106-1)
trixie: resolved (fixed in 80.0.3987.106-1)
No detection rules found.
No public exploits indexed.
Bugzilla
Autofill preview text can disclose sensitive information
bugzilla·2021-11-18·CVSS 6.5
[MEDIUM] Autofill preview text can disclose sensitive information
Autofill preview text can disclose sensitive information
The previewed text of autofill, shown to the user when the user hovers over an autofill entry, contains sensitive information and should not be accessible by the website until the user selects it. However, several vulnerabilities exist that can be used to steal the preview text.
1. Font side-channel attack
The font of the preview text follows the style of the field, making it possible to set the font of the preview text. The website can use a specially crafted font to infer the preview text, of which glyphs differ in size or font face.
(1) Size
Each character can have different width, and content can be inferred from size properties such as `scrollWidth.` Similar attacks have been proposed and patched in Chromium: crbug.com/916838
Bugzilla
CVE-2020-6381 CVE-2020-6382 CVE-2020-6385 CVE-2020-6387 CVE-2020-6388 CVE-2020-6389 CVE-2020-6390 CVE-2020-6391 CVE-2020-6392 CVE-2020-6393 CVE-2020-6394 CVE-2020-6395 CVE-2020-6396 CVE-2020-6397 CVE-
bugzilla·2020-02-11·CVSS 8.8
CVE-2020-6381 [HIGH] CVE-2020-6381 CVE-2020-6382 CVE-2020-6385 CVE-2020-6387 CVE-2020-6388 CVE-2020-6389 CVE-2020-6390 CVE-2020-6391 CVE-2020-6392 CVE-2020-6393 CVE-2020-6394 CVE-2020-6395 CVE-2020-6396 CVE-2020-6397 CVE-
CVE-2020-6381 CVE-2020-6382 CVE-2020-6385 CVE-2020-6387 CVE-2020-6388 CVE-2020-6389 CVE-2020-6390 CVE-2020-6391 CVE-2020-6392 CVE-2020-6393 CVE-2020-6394 CVE-2020-6395 CVE-2020-6396 CVE-2020-6397 CVE-2020-6398 ... chromium: various flaws [epel-7]
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-7.
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 top-l
Bugzilla
CVE-2020-6381 CVE-2020-6382 CVE-2020-6385 CVE-2020-6387 CVE-2020-6388 CVE-2020-6389 CVE-2020-6390 CVE-2020-6391 CVE-2020-6392 CVE-2020-6393 CVE-2020-6394 CVE-2020-6395 CVE-2020-6396 CVE-2020-6397 CVE-
bugzilla·2020-02-11·CVSS 8.8
CVE-2020-6381 [HIGH] CVE-2020-6381 CVE-2020-6382 CVE-2020-6385 CVE-2020-6387 CVE-2020-6388 CVE-2020-6389 CVE-2020-6390 CVE-2020-6391 CVE-2020-6392 CVE-2020-6393 CVE-2020-6394 CVE-2020-6395 CVE-2020-6396 CVE-2020-6397 CVE-
CVE-2020-6381 CVE-2020-6382 CVE-2020-6385 CVE-2020-6387 CVE-2020-6388 CVE-2020-6389 CVE-2020-6390 CVE-2020-6391 CVE-2020-6392 CVE-2020-6393 CVE-2020-6394 CVE-2020-6395 CVE-2020-6396 CVE-2020-6397 CVE-2020-6398 ... 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-6393 chromium-browser: Insufficient policy enforcement in Blink
bugzilla·2020-02-10·CVSS 6.5
CVE-2020-6393 [MEDIUM] CVE-2020-6393 chromium-browser: Insufficient policy enforcement in Blink
CVE-2020-6393 chromium-browser: Insufficient policy enforcement in Blink
An insufficient policy enforcement flaw was found in the Blink component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=1035058
External References:
https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop.html
Discussion:
Created chromium tracking bugs for this issue:
Affects: epel-7 [bug 1801839]
Affects: fedora-all [bug 1801838]
---
This issue has been addressed in the following products:
Red Hat Enterprise Linux 6 Supplementary
Via RHSA-2020:0514 https://access.redhat.com/errata/RHSA-2020:0514
---
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):
https://access.redhat.com/securit
http://lists.opensuse.org/opensuse-security-announce/2020-02/msg00015.htmlhttp://lists.opensuse.org/opensuse-security-announce/2020-02/msg00025.htmlhttps://access.redhat.com/errata/RHSA-2020:0514https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop.htmlhttps://crbug.com/1035058https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6IOHSO6BUKC6I66J5PZOMAGFVJ66ZS57/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/X3B5RWJQD5LA45MYLLR55KZJOJ5NVZGP/https://security.gentoo.org/glsa/202003-08https://www.debian.org/security/2020/dsa-4638http://lists.opensuse.org/opensuse-security-announce/2020-02/msg00015.htmlhttp://lists.opensuse.org/opensuse-security-announce/2020-02/msg00025.htmlhttps://access.redhat.com/errata/RHSA-2020:0514https://chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop.htmlhttps://crbug.com/1035058https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6IOHSO6BUKC6I66J5PZOMAGFVJ66ZS57/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/X3B5RWJQD5LA45MYLLR55KZJOJ5NVZGP/https://security.gentoo.org/glsa/202003-08https://www.debian.org/security/2020/dsa-4638
2020-02-11
Published