CVE-2017-3273 in MySQL Server
Summary
by MITRE
Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: DDL). Supported versions that are affected are 5.6.34 and earlier and 5.7.16 and earlier. Easily exploitable vulnerability allows low 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 v3.0 Base Score 6.5 (Availability impacts).
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 05/15/2026
The vulnerability identified as CVE-2017-3273 represents a critical availability threat within Oracle MySQL Server's Data Definition Language (DDL) subsystem. This flaw exists in the server component that handles database schema modifications and structural changes, making it particularly dangerous as it affects fundamental database operations. The vulnerability impacts specific version ranges including MySQL 5.6.34 and earlier versions, as well as 5.7.16 and earlier releases, indicating this weakness has persisted across multiple major versions of the database system. The vulnerability's classification as easily exploitable means that attackers with minimal privileges and network access can potentially trigger the flaw, making it a significant concern for database security.
The technical nature of this vulnerability involves a flaw in how MySQL Server processes certain DDL operations, specifically those related to schema modifications and structural changes within the database. When exploited, the vulnerability allows an attacker to cause the MySQL Server to either hang or experience frequently repeatable crashes, effectively resulting in a complete denial of service condition. This type of vulnerability falls under CWE-119 which describes weaknesses related to memory safety and improper handling of data structures during database operations. The flaw operates through multiple network protocols, making it particularly versatile in its exploitation potential and increasing the attack surface for potential adversaries.
The operational impact of CVE-2017-3273 extends beyond simple service disruption to potentially compromise the entire database infrastructure. A successful attack can render MySQL Server completely unavailable to legitimate users and applications, causing significant business disruption and potential data accessibility issues. The vulnerability's ability to cause repeated crashes means that even a single successful exploitation attempt can lead to prolonged service outages, as administrators must restart the database service and potentially recover from any corrupted state. This type of availability attack aligns with ATT&CK technique T1499 which encompasses various methods of disrupting services and causing denial of service conditions. Organizations relying on MySQL for critical applications face substantial risk of operational downtime and potential financial losses.
Mitigation strategies for CVE-2017-3273 should prioritize immediate patching of affected MySQL versions to the latest available releases that contain fixes for this specific vulnerability. System administrators should implement network segmentation and access controls to limit exposure of MySQL servers to untrusted networks, reducing the attack surface for potential exploitation. Monitoring and logging of database activities should be enhanced to detect anomalous DDL operations that might indicate exploitation attempts. Additionally, implementing database firewalls and intrusion detection systems can help identify and block malicious network traffic targeting MySQL services. The vulnerability highlights the importance of maintaining up-to-date database systems and following security best practices for database server hardening. Organizations should also consider implementing redundant database systems and backup procedures to minimize the impact of potential denial of service attacks. Regular vulnerability assessments and penetration testing should be conducted to identify and remediate similar weaknesses in database infrastructure, ensuring comprehensive protection against both current and emerging threats.