CVE-2024-50597VulnerabilityPublished 2 Apr 2025Updated 3 Nov 2025

CVE-2024-50597: STMicroelectronics X-CUBE-AZRT-H7RS · Integer Underflow (Wrap or Wraparound)

Affects STMicroelectronics X-CUBE-AZRT-H7RSSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Apr 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
STMicroelectronics X-CUBE-AZRT-H7RS	Affected =1.0.0	Fixed in–

AI-suggested

1. Implement strict network segmentation and access controls to isolate vulnerable embedded devices from untrusted networks, reducing exposure to malicious packets. 2. Restrict network access to the HTTP server interface of devices running X-CUBE-AZRTOS-WL to trusted management networks only. 3. Monitor network traffic for anomalous PUT requests or malformed packets targeting the HTTP server. 4. Engage with STMicroelectronics for updates and apply patches or firmware updates as soon as they become available. 5. Where possible, disable or limit HTTP server functionality on embedded devices if not required. 6. Conduct thorough inventory and asset management to identify devices using the affected middleware version 1.0.0. 7. Employ intrusion detection/prevention systems (IDS/IPS) tuned to detect exploitation attempts of integer underflow vulnerabilities in embedded HTTP servers. 8. Develop incident response plans specific to embedded device DoS scenarios to minimize operational impact.

Description

An integer underflow vulnerability exists in the HTTP server PUT request 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 the NetX Duo Component HTTP Server implementation which can be found in x-cube-azrtos-f7\Middlewares\ST\netxduo\addons\http\nxd_http_server.c

Impact

For European organizations, the primary impact is a potential denial of service on embedded or IoT devices running the vulnerable STMicroelectronics middleware. This could disrupt industrial automation systems, automotive control units, or smart devices, leading to operational downtime or degraded service availability. Critical sectors such as manufacturing, automotive, energy, and smart city infrastructure could face interruptions if these devices are exposed to untrusted networks. Although the vulnerability does not compromise data confidentiality or integrity, loss of availability in critical embedded systems can have cascading effects on production lines, safety systems, or service delivery. The medium CVSS score indicates moderate risk, but the actual impact depends on device deployment scale and network exposure. European organizations with extensive use of STMicroelectronics components in their supply chain or operational technology environments should prioritize risk assessments and monitoring.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2025, 20:00 UTC

WeaknessesCWE-191

Technical details

References

Community reviews

Related threats