VDB-325 · SA9977 · GCVE-100-325

HP HP-UX 11.00/11.11/11.22 dtprintinfo DISPLAY 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.
5.3$0-$5k0.00

Summaryinfo

A vulnerability has been found in HP HP-UX 11.00/11.11/11.22 and classified as critical. The affected element is an unknown function of the component dtprintinfo. This manipulation of the argument DISPLAY causes memory corruption. The attack requires access to the local network. No exploit is available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability classified as critical was found in HP HP-UX 11.00/11.11/11.22 (Operating System). Affected by this vulnerability is an unknown part of the component dtprintinfo. The manipulation of the argument DISPLAY with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability.

The weakness was published 10/09/2003 by Davide Del Vecchio (Website). The advisory is shared at www4.itrc.hp.com. The attack needs to be done within the local network. Technical details are known, but no exploit is available.

Applying a patch is able to eliminate this problem. The bugfix is ready for download at itrc.hp.com.

The vulnerability is also documented in the vulnerability database at Secunia (SA9977†). Additional details are provided at ciac.org. 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: 5.5
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Patch: itrc.hp.com

Timelineinfo

10/09/2003 🔍
10/13/2003 +4 days 🔍
06/26/2019 +5735 days 🔍

Sourcesinfo

Vendor: hp.com

Advisory: www4.itrc.hp.com
Researcher: Davide Del Vecchio
Status: Not defined

GCVE (VulDB): GCVE-100-325
Secunia: 9977 - HP-UX dtprintinfo DISPLAY Buffer Overflow Vulnerability, Less Critical

Misc.: 🔍

Entryinfo

Created: 10/13/2003 10:57
Updated: 06/26/2019 16:52
Changes: 10/13/2003 10:57 (48), 06/26/2019 16:52 (5)
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 stay up to date on a daily basis?

Enable the mail alert feature now!