Skip to content
Connect AISign inSign up free
CVE-2020-15180Not scoredCWE-96

CVE-2020-15180: mariadb vulnerability

Mariadb · mariadb

Vendor fix available · Affected: mariadb · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

5.3%probability of exploitation in the next 30 days
92nd percentile
050100

Higher than 92% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • mariadbmariadb 10.1.47, mariadb 10.2.34, mariadb 10.3.25, mariadb…

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
Mariadb
Published
May 2021

CoverageNo articles yet

No CyberSIXT article names CVE-2020-15180 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References