| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.0 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in HP HP-UX and classified as problematic. Impacted is an unknown function. This manipulation causes symlink. This vulnerability is tracked as CVE-2000-0005. No exploit exists. The affected component should be upgraded.
Details
A vulnerability classified as critical was found in HP HP-UX (Operating System). Affected by this vulnerability is an unknown part. The manipulation with an unknown input leads to a symlink vulnerability. The CWE definition for the vulnerability is CWE-61. The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
HP-UX aserver program allows local users to gain privileges via a symlink attack.
The weakness was disclosed 01/02/1999 by FIRST (Website). The advisory is shared at oval.cisecurity.org. This vulnerability is known as CVE-2000-0005. 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 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (3881), SecurityFocus (BID 1928†), OSVDB (9609†) and Vulnerability Center (SBV-20908†). The entries VDB-15214 and VDB-15215 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 7.00
- 7.02
- 7.04
- 7.06
- 7.08
- 8.00
- 8.01
- 8.02
- 8.04
- 8.05
- 8.06
- 8.07
- 8.08
- 8.09
- 9.00
- 9.01
- 9.03
- 9.04
- 9.05
- 9.06
- 9.07
- 9.08
- 9.09
- 9.10
- 10.00
- 10.01
- 10.08
- 10.09
- 10.10
- 10.16
- 10.20
- 10.24
- 10.30
- 10.34
- 11.00
License
Website
- Vendor: https://www.hp.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.4VulDB Meta Temp Score: 8.0
VulDB Base Score: 8.4
VulDB Temp Score: 8.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: SymlinkCWE: CWE-61 / CWE-59
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
01/02/1999 🔍01/02/1999 🔍
01/02/1999 🔍
01/02/2000 🔍
02/17/2009 🔍
06/20/2014 🔍
04/18/2026 🔍
Sources
Vendor: hp.comAdvisory: oval.cisecurity.org
Researcher: FIRST
Status: Confirmed
CVE: CVE-2000-0005 (🔍)
GCVE (CVE): GCVE-0-2000-0005
GCVE (VulDB): GCVE-100-14437
OVAL: 🔍
X-Force: 3881
SecurityFocus: 1928 - HP-UX Aserver /tmp/null Symbolic Link Vulnerability
OSVDB: 9609 - HP-UX aserver -f Argument last_uuid Symlink Privilege Escalation
Vulnerability Center: 20908 - HP-UX 10 Through 11.4 Aserver Program Local Privilege Escalation Vulnerability via a Symlink Attack, High
See also: 🔍
Entry
Created: 06/20/2014 12:39Updated: 04/18/2026 04:06
Changes: 06/20/2014 12:39 (60), 08/27/2019 12:05 (3), 04/18/2026 04:06 (18)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.

No comments yet. Languages: en.
Please log in to comment.