CVE-2017-3302: Use After Free

Q: What is the severity of CVE-2017-3302?

CVE-2017-3302 has a high severity level due to the potential for application crashes caused by exploitation.

Q: How do I fix CVE-2017-3302?

To resolve CVE-2017-3302, upgrade the MySQL client library to versions 5.5.55, 5.6.21, 5.7.5, or appropriate versions of MariaDB.

Q: What types of applications are affected by CVE-2017-3302?

Applications using the affected MySQL client library (libmysqlclient.so) are vulnerable to CVE-2017-3302.

Q: Who is vulnerable to CVE-2017-3302?

Vulnerable users include anyone running the specified versions of MySQL and MariaDB client libraries.

Q: Can CVE-2017-3302 be exploited remotely?

Yes, a malicious MySQL server could exploit CVE-2017-3302 to crash applications remotely.

Published Feb 12, 2017

Updated

A use-after-free flaw was found in the MySQL client library (libmysqlclient.so). A malicious MySQL server could cause an application using the MySQL client library to crash.

Upstream bugs:

https://bugs.mysql.com/bug.php?id=70429 https://bugs.mysql.com/bug.php?id=63363

Upstream patch:

https://github.com/mysql/mysql-server/commit/4797ea0b772d5f4c5889bc552424132806f46e93

Other sources

Crash in libmysqlclient.so in Oracle MySQL before 5.6.21 and 5.7.x before 5.7.5 and MariaDB through 5.5.54, 10.0.x through 10.0.29, 10.1.x through 10.1.21, and 10.2.x through 10.2.3.

— MITRE

Affected Software

22 affected componentsFixes available

redhat/mysql<5.5.55

5.5.55

redhat/mysql<5.6.21

5.6.21

redhat/mysql<5.7.5

5.7.5

redhat/mariadb<10.0.30

10.0.30

redhat/mariadb<10.1.22

10.1.22

redhat/mariadb<10.2.5

10.2.5

redhat/mariadb<5.5.55

5.5.55

Oracle MySQL>=5.6.0<5.6.21

Oracle MySQL>=5.7.0<5.7.5

MariaDB MariaDB<=5.5.54

MariaDB MariaDB>=10.0.0<=10.0.29

MariaDB MariaDB>=10.1.0<=10.1.21

MariaDB MariaDB>=10.2.0<=10.2.3

Debian Debian Linux=8.0

redhat Enterprise Linux Desktop=7.0

redhat Enterprise Linux Server=7.0

redhat Enterprise Linux Server Aus=7.4

redhat Enterprise Linux Server Aus=7.6

redhat Enterprise Linux Server Eus=7.4

redhat Enterprise Linux Server Eus=7.5

redhat Enterprise Linux Server Eus=7.6

redhat Enterprise Linux Workstation=7.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade redhat/mysql to a version that resolves this vulnerability.
Fixed in 5.5.55
Upgrade
Upgrade redhat/mysql to a version that resolves this vulnerability.
Fixed in 5.6.21
Upgrade
Upgrade redhat/mysql to a version that resolves this vulnerability.
Fixed in 5.7.5
Upgrade
Upgrade redhat/mariadb to a version that resolves this vulnerability.
Fixed in 10.0.30
Upgrade
Upgrade redhat/mariadb to a version that resolves this vulnerability.
Fixed in 10.1.22
Upgrade
Upgrade redhat/mariadb to a version that resolves this vulnerability.
Fixed in 10.2.5
Upgrade
Upgrade redhat/mariadb to a version that resolves this vulnerability.
Fixed in 5.5.55
Upgrade
Upgrade Oracle MySQL to a version that resolves this vulnerability.
Fixed in 5.6.21
Upgrade
Upgrade Oracle MySQL 5.7.x to a version that resolves this vulnerability.
Fixed in 5.7.5
Upgrade
Upgrade MariaDB to a version that resolves this vulnerability.
Fixed in 5.5.54
Upgrade
Upgrade MariaDB 10.0.x to a version that resolves this vulnerability.
Fixed in 10.0.29
Upgrade
Upgrade MariaDB 10.1.x to a version that resolves this vulnerability.
Fixed in 10.1.21
Upgrade
Upgrade MariaDB 10.2.x to a version that resolves this vulnerability.
Fixed in 10.2.3

Event History

Feb 12, 2017

CVE Published

via MITRE·04:43 AM

Data Sourced

via MITRE·04:43 AM

DescriptionWeakness

Data Sourced

via NVD·04:59 AM

RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

What is the severity of CVE-2017-3302?

CVE-2017-3302 has a high severity level due to the potential for application crashes caused by exploitation.

How do I fix CVE-2017-3302?

To resolve CVE-2017-3302, upgrade the MySQL client library to versions 5.5.55, 5.6.21, 5.7.5, or appropriate versions of MariaDB.

What types of applications are affected by CVE-2017-3302?