**MariaDB 10.2.15**

Release notes :

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

CVEs fixed :

CVE-2018-2755 CVE-2018-2761 CVE-2018-2766 CVE-2018-2771 CVE-2018-2781 CVE-2018-2782 CVE-2018-2784 CVE-2018-2787 CVE-2018-2813 CVE-2018-2817 CVE-2018-2819 CVE-2018-2786 CVE-2018-2759 CVE-2018-2777 CVE-2018-2810

New features :

  - Now builds with lz4 support

Enhacements :

  - mysqladmin is now used to check the socket when the     daemon is starting

issues :

  - Please note, that TokuDB storage engine is being build     in a unsupported way - without jemalloc. it will remain     this way, until TokuDB is fixed to be able to build and     run with jemalloc 5 or witout jemalloc at all.

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.

An update of the mysql package has been released.

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.

The version of MySQL running on the remote host is 5.7.x prior to 5.7.22. It is, therefore, affected by multiple vulnerabilities as noted in the April 2018 Critical Patch Update advisory. Please consult the CVRF details for the applicable CVEs for additional information.

ID	Name	Product	Family	Published	Updated	Severity
120297	Fedora 28 : 3:mariadb (2018-2513b888a4)	Nessus	Fedora Local Security Checks	1/3/2019	7/8/2024	high
121940	Photon OS 2.0: Mysql PHSA-2018-2.0-0040	Nessus	PhotonOS Local Security Checks	2/7/2019	7/23/2024	medium
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
700626	MySQL 5.7.x < 5.7.22 Multiple Vulnerabilities (April 2018 CPU)	Nessus Network Monitor	Database	4/25/2019	4/25/2019	high

Detections

Analytics

Plugins Search

high

medium

high

high