CVE-2005-0083: Medium severity MySQL MaxDB vulnerability

Published Mar 17, 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) DBMCliString::ReallocString, (2) DBMCliString::operator, (3) DBMCliBuffer::ForceResize, (4) DBMCliWizard::InstallDatabase, (5) DBMCliDevspaces::Complete, (6) DBMWebTemplateWizard::askForWriteCountStep5, or (7) DBMWebDBMWeb::wizardDB functions, which triggers a null dereference.

Affected Software

1 affected component

MySQL MaxDB=7.5.00

Remediation

Patch Available

http://www.idefense.com/application/poi/display?id=218&type=vulnerabilities

Event History

Mar 17, 2005

CVE Published

via MITRE·05:00 AM

Data Sourced

via MITRE·05:00 AM

Description

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.