CVE-2018-8531
First published: Wed Oct 10 2018(Updated: )
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.
Credit: secure@microsoft.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Microsoft Azure IoT Edge | ||
| Microsoft Csharp Software Development Kit |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2018-8531?
The severity of CVE-2018-8531 is considered critical due to its potential for remote code execution.
How do I fix CVE-2018-8531?
To fix CVE-2018-8531, you should update the Azure IoT Hub Device Client SDK and Azure IoT Edge to the latest versions provided by Microsoft.
What are the affected products for CVE-2018-8531?
CVE-2018-8531 affects Microsoft Azure IoT Edge and the Microsoft Csharp Software Development Kit for Azure IoT.
Is remote code execution possible with CVE-2018-8531?
Yes, due to the memory corruption vulnerability in CVE-2018-8531, remote code execution is possible.
What is the attack vector for CVE-2018-8531?
The attack vector for CVE-2018-8531 involves exploiting the Azure IoT Hub Device Client SDK when using the MQTT protocol.
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/weakness
- agent/last-modified-date
- agent/remedy
- agent/author
- agent/first-publish-date
- agent/description
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/microsoft
- canonical/microsoft azure iot edge
- canonical/microsoft csharp software development kit