NeXT NeXTstep 1.0/1.0a npd 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.
8.0$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in NeXT NeXTstep 1.0/1.0a. This vulnerability affects unknown code of the component npd. This manipulation causes Local Privilege Escalation. This vulnerability is handled as CVE-1999-1391. There is not any exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability has been found in NeXT NeXTstep 1.0/1.0a and classified as critical. Affected by this vulnerability is some unknown processing of the component npd. The manipulation with an unknown input leads to a local privilege escalation vulnerability. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

vulnerability in next 1.0a and 1.0 with publicly accessible printers allows local users to gain privileges via a combination of the npd program and weak directory permissions.

The weakness was released 10/03/1990 (Website). The advisory is shared at cert.org. This vulnerability is known as CVE-1999-1391. The exploitation appears to be easy. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.

Upgrading to version 2.0 eliminates this vulnerability.

The vulnerability is also documented in the databases at X-Force (7143) and SecurityFocus (BID 10†). Entries connected to this vulnerability are available at VDB-13620 and VDB-13622. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.4
VulDB Meta Temp Score: 8.0

VulDB Base Score: 8.4
VulDB Temp Score: 8.0
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: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: NeXTstep 2.0

Timelineinfo

10/02/1990 🔍
10/03/1990 +1 days 🔍
10/03/1990 +0 days 🔍
06/16/2014 +8657 days 🔍
06/08/2024 +3645 days 🔍

Sourcesinfo

Advisory: cert.org
Status: Not defined

CVE: CVE-1999-1391 (🔍)
GCVE (CVE): GCVE-0-1999-1391
GCVE (VulDB): GCVE-100-13621
X-Force: 7143
SecurityFocus: 10 - NeXTstep npd Vulnerability

See also: 🔍

Entryinfo

Created: 06/16/2014 15:30
Updated: 06/08/2024 13:54
Changes: 06/16/2014 15:30 (40), 04/03/2019 11:19 (12), 06/08/2024 13:54 (17)
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 ▸

Want to know what is going to be exploited?

We predict KEV entries!