Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1524234 - (CVE-2017-15365) CVE-2017-15365 mariadb: Replication in sql/event_data_objects.cc occurs before ACL checks
CVE-2017-15365 mariadb: Replication in sql/event_data_objects.cc occurs befor...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20171006,repor...
: Security
Depends On: 1524767 1558264 1558265 1524235 1527365
Blocks: 1523473
  Show dependency treegraph
 
Reported: 2017-12-10 20:56 EST by Sam Fowler
Modified: 2018-03-19 19:12 EDT (History)
23 users (show)

See Also:
Fixed In Version: mariadb 10.2.10, mariadb 10.1.30
Doc Type: If docs needed, set a value
Doc Text:
It was discovered that MariaDB could replicate certain data definition language (DDL) commands to other cluster nodes despite an access control check failure. A user with an SQL access to the server could possibly use this flaw to perform database modification on certain cluster nodes without having privileges to perform such changes.
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sam Fowler 2017-12-10 20:56:19 EST
MariaDB have noted in their release notes that reserved CVE-2017-15365 has been fixed in version 10.2.10[1], however they have not described how or what the vulnerability was. This CVE is also mentioned to affect Percona[2] with the fix is described as:

"Added access checks for DDL commands to make sure they do not get replicated if they failed without proper permissions"

A comparison with the MariaDB 10.2.10 changelog[3] and Percona description finds this commit[4], which seems a likely candidate for both describing and fixing the vulnerability.
The vulnerable code block in sql/event_data_objects.cc is also present in version 10.1, suggesting that it is also affected.

[0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15365
[1] https://mariadb.com/kb/en/library/mariadb-10210-release-notes/
[2] https://www.percona.com/doc/percona-xtradb-cluster/LATEST/release-notes/Percona-XtraDB-Cluster-5.7.19-29.22-3.html
[3] https://mariadb.com/kb/en/library/mariadb-10210-changelog/
[4] https://github.com/MariaDB/server/commit/0b5a5258abbeaf8a0c3a18c7e753699787fdf46e
Comment 1 Sam Fowler 2017-12-10 20:57:06 EST
Created mariadb tracking bugs for this issue:

Affects: fedora-all [bug 1524235]
Comment 2 Sam Fowler 2017-12-11 20:50:04 EST
Created mariadb tracking bugs for this issue:

Affects: openstack-rdo [bug 1524767]
Comment 5 Michal Schorm 2018-02-07 22:36:52 EST
Hi, upstream says on https://mariadb.com/kb/en/library/security/ that the issue has been fixed in both MariaDB 10.2.10, MariaDB 10.1.30.

There are no older versions present in Fedora.
Can I just close the Fedora bug, or do we need more complicate fix on downstream side?
Comment 6 Michal Schorm 2018-02-07 22:39:12 EST
Yeah, I'm so blind I can't even read my own notes.

The Fedora bug was left open till 10.2.10 released in F27.
I had long long troubles releasing that (and 10.2.12) update, and I forgot to add it to it as solved.

Note You need to log in before you can comment on or make changes to this bug.