Critical Man-in-the-Middle Vulnerability in MariaDB on Windows
Summary
ALPINE-CVE-2020-28912: 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... Affects mariadb versions < 10.3.27-r0. Fixed in 10.3.27-r0. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
MariaDB is an open-source relational database management system that is widely used for web applications and data storage. It is known for its high performance, scalability, and compatibility with MySQL. However, certain versions of MariaDB have been found to be vulnerable to a man-in-the-middle attack when local clients connect to the server over named pipes, allowing unauthorized access to sensitive data.
Vulnerability Detail
The vulnerability arises from an incorrect security descriptor in MariaDB when running on Windows. This flaw allows an unprivileged user with code execution capabilities on the server machine to intercept named pipe connections. As a result, the attacker can access all data transmitted between the client and the server, and execute SQL commands on behalf of the connected user. This vulnerability affects MariaDB Server versions prior to 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. It is important to note that this issue is specific to MariaDB and does not apply to other vendors affected by CVE-2019-2503.
How To Fix
Minimum fixed version
10.3.27-r0
This is the first release that contains the fix.
sudo apk add --upgrade mariadbTip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, consider disabling named pipe connections or restricting access to the server to trusted users only until the update can be applied. This can help mitigate the risk of unauthorized access.
Conclusion
The identified vulnerability in MariaDB poses a significant risk to data security when running on Windows. It is crucial for users to update to the patched version to mitigate potential attacks. Implementing workarounds can provide temporary relief while ensuring that systems are secured against unauthorized access.
See every vulnerability recorded for mariadb →
FAQ
The CVSS score of this vulnerability is 7.0, indicating a high severity level.
Affected versions include MariaDB Server versions 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.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
If immediate updates are not possible, implement workarounds such as disabling named pipe connections or limiting server access to trusted users.
Yes, this vulnerability is specific to MariaDB and does not apply to other vendors that were originally affected by CVE-2019-2503.
References
Related vulnerabilities
Recent vulnerabilities recorded for mariadb.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
