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

CVE-2024-50595: 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

European organizations should first identify any embedded systems or IoT devices using STMicroelectronics X-CUBE-AZRTOS-WL 2.0.0 or specifically the X-CUBE-AZRT-H7RS middleware. Network segmentation and strict access controls should be implemented to limit exposure of vulnerable devices to untrusted networks. Monitoring network traffic for unusual PUT request patterns targeting HTTP servers on these devices can help detect exploitation attempts. Since no official patches are currently available, organizations should engage with STMicroelectronics for updates or workarounds. Where feasible, disabling or restricting HTTP PUT functionality on affected devices can reduce attack surface. Additionally, implementing rate limiting and anomaly detection on network interfaces can mitigate the risk of denial of service. Finally, incorporating these devices into vulnerability management and incident response plans will improve preparedness against exploitation attempts.

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 Component HTTP Server implementation which can be found in x-cube-azrtos-f7\Middlewares\ST\netxduo\addons\http\nxd_http_server.c

Impact

The primary impact of CVE-2024-50595 is denial of service, which can disrupt the availability of embedded devices running STMicroelectronics X-CUBE-AZRTOS-WL 2.0.0 with the vulnerable NetX Duo HTTP server. For European organizations, this could affect industrial automation systems, IoT devices, and critical infrastructure components that use this middleware, potentially leading to operational downtime, loss of productivity, or safety risks if control systems become unresponsive. Although the vulnerability does not compromise data confidentiality or integrity, the loss of service could have cascading effects in environments where continuous device availability is critical. The medium severity rating reflects that exploitation requires network access and low privileges but no user interaction, making it feasible for attackers with internal network presence or access to exposed devices. The lack of known exploits reduces immediate risk, but the potential for targeted disruption in sectors such as manufacturing, energy, or transportation is notable.

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