Race condition in signal handling of procmail 3.20 and earlier, when running setuid, allows local users to cause a denial of service or gain
Race condition in signal handling of procmail 3.20 and earlier, when running setuid, allows local users to cause a denial of service or gain root privileges by sending a signal while a signal handling routine is already running.
- Published
- Oct 18, 2001
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 23th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
24
Monitor
Low priority for now.
- CVSS
- 24 / 40 · 6.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| procmail | procmail | cpe:2.3:a:procmail:procmail |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- procmail procmailup to 3.20 inclusive
Same product
procmail: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-16844Heap-based buffer overflow in the loadbuf function in formisc.c in formail in procmail 3.22 allows remote attackers to cause a denial of ser43Plan
- CVE-2014-3618Heap-based buffer overflow in formisc.c in formail in procmail 3.22 allows remote attackers to cause a denial of service (crash) and possibl33Monitor
- CVE-1999-0439Buffer overflow in procmail before version 3.12 allows remote or local attackers to execute commands via expansions in the procmailrc config31Monitor
- CVE-1999-0475A race condition in how procmail handles .procmailrc files allows a local user to read arbitrary files available to the user who is running 4Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- C · the service can be disrupted
- Attack complexity
- High
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- C
Weakness class (CWE)
—
CVSS vector
AV:L/AC:H/Au:N/C:C/I:C/A:C
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-01:60.procmail.asc
- distro.conectiva.com.br/atualizacoes/?id=a&anuncio=000433
- www.debian.org/security/2001/dsa-083
- www.linux-mandrake.com/en/security/2001/MDKSA-2001-085.php3
- www.redhat.com/support/errata/RHSA-2001-093.html
- www.securityfocus.com/bid/3071
- exchange.xforce.ibmcloud.com/vulnerabilities/6872
Vendor advisories and official records. Exploit/PoC links are deliberately left out.