Huawei eSpace 7910/eSpace 7950/eSpace 8950 URL path traversal

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Huawei eSpace 7910, eSpace 7950 and eSpace 8950. Affected by this issue is some unknown functionality of the component URL Handler. Performing a manipulation results in path traversal. This vulnerability is identified as CVE-2017-17223. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability classified as critical has been found in Huawei eSpace 7910, eSpace 7950 and eSpace 8950 (affected version not known). This affects some unknown functionality of the component URL Handler. The manipulation with an unknown input leads to a path traversal vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Huawei eSpace 7910 V200R003C30; eSpace 7950 V200R003C30; eSpace 8950 V200R003C00; V200R003C30 have a directory traversal vulnerability. An authenticated, remote attacker can craft specific URL to the affected products. Due to insufficient verification of the URL, successful exploit will upload and download files and cause information leak and system crash.
The bug was discovered 01/31/2018. The weakness was released 03/09/2018 (Website). It is possible to read the advisory at huawei.com. This vulnerability is uniquely identified as CVE-2017-17223 since 12/04/2017. The exploitability is told to be easy. It is possible to initiate the attack remotely. A authentication is required for exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 02/21/2023). The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 37 days. During that time the estimated underground price was around $5k-$25k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
License
Website
- Vendor: https://www.huawei.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
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: 🔍
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 Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/04/2017 🔍01/31/2018 🔍
03/09/2018 🔍
03/09/2018 🔍
03/10/2018 🔍
02/21/2023 🔍
Sources
Vendor: huawei.comAdvisory: sa-20180131-02
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-17223 (🔍)
GCVE (CVE): GCVE-0-2017-17223
GCVE (VulDB): GCVE-100-114291
Entry
Created: 03/10/2018 15:25Updated: 02/21/2023 06:27
Changes: 03/10/2018 15:25 (55), 01/11/2020 22:55 (2), 02/21/2023 06:27 (3)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.