CVE-2017-10165 in MySQL Server
Summary
by MITRE
Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Replication). Supported versions that are affected are 5.7.19 and earlier. 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.0 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 01/18/2021
The vulnerability identified as CVE-2017-10165 resides within the MySQL Server component, specifically within the Server: Replication subcomponent of Oracle MySQL software. This issue affects versions 5.7.19 and earlier, representing a significant security concern for database administrators managing MySQL deployments. The vulnerability operates at a fundamental level within the replication mechanism that MySQL employs to maintain data consistency across multiple database instances, making it particularly dangerous given the critical role replication plays in database infrastructure.
The technical flaw manifests as an easily exploitable vulnerability that requires only high privileged attacker access combined with network connectivity through multiple protocols to achieve successful exploitation. This configuration creates a dangerous attack surface where authenticated users with elevated privileges can leverage their access to deliver malicious payloads that target the replication subsystem. The vulnerability's exploitability classification indicates that attackers do not require specialized tools or extensive technical knowledge to execute successful attacks, making it particularly concerning for production environments where privilege escalation might occur through various attack vectors.
The operational impact of this vulnerability extends beyond simple service disruption to potentially causing complete denial of service conditions within MySQL Server environments. Successful exploitation results in unauthorized ability to cause either hangs or frequently repeatable crashes that can completely bring down the database server. This availability impact represents a severe threat to database reliability and business continuity, as database downtime can cascade into broader system failures affecting applications and services dependent on the affected MySQL instances. The CVSS 3.0 Base Score of 4.9 reflects the moderate to high severity of the availability impact, with the vector indicating network accessibility, low attack complexity, high privileges required, and no user interaction needed.
From a cybersecurity perspective, this vulnerability aligns with CWE-119, which addresses improper restriction of operations within a limited scope, and demonstrates characteristics consistent with ATT&CK technique T1489, which involves denying access to resources through service interruption. The replication subsystem represents a critical component where attackers can leverage existing elevated privileges to disrupt database operations, potentially causing cascading failures throughout connected systems that depend on MySQL replication for data synchronization and high availability configurations.
Organizations should immediately implement mitigations including upgrading to MySQL versions that address this vulnerability, typically versions beyond 5.7.19, and implementing network segmentation to limit access to database servers. Additional protective measures include monitoring replication processes for anomalous behavior, implementing strict access controls to prevent privilege escalation, and conducting regular security assessments of database environments to identify and remediate similar vulnerabilities. The vulnerability highlights the importance of maintaining current database software versions and implementing robust security controls around privileged database access to prevent exploitation that could result in complete service disruption and data availability issues.