Outdated MySQL or MariaDB
A MySQL or MariaDB server runs a release that is missing security fixes or is no longer supported.
| Severity | Medium |
| CVSS 3.1 | 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Open in the calculator |
| CVSS 4.0 | 7.1 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-1395: Dependency on Vulnerable Third-Party Component |
| OWASP Top 10 | A03:2025 Software Supply Chain Failures |
| MITRE ATT&CK | T1499.004 Application or System Exploitation, T1210 Exploitation of Remote Services |
| Category | Outdated Components |
Description
A MySQL or MariaDB database server runs a release that predates fixes for one or more published vulnerabilities, or a release series that no longer receives fixes, in which the number of unfixed flaws grows over time. Oracle publishes MySQL fixes in its quarterly Critical Patch Updates, which typically list many MySQL Server flaws, and MariaDB publishes the CVEs fixed in each of its releases.
Most of these flaws let an authenticated user crash the server or make it hang, so a user with a database account, including an application's own account if the application is compromised, can stop the database repeatedly and cause an outage for every application that relies on it. A smaller number allow such a user to read or modify data beyond their privileges or to escalate to administrative rights, or allow exploitation of vulnerable components bundled with the server, such as its TLS library. Very few MySQL or MariaDB vulnerabilities are exploitable without credentials, so the risk is considerably higher where the database port is exposed to untrusted networks or where weak or shared database credentials are in use.
The finding is usually raised from the version string the server sends in its greeting before authentication, or from installed packages in an authenticated scan, and scanners report one result per advisory affecting that version. Linux distributions backport fixes into the version they ship, so results based on the greeting alone should be confirmed against the distribution's advisories. Because Oracle's advisories describe each flaw only briefly, the privileges and server component needed to exploit each one should be checked before judging its relevance.
Remediation
Update the database server and limit who can reach it:
- Install the latest release of the series in use, from Oracle or MariaDB, or the distribution's latest packages, following the vendor's upgrade notes, and restart the server. For MySQL, apply each quarterly Critical Patch Update promptly after its release.
- Move release series that have reached end of life, as published by Oracle and the MariaDB project, to a supported series, testing applications first.
- Restrict network access to the database port to the application servers and administrators that need it, and never expose it to the internet.
- Give application accounts only the privileges they need, remove anonymous and unused accounts, and limit administrative accounts to local or management connections.
Confirm the fix by running SELECT VERSION(); and comparing the result with the fixed version for each reported CVE, or by checking the installed package against the distribution's advisories.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.