What is the severity of CVE-2015-4866?

CVE-2015-4866 has been classified as having an unspecified severity level.

How do I fix CVE-2015-4866?

To fix CVE-2015-4866, update Oracle MySQL Server to a version later than 5.6.23.

What systems are affected by CVE-2015-4866?

CVE-2015-4866 affects Oracle MySQL Server 5.6.23 and earlier, as well as certain versions of MariaDB and specific Ubuntu Linux distributions.

Is there a workaround for CVE-2015-4866?

There are no documented workarounds for CVE-2015-4866; the only mitigation is upgrading to a patched version.

Can CVE-2015-4866 be exploited remotely?

Yes, CVE-2015-4866 can be exploited by remote authenticated users, potentially affecting the availability of the database.

Vulnerability/
CVE-2015-4866

medium

21/10/2015

6/8/2024

CVE-2015-4866

First published: Wed Oct 21 2015(Updated: )

Unspecified vulnerability in Oracle MySQL Server 5.6.23 and earlier allows remote authenticated users to affect availability via unknown vectors related to Server : InnoDB.

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
MySQL	>=5.6.0<=5.6.23
Mariadb Mariadb	>=10.0.0<10.0.18
Mariadb Mariadb	>=10.1.0<10.1.8
Ubuntu Linux	=12.04
Ubuntu Linux	=14.04
Ubuntu Linux	=15.04
Ubuntu Linux	=15.10

Remedy

http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2015-4866?
CVE-2015-4866 has been classified as having an unspecified severity level.
How do I fix CVE-2015-4866?
To fix CVE-2015-4866, update Oracle MySQL Server to a version later than 5.6.23.
What systems are affected by CVE-2015-4866?
CVE-2015-4866 affects Oracle MySQL Server 5.6.23 and earlier, as well as certain versions of MariaDB and specific Ubuntu Linux distributions.
Is there a workaround for CVE-2015-4866?
There are no documented workarounds for CVE-2015-4866; the only mitigation is upgrading to a patched version.
Can CVE-2015-4866 be exploited remotely?
Yes, CVE-2015-4866 can be exploited by remote authenticated users, potentially affecting the availability of the database.

agent/references
agent/type
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/author
agent/remedy
agent/severity
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
agent/softwarecombine
vendor/oracle
canonical/mysql
version/mysql/5.6.0
version/mysql/5.6.23
vendor/mariadb
canonical/mariadb mariadb
version/mariadb mariadb/10.0.0
version/mariadb mariadb/10.1.0
vendor/canonical
canonical/ubuntu linux
version/ubuntu linux/12.04
version/ubuntu linux/14.04
version/ubuntu linux/15.04
version/ubuntu linux/15.10

Company

Resources

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.

Frequently Asked Questions

What is the severity of CVE-2015-4866?
CVE-2015-4866 has been classified as having an unspecified severity level.
How do I fix CVE-2015-4866?
To fix CVE-2015-4866, update Oracle MySQL Server to a version later than 5.6.23.
What systems are affected by CVE-2015-4866?
CVE-2015-4866 affects Oracle MySQL Server 5.6.23 and earlier, as well as certain versions of MariaDB and specific Ubuntu Linux distributions.
Is there a workaround for CVE-2015-4866?
There are no documented workarounds for CVE-2015-4866; the only mitigation is upgrading to a patched version.
Can CVE-2015-4866 be exploited remotely?
Yes, CVE-2015-4866 can be exploited by remote authenticated users, potentially affecting the availability of the database.