Announcing Galera Cluster 5.5.52 and 5.6.33 with Galera 3.18 with fix for CVE-2016-6662

Codership is pleased to announce a new release of Galera Cluster for MySQL consisting of MySQL-wsrep 5.6.33 and Galera 3.18, wsrep API version 25.

This release incorporates all changes up to MySQL 5.5.52 and 5.6.33, including the fix for CVE-2016-6662.

Galera Cluster is now available as targeted packages and package repositories for a number of Linux distributions, including Ubuntu, Debian, Fedora, CentOS, RHEL, OpenSUSE and SLES. Obtaining packages using a package repository removes the
need to download individual files and facilitates the deployment and upgrade of Galera nodes.

This and future releases will be available from The source repositories and bug tracking are now on

New features and notable fixes in Galera replication since last binary release by Codership (3.17):

  • After a certain pattern of server restarts, an isolated node could stop attempting to reconnect to the cluster (GCF-890)
  • Galera would fail to compile with clang 3.8 (refs codership/galera#412)
  • The wsrep_desync_count variable could show a wrong value (GAL-401)

Notable bug fixes in MySQL-wsrep 5.6.33:

  • Galera would crash on startup if compiled with GCC 6 (MW-267, codership/mysql-wsrep#267)

New features, notable changes and bug fixes in Oracle MySQL 5.6.32 and 5.6.33:

  • CVE-2016-6662. An authenticated remote user could leverage the mysqld_safe script to obtain elevated local privileges
  • It was possible to write log files ending with .ini or .cnf that later could be parsed as option files. The general query log and slow query log can no longer be written to a file ending with .ini or .cnf. (Bug #24388753)
  • Privilege escalation was possible by exploiting the way REPAIR TABLE used temporary files. (Bug #24388746)
  • Multiple buffer overflows were fixed

Known issues with this release:

  • If using the Ubuntu 16.04 Xenial package, the server can not be bootstrapped using systemd. Please use the SysV init script with the ‘bootstap’ option to bootstrap the node. Note that a server that has been started that way can not be controlled via systemd and must be stopped using the SysV script. Normal server startup and shutdown is possible via systemd.

Leave a Reply

Your email address will not be published. Required fields are marked *