CVE-2019-5917 in the critical feed json
azure-umqtt-c (available through GitHub prior to 2017 October 6) allows remote attackers to cause a denial of service via unspecified vecto…
published 7y ago modified 4mo ago also EUVD-2019-15486
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 21.4%
- EPSS 21.4% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
azure-umqtt-c (available through GitHub prior to 2017 October 6) allows remote attackers to cause a denial of service via unspecified vectors.
Patch / fix
- microsoft azure-umqtt-c 2017-10-06
Is CVE-2019-5917 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 FencerExploit prediction
21.42% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Affected products
- Microsoft azure-umqtt-c
References
-
github.com
/Azure/azure-umqtt-c
third-party-advisory
-
securityfocus.com
/bid/107149
vdb-entry, third-party-advisory
-
jvn.jp
/en/jp/JVN05875753/index.html
third-party-advisory
Sources
- CVE List CVE-2019-5917
- NVD CVE-2019-5917
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.