Code execution via AMQP messaging double free
Published Aug 13, 2024 · Updated Jul 10, 2025
Double-free in Microsoft Azure IoT Hub Device Client SDK before 1.12.1 allows local users to execute arbitrary code. The AMQP messaging module releases the same allocation twice; Microsoft has not published the exact triggering input or state. Exploitation requires low local privileges and a high-complexity condition, and successful exploitation runs code in the SDK-hosting process.
Summary
What happened
Double-free in Microsoft Azure IoT Hub Device Client SDK before 1.12.1 allows local users to execute arbitrary code. The AMQP messaging module releases the same allocation twice; Microsoft has not published the exact triggering input or state. Exploitation requires low local privileges and a high-complexity condition, and successful exploitation runs code in the SDK-hosting process.
The record
- CVE
- CVE-2024-38157
- Published
- Aug 13, 2024
- Updated
- Jul 10, 2025
- Vendor
- Microsoft
- Product
- Azure IoT Hub Device Client SDK
- Classifications
- CWE-415, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 13, 2024CVE publishedPublication date reported by the CVE source.
- Jul 10, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <1.12.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo