CVE-2024-25110: Azure IoT Platform Device SDK Remote Code Execution Vulnerability
Vulnerability summary
CVE-2024-25110 is a critical (CVSS 9.8) Code Injection vulnerability in azure azure-uamqp-c. EPSS estimates a 7.29% chance of exploitation in the next 30 days, higher than 94.3% of scored vulnerabilities.
Timeline
- 12-02-2024PublishedVulnerability first disclosed.
- 07-11-2024Last modifiedVulnerability information updated.
Description
The UAMQP is a general purpose C library for AMQP 1.0. During a call to open_get_offered_capabilities, a memory allocation may fail causing a use-after-free issue and if a client called it during connection communication it may cause a remote code execution. Users are advised to update the submodule with commit `30865c9c`. There are no known workarounds for this vulnerability.
CVSS metrics
4 scores · 4 sources · 1 version- OSV · UbuntuEcosystem advisory · calculated8.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HDiffers
- OSV · DebianEcosystem advisory · calculated8.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HDiffers
- NVDNIST8.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HDiffers
EPSS trend
Probability
7.29%
Chance of exploitation in the next 30 days
Percentile
94%
Versus all other CVEs
30-day change
Increase +0.06 pp
From 7.23% on 22-09-2026
Known exploited
Compare KEV catalogs
CISA KEVNot in the CISA KEV catalog.
ENISA CNWNot in the ENISA CNW catalog.
CIRCLNot in the CIRCL catalog.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root cause- CWE-94Improper Control of Generation of Code ('Code Injection')The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
- CWE-416Use After FreeThe product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Affected systems
Suse4 products
- python-uamqp&distro=SUSE Linux Enterprise Module for Public Cloud 15 SP2< 1.5.3-150100.4.13.1
- python-uamqp&distro=SUSE Linux Enterprise Module for Public Cloud 15 SP3< 1.5.3-150100.4.13.1
- python-uamqp&distro=SUSE Linux Enterprise Module for Public Cloud 15 SP4< 1.5.3-150100.4.13.1
- python-uamqp&distro=SUSE Linux Enterprise Module for Public Cloud 15 SP5< 1.5.3-150100.4.13.1
Azure1 product
- azure-uamqp-c< 2024-01-01
Debian1 product
- azure-uamqp-pythonAll versions (No fix recorded) | < 1.6.8-2
Microsoft1 product
- azure_uamqp< 2024-02-01
Opensuse1 product
- python-uamqp&distro=openSUSE Leap 15.5< 1.5.3-150100.4.13.1
Ubuntu1 product
- azure-uamqp-pythonAll versions (No fix recorded)
6 vendors · 9 products
References
10 links- github.com/Azure/azure-uamqp-c/security/advisories/GHSA-c646-4whf-r67vX Refsource CONFIRMREPORTVendor Advisory
- github.com/Azure/azure-uamqp-c/commit/30865c9ccedaa32ddb036e87a8ebb52c3f18f695X Refsource MISCREPORTPatch
