CVE-2010-3683: Medium severity MySQL mysql vulnerability
MySQL improperly handled LOAD DATA INFILE requests (it did not check for SQL errors and sent an OK packet even when errors were already reported). A remote, authenticated MySQL user could use this flaw to cause mysqld daemon abort (assertion failure).
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=52512
Upstream changeset: [4] http://lists.mysql.com/commits/105163
Other sources
Oracle MySQL 5.1 before 5.1.49 and 5.5 before 5.5.5 sends an OK packet when a LOAD DATA INFILE request generates SQL errors, which allows remote authenticated users to cause a denial of service (mysqld daemon crash) via a crafted request.
Affected Software
Remediation
Patch Available
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2010-3683?
CVE-2010-3683 is classified as a moderate severity vulnerability.
How do I fix CVE-2010-3683?
To fix CVE-2010-3683, upgrade MySQL to version 5.1.52 or later, or apply the recommended security patch.
Who is affected by CVE-2010-3683?
CVE-2010-3683 affects remote, authenticated users of MySQL versions prior to 5.1.52.
What is the impact of CVE-2010-3683?
The impact of CVE-2010-3683 can lead to a mysqld daemon abort due to an assertion failure.
Is CVE-2010-3683 easy to exploit?
CVE-2010-3683 can be exploited remotely by authenticated users, making it a notable risk if not mitigated.