medium
4
CWE
399
Advisory Published
CVE Published
Updated

CVE-2010-3679

First published: Fri Aug 27 2010(Updated: )

A use of unassigned memory was found in the way MySQL processed certain values provided to the BINLOG statement. A remote attacker could use this flaw to cause denial of service (mysqld daemon crash) in some cases. 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=54393">http://bugs.mysql.com/bug.php?id=54393</a> Upstream changeset: [4] <a href="http://lists.mysql.com/commits/111591">http://lists.mysql.com/commits/111591</a> Note: The impact of this flaw is further mitigated by the requirement only privileged user can run the BINLOG statement.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
MySQL (MySQL-common)=5.1.5
MySQL (MySQL-common)=5.1.23
MySQL (MySQL-common)=5.1.31
MySQL (MySQL-common)=5.1.32
MySQL (MySQL-common)=5.1.34
MySQL (MySQL-common)=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

Remedy

http://bugs.mysql.com/bug.php?id=54393

Remedy

http://www.openwall.com/lists/oss-security/2010/09/28/10

Remedy

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

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

    The severity of CVE-2010-3679 is classified as high due to its potential to cause denial of service.

  • How do I fix CVE-2010-3679?

    To fix CVE-2010-3679, you should upgrade MySQL to version 5.1.49 or later.

  • Which MySQL versions are affected by CVE-2010-3679?

    CVE-2010-3679 affects MySQL versions 5.1.5 through 5.1.48.

  • Is CVE-2010-3679 a remote vulnerability?

    Yes, CVE-2010-3679 can be exploited by a remote attacker.

  • What type of attack can exploit CVE-2010-3679?

    CVE-2010-3679 can be exploited to cause denial of service, leading to a crash of the mysqld daemon.

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