CVE-2016-6663 Race condition in n/a

High 7.0 Published Updated

Local attackers can exploit a race condition in REPAIR TABLE to gain elevated privileges on MySQL and MariaDB servers.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2016-6663?

CVE-2016-6663 is a high-severity vulnerability in Mariadb Mariadb, published on 13 Dec 2016. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

Race condition in Oracle MySQL before 5.5.52, 5.6.x before 5.6.33, 5.7.x before 5.7.15, and 8.x before 8.0.1; MariaDB before 5.5.52, 10.0.x before 10.0.28, and 10.1.x before 10.1.18; Percona Server before 5.5.51-38.2, 5.6.x before 5.6.32-78-1, and 5.7.x before 5.7.14-8; and Percona XtraDB Cluster before 5.5.41-37.0, 5.6.x before 5.6.32-25.17, and 5.7.x before 5.7.14-26.17 allows local users with certain permissions to gain privileges by leveraging use of my_copystat by REPAIR TABLE to repair a MyISAM table.

Weakness: CWE-362

Which versions are affected by CVE-2016-6663?

It affects 4 products.

Products include Mariadb Mariadb, Oracle Mysql, Percona Percona Server, Percona Xtradb Cluster.

How do I fix CVE-2016-6663?

Upgrade to a fixed version.

Is CVE-2016-6663 being exploited?

There is no known exploitation of CVE-2016-6663 in the wild and no public exploit code.

Public exploit code: 1 Exploit-DB entry and 1 proofs of concept on GitHub.

All Mariadb Mariadb vulnerabilities

Sources

Also known as CVE-2016-5616, GHSA-g76x-xjc6-4pgh, UBUNTU-CVE-2016-6663.

Is CVE-2016-6663 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free