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.
No CVE has been assigned; I presume that Oracle will likely end up doing that (hard to tell since their bug is private).
Mariadb patches: 5.1: http://bazaar.launchpad.net/~maria-captains/maria/5.1/revision/3188 5.5: http://bazaar.launchpad.net/~maria-captains/maria/5.5/revision/3682
Created mysql tracking bugs for this issue Affects: fedora-all [bug 921836]
This issue was assigned CVE-2013-1861 via: http://seclists.org/oss-sec/2013/q1/671
Statement: This issue was addressed in the package mysql55-mysql as shipped with Red Hat Enterprise Linux 5 via RHEA-2013:1330. This issue was addressed in the package mysql as shipped with Red Hat Enterprise Linux 6 via RHBA-2013:1647.
See also: http://lists.askmonty.org/pipermail/commits/2013-March/004447.html
community-mysql-5.5.31-7.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
This issue is noted as being corrected in the Oracle July 2013 CPU: http://www.oracle.com/technetwork/topics/security/cpujuly2013-1899826.html#AppendixMSQL It is reported to be fixed in 5.6.12, 5.5.32, and 5.1.70.