Security update for mariadb (important)

This update for mariadb to 10.0.34 fixes several issues.

These security issues were fixed:

• CVE-2017-10378: Vulnerability in subcomponent: Server: Optimizer. Easily
  exploitable vulnerability allowed 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) (bsc#1064115).
• CVE-2017-10268: Vulnerability in subcomponent: Server: Replication.
  Difficult to exploit vulnerability allowed high privileged attacker with
  logon to the infrastructure where MySQL Server executes to compromise
  MySQL Server. Successful attacks of this vulnerability can result in
  unauthorized access to critical data or complete access to all MySQL
  Server accessible data (bsc#1064101).
• CVE-2018-2562: Vulnerability in the MySQL Server subcomponent: Server :
  Partition. Easily exploitable vulnerability allowed 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 as well as unauthorized update, insert or
  delete access to some of MySQL Server accessible data.
• CVE-2018-2622: Vulnerability in the MySQL Server subcomponent: Server:
  DDL. Easily exploitable vulnerability allowed 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-2640: Vulnerability in the MySQL Server subcomponent: Server:
  Optimizer. 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-2665: Vulnerability in the MySQL Server subcomponent: Server:
  Optimizer. Easily exploitable vulnerability allowed 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-2668: Vulnerability in the MySQL Server subcomponent: Server:
  Optimizer. Easily exploitable vulnerability allowed 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-2612: Vulnerability in the MySQL Server subcomponent: InnoDB.
  Easily exploitable vulnerability allowed high privileged attacker with
  network access via multiple protocols to compromise MySQL Server.
  Successful attacks of this vulnerability can result in unauthorized
  creation, deletion or modification access to critical data or all MySQL
  Server accessible data and unauthorized ability to cause a hang or
  frequently repeatable crash (complete DOS) of MySQL Server.

These non-security issues were fixed:

• Relax the required version of mariadb-errormessages to fix the update to
  MariaDB 10.2. (bsc#1072665)
• CHECK TABLE no longer returns an error when run on a CONNECT table
• ‘Undo log record is too big.’ error occurring in very narrow range of
  string lengths
• Race condition between INFORMATION_SCHEMA.INNODB_SYS_TABLESTATS and
  ALTER/DROP/TRUNCATE TABLE
• Wrong result after altering a partitioned table fixed bugs in InnoDB
  FULLTEXT INDEX
• InnoDB FTS duplicate key error * MDEV-13051: InnoDB crash after failed
  ADD INDEX and table_definition_cache eviction
• fts_create_doc_id() unnecessarily allocates 8 bytes for every inserted
  row
• IMPORT TABLESPACE may corrupt ROW_FORMAT=REDUNDANT tables

For additional changes please see
<a href=“https://kb.askmonty.org/en/mariadb-10033-changelog”>https://kb.askmonty.org/en/mariadb-10033-changelog</a> and
<a href=“https://kb.askmonty.org/en/mariadb-10034-changelog”>https://kb.askmonty.org/en/mariadb-10034-changelog</a> .