CVE-2010-3679: Medium severity MySQL mysql vulnerability
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] 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=54393
Upstream changeset: [4] http://lists.mysql.com/commits/111591
Note: The impact of this flaw is further mitigated by the requirement only privileged user can run the BINLOG statement.
Other sources
Oracle MySQL 5.1 before 5.1.49 allows remote authenticated users to cause a denial of service (mysqld daemon crash) via certain arguments to the BINLOG command, which triggers an access of uninitialized memory, as demonstrated by valgrind.
Affected Software
Remediation
Patch Available
Patch Available
Patch Available
Event History
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.