medium
4
CWE
Advisory Published
CVE Published
Updated

CVE-2010-3834

First published: Wed Oct 06 2010(Updated: )

A flaw in MySQL versions prior to 5.1.51 [1] was reported [2] that could allow an authenticated user to kill connections to MySQL, where the server could crash after materializing a derived table that required a temporary table for grouping. [1] <a href="http://dev.mysql.com/doc/refman/5.1/en/news-5-1-51.html">http://dev.mysql.com/doc/refman/5.1/en/news-5-1-51.html</a> [2] <a href="http://bugs.mysql.com/bug.php?id=55568">http://bugs.mysql.com/bug.php?id=55568</a>

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
MySQL=5.1.23
MySQL=5.1.34
MySQL=5.1.37
MySQL=5.1.31
MySQL=5.1.32
MySQL=5.1.5
MySQL=5.1.39
MySQL=5.1.40-sp1
MySQL=5.1.40
MySQL=5.1.41
MySQL=5.1.42
MySQL=5.1.43
MySQL=5.1.43-sp1
MySQL=5.1.44
MySQL=5.1.45
MySQL=5.1.46-sp1
MySQL=5.1.46
MySQL=5.1.47
MySQL=5.1.48
MySQL=5.1.49-sp1
MySQL=5.1.49
MySQL=5.1.50
MySQL=5.1
MySQL=5.1.1
MySQL=5.1.2
MySQL=5.1.3
MySQL=5.1.4
MySQL=5.1.6
MySQL=5.1.7
MySQL=5.1.8
MySQL=5.1.9
MySQL=5.1.10
MySQL=5.1.11
MySQL=5.1.12
MySQL=5.1.13
MySQL=5.1.14
MySQL=5.1.15
MySQL=5.1.16
MySQL=5.1.17
MySQL=5.1.18
MySQL=5.1.19
MySQL=5.1.20
MySQL=5.1.21
MySQL=5.1.22
MySQL=5.1.24
MySQL=5.1.25
MySQL=5.1.26
MySQL=5.1.27
MySQL=5.1.28
MySQL=5.1.29
MySQL=5.1.30
MySQL=5.1.33
MySQL=5.1.35
MySQL=5.1.36
MySQL=5.1.38
MySQL=5.1.23-a
MySQL=5.1.31-sp1
MySQL=5.1.34-sp1
MySQL=5.1.37-sp1
MySQL=5.5.3
MySQL=5.5.2
MySQL=5.5.5
MySQL=5.5.1
MySQL=5.5.4
MySQL=5.5.0
MySQL=5.0.5
MySQL=5.0.10
MySQL=5.0.54
MySQL=5.0.0
MySQL=5.0.84
MySQL=5.0.15
MySQL=5.0.17
MySQL=5.0.5.0.21
MySQL=5.0.3
MySQL=5.0.44
MySQL=5.0.66
MySQL=5.0.56
MySQL=5.0.60
MySQL=5.0.24
MySQL=5.0.87
MySQL=5.0.2
MySQL=5.0.22.1.0.1
MySQL=5.0.30
MySQL=5.0.20
MySQL=5.0.1
MySQL=5.0.4
MySQL=5.0.82
MySQL=5.0.36
MySQL=5.0.16
MySQL=5.0.45b
MySQL=5.0.50
MySQL=5.0.51
MySQL=5.0.0-alpha
MySQL=5.0.3-beta
MySQL=5.0.6
MySQL=5.0.11
MySQL=5.0.12
MySQL=5.0.13
MySQL=5.0.14
MySQL=5.0.18
MySQL=5.0.19
MySQL=5.0.21
MySQL=5.0.22
MySQL=5.0.23
MySQL=5.0.25
MySQL=5.0.26
MySQL=5.0.27
MySQL=5.0.30-sp1
MySQL=5.0.32
MySQL=5.0.33
MySQL=5.0.37
MySQL=5.0.38
MySQL=5.0.41
MySQL=5.0.42
MySQL=5.0.45
MySQL=5.0.52
MySQL=5.0.7
MySQL=5.0.8
MySQL=5.0.67
MySQL=5.0.75
MySQL=5.0.77
MySQL=5.0.81
MySQL=5.0.9
MySQL=5.0.83
MySQL=5.0.85
MySQL=5.0.86
MySQL=5.0.88
MySQL=5.0.89
MySQL=5.0.90
MySQL=5.0.91

Remedy

https://bugzilla.redhat.com/show_bug.cgi?id=640808

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2010-3834?

    CVE-2010-3834 has a medium severity rating due to its impact on MySQL server stability.

  • How do I fix CVE-2010-3834?

    To fix CVE-2010-3834, upgrade to MySQL version 5.1.51 or later.

  • What versions of MySQL are affected by CVE-2010-3834?

    CVE-2010-3834 affects MySQL versions prior to 5.1.51.

  • What impact does CVE-2010-3834 have on MySQL?

    CVE-2010-3834 can allow authenticated users to kill MySQL connections, potentially leading to server crashes.

  • Who can exploit CVE-2010-3834?

    Authenticated users with access to the MySQL server can exploit CVE-2010-3834.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203