First published: Wed Nov 04 2009(Updated: )
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 null_value 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.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/mysql | <0:5.0.77-4.el5_4.2 | 0:5.0.77-4.el5_4.2 |
MySQL (MySQL-common) | =5.0.5 | |
MySQL (MySQL-common) | =5.0.10 | |
MySQL (MySQL-common) | =5.0.54 | |
MySQL (MySQL-common) | =5.0.0 | |
MySQL (MySQL-common) | =5.1.23 | |
MySQL (MySQL-common) | =5.0.15 | |
MySQL (MySQL-common) | =5.0.17 | |
MySQL (MySQL-common) | =5.0.5.0.21 | |
MySQL (MySQL-common) | =5.0.3 | |
MySQL (MySQL-common) | =5.0.44 | |
MySQL (MySQL-common) | =5.0.66 | |
MySQL (MySQL-common) | =5.0.56 | |
MySQL (MySQL-common) | =5.0.60 | |
MySQL (MySQL-common) | =5.0.24 | |
MySQL (MySQL-common) | =5.0.2 | |
MySQL (MySQL-common) | =5.0.22.1.0.1 | |
MySQL (MySQL-common) | =5.0.30 | |
MySQL (MySQL-common) | =5.0.20 | |
MySQL (MySQL-common) | =5.0.1 | |
MySQL (MySQL-common) | =5.0.4 | |
MySQL (MySQL-common) | =5.0.82 | |
MySQL (MySQL-common) | =5.0.36 | |
MySQL (MySQL-common) | =5.1.32 | |
MySQL (MySQL-common) | =5.0.16 | |
MySQL (MySQL-common) | =5.1.5 | |
Oracle MySQL | =5.0.50 | |
Oracle MySQL | =5.0.51 | |
Oracle MySQL | =5.0.51a | |
Oracle MySQL | =5.0.0-alpha | |
Oracle MySQL | =5.0.3-beta | |
Oracle MySQL | =5.0.6 | |
Oracle MySQL | =5.0.11 | |
Oracle MySQL | =5.0.12 | |
Oracle MySQL | =5.0.13 | |
Oracle MySQL | =5.0.14 | |
Oracle MySQL | =5.0.18 | |
Oracle MySQL | =5.0.19 | |
Oracle MySQL | =5.0.21 | |
Oracle MySQL | =5.0.22 | |
Oracle MySQL | =5.0.23 | |
Oracle MySQL | =5.0.25 | |
Oracle MySQL | =5.0.26 | |
Oracle MySQL | =5.0.27 | |
Oracle MySQL | =5.0.30-sp1 | |
Oracle MySQL | =5.0.32 | |
Oracle MySQL | =5.0.33 | |
Oracle MySQL | =5.0.37 | |
Oracle MySQL | =5.0.38 | |
Oracle MySQL | =5.0.41 | |
Oracle MySQL | =5.0.42 | |
Oracle MySQL | =5.0.45 | |
Oracle MySQL | =5.0.52 | |
Oracle MySQL | =5.0.7 | |
Oracle MySQL | =5.0.8 | |
Oracle MySQL | =5.0.75 | |
Oracle MySQL | =5.0.77 | |
Oracle MySQL | =5.0.81 | |
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.30 | |
Oracle MySQL | =5.0.83 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2009-4019 has a severity rating classified as high due to its potential impact on remote authentication.
To fix CVE-2009-4019, upgrade your MySQL server to version 5.0.88, 5.1.41 or higher.
CVE-2009-4019 affects MySQL versions prior to 5.0.88 and 5.1.41.
The risks associated with CVE-2009-4019 include possible remote code execution and unauthorized access to sensitive data.
There are no reliable workarounds for CVE-2009-4019, so upgrading is the recommended action.