{"answers":{"affected":"It affects 7 products.","exploited":"There is no known exploitation of CVE-2020-16630 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-16630 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-16630 is a medium-severity authentication bypass vulnerability in n/a, published on 20 Sep 2021. 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-2020-16630 and fix it if it is affected.\n\nWhat it is: CVE-2020-16630 is a medium-severity authentication bypass vulnerability in n/a, published on 20 Sep 2021. 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-2020-16630 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-2020-16630/ (Markdown: https://insights.sbomify.com/CVE-2020-16630/index.md)","id":"CVE-2020-16630","markdown":"https://insights.sbomify.com/CVE-2020-16630/index.md","name":"CVE-2020-16630","record":{"aliases":["GHSA-h5cr-94cg-hxmr"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["security_bypass","data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TI BLE stack","requires_auth":"none","summary":"Attackers can bypass Bluetooth authentication checks by spoofing MAC addresses, gaining unauthorized read and write access to protected device attributes.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"15.4-stack","vendor":"ti"},{"product":"ble5-stack","vendor":"ti"},{"product":"dynamic_multi-protocal_manager","vendor":"ti"},{"product":"easylink","vendor":"ti"},{"product":"openthread","vendor":"ti"},{"product":"real-time_operating_system","vendor":"ti"},{"product":"z-stack","vendor":"ti"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"TI’s BLE stack caches and reuses the LTK’s property for a bonded mobile. A LTK can be an unauthenticated-and-no-MITM-protection key created by Just Works or an authenticated-and-MITM-protection key created by Passkey Entry, Numeric Comparison or OOB. Assume that a victim mobile uses secure pairing to pair with a victim BLE device based on TI chips and generate an authenticated-and-MITM-protection LTK. If a fake mobile with the victim mobile’s MAC address uses Just Works and pairs with the victim device, the generated LTK still has the property of authenticated-and-MITM-protection. Therefore, the fake mobile can access attributes with the authenticated read/write permission.","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":"Auth bypass in n/a","id":"CVE-2020-16630","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-16632"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2020-16629"},"products":["n/a"],"published":"2021-09-20","related":[],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can bypass Bluetooth authentication checks by spoofing MAC addresses, gaining unauthorized read and write access to protected device attributes.","url":"https://insights.sbomify.com/CVE-2020-16630/"}