Menu

Star on GitHub · 3.2k

CVE-1999-1590

3.5 · LOW

Directory traversal vulnerability in Muhammad A.

Published Dec 31, 1999wwwcountEPSS 1.07%

Overview

CVE-1999-1590 is a low-severity vulnerability affecting wwwcount wwwcount. It was published on December 31, 1999 and has a CVSS 2.0 base score of 3.5 (LOW).

This vulnerability has a CVSS 2.0 base score of 3.5, rated LOW. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

Directory traversal vulnerability in Muhammad A. Muquit wwwcount (Count.cgi) 2.3 allows remote attackers to read arbitrary GIF files via ".." sequences in the image parameter, a different vulnerability than CVE-1999-0021.

Remediation

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

CVE-1999-1590 is a low-severity vulnerability affecting wwwcount wwwcount. It was published on December 31, 1999 and has a CVSS 2.0 base score of 3.5 (LOW).

How severe is CVE-1999-1590?

This vulnerability has a CVSS 2.0 base score of 3.5, rated LOW. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-1999-1590?

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

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

View all