Digital Ultrix 4.2 /usr/bin/mail Local Privilege Escalation

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.
5.9$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in Digital Ultrix 4.2. The affected element is an unknown function of the file /usr/bin/mail. Performing a manipulation results in Local Privilege Escalation. This vulnerability is known as CVE-1999-1415. No exploit is available.

Detailsinfo

A vulnerability classified as problematic has been found in Digital Ultrix 4.2. This affects some unknown processing of the file /usr/bin/mail. The manipulation with an unknown input leads to a local privilege escalation vulnerability. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

vulnerability in /usr/bin/mail in dec ultrix before 4.2 allows local users to gain privileges.

The weakness was published 08/23/1991 (Website). It is possible to read the advisory at cert.org. This vulnerability is uniquely identified as CVE-1999-1415. The exploitability is told to be easy. Attacking locally is a requirement. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 27†). Similar entry is available at VDB-13631. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.9
VulDB Meta Temp Score: 5.9

VulDB Base Score: 5.9
VulDB Temp Score: 5.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Local Privilege Escalation
CWE: Unknown
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: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

08/23/1991 🔍
08/23/1991 +0 days 🔍
08/23/1991 +0 days 🔍
06/16/2014 +8333 days 🔍
04/03/2025 +3944 days 🔍

Sourcesinfo

Advisory: cert.org
Status: Not defined

CVE: CVE-1999-1415 (🔍)
GCVE (CVE): GCVE-0-1999-1415
GCVE (VulDB): GCVE-100-13635
SecurityFocus: 27

See also: 🔍

Entryinfo

Created: 06/16/2014 15:30
Updated: 04/03/2025 05:35
Changes: 06/16/2014 15:30 (43), 05/17/2018 09:07 (6), 04/03/2025 05:35 (16)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!