Menu

Star on GitHub · 3.2k

CVE-2002-0137

7.2 · HIGH

CDRDAO 1.1.4 and 1.1.5 allows local users to overwrite arbitrary files via a symlink attack on the $HOME/.cdrdao configuration file.

Published Mar 25, 2002andreas_muellerEPSS 0.75%

Overview

CVE-2002-0137 is a high-severity vulnerability affecting andreas_mueller cdrdao. It was published on March 25, 2002 and has a CVSS 2.0 base score of 7.2 (HIGH).

This vulnerability has a CVSS 2.0 base score of 7.2, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

CDRDAO 1.1.4 and 1.1.5 allows local users to overwrite arbitrary files via a symlink attack on the $HOME/.cdrdao configuration file.

Remediation

Check the references section for vendor advisories and patches from andreas_mueller. Update cdrdao to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2002-0137?

CVE-2002-0137 is a high-severity vulnerability affecting andreas_mueller cdrdao. It was published on March 25, 2002 and has a CVSS 2.0 base score of 7.2 (HIGH).

How severe is CVE-2002-0137?

This vulnerability has a CVSS 2.0 base score of 7.2, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2002-0137?

Check the references section for vendor advisories and patches from andreas_mueller. Update cdrdao to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2002-0137?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2002-0137 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2002

View all