What is the severity of CVE-2024-21199?

CVE-2024-21199 is classified as a high severity vulnerability due to its exploitability by privileged attackers.

How do I fix CVE-2024-21199?

To fix CVE-2024-21199, update to MySQL version 8.0.40-1 or higher, or upgrade to the latest available version.

What versions of MySQL are affected by CVE-2024-21199?

CVE-2024-21199 affects MySQL versions 8.0.39 and prior, 8.4.2 and prior, and 9.0.1 and prior.

Is CVE-2024-21199 easy to exploit?

Yes, CVE-2024-21199 is considered easily exploitable by high privileged attackers with network access.

What component of MySQL is affected by CVE-2024-21199?

CVE-2024-21199 affects the InnoDB component of Oracle MySQL Server.

Vulnerability/
CVE-2024-21199

medium

4.9

15/10/2024

16/10/2024

CVE-2024-21199

First published: Tue Oct 15 2024(Updated: )

Last updated 12 November 2024

Credit: secalert_us@oracle.com secalert_us@oracle.com

Affected Software	Affected Version	How to fix
debian/mysql-8.0		8.0.40-1
MySQL	>=8.0.0<=8.0.39
MySQL	>=8.4.0<=8.4.2
MySQL	=9.0.0
MySQL	=9.0.1

Remedy

https://www.oracle.com/security-alerts/cpuoct2024.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2024-21199?
CVE-2024-21199 is classified as a high severity vulnerability due to its exploitability by privileged attackers.
How do I fix CVE-2024-21199?
To fix CVE-2024-21199, update to MySQL version 8.0.40-1 or higher, or upgrade to the latest available version.
What versions of MySQL are affected by CVE-2024-21199?
CVE-2024-21199 affects MySQL versions 8.0.39 and prior, 8.4.2 and prior, and 9.0.1 and prior.
Is CVE-2024-21199 easy to exploit?
Yes, CVE-2024-21199 is considered easily exploitable by high privileged attackers with network access.
What component of MySQL is affected by CVE-2024-21199?
CVE-2024-21199 affects the InnoDB component of Oracle MySQL Server.

agent/first-publish-date
agent/type
agent/severity
agent/last-modified-date
agent/remedy
collector/mitre-cve
source/MITRE
agent/references
collector/security-tracker-debian
source/Debian
agent/software-canonical-lookup
agent/softwarecombine
collector/usn-cve
source/Ubuntu
agent/description
agent/event
agent/author
agent/source
agent/tags
collector/nvd-api
source/NVD
agent/software-canonical-lookup-request
collector/nvd-cve
package-manager/debian
vendor/oracle
canonical/mysql
version/mysql/8.0.0
version/mysql/8.0.39
version/mysql/8.4.0
version/mysql/8.4.2
version/mysql/9.0.0
version/mysql/9.0.1

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2024-21199?
CVE-2024-21199 is classified as a high severity vulnerability due to its exploitability by privileged attackers.
How do I fix CVE-2024-21199?
To fix CVE-2024-21199, update to MySQL version 8.0.40-1 or higher, or upgrade to the latest available version.
What versions of MySQL are affected by CVE-2024-21199?
CVE-2024-21199 affects MySQL versions 8.0.39 and prior, 8.4.2 and prior, and 9.0.1 and prior.
Is CVE-2024-21199 easy to exploit?
Yes, CVE-2024-21199 is considered easily exploitable by high privileged attackers with network access.
What component of MySQL is affected by CVE-2024-21199?
CVE-2024-21199 affects the InnoDB component of Oracle MySQL Server.