This update for mariadb to version 10.0.33 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) of MySQL Server (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).

These non-security issues were fixed:

- 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
- 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 details please see https://kb.askmonty.org/en/mariadb-10033-changelog

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