CVE-2005-0081
First published: Thu Apr 14 2005(Updated: )
MySQL MaxDB 7.5.0.0, and other versions before 7.5.0.21, allows remote attackers to cause a denial of service (crash) via an HTTP request with invalid headers.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| MySQL MaxDB | =7.5.00 | |
| MySQL MaxDB | =7.5.00.18 | |
| 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.19 | |
| MySQL MaxDB | =7.5.00.11 | |
| MySQL MaxDB | =7.5.00.08 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2005-0081?
CVE-2005-0081 is classified as a denial of service vulnerability.
How do I fix CVE-2005-0081?
To fix CVE-2005-0081, upgrade MySQL MaxDB to version 7.5.0.21 or later.
What software versions are affected by CVE-2005-0081?
CVE-2005-0081 affects MySQL MaxDB versions prior to 7.5.0.21.
Can CVE-2005-0081 be exploited remotely?
Yes, CVE-2005-0081 can be exploited by remote attackers.
What type of attack does CVE-2005-0081 facilitate?
CVE-2005-0081 facilitates a denial of service attack that can cause the application to crash.
- agent/author
- agent/description
- agent/event
- agent/first-publish-date
- agent/last-modified-date
- agent/references
- agent/remedy
- agent/severity
- agent/softwarecombine
- agent/tags
- agent/type
- agent/weakness
- collector/nvd-historical
- vendor/mysql
- vendor/maxdb
- collector/nvd-index
- canonical/mysql maxdb
- version/mysql maxdb/7.5.00
- version/mysql maxdb/7.5.00.18
- 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.19
- version/mysql maxdb/7.5.00.11
- version/mysql maxdb/7.5.00.08