CVE-2020-27640
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Bluetooth handset of Mitel MiVoice 6940 and 6930 MiNet phones with firmware before 1.5.3 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Mitel MiVoice 6940 and 6930 MiNet phones contain an improper Bluetooth pairing mechanism in the handset firmware prior to version 1.5.3. When the phone handset loses its Bluetooth connection, an unauthenticated attacker within Bluetooth range can exploit this condition to pair a rogue Bluetooth device, enabling eavesdropping on conversations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.5.3< 1.5.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the phone modelLocate the device model label on the physical phone or check the device inventory/DHCP fingerprinting records. Confirm it is either Mitel MiVoice 6940 or Mitel MiVoice 6930.Affected if The device is not a MiVoice 6940 or 6930 model.
-
Check the firmware versionAccess the phone's web administration interface or check via the device management console. Navigate to Status or About section to view the firmware version. Compare against 1.5.3.Affected if Firmware version is less than 1.5.3.
-
Verify Bluetooth is enabledCheck the phone's web UI under Bluetooth settings, or inspect the device configuration profile. Confirm Bluetooth is turned on and a handset is paired.Affected if Bluetooth is disabled or no handset is currently paired.
-
Confirm the device lost connection stateReview device logs or monitoring alerts for Bluetooth disconnection events on the phone. This condition triggers the vulnerable pairing window.Affected if The device has experienced Bluetooth connection loss with an active handset.
The device is affected if it is a MiVoice 6940 or 6930 phone running firmware below version 1.5.3, has Bluetooth enabled with a paired handset, and has experienced Bluetooth disconnection events.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.5.3
Update Mitel MiVoice 6940 and 6930 phone firmware to version 1.5.3 or later to remediate the improper pairing mechanism.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-27640 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-27640 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data