medium
4
CWE
399
Advisory Published
CVE Published
Updated

CVE-2010-3677

First published: Fri Aug 27 2010(Updated: )

A denial of service flaw was found in the way MySQL processed joins queries, which involved a table with unique SET column. A remote MySQL user could use this flaw to cause mysqld daemon crash. References: [1] <a href="http://secunia.com/advisories/41048/">http://secunia.com/advisories/41048/</a> [2] <a href="http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html">http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html</a> Upstream bug report: [3] <a href="http://bugs.mysql.com/bug.php?id=54575">http://bugs.mysql.com/bug.php?id=54575</a> 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.

Credit: cve@mitre.org

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

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-3677?

    CVE-2010-3677 has been classified as a high severity vulnerability due to its potential to cause a denial of service by crashing the MySQL server.

  • How do I fix CVE-2010-3677?

    To mitigate CVE-2010-3677, users should upgrade to MySQL version 5.1.49 or later where the issue has been addressed.

  • What software versions are affected by CVE-2010-3677?

    CVE-2010-3677 affects multiple MySQL versions up to 5.1.48 inclusive, including specifically versions 5.1.23, 5.1.34, 5.1.37, among others.

  • What type of attack does CVE-2010-3677 facilitate?

    CVE-2010-3677 facilitates a denial of service attack that can crash the mysqld daemon when processing certain complex join queries.

  • Who can exploit CVE-2010-3677?

    Any remote MySQL user can exploit CVE-2010-3677 by crafting specific join queries that trigger the vulnerability.

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