CVE-2005-2573: Medium severity MySQL mysql vulnerability

Published Aug 16, 2005
·
Updated

The mysqlcreatefunction function in sqludf.cc for MySQL 4.0 before 4.0.25, 4.1 before 4.1.13, and 5.0 before 5.0.7-beta, when running on Windows, uses an incomplete blacklist in a directory traversal check, which allows attackers to include arbitrary files via the backslash (\) character.

Affected Software

38 affected components
MySQL mysql=4.1.0
MySQL mysql=4.1.3
MySQL mysql=4.1.10
MySQL mysql=5.0.1
MySQL mysql=5.0.2
MySQL mysql=5.0.3
MySQL mysql=5.0.4
Oracle MySQL=4.0.0
Oracle MySQL=4.0.1
Oracle MySQL=4.0.2
Oracle MySQL=4.0.3
Oracle MySQL=4.0.4
Oracle MySQL=4.0.5
Oracle MySQL=4.0.5a
Oracle MySQL=4.0.6
Oracle MySQL=4.0.7
Oracle MySQL=4.0.7-gamma
Oracle MySQL=4.0.8
Oracle MySQL=4.0.8-gamma
Oracle MySQL=4.0.9
Oracle MySQL=4.0.9-gamma
Oracle MySQL=4.0.10
Oracle MySQL=4.0.11
Oracle MySQL=4.0.11-gamma
Oracle MySQL=4.0.12
Oracle MySQL=4.0.13
Oracle MySQL=4.0.14
Oracle MySQL=4.0.15
Oracle MySQL=4.0.18
Oracle MySQL=4.0.20
Oracle MySQL=4.0.21
Oracle MySQL=4.0.24
Oracle MySQL=4.1.0-alpha
Oracle MySQL=4.1.2-alpha
Oracle MySQL=4.1.3-beta
Oracle MySQL=4.1.4
Oracle MySQL=4.1.5
Oracle MySQL=5.0.0-alpha

Event History

Aug 16, 2005
CVE Published
04:00 AM
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2005-2573?

CVE-2005-2573 is classified as a medium severity vulnerability due to its potential for local file inclusion.

2

How do I fix CVE-2005-2573?

To fix CVE-2005-2573, upgrade to MySQL versions 4.0.25, 4.1.13, or 5.0.7-beta or later.

3

Which versions of MySQL are affected by CVE-2005-2573?

CVE-2005-2573 affects MySQL versions 4.0 before 4.0.25, 4.1 before 4.1.13, and 5.0 before 5.0.7-beta.

4

What kind of attacks can exploit CVE-2005-2573?

CVE-2005-2573 can be exploited to perform local file inclusion attacks, allowing unauthorized file access.

5

What is the root cause of CVE-2005-2573?

The root cause of CVE-2005-2573 is an incomplete blacklist in the directory traversal check of the mysql_create_function in affected MySQL versions.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203