CVE-2020-6484
published 2020-05-21CVE-2020-6484: Insufficient data validation in ChromeDriver in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypass navigation restrictions via a crafted…
PriorityP431medium6.5CVSS 3.1
AVNACLPRNUIRSUCNIHAN
EPSS
1.49%
71.2th percentile
Insufficient data validation in ChromeDriver in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypass navigation restrictions via a crafted request.
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.
GHSA
GHSA-7443-chw4-pmw5: Insufficient data validation in ChromeDriver in Google Chrome prior to 83
ghsa_unreviewed·2022-05-24
CVE-2020-6484 [MEDIUM] CWE-276 GHSA-7443-chw4-pmw5: Insufficient data validation in ChromeDriver in Google Chrome prior to 83
Insufficient data validation in ChromeDriver in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypass navigation restrictions via a crafted request.
OSV
CVE-2020-6484: Insufficient data validation in ChromeDriver in Google Chrome prior to 83
osv·2020-05-21·CVSS 6.5
CVE-2020-6484 [MEDIUM] CVE-2020-6484: Insufficient data validation in ChromeDriver in Google Chrome prior to 83
Insufficient data validation in ChromeDriver in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypass navigation restrictions via a crafted request.
Red Hat
chromium-browser: Insufficient data validation in ChromeDriver
vendor_redhat·2020-05-19·CVSS 6.5
CVE-2020-6484 [MEDIUM] chromium-browser: Insufficient data validation in ChromeDriver
chromium-browser: Insufficient data validation in ChromeDriver
Insufficient data validation in ChromeDriver in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypass navigation restrictions via a crafted request.
Chrome
Stable Channel Update for Desktop: CVE-2020-6484
vendor_chrome·2020-05-19·CVSS 6.5
CVE-2020-6484 [MEDIUM] Stable Channel Update for Desktop: CVE-2020-6484
Stable Channel Update for Desktop
CVE-2020-6484: Insufficient data validation in ChromeDriver. Reported by Artem Zinenko on 2020-01-26
[$N/A][ 1047285 ] Medium CVE-2020-6485: Insufficient data validation in media router
Reported by Sergei Glazunov of Google Project Zero on 2020-01-30
Severity: medium
Debian
CVE-2020-6484: chromium - Insufficient data validation in ChromeDriver in Google Chrome prior to 83.0.4103...
vendor_debian·2020·CVSS 6.5
CVE-2020-6484 [MEDIUM] CVE-2020-6484: chromium - Insufficient data validation in ChromeDriver in Google Chrome prior to 83.0.4103...
Insufficient data validation in ChromeDriver in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypass navigation restrictions via a crafted request.
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)
No detection rules found.
No public exploits indexed.
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/1045787https://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://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/1045787https://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://www.debian.org/security/2020/dsa-4714
2020-05-21
Published