CVE-2016-3459: Medium severity mariadb vulnerability

Q: What is the severity of CVE-2016-3459?

CVE-2016-3459 is considered a medium severity vulnerability.

Q: How do I fix CVE-2016-3459?

To fix CVE-2016-3459, upgrade your Oracle MySQL to version 5.6.31 or later, or 5.7.13 or later, and MariaDB to version 10.0.25 or later, or 10.1.14 or later.

Q: What software is affected by CVE-2016-3459?

CVE-2016-3459 affects Oracle MySQL versions 5.6.30 and earlier, 5.7.12 and earlier, and MariaDB versions 10.0.x before 10.0.25 and 10.1.x before 10.1.14.

Q: What types of attacks can exploit CVE-2016-3459?

CVE-2016-3459 can be exploited by remote administrators to affect the availability of the database server.

Q: When was CVE-2016-3459 disclosed?

CVE-2016-3459 was disclosed in July 2016 as part of Oracle's Critical Patch Update.

Published Jul 21, 2016

Updated

Unspecified vulnerability in Oracle MySQL 5.6.30 and earlier and 5.7.12 and earlier and MariaDB 10.0.x before 10.0.25 and 10.1.x before 10.1.14 allows remote administrators to affect availability via vectors related to Server: InnoDB.

Affected Software

4 affected components

MariaDB MariaDB>=10.0.0<10.0.25

MariaDB MariaDB>=10.1.0<10.1.14

ORACLE MySQL>=5.6.0<=5.6.30

ORACLE MySQL>=5.7.0<=5.7.12

Remediation

Patch Available

http://www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html

Event History

Jul 21, 2016

CVE Published

via MITRE·10:00 AM

Data Sourced

via MITRE·10:00 AM

Description

Frequently Asked Questions

What is the severity of CVE-2016-3459?

CVE-2016-3459 is considered a medium severity vulnerability.

How do I fix CVE-2016-3459?