VDB-93231 · CVE-2016-6663 · EDB 40360

MariaDB up to 5.5.51/10.0.27/10.1.17 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 MariaDB up to 5.5.51/10.0.27/10.1.17. It has been classified as problematic. The affected element is an unknown function. Performing a manipulation results in race condition. This vulnerability is identified as CVE-2016-6663. The attack is only possible with local access. Additionally, an exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as problematic has been found in MariaDB up to 5.5.51/10.0.27/10.1.17 (Database Software). This affects an unknown code block. The manipulation with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability.

The bug was discovered 09/12/2016. The weakness was released 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). It is possible to read the advisory at seclists.org. The public release was coordinated with the project team. This vulnerability is uniquely identified as CVE-2016-6663 since 08/10/2016. The exploitability is told to be easy. Attacking locally is a requirement. The requirement for exploitation is a 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. The exploit is shared for download 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)).

Upgrading to version 5.5.52, 10.0.28 or 10.1.18 eliminates this vulnerability. A possible mitigation has been published 4 months after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Exploit-DB (40360), Tenable (96812) and SecurityFocus (BID 92911†). Entries connected to this vulnerability are available at VDB-4597, VDB-4598, VDB-20222 and VDB-79101. Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

Database Software

Name

MariaDB

Version

License

open-source

CPE 2.3info

CPE 2.2info

Video

Open Video | Show More Videos

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: Upgrade
Status: 🔍

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

Upgrade: MariaDB 5.5.52/10.0.28/10.1.18
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/12/2016 +40 days 🔍
01/26/2017 +44 days 🔍
01/27/2017 +1 days 🔍
11/23/2024 +2857 days 🔍