Command execution via unchecked configuration expansion
Published Jan 4, 2000 · Updated Aug 1, 2024
Heap overflow in Procmail before 3.12 allows attackers to execute commands via oversized procmailrc configuration expansions. Expansion processing fails to verify available heap-buffer space before writing expanded values. Remote attackers require recipes that reuse message-derived data in expansions; local users can supply configuration input, with elevated access dependent on retained mail-group or root privileges.
Summary
What happened
Heap overflow in Procmail before 3.12 allows attackers to execute commands via oversized procmailrc configuration expansions. Expansion processing fails to verify available heap-buffer space before writing expanded values. Remote attackers require recipes that reuse message-derived data in expansions; local users can supply configuration input, with elevated access dependent on retained mail-group or root privileges.
The record
- CVE
- CVE-1999-0439
- Published
- Jan 4, 2000
- Updated
- Aug 1, 2024
- Vendor
- Procmail
- Product
- Procmail
- Classifications
- T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 4, 2000CVE publishedPublication date reported by the CVE source.
- Aug 1, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us