CVE-2022-21604 in MySQL Server
Summary
by MITRE • 10/19/2022
Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.30 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).
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 04/26/2026
The vulnerability identified as CVE-2022-21604 resides within the InnoDB storage engine component of Oracle MySQL Server, representing a critical availability risk that affects all versions up to and including 8.0.30. This flaw manifests as a denial of service condition that can be triggered by high-privileged attackers who possess network access through multiple communication protocols. The vulnerability's classification as easily exploitable indicates that adversaries with sufficient privileges and network connectivity can reliably execute attacks without requiring complex exploitation techniques or specialized tools. The CVSS 3.1 scoring system assigns this vulnerability a base score of 4.9, with the availability impact component carrying the highest weight at level 8.0, reflecting the severe consequences of successful exploitation.
The technical nature of this vulnerability stems from improper handling of specific database operations within the InnoDB storage engine that leads to system instability. When exploited, the vulnerability enables attackers to cause either a complete hang or repeated crashes of the MySQL Server instance, effectively rendering the database service unavailable to legitimate users and applications. This behavior aligns with the ATT&CK framework's privilege escalation and denial of service tactics, where adversaries leverage existing access to disrupt service availability. The vulnerability's impact is particularly concerning because it operates at the server level, meaning that successful exploitation can compromise the entire database infrastructure rather than just individual queries or transactions. The fact that this affects high-privileged attackers suggests that the vulnerability may be triggered through administrative or database user accounts that already possess significant access rights.
From an operational perspective, the implications of CVE-2022-21604 extend beyond simple service disruption to encompass potential business continuity issues and data availability concerns. Organizations running affected MySQL versions face the risk of extended downtime that can impact applications dependent on database services, potentially leading to revenue loss and customer dissatisfaction. The vulnerability's susceptibility to network-based attacks means that even internal network compromise can lead to exploitation, as attackers can leverage existing database connections or network access points to deliver malicious payloads. This threat vector aligns with CWE-119, which addresses improper access to memory locations, and reflects the broader category of memory safety issues that can lead to system instability. The complete denial of service condition can result in cascading failures across interconnected systems that rely on MySQL for data persistence and transaction management.
Organizations should prioritize immediate remediation through official Oracle patches and updates to address this vulnerability. The recommended mitigation strategy includes applying the latest MySQL 8.0 patches that specifically address the InnoDB storage engine issues identified in this CVE. Network segmentation and access controls should be reviewed to limit unnecessary network access to MySQL instances, particularly for high-privileged accounts. Monitoring systems should be enhanced to detect unusual patterns of database connection behavior or performance degradation that might indicate exploitation attempts. Security teams should also consider implementing database activity monitoring solutions that can identify and alert on potentially malicious database operations that could trigger the vulnerability. Additionally, regular vulnerability assessments and penetration testing should be conducted to identify and remediate similar issues within the database infrastructure, as this vulnerability demonstrates the importance of maintaining up-to-date database software and security configurations. The ATT&CK framework's relevance here extends to defensive strategies that include network detection and response capabilities to identify and mitigate exploitation attempts before they can cause service disruption.