The version of MariaDB installed on the remote host is prior to 10.1.30. It is, therefore, affected by multiple vulnerabilities as referenced in the mariadb-10-1-30-release-notes advisory.

  - sql/event_data_objects.cc in MariaDB before 10.1.30 and 10.2.x before 10.2.10 and Percona XtraDB Cluster     before 5.6.37-26.21-3 and 5.7.x before 5.7.19-29.22-3 allows remote authenticated users with SQL access to     bypass intended access restrictions and replicate data definition language (DDL) statements to cluster     nodes by leveraging incorrect ordering of DDL replication and ACL checking. (CVE-2017-15365)

  - Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Parser). Supported     versions that are affected are 5.5.61 and prior, 5.6.41 and prior, 5.7.23 and prior and 8.0.12 and prior.
    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. (CVE-2018-3133)

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 MariaDB database server.
The vulnerabilities are addressed by upgrading MariaDB to the new upstream version 10.1.37. Please see the MariaDB 10.1 Release Notes for further details :

  -     https://mariadb.com/kb/en/mariadb/mariadb-10127-release-     notes/
  -     https://mariadb.com/kb/en/mariadb/mariadb-10128-release-     notes/

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

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

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

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

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

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

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

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

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

The MariaDB project reports :

Fixes for the following security vulnerabilities : CVE-2017-15365

**Update to 10.1.30**

sysusers and tmpfiles added by upstream

**Release notes:**

https://mariadb.com/kb/en/library/mariadb-10130-release-notes/

**CVE's fixed:**

CVE-2017-15365

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 version of MariaDB running on the remote host is 10.2.x prior to 10.2.10. It is, therefore, affected by multiple vulnerabilities.

The remote Redhat Enterprise Linux 6 / 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2019:1258 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-mariadb102-mariadb (10.2.22),     rh-mariadb102-galera (25.3.25).

    Security Fix(es):

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

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

    * mariadb: Replication in sql/event_data_objects.cc occurs before ACL checks (CVE-2017-15365)

    * mysql: Server: Partition unspecified vulnerability (CPU Jan 2018) (CVE-2018-2562)

    * mysql: InnoDB unspecified vulnerability (CPU Jan 2018) (CVE-2018-2612)

    * mysql: Server: DDL unspecified vulnerability (CPU Jan 2018) (CVE-2018-2622)

    * mysql: Server: Optimizer multiple unspecified vulnerabilities (CPU Jan 2018) (CVE-2018-2640,     CVE-2018-2665, CVE-2018-2668)

    * mysql: Server: Replication unspecified vulnerability (CPU Apr 2018) (CVE-2018-2755)

    * mysql: InnoDB multiple unspecified vulnerabilities (CPU Apr 2018) (CVE-2018-2759, CVE-2018-2766,     CVE-2018-2777, CVE-2018-2782, CVE-2018-2784, CVE-2018-2786, CVE-2018-2787, CVE-2018-2810, CVE-2018-2819)

    * mysql: Client programs unspecified vulnerability (CPU Apr 2018) (CVE-2018-2761)

    * mysql: Server: Locking unspecified vulnerability (CPU Apr 2018) (CVE-2018-2771)

    * mysql: Server: Optimizer unspecified vulnerability (CPU Apr 2018) (CVE-2018-2781)

    * mysql: Server: DDL multiple unspecified vulnerabilities (CPU Apr 2018) (CVE-2018-2813, CVE-2018-2817)

    * mysql: MyISAM unspecified vulnerability (CPU Jul 2018) (CVE-2018-3058)

    * mysql: InnoDB multiple unspecified vulnerabilities (CPU Jul 2018) (CVE-2018-3060, CVE-2018-3064)

    * mysql: Server: Security: Privileges unspecified vulnerability (CPU Jul 2018) (CVE-2018-3063)

    * mysql: Client programs unspecified vulnerability (CPU Jul 2018) (CVE-2018-3081)

    * mysql: Server: Parser unspecified vulnerability (CPU Oct 2018) (CVE-2018-3133)

    * mysql: InnoDB multiple unspecified vulnerabilities (CPU Oct 2018) (CVE-2018-3143, CVE-2018-3156,     CVE-2018-3162, CVE-2018-3173, CVE-2018-3185, CVE-2018-3200, CVE-2018-3251, CVE-2018-3277, CVE-2018-3284)

    * mysql: Server: Storage Engines unspecified vulnerability (CPU Oct 2018) (CVE-2018-3282)

    * mysql: Server: Parser unspecified vulnerability (CPU Jan 2019) (CVE-2019-2455)

    * mysql: Server: Connection Handling unspecified vulnerability (CPU Jan 2019) (CVE-2019-2503)

    * mysql: InnoDB unspecified vulnerability (CPU Jan 2019) (CVE-2019-2510)

    * mysql: Server: DDL unspecified vulnerability (CPU Jan 2019) (CVE-2019-2537)

    * mysql: Server: Options unspecified vulnerability (CPU Jul 2018) (CVE-2018-3066)

    * mysql: Init script calling kill with root privileges using pid from pidfile owned by mysql user (CPU Oct     2018) (CVE-2018-3174)

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

    Bug Fix(es):

    * SELinux blocks working in /tmp directory for wsrep_recover_position function (BZ#1701252)

    * mysql faces a bug which prevents bacula from functioning (BZ#1701254)

    * GSSAPI module build fix - backport request (BZ#1701257)

    * Deadlock in RNG initialization in the FIPS mode on some circumstances (BZ#1701258)

    * Use appropriate version of Galera (BZ#1704162)

    * Encountered WSREP: BF lock wait long for trx MariaDB 10.2.8 (BZ#1709233)

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.

ID	Name	Product	Family	Published	Updated	Severity
167856	MariaDB 10.1.0 < 10.1.30 Multiple Vulnerabilities	Nessus	Databases	11/18/2022	11/18/2022	high
119040	Debian DSA-4341-1 : mariadb-10.1 - security update	Nessus	Debian Local Security Checks	11/20/2018	7/22/2024	high
105451	FreeBSD : MariaDB -- unspecified vulnerability (b7d89082-e7c0-11e7-ac58-b499baebfeaf)	Nessus	FreeBSD Local Security Checks	12/26/2017	1/4/2021	high
106274	Fedora 26 : 3:mariadb (2018-0d6a80f496)	Nessus	Fedora Local Security Checks	1/24/2018	1/6/2021	high
105077	MariaDB 10.2.x < 10.2.10 Multiple Vulnerabilities	Nessus	Databases	12/7/2017	11/18/2022	high
194143	RHEL 6 / 7 : rh-mariadb102-mariadb and rh-mariadb102-galera (RHSA-2019:1258)	Nessus	Red Hat Local Security Checks	4/28/2024	11/6/2024	high

Detections

Analytics

Plugins Search

high

high

high

high

high

high