What is the severity of CVE-2013-0367?

CVE-2013-0367 has a medium severity rating, as it can potentially affect the availability of the Server component in Oracle MySQL and MariaDB.

How do I fix CVE-2013-0367?

To fix CVE-2013-0367, upgrade Oracle MySQL to version 5.5.29 or later or update your MariaDB installation to a secure version.

Who is affected by CVE-2013-0367?

CVE-2013-0367 affects users of Oracle MySQL versions 5.5.28 and earlier, as well as specific versions of MariaDB.

What types of attacks are possible with CVE-2013-0367?

CVE-2013-0367 can be exploited by remote authenticated users to impact the availability of the affected server.

Is there a workaround for CVE-2013-0367?

There are no known workarounds for CVE-2013-0367 other than applying the recommended software updates.

Vulnerability/
CVE-2013-0367

medium

17/1/2013

6/8/2024

CVE-2013-0367

First published: Thu Jan 17 2013(Updated: )

Unspecified vulnerability in the Server component in Oracle MySQL 5.5.28 and earlier allows remote authenticated users to affect availability via unknown vectors related to Server Partition.

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
MySQL	>=5.5.0<=5.5.28
Mariadb Mariadb	>=5.5.0<5.5.29
Mariadb Mariadb	=10.0.0
Ubuntu Linux	=10.04
Ubuntu Linux	=11.10
Ubuntu Linux	=12.04
Ubuntu Linux	=12.10

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2013-0367?
CVE-2013-0367 has a medium severity rating, as it can potentially affect the availability of the Server component in Oracle MySQL and MariaDB.
How do I fix CVE-2013-0367?
To fix CVE-2013-0367, upgrade Oracle MySQL to version 5.5.29 or later or update your MariaDB installation to a secure version.
Who is affected by CVE-2013-0367?
CVE-2013-0367 affects users of Oracle MySQL versions 5.5.28 and earlier, as well as specific versions of MariaDB.
What types of attacks are possible with CVE-2013-0367?
CVE-2013-0367 can be exploited by remote authenticated users to impact the availability of the affected server.
Is there a workaround for CVE-2013-0367?
There are no known workarounds for CVE-2013-0367 other than applying the recommended software updates.

agent/references
agent/type
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/author
agent/description
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
agent/softwarecombine
vendor/oracle
canonical/mysql
version/mysql/5.5.0
version/mysql/5.5.28
vendor/mariadb
canonical/mariadb mariadb
version/mariadb mariadb/5.5.0
version/mariadb mariadb/10.0.0
vendor/canonical
canonical/ubuntu linux
version/ubuntu linux/10.04
version/ubuntu linux/11.10
version/ubuntu linux/12.04
version/ubuntu linux/12.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-2013-0367?
CVE-2013-0367 has a medium severity rating, as it can potentially affect the availability of the Server component in Oracle MySQL and MariaDB.
How do I fix CVE-2013-0367?
To fix CVE-2013-0367, upgrade Oracle MySQL to version 5.5.29 or later or update your MariaDB installation to a secure version.
Who is affected by CVE-2013-0367?
CVE-2013-0367 affects users of Oracle MySQL versions 5.5.28 and earlier, as well as specific versions of MariaDB.
What types of attacks are possible with CVE-2013-0367?
CVE-2013-0367 can be exploited by remote authenticated users to impact the availability of the affected server.
Is there a workaround for CVE-2013-0367?
There are no known workarounds for CVE-2013-0367 other than applying the recommended software updates.