CVE-2024-45064 in X-CUBE-AZRT-H7RS
Summary
by MITRE • 04/02/2025
A buffer overflow vulnerability exists in the FileX Internal RAM interface functionality of STMicroelectronics X-CUBE-AZRTOS-WL 2.0.0. A specially crafted set of network packets can lead to code execution. An attacker can send a sequence of requests to trigger this vulnerability.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 09/05/2025
The buffer overflow vulnerability identified as CVE-2024-45064 resides within the FileX Internal RAM interface functionality of STMicroelectronics X-CUBE-AZRTOS-WL version 2.0.0, representing a critical security flaw that could enable remote code execution. This vulnerability specifically targets the embedded real-time operating system components used in IoT and embedded device applications, making it particularly concerning for industrial control systems and connected devices that rely on STMicroelectronics middleware for network communication. The flaw manifests when the system processes network packets through the FileX RAM interface, where insufficient input validation allows malicious data to overflow buffer boundaries and potentially overwrite critical memory regions.
The technical implementation of this vulnerability stems from improper bounds checking within the FileX component that handles internal RAM operations for Azure RTOS Wireless Library implementations. When processing network packets, the system fails to adequately validate the size or content of incoming data before copying it into fixed-size memory buffers. This classic buffer overflow condition creates opportunities for attackers to manipulate program execution flow by overwriting return addresses, function pointers, or other critical control data structures within the application's memory space. The vulnerability operates at the network protocol level, making it accessible to remote attackers who can craft malicious packets to exploit the flaw without requiring physical access to the device.
The operational impact of CVE-2024-45064 extends beyond simple system instability, as successful exploitation could result in complete system compromise and unauthorized code execution. Attackers leveraging this vulnerability could potentially gain persistent access to affected devices, enabling them to install backdoors, exfiltrate sensitive data, or use compromised devices as launch points for broader network attacks. Given that this vulnerability affects middleware components used in IoT deployments, the potential attack surface includes industrial control systems, smart grid infrastructure, automotive applications, and other embedded systems where STMicroelectronics X-CUBE-AZRTOS-WL is deployed. The remote nature of the attack vector means that adversaries could exploit this flaw from anywhere on the network, making it particularly dangerous for connected environments.
Mitigation strategies for CVE-2024-45064 should prioritize immediate firmware updates from STMicroelectronics to address the buffer overflow in the FileX RAM interface component. Organizations should also implement network segmentation and access controls to limit exposure of affected systems to untrusted networks, while monitoring for suspicious network traffic patterns that could indicate exploitation attempts. The vulnerability aligns with CWE-121, which describes stack-based buffer overflow conditions, and could be mapped to ATT&CK technique T1059.007 for remote code execution through network services. Additionally, defensive measures including input validation, address space layout randomization, and stack canaries should be considered as supplementary protections, though the primary remediation must focus on the vendor-provided patch addressing the specific FileX interface implementation flaw.