Several issues have been discovered in the MariaDB database server.
The vulnerabilities are addressed by upgrading MariaDB to the new upstream version 10.0.29. Please see the MariaDB 10.0 Release Notes for further details :

  -     https://mariadb.com/kb/en/mariadb/mariadb-10029-release-     notes/

**Rebase to 10.1.24**

Plugin oqgraph enabled Plugin jemalloc enabled Sphinx engine enabled Build dependecies Bison and Libarchive added, others corrected Disabling Mroonga engine for i686 architecture, as it is not supported by MariaDB

**Removed patches: (fixed by upstream)**

Patch5: %{pkgnamepatch}-file-contents.patch Patch14:
%{pkgnamepatch}-example-config-files.patch Patch31:
%{pkgnamepatch}-string-overflow.patch Patch32:
%{pkgnamepatch}-basedir.patch Patch41:
%{pkgnamepatch}-galera-new-cluster-help.patch

**CVEs fix**

CVE-2017-3313 CVE-2017-3308 CVE-2017-3309 CVE-2017-3453 CVE-2017-3456 CVE-2017-3464

**Testsuite**

Enabled '--big-test' option for the testsuite Disabled '--skip-rpl' option for the testsuite = replication tests enabled

**Warning**

Some Spider tests started to fail, the engine can be probabbly unsafe now.

**Aditional bugs solved:**

#1459671: mariadb fails to start with tokudb; jemalloc not correctly enabled

----

**Rebase to 10.1.24**

Plugin oqgraph enabled Plugin jemalloc enabled Sphinx engine enabled Build dependecies Bison and Libarchive added, others corrected Disabling Mroonga engine for i686 architecture, as it is not supported by MariaDB

**Removed patches: (fixed by upstream)**

Patch5: %{pkgnamepatch}-file-contents.patch Patch14:
%{pkgnamepatch}-example-config-files.patch Patch31:
%{pkgnamepatch}-string-overflow.patch Patch32:
%{pkgnamepatch}-basedir.patch Patch41:
%{pkgnamepatch}-galera-new-cluster-help.patch

**CVEs fix**

CVE-2017-3313 CVE-2017-3308 CVE-2017-3309 CVE-2017-3453 CVE-2017-3456 CVE-2017-3464

**Testsuite**

Enabled '--big-test' option for the testsuite Disabled '--skip-rpl' option for the testsuite = replication tests enabled

**Warning**

Some Spider tests started to fail, the engine can be probabbly unsafe now.

**Aditional bugs solved:**

#1459671: mariadb fails to start with tokudb; jemalloc not correctly enabled

----

**Rebase to 10.1.24** Plugin oqgraph enabled Plugin jemalloc enabled Sphinx engine enabled Build dependecies Bison and Libarchive added, others corrected Disabling Mroonga engine for i686 architecture, as it is not supported by MariaDB

**Removed patches: (fixed by upstream)**

Patch5: %{pkgnamepatch}-file-contents.patch Patch14:
%{pkgnamepatch}-example-config-files.patch Patch31:
%{pkgnamepatch}-string-overflow.patch Patch32:
%{pkgnamepatch}-basedir.patch Patch41:
%{pkgnamepatch}-galera-new-cluster-help.patch

**CVEs fix**

CVE-2017-3313 CVE-2017-3308 CVE-2017-3309 CVE-2017-3453 CVE-2017-3456 CVE-2017-3464

**Testsuite**

Enabled '--big-test' option for the testsuite Disabled '--skip-rpl' option for the testsuite = replication tests enabled

**Warning**

Some Spider tests started to fail, the engine can be probabbly unsafe now.

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote Redhat Enterprise Linux 6 / 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2017:2886 advisory.

    MySQL is a multi-user, multi-threaded SQL database server. It consists of the MySQL server daemon, mysqld,     and many client programs.

    The following packages have been upgraded to a later upstream version: rh-mysql57-mysql (5.7.19).

    Security Fix(es):

    * An integer overflow flaw leading to a buffer overflow was found in the way MySQL parsed connection     handshake packets. An unauthenticated remote attacker with access to the MySQL port could use this flaw to     crash the mysqld daemon. (CVE-2017-3599)

    * It was discovered that the mysql and mysqldump tools did not correctly handle database and table names     containing newline characters. A database user with privileges to create databases or tables could cause     the mysql command to execute arbitrary shell or SQL commands while restoring database backup created using     the mysqldump tool. (CVE-2016-5483, CVE-2017-3600)

    * It was discovered that the mysqld_safe script honored the ledir option value set in a MySQL     configuration file. A user able to modify one of the MySQL configuration files could use this flaw to     escalate their privileges to root. (CVE-2017-3291)

    * Multiple flaws were found in the way the mysqld_safe script handled creation of error log file. The     mysql operating system user could use these flaws to escalate their privileges to root. (CVE-2017-3312)

    * This update fixes several vulnerabilities in the MySQL database server. Information about these flaws     can be found on the Oracle Critical Patch Update Advisory pages listed in the References section.
    (CVE-2016-8327, CVE-2017-3238, CVE-2017-3244, CVE-2017-3251, CVE-2017-3256, CVE-2017-3257, CVE-2017-3258,     CVE-2017-3273, CVE-2017-3308, CVE-2017-3309, CVE-2017-3313, CVE-2017-3317, CVE-2017-3318, CVE-2017-3319,     CVE-2017-3320, CVE-2017-3331, CVE-2017-3450, CVE-2017-3453, CVE-2017-3454, CVE-2017-3455, CVE-2017-3456,     CVE-2017-3457, CVE-2017-3458, CVE-2017-3459, CVE-2017-3460, CVE-2017-3461, CVE-2017-3462, CVE-2017-3463,     CVE-2017-3464, CVE-2017-3465, CVE-2017-3467, CVE-2017-3468, CVE-2017-3529, CVE-2017-3633, CVE-2017-3634,     CVE-2017-3637, CVE-2017-3638, CVE-2017-3639, CVE-2017-3640, CVE-2017-3641, CVE-2017-3642, CVE-2017-3643,     CVE-2017-3644, CVE-2017-3645, CVE-2017-3646, CVE-2017-3647, CVE-2017-3648, CVE-2017-3649, CVE-2017-3650,     CVE-2017-3651, CVE-2017-3652, CVE-2017-3653)

    Bug Fix(es):

    * Prior to this update, the scl macros were not set for the rh-mysql57-mysqld@.service file, which     consequently made the service file unusable. This bug has been fixed, and rh-mysql57-mysqld@.service now     works as expected. (BZ#1452511)

    * Previously, the md5() function was blocked by MySQL in FIPS mode because the MD5 hash algorithm is     considered insecure. Consequently, the mysqld daemon failed with error messages when FIPS mode was     enabled. With this update, md5() is allowed in FIPS mode for non-security operations. Note that users are     able to use md5() for security purposes but such usage is not supported by Red Hat. (BZ#1452514)

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Several issues have been discovered in the MySQL database server. The vulnerabilities are addressed by upgrading MySQL to the new upstream version 5.5.54, which includes additional changes, such as performance improvements, bug fixes, new features, and possibly incompatible changes. Please see the MySQL 5.5 Release Notes and Oracle's Critical Patch Update advisory for further details :

  -     https://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5
    -54.html
  -     http://www.oracle.com/technetwork/security-advisory/cpuj     an2017-2881727.html

An update for mariadb is now available for Red Hat Enterprise Linux 7.

Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

MariaDB is a multi-user, multi-threaded SQL database server that is binary compatible with MySQL.

The following packages have been upgraded to a later upstream version:
mariadb (5.5.56). (BZ#1458933)

Security Fix(es) :

* It was discovered that the mysql and mysqldump tools did not correctly handle database and table names containing newline characters. A database user with privileges to create databases or tables could cause the mysql command to execute arbitrary shell or SQL commands while restoring database backup created using the mysqldump tool. (CVE-2016-5483, CVE-2017-3600)

* A flaw was found in the way the mysqld_safe script handled creation of error log file. The mysql operating system user could use this flaw to escalate their privileges to root. (CVE-2016-5617, CVE-2016-6664)

* Multiple flaws were found in the way the MySQL init script handled initialization of the database data directory and permission setting on the error log file. The mysql operating system user could use these flaws to escalate their privileges to root. (CVE-2017-3265)

* It was discovered that the mysqld_safe script honored the ledir option value set in a MySQL configuration file. A user able to modify one of the MySQL configuration files could use this flaw to escalate their privileges to root. (CVE-2017-3291)

* Multiple flaws were found in the way the mysqld_safe script handled creation of error log file. The mysql operating system user could use these flaws to escalate their privileges to root. (CVE-2017-3312)

* A flaw was found in the way MySQL client library (libmysqlclient) handled prepared statements when server connection was lost. A malicious server or a man-in-the-middle attacker could possibly use this flaw to crash an application using libmysqlclient.
(CVE-2017-3302)

* This update fixes several vulnerabilities in the MariaDB database server. Information about these flaws can be found on the Oracle Critical Patch Update Advisory page, listed in the References section.
(CVE-2017-3238, CVE-2017-3243, CVE-2017-3244, CVE-2017-3258, CVE-2017-3308, CVE-2017-3309, CVE-2017-3313, CVE-2017-3317, CVE-2017-3318, CVE-2017-3453, CVE-2017-3456, CVE-2017-3464)

Additional Changes :

For detailed information on changes in this release, see the Red Hat Enterprise Linux 7.4 Release Notes linked from the References section.

The remote Redhat Enterprise Linux 6 / 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2018:0574 advisory.

    MariaDB is a multi-user, multi-threaded SQL database server. For all practical purposes, MariaDB is     binary-compatible with MySQL.

    The following packages have been upgraded to a later upstream version: rh-mariadb101-mariadb (10.1.29).
    (BZ#1463417, BZ#1517327)

    Security Fix(es):

    * mysql: insecure error log file handling in mysqld_safe (CPU Oct 2016) (CVE-2016-5617, CVE-2016-6664)

    * mysql: Server: Optimizer unspecified vulnerability (CPU Jan 2017) (CVE-2017-3238)

    * mysql: Server: Charsets unspecified vulnerability (CPU Jan 2017) (CVE-2017-3243)

    * mysql: Server: DML unspecified vulnerability (CPU Jan 2017) (CVE-2017-3244)

    * mysql: Server: InnoDB unspecified vulnerability (CPU Jan 2017) (CVE-2017-3257)

    * mysql: Server: DDL unspecified vulnerability (CPU Jan 2017) (CVE-2017-3258)

    * mysql: unsafe chmod/chown use in init script (CPU Jan 2017) (CVE-2017-3265)

    * mysql: unrestricted mysqld_safe's ledir (CPU Jan 2017) (CVE-2017-3291)

    * mysql: Server: DML unspecified vulnerability (CPU Apr 2017) (CVE-2017-3308)

    * mysql: Server: Optimizer unspecified vulnerability (CPU Apr 2017) (CVE-2017-3309)

    * mysql: insecure error log file handling in mysqld_safe, incomplete CVE-2016-6664 fix (CPU Jan 2017)     (CVE-2017-3312)

    * mysql: Server: MyISAM unspecified vulnerability (CPU Jan 2017) (CVE-2017-3313)

    * mysql: Logging unspecified vulnerability (CPU Jan 2017) (CVE-2017-3317)

    * mysql: Server: Error Handling unspecified vulnerability (CPU Jan 2017) (CVE-2017-3318)

    * mysql: Server: Optimizer unspecified vulnerability (CPU Apr 2017) (CVE-2017-3453)

    * mysql: Server: DML unspecified vulnerability (CPU Apr 2017) (CVE-2017-3456)

    * mysql: Server: DDL unspecified vulnerability (CPU Apr 2017) (CVE-2017-3464)

    * mysql: Client programs unspecified vulnerability (CPU Jul 2017) (CVE-2017-3636)

    * mysql: Server: DML unspecified vulnerability (CPU Jul 2017) (CVE-2017-3641)

    * mysql: Server: Replication unspecified vulnerability (CPU Oct 2017) (CVE-2017-10268)

    * mysql: Server: InnoDB unspecified vulnerability (CPU Oct 2017) (CVE-2017-10286)

    * mysql: Server: Optimizer unspecified vulnerability (CPU Oct 2017) (CVE-2017-10378)

    * mysql: Client programs unspecified vulnerability (CPU Oct 2017) (CVE-2017-10379)

    * mysql: Server: DDL unspecified vulnerability (CPU Oct 2017) (CVE-2017-10384)

    * mysql: prepared statement handle use-after-free after disconnect (CVE-2017-3302)

    * mysql: Server: DDL unspecified vulnerability (CPU Jul 2017) (CVE-2017-3653)

    For more details about the security issue(s), including the impact, a CVSS score, and other related     information, refer to the CVE page(s) listed in the References section.

    Bug Fix(es):

    * Previously, a syntax error in the Galera Arbitrator SysV init script prevented the garbd daemon from     being started when the SysV init script was used. With this update, the definition of the main daemon     binary in the SysV init script has been fixed, and the described problem no longer occurs. (BZ#1466473)

    * Prior to this update, the scl macros were not set for the rh-mariadb101-mariadb@.service file, which     consequently made the service file unusable. This bug has been fixed, and rh-mariadb101-mariadb@.service     now works as expected. (BZ#1485995)

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 6 / 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2018:0279 advisory.

    MariaDB is a multi-user, multi-threaded SQL database server. For all practical purposes, MariaDB is     binary-compatible with MySQL.

    The following packages have been upgraded to a later upstream version: rh-mariadb100-mariadb (10.0.33).

    Security Fix(es):

    * A flaw was found in the way the mysqld_safe script handled creation of error log file. The mysql     operating system user could use this flaw to escalate their privileges to root. (CVE-2016-5617,     CVE-2016-6664)

    * Multiple flaws were found in the way the MySQL init script handled initialization of the database data     directory and permission setting on the error log file. The mysql operating system user could use these     flaws to escalate their privileges to root. (CVE-2017-3265)

    * It was discovered that the mysqld_safe script honored the ledir option value set in a MySQL     configuration file. A user able to modify one of the MySQL configuration files could use this flaw to     escalate their privileges to root. (CVE-2017-3291)

    * Multiple flaws were found in the way the mysqld_safe script handled creation of error log file. The     mysql operating system user could use these flaws to escalate their privileges to root. (CVE-2017-3312)

    * A flaw was found in the way MySQL client library (libmysqlclient) handled prepared statements when     server connection was lost. A malicious server or a man-in-the-middle attacker could possibly use this     flaw to crash an application using libmysqlclient. (CVE-2017-3302)

    * This update fixes several vulnerabilities in the MariaDB database server. Information about these flaws     can be found on the Oracle Critical Patch Update Advisory pages listed in the References section.
    (CVE-2017-3238, CVE-2017-3243, CVE-2017-3244, CVE-2017-3257, CVE-2017-3258, CVE-2017-3308, CVE-2017-3309,     CVE-2017-3313, CVE-2017-3317, CVE-2017-3318, CVE-2017-3453, CVE-2017-3456, CVE-2017-3464, CVE-2017-3636,     CVE-2017-3641, CVE-2017-3653, CVE-2017-10268, CVE-2017-10286, CVE-2017-10378, CVE-2017-10379,     CVE-2017-10384)

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of MariaDB installed on the remote host is prior to 5.5.54. It is, therefore, affected by multiple vulnerabilities as referenced in the 5.5.54 advisory.

  - mysqld_safe in Oracle MySQL through 5.5.51, 5.6.x through 5.6.32, and 5.7.x through 5.7.14; MariaDB;
    Percona Server before 5.5.51-38.2, 5.6.x before 5.6.32-78-1, and 5.7.x before 5.7.14-8; and Percona XtraDB     Cluster before 5.5.41-37.0, 5.6.x before 5.6.32-25.17, and 5.7.x before 5.7.14-26.17, when using file-     based logging, allows local users with access to the mysql account to gain root privileges via a symlink     attack on error logs and possibly other files. (CVE-2016-6664)

  - Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Optimizer). Supported     versions that are affected are 5.5.53 and earlier, 5.6.34 and earlier and 5.7.16 and earlier. Easily     exploitable vulnerability allows low privileged attacker with network access via multiple protocols to     compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to     cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS v3.0 Base Score 6.5     (Availability impacts). (CVE-2017-3238)

  - Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Charsets). Supported     versions that are affected are 5.5.53 and earlier. Difficult to exploit vulnerability allows high     privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful     attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable     crash (complete DOS) of MySQL Server. CVSS v3.0 Base Score 4.4 (Availability impacts). (CVE-2017-3243)

  - Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: DML). Supported     versions that are affected are 5.5.53 and earlier, 5.6.34 and earlier and 5.7.16 and earlier. Easily     exploitable vulnerability allows low privileged attacker with network access via multiple protocols to     compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to     cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS v3.0 Base Score 6.5     (Availability impacts). (CVE-2017-3244)

  - Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: DDL). Supported     versions that are affected are 5.5.53 and earlier, 5.6.34 and earlier and 5.7.16 and earlier. Easily     exploitable vulnerability allows low privileged attacker with network access via multiple protocols to     compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to     cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS v3.0 Base Score 6.5     (Availability impacts). (CVE-2017-3258)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

This mariadb version update to 10.0.29 fixes the following issues :

  - CVE-2017-3318: unspecified vulnerability affecting Error     Handling (bsc#1020896)

  - CVE-2017-3317: unspecified vulnerability affecting     Logging (bsc#1020894)

  - CVE-2017-3312: insecure error log file handling in     mysqld_safe, incomplete CVE-2016-6664 (bsc#1020873)

  - CVE-2017-3291: unrestricted mysqld_safe's ledir     (bsc#1020884)

  - CVE-2017-3265: unsafe chmod/chown use in init script     (bsc#1020885)

  - CVE-2017-3258: unspecified vulnerability in the DDL     component (bsc#1020875)

  - CVE-2017-3257: unspecified vulnerability affecting     InnoDB (bsc#1020878)

  - CVE-2017-3244: unspecified vulnerability affecing the     DML component (bsc#1020877)

  - CVE-2017-3243: unspecified vulnerability affecting the     Charsets component (bsc#1020891)

  - CVE-2017-3238: unspecified vulnerability affecting the     Optimizer component (bsc#1020882)

  - CVE-2016-6664: Root Privilege Escalation (bsc#1008253)

  - Applications using the client library for MySQL     (libmysqlclient.so) had a use-after-free issue that     could cause the applications to crash (bsc#1022428)

  - notable changes :

  - XtraDB updated to 5.6.34-79.1

  - TokuDB updated to 5.6.34-79.1

  - Innodb updated to 5.6.35

  - Performance Schema updated to 5.6.35 Release notes and     changelog :

  - https://kb.askmonty.org/en/mariadb-10029-release-notes

  - https://kb.askmonty.org/en/mariadb-10029-changelog

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

This mariadb version update to 10.0.29 fixes the following issues :

  - CVE-2017-3318: unspecified vulnerability affecting Error     Handling (bsc#1020896)

  - CVE-2017-3317: unspecified vulnerability affecting     Logging (bsc#1020894)

  - CVE-2017-3312: insecure error log file handling in     mysqld_safe, incomplete CVE-2016-6664 (bsc#1020873)

  - CVE-2017-3291: unrestricted mysqld_safe's ledir     (bsc#1020884)

  - CVE-2017-3265: unsafe chmod/chown use in init script     (bsc#1020885)

  - CVE-2017-3258: unspecified vulnerability in the DDL     component (bsc#1020875)

  - CVE-2017-3257: unspecified vulnerability affecting     InnoDB (bsc#1020878)

  - CVE-2017-3244: unspecified vulnerability affecing the     DML component (bsc#1020877)

  - CVE-2017-3243: unspecified vulnerability affecting the     Charsets component (bsc#1020891)

  - CVE-2017-3238: unspecified vulnerability affecting the     Optimizer component (bsc#1020882)

  - CVE-2016-6664: Root Privilege Escalation (bsc#1008253)

  - Applications using the client library for MySQL     (libmysqlclient.so) had a use-after-free issue that     could cause the applications to crash (bsc#1022428)

  - notable changes :

  - XtraDB updated to 5.6.34-79.1

  - TokuDB updated to 5.6.34-79.1

  - Innodb updated to 5.6.35

  - Performance Schema updated to 5.6.35

Release notes and changelog :

  - https://kb.askmonty.org/en/mariadb-10029-release-notes

  - https://kb.askmonty.org/en/mariadb-10029-changelog

This update was imported from the SUSE:SLE-12-SP1:Update update project.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
96669	Debian DSA-3770-1 : mariadb-10.0 - security update	Nessus	Debian Local Security Checks	2017/1/23	2026/1/5	high
101568	Fedora 26 : 3:mariadb (2017-09dd8907da)	Nessus	Fedora Local Security Checks	2017/7/17	2025/12/10	medium
194054	RHEL 6 / 7 : rh-mysql57-mysql (RHSA-2017:2886)	Nessus	Red Hat Local Security Checks	2024/4/27	2025/8/29	medium
96638	Debian DSA-3767-1 : mysql-5.5 - security update	Nessus	Debian Local Security Checks	2017/1/20	2026/1/5	medium
102755	CentOS 7 : mariadb (CESA-2017:2192)	Nessus	CentOS Local Security Checks	2017/8/25	2025/11/25	high
194041	RHEL 6 / 7 : rh-mariadb101-mariadb and rh-mariadb101-galera (RHSA-2018:0574)	Nessus	Red Hat Local Security Checks	2024/4/27	2025/9/1	high
210322	RHEL 6 / 7 : rh-mariadb100-mariadb (RHSA-2018:0279)	Nessus	Red Hat Local Security Checks	2024/11/5	2025/9/1	high
289860	MiracleLinux 4 : rh-mysql57-mysql-5.7.19-6.AXS4 (AXSA:2017-2329:01)	Nessus	Miracle Linux Local Security Checks	2026/1/16	2026/2/9	high
96489	MariaDB 5.5.0 < 5.5.54 Multiple Vulnerabilities	Nessus	Databases	2017/1/13	2026/1/29	high
97064	SUSE SLED12 / SLES12 Security Update : mariadb (SUSE-SU-2017:0412-1)	Nessus	SuSE Local Security Checks	2017/2/8	2026/1/1	high
97277	openSUSE Security Update : mariadb (openSUSE-2017-257)	Nessus	SuSE Local Security Checks	2017/2/21	2025/12/31	high

检测

插件搜索

high

medium

medium

medium

high

high

high

high

high

high

high