Skip to content
Fencer Vulns
critical 9.8

CVE-2024-21646 json

Azure IoT Platform Device SDK Remote Code Execution Vulnerability

published 2024-01-09 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-19279

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
5.1%
EPSS 5.1% chance of exploitation in 30 days, percentile 92%
public exploits
0
none known

Summary

Azure uAMQP is a general purpose C library for AMQP 1.0. The UAMQP library is used by several clients to implement AMQP protocol communication. When clients using this library receive a crafted binary type data, an integer overflow or wraparound or memory safety issue can occur and may cause remote code execution. This vulnerability has been patched in release 2024-01-01.

Patch / fix

  • microsoft azure_uamqp 2024-01-01
  • azure-uamqp-python Debian 14, Debian 13 1.6.8-1

debian advisories DEBIAN-CVE-2024-21646

  • python-uamqp SLE Module for Public Cloud 15 SP5, SLE Module for Public Cloud 15 SP4, SLE Module for Public Cloud 15 SP3 +2 more 1.5.3-150100.4.10.1

suse advisories SUSE-SU-2024:0323-1

  • azure-iot-sdk-c CBL-Mariner 2.0 2022.01.21-2
  • azure-iot-sdk-c Azure Linux 3.0 2024.03.04-1

azure linux advisories AZL-33284AZL-34555

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
16 mo ago

Exploit prediction

5.11% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Azure azure-uamqp-c

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code
  • CWE-190 Integer Overflow or Wraparound

References

Sources

Fencer Vulns 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.