{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-48694 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-48694 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-48694 is a medium-severity use after free vulnerability in azure-rtos usbx, published on 5 Dec 2023. 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-2023-48694 and fix it if it is affected.\n\nWhat it is: CVE-2023-48694 is a medium-severity use after free vulnerability in azure-rtos usbx, published on 5 Dec 2023. 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-2023-48694 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-2023-48694/ (Markdown: https://insights.sbomify.com/CVE-2023-48694/index.md)","id":"CVE-2023-48694","markdown":"https://insights.sbomify.com/CVE-2023-48694/index.md","name":"CVE-2023-48694","record":{"aliases":["GHSA-qjw8-7w86-44qj"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Azure RTOS USBX","requires_auth":"none","summary":"Attackers can achieve remote code execution in Azure RTOS USBX via expired pointer dereference and type confusion flaws in the host stack.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"threadx_usbx","vendor":"eclipse"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-843","name":"Access of Resource Using Incompatible Type"},{"id":"CWE-825","name":"Expired Pointer Dereference"}],"description":"Azure RTOS USBX is a USB host, device, and on-the-go (OTG) embedded stack, that is fully integrated with Azure RTOS ThreadX. An attacker can cause remote code execution due to expired pointer dereference and type confusion vulnerabilities in Azure RTOS USBX. The affected components include functions/processes in host stack and host class, related to device linked classes, ASIX, Prolific, SWAR, audio, CDC ECM in RTOS v6.2.1 and below. The fixes have been included in USBX release 6.3.0. Users are advised to upgrade. There are no known workarounds for 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":"Azure RTOS USBX Remote Code Execution Vulnerability","id":"CVE-2023-48694","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Azure RTOS USBX Remote Code Execution Vulnerability","id":"CVE-2023-48695"},"packages":[],"prev":{"headline":"Azure RTOS ThreadX Remote Code Execution Vulnerability","id":"CVE-2023-48693"},"products":["usbx"],"published":"2023-12-05","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-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":"total"},"state":"PUBLISHED","updated":"2024-10-15","vendors":["azure-rtos"]},"summary":"Attackers can achieve remote code execution in Azure RTOS USBX via expired pointer dereference and type confusion flaws in the host stack.","url":"https://insights.sbomify.com/CVE-2023-48694/"}