Microsoft Azure IoT SDK double free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.4$0-$5k0.00

Summaryinfo

A vulnerability labeled as critical has been found in Microsoft Azure IoT SDK. Impacted is an unknown function. Such manipulation leads to double free. This vulnerability is documented as CVE-2024-38157. The attack needs to be performed locally. There is not any exploit available. A patch should be applied to remediate this issue.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Microsoft Azure IoT SDK (the affected version unknown). Affected by this issue is an unknown part. The manipulation with an unknown input leads to a double free vulnerability. Using CWE to declare the problem leads to CWE-415. The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations. Impacted is confidentiality, integrity, and availability.

The weakness was released 08/13/2024 as confirmed security update guide (Website). The advisory is available at msrc.microsoft.com. This vulnerability is handled as CVE-2024-38157. The exploitation is known to be difficult. Local access is required to approach this attack. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 05/20/2025).

Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2024-37130). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.0
VulDB Meta Temp Score: 6.4

VulDB Base Score: 7.0
VulDB Temp Score: 6.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

Vendor Base Score (Microsoft): 7.0
Vendor Vector (Microsoft): 🔍

CNA Base Score: 7.0
CNA Vector (Microsoft): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Double free
CWE: CWE-415 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Unproven

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Timelineinfo

08/13/2024 🔍
08/13/2024 +0 days 🔍
08/13/2024 +0 days 🔍
05/20/2025 +280 days 🔍

Sourcesinfo

Vendor: microsoft.com

Advisory: msrc.microsoft.com
Status: Confirmed

CVE: CVE-2024-38157 (🔍)
GCVE (CVE): GCVE-0-2024-38157
GCVE (VulDB): GCVE-100-274466
EUVD: 🔍

Entryinfo

Created: 08/13/2024 20:02
Updated: 05/20/2025 14:37
Changes: 08/13/2024 20:02 (33), 08/13/2024 20:06 (35), 08/14/2024 05:31 (10), 05/20/2025 14:37 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!