CVE-2020-6493

Use after free in WebAuthentication in Google Chrome prior to 83.0.4103.97 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page.

Published: 2020-06-03 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-6493 is rated High Risk (66.5/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 1.64%). High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-6493

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-22 1.98% 1.64% -0.34%
2 2025-10-15 3.61% 1.98% -1.63%
3 2025-03-30 — 3.61% —

Full EPSS history (17 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-6493

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.6 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 6.0 [email protected]
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 6.4 [email protected]

Weakness enumeration for CVE-2020-6493

OS Trackers for CVE-2020-6493

vendor priority summary link
debian not yet assigned CVE-2020-6493 not yet assigned priority: Debian including 1 source packages (chromium), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2020-6493
gentoo normal CVE-2020-6493: 1 GLSA(s) (202006-02), 2 atom(s) (www-client/chromium, www-client/google-chrome); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2020-6493
redhat high — https://access.redhat.com/security/cve/CVE-2020-6493
ubuntu medium CVE-2020-6493 medium priority: Ubuntu including 1 source packages (chromium-browser), 6 status rows across 6 suites (bionic, eoan, focal, trusty, upstream, xenial): released 3, DNE 2, not-affected 1. https://ubuntu.com/security/CVE-2020-6493

Affected software / configurations for CVE-2020-6493

Vendor Product Version Raw CPE
google chrome < 83.0.4103.97 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
debian debian_linux 9.0 cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
opensuse backports sle-15 cpe:2.3:o:opensuse:backports:sle-15:sp1:*:*:*:*:*:*
opensuse leap 15.1 cpe:2.3:o:opensuse:leap:15.1:*:*:*:*:*:*:*

References for CVE-2020-6493

cvelogic Threat Intelligence