Menu

Star on GitHub · 3.2k

CVE-1999-0475

1.2 · LOW

A race condition in how procmail handles .procmailrc files allows a local user to read arbitrary files available to the user who is running procmail.

Published Apr 5, 1999procmailEPSS 0.32%

Overview

CVE-1999-0475 is a low-severity vulnerability affecting procmail procmail. It was published on April 5, 1999 and has a CVSS 2.0 base score of 1.2 (LOW).

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

Technical description

A race condition in how procmail handles .procmailrc files allows a local user to read arbitrary files available to the user who is running procmail.

Remediation

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

CVE-1999-0475 is a low-severity vulnerability affecting procmail procmail. It was published on April 5, 1999 and has a CVSS 2.0 base score of 1.2 (LOW).

How severe is CVE-1999-0475?

This vulnerability has a CVSS 2.0 base score of 1.2, 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-1999-0475?

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

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