CVE-2007-1420: Low severity MySQL mysql vulnerability

Q: What is the severity of CVE-2007-1420?

CVE-2007-1420 is considered a moderate severity vulnerability due to its potential to cause a denial of service.

Q: How do I fix CVE-2007-1420?

To fix CVE-2007-1420, upgrade MySQL to version 5.0.36 or later.

Q: What versions of MySQL are affected by CVE-2007-1420?

CVE-2007-1420 affects MySQL versions prior to 5.0.36, including multiple 5.0.x releases.

Q: What kind of attack exploits CVE-2007-1420?

CVE-2007-1420 can be exploited through specific information_schema table queries that trigger a database crash.

Q: Is there a known workaround for CVE-2007-1420?

There are no known workarounds for CVE-2007-1420 aside from upgrading to a secure version of MySQL.

Published Mar 12, 2007

Updated

MySQL 5.x before 5.0.36 allows local users to cause a denial of service (database crash) by performing informationschema 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.

Affected Software

18 affected components

MySQL mysql=5.0.5

MySQL mysql=5.0.10

MySQL mysql=5.0.0

MySQL mysql=5.0.15

MySQL mysql=5.0.17

MySQL mysql=5.0.3

MySQL mysql<=5.0.33

MySQL mysql=5.0.24

MySQL mysql=5.0.2

MySQL mysql=5.0.30

MySQL mysql=5.0.20

MySQL mysql=5.0.1

MySQL mysql=5.0.4

MySQL mysql=5.0.16

Oracle MySQL=5.0.6

Oracle MySQL=5.0.32

Oracle MySQL=5.0.41

Oracle MySQL=5.0.7

Remediation

Patch Available

http://www.securityfocus.com/bid/22900

Event History

Mar 12, 2007

CVE Published

11:19 PM

Mar 13, 2007

CVE Published

via MITRE·03:00 AM

Data Sourced

via MITRE·03:00 AM

Description

Frequently Asked Questions

What is the severity of CVE-2007-1420?

CVE-2007-1420 is considered a moderate severity vulnerability due to its potential to cause a denial of service.

How do I fix CVE-2007-1420?