# Security update re CVE-2016-6662 **URL:** \ **Category:** Percona XtraDB Cluster 5.x\ **Created:** [September 12, 2016, 12:58pm UTC](https://forums.percona.com/t/security-update-re-cve-2016-6662/5078 "2016-09-12T12:58:24Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Rob\_Thomas](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/rob_thomas/32/7221_2.png) [@Rob\_Thomas](https://forums.percona.com/u/Rob_Thomas)\ **Post date:** [September 12, 2016, 12:58pm UTC](https://forums.percona.com/t/security-update-re-cve-2016-6662/5078/1 "2016-09-12T12:58:24Z")
We’ve just received an email (from Percona, thanks guys!) alerting us to CVE-2106-6662, and that we should be running 5.6.32-78.0 or higher Being the good peope we are, we immediately went and tried to update our Percona servers… ```auto [root@cluster-db-1 ~]# rpm -qa | grep Perc Percona-XtraDB-Cluster-server-56-5.6.30-25.16.1.el7.x86_64 Percona-XtraDB-Cluster-client-56-5.6.30-25.16.1.el7.x86_64 Percona-XtraDB-Cluster-shared-56-5.6.30-25.16.1.el7.x86_64 Percona-XtraDB-Cluster-56-5.6.30-25.16.1.el7.x86_64 Percona-XtraDB-Cluster-galera-3-3.16-1.rhel7.x86_64 Percona-XtraDB-Cluster-devel-56-5.6.30-25.16.1.el7.x86_64 [root@cluster-db-1 ~]# yum clean metadata Loaded plugins: fastestmirror Cleaning repos: base epel extras percona-release-noarch percona-release-x86_64 sensu updates 21 metadata files removed 14 sqlite files removed 0 metadata files removed [root@cluster-db-1 ~]# yum update Loaded plugins: fastestmirror base | 3.6 kB 00:00:00 epel/x86_64/metalink | 8.8 kB 00:00:00 epel | 4.3 kB 00:00:00 extras | 3.4 kB 00:00:00 percona-release-noarch | 2.4 kB 00:00:00 percona-release-x86_64 | 2.5 kB 00:00:00 sensu | 2.5 kB 00:00:00 updates | 3.4 kB 00:00:00 (1/10): base/7/x86_64/group_gz | 155 kB 00:00:00 (2/10): epel/x86_64/group_gz | 170 kB 00:00:00 (3/10): epel/x86_64/updateinfo | 622 kB 00:00:00 (4/10): percona-release-noarch/7/primary_db | 13 kB 00:00:00 (5/10): percona-release-x86_64/7/x86_64/primary_db | 332 kB 00:00:00 (6/10): extras/7/x86_64/primary_db | 160 kB 00:00:00 (7/10): sensu/x86_64/primary_db | 38 kB 00:00:00 (8/10): base/7/x86_64/primary_db | 5.3 MB 00:00:01 (9/10): epel/x86_64/primary_db | 4.2 MB 00:00:00 (10/10): updates/7/x86_64/primary_db | 7.1 MB 00:00:01 Loading mirror speeds from cached hostfile * base: mirror.steadfast.net * epel: mirror.steadfast.net * extras: mirror.steadfast.net * updates: mirror.steadfast.net No packages marked for update [root@cluster-db-1 ~]# ``` Has someone forgotten to move the new RPMs out of testing? 8) ---
**Author:** ![pavelk](https://avatars.discourse-cdn.com/v4/letter/p/bbe5ce/32.png) [@pavelk](https://forums.percona.com/u/pavelk)\ **Post date:** [September 12, 2016, 2:36pm UTC](https://forums.percona.com/t/security-update-re-cve-2016-6662/5078/2 "2016-09-12T14:36:51Z")
Hello, will be this update also available for Percona XtraDB Cluster? We are currently using latest version available 5.5.41. Is there a plan to implenet security fixes and new features also in MySQL product line 5.5? Thanks in advance Pavel ---
**Author:** ![shockwavecs](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@shockwavecs](https://forums.percona.com/u/shockwavecs)\ **Post date:** [September 12, 2016, 2:40pm UTC](https://forums.percona.com/t/security-update-re-cve-2016-6662/5078/3 "2016-09-12T14:40:51Z")
the email you received likely states on Percona Server and not XtraDB Cluster. It will come out after they give it a good testing. ---
**Author:** ![Barrett](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/barrett/32/15734_2.png) [@Barrett](https://forums.percona.com/u/Barrett)\ **Post date:** [September 13, 2016, 7:58am UTC](https://forums.percona.com/t/security-update-re-cve-2016-6662/5078/4 "2016-09-13T07:58:00Z")
Hi Pavel and Rob, shockwavecs is correct. Here is a blog post concerning the CVE-2016-6662 vulnerability: [url][https://www.percona.com/blog/2016/09/12/database-affected-cve-2016-6662/[/url]](https://www.percona.com/blog/2016/09/12/database-affected-cve-2016-6662/%5B/url%5D) The update for Percona XtraDB Cluster is planned, but not yet released. ---
**Author:** ![zoe](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/zoe/32/19787_2.png) [@zoe](https://forums.percona.com/u/zoe)\ **Post date:** [September 14, 2016, 3:00am UTC](https://forums.percona.com/t/security-update-re-cve-2016-6662/5078/5 "2016-09-14T03:00:07Z")
Hi everyone, Excuse me if this is the wrong place to ask this but following the blog post regarding the CVE-2016-6662 vulnerability, we are currently using Percona-XtraDB-Cluster-server-56-5.6.26. After checking for an update i get this output > [@](#): > > # ============================================================================================================================================================== Package Arch Version Repository Size > > Updating: > Percona-XtraDB-Cluster-56-debuginfo x86\_64 1:5.6.30-25.16.1.el7 percona-release-x86\_64 37 M > Percona-XtraDB-Cluster-client-56 x86\_64 1:5.6.30-25.16.1.el7 percona-release-x86\_64 5.4 M > Percona-XtraDB-Cluster-devel-56 x86\_64 1:5.6.30-25.16.1.el7 percona-release-x86\_64 2.1 M > Percona-XtraDB-Cluster-full-56 x86\_64 1:5.6.30-25.16.1.el7 percona-release-x86\_64 26 k > Percona-XtraDB-Cluster-galera-3 x86\_64 3.16-1.rhel7 percona-release-x86\_64 852 k > Percona-XtraDB-Cluster-galera-3-debuginfo x86\_64 3.16-1.rhel7 percona-release-x86\_64 9.7 M > Percona-XtraDB-Cluster-garbd-3 x86\_64 3.16-1.rhel7 percona-release-x86\_64 630 k > Percona-XtraDB-Cluster-server-56 x86\_64 1:5.6.30-25.16.1.el7 percona-release-x86\_64 18 M > Percona-XtraDB-Cluster-shared-56 x86\_64 1:5.6.30-25.16.1.el7 percona-release-x86\_64 615 k > Percona-XtraDB-Cluster-test-56 x86\_64 1:5.6.30-25.16.1.el7 percona-release-x86\_64 21 M > Transaction Summary Is there a guide for a safe upgrade from 5.6.26 to 5.6.30 or do i even need one? Can you provide advice on how to proceed on updating a production cluster, should i do a rolling upgrade or bring down the whole cluster before doing the update Thanks for the time Regards Zoe ---
**Author:** ![blade106](https://avatars.discourse-cdn.com/v4/letter/b/e9c0ed/32.png) [@blade106](https://forums.percona.com/u/blade106)\ **Post date:** [September 15, 2016, 1:17am UTC](https://forums.percona.com/t/security-update-re-cve-2016-6662/5078/6 "2016-09-15T01:17:39Z")
This package is still affected by the CVE bug. So you’ll have to upgrade twice. We are waiting for the fixed one (could be 5.6.30 or higher). For the upgrade, it’s pretty strait forward, but you can check if there is specific changes by looking at the MySQL changelog between 5.6.26 and 5.6.30. Then you just upgrade one node at a time, and do wait for the node to be in sync again. The best way to check this is to ```auto tail -f /var/log/mysql/mysql.log ``` and wait for the line ```auto WSREP: Shifting JOINED -> SYNCED ``` . You also have some tutorials on this very website. ---
**Author:** ![blade106](https://avatars.discourse-cdn.com/v4/letter/b/e9c0ed/32.png) [@blade106](https://forums.percona.com/u/blade106)\ **Post date:** [September 15, 2016, 2:43am UTC](https://forums.percona.com/t/security-update-re-cve-2016-6662/5078/7 "2016-09-15T02:43:12Z")
It seems that 5.6.30-25.16-2.jessie has just been set to Debian’s repository. Thanks!