MariaDB: Numerous issues caused by historical #mysql50# tablename encoding bypass.
- Published
- Last modified
- Status
- published
- Known exploitation
- Not listed in CISA KEV
- Fix
- Fixed in 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 1 more
- Public exploit
- None on Exploit-DB
- Exploitation: none
- Automatable: no
- Technical impact: total
?
Decision points from CISA's Vulnrichment, assessed (SSVC 2.0.3).
SSVC documentationSummary
MariaDB server is a community developed fork of MySQL server. From 10.6.1 until 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2, the #mysql50# bypass prefix is affected because it allows the #mysql50# prefix to bypass normal table-name filesystem encoding. An attacker can trigger the issue with a table name using the #mysql50# prefix, then use a #mysql50# table name to access files under their legacy unencoded name and cause crashes, data corruption, data exfiltration, or remote code execution. This issue is fixed in versions 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2.
Affected versions
- MariaDB server
From 10.6.1 · fixed in 10.6.28; From 10.11.1 · fixed in 10.11.19; From 11.4.1 · fixed in 11.4.13; From 11.8.1 · fixed in 11.8.9; From 12.3.1 · fixed in 12.3.3; From 13.0.1 · fixed in 13.0.2
- mariadbBitnami
From 10.6.1 · fixed in 10.6.28; From 10.11.0 · fixed in 10.11.19; From 11.4.0 · fixed in 11.4.13; From 11.8.0 · fixed in 11.8.9; From 12.3.0 · fixed in 12.3.3; From 13.0.0 · fixed in 13.0.2
- mariadb-minBitnami
From 10.6.1 · fixed in 10.6.28; From 10.11.0 · fixed in 10.11.19; From 11.4.0 · fixed in 11.4.13; From 11.8.0 · fixed in 11.8.9; From 12.3.0 · fixed in 12.3.3; From 13.0.0 · fixed in 13.0.2
- mysql-clientBitnami
From 10.6.1 · fixed in 10.6.28; From 10.11.0 · fixed in 10.11.19; From 11.4.0 · fixed in 11.4.13; From 11.8.0 · fixed in 11.8.9; From 12.3.0 · fixed in 12.3.3; From 13.0.0 · fixed in 13.0.2