Remote code execution via wrapped binary allocation
Published Jan 9, 2024 · Updated Jun 16, 2025
Memory corruption in Microsoft Azure uAMQP C before 2024-01-01 allows remote authenticated users to execute code through malformed AMQP data. In internal_decoder_decode_bytes, an untrusted binary length plus one can wrap to zero, while failed-state processing can free the same allocation twice. Exploitation requires a compromised Azure account able to send malformed IoT Hub payloads, an allocation failure or protocol violation, and control sufficient to overwrite code space.
Summary
What happened
Memory corruption in Microsoft Azure uAMQP C before 2024-01-01 allows remote authenticated users to execute code through malformed AMQP data. In internal_decoder_decode_bytes, an untrusted binary length plus one can wrap to zero, while failed-state processing can free the same allocation twice. Exploitation requires a compromised Azure account able to send malformed IoT Hub payloads, an allocation failure or protocol violation, and control sufficient to overwrite code space.
The record
- CVE
- CVE-2024-21646
- Published
- Jan 9, 2024
- Updated
- Jun 16, 2025
- Vendor
- Microsoft
- Product
- Azure uAMQP C
- Classifications
- CWE-94, CWE-190, T1203
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jan 9, 2024CVE publishedPublication date reported by the CVE source.
- Jun 16, 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=< 2024-01-01
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.
Weakness, pattern, technique
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