Menu

Star on GitHub · 3.2k

CVE-1999-0439

7.5 · HIGH

Buffer overflow in procmail before version 3.12 allows remote or local attackers to execute commands via expansions in the procmailrc configuration file.

Published Apr 5, 1999procmailEPSS 2.53%

Overview

CVE-1999-0439 is a high-severity vulnerability affecting procmail procmail. It was published on April 5, 1999 and has a CVSS 2.0 base score of 7.5 (HIGH).

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

Buffer overflow in procmail before version 3.12 allows remote or local attackers to execute commands via expansions in the procmailrc configuration file.

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
procmailprocmail0Affected

Frequently asked questions

What is CVE-1999-0439?

CVE-1999-0439 is a high-severity vulnerability affecting procmail procmail. It was published on April 5, 1999 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-1999-0439?

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

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

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

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