CVE-2012-2749: Medium severity MySQL mysql vulnerability

Published Jun 20, 2012
·
Updated

MySQL 5.1.x before 5.1.63 and 5.5.x before 5.5.24 allows remote authenticated users to cause a denial of service (mysqld crash) via vectors related to incorrect calculation and a sort order index.

Other sources

MySQL versions 5.1.63 and 5.5.24 fix the following bug noted in the 5.1.63 release notes:

Security Fix: Bug #59387 was fixed.

http://dev.mysql.com/doc/refman/5.1/en/news-5-1-63.html

This bug is also fixed in 5.5.24, but not mentioned in the release notes or changelog.

Related upstream change is:

http://bazaar.launchpad.net/~mysql/mysql-server/5.1/revision/3560.10.16 Bug#11766300 59387: FAILING ASSERTION: CURSOR->POSSTATE == 1997660512 (BTRPCURISPOSITIONE Bug#13639204 64111: CRASH ON SELECT SUBQUERY WITH NON UNIQUE INDEX

This issue allows non-admin database user with full SQL access to crash mysqld. Upstream commit explains issue details:

The crash happened due to wrong calculation of key length during creation of reference for sort order index. The problem is that keyuse->usedtables can have OUTERREFTABLEBIT enabled but usedtables parameter(createrefforkey() func) does not have it. So key parts which have OUTERREFTABLEBIT are ommited and it could lead to incorrect key length calculation(zero key length).

Affected Software

97 affected componentsFixes available
redhat/mysql<5.1.63
5.1.63
redhat/mysql<5.5.24
5.5.24
MySQL mysql=5.1.5
MySQL mysql=5.1.23
MySQL mysql=5.1.31
MySQL mysql=5.1.32
MySQL mysql=5.1.34
MySQL mysql=5.1.37
Oracle MySQL=5.1
Oracle MySQL=5.1.1
Oracle MySQL=5.1.2
Oracle MySQL=5.1.3
Oracle MySQL=5.1.4
Oracle MySQL=5.1.6
Oracle MySQL=5.1.7
Oracle MySQL=5.1.8
Oracle MySQL=5.1.9
Oracle MySQL=5.1.10
Oracle MySQL=5.1.11
Oracle MySQL=5.1.12
Oracle MySQL=5.1.13
Oracle MySQL=5.1.14
Oracle MySQL=5.1.15
Oracle MySQL=5.1.16
Oracle MySQL=5.1.17
Oracle MySQL=5.1.18
Oracle MySQL=5.1.19
Oracle MySQL=5.1.20
Oracle MySQL=5.1.21
Oracle MySQL=5.1.22
Oracle MySQL=5.1.23-a
Oracle MySQL=5.1.24
Oracle MySQL=5.1.25
Oracle MySQL=5.1.26
Oracle MySQL=5.1.27
Oracle MySQL=5.1.28
Oracle MySQL=5.1.29
Oracle MySQL=5.1.30
Oracle MySQL=5.1.31-sp1
Oracle MySQL=5.1.33
Oracle MySQL=5.1.34-sp1
Oracle MySQL=5.1.35
Oracle MySQL=5.1.36
Oracle MySQL=5.1.37-sp1
Oracle MySQL=5.1.38
Oracle MySQL=5.1.39
Oracle MySQL=5.1.40
Oracle MySQL=5.1.40-sp1
Oracle MySQL=5.1.41
Oracle MySQL=5.1.42
Oracle MySQL=5.1.43
Oracle MySQL=5.1.43-sp1
Oracle MySQL=5.1.44
Oracle MySQL=5.1.45
Oracle MySQL=5.1.46
Oracle MySQL=5.1.46-sp1
Oracle MySQL=5.1.47
Oracle MySQL=5.1.48
Oracle MySQL=5.1.49
Oracle MySQL=5.1.49-sp1
Oracle MySQL=5.1.50
Oracle MySQL=5.1.51
Oracle MySQL=5.1.52
Oracle MySQL=5.1.52-sp1
Oracle MySQL=5.1.53
Oracle MySQL=5.1.54
Oracle MySQL=5.1.55
Oracle MySQL=5.1.56
Oracle MySQL=5.1.57
Oracle MySQL=5.1.58
Oracle MySQL=5.1.59
Oracle MySQL=5.1.60
Oracle MySQL=5.1.61
Oracle MySQL=5.1.62
Oracle MySQL=5.5.0
Oracle MySQL=5.5.1
Oracle MySQL=5.5.2
Oracle MySQL=5.5.3
Oracle MySQL=5.5.4
Oracle MySQL=5.5.5
Oracle MySQL=5.5.6
Oracle MySQL=5.5.7
Oracle MySQL=5.5.9
Oracle MySQL=5.5.10
Oracle MySQL=5.5.11
Oracle MySQL=5.5.12
Oracle MySQL=5.5.13
Oracle MySQL=5.5.14
Oracle MySQL=5.5.15
Oracle MySQL=5.5.16
Oracle MySQL=5.5.17
Oracle MySQL=5.5.18
Oracle MySQL=5.5.19
Oracle MySQL=5.5.20
Oracle MySQL=5.5.21
Oracle MySQL=5.5.22
Oracle MySQL=5.5.23

Event History

Jun 20, 2012
Data Sourced
via Red Hat·08:27 AM
DescriptionSeverityAffected Software
Aug 17, 2012
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2012-2749?

The severity of CVE-2012-2749 is categorized as medium, as it allows for denial of service through a crash of the mysqld process.

2

How do I fix CVE-2012-2749?

To fix CVE-2012-2749, you should upgrade your MySQL installation to version 5.1.63 or 5.5.24 or later.

3

Who is affected by CVE-2012-2749?

CVE-2012-2749 affects authenticated users of MySQL versions 5.1.x before 5.1.63 and 5.5.x before 5.5.24.

4

What can exploit CVE-2012-2749?

CVE-2012-2749 can be exploited by remote authenticated users via incorrect calculation and sort order index, leading to a denial of service.

5

What are the vulnerable versions of MySQL for CVE-2012-2749?

The vulnerable versions of MySQL for CVE-2012-2749 are 5.1.5 through 5.1.62 and 5.5.0 through 5.5.23.

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