{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-29223 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-29223 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-29223 is a high-severity memory corruption vulnerability in azure-rtos usbx, published on 24 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-29223 and fix it if it is affected.\n\nWhat it is: CVE-2022-29223 is a high-severity memory corruption vulnerability in azure-rtos usbx, published on 24 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-29223 in the wild and no public exploit code.\n\nAffected product: azure-rtos 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-2022-29223/ (Markdown: https://insights.sbomify.com/CVE-2022-29223/index.md)","id":"CVE-2022-29223","markdown":"https://insights.sbomify.com/CVE-2022-29223/index.md","name":"CVE-2022-29223","record":{"aliases":["GHSA-2qc5-385m-x862"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Azure RTOS USBX","requires_auth":"none","summary":"An attacker can trigger a buffer overflow in Azure RTOS USBX by providing a malicious HUB descriptor, potentially leading to code execution or denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"threadx_usbx","vendor":"eclipse"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"Azure RTOS USBX is a USB host, device, and on-the-go (OTG) embedded stack. In versions prior to 6.1.10, an attacker can cause a buffer overflow by providing the Azure RTOS USBX host stack a HUB descriptor with `bNbPorts` set to a value greater than `UX_MAX_TT` which defaults to 8. For a `bNbPorts` value of 255, the implementation of `ux_host_class_hub_descriptor_get` function will modify the contents of `hub` -\u003e `ux_host_class_hub_device` -\u003e `ux_device_hub_tt` array violating the end boundary by 255 - `UX_MAX_TT` items. The USB host stack needs to validate the number of ports reported by the hub, and if the value is larger than UX_MAX_TT, USB stack needs to reject the request. This fix has been included in USBX release 6.1.10.","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":"Buffer overflow on HUB descriptor in Azure RTOS USBX","id":"CVE-2022-29223","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Segmentation fault leading to crash in Envoy","id":"CVE-2022-29224"},"packages":[],"prev":{"headline":"Improper Certificate Validation in Pion DTLS","id":"CVE-2022-29222"},"products":["usbx"],"published":"2022-05-24","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.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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["azure-rtos"]},"summary":"An attacker can trigger a buffer overflow in Azure RTOS USBX by providing a malicious HUB descriptor, potentially leading to code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2022-29223/"}