CVE-2018-8531 in the critical feed json
A remote code execution vulnerability exists in the way that Azure IoT Hub Device Client SDK using MQTT protocol accesses objects in memory…
published 2018-10-10 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-20155
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 15.1%
- EPSS 15.1% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Exploit prediction
15.13% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Affected products
- Microsoft Hub Device Client SDK
- Microsoft Azure IoT Edge
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2018-8531
patch, vendor-advisory
-
securityfocus.com
/bid/105472
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-8531
- NVD CVE-2018-8531
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.