Azure C Shared Utility
Approved changes feed: RSS · Atom
cpe:2.3:a:azure:azure-c-shared-utility:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Azure (bcdde641-20ca-55ac-abda-dda8306c0a74) |
|---|---|
| Product | Azure C Shared Utility (97c536e3-408c-59e7-b201-266b88b1d615) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-29195 |
vulnerable | 2026-06-08 06:33:28.950830 |
Azure C SDK Integer Wraparound Vulnerability
MEDIUM (6)
The azure-c-shared-utility is a C library for AMQP/MQTT communication to Azure Cloud Services. This library may be used by the Azure IoT C SDK for communication between IoT Hub and IoT Hub devices. An attacker can cause an integer wraparound or under-allocation or heap buffer overflow due to vulnerabilities in parameter checking mechanism, by exploiting the buffer length parameter in Azure C SDK, which may lead to remote code execution. Requirements for RCE are 1. Compromised Azure account allowing malformed payloads to be sent to the device via IoT Hub service, 2. By passing IoT hub service max message payload limit of 128KB, and 3. Ability to overwrite code space with remote code. Fixed in commit https://github.com/Azure/azure-c-shared-utility/commit/1129147c38ac02ad974c4c701a1e01b2141b9fe2.
Published: 2024-03-26T02:57:20.769Z
Updated: 2024-08-04T11:26:22.203Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.