# CVE-2022-25836: Auth bypass in n/a

> An unauthenticated attacker can bypass Bluetooth pairing authentication via a man-in-the-middle attack to acquire credentials and impersonate devices.

- **Severity:** High 7.5 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Dec 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-399c-6449-xhh6, ROOT-OS-UBUNTU-2204-CVE-2022-25836, ROOT-OS-UBUNTU-2404-CVE-2022-25836, UBUNTU-CVE-2022-25836

## What is CVE-2022-25836?

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.

### Official 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.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

## Which versions are affected by CVE-2022-25836?

It affects 1 product.


Products: Bluetooth Bluetooth Core Specification.

## How do I fix CVE-2022-25836?

Apply the vendor's patch.

## Is CVE-2022-25836 being exploited?

There is no known exploitation of CVE-2022-25836 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-25837](https://insights.sbomify.com/CVE-2022-25837/): Auth bypass in n/a (high 7.5)
- [CVE-2020-26556](https://insights.sbomify.com/CVE-2020-26556/): Auth bypass in n/a (high 7.5)
- [CVE-2023-24023](https://insights.sbomify.com/CVE-2023-24023/): Weak cryptography in n/a (medium 6.4)
- [CVE-2020-15802](https://insights.sbomify.com/CVE-2020-15802/): Auth bypass in n/a (medium 5.9)
- [CVE-2020-26555](https://insights.sbomify.com/CVE-2020-26555/): Auth bypass in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25836 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2022-25836 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-25836/ (Markdown: https://insights.sbomify.com/CVE-2022-25836/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-25836
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-25836
- OSV: https://osv.dev/vulnerability/CVE-2022-25836

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-25836/
Summaries are generated and may contain mistakes; the official description above is the record.