MySQL vulnerabilitiesRanked by how likely they are to be used.
MySQL is made by Oracle. We track 1,297 published vulnerabilities listed under that exact name, across 676 versions. None of them is on the list of flaws known to be exploited today. Oracle lists newer releases under their own names, such as Mysql Server, so check those pages too.
We keep watching the known-exploited list.
Is MySQL listed under other names? Yes.
Oracle also lists MySQL under more specific names, such as Mysql Server and Mysql Enterprise Monitor. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
- Mysql Server229 published vulnerabilities
- Mysql Enterprise Monitor58 published vulnerabilities
- Mysql Cluster44 published vulnerabilities
- Mysql Workbench42 published vulnerabilities
- Mysql Connectors17 published vulnerabilities
- Mysql Connector/j6 published vulnerabilities
- Mysql Connector/net4 published vulnerabilities
- Mysql Connector/python3 published vulnerabilities
- Mysql Connector/c2 published vulnerabilities
- Mysql Enterprise Backup2 published vulnerabilities
- Mysql Shell2 published vulnerabilities
- Mysql Installer1 published vulnerability
Which MySQL vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of MySQL's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which MySQL flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 97%CVE-2012-2122Medium
sql/password.c in Oracle MySQL 5.1.x before 5.1.63, 5.5.x before 5.5.24, and 5.6.x before 5.6.6, and MariaDB 5.1.x before 5.1.62, 5.2.x before 5.2.12, 5.3.x before 5.3.6, and 5.5.x before 5.5.23, when running in...
- 92%CVE-2008-0226High
Multiple buffer overflows in yaSSL 1.7.5 and earlier, as used in MySQL and possibly other products, allow remote attackers to execute arbitrary code via (1) the ProcessOldClientHello function in handshake.cpp or (2)...
- 90%CVE-2017-3599High
Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Pluggable Auth).
- 89%CVE-2020-5398High
In Spring Framework, versions 5.2.x prior to 5.2.3, versions 5.1.x prior to 5.1.13, and versions 5.0.x prior to 5.0.16, an application is vulnerable to a reflected file download (RFD) attack when it sets a...
- 78%CVE-2003-0780Critical
Buffer overflow in get_salt_from_password from sql_acl.cc for MySQL 4.0.14 and earlier, and 3.23.x, allows attackers with ALTER TABLE privileges to execute arbitrary code via a long Password field.
- 70%CVE-2009-4484High
Multiple stack-based buffer overflows in the CertDecoder::GetName function in src/asn.cpp in TaoCrypt in yaSSL before 1.9.9, as used in mysqld in MySQL 5.0.x before 5.0.90, MySQL 5.1.x before 5.1.43, MySQL 5.5.x...
- 68%CVE-2016-6662Critical
Oracle MySQL through 5.5.52, 5.6.x through 5.6.33, and 5.7.x through 5.7.15; MariaDB before 5.5.51, 10.0.x before 10.0.27, and 10.1.x before 10.1.17; and Percona Server before 5.5.51-38.1, 5.6.x before 5.6.32-78.0,...
- 53%CVE-2020-1967High
Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due to a NULL pointer dereference as a result of incorrect handling of the...
- 45%CVE-2003-0150Critical
MySQL 3.23.55 and earlier creates world-writeable files and allows mysql users to gain root privileges by using the "SELECT * INFO OUTFILE" operator to overwrite a configuration file and cause mysql to run as root...
- 40%CVE-2016-2105High
Integer overflow in the EVP_EncodeUpdate function in crypto/evp/encode.c in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h allows remote attackers to cause a denial of service (heap memory corruption) via a large...
Running MySQL? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
sql/password.c in Oracle MySQL 5.1.x before 5.1.63, 5.5.x before 5.5.24, and 5.6.x before 5.6.6, and MariaDB 5.1.x before 5.1.62, 5.2.x before 5.2.12, 5.3.x before 5.3.6, and 5.5.x before 5.5.23, when running in certain environments with certain implementations of the memcmp function, allows remote attackers to bypass authentication by repeatedly authenticating with the same incorrect password, which eventually causes a token comparison to succeed due to an improperly-checked return value.
- Matched to
- MySQL on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 1,297 published vulnerabilities listed under the name MySQL, across 676 versions.
None of MySQL's vulnerabilities is on the list of flaws known to be exploited today.
Oracle also lists MySQL under more specific names, such as Mysql Server and Mysql Enterprise Monitor. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track MySQL. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.