| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Hitachi JP1-HiCommand Suite. It has been declared as problematic. This vulnerability affects unknown code. Executing a manipulation can lead to cross site scripting. The identification of this vulnerability is CVE-2007-3623. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability classified as problematic was found in Hitachi JP1-HiCommand Suite (version now known). This vulnerability affects some unknown processing. The manipulation with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-80. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. As an impact it is known to affect integrity.
The weakness was shared 07/06/2007 (Website). The advisory is shared for download at hitachi-support.com. This vulnerability was named CVE-2007-3623 since 07/09/2007. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1059.007.
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 X-Force (35286), SecurityFocus (BID 24797†), OSVDB (37849†) and Secunia (SA25973†). The entry VDB-37698 is related to this item. Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
License
Website
- Vendor: https://www.hitachi.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
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: Cross site scriptingCWE: CWE-80 / CWE-74 / CWE-707
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
07/06/2007 🔍07/06/2007 🔍
07/06/2007 🔍
07/09/2007 🔍
07/09/2007 🔍
10/16/2007 🔍
05/08/2016 🔍
08/12/2022 🔍
Sources
Vendor: hitachi.comAdvisory: hitachi-support.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2007-3623 (🔍)
GCVE (CVE): GCVE-0-2007-3623
GCVE (VulDB): GCVE-100-85924
X-Force: 35286
SecurityFocus: 24797 - JP1/HiCommand Series Products Cross-Site Scripting Vulnerability
Secunia: 25973 - Hitachi JP1/HiCommand Series Two Vulnerabilities, Less Critical
OSVDB: 37849 - Hitachi JP1/ HiCommand Suite Common Component SSLv2 Rollback Weakness
Vupen: ADV-2007-2457
See also: 🔍
Entry
Created: 05/08/2016 22:08Updated: 08/12/2022 12:20
Changes: 05/08/2016 22:08 (54), 01/17/2019 12:05 (4), 08/12/2022 12:20 (3)
Complete: 🔍
Cache ID: 216:9A2:103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.