First published: Mon Mar 12 2007(Updated: )
MySQL 5.x before 5.0.36 allows local users to cause a denial of service (database crash) by performing information_schema table subselects and using ORDER BY to sort a single-row result, which prevents certain structure elements from being initialized and triggers a NULL dereference in the filesort function.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
MySQL Server | =5.0.5 | |
MySQL Server | =5.0.10 | |
MySQL Server | =5.0.0 | |
MySQL Server | =5.0.15 | |
MySQL Server | =5.0.17 | |
MySQL Server | =5.0.3 | |
MySQL Server | <=5.0.33 | |
MySQL Server | =5.0.24 | |
MySQL Server | =5.0.2 | |
MySQL Server | =5.0.30 | |
MySQL Server | =5.0.20 | |
MySQL Server | =5.0.1 | |
MySQL Server | =5.0.4 | |
MySQL Server | =5.0.16 | |
MySQL | =5.0.6 | |
MySQL | =5.0.32 | |
MySQL | =5.0.41 | |
MySQL | =5.0.7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2007-1420 is considered a moderate severity vulnerability due to its potential to cause a denial of service.
To fix CVE-2007-1420, upgrade MySQL to version 5.0.36 or later.
CVE-2007-1420 affects MySQL versions prior to 5.0.36, including multiple 5.0.x releases.
CVE-2007-1420 can be exploited through specific information_schema table queries that trigger a database crash.
There are no known workarounds for CVE-2007-1420 aside from upgrading to a secure version of MySQL.