Oracle MySQL up to 5.5.51/5.6.32/5.7.14 race condition

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.
5.9	$0-$5k	0.00

Summaryinfo

A vulnerability was found in Oracle MySQL up to 5.5.51/5.6.32/5.7.14. It has been declared as problematic. The impacted element is an unknown function. Executing a manipulation can lead to race condition. This vulnerability is tracked as CVE-2016-6663. The attack is restricted to local execution. Moreover, an exploit is present. Applying a patch is advised to resolve this issue.

Detailsinfo

A vulnerability classified as problematic was found in Oracle MySQL up to 5.5.51/5.6.32/5.7.14 (Database Software). This vulnerability affects some unknown processing. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. As an impact it is known to affect confidentiality, integrity, and availability.

The bug was discovered 09/12/2016. The weakness was disclosed 11/01/2016 by Dawid Golunski as MySQL / MariaDB / PerconaDB - Privilege Escalation / Race Condition Exploit [CVE-2016-6663 / OCVE-2016-5616] as confirmed mailinglist post (Full-Disclosure). The advisory is shared for download at seclists.org. The public release has been coordinated in cooperation with the vendor. This vulnerability was named CVE-2016-6663 since 08/10/2016. The exploitation appears to be easy. The attack needs to be approached locally. Required for exploitation is a single authentication. Technical details are unknown but a public exploit is available. The advisory points out:

An independent research has revealed a race condition vulnerability which affects MySQl, MariaDB and PerconaDB databases. The vulnerability can allow a local system user with access to the affected database in the context of a low-privileged account (CREATE/INSERT/SELECT grants) to escalate their privileges and execute arbitrary code as the database system user (typically 'mysql'). Successful exploitation would allow an attacker to gain full read/write access to all of the files (including configuration files) and databases belonging to the affected database server.

A public exploit has been developed by Dawid Golunski in ANSI C and been published immediately after the advisory. It is possible to download the exploit at legalhackers.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 50 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 96812 (CentOS 6 : mysql (CESA-2017:0184)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CentOS Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 236167 (Red Hat Update for mariadb (RHSA-2016:2595)).

Applying a patch is able to eliminate this problem. A possible mitigation has been published 4 months after the disclosure of the vulnerability. The mailinglist post contains the following remark:

The issue was however mentioned in Oracle CPU mistakenly under a new CVE of CVE-2016-5616, resulting in a duplicate. Oracle has informed that CPU will be updated to state that CVE-2016-5616 is equivalent to CVE-2016-6663.

The vulnerability is also documented in the databases at Exploit-DB (40360), Tenable (96812) and SecurityFocus (BID 92911†). The entries VDB-4597, VDB-4598, VDB-20222 and VDB-79101 are pretty similar. VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

• Database Software

Vendor

• Oracle

Name

• MySQL

Version

• 5.5.0
• 5.5.1
• 5.5.2
• 5.5.3
• 5.5.4
• 5.5.5
• 5.5.6
• 5.5.7
• 5.5.8
• 5.5.9
• 5.5.10
• 5.5.11
• 5.5.12
• 5.5.13
• 5.5.14
• 5.5.15
• 5.5.16
• 5.5.17
• 5.5.18
• 5.5.19
• 5.5.20
• 5.5.21
• 5.5.22
• 5.5.23
• 5.5.24
• 5.5.25
• 5.5.26
• 5.5.27
• 5.5.28
• 5.5.29
• 5.5.30
• 5.5.31
• 5.5.32
• 5.5.33
• 5.5.34
• 5.5.35
• 5.5.36
• 5.5.37
• 5.5.38
• 5.5.39
• 5.5.40
• 5.5.41
• 5.5.42
• 5.5.43
• 5.5.44
• 5.5.45
• 5.5.46
• 5.5.47
• 5.5.48
• 5.5.49
• 5.5.50
• 5.5.51
• 5.6.0
• 5.6.1
• 5.6.2
• 5.6.3
• 5.6.4
• 5.6.5
• 5.6.6
• 5.6.7
• 5.6.8
• 5.6.9
• 5.6.10
• 5.6.11
• 5.6.12
• 5.6.13
• 5.6.14
• 5.6.15
• 5.6.16
• 5.6.17
• 5.6.18
• 5.6.19
• 5.6.20
• 5.6.21
• 5.6.22
• 5.6.23
• 5.6.24
• 5.6.25
• 5.6.26
• 5.6.27
• 5.6.28
• 5.6.29
• 5.6.30
• 5.6.31
• 5.6.32
• 5.7.0
• 5.7.1
• 5.7.2
• 5.7.3
• 5.7.4
• 5.7.5
• 5.7.6
• 5.7.7
• 5.7.8
• 5.7.9
• 5.7.10
• 5.7.11
• 5.7.12
• 5.7.13
• 5.7.14

License

• open-source

Website

• Vendor: https://www.oracle.com

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

Video

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.1
VulDB Meta Temp Score: 5.9

VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.0
NVD Vector: 🔍

CVSSv2info

AV	AC	Au	C	I	A
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳

Vector	Complexity	Authentication	Confidentiality	Integrity	Availability
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock

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

NVD Base Score: 🔍

Exploitinginfo

Class: Race condition
CWE: CWE-362
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: Dawid Golunski
Programming Language: 🔍
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Nessus ID: 96812
Nessus Name: CentOS 6 : mysql (CESA-2017:0184)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 881932
OpenVAS Name: CentOS Update for mysql CESA-2017:0184 centos6
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Exploit Delay Time: 🔍

Patch: github.com

Timelineinfo

08/10/2016 🔍
09/12/2016 +33 days 🔍
09/12/2016 +0 days 🔍
11/01/2016 +50 days 🔍
11/01/2016 +0 days 🔍
11/02/2016 +1 days 🔍
12/13/2016 +41 days 🔍
01/26/2017 +44 days 🔍
01/27/2017 +1 days 🔍
11/23/2024 +2857 days 🔍

Sourcesinfo

Vendor: oracle.com

Advisory: MySQL / MariaDB / PerconaDB - Privilege Escalation / Race Condition Exploit [CVE-2016-6663 / OCVE-2016-5616]
Researcher: Dawid Golunski
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2016-6663 (🔍)
GCVE (CVE): GCVE-0-2016-6663
GCVE (VulDB): GCVE-100-93232

OVAL: 🔍

SecurityFocus: 92911 - Oracle MySQL CVE-2016-6663 Unspecified Security Vulnerability

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

Entryinfo

Created: 11/02/2016 07:48
Updated: 11/23/2024 10:08
Changes: 11/02/2016 07:48 (76), 07/15/2019 16:41 (18), 09/29/2022 09:06 (5), 11/23/2024 10:08 (14)
Complete: 🔍
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

Want to know what is going to be exploited?

We predict KEV entries!