CVE-2004-0931: Medium severity MySQL MaxDB vulnerability
Published Dec 31, 2004
·Updated
MySQL MaxDB before 7.5.00.18 allows remote attackers to cause a denial of service (crash) via an HTTP request to webdbm with high ASCII values in the Server field, which triggers an assert error in the IsAscii7 function.
Affected Software
6 affected components
MySQL MaxDB=7.5.00.15
MySQL MaxDB=7.5.00.12
MySQL MaxDB=7.5.00.16
MySQL MaxDB=7.5.00.14
MySQL MaxDB=7.5.00.11
MySQL MaxDB=7.5.00.08
Remediation
Patch Available
Patch Available
Event History
Dec 31, 2004
CVE Published
05:00 AM
Jan 19, 2005
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2004-0931?
CVE-2004-0931 is classified as a denial of service vulnerability which can lead to crashes of the MySQL MaxDB server.
2
How do I fix CVE-2004-0931?
To mitigate CVE-2004-0931, upgrade to MySQL MaxDB version 7.5.00.18 or later.
3
Which versions of MySQL MaxDB are affected by CVE-2004-0931?
CVE-2004-0931 affects MySQL MaxDB versions 7.5.00.11, 7.5.00.12, 7.5.00.14, 7.5.00.15, and 7.5.00.16.
4
What type of attack is associated with CVE-2004-0931?
CVE-2004-0931 is associated with remote denial of service attacks triggered by malformed HTTP requests.
5
Can I be at risk if I use a version of MySQL MaxDB earlier than 7.5.00.18?
Yes, using any version of MySQL MaxDB prior to 7.5.00.18 exposes your system to risks from CVE-2004-0931.