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.

How do I fix CVE-2004-0931?

To mitigate CVE-2004-0931, upgrade to MySQL MaxDB version 7.5.00.18 or later.

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.

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.

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.

Vulnerability/
CVE-2004-0931

medium

CWE

NVD-CWE-Other

31/12/2004

19/1/2005

8/8/2024

CVE-2004-0931

First published: Fri 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.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
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

Remedy

http://www.secunia.com/advisories/12756

Remedy

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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

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.
How do I fix CVE-2004-0931?
To mitigate CVE-2004-0931, upgrade to MySQL MaxDB version 7.5.00.18 or later.
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.
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.
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.

collector/nvd-historical
collector/nvd-index
agent/type
agent/remedy
agent/first-publish-date
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/references
agent/severity
agent/weakness
agent/author
agent/last-modified-date
agent/tags
agent/description
agent/event
agent/source
vendor/mysql
canonical/mysql maxdb
version/mysql maxdb/7.5.00.15
version/mysql maxdb/7.5.00.12
version/mysql maxdb/7.5.00.16
version/mysql maxdb/7.5.00.14
version/mysql maxdb/7.5.00.11
version/mysql maxdb/7.5.00.08

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.