HP SOA Registry Foundation 6.63

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.
7.7	$0-$5k	0.00

Summaryinfo

A vulnerability described as critical has been identified in HP SOA Registry Foundation 6.63. This vulnerability affects unknown code. Such manipulation leads to an unknown weakness. This vulnerability is traded as CVE-2010-0450. There is no exploit available. It is advisable to implement a patch to correct this issue.

Detailsinfo

A vulnerability was found in HP SOA Registry Foundation 6.63 and classified as critical. Impacted is confidentiality, and integrity. CVE summarizes:

Unspecified vulnerability in HP SOA Registry Foundation 6.63 and 6.64 allows remote authenticated users to gain privileges via unknown vectors.

The weakness was shared 03/31/2010 as confirmed posting (Bugtraq). The advisory is shared for download at marc.info. This vulnerability is handled as CVE-2010-0450 since 01/27/2010. The exploitation is known to be easy. The attack may be launched remotely. The requirement for exploitation is a simple authentication. There are neither technical details nor an exploit publicly available.

Applying a patch is able to eliminate this problem.

The vulnerability is also documented in the databases at SecurityFocus (BID 39061†), Secunia (SA39187†) and SecurityTracker (ID 1023765†). The entries VDB-52483 and VDB-52482 are related to this item. Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• HP

Name

• SOA Registry Foundation

Version

• 6.63

License

• commercial

Website

• Vendor: https://www.hp.com/

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.1
VulDB Meta Temp Score: 7.7

VulDB Base Score: 8.1
VulDB Temp Score: 7.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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: 🔍

Exploitinginfo

Class: Unknown
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

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 Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Timelineinfo

01/27/2010 🔍
03/30/2010 +62 days 🔍
03/30/2010 +0 days 🔍
03/30/2010 +0 days 🔍
03/31/2010 +1 days 🔍
03/31/2010 +0 days 🔍
03/19/2015 +1814 days 🔍
12/30/2017 +1017 days 🔍

Sourcesinfo

Vendor: hp.com

Advisory: marc.info
Status: Confirmed

CVE: CVE-2010-0450 (🔍)
GCVE (CVE): GCVE-0-2010-0450
GCVE (VulDB): GCVE-100-52484
SecurityFocus: 39061 - HP SOA Registry Foundation Unspecified Privilege Escalation Vulnerability
Secunia: 39187 - HP SOA Registry Foundation Multiple Vulnerabilities, Moderately Critical
SecurityTracker: 1023765

See also: 🔍

Entryinfo

Created: 03/19/2015 12:22
Updated: 12/30/2017 06:11
Changes: 03/19/2015 12:22 (52), 12/30/2017 06:11 (6)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

Want to know what is going to be exploited?

We predict KEV entries!