{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-55099 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-55099 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-55099 is a low-severity memory corruption vulnerability in Eclipse Foundation USBX, published on 17 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-55099 and fix it if it is affected.\n\nWhat it is: CVE-2025-55099 is a low-severity memory corruption vulnerability in Eclipse Foundation USBX, published on 17 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-55099 in the wild and no public exploit code.\n\nAffected product: Eclipse Foundation USBX. 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-2025-55099/ (Markdown: https://insights.sbomify.com/CVE-2025-55099/index.md)","id":"CVE-2025-55099","markdown":"https://insights.sbomify.com/CVE-2025-55099/index.md","name":"CVE-2025-55099","record":{"aliases":[],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ThreadX USBX module","requires_auth":"none","summary":"An attacker can trigger an out-of-bounds read in the USBX audio class driver via a malicious USB descriptor, potentially causing a crash or leaking memory.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"threadx_usbx","vendor":"eclipse"}],"cvss":{"score":2.4,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"In USBX before 6.4.3, the USB support module for Eclipse Foundation ThreadX, there was a potential out of bound read issue in _ux_host_class_audio_alternate_setting_locate() when parsing a descriptor with attacker-controlled frequency fields.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Potential out-of-bounds read in _ux_host_class_audio_alternate_setting_locate()","id":"CVE-2025-55099","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Potential out-of-bounds read in _ux_host_class_audio10_sam_parse_func()","id":"CVE-2025-55100"},"packages":[],"prev":{"headline":"Potential out-of-bounds read in _ux_host_class_audio_device_type_get()","id":"CVE-2025-55098"},"products":["USBX"],"published":"2025-10-17","related":[{"cvss_score":9.8,"headline":"Potential buffer overflow in function DFU upload in Azure RTOS USBX","id":"CVE-2022-29246","kev_date_added":null,"published":"2022-05-24"},{"cvss_score":8.6,"headline":"Azure RTOS USBX Host PIMA vulnerable to read integer underflow with buffer overflow","id":"CVE-2022-39293","kev_date_added":null,"published":"2022-10-13"},{"cvss_score":7.6,"headline":"USBX Host CDC ECM integer underflow with buffer overflow","id":"CVE-2022-36063","kev_date_added":null,"published":"2022-10-10"},{"cvss_score":7.5,"headline":"Buffer overflow on HUB descriptor in Azure RTOS USBX","id":"CVE-2022-29223","kev_date_added":null,"published":"2022-05-24"},{"cvss_score":7.2,"headline":"Azure RTOS USBX Remote Code Execution Vulnerability","id":"CVE-2023-48695","kev_date_added":null,"published":"2023-12-05"},{"cvss_score":6.8,"headline":"Azure RTOS USBX Remote Code Execution Vulnerability","id":"CVE-2023-48694","kev_date_added":null,"published":"2023-12-05"},{"cvss_score":6.8,"headline":"Azure RTOS USBX Remote Code Execution Vulnerability","id":"CVE-2023-48698","kev_date_added":null,"published":"2023-12-05"}],"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":"partial"},"state":"PUBLISHED","updated":"2025-10-17","vendors":["Eclipse Foundation"]},"summary":"An attacker can trigger an out-of-bounds read in the USBX audio class driver via a malicious USB descriptor, potentially causing a crash or leaking memory.","url":"https://insights.sbomify.com/CVE-2025-55099/"}