mariadb: Multiple security vulnerabilities (Various CVEs)
CVE-2016-0640: MariaDB 5.5.48
CVE-2016-0641: MariaDB 5.5.48
CVE-2016-0644: MariaDB 5.5.48
CVE-2016-0646: MariaDB 5.5.48
CVE-2016-0649: MariaDB 5.5.48
CVE-2016-0650: MariaDB 5.5.48
Reference:
https://mariadb.com/kb/en/mariadb/mariadb-5548-release-notes/
CVE-2016-0647: MariaDB 5.5.49, MariaDB 10.1.14
CVE-2016-0648: MariaDB 5.5.49, MariaDB 10.1.14
CVE-2016-0666: MariaDB 5.5.49, MariaDB 10.1.14
CVE-2016-0643: MariaDB 5.5.49, MariaDB 10.1.14
CVE-2016-5444: MariaDB 5.5.49, MariaDB 10.1.14
CVE-2016-3452: MariaDB 5.5.49, MariaDB 10.1.14
Reference:
https://mariadb.com/kb/en/mariadb/mariadb-5549-release-notes/
https://mariadb.com/kb/en/mariadb/mariadb-10114-release-notes/
CVE-2016-3477: MariaDB 5.5.50, MariaDB 10.1.16
CVE-2016-3521: MariaDB 5.5.50, MariaDB 10.1.16
CVE-2016-3615: MariaDB 5.5.50, MariaDB 10.1.16
CVE-2016-5440: MariaDB 5.5.50, MariaDB 10.1.16
Reference:
https://mariadb.com/kb/en/mariadb/mariadb-5550-release-notes/
https://mariadb.com/kb/en/mariadb/mariadb-10115-release-notes/
CVE-2016-6662: MariaDB 5.5.51, MariaDB 10.1.17
Reference:
https://mariadb.com/kb/en/mariadb/mariadb-5551-release-notes/
https://jira.mariadb.org/browse/MDEV-10465
v3.3 and v3.4 should upgrade to 10.1.17
v3.2 should upgrade to 5.5.51 at least
(from redmine: issue id 6169, created on 2016-09-16, closed on 2016-10-18)
- Relations:
- child #6170 (closed)
- child #6171 (closed)
- child #6172 (closed)