Huawei DP300 up to V500R002C00SPC800 CIDAM Protocol input validation

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.

A vulnerability was found in Huawei DP300 (Unified Communication Software). It has been rated as critical. This issue affects some unknown processing of the component CIDAM Protocol Handler. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to 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. Impacted is 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 released 03/09/2018 (Website). The advisory is shared at The identification of this vulnerability is CVE-2017-17170 since 12/04/2017. The attack may be initiated remotely. Required for exploitation is a simple 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/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.

Entries connected to this vulnerability are available at 114279, 114280 and 114301.






  • commercial

CPE 2.3info

CPE 2.2info


VulDB Meta Base Score: 7.3
VulDB 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: 🔍



VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍


Class: Input validation
ATT&CK: Unknown

Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍


Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍


Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍


12/04/2017 🔍
12/20/2017 +16 days 🔍
03/09/2018 +79 days 🔍
03/09/2018 +0 days 🔍
03/10/2018 +1 days 🔍
02/17/2023 +1805 days 🔍



Advisory: sa-20171220-02
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-17170 (🔍)
See also: 🔍


Created: 03/10/2018 03:25 PM
Updated: 02/17/2023 09:04 PM
Changes: 03/10/2018 03:25 PM (58), 01/11/2020 09:23 PM (2), 02/17/2023 09:04 PM (3)
Complete: 🔍


No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!