CVE-2016-0649: Medium severity ibm powerkvm vulnerability

Published Apr 21, 2016
·
Updated

Unspecified vulnerability in Oracle MySQL 5.5.47 and earlier, 5.6.28 and earlier, and 5.7.10 and earlier and MariaDB before 5.5.48, 10.0.x before 10.0.24, and 10.1.x before 10.1.12 allows local users to affect availability via vectors related to PS.

Other sources

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: PS). Supported versions that are affected are 5.5.47 and earlier, 5.6.28 and earlier and 5.7.10 and earlier. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where MySQL Server executes to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server.

External References:

http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html#AppendixMSQL

Red Hat

Affected Software

19 affected componentsFixes available
redhat/mysql<5.5.48
5.5.48
redhat/mysql<5.6.29
5.6.29
redhat/mysql<5.7.11
5.7.11
redhat/mariadb<5.5.48
5.5.48
redhat/mariadb<10.1.12
10.1.12
redhat/mariadb<10.0.24
10.0.24
IBM PowerKVM=2.1
IBM PowerKVM=3.1
redhat Enterprise Linux=6.0
redhat Enterprise Linux=7.0
openSUSE Leap=42.1
Debian Debian Linux=8.0
Oracle Linux=7
Oracle MySQL>=5.5.0<=5.5.47
Oracle MySQL>=5.6.0<=5.6.28
Oracle MySQL>=5.7.0<=5.7.10
MariaDB MariaDB>=5.5.20<5.5.48
MariaDB MariaDB>=10.0.0<10.0.24
MariaDB MariaDB>=10.1.0<10.1.12

Event History

Apr 21, 2016
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2016-0649?

The severity of CVE-2016-0649 is considered potentially critical, as it allows local users to affect the availability of MySQL and MariaDB servers.

2

How do I fix CVE-2016-0649?

To fix CVE-2016-0649, upgrade your MySQL to version 5.5.48 or later, 5.6.29 or later, or 5.7.11 or later, or upgrade MariaDB to 5.5.48, 10.0.24, or 10.1.12 or later.

3

Which versions of MySQL are affected by CVE-2016-0649?

CVE-2016-0649 affects MySQL versions 5.5.47 and earlier, 5.6.28 and earlier, and 5.7.10 and earlier.

4

Which versions of MariaDB are affected by CVE-2016-0649?

CVE-2016-0649 affects MariaDB versions before 5.5.48, 10.0.x before 10.0.24, and 10.1.x before 10.1.12.

5

Is CVE-2016-0649 a local or remote vulnerability?

CVE-2016-0649 is a local vulnerability, meaning it can only be exploited by local users on the affected systems.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203