Mysql Server vulnerabilitiesRanked by how likely they are to be used.
Mysql Server is made by Oracle. We track 229 published vulnerabilities in it, across 59 versions. None of them is on the list of flaws known to be exploited today. If you run Mysql Server, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Mysql Server vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Mysql Server's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Mysql Server 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.
- 88%CVE-2021-3711Critical
In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt().
- 83%CVE-2022-1292High
The c_rehash script does not properly sanitise shell metacharacters to prevent command injection.
- 82%CVE-2021-21351Medium
XStream is a Java library to serialize objects to XML and back again.
- 76%CVE-2021-21344Medium
XStream is a Java library to serialize objects to XML and back again.
- 64%CVE-2021-3449Medium
An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client.
- 64%CVE-2021-22901High
curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session ticket arrives over a connection.
- 51%CVE-2021-23840High
Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform.
- 50%CVE-2021-3712High
ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length.
- 50%CVE-2019-5436High
A heap buffer overflow in the TFTP receiving code allows for DoS or arbitrary code execution in libcurl versions 7.19.4 through 7.64.1.
- 41%CVE-2021-2429Medium
Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB).
Running Mysql Server? 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
In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the "out" parameter can be NULL and, on exit, the "outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the "out" parameter. A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a second time with a buffer that is too small. A malicious attacker who is able present SM2 content for decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of 62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour or causing the application to crash. The location of the buffer is application dependent but is typically heap allocated. Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k).
- Matched to
- Mysql Server 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 229 published vulnerabilities listed under the name Mysql Server, across 59 versions.
None of Mysql Server's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Mysql Server. 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.