Skip to content
OpenAdvisories
Unscored SUSE-SU-2016:1620-1 25 CVEs

Security update for mariadb

Published Jun 17, 2016 · Updated Feb 4, 2026

Summary

mariadb was updated to version 10.0.25 to fix 25 security issues.

These security issues were fixed:
- CVE-2016-0505: Unspecified vulnerability allowed remote authenticated users to affect availability via unknown vectors related to Options (bsc#980904).
- CVE-2016-0546: Unspecified vulnerability allowed local users to affect confidentiality, integrity, and availability via unknown vectors related to Client (bsc#980904).
- CVE-2016-0596: Unspecified vulnerability allowed remote authenticated users to affect availability via vectors related to DML (bsc#980904).
- CVE-2016-0597: Unspecified vulnerability allowed remote authenticated users to affect availability via unknown vectors related to Optimizer (bsc#980904).
- CVE-2016-0598: Unspecified vulnerability allowed remote authenticated users to affect availability via vectors related to DML (bsc#980904).
- CVE-2016-0600: Unspecified vulnerability allowed remote authenticated users to affect availability via unknown vectors related to InnoDB (bsc#980904).
- CVE-2016-0606: Unspecified vulnerability allowed remote authenticated users to affect integrity via unknown vectors related to encryption (bsc#980904).
- CVE-2016-0608: Unspecified vulnerability allowed remote authenticated users to affect availability via vectors related to UDF (bsc#980904).
- CVE-2016-0609: Unspecified vulnerability allowed remote authenticated users to affect availability via unknown vectors related to privileges (bsc#980904).
- CVE-2016-0616: Unspecified vulnerability allowed remote authenticated users to affect availability via unknown vectors related to Optimizer (bsc#980904).
- CVE-2016-0640: Unspecified vulnerability allowed local users to affect integrity and availability via vectors related to DML (bsc#980904).
- CVE-2016-0641: Unspecified vulnerability allowed local users to affect confidentiality and availability via vectors related to MyISAM (bsc#980904).
- CVE-2016-0642: Unspecified vulnerability allowed local users to affect integrity and availability via vectors related to Federated (bsc#980904).
- CVE-2016-0643: Unspecified vulnerability allowed local users to affect confidentiality via vectors related to DML (bsc#980904).
- CVE-2016-0644: Unspecified vulnerability allowed local users to affect availability via vectors related to DDL (bsc#980904).
- CVE-2016-0646: Unspecified vulnerability allowed local users to affect availability via vectors related to DML (bsc#980904).
- CVE-2016-0647: Unspecified vulnerability allowed local users to affect availability via vectors related to FTS (bsc#980904).
- CVE-2016-0648: Unspecified vulnerability allowed local users to affect availability via vectors related to PS (bsc#980904).
- CVE-2016-0649: Unspecified vulnerability allowed local users to affect availability via vectors related to PS (bsc#980904).
- CVE-2016-0650: Unspecified vulnerability allowed local users to affect availability via vectors related to Replication (bsc#980904).
- CVE-2016-0651: Unspecified vulnerability allowed local users to affect availability via vectors related to Optimizer (bsc#980904).
- CVE-2016-0655: Unspecified vulnerability allowed local users to affect availability via vectors related to InnoDB (bsc#980904).
- CVE-2016-0666: Unspecified vulnerability allowed local users to affect availability via vectors related to Security: Privileges (bsc#980904).
- CVE-2016-0668: Unspecified vulnerability allowed local users to affect availability via vectors related to InnoDB (bsc#980904).
- CVE-2016-2047: The ssl_verify_server_cert function in sql-common/client.c did not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allowed man-in-the-middle attackers to spoof SSL servers via a '/CN=' string in a field in a certificate, as demonstrated by '/OU=/CN=bar.com/CN=foo.com (bsc#963806).

These non-security issues were fixed:
- bsc#961935: Remove the leftovers of 'openSUSE' string in the '-DWITH_COMMENT' and 'DCOMPILATION_COMMENT' options
- bsc#970287: remove ha_tokudb.so plugin and tokuft_logprint and tokuftdump binaries as TokuDB storage engine requires the jemalloc library that isn't present in SLE-12-SP1
- bsc#970295: Fix the leftovers of 'logrotate.d/mysql' string in the logrotate error message. Occurrences of this string were changed to 'logrotate.d/mariadb'
- bsc#963810: Add 'log-error' and 'secure-file-priv' configuration options
* add '/etc/my.cnf.d/error_log.conf' that specifies
'log-error = /var/log/mysql/mysqld.log'. If no path is set,
the error log is written to '/var/lib/mysql/$HOSTNAME.err',
which is not picked up by logrotate.
* add '/etc/my.cnf.d/secure_file_priv.conf' which specifies that
'LOAD DATA', 'SELECT ... INTO' and 'LOAD FILE()' will only work
with files in the directory specified by 'secure-file-priv'
option (='/var/lib/mysql-files').

Fixed packages 5

ReleasePackageFixed in
SUSE · SLES 12 SP1 Linux Enterprise Desktop 12 SP1 mariadb 10.0.25-6.1
SUSE · SLES 12 SP1 Linux Enterprise Server 12 SP1 mariadb 10.0.25-6.1
SUSE · SLES for SAP 12 SP1 Linux Enterprise Server for SAP Applications 12 SP1 mariadb 10.0.25-6.1
SUSE · SLES 12 SP1 Linux Enterprise Software Development Kit 12 SP1 mariadb 10.0.25-6.1
SUSE · SLES 12 SP1 Linux Enterprise Workstation Extension 12 SP1 mariadb 10.0.25-6.1

Vulnerabilities 25

References

  • report
    https://bugzilla.suse.com/961935
  • report
    https://bugzilla.suse.com/963806
  • report
    https://bugzilla.suse.com/963810
  • report
    https://bugzilla.suse.com/970287
  • report
    https://bugzilla.suse.com/970295
  • report
    https://bugzilla.suse.com/980904
  • web
    https://www.suse.com/security/cve/CVE-2016-0505
  • web
    https://www.suse.com/security/cve/CVE-2016-0546
  • web
    https://www.suse.com/security/cve/CVE-2016-0596
  • web
    https://www.suse.com/security/cve/CVE-2016-0597
  • web
    https://www.suse.com/security/cve/CVE-2016-0598
  • web
    https://www.suse.com/security/cve/CVE-2016-0600
  • web
    https://www.suse.com/security/cve/CVE-2016-0606
  • web
    https://www.suse.com/security/cve/CVE-2016-0608
  • web
    https://www.suse.com/security/cve/CVE-2016-0609
  • web
    https://www.suse.com/security/cve/CVE-2016-0616
  • web
    https://www.suse.com/security/cve/CVE-2016-0640
  • web
    https://www.suse.com/security/cve/CVE-2016-0641
  • web
    https://www.suse.com/security/cve/CVE-2016-0642
  • web
    https://www.suse.com/security/cve/CVE-2016-0643
  • web
    https://www.suse.com/security/cve/CVE-2016-0644
  • web
    https://www.suse.com/security/cve/CVE-2016-0646
  • web
    https://www.suse.com/security/cve/CVE-2016-0647
  • web
    https://www.suse.com/security/cve/CVE-2016-0648
  • web
    https://www.suse.com/security/cve/CVE-2016-0649
  • web
    https://www.suse.com/security/cve/CVE-2016-0650
  • web
    https://www.suse.com/security/cve/CVE-2016-0651
  • web
    https://www.suse.com/security/cve/CVE-2016-0655
  • web
    https://www.suse.com/security/cve/CVE-2016-0666
  • web
    https://www.suse.com/security/cve/CVE-2016-0668
  • web
    https://www.suse.com/security/cve/CVE-2016-2047