CVE-2020-17002

Azure SDK for C Security Feature Bypass Vulnerability

Description

Azure SDK for C Security Feature Bypass Vulnerability

7.4
CVSS
Severity: High
CVSS 3.1 •
CVSS 2.0 •
EPSS 6.19% Top 10%
Vendor Advisory microsoft.com Vendor Advisory microsoft.com
Affected: Microsoft azure-c-shared-utility
Affected: Microsoft Azure-c-shared-utility Release LTS_07_2020_Ref02
Affected: Microsoft Azure-c-shared-utility Release LTS_02_2020_Ref02
Affected: Microsoft azure-uamqp-c
Affected: Microsoft azure-umqtt-c
Affected: Microsoft azure-uhttp-c
Affected: Microsoft azure-utpm-c
Affected: Microsoft azure-uamqp-c Release LTS_07_2020_Ref02
Affected: Microsoft azure-umqtt-c Release LTS_07_2020_Ref02
Affected: Microsoft azure-uhttp-c Release LTS_07_2020_Ref02
Affected: Microsoft azure-utpm-c Release LTS_07_2020_Ref02
Affected: Microsoft azure-uamqp-c Release LTS_02_2020_Ref02
Affected: Microsoft azure-umqtt-c Release LTS_02_2020_Ref02
Affected: Microsoft azure-uhttp-c Release LTS_02_2020_Ref02
Affected: Microsoft azure-utpm-c Release LTS_02_2020_Ref02
Affected: Microsoft C SDK for Azure IoT Release LTS_07_2020_Ref02
Affected: Microsoft C SDK for Azure IoT Release LTS_02_2020_Ref02
Affected: Microsoft C SDK for Azure IoT
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2020-17002?
CVE-2020-17002 has been scored as a high severity vulnerability.
How to fix CVE-2020-17002?
To fix CVE-2020-17002, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-17002 being actively exploited in the wild?
It is possible that CVE-2020-17002 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~6% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2020-17002?
CVE-2020-17002 affects Microsoft azure-c-shared-utility, Microsoft Azure-c-shared-utility Release LTS_07_2020_Ref02, Microsoft Azure-c-shared-utility Release LTS_02_2020_Ref02, Microsoft azure-uamqp-c, Microsoft azure-umqtt-c, Microsoft azure-uhttp-c, Microsoft azure-utpm-c, Microsoft azure-uamqp-c Release LTS_07_2020_Ref02, Microsoft azure-umqtt-c Release LTS_07_2020_Ref02, Microsoft azure-uhttp-c Release LTS_07_2020_Ref02, Microsoft azure-utpm-c Release LTS_07_2020_Ref02, Microsoft azure-uamqp-c Release LTS_02_2020_Ref02, Microsoft azure-umqtt-c Release LTS_02_2020_Ref02, Microsoft azure-uhttp-c Release LTS_02_2020_Ref02, Microsoft azure-utpm-c Release LTS_02_2020_Ref02, Microsoft C SDK for Azure IoT Release LTS_07_2020_Ref02, Microsoft C SDK for Azure IoT Release LTS_02_2020_Ref02, Microsoft C SDK for Azure IoT.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.