Huawei DP300 up to V500R002C00SPC800 CIDAM Protocol input validation
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
7.3 | $5k-$25k | 0.00 |
A vulnerability was found in Huawei DP300 (Unified Communication Software). It has been classified as critical. This affects an unknown code of the component CIDAM Protocol Handler. The manipulation with an unknown input 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 integrity, and availability. The summary by CVE is:
The CIDAM Protocol on Huawei DP300 V500R002C00; V500R002C00B010; V500R002C00B011; V500R002C00B012; V500R002C00B013; V500R002C00B014; V500R002C00B017; V500R002C00B018; V500R002C00SPC100; V500R002C00SPC200; V500R002C00SPC300; V500R002C00SPC400; V500R002C00SPC500; V500R002C00SPC600; V500R002C00SPC800; V500R002C00SPC900; V500R002C00SPCa00 has an input validation vulnerability due to insufficient validation of specific messages when the protocol is implemented. An authenticated remote attacker could send a malicious message to a target system. Successful exploit could allow the attacker to tamper with business and make the system abnormal.
The bug was discovered 12/20/2017. The weakness was shared 03/09/2018 (Website). It is possible to read the advisory at huawei.com. This vulnerability is uniquely identified as CVE-2017-17168 since 12/04/2017. It is possible to initiate the attack remotely. A authentication is needed 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/17/2023).
The vulnerability was handled as a non-public zero-day exploit for at least 79 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.
Product
Type
Vendor
Name
Version
- V500R002C00
- V500R002C00B010
- V500R002C00B011
- V500R002C00B012
- V500R002C00B013
- V500R002C00B014
- V500R002C00B017
- V500R002C00B018
- V500R002C00SPC100
- V500R002C00SPC200
- V500R002C00SPC300
- V500R002C00SPC400
- V500R002C00SPC500
- V500R002C00SPC600
- V500R002C00SPC800
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 8.1
VulDB Temp Score: 8.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
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: 🔍
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/20/2017 🔍
03/09/2018 🔍
03/09/2018 🔍
03/10/2018 🔍
02/17/2023 🔍
Sources
Vendor: huawei.comAdvisory: sa-20171220-02
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-17168 (🔍)
Entry
Created: 03/10/2018 15:25Updated: 02/17/2023 20:49
Changes: 03/10/2018 15:25 (58), 01/11/2020 21:10 (2), 02/17/2023 20:49 (3)
Complete: 🔍
Cache ID: 3:8AF:103
No comments yet. Languages: en.
Please log in to comment.