Read the docs
TI-2024-25441 Aliases CVE-2024-38157GHSA-fr76-j9qw-qp24

Azure IoT SDK Remote Code Execution Vulnerability

Priority LOW 33CWE-415Published · Updated

Key facts

Attack vector
Local
Privileges required
Low
User interaction
None
Attack complexity
High
Impact type
Code execution
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from Microsoft.

Summary

Azure IoT SDK Remote Code Execution Vulnerability

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.0048 41st percentileScored 2026-11-07
Fix Fixed Azure IoT Hub Device Client SDK (Microsoft): 1.12.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
MicrosoftAzure IoT Hub Device Client SDK1.0.0 to before 1.12.11.12.1Patch availableCNA
  • Azure IoT Hub Device Client SDK VendorMicrosoft Affected 1.0.0 to before 1.12.1 Fixed in 1.12.1 Patch available CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:microsoft:azure_iot_hub_device_client_sdk:*:*:*:*:*:*:*:*before 1.12.1VulnerableMicrosoft
  • cpe:2.3:a:microsoft:azure_iot_hub_device_client_sdk:*:*:*:*:*:*:*:* Versions before 1.12.1 Vulnerable ·Microsoft

Remediation

  • Fix · CNA Azure IoT Hub Device Client SDK (Microsoft) Fixed in 1.12.1

Vendor assessments

Microsoft

Microsoft's page for this CVE →

Impact
Remote Code Execution
Exploited
No
Publicly disclosed
No
Exploitability
Exploitation Less Likely
ProductStatusPlan or fix
Azure IoT Hub Device Client SDKFixed 1.12.1 · Security Update

Timeline

  1. 2026-10-02 Threatist record created from CVE-2024-38157
  2. 2026-10-03 Alias added: GHSA-fr76-j9qw-qp24

References

Patch 1

  • TI-2024-25442 Azure IoT SDK Remote Code Execution Vulnerability CVSS 3.1HIGH 7.0

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences