Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-50385: CWE-459: Incomplete Cleanup in STMicroelectronics X-CUBE-AZRT-H7RS

0
Medium
VulnerabilityCVE-2024-50385cvecve-2024-50385cwe-459
Published: Wed Apr 02 2025 (04/02/2025, 13:41:57 UTC)
Source: CVE Database V5
Vendor/Project: STMicroelectronics
Product: X-CUBE-AZRT-H7RS

Description

A denial of service vulnerability exists in the NetX Component HTTP server functionality of STMicroelectronics X-CUBE-AZRTOS-WL 2.0.0. A specially crafted network packet can lead to denial of service. An attacker can send a malicious packet to trigger this vulnerability.This vulnerability affects X-CUBE-AZRTOS-F7 NetX Duo Component HTTP Server HTTP server v 1.1.0. This HTTP server implementation is contained in this file - x-cube-azrtos-f7\Middlewares\ST\netxduo\addons\http\nxd_http_server.c

AI-Powered Analysis

AILast updated: 11/03/2025, 19:59:16 UTC

Technical Analysis

CVE-2024-50385 is a denial of service (DoS) vulnerability identified in the HTTP server functionality of the NetX component within STMicroelectronics' X-CUBE-AZRTOS-F7 middleware, specifically version 1.0.0. The root cause is an incomplete cleanup process in the HTTP server implementation (file: nxd_http_server.c), which can be triggered by a specially crafted network packet. When exploited, this vulnerability causes the HTTP server to crash or become unresponsive, leading to a denial of service condition. The vulnerability is classified under CWE-459, indicating improper resource cleanup that results in resource exhaustion or instability. The attack vector is network-based (AV:N), requires low attack complexity (AC:L), and low privileges (PR:L), with no user interaction (UI:N) needed. The scope is unchanged (S:U), and the impact is limited to availability (A:H), with no confidentiality or integrity impact. Although no exploits have been observed in the wild, the vulnerability poses a risk to embedded systems and IoT devices that rely on this middleware for HTTP server functionality. The middleware is commonly used in real-time operating system environments for microcontrollers, often found in industrial control systems, automotive, and other embedded applications. The vulnerability's exploitation could disrupt device operations, potentially affecting critical systems that depend on continuous availability.

Potential Impact

For European organizations, the primary impact of CVE-2024-50385 is the potential disruption of embedded systems and IoT devices that utilize the vulnerable STMicroelectronics middleware. This can lead to denial of service conditions, causing operational downtime in industrial automation, manufacturing, automotive systems, and critical infrastructure sectors. Such disruptions could affect production lines, safety systems, or communication networks, leading to financial losses and safety risks. Since the vulnerability does not affect confidentiality or integrity, data breaches are unlikely; however, availability interruptions can have cascading effects in tightly integrated industrial environments. Organizations relying on real-time control systems or embedded devices with this middleware should be aware of the risk of service interruptions and plan accordingly. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits in the future.

Mitigation Recommendations

1. Apply patches or updates from STMicroelectronics as soon as they become available for the X-CUBE-AZRTOS-F7 middleware, specifically addressing version 1.0.0. 2. Implement network segmentation to isolate devices running the vulnerable middleware from untrusted networks, reducing exposure to malicious packets. 3. Deploy network intrusion detection and prevention systems (IDS/IPS) with signatures or anomaly detection rules to identify and block malformed HTTP packets targeting the NetX HTTP server. 4. Restrict access to vulnerable devices by enforcing strict firewall rules allowing only trusted hosts and management stations to communicate with the HTTP server. 5. Monitor device logs and network traffic for signs of repeated malformed packet attempts or service disruptions indicative of exploitation attempts. 6. Where possible, disable or limit HTTP server functionality on embedded devices if not required for operation. 7. Engage with STMicroelectronics support channels to obtain guidance on interim mitigations or workarounds until official patches are released.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
talos
Date Reserved
2024-10-23T18:58:47.945Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 690908517fff0e30cee23598

Added to database: 11/3/2025, 7:53:53 PM

Last enriched: 11/3/2025, 7:59:16 PM

Last updated: 11/5/2025, 11:36:42 AM

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats