{"answers":{"affected":"It affects 10 products.","exploited":"There is no known exploitation of CVE-2024-45064 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-45064 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-45064 is a high-severity memory corruption vulnerability in STMicroelectronics X-CUBE-AZRT-H7RS, published on 2 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-45064 and fix it if it is affected.\n\nWhat it is: CVE-2024-45064 is a high-severity memory corruption vulnerability in STMicroelectronics X-CUBE-AZRT-H7RS, published on 2 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-45064 in the wild and no public exploit code.\n\nAffected product: STMicroelectronics X-CUBE-AZRT-H7RS. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-45064/ (Markdown: https://insights.sbomify.com/CVE-2024-45064/index.md)","id":"CVE-2024-45064","markdown":"https://insights.sbomify.com/CVE-2024-45064/index.md","name":"CVE-2024-45064","record":{"aliases":["GHSA-h8hc-8pw6-mf3x"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"STM32 RTOS middleware","requires_auth":"low_privilege","summary":"A buffer overflow in STMicroelectronics X-CUBE-AZRTOS allows remote attackers to execute arbitrary code via crafted network packets.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"x-cube-azrt-h7rs","vendor":"st"},{"product":"x-cube-azrtos-f4","vendor":"st"},{"product":"x-cube-azrtos-f7","vendor":"st"},{"product":"x-cube-azrtos-g0","vendor":"st"},{"product":"x-cube-azrtos-g4","vendor":"st"},{"product":"x-cube-azrtos-h7","vendor":"st"},{"product":"x-cube-azrtos-l4","vendor":"st"},{"product":"x-cube-azrtos-l5","vendor":"st"},{"product":"x-cube-azrtos-wb","vendor":"st"},{"product":"x-cube-azrtos-wl","vendor":"st"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Memory corruption in X-CUBE-AZRT-H7RS","id":"CVE-2024-45064","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"This candidate was in a CNA pool that was not assigned to any issues during 2024.","id":"CVE-2024-45065"},"packages":[],"prev":{"headline":"Multiple issues in ctl(4) CAM Target Layer","id":"CVE-2024-45063"},"products":["X-CUBE-AZRT-H7RS","X-CUBE-AZRTOS-F4","X-CUBE-AZRTOS-F7","X-CUBE-AZRTOS-G0","X-CUBE-AZRTOS-G4","X-CUBE-AZRTOS-H7","X-CUBE-AZRTOS-L4","X-CUBE-AZRTOS-L5","X-CUBE-AZRTOS-WB","X-CUBE-AZRTOS-WL"],"published":"2025-04-02","related":[{"cvss_score":6.5,"headline":"Denial of service in X-CUBE-AZRT-H7RS","id":"CVE-2024-50384","kev_date_added":null,"published":"2025-04-02"},{"cvss_score":6.5,"headline":"Denial of service in X-CUBE-AZRT-H7RS","id":"CVE-2024-50385","kev_date_added":null,"published":"2025-04-02"},{"cvss_score":4.3,"headline":"Integer overflow in X-CUBE-AZRT-H7RS","id":"CVE-2024-50594","kev_date_added":null,"published":"2025-04-02"},{"cvss_score":4.3,"headline":"Integer overflow in X-CUBE-AZRT-H7RS","id":"CVE-2024-50595","kev_date_added":null,"published":"2025-04-02"},{"cvss_score":4.3,"headline":"Integer overflow in X-CUBE-AZRT-H7RS","id":"CVE-2024-50596","kev_date_added":null,"published":"2025-04-02"},{"cvss_score":4.3,"headline":"Integer overflow in X-CUBE-AZRT-H7RS","id":"CVE-2024-50597","kev_date_added":null,"published":"2025-04-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-02","vendors":["STMicroelectronics"]},"summary":"A buffer overflow in STMicroelectronics X-CUBE-AZRTOS allows remote attackers to execute arbitrary code via crafted network packets.","url":"https://insights.sbomify.com/CVE-2024-45064/"}