Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.0-8.0.43, 8.4.0-8.4.6 and 9.0.0-9.4.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 as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 5.5 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H).
Weakness
The product does not properly control the allocation and maintenance of a limited resource.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Mysql_server | Oracle | 8.0.0 (including) | 8.0.42 (including) |
| Mysql_server | Oracle | 8.4.0 (including) | 8.4.6 (including) |
| Mysql_server | Oracle | 9.0.0 (including) | 9.4.0 (including) |
| Red Hat Enterprise Linux 10 | RedHat | mysql8.4-0:8.4.7-1.el10_1 | * |
| Red Hat Enterprise Linux 8 | RedHat | mysql:8.0-8100020251125095949.489197e6 | * |
| Red Hat Enterprise Linux 8 | RedHat | mysql:8.4-8100020251124123230.489197e6 | * |
| Red Hat Enterprise Linux 9 | RedHat | mysql-0:8.0.44-1.el9_7 | * |
| Red Hat Enterprise Linux 9 | RedHat | mysql:8.4-9070020251124122854.rhel9 | * |
| Mariadb-10.3 | Ubuntu | esm-apps/focal | * |
| Mysql-5.5 | Ubuntu | esm-infra-legacy/trusty | * |
| Mysql-5.7 | Ubuntu | esm-infra/bionic | * |
| Mysql-5.7 | Ubuntu | esm-infra/xenial | * |
| Mysql-8.0 | Ubuntu | jammy | * |
| Mysql-8.0 | Ubuntu | noble | * |
| Mysql-8.0 | Ubuntu | upstream | * |
| Mysql-8.4 | Ubuntu | devel | * |
| Mysql-8.4 | Ubuntu | plucky | * |
| Mysql-8.4 | Ubuntu | questing | * |
| Mysql-8.4 | Ubuntu | upstream | * |
Potential Mitigations
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
Related Attack Patterns
- https://cwe.mitre.org/data/definitions/147.html
- https://cwe.mitre.org/data/definitions/227.html
- https://cwe.mitre.org/data/definitions/492.html