CVE-2025-21490: Medium severity Oracle MySQL Server vulnerability

Published Jan 21, 2025
·
Updated

Last updated 31 March 2025

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

— Launchpad

Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.40 and prior, 8.4.3 and prior and 9.1.0 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).

— NVD

Affected Software

14 affected componentsFixes available
Oracle MySQL Server<8.0.40, <8.4.3, <9.1.0
Oracle MySQL Server>=8.0.0<=8.0.40
Oracle MySQL Server>=8.4.0<=8.4.3
Oracle MySQL Server>=9.0.0<=9.1.0
Debian Debian Linux=11.0
debian/mariadb
1:10.11.11-0+deb12u11:11.8.1-4
debian/mariadb-10.5<=1:10.5.23-0+deb11u1
1:10.5.28-0+deb11u1
debian/mysql-8.0
8.0.42-1
Microsoft cbl2 mariadb 10.6.20-1<10.6.21-1
10.6.21-1
Microsoft azl3 mariadb 10.11.10-1<10.11.11-1
10.11.11-1
Microsoft cbl2 mariadb 10.6.21-1<10.6.21-1
10.6.21-1
Microsoft cbl2 mysql 8.0.41-1<8.0.41-1
8.0.41-1
Microsoft cbl2 mysql 8.0.40-4<8.0.41-1
8.0.41-1
Microsoft azl3 mariadb 10.11.11-1<10.11.11-1
10.11.11-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/mariadb to a version that resolves this vulnerability.

    Fixed in 1:10.11.11-0+deb12u1Fixed in 1:11.8.1-4
  2. Upgrade

    Upgrade debian/mariadb-10.5 to a version that resolves this vulnerability.

    Fixed in 1:10.5.28-0+deb11u1
  3. Upgrade

    Upgrade debian/mysql-8.0 to a version that resolves this vulnerability.

    Fixed in 8.0.42-1
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.6.21-1
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.0.41-1
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.11.11-1
  7. Upgrade

    Upgrade Oracle MySQL (MySQL Server) - InnoDB to a version that resolves this vulnerability.

    Fixed in 8.0.40
  8. Upgrade

    Upgrade Oracle MySQL (MySQL Server) - InnoDB to a version that resolves this vulnerability.

    Fixed in 8.4.3
  9. Upgrade

    Upgrade Oracle MySQL (MySQL Server) - InnoDB to a version that resolves this vulnerability.

    Fixed in 9.1.0

Event History

Jan 21, 2025
CVE Published
via MITRE·08:52 PM
Data Sourced
via MITRE·08:52 PM
DescriptionSeverity
Data Sourced
via Red Hat·09:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeaknessAffected Software
Mar 27, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
Severity
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Data Sourced
via Launchpad·11:43 AM
Description
Apr 8, 2025
Data Sourced
via Ubuntu·11:44 AM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-21490?

CVE-2025-21490 is considered a high severity vulnerability due to its ease of exploitation by high privileged attackers.

2

How do I fix CVE-2025-21490?

To fix CVE-2025-21490, upgrade to MySQL Server versions 8.0.41-2, 8.4.4 or later, and 9.1.1 or later.

3

Which MySQL versions are affected by CVE-2025-21490?

Affected MySQL versions include 8.0.40 and prior, 8.4.3 and prior, and 9.1.0 and prior.

4

What component of MySQL is impacted by CVE-2025-21490?

CVE-2025-21490 impacts the InnoDB component of the MySQL Server product.

5

Who is primarily affected by CVE-2025-21490?

High privileged attackers with network access are primarily able to exploit CVE-2025-21490.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203