Hitachi Ucosminexus Developer Standard up to 07_50_01 input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Hitachi Ucosminexus Developer Standard up to 07_50_01. It has been rated as critical. Affected by this issue is some unknown functionality. The manipulation leads to input validation. This vulnerability is uniquely identified as CVE-2007-5810. No exploit exists.
Details
A vulnerability, which was classified as critical, has been found in Hitachi Ucosminexus Developer Standard up to 07_50_01. This issue affects an unknown function. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. Impacted is integrity. The summary by CVE is:
Hitachi Web Server 01-00 through 03-00-01, as used by certain Cosminexus products, does not properly validate SSL client certificates, which might allow remote attackers to spoof authentication via a client certificate with a forged signature.
The weakness was disclosed 10/31/2007 (Website). The advisory is shared at hitachi-support.com. The identification of this vulnerability is CVE-2007-5810 since 11/05/2007. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.
It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at SecurityFocus (BID 26271†), OSVDB (42026†) and Secunia (SA27421†). The entry VDB-39556 is pretty similar. 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.hitachi.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.3
VulDB Temp Score: 5.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: Input validationCWE: CWE-20
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/31/2007 🔍10/31/2007 🔍
10/31/2007 🔍
10/31/2007 🔍
11/05/2007 🔍
11/05/2007 🔍
03/16/2015 🔍
11/03/2017 🔍
Sources
Vendor: hitachi.comAdvisory: hitachi-support.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2007-5810 (🔍)
GCVE (CVE): GCVE-0-2007-5810
GCVE (VulDB): GCVE-100-39557
SecurityFocus: 26271 - Hitachi Web Server HTML Injection Vulnerability and Signature Forgery Vulnerability
Secunia: 27421 - Hitachi Web Server Multiple Vulnerabilities, Less Critical
OSVDB: 42026 - Hitachi Web Server SSL Client Certification Validation Weakness
Vupen: ADV-2007-3666
See also: 🔍
Entry
Created: 03/16/2015 12:18Updated: 11/03/2017 07:54
Changes: 03/16/2015 12:18 (52), 11/03/2017 07:54 (7)
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.