CVE-2010-3682: Null Pointer Dereference

Published Aug 29, 2010
·
Updated

A denial of service flaw was found in the way MySQL processed EXPLAIN statements for SQL queries of the form:

SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...)

A remote authenticated MySQL user could use this flaw to cause mysqld deamon crash (dereference NULL pointer).

References: [1] http://secunia.com/advisories/41048/ [2] http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html

Upstream bug report: [3] http://bugs.mysql.com/bug.php?id=52711

Upstream changesets: [4] http://lists.mysql.com/commits/105750 [5] http://lists.mysql.com/commits/112043

Note: This issue only causes a temporary denial of service, as the mysql daemon shipped with Red Hat Enterprise Linux 5 will be automatically restarted after the crash.

Other sources

Oracle MySQL 5.1 before 5.1.49 and 5.0 before 5.0.92 allows remote authenticated users to cause a denial of service (mysqld daemon crash) by using EXPLAIN with crafted "SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...)" statements, which triggers a NULL pointer dereference in the Itemsinglerowsubselect::store function.

Affected Software

116 affected components
MySQL mysql=5.1.23
MySQL mysql=5.1.34
MySQL mysql<=5.1.48
MySQL mysql=5.1.37
MySQL mysql=5.1.31
MySQL mysql=5.1.32
Oracle MySQL=5.1.39
Oracle MySQL=5.1.40-sp1
Oracle MySQL=5.1.40
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-sp1
Oracle MySQL=5.1.46
Oracle MySQL=5.1.47
Oracle MySQL=5.1.1
Oracle MySQL=5.1.2
Oracle MySQL=5.1.3
Oracle MySQL=5.1.4
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.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.33
Oracle MySQL=5.1.35
Oracle MySQL=5.1.36
Oracle MySQL=5.1.38
Oracle MySQL=5.1.23-a
Oracle MySQL=5.1.31-sp1
Oracle MySQL=5.1.34-sp1
Oracle MySQL=5.1.37-sp1
MySQL mysql=5.0.10
MySQL mysql<=5.0.91
MySQL mysql=5.0.54
MySQL mysql=5.0.0
MySQL mysql=5.0.84
MySQL mysql=5.0.15
MySQL mysql=5.0.17
MySQL mysql=5.0.44
MySQL mysql=5.0.66
MySQL mysql=5.0.56
MySQL mysql=5.0.74
MySQL mysql=5.0.60
MySQL mysql=5.0.24
MySQL mysql=5.0.87
MySQL mysql=5.0.2
MySQL mysql=5.0.30
MySQL mysql=5.0.20
MySQL mysql=5.0.1
MySQL mysql=5.0.72
MySQL mysql=5.0.82
MySQL mysql=5.0.36
MySQL mysql=5.0.16
Oracle MySQL=5.0.48
Oracle MySQL=5.0.50
Oracle MySQL=5.0.51-a
Oracle MySQL=5.0.51-b
Oracle MySQL=5.0.28
Oracle MySQL=5.0.30-sp1
Oracle MySQL=5.0.32
Oracle MySQL=5.0.34
Oracle MySQL=5.0.36-sp1
Oracle MySQL=5.0.38
Oracle MySQL=5.0.40
Oracle MySQL=5.0.41
Oracle MySQL=5.0.42
Oracle MySQL=5.0.44-sp1
Oracle MySQL=5.0.45
Oracle MySQL=5.0.46
Oracle MySQL=5.0.52
Oracle MySQL=5.0.56-sp1
Oracle MySQL=5.0.58
Oracle MySQL=5.0.62
Oracle MySQL=5.0.64
Oracle MySQL=5.0.67
Oracle MySQL=5.0.68
Oracle MySQL=5.0.70
Oracle MySQL=5.0.75
Oracle MySQL=5.0.76
Oracle MySQL=5.0.77
Oracle MySQL=5.0.78
Oracle MySQL=5.0.79
Oracle MySQL=5.0.80
Oracle MySQL=5.0.81
Oracle MySQL=5.0.83
Oracle MySQL=5.0.85
Oracle MySQL=5.0.86
Oracle MySQL=5.0.88
Oracle MySQL=5.0.89
Oracle MySQL=5.0.90
Oracle MySQL=5.0.66-a
Oracle MySQL=5.0.66-sp1
Oracle MySQL=5.0.72-sp1
Oracle MySQL=5.0.74-sp1
Oracle MySQL=5.0.82-sp1
Oracle MySQL=5.0.84-sp1
Oracle MySQL=5.0.87-sp1

Event History

Aug 29, 2010
Data Sourced
01:57 PM
DescriptionSeverityAffected Software
Jan 11, 2011
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2010-3682?

CVE-2010-3682 has been classified as a denial-of-service vulnerability that could lead to a crash of the MySQL daemon.

2

How do I fix CVE-2010-3682?

To mitigate CVE-2010-3682, it is recommended to upgrade to a fixed version of MySQL that addresses this vulnerability.

3

Which versions are affected by CVE-2010-3682?

CVE-2010-3682 affects MySQL versions 5.1.1 through 5.1.48, as well as specific higher versions based on the software versioning.

4

Who can exploit CVE-2010-3682?

A remote authenticated MySQL user can exploit CVE-2010-3682 to cause a denial-of-service condition.

5

What is the impact of exploiting CVE-2010-3682?

Exploiting CVE-2010-3682 can cause the MySQL server process to crash, resulting in a denial of service.

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