With MariaDB running on Windows, when local clients connect… (CVE-2020-28912)

Summary

Vulnerability reported (CVE-2020-28912). Successful exploitation can lead to full system takeover.

Original description

The description as published by the source.

With MariaDB running on Windows, when local clients connect to the server over named pipes, it's possible for an unprivileged user with an ability to run code on the server machine to intercept the named pipe connection and act as a man-in-the-middle, gaining access to all the data passed between the client and the server, and getting the ability to run SQL commands on behalf of the connected user. This occurs because of an incorrect security descriptor. This affects MariaDB Server before 10.1.48, 10.2.x before 10.2.35, 10.3.x before 10.3.26, 10.4.x before 10.4.16, and 10.5.x before 10.5.7. NOTE: this issue exists because certain details of the MariaDB CVE-2019-2503 fix did not comprehensively address attack variants against MariaDB. This situation is specific to MariaDB, and thus CVE-2020-28912 does NOT apply to other vendors that were originally affected by CVE-2019-2503.

Source: OSV.dev (Open Source Vulnerabilities) NVD 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 CVE-2020-28912 has been found.
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 "CVE-2020-28912" on the vendor's site.

CVE-2020-28912
Attack vector: local / no user interaction
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) has been reported.

📍 Affected scope

Check the vendor advisory for the affected versions.

🔥 Severity

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

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
2
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami mysql-client

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"10.1.48"},{"introduced":"10.2.0"},{"fixed":"10.2.35"},{"introduced":"10.3.0"},{"fixed":"10.3.26"},{"introduced":"10.4.0"},{"fixed":"10.4.16"},{"introduced":"10.5.0"},{"fixed":"10.5.7"}]}]

Bitnami mariadb-min

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"10.1.48"},{"introduced":"10.2.0"},{"fixed":"10.2.35"},{"introduced":"10.3.0"},{"fixed":"10.3.26"},{"introduced":"10.4.0"},{"fixed":"10.4.16"},{"introduced":"10.5.0"},{"fixed":"10.5.7"}]}]

Bitnami mariadb

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"10.1.48"},{"introduced":"10.2.0"},{"fixed":"10.2.35"},{"introduced":"10.3.0"},{"fixed":"10.3.26"},{"introduced":"10.4.0"},{"fixed":"10.4.16"},{"introduced":"10.5.0"},{"fixed":"10.5.7"}]}]

With MariaDB running on Windows, when local clients connect to the server over named pipes, it's possible for an…

Summary

Original description

Auto-generated summary

Response actions

Affected packages

References