CVE-2016-5626: Medium severity mysql vulnerability
Published Oct 25, 2016
·Updated
Unspecified vulnerability in Oracle MySQL 5.5.51 and earlier, 5.6.32 and earlier, and 5.7.14 and earlier allows remote authenticated users to affect availability via vectors related to GIS.
Affected Software
19 affected components
Oracle MySQL>=5.5.0<=5.5.51
Oracle MySQL>=5.6.0<=5.6.32
Oracle MySQL>=5.7.0<=5.7.14
MariaDB MariaDB>=5.5.0<5.5.52
MariaDB MariaDB>=10.0.0<10.0.28
MariaDB MariaDB>=10.1.0<10.1.18
redhat Enterprise Linux Eus=7.3
redhat Enterprise Linux Eus=7.4
redhat Enterprise Linux Eus=7.5
redhat Enterprise Linux Eus=7.6
redhat Enterprise Linux Eus=7.7
redhat Enterprise Linux Server=7.0
redhat Enterprise Linux Server Aus=7.3
redhat Enterprise Linux Server Aus=7.4
redhat Enterprise Linux Server Aus=7.6
redhat Enterprise Linux Server Aus=7.7
redhat Enterprise Linux Server Tus=7.3
redhat Enterprise Linux Server Tus=7.6
redhat Enterprise Linux Server Tus=7.7
Remediation
Event History
Oct 25, 2016
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2016-5626?
CVE-2016-5626 is classified as a medium severity vulnerability that affects availability.
2
How do I fix CVE-2016-5626?
To fix CVE-2016-5626, update MySQL to a version later than 5.5.51, 5.6.32, or 5.7.14.
3
What products are affected by CVE-2016-5626?
CVE-2016-5626 affects Oracle MySQL versions 5.5.51 and earlier, 5.6.32 and earlier, and 5.7.14 and earlier.
4
Can CVE-2016-5626 be exploited remotely?
Yes, CVE-2016-5626 can be exploited by remote authenticated users.
5
Does CVE-2016-5626 affect MariaDB?
Yes, certain versions of MariaDB that are earlier than 5.5.52, 10.0.28, and 10.1.18 are affected by CVE-2016-5626.