CVE-2022-21637 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/27/2026
The vulnerability identified as CVE-2022-21637 resides within the InnoDB storage engine component of Oracle MySQL Server, representing a significant availability risk that affects versions 8.0.30 and earlier. This flaw manifests as a denial of service condition that can be triggered by a high privileged attacker who possesses network access through multiple protocols. The vulnerability operates at the database engine level where InnoDB manages transactional operations and storage management, making it particularly dangerous as it directly impacts the core functionality of the database system. The attack vector requires network connectivity and elevated privileges, indicating that while not trivial to exploit, it represents a genuine threat to database availability and system stability. The CVSS score of 4.9 reflects the moderate severity of the availability impact, though the potential for complete system disruption makes this vulnerability particularly concerning for production environments.
The technical nature of this vulnerability stems from improper handling of certain database operations within the InnoDB storage engine that leads to system instability. When exploited, the flaw causes the MySQL Server to either hang indefinitely or experience repeated crashes that can effectively render the database service unavailable to legitimate users and applications. This behavior aligns with CWE-400 vulnerability classification related to resource exhaustion and system instability, though specifically within the database context. The vulnerability's exploitation requires an attacker with high privileges, suggesting that the threat may come from internal sources or compromised administrative accounts rather than external attackers. However, the network accessibility aspect means that any compromised account with sufficient privileges could potentially trigger this condition, making it a critical concern for database administrators who must maintain strict access controls and monitoring protocols.
From an operational impact perspective, successful exploitation of CVE-2022-21637 can result in complete disruption of database services, affecting all applications and systems that depend on the MySQL Server for data operations. The repeated crash scenario poses particular challenges for database availability, as it can lead to extended downtime periods that may require manual intervention to restore service. Organizations relying on MySQL for mission-critical applications face significant risk from this vulnerability, as the denial of service condition can cascade through dependent systems and applications. The impact extends beyond simple unavailability to include potential data consistency issues and recovery complications that may require extensive troubleshooting and system restoration efforts. This vulnerability directly maps to ATT&CK technique T1499.004 related to network denial of service, though specifically targeting database services rather than general network infrastructure.
The recommended mitigation strategies for CVE-2022-21637 center around immediate patching of affected MySQL Server installations to version 8.0.31 or later, which contains the necessary fixes for the InnoDB storage engine vulnerability. Organizations should also implement robust monitoring solutions that can detect unusual patterns of database crashes or hangs that might indicate exploitation attempts. Access controls should be strictly enforced with minimal privilege assignments and comprehensive audit logging of administrative activities to detect potential misuse of elevated privileges. Network segmentation and firewall rules should be reviewed to limit unnecessary access to MySQL services, while implementing intrusion detection systems that can identify suspicious network activity patterns. Additionally, organizations should conduct regular vulnerability assessments and penetration testing to identify potential attack vectors and ensure that all database systems remain protected against similar vulnerabilities. The remediation process should include thorough testing of patches in non-production environments before deployment to ensure compatibility with existing applications and database configurations.