Menu

Star on GitHub · 3.2k

CVE-2002-1193

2.1 · LOW

tkmail before 4.0beta9-8.1 allows local users to create or overwrite files as users via a symlink attack on temporary files.

Published Oct 28, 2002tkmailEPSS 0.34%

Overview

CVE-2002-1193 is a low-severity vulnerability affecting tkmail tkmail. It was published on October 28, 2002 and has a CVSS 2.0 base score of 2.1 (LOW).

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

Technical description

tkmail before 4.0beta9-8.1 allows local users to create or overwrite files as users via a symlink attack on temporary files.

Remediation

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

CVE-2002-1193 is a low-severity vulnerability affecting tkmail tkmail. It was published on October 28, 2002 and has a CVSS 2.0 base score of 2.1 (LOW).

How severe is CVE-2002-1193?

This vulnerability has a CVSS 2.0 base score of 2.1, rated LOW. 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-1193?

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

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

View all