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

CVE-2024-50594: 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, 07:57 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. Monitor network traffic to devices running STMicroelectronics X-CUBE-AZRTOS-WL middleware for unusual or repeated HTTP PUT requests that could indicate exploitation attempts. 2. Restrict network access to embedded devices hosting the vulnerable HTTP server by implementing network segmentation and firewall rules to limit exposure only to trusted management networks. 3. Employ intrusion detection/prevention systems (IDS/IPS) with signatures or heuristics capable of detecting anomalous HTTP PUT request patterns targeting embedded devices. 4. Engage with STMicroelectronics for updates or patches addressing this vulnerability and plan timely deployment once available. 5. Where possible, disable or limit HTTP server functionality on embedded devices if not required for operation. 6. Conduct regular firmware and middleware audits to identify devices running the affected version (1.0.0) and prioritize remediation. 7. Implement robust device authentication and network access controls to reduce the risk of unauthorized network access to vulnerable devices. 8. Prepare incident response plans that include procedures for handling denial of service events affecting embedded systems.

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 series of network requests can lead to denial of service. An attacker can send a sequence of malicious packets to trigger this vulnerability.This vulnerability affects the NetX Duo Web Component HTTP Server implementation which can be found in x-cube-azrtos-f7\Middlewares\ST\netxduo\addons\web\nx_web_http_server.c

Impact

The primary impact of CVE-2024-50594 is denial of service, which can disrupt the availability of embedded devices running the affected STMicroelectronics middleware. For European organizations, especially those in industrial automation, automotive manufacturing, and IoT sectors that rely on STMicroelectronics microcontrollers and middleware, this vulnerability could cause operational downtime, impacting production lines, critical infrastructure, or connected devices. While the vulnerability does not compromise confidentiality or integrity, the loss of availability can lead to significant operational and financial consequences, including halted manufacturing processes, safety system failures, or service interruptions. The medium CVSS score reflects moderate risk, but the impact could be amplified in environments where uptime is critical. Since no known exploits exist yet, the threat is currently theoretical but should be addressed proactively. The vulnerability could also be leveraged as part of a larger attack chain to cause disruption or distract from other malicious activities.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2025, 19:59 UTC

WeaknessesCWE-191

Technical details

References

Community reviews

Related threats