Skip to content
Fencer Intel
critical 9.1

CVE-2020-17002 json

Azure SDK for C Security Feature Bypass Vulnerability

published 5y ago modified 4mo ago also EUVD-2020-8959

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
3.5%
EPSS 3.5% chance of exploitation in 30 days, percentile 89%
public exploits
0
none known

Summary

Azure SDK for C Security Feature Bypass Vulnerability

Patch / fix

  • microsoft c_sdk_for_azure_iot lts_07_2020_ref02

Is CVE-2020-17002 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

3.49% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
CNA 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD 2.0 9.4 AV:N/AC:L/Au:N/C:C/I:C/A:N

Affected products

  • Microsoft azure-c-shared-utility
  • Microsoft Azure-c-shared-utility Release LTS_02_2020_Ref02
  • Microsoft Azure-c-shared-utility Release LTS_07_2020_Ref02
  • Microsoft azure-uamqp-c
  • Microsoft azure-uamqp-c Release LTS_02_2020_Ref02
  • Microsoft azure-uamqp-c Release LTS_07_2020_Ref02
  • Microsoft azure-uhttp-c
  • Microsoft azure-uhttp-c Release LTS_02_2020_Ref02
  • Microsoft azure-uhttp-c Release LTS_07_2020_Ref02
  • Microsoft azure-umqtt-c
  • Microsoft azure-umqtt-c Release LTS_02_2020_Ref02
  • Microsoft azure-umqtt-c Release LTS_07_2020_Ref02
  • Microsoft azure-utpm-c
  • Microsoft azure-utpm-c Release LTS_02_2020_Ref02
  • Microsoft azure-utpm-c Release LTS_07_2020_Ref02
  • Microsoft C SDK for Azure IoT
  • Microsoft C SDK for Azure IoT Release LTS_02_2020_Ref02
  • Microsoft C SDK for Azure IoT Release LTS_07_2020_Ref02

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.