HP Data Protector 6.10 crs.exe path traversal ⚔ [Disputed]

CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in HP Data Protector 6.10. This affects an unknown part of the file crs.exe. The manipulation leads to path traversal. This vulnerability is uniquely identified as CVE-2014-5160. There is no exploit available. The real existence of this vulnerability is still doubted at the moment. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Details
A vulnerability was found in HP Data Protector 6.10 (Backup Software). It has been rated as critical. Affected by this issue is an unknown function of the file crs.exe. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is integrity, and availability. CVE summarizes:
** DISPUTED ** Multiple directory traversal vulnerabilities in crs.exe in the Cell Request Service in HP Data Protector allow remote attackers to create arbitrary files via an opcode-1091 request, or create or delete arbitrary files via an opcode-305 request. NOTE: the vendor reportedly asserts that this behavior is "by design."
The weakness was disclosed 08/01/2014 (Website). The advisory is shared for download at zerodayinitiative.com. This vulnerability is handled as CVE-2014-5160 since 07/31/2014. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 08/06/2024). The MITRE ATT&CK project declares the attack technique as T1006.
The real existence of this vulnerability is still doubted at the moment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 6.5
VulDB Temp Score: 6.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: Path traversalCWE: CWE-22
CAPEC: 🔍
ATT&CK: 🔍
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 Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/31/2014 🔍08/01/2014 🔍
08/01/2014 🔍
03/26/2015 🔍
08/06/2024 🔍
Sources
Vendor: hp.comAdvisory: zerodayinitiative.com
Status: Not defined
Disputed: 🔍
CVE: CVE-2014-5160 (🔍)
GCVE (CVE): GCVE-0-2014-5160
GCVE (VulDB): GCVE-100-70532
Entry
Created: 03/26/2015 12:07 PMUpdated: 08/06/2024 03:02 PM
Changes: 03/26/2015 12:07 PM (42), 08/16/2018 07:31 AM (6), 08/06/2024 03:02 PM (17)
Complete: 🔍
Cache ID: 18:A1A:40
No comments yet. Languages: en.
Please log in to comment.