# CVE-2020-27639: Auth bypass in n/a

> An unauthenticated attacker within Bluetooth range can pair a rogue device to eavesdrop on conversations due to improper pairing mechanisms in Mitel SIP phones.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-622c-r8r9-89jj

## What is CVE-2020-27639?

CVE-2020-27639 is a high-severity authentication bypass vulnerability in n/a, published on 18 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Bluetooth handset of Mitel MiVoice 6873i, 6930, and 6940 SIP phones with firmware before 5.1.0.SP6 could allow an unauthenticated attacker within Bluetooth range to pair a rogue Bluetooth device when a phone handset loses connection, due to an improper pairing mechanism. A successful exploit could allow an attacker to eavesdrop on conversations.

## Which versions are affected by CVE-2020-27639?

It affects 3 products.


Products: Mitel 6873i Sip Firmware, Mitel 6930 Sip Firmware, Mitel 6940 Sip Firmware.

## How do I fix CVE-2020-27639?

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

## Is CVE-2020-27639 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-27639 and fix it if it is affected.

What it is: CVE-2020-27639 is a high-severity authentication bypass vulnerability in n/a, published on 18 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-27639 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-2020-27639/ (Markdown: https://insights.sbomify.com/CVE-2020-27639/index.md)
```

## Sources

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

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