{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-41093 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-41093 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-41093 is a low-severity use after free vulnerability in Silicon Labs Simplicity SDK, published on 12 Jul 2024. 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-41093 and fix it if it is affected.\n\nWhat it is: CVE-2023-41093 is a low-severity use after free vulnerability in Silicon Labs Simplicity SDK, published on 12 Jul 2024. 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-41093 in the wild and no public exploit code.\n\nAffected product: Silicon Labs Simplicity SDK. 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-41093/ (Markdown: https://insights.sbomify.com/CVE-2023-41093/index.md)","id":"CVE-2023-41093","markdown":"https://insights.sbomify.com/CVE-2023-41093/index.md","name":"CVE-2023-41093","record":{"aliases":["GHSA-jrq9-x3g5-75ph"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Bluetooth SDK","requires_auth":"none","summary":"An attacker with precise timing can intercept packets intended for disconnected devices due to a race condition in the Bluetooth controller.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Silabs","cpe":[{"product":"bluetooth_low_energy_software_development_kit","vendor":"silabs"}],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"Use After Free vulnerability in Silicon Labs Bluetooth SDK on 32 bit, ARM may allow an attacker with precise timing capabilities to intercept a small number of packets intended for a recipient that has left the network.This issue affects Silabs Bluetooth SDK: through 8.0.0.","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":"Loss of confidentiality due to potential race condition in Bluetooth controller Connection_Handle reuse","id":"CVE-2023-41093","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":"Touchlink authentication bypass due to packets processed after timeout or out of range in Ember ZNet","id":"CVE-2023-41094"},"packages":[],"prev":{"headline":"Denial of service in Intel(R) Stratix 10 and Intel(R) Agilex 7 FPGAs","id":"CVE-2023-41092"},"products":["Simplicity SDK"],"published":"2024-07-12","related":[{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2020-15531","kev_date_added":null,"published":"2020-08-19"},{"cvss_score":6.5,"headline":"Memory corruption in n/a","id":"CVE-2020-15532","kev_date_added":null,"published":"2020-08-19"},{"cvss_score":5.3,"headline":"Connection update while closing connection may lead to denial-of-service","id":"CVE-2023-2683","kev_date_added":null,"published":"2023-06-15"}],"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":"2024-08-02","vendors":["Silicon Labs"]},"summary":"An attacker with precise timing can intercept packets intended for disconnected devices due to a race condition in the Bluetooth controller.","url":"https://insights.sbomify.com/CVE-2023-41093/"}