Skip to content
Fencer Vulns
high 8.5

CVE-2024-45064 json

A buffer overflow vulnerability exists in the FileX Internal RAM interface functionality of STMicroelectronics X-CUBE-AZRTOS-WL 2.0.0.

published 2025-04-02 19 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-9543

cvss
8.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits
0
none known

Summary

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.

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
19 mo ago

Exploit prediction

1.11% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • talosintelligence.com https://talosintelligence.com/vulnerability_reports/TALOS-2024-2096 referenced PoC, tagged "exploit" by a source, unverified
  • talosintelligence.com https://www.talosintelligence.com/vulnerability_reports/TALOS-2024-2096 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 8.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • STMicroelectronics X-CUBE-AZRT-H7RS
  • STMicroelectronics X-CUBE-AZRTOS-F4
  • STMicroelectronics X-CUBE-AZRTOS-F7
  • STMicroelectronics X-CUBE-AZRTOS-G0
  • STMicroelectronics X-CUBE-AZRTOS-G4
  • STMicroelectronics X-CUBE-AZRTOS-H7
  • STMicroelectronics X-CUBE-AZRTOS-L4
  • STMicroelectronics X-CUBE-AZRTOS-L5
  • STMicroelectronics X-CUBE-AZRTOS-WB
  • STMicroelectronics X-CUBE-AZRTOS-WL

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.