CVE-2005-0083
First published: Mon May 02 2005(Updated: )
MySQL MaxDB 7.5.00 for Windows, and possibly earlier versions and other platforms, allows remote attackers to cause a denial of service (application crash) via invalid parameters to the (1) DBMCli_String::ReallocString, (2) DBMCli_String::operator, (3) DBMCli_Buffer::ForceResize, (4) DBMCli_Wizard::InstallDatabase, (5) DBMCli_Devspaces::Complete, (6) DBMWeb_TemplateWizard::askForWriteCountStep5, or (7) DBMWeb_DBMWeb::wizardDB functions, which triggers a null dereference.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| MySQL MaxDB | =7.5.00 |
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.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2005-0083?
CVE-2005-0083 has a severity rating that indicates it can lead to denial of service, causing application crashes.
How do I fix CVE-2005-0083?
To address CVE-2005-0083, it is recommended to upgrade to a patched version of MySQL MaxDB that resolves the identified vulnerabilities.
Which versions of MySQL MaxDB are affected by CVE-2005-0083?
CVE-2005-0083 affects MySQL MaxDB version 7.5.00 and potentially earlier versions and other platforms.
What type of vulnerability is CVE-2005-0083?
CVE-2005-0083 is classified as a denial of service vulnerability that can be exploited remotely.
Are there any known exploits for CVE-2005-0083?
Yes, there are reports of remote attackers using invalid parameters to exploit CVE-2005-0083 and cause application crashes.
- 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
- collector/nvd-index
- vendor/mysql
- canonical/mysql maxdb
- version/mysql maxdb/7.5.00