{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-10134 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-10134 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-10134 is a medium-severity authentication bypass vulnerability in Bluetooth LE, published on 19 May 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-10134 and fix it if it is affected.\n\nWhat it is: CVE-2020-10134 is a medium-severity authentication bypass vulnerability in Bluetooth LE, published on 19 May 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-10134 in the wild and no public exploit code.\n\nAffected product: Bluetooth LE. 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-10134/ (Markdown: https://insights.sbomify.com/CVE-2020-10134/index.md)","id":"CVE-2020-10134","markdown":"https://insights.sbomify.com/CVE-2020-10134/index.md","name":"CVE-2020-10134","record":{"aliases":["GHSA-4fx5-wvjj-h2jp","UBUNTU-CVE-2020-10134"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Bluetooth stack","requires_auth":"none","summary":"An adjacent attacker can bypass Bluetooth authentication via method confusion, gaining unauthorized access to device operations and data.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"bluetooth_core","vendor":"bluetooth"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-436","name":"Interpretation Conflict"},{"id":"CWE-351","name":"Insufficient Type Distinction"}],"description":"Pairing in Bluetooth® Core v5.2 and earlier may permit an unauthenticated attacker to acquire credentials with two pairing devices via adjacent access when the unauthenticated user initiates different pairing methods in each peer device and an end-user erroneously completes both pairing procedures with the MITM using the confirmation number of one peer as the passkey of the other. An adjacent, unauthenticated attacker could be able to initiate any Bluetooth operation on either attacked device exposed by the enabled Bluetooth profiles. This exposure may be limited when the user must authorize certain access explicitly, but so long as a user assumes that it is the intended remote device requesting permissions, device-local protections may be weakened.","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":"Bluetooth devices supporting LE and specific BR/EDR implementations are vulnerable to method confusion attacks","id":"CVE-2020-10134","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":"Bluetooth devices supporting BR/EDR v5.2 and earlier are vulnerable to impersonation attacks","id":"CVE-2020-10135"},"packages":[],"prev":{"headline":"CVE-2020-10132","id":"CVE-2020-10132"},"products":["LE"],"published":"2020-05-19","related":[{"cvss_score":5.4,"headline":"Bluetooth devices supporting BR/EDR v5.2 and earlier are vulnerable to impersonation attacks","id":"CVE-2020-10135","kev_date_added":null,"published":"2020-05-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Bluetooth"]},"summary":"An adjacent attacker can bypass Bluetooth authentication via method confusion, gaining unauthorized access to device operations and data.","url":"https://insights.sbomify.com/CVE-2020-10134/"}