What is the severity of CVE-2004-0457?

CVE-2004-0457 is considered a moderate severity vulnerability due to its potential for local users to exploit the symlink attack.

How do I fix CVE-2004-0457?

To fix CVE-2004-0457, upgrade to MySQL version 4.0.21 or later which addresses this issue.

What are the potential impacts of CVE-2004-0457?

The potential impact of CVE-2004-0457 includes unauthorized overwriting of arbitrary files by local users.

Who is primarily affected by CVE-2004-0457?

Local users of MySQL version 4.0.20 and earlier are primarily affected by CVE-2004-0457.

What system components are involved in CVE-2004-0457?

The mysqlhotcopy script in the MySQL server package is involved in CVE-2004-0457.

Vulnerability/
CVE-2004-0457

medium

4.6

CWE

NVD-CWE-Other

19/8/2004

8/8/2024

CVE-2004-0457

First published: Thu Aug 19 2004(Updated: )

The mysqlhotcopy script in mysql 4.0.20 and earlier, when using the scp method from the mysql-server package, allows local users to overwrite arbitrary files via a symlink attack on temporary files.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
MySQL	<=4.0.20

Remedy

http://www.redhat.com/support/errata/RHSA-2004-597.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2004-0457?
CVE-2004-0457 is considered a moderate severity vulnerability due to its potential for local users to exploit the symlink attack.
How do I fix CVE-2004-0457?
To fix CVE-2004-0457, upgrade to MySQL version 4.0.21 or later which addresses this issue.
What are the potential impacts of CVE-2004-0457?
The potential impact of CVE-2004-0457 includes unauthorized overwriting of arbitrary files by local users.
Who is primarily affected by CVE-2004-0457?
Local users of MySQL version 4.0.20 and earlier are primarily affected by CVE-2004-0457.
What system components are involved in CVE-2004-0457?
The mysqlhotcopy script in the MySQL server package is involved in CVE-2004-0457.

agent/references
agent/type
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/remedy
agent/author
agent/weakness
agent/description
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-historical
agent/softwarecombine
vendor/oracle
canonical/mysql
version/mysql/4.0.20

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-2004-0457?
CVE-2004-0457 is considered a moderate severity vulnerability due to its potential for local users to exploit the symlink attack.
How do I fix CVE-2004-0457?
To fix CVE-2004-0457, upgrade to MySQL version 4.0.21 or later which addresses this issue.
What are the potential impacts of CVE-2004-0457?
The potential impact of CVE-2004-0457 includes unauthorized overwriting of arbitrary files by local users.
Who is primarily affected by CVE-2004-0457?
Local users of MySQL version 4.0.20 and earlier are primarily affected by CVE-2004-0457.
What system components are involved in CVE-2004-0457?
The mysqlhotcopy script in the MySQL server package is involved in CVE-2004-0457.