VDB-165695 · CVE-2020-17002 · GCVE-0-2020-17002

Microsoft C SDK for Azure IoT protection mechanism

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.
7.3	$0-$5k	0.00

Summaryinfo

A vulnerability was found in Microsoft C SDK for Azure IoT. It has been classified as critical. This affects an unknown part. The manipulation leads to protection mechanism. This vulnerability is referenced as CVE-2020-17002. Remote exploitation of the attack is possible. No exploit is available. It is recommended to apply a patch to fix this issue.

Detailsinfo

A vulnerability was found in Microsoft C SDK for Azure IoT (unknown version) and classified as critical. This issue affects an unknown code block. The manipulation with an unknown input leads to a protection mechanism vulnerability. Using CWE to declare the problem leads to CWE-693. The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. Impacted is confidentiality, and integrity.

The weakness was published 12/08/2020 as confirmed security guidance (Website). It is possible to read the advisory at portal.msrc.microsoft.com. The identification of this vulnerability is CVE-2020-17002. The technical details are unknown and an exploit is not publicly available.

Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

Microsoft

Name

C SDK for Azure IoT

License

commercial

Website

Vendor: https://www.microsoft.com/

CPE 2.3info

🔍

CPE 2.2info

🔍

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.8
VulDB Meta Temp Score: 7.3

VulDB Base Score: 7.4
VulDB Temp Score: 6.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

Vendor Base Score (Microsoft): 7.4
Vendor Vector (Microsoft): 🔍

NVD Base Score: 9.1
NVD Vector: 🔍

CNA Base Score: 7.4
CNA Vector: 🔍

CVSSv2info

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: 🔍

Exploitinginfo

Class: Protection mechanism
CWE: CWE-693
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Unproven

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Timelineinfo

08/04/2020 🔍
12/08/2020 +126 days 🔍
12/08/2020 +0 days 🔍
12/09/2020 +0 days 🔍
08/29/2025 +1723 days 🔍

Sourcesinfo

Vendor: microsoft.com

Advisory: portal.msrc.microsoft.com
Status: Confirmed

CVE: CVE-2020-17002 (🔍)
GCVE (CVE): GCVE-0-2020-17002
GCVE (VulDB): GCVE-100-165695

Entryinfo

Created: 12/09/2020 01:21
Updated: 08/29/2025 01:41
Changes: 12/09/2020 01:21 (11), 12/09/2020 01:22 (23), 12/09/2020 01:26 (17), 12/13/2020 11:45 (2), 12/13/2020 11:49 (18), 08/29/2025 01:41 (25)
Complete: 🔍
Cache ID: 216::103