CVE-2013-1861: Buffer Overflow

Published Mar 7, 2013
·
Updated

Alyssa Milburn reported that when MySQL attempts to convert a binary string representation of a raw geometry object to a textual representation, the length checks in MySQL's spatial functions would overflow, resulting in a crash of mysqld (for instance, a query like "select astext(0x0100000000030000000100000000000010);" will cause the crash).

This has been reported to both upstream MariaDB [1] and Oracle [2]. A proposed patch is available [3].

[1] https://mariadb.atlassian.net/browse/MDEV-4252 [2] http://bugs.mysql.com/bug.php?id=68591 [3] http://lists.askmonty.org/pipermail/commits/2013-March/004371.html

Acknowledgements:

Red Hat would like to thank Alyssa Milburn for reporting this issue.

Other sources

MariaDB 5.5.x before 5.5.30, 5.3.x before 5.3.13, 5.2.x before 5.2.15, and 5.1.x before 5.1.68, and Oracle MySQL 5.1.69 and earlier, 5.5.31 and earlier, and 5.6.11 and earlier allows remote attackers to cause a denial of service (crash) via a crafted geometry feature that specifies a large number of points, which is not properly handled when processing the binary representation of this feature, related to a numeric calculation error.

MITRE

Affected Software

22 affected componentsFixes available
redhat/mysql<5.6.12
5.6.12
redhat/mysql<5.5.32
5.5.32
redhat/mysql<5.1.70
5.1.70
MariaDB MariaDB>=5.5.0<5.5.32
MariaDB MariaDB>=10.0.0<10.0.4
Oracle MySQL>=5.1.0<=5.1.69
Oracle MySQL>=5.5.0<=5.5.31
Oracle MySQL>=5.6.0<=5.6.11
redhat Enterprise Linux=5
redhat Enterprise Linux=6.0
Debian Debian Linux=7.0
Canonical Ubuntu Linux=10.04
Canonical Ubuntu Linux=12.04
Canonical Ubuntu Linux=12.10
Canonical Ubuntu Linux=13.04
openSUSE openSUSE=11.4
openSUSE openSUSE=12.2
openSUSE openSUSE=12.3
SUSE Linux Enterprise Desktop=11-sp3
SUSE Linux Enterprise Server=11-sp3
SUSE Linux Enterprise Server Vmware=11-sp3
SUSE Linux Enterprise Software Development Kit=11-sp3

Event History

Mar 7, 2013
Data Sourced
via Red Hat·10:25 PM
DescriptionSeverityAffected Software
Mar 28, 2013
CVE Published
via MITRE·11:00 PM
Data Sourced
via MITRE·11:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2013-1861?

CVE-2013-1861 has a high severity rating as it can lead to a crash of the MySQL server.

2

How do I fix CVE-2013-1861?

To mitigate CVE-2013-1861, upgrade MySQL to version 5.6.12, 5.5.32, or 5.1.70 or higher.

3

What versions of MySQL are affected by CVE-2013-1861?

CVE-2013-1861 affects MySQL versions below 5.6.12, 5.5.32, and 5.1.70.

4

Is MariaDB affected by CVE-2013-1861?

Yes, MariaDB versions between 5.5.0 and 5.5.32 and 10.0.0 and 10.0.4 are affected by CVE-2013-1861.

5

What can happen if CVE-2013-1861 is exploited?

Exploitation of CVE-2013-1861 can cause a crash of the mysqld process, resulting in service disruption.

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