CVE-2020-29591

Versions of the Official registry Docker images through 2.7.0 contain a blank password for the root user. Systems deployed using affected versions of the registry container may allow a remote attacker to achieve root access with a blank password.

Published: 2020-12-11 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-29591 is rated High Risk (68.3/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 2.61%). 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-29591

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 2026-06-15 2.66% 2.61% -0.04%
2 2025-03-30 4.48% 2.66% -1.83%
3 2025-03-29 — 4.48% —

Full EPSS history (12 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
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.
 3.9 5.9 [email protected]
10.0 2.0 HIGH
AV:N/AC:L/Au:N/C:C/I:C/A:C Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 10.0 10.0 [email protected]

Weakness enumeration for CVE-2020-29591

Affected software / configurations for CVE-2020-29591

Vendor Product Version Raw CPE
docker registry 2.5 cpe:2.3:a:docker:registry:2.5:*:*:*:*:*:*:*
docker registry 2.5.0 cpe:2.3:a:docker:registry:2.5.0:*:*:*:*:*:*:*
docker registry 2.5.0 cpe:2.3:a:docker:registry:2.5.0:rc:*:*:*:*:*:*
docker registry 2.5.0 cpe:2.3:a:docker:registry:2.5.0:rc2:*:*:*:*:*:*
docker registry 2.5.1 cpe:2.3:a:docker:registry:2.5.1:*:*:*:*:*:*:*
docker registry 2.6.0 cpe:2.3:a:docker:registry:2.6.0:*:*:*:*:*:*:*
docker registry 2.6.0 cpe:2.3:a:docker:registry:2.6.0:rc2:*:*:*:*:*:*
docker registry 2.6.1 cpe:2.3:a:docker:registry:2.6.1:*:*:*:*:*:*:*
docker registry 2.6.1 cpe:2.3:a:docker:registry:2.6.1:rc2:*:*:*:*:*:*
docker registry 2.7.0 cpe:2.3:a:docker:registry:2.7.0:*:*:*:*:*:*:*

References for CVE-2020-29591

cvelogic Threat Intelligence