# CVE-2021-37577: Security feature bypass in n/a

> Man-in-the-middle attackers can bypass Bluetooth pairing authentication to complete secure connections using the correct passkey.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Oct 2024
- **Updated:** 15 Nov 2024
- **Also known as:** GHSA-f7h9-hrg7-94fg, UBUNTU-CVE-2021-37577

## What is CVE-2021-37577?

CVE-2021-37577 is a medium-severity vulnerability in n/a, published on 1 Oct 2024. 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 LE and BR/EDR Secure Connections pairing and Secure Simple Pairing using the Passkey entry protocol in Bluetooth Core Specifications 2.1 through 5.3 may permit an unauthenticated man-in-the-middle attacker to identify the Passkey used during pairing by reflection of a crafted public key with the same X coordinate as the offered public key and by reflection of the authentication evidence of the initiating device, potentially permitting this attacker to complete authenticated pairing with the responding device using the correct Passkey for the pairing session. This is a related issue to CVE-2020-26558.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2021-37577?


## How do I fix CVE-2021-37577?

No fix has been published for CVE-2021-37577 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-37577 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-37577 and fix it if it is affected.

What it is: CVE-2021-37577 is a medium-severity vulnerability in n/a, published on 1 Oct 2024. 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-2021-37577 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-2021-37577/ (Markdown: https://insights.sbomify.com/CVE-2021-37577/index.md)
```

## Sources

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

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