CVE-2009-4019: Medium severity mysql vulnerability
Multiple denial of service flaws were found in MySQL SQL database server. Quoting from upstream 5.0.88 release notes:
Error handling was missing for SELECT statements containing subqueries in the WHERE clause and that assigned a SELECT result to a user variable. The server could crash as a result. (Bug#48291)
If the first argument to GeomFromWKB() function was a geometry value, the function just returned its value. However, it failed to preserve the argument's nullvalue flag, which caused an unexpected NULL value to be returned to the caller, resulting in a server crash. (Bug#47780)
References: ----------- http://dev.mysql.com/doc/refman/5.0/en/news-5-0-88.html (there are more DoS issues mentioned in the release notes, but this CVE was assigned to these two)
http://dev.mysql.com/doc/refman/5.1/en/news-5-1-41.html http://bugs.mysql.com/47780 http://bugs.mysql.com/48291
Upstream patches: ----------------- For Bug #48291 crash with row() operator,select into @var, and subquery returning multiple rows: http://lists.mysql.com/commits/88409 http://lists.mysql.com/commits/88741
For Bug #47780: crash when comparing GIS items from subquery: http://lists.mysql.com/commits/87591 http://lists.mysql.com/commits/88069
Other sources
mysqld in MySQL 5.0.x before 5.0.88 and 5.1.x before 5.1.41 does not (1) properly handle errors during execution of certain SELECT statements with subqueries, and does not (2) preserve certain nullvalue flags during execution of statements that use the GeomFromWKB function, which allows remote authenticated users to cause a denial of service (daemon crash) via a crafted statement.
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2009-4019?
CVE-2009-4019 has a severity rating classified as high due to its potential impact on remote authentication.
How do I fix CVE-2009-4019?
To fix CVE-2009-4019, upgrade your MySQL server to version 5.0.88, 5.1.41 or higher.
Which MySQL versions are affected by CVE-2009-4019?
CVE-2009-4019 affects MySQL versions prior to 5.0.88 and 5.1.41.
What are the risks associated with CVE-2009-4019?
The risks associated with CVE-2009-4019 include possible remote code execution and unauthorized access to sensitive data.
Is there a workaround for CVE-2009-4019 if I can't upgrade MySQL?
There are no reliable workarounds for CVE-2009-4019, so upgrading is the recommended action.