mysqld_safe in Oracle MySQL through 5.5.51, 5.6.x through 5.6.32, and 5.7.x through 5.7.14; MariaDB; Percona Server before 5.5.51-38.2, 5.6.x before 5.6.32-78-1, and 5.7.x before 5.7.14-8; and Percona XtraDB Cluster before 5.5.41-37.0, 5.6.x before 5.6.32-25.17, and 5.7.x before 5.7.14-26.17, when using file-based logging, allows local users with access to the mysql account to gain root privileges via a symlink attack on error logs and possibly other files.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HMariaDB
APPMariadb5.5.0 – 5.5.54 (bez)10.0.0 – 10.0.29 (bez)10.1.0 – 10.1.21 (bez)Oracle MySQL
APPOracle5.5.0 – 5.5.515.6.0 – 5.6.325.7.0 – 5.7.14Percona Server
APPPercona5.5 – 5.5.51-38.2 (bez)5.6 – 5.6.32-78.1 (bez)5.7 – 5.7.14-8 (bez)Percona Xtradb Cluster
APPPercona5.5 – 5.5.41-37.0 (bez)5.6 – 5.6.32-25.17 (bez)5.7 – 5.7.14-26.17 (bez)
Related vulnerabilities
MariaDB: command injection przez wsrep_notify_cmd w nazwie węzła Galera
MariaDB v10.5 — RCE przez UDF w plikach współdzielonych (disputed)
A flaw was found in the mysql-wsrep component of mariadb. Lack of input sanitization in `wsrep_sst_method` all...
An issue was discovered in the MongoDB Simple LDAP plugin through 2020-10-02 for Percona Server when using the...
In SQLite through 3.31.1, the ALTER TABLE implementation has a use-after-free, as demonstrated by an ORDER BY ...