{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-29195 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2024-29195 is a medium-severity vulnerability in azure-c-shared-utility, published on 26 Mar 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-29195 and fix it if it is affected.\n\nWhat it is: CVE-2024-29195 is a medium-severity vulnerability in azure-c-shared-utility, published on 26 Mar 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-29195 in the wild and no public exploit code.\n\nAffected product: azure-c-shared-utility. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-29195/ (Markdown: https://insights.sbomify.com/CVE-2024-29195/index.md)","id":"CVE-2024-29195","markdown":"https://insights.sbomify.com/CVE-2024-29195/index.md","name":"CVE-2024-29195","record":{"aliases":["AZL-37068","AZL-37086","AZL-70178","AZL-70310","DEBIAN-CVE-2024-29195","GHSA-m8wp-hc7w-x4xg","UBUNTU-CVE-2024-29195"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Azure IoT C SDK","requires_auth":"high_privilege","summary":"An attacker with a compromised Azure account can trigger an integer overflow in the Azure C SDK to achieve remote code execution on IoT devices.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"azure_c_shared_utility","vendor":"microsoft"}],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Azure C SDK Integer Wraparound Vulnerability","id":"CVE-2024-29195","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"phpMyFAQ Path Traversal in Attachments","id":"CVE-2024-29196"},"packages":[],"prev":{"headline":"OneUptime Vulnerable to a Privilege Escalation via Local Storage Key Manipulation","id":"CVE-2024-29194"},"products":["azure-c-shared-utility"],"published":"2024-03-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Azure"]},"summary":"An attacker with a compromised Azure account can trigger an integer overflow in the Azure C SDK to achieve remote code execution on IoT devices.","url":"https://insights.sbomify.com/CVE-2024-29195/"}