CVE-2016-6663: Race Condition

Published Dec 13, 2016
·
Updated

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 mycopystat by REPAIR TABLE to repair a MyISAM table.

Affected Software

13 affected components
Oracle MySQL>=5.5.0<=5.5.52
Oracle MySQL>=5.6.0<=5.6.33
Oracle MySQL>=5.7.0<=5.7.15
Percona Percona Server>=5.5<5.5.51-38.2
Percona Percona Server>=5.6<5.6.32-78.1
Percona Percona Server>=5.7<5.7.14-8
Percona XtraDB Cluster>=5.5<5.5.41-37.0
Percona XtraDB Cluster>=5.6<5.6.32-25.17
Percona XtraDB Cluster>=5.7<5.7.14-26.17
MariaDB MariaDB>=5.5.20<5.5.52
MariaDB MariaDB>=10.0.0<10.0.28
MariaDB MariaDB>=10.1.0<10.1.18
Oracle MySQL=8.0

Event History

Dec 13, 2016
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2016-6663?

CVE-2016-6663 has been assigned a medium severity level due to its potential impact on system integrity.

2

How do I fix CVE-2016-6663?

To fix CVE-2016-6663, upgrade MySQL to versions 5.5.52, 5.6.33, 5.7.15, or 8.0.1, or apply the relevant patches.

3

Which versions are affected by CVE-2016-6663?

CVE-2016-6663 affects multiple MySQL versions, including 5.5 before 5.5.52, 5.6 before 5.6.33, and various versions of MariaDB and Percona Server.

4

What are the potential impacts of CVE-2016-6663?

The potential impacts of CVE-2016-6663 include data corruption and inconsistent database operations due to a race condition.

5

Is there a workaround for CVE-2016-6663?

There are no known effective workarounds for CVE-2016-6663, so it is recommended to apply patches or upgrade to safer versions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203