CWE
NVD-CWE-Other
Advisory Published
CVE Published
Updated

CVE-2010-3839

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 cause the MySQL server to enter an infinite loop by creating a query with nested JOINs when used from stored procedures and prepared statements. [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=53544">http://bugs.mysql.com/bug.php?id=53544</a> This affects MySQL 5.x, but MySQL 4.x and early do not have support for stored procedures. This causes CPU consumption around 95-100%, however connections and queries to the database can continue. Killing the query itself is ineffective, and even a 'service mysqld restart' will fail unless the mysqld process that is handling the query is forcibly killed.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
MySQL (MySQL-common)=5.1.23
MySQL (MySQL-common)=5.1.34
MySQL (MySQL-common)=5.1.37
MySQL (MySQL-common)=5.1.31
MySQL (MySQL-common)=5.1.32
MySQL (MySQL-common)=5.1.5
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.48
Oracle MySQL=5.1.49-sp1
Oracle MySQL=5.1.49
Oracle MySQL=5.1.50
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.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
Oracle MySQL=5.5.3
Oracle MySQL=5.5.2
Oracle MySQL=5.5.5
Oracle MySQL=5.5.1
Oracle MySQL=5.5.4
Oracle MySQL=5.5.0

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.

Frequently Asked Questions

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

    CVE-2010-3839 is considered a moderate severity vulnerability as it can cause a denial of service through an infinite loop.

  • How do I fix CVE-2010-3839?

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

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

    CVE-2010-3839 affects MySQL versions prior to 5.1.51, including numerous earlier versions from 5.1.5 to 5.1.50.

  • Can CVE-2010-3839 be exploited remotely?

    CVE-2010-3839 requires an authenticated user to be exploited, as it involves creating specific queries that trigger the vulnerability.

  • What impact does CVE-2010-3839 have on MySQL databases?

    The impact of CVE-2010-3839 is that it can cause the MySQL server to become unresponsive, potentially disrupting service for users.

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