Percona XtraDB Cluster up to 5.5.41/5.6.32/5.7.14 Error Handling access control

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.0$0-$5k0.00

Summaryinfo

A vulnerability marked as critical has been reported in Percona XtraDB Cluster up to 5.5.41/5.6.32/5.7.14. Affected is an unknown function of the component Error Handling. Performing a manipulation results in access control. This vulnerability is cataloged as CVE-2016-5617. The attack must be initiated from a local position. Furthermore, there is an exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in Percona XtraDB Cluster up to 5.5.41/5.6.32/5.7.14. This affects an unknown code of the component Error Handling. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Unspecified vulnerability in Oracle MySQL 5.5.51 and earlier, 5.6.32 and earlier, and 5.7.14 and earlier allows local users to affect confidentiality, integrity, and availability via vectors related to Server: Error Handling.

The bug was discovered 10/18/2016. The weakness was shared 11/01/2016 by Dawid Golunski as MySQL / MariaDB / PerconaDB - Root Privilege Escalation Exploit as confirmed mailinglist post (Full-Disclosure). It is possible to read the advisory at seclists.org. The vendor cooperated in the coordination of the public release. This vulnerability is uniquely identified as CVE-2016-5617 since 06/16/2016. Attacking locally is a requirement. A authentication is needed for exploitation. Technical details are unknown but a public exploit is available. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

A public exploit has been developed by Dawid Golunski and been published immediately after the advisory. The exploit is shared for download at legalhackers.com. It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 94165 (MySQL 5.5.x < 5.5.53 Multiple Vulnerabilities (October 2016 CPU)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Databases and running in the context r. The commercial vulnerability scanner Qualys is able to test this issue with plugin 20027 (Oracle MySQL October 2016 Critical Patch Update (CPUOCT2016)).

Upgrading to version 5.5.41-37.0, 5.6.32-25.17 or 5.7.14-26.17 eliminates this vulnerability. A possible mitigation has been published before and not just after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Exploit-DB (40679), Tenable (94165) and SecurityFocus (BID 92912†). The entries VDB-91505, VDB-91506, VDB-91507 and VDB-92830 are related to this item. Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

Video

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.8
VulDB Meta Temp Score: 7.0

VulDB Base Score: 7.8
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Access control
CWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: Dawid Golunski
Download: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 94165
Nessus Name: MySQL 5.5.x < 5.5.53 Multiple Vulnerabilities (October 2016 CPU)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 867773
OpenVAS Name: Fedora Update for community-mysql FEDORA-2016-c7e60a9fd4
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍
Exploit Delay Time: 🔍

Upgrade: XtraDB Cluster 5.5.41-37.0/5.6.32-25.17/5.7.14-26.17

Timelineinfo

06/16/2016 🔍
10/18/2016 +124 days 🔍
10/18/2016 +0 days 🔍
10/19/2016 +1 days 🔍
10/20/2016 +1 days 🔍
11/01/2016 +12 days 🔍
11/01/2016 +0 days 🔍
11/28/2024 +2949 days 🔍

Sourcesinfo

Advisory: MySQL / MariaDB / PerconaDB - Root Privilege Escalation Exploit
Researcher: Dawid Golunski
Status: Confirmed
Coordinated: 🔍

CVE: CVE-2016-5617 (🔍)
GCVE (CVE): GCVE-0-2016-5617
GCVE (VulDB): GCVE-100-93279
SecurityFocus: 92912

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 10/19/2016 10:22
Updated: 11/28/2024 16:35
Changes: 10/19/2016 10:22 (55), 07/25/2019 08:42 (15), 09/29/2022 13:34 (7), 11/28/2024 16:35 (14)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!