What is the severity of CVE-2002-2001?

CVE-2002-2001 is considered a medium severity vulnerability due to the potential for local file overwriting through a symlink attack.

How do I fix CVE-2002-2001?

To fix CVE-2002-2001, you should update jmcce to a version that does not create predictable log file names.

Who is affected by CVE-2002-2001?

Users of jmcce version 1.3.8 on Mandrake Linux 8.1 are primarily affected by CVE-2002-2001.

What type of attack does CVE-2002-2001 enable?

CVE-2002-2001 enables local users to conduct a symlink attack to overwrite arbitrary files.

When was CVE-2002-2001 disclosed?

CVE-2002-2001 was disclosed in the year 2002.

Vulnerability/
CVE-2002-2001

low

1.2

CWE

NVD-CWE-Other

31/12/2002

14/7/2005

8/8/2024

CVE-2002-2001

First published: Tue Dec 31 2002(Updated: )

jmcce 1.3.8 in Mandrake 8.1 creates log files in /tmp with predictable names, which allows local users to overwrite arbitrary files via a symlink attack.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
jmcce jmcce	=1.3.8
Mandrake Linux	=8.1

Remedy

http://www.iss.net/security_center/static/7980.php

Remedy

http://www.securityfocus.com/bid/3940

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2002-2001?
CVE-2002-2001 is considered a medium severity vulnerability due to the potential for local file overwriting through a symlink attack.
How do I fix CVE-2002-2001?
To fix CVE-2002-2001, you should update jmcce to a version that does not create predictable log file names.
Who is affected by CVE-2002-2001?
Users of jmcce version 1.3.8 on Mandrake Linux 8.1 are primarily affected by CVE-2002-2001.
What type of attack does CVE-2002-2001 enable?
CVE-2002-2001 enables local users to conduct a symlink attack to overwrite arbitrary files.
When was CVE-2002-2001 disclosed?
CVE-2002-2001 was disclosed in the year 2002.

agent/type
agent/remedy
agent/first-publish-date
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/references
agent/severity
agent/weakness
agent/author
agent/description
agent/event
agent/source
agent/tags
agent/softwarecombine
collector/nvd-historical
agent/software-canonical-lookup-request
collector/nvd-index
vendor/jmcce
canonical/jmcce jmcce
version/jmcce jmcce/1.3.8
vendor/mandrakesoft
canonical/mandrake linux
version/mandrake linux/8.1

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-2002-2001?
CVE-2002-2001 is considered a medium severity vulnerability due to the potential for local file overwriting through a symlink attack.
How do I fix CVE-2002-2001?
To fix CVE-2002-2001, you should update jmcce to a version that does not create predictable log file names.
Who is affected by CVE-2002-2001?
Users of jmcce version 1.3.8 on Mandrake Linux 8.1 are primarily affected by CVE-2002-2001.
What type of attack does CVE-2002-2001 enable?
CVE-2002-2001 enables local users to conduct a symlink attack to overwrite arbitrary files.
When was CVE-2002-2001 disclosed?
CVE-2002-2001 was disclosed in the year 2002.