Procmail .procmailrc privileges management

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
2.8$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in Procmail. Affected by this vulnerability is an unknown functionality of the file .procmailrc. The manipulation leads to privileges management. This vulnerability is uniquely identified as CVE-1999-0475. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Procmail (Mail Server Software) (affected version not known). It has been rated as problematic. This issue affects some unknown functionality of the file .procmailrc. The manipulation with an unknown input leads to a privileges management vulnerability. Using CWE to declare the problem leads to CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. Impacted is confidentiality. The summary by CVE is:

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.

The weakness was disclosed 04/05/1999. The identification of this vulnerability is CVE-1999-0475. The exploitation is known to be difficult. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

Upgrading eliminates this vulnerability.

The vulnerability is also documented in the databases at X-Force (2083) and Vulnerability Center (SBV-617†). The entry VDB-14595 is pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 2.9
VulDB Meta Temp Score: 2.8

VulDB Base Score: 2.9
VulDB Temp Score: 2.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Privileges management
CWE: CWE-269 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Timelineinfo

04/05/1999 🔍
04/05/1999 +0 days 🔍
04/05/1999 +0 days 🔍
12/31/2002 +1366 days 🔍
06/20/2014 +4189 days 🔍
04/19/2026 +4320 days 🔍

Sourcesinfo

Status: Confirmed

CVE: CVE-1999-0475 (🔍)
GCVE (CVE): GCVE-0-1999-0475
GCVE (VulDB): GCVE-100-14597
X-Force: 2083
Vulnerability Center: 617 - Procmail - Read Files in The User Machine, Low

See also: 🔍

Entryinfo

Created: 06/20/2014 23:22
Updated: 04/19/2026 01:15
Changes: 06/20/2014 23:22 (35), 05/07/2019 22:11 (16), 04/19/2026 01:15 (18)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!