Vulnerability in mariadb (CVE-2020-15180)
Summary
Vulnerability in mariadb (CVE-2020-15180). Successful exploitation can lead to full system takeover. Exploitable via wsrep_sst_method.
Original description
The description as published by the source.
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.
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-15180 has been found in mariadb.
Attackers can target a specific entry point like wsrep_sst_method over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "mariadb CVE-2020-15180" on the vendor's site.
CVE-2020-15180 (mariadb)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: wsrep_sst_method
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in mariadb. Attackers reach the vulnerable code path via wsrep_sst_method without authentication.
Check the vendor advisory for the affected versions of mariadb. Attack surface: wsrep_sst_method.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mariadb' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mariadb' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mariadbを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Alpine Linux ALPINE-CVE-2020-15180 mariadb Fixed in: 10.3.25-r0
- Debian DEBIAN-CVE-2020-15180 mariadb-10.5 Fixed in: 1:10.5.6-1
References
- advisory lists.debian.org
- advisory security.gentoo.org
- advisory debian.org
- advisory bugzilla.redhat.com
- advisory percona.com
- web nvd.nist.gov