What is the severity of CVE-2013-1512?

CVE-2013-1512 is classified as a moderate severity vulnerability affecting Oracle MySQL and MariaDB.

How do I fix CVE-2013-1512?

To fix CVE-2013-1512, upgrade to MySQL version 5.5.30 or later and ensure that you are using an updated version of MariaDB.

Who is affected by CVE-2013-1512?

CVE-2013-1512 affects remote authenticated users of Oracle MySQL 5.5.29 and earlier, as well as certain versions of MariaDB.

What types of attacks can CVE-2013-1512 enable?

CVE-2013-1512 can potentially allow remote authenticated users to affect the availability of the database through Data Manipulation Language operations.

When was CVE-2013-1512 discovered?

CVE-2013-1512 was disclosed in 2013.

Vulnerability/
CVE-2013-1512

medium

17/4/2013

26/8/2022

CVE-2013-1512

First published: Wed Apr 17 2013(Updated: )

Unspecified vulnerability in Oracle MySQL 5.5.29 and earlier allows remote authenticated users to affect availability via unknown vectors related to Data Manipulation Language.

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
MySQL	>=5.5.0<=5.5.29
Mariadb Mariadb	>=5.5.0<5.5.30
Mariadb Mariadb	>=10.0.0<10.0.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2013-1512?
CVE-2013-1512 is classified as a moderate severity vulnerability affecting Oracle MySQL and MariaDB.
How do I fix CVE-2013-1512?
To fix CVE-2013-1512, upgrade to MySQL version 5.5.30 or later and ensure that you are using an updated version of MariaDB.
Who is affected by CVE-2013-1512?
CVE-2013-1512 affects remote authenticated users of Oracle MySQL 5.5.29 and earlier, as well as certain versions of MariaDB.
What types of attacks can CVE-2013-1512 enable?
CVE-2013-1512 can potentially allow remote authenticated users to affect the availability of the database through Data Manipulation Language operations.
When was CVE-2013-1512 discovered?
CVE-2013-1512 was disclosed in 2013.

agent/severity
agent/references
agent/tags
agent/event
agent/type
agent/last-modified-date
agent/softwarecombine
agent/first-publish-date
collector/nvd-index
agent/software-canonical-lookup-request
agent/description
agent/author
vendor/oracle
canonical/mysql
version/mysql/5.5.0
version/mysql/5.5.29
vendor/mariadb
canonical/mariadb mariadb
version/mariadb mariadb/5.5.0
version/mariadb mariadb/10.0.0

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-1512?
CVE-2013-1512 is classified as a moderate severity vulnerability affecting Oracle MySQL and MariaDB.
How do I fix CVE-2013-1512?
To fix CVE-2013-1512, upgrade to MySQL version 5.5.30 or later and ensure that you are using an updated version of MariaDB.
Who is affected by CVE-2013-1512?
CVE-2013-1512 affects remote authenticated users of Oracle MySQL 5.5.29 and earlier, as well as certain versions of MariaDB.
What types of attacks can CVE-2013-1512 enable?
CVE-2013-1512 can potentially allow remote authenticated users to affect the availability of the database through Data Manipulation Language operations.
When was CVE-2013-1512 discovered?
CVE-2013-1512 was disclosed in 2013.