Important 📢 Publicly disclosed 2018-10 archive

Executive Summary

A remote code execution vulnerability exists in the way that Azure IoT Hub Device Client SDK using MQTT protocol accesses objects in memory. The vulnerability could corrupt memory in a way that could allow an attacker to execute arbitrary code in the context of the current user. An attacker who successfully exploited the vulnerability could gain the same user rights as the current user. If the current user is logged on with administrative user rights, the attacker could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. An attacker would have no way to force users to view the attacker-controlled content. Instead, an attacker would have to convince users to take action, typically via an enticement in email or instant message, or by getting them to open an email attachment. The security update addresses the vulnerability by changing the default allocators.

Overview

Important
MS Severity
Not Exploited
MS Exploit Status
Less Likely
MS Exploit Likelihood
Category Information Disclosure
Released Oct 9 2018
Last Updated Oct 9 2018
Publicly Disclosed Yes
CISA KEV Not Listed
Known Exploits None Known

EPSS Score

No EPSS score available for this CVE.

View on FIRST.org

Affected Products

2 affected products
Product KB Article Severity Impact Restart Required
Azure IoT Edge Release Notes (Security Update) Important Information Disclosure Yes
Hub Device Client SDK for Azure IoT Release Notes (Security Update) Important Remote Code Execution Yes

Patches

1 patch
Article Type Restart
Release Notes Security Update Yes

Known Exploits

Acknowledgments

Cristian Pop of Azure IoT