EmergencyEMERGENCY? Get 24/7 Help Now!

Percona responds to CVE-2016-6663 and CVE-2016-6664

 | November 2, 2016 |  Posted In: Events and Announcements, MySQL, Percona XtraDB Cluster

PREVIOUS POST
NEXT POST

CVE-2016-6663 and CVE-2016-6664Percona has addressed CVE-2016-6663 and CVE-2016-6664 in releases of Percona Server for MySQL and Percona XtraDB Cluster.

Percona is happy to announce that the following vulnerabilities are fixed in current releases of Percona Server for MySQL and Percona XtraDB Cluster:

  • CVE-2016-6663: allows 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”).
  • CVE-2016-6664: can let attackers who have gained access to mysql system user to further escalate their privileges to root user allowing them to fully compromise the system.

Users should upgrade to their relevant incremental release.

Percona Server

Percona XtraDB Cluster

Users should update as soon as is practical to ensure protection from these vulnerabilities.

Percona would like to thank Dawid Golunski (https://legalhackers.com) for disclosing this issue.

PREVIOUS POST
NEXT POST
David Busby

Information Security Architect

14 Comments

  • Your description for -6664 is totally wrong, you apparently, copy-pasted a description of a different vulnerability there

  • Just for clarity, the listed Percona Server/XtraDB Cluster versions are in fact patched, and not the most recent unpatched versions?

  • Some of us still use the old 5.1 series of Percona Server. Any chance to backport these security fixes to the old 5.1 series?

      • Thank you for your help! Unfortunately upgrade is not always an option, and not always my decision (due the tight software dependency).

        Please note MySQL 5.1 is still supported and will supported until 2020 on RHEL6 (and their derivates CentOS6, Scientific Linux 6). But the Percona Server 5.1 is lot more tuned and has more administrative features for production workload, than the original version. So I would prefer to stay on the Percona Server 5.1 instead of replacing it with the untuned distro version. As Redhat will eventually release the fixes (as source code), your security team could also use it as a patch source. I would be really helpful if the security team at least integrate the security patches released by Redhat to the Percona Server 5.1 series, and rebuild the packages.

        Thanks for your help!

        • I’ve had a response from our developers and that is that Percona Server 5.1 will move to “Customized support”, which essential is EOL unless someone pays for a release and backports. As such our recommendation is to upgrade to at least 5.5 as soon as possible.

  • The CVE-2016-6663 could also successfully executed and gain a shell with mysql user on Percona-Server-server-51-5.1.73-rel14.12.624.rhel6.x86_64 ….

  • There seems to be no change in the percona-xtradb-cluster-5.5 between version 5.5.41-25.11.1 and 5.5.41-37.0. Are we sure this has the right fix? If so that seems to suggest the fix was in place back in Sept.

Leave a Reply

 
 

Percona’s widely read Percona Database Performance blog highlights our expertise in enterprise-class software, support, consulting and managed services solutions for both MySQL® and MongoDB® across traditional and cloud-based platforms. The decades of experience represented by our consultants is found daily in numerous and relevant blog posts.

Besides specific database help, the blog also provides notices on upcoming events and webinars.
Want to get weekly updates listing the latest blog posts? Subscribe to our blog now! Submit your email address below and we’ll send you an update every Friday at 1pm ET.

No, thank you. Please do not ask me again.