{"answers":{"affected":"It affects 14 products.","exploited":"There is no known exploitation of CVE-2022-46399 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-46399 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-46399 is a high-severity denial of service vulnerability in n/a, published on 19 Dec 2022. 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-2022-46399 and fix it if it is affected.\n\nWhat it is: CVE-2022-46399 is a high-severity denial of service vulnerability in n/a, published on 19 Dec 2022. 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-2022-46399 in the wild and no public exploit code.\n\nAffected product: n/a. 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-46399/ (Markdown: https://insights.sbomify.com/CVE-2022-46399/index.md)","id":"CVE-2022-46399","markdown":"https://insights.sbomify.com/CVE-2022-46399/index.md","name":"CVE-2022-46399","record":{"aliases":["GHSA-6w9r-9p3m-qrj9"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Bluetooth module firmware","requires_auth":"none","summary":"The Microchip RN4870 Bluetooth module firmware becomes unresponsive when handling a specific connection request timeout, causing a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bm64_firmware","vendor":"microchip"},{"product":"bm70_firmware","vendor":"microchip"},{"product":"bm71_firmware","vendor":"microchip"},{"product":"bm77_firmware","vendor":"microchip"},{"product":"bm78_firmware","vendor":"microchip"},{"product":"bm83_firmware","vendor":"microchip"},{"product":"is1870_firmware","vendor":"microchip"},{"product":"is1871_firmware","vendor":"microchip"},{"product":"pic32cx1012bz25048_firmware","vendor":"microchip"},{"product":"pic_lightblue_explorer_demo_firmware","vendor":"microchip"},{"product":"rn4678_firmware","vendor":"microchip"},{"product":"rn4870_firmware","vendor":"microchip"},{"product":"rn4871_firmware","vendor":"microchip"},{"product":"wbz451_firmware","vendor":"microchip"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"The Microchip RN4870 module firmware 1.43 (and the Microchip PIC LightBlue Explorer Demo 4.2 DT100112) is unresponsive with ConReqTimeoutZero.","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":"Denial of service in n/a","id":"CVE-2022-46399","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"Auth bypass in n/a","id":"CVE-2022-46400"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2022-46397"},"products":["n/a"],"published":"2022-12-19","related":[{"cvss_score":5.4,"headline":"Security feature bypass in n/a","id":"CVE-2022-46401","kev_date_added":null,"published":"2022-12-19"}],"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-17","vendors":["n/a"]},"summary":"The Microchip RN4870 Bluetooth module firmware becomes unresponsive when handling a specific connection request timeout, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2022-46399/"}