HP HP-UX 10 mstm memory corruption

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

Summaryinfo

A vulnerability marked as problematic has been reported in HP HP-UX 10. Affected by this issue is some unknown functionality of the component mstm. Performing a manipulation results in memory corruption. This vulnerability was named CVE-1999-0336. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in HP HP-UX 10 (Operating System). This affects an unknown code of the component mstm. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

buffer overflow in mstm in hp-ux allows local users to gain root access.

The weakness was presented 11/01/1996. This vulnerability is uniquely identified as CVE-1999-0336. The exploitability is told to be easy. An attack has to be approached locally. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.

Upgrading eliminates this vulnerability.

The vulnerability is also documented in the databases at X-Force (1439), SecurityFocus (BID 83081†) and Vulnerability Center (SBV-56670†). See VDB-16209 for similar entry. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.3
VulDB Meta Temp Score: 8.9

VulDB Base Score: 9.3
VulDB Temp Score: 8.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
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

10/31/1996 🔍
10/31/1996 +0 days 🔍
11/01/1996 +0 days 🔍
11/01/1996 +0 days 🔍
06/17/2014 +6437 days 🔍
02/17/2016 +610 days 🔍
04/16/2026 +3710 days 🔍

Sourcesinfo

Vendor: hp.com

Status: Confirmed

CVE: CVE-1999-0336 (🔍)
GCVE (CVE): GCVE-0-1999-0336
GCVE (VulDB): GCVE-100-13773
X-Force: 1439
SecurityFocus: 83081 - HP-UX CVE-1999-0336 Local Security Vulnerability
Vulnerability Center: 56670 - HP-UX 10 Local Privilege Escalation Vulnerability, High

See also: 🔍

Entryinfo

Created: 06/17/2014 17:37
Updated: 04/16/2026 11:10
Changes: 06/17/2014 17:37 (55), 08/23/2018 08:15 (2), 04/16/2026 11:10 (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 ▸

Interested in the pricing of exploits?

See the underground prices here!