CVE-2025-50099
Description
From CVE.org
Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.0-8.0.42, 8.4.0-8.4.5 and 9.0.0-9.3.0. 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).
Statement
A moderate impact denial of service vulnerability was found in the InnoDB component of MySQL. An easily exploitable flaw allows a highly privileged attacker with network access via multiple protocols to compromise MySQL Server; successful attacks can result in a hang or frequently repeatable crash (complete denial of service) of MySQL Server. Only availability is impacted; confidentiality and integrity are not affected. Upstream reports that MySQL Server versions 8.0.0-8.0.42, 8.4.0-8.4.5, and 9.0.0-9.3.0 are affected. Red Hat rated this flaw Moderate impact with a CVSS 3.1 base score of 4.9 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H), consistent with the upstream Oracle assessment.
The mysql components in Red Hat Enterprise Linux 8, 9, and 10 (including the mysql:8.0 and mysql:8.4 module streams and the mysql8.4 component) are affected, and a fix is being pursued through the delegated resolution channels with updated packages delivered via the respective update streams. The mysql package in Red Hat Enterprise Linux 6 Extended Lifecycle Support is not affected because the vulnerable code is not present. The Red Hat In-Vehicle OS stream is delegated and has been assessed as not affected by the platform team. For Fedora, updates for the mysql8.0 and mysql8.4 packages are deferred; the fix is available in Rawhide, and users of stable Fedora releases remain exposed to a denial of service by a highly privileged database user until updated packages become available.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Updated mysql packages that address this flaw have been released for the affected Red Hat Enterprise Linux releases through their respective update streams, and users are advised to update to the latest available packages. For Fedora, the fix is currently available only in Rawhide.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 4.9 | N/A | 4.9 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | High | N/A | High |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)
If an attacker can trigger the allocation of the limited resources, but the number or size of the resources is not controlled, then the most common result is denial of service. This would prevent valid users from accessing the product, and it could potentially have an impact on the surrounding environment, i.e., the product may slow down, crash due to unhandled errors, or lock out legitimate users. For example, a memory exhaustion attack against an application could slow down the application as well as its host operating system.
Access Control,Other
Technical Impact: Bypass Protection Mechanism; Other
In some cases it may be possible to force the product to "fail open" in the event of resource exhaustion. The state of the product -- and possibly the security functionality - may then be compromised.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
