CVE-2005-0082: Medium severity mysql maxdb vulnerability

Published Jan 20, 2005

Updated

The sapdbwaGetUserData function in 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 invalid parameters to the WebDAV handler code, which triggers a null dereference that causes the SAP DB Web Agent to crash.

Affected Software

9 affected components

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

Remediation

Patch Available

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

Event History

Jan 20, 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-0082?

CVE-2005-0082 is considered to have a high severity due to its potential to cause denial of service.

How do I fix CVE-2005-0082?

To fix CVE-2005-0082, it is recommended to upgrade MySQL MaxDB to version 7.5.0.21 or later.

What versions of MySQL MaxDB are affected by CVE-2005-0082?

CVE-2005-0082 affects MySQL MaxDB versions before 7.5.0.21, including versions 7.5.0.0 through 7.5.0.20.

What impact does CVE-2005-0082 have on MySQL MaxDB?

CVE-2005-0082 can cause a crash of the SAP DB Web Agent, resulting in a denial of service.

Is there a workaround for CVE-2005-0082?

There is no official workaround for CVE-2005-0082; upgrading to a patched version is the only solution.