Menu

Star on GitHub · 3.2k

CVE-2002-0248

7.2 · HIGH

wmtv 0.6.5 and earlier allows local users to modify arbitrary files via a symlink attack on a configuration file.

Published May 29, 2002wliangEPSS 0.35%

Overview

CVE-2002-0248 is a high-severity vulnerability affecting wliang wmtv. It was published on May 29, 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

wmtv 0.6.5 and earlier allows local users to modify arbitrary files via a symlink attack on a configuration file.

Remediation

Check the references section for vendor advisories and patches from wliang. Update wmtv 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
wliangwmtv0Affected

Frequently asked questions

What is CVE-2002-0248?

CVE-2002-0248 is a high-severity vulnerability affecting wliang wmtv. It was published on May 29, 2002 and has a CVSS 2.0 base score of 7.2 (HIGH).

How severe is CVE-2002-0248?

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-0248?

Check the references section for vendor advisories and patches from wliang. Update wmtv 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-0248?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2002-0248 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