CVE-2020-15180

A flaw was found in the mysql-wsrep component of mariadb. Lack of input sanitization in `wsrep_sst_method` allows for command injection that can be exploited by a remote attacker to execute arbitrary commands on galera cluster nodes. This threatens the system's confidentiality, integrity, and availability. This flaw affects mariadb versions before 10.1.47, before 10.2.34, before 10.3.25, before 10.4.15 and before 10.5.6.

Published: 2021-05-27 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-15180 is rated High Risk (68.3/100): CVSS Critical severity, with high exploitation likelihood (EPSS 5.54%, 92th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. 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-15180

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-23 5.35% 5.54% +0.19%
2 2026-06-18 5.56% 5.35% -0.22%
3 2026-06-15 — 5.56% —

Full EPSS history (20 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.0 3.1 CRITICAL
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
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: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.2 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-15180

OS Trackers for CVE-2020-15180

vendor priority summary link
alpine critical CVE-2020-15180: 1 source package rows (mariadb); 60 state rows across 10 repos (3.10-main, 3.11-main, 3.12-main, 3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 10, open 50. https://security.alpinelinux.org/vuln/CVE-2020-15180
debian not yet assigned CVE-2020-15180 not yet assigned priority: Debian including 1 source packages (mariadb-10.5), 1 status rows across 1 suites (bullseye): resolved 1. https://security-tracker.debian.org/tracker/CVE-2020-15180
gentoo high CVE-2020-15180: 1 GLSA(s) (202011-14), 1 atom(s) (dev-db/mariadb); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2020-15180
redhat high — https://access.redhat.com/security/cve/CVE-2020-15180
suse critical CVE-2020-15180 severity critical: SUSE including 151 source package names (10.6-12.1:libmariadb3-3.1.11-3.22.2, 10.6-14.4:libmariadb3-3.1.11-3.22.2, …), 385 product×package rows across 51 product lines (Container suse/rmt-mariadb, Container suse/rmt-mariadb-client, … (51 product lines)): Fixed 313, Known Not Affected 72. https://www.suse.com/security/cve/CVE-2020-15180/
ubuntu medium CVE-2020-15180 medium priority: Ubuntu including 3 source packages (mariadb-10.0, mariadb-10.1, mariadb-10.3), 48 status rows across 16 suites (bionic, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 41, needs-triage 3, released 2, ignored 1, needed 1. https://ubuntu.com/security/CVE-2020-15180

Affected software / configurations for CVE-2020-15180

Vendor Product Version Raw CPE
mariadb mariadb >= 10.1.0, < 10.1.47 cpe:2.3:a:mariadb:mariadb:*:*:*:*:*:*:*:*
mariadb mariadb >= 10.2.0, < 10.2.34 cpe:2.3:a:mariadb:mariadb:*:*:*:*:*:*:*:*
mariadb mariadb >= 10.3.0, < 10.3.25 cpe:2.3:a:mariadb:mariadb:*:*:*:*:*:*:*:*
mariadb mariadb >= 10.4.0, < 10.4.15 cpe:2.3:a:mariadb:mariadb:*:*:*:*:*:*:*:*
mariadb mariadb >= 10.5.0, < 10.5.6 cpe:2.3:a:mariadb:mariadb:*:*:*:*:*:*:*:*
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:*:*:*:*:*:*:*
percona xtradb_cluster < 5.6.49-28.42.2 cpe:2.3:a:percona:xtradb_cluster:*:*:*:*:*:*:*:*
percona xtradb_cluster >= 5.7, < 5.7.31-31.45.2 cpe:2.3:a:percona:xtradb_cluster:*:*:*:*:*:*:*:*
percona xtradb_cluster >= 8.0, < 8.0.20-11.2 cpe:2.3:a:percona:xtradb_cluster:*:*:*:*:*:*:*:*
galeracluster galera_cluster_for_mysql >= 5.6, < 5.6.49 cpe:2.3:a:galeracluster:galera_cluster_for_mysql:*:*:*:*:*:*:*:*
galeracluster galera_cluster_for_mysql >= 5.7, < 5.7.31 cpe:2.3:a:galeracluster:galera_cluster_for_mysql:*:*:*:*:*:*:*:*
galeracluster galera_cluster_for_mysql >= 8.0, < 8.0.21 cpe:2.3:a:galeracluster:galera_cluster_for_mysql:*:*:*:*:*:*:*:*

References for CVE-2020-15180

cvelogic Threat Intelligence