| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in HP Version Control Agent up to 2.1.4. Affected is an unknown function. Performing a manipulation results in privileges management. This vulnerability is reported as CVE-2006-5300. No exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability was found in HP Version Control Agent up to 2.1.4. It has been classified as critical. This affects an unknown code. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Unspecified vulnerability in HP Version Control Agent before 2.1.5 allows remote authenticated users to obtain "unauthorized access" to a remote Repository Manager account and potentially gain privileges via unspecified vectors.
The weakness was disclosed 10/17/2006 (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2006-5300 since 10/17/2006. The exploitability is told to be easy. It is possible to initiate the attack remotely. A authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
It is declared as proof-of-concept.
Upgrading to version 2.1.5 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (29500), SecurityFocus (BID 20465†), Secunia (SA22399†) and SecurityTracker (ID 1017042†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.hp.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.5
VulDB Base Score: 6.3
VulDB Temp Score: 5.5
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: Privileges managementCWE: CWE-269 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
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: 🔍
Upgrade: Version Control Agent 2.1.5
Timeline
10/11/2006 🔍10/11/2006 🔍
10/13/2006 🔍
10/17/2006 🔍
10/17/2006 🔍
10/17/2006 🔍
03/12/2015 🔍
04/24/2026 🔍
Sources
Vendor: hp.comAdvisory: securityfocus.com⛔
Status: Confirmed
CVE: CVE-2006-5300 (🔍)
GCVE (CVE): GCVE-0-2006-5300
GCVE (VulDB): GCVE-100-32757
X-Force: 29500 - HP Version Control Agent privilege escalation
SecurityFocus: 20465 - HP Version Control Agent Remote Unauthorized Access and Privilege Escalation Vulnerability
Secunia: 22399 - HP Version Control Agent Security Bypass Vulnerability, Less Critical
SecurityTracker: 1017042 - HP Version Control Agent Lets Remote Authenticated Users Access the System With Elevated Privileges
Vupen: ADV-2006-4017
Entry
Created: 03/12/2015 22:21Updated: 04/24/2026 10:15
Changes: 03/12/2015 22:21 (57), 10/01/2017 20:55 (7), 04/24/2026 10:15 (17)
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.