{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-25836 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-25836 is a high-severity authentication bypass vulnerability in n/a, published on 12 Dec 2022. 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-2022-25836 and fix it if it is affected.\n\nWhat it is: CVE-2022-25836 is a high-severity authentication bypass vulnerability in n/a, published on 12 Dec 2022. 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-2022-25836 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-25836/ (Markdown: https://insights.sbomify.com/CVE-2022-25836/index.md)","id":"CVE-2022-25836","markdown":"https://insights.sbomify.com/CVE-2022-25836/index.md","name":"CVE-2022-25836","record":{"aliases":["GHSA-399c-6449-xhh6","ROOT-OS-UBUNTU-2204-CVE-2022-25836","ROOT-OS-UBUNTU-2404-CVE-2022-25836","UBUNTU-CVE-2022-25836"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["account_takeover","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Bluetooth LE pairing","requires_auth":"none","summary":"An unauthenticated attacker can bypass Bluetooth pairing authentication via a man-in-the-middle attack to acquire credentials and impersonate devices.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bluetooth_core_specification","vendor":"bluetooth"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-294","name":"Authentication Bypass by Capture-replay"}],"description":"Bluetooth® Low Energy Pairing in Bluetooth Core Specification v4.0 through v5.3 may permit an unauthenticated MITM to acquire credentials with two pairing devices via adjacent access when the MITM negotiates Legacy Passkey Pairing with the pairing Initiator and Secure Connections Passkey Pairing with the pairing Responder and brute forces the Passkey entered by the user into the Initiator. The MITM attacker can use the identified Passkey value to complete authentication with the Responder via Bluetooth pairing method confusion.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Auth bypass in n/a","id":"CVE-2022-25836","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in n/a","id":"CVE-2022-25837"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2022-25834"},"products":["n/a"],"published":"2022-12-12","related":[{"cvss_score":7.5,"headline":"Auth bypass in n/a","id":"CVE-2022-25837","kev_date_added":null,"published":"2022-12-12"},{"cvss_score":7.5,"headline":"Auth bypass in n/a","id":"CVE-2020-26556","kev_date_added":null,"published":"2021-05-24"},{"cvss_score":6.4,"headline":"Weak cryptography in n/a","id":"CVE-2023-24023","kev_date_added":null,"published":"2023-11-28"},{"cvss_score":5.9,"headline":"Auth bypass in n/a","id":"CVE-2020-15802","kev_date_added":null,"published":"2020-09-11"},{"cvss_score":5.4,"headline":"Auth bypass in n/a","id":"CVE-2020-26555","kev_date_added":null,"published":"2021-05-24"},{"cvss_score":5.3,"headline":"Race condition in n/a","id":"CVE-2021-31615","kev_date_added":null,"published":"2021-06-25"}],"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-22","vendors":["n/a"]},"summary":"An unauthenticated attacker can bypass Bluetooth pairing authentication via a man-in-the-middle attack to acquire credentials and impersonate devices.","url":"https://insights.sbomify.com/CVE-2022-25836/"}