What is the severity of CVE-2003-0073?

CVE-2003-0073 has a severity rating that indicates it can cause a denial of service.

How do I fix CVE-2003-0073?

To fix CVE-2003-0073, upgrade MySQL to version 3.23.55 or later.

Which versions of MySQL are affected by CVE-2003-0073?

CVE-2003-0073 affects MySQL versions 3.23.31 through 3.23.54a.

What kind of attack does CVE-2003-0073 facilitate?

CVE-2003-0073 facilitates a denial of service attack through a double-free vulnerability.

Who is vulnerable to CVE-2003-0073?

Users with MySQL access to affected versions of MySQL are vulnerable to CVE-2003-0073.

Vulnerability/
CVE-2003-0073

medium

CWE

NVD-CWE-Other

19/2/2003

1/9/2004

8/8/2024

CVE-2003-0073

First published: Wed Feb 19 2003(Updated: )

Double-free vulnerability in mysqld for MySQL before 3.23.55 allows attackers with MySQL access to cause a denial of service (crash) via mysql_change_user.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
MySQL	=3.23.31
MySQL	=3.23.36
MySQL	=3.23.41
MySQL	=3.23.47
MySQL	=3.23.52
MySQL	=3.23.53
MySQL	=3.23.54
MySQL	=3.23.54a

Remedy

http://www.debian.org/security/2003/dsa-303

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2003-0073?
CVE-2003-0073 has a severity rating that indicates it can cause a denial of service.
How do I fix CVE-2003-0073?
To fix CVE-2003-0073, upgrade MySQL to version 3.23.55 or later.
Which versions of MySQL are affected by CVE-2003-0073?
CVE-2003-0073 affects MySQL versions 3.23.31 through 3.23.54a.
What kind of attack does CVE-2003-0073 facilitate?
CVE-2003-0073 facilitates a denial of service attack through a double-free vulnerability.
Who is vulnerable to CVE-2003-0073?
Users with MySQL access to affected versions of MySQL are vulnerable to CVE-2003-0073.

agent/references
agent/type
agent/first-publish-date
collector/mitre-cve
source/MITRE
agent/weakness
agent/remedy
agent/author
agent/severity
agent/last-modified-date
agent/event
agent/description
agent/source
agent/tags
collector/nvd-historical
agent/software-canonical-lookup-request
collector/nvd-index
agent/softwarecombine
vendor/oracle
canonical/mysql
version/mysql/3.23.31
version/mysql/3.23.36
version/mysql/3.23.41
version/mysql/3.23.47
version/mysql/3.23.52
version/mysql/3.23.53
version/mysql/3.23.54
version/mysql/3.23.54a

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.

Frequently Asked Questions

What is the severity of CVE-2003-0073?
CVE-2003-0073 has a severity rating that indicates it can cause a denial of service.
How do I fix CVE-2003-0073?
To fix CVE-2003-0073, upgrade MySQL to version 3.23.55 or later.
Which versions of MySQL are affected by CVE-2003-0073?
CVE-2003-0073 affects MySQL versions 3.23.31 through 3.23.54a.
What kind of attack does CVE-2003-0073 facilitate?
CVE-2003-0073 facilitates a denial of service attack through a double-free vulnerability.
Who is vulnerable to CVE-2003-0073?
Users with MySQL access to affected versions of MySQL are vulnerable to CVE-2003-0073.