Vulnerability in mariadb-10.5 (DEBIAN-CVE-2020-15180)

Summary

Vulnerability in mariadb-10.5 (DEBIAN-CVE-2020-15180). Successful exploitation can lead to full system takeover. Exploitable via wsrep_sst_method. Mitigation: upgrade to 1:10.5.6-1 or later.

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.

Source: OSV.dev (Open Source Vulnerabilities) OSV

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 DEBIAN-CVE-2020-15180 has been found in mariadb-10.5.
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: upgrade mariadb-10.5 to 1:10.5.6-1 or later.
If unsure, ask your IT team or search "mariadb-10.5 DEBIAN-CVE-2020-15180" on the vendor's site.

DEBIAN-CVE-2020-15180 (mariadb-10.5)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: wsrep_sst_method
Patched: 1:10.5.6-1 — apply immediately
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.

❓ What is the problem

A vulnerability (unclassified) exists in mariadb-10.5. Attackers reach the vulnerable code path via wsrep_sst_method without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of mariadb-10.5. Attack surface: wsrep_sst_method.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1:10.5.6-1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mariadb-10.5' . 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

1
Identify exposure identify
```
grep -r 'mariadb-10.5' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で mariadb-10.5 を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade mariadb-10.5 to 1:10.5.6-1
```
ステージング環境で 1:10.5.6-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:11 mariadb-10.5

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:10.5.6-1"}]}]

References

advisory security-tracker.debian.org