Huawei DP300/RP200/TE50/TE60/VP9660 System Manager Putty Key input validation

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $5k-$25k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Huawei DP300, RP200, TE50, TE60 and VP9660. This impacts an unknown function of the component System Manager. Performing a manipulation as part of Putty Key results in input validation. This vulnerability is reported as CVE-2017-17131. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as problematic has been found in Huawei DP300, RP200, TE50, TE60 and VP9660 (Unified Communication Software). This affects some unknown processing of the component System Manager. The manipulation as part of a Putty Key leads to a input validation vulnerability. CWE is classifying the issue as 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. This is going to have an impact on availability. The summary by CVE is:
Huawei DP300 V500R002C00; RP200 V500R002C00; V600R006C00; TE30 V100R001C10; V600R006C00; TE50 V600R006C00; TE60 V100R001C10; V500R002C00; V600R006C00; VP9660 V500R002C10 have an DoS vulnerability due to insufficient validation of the parameter when a putty comment key is loaded. An authenticated remote attacker can place a malformed putty key file in system when a system manager load the key an infinite loop happens which lead to reboot the system.
The bug was discovered 12/06/2017. The weakness was disclosed 03/05/2018 (Website). The advisory is shared at huawei.com. This vulnerability is uniquely identified as CVE-2017-17131 since 12/04/2017. It is possible to initiate the attack remotely. Required for exploitation is a authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 02/16/2023).
The vulnerability was handled as a non-public zero-day exploit for at least 89 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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
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: 5.0VulDB Meta Temp Score: 5.0
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.7
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: Input validationCWE: CWE-20
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 🔍12/06/2017 🔍
03/05/2018 🔍
03/05/2018 🔍
03/06/2018 🔍
02/16/2023 🔍
Sources
Vendor: huawei.comAdvisory: sa-20171206-01
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-17131 (🔍)
GCVE (CVE): GCVE-0-2017-17131
GCVE (VulDB): GCVE-100-114057
Entry
Created: 03/06/2018 07:51Updated: 02/16/2023 19:15
Changes: 03/06/2018 07:51 (57), 01/10/2020 11:34 (2), 02/16/2023 19:15 (3)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.