Bluetooth Core Specification up to 5.3 Pairing channel accessible

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.00

Summaryinfo

A vulnerability has been found in Bluetooth Core Specification up to 5.3 and classified as critical. Affected by this vulnerability is an unknown functionality of the component Pairing. This manipulation causes channel accessible. This vulnerability is handled as CVE-2022-25837. The attack can only be done within the local network. There is not any exploit available.

Detailsinfo

A vulnerability classified as problematic was found in Bluetooth Core Specification up to 5.3. Affected by this vulnerability is an unknown part of the component Pairing. The manipulation with an unknown input leads to a channel accessible vulnerability. The CWE definition for the vulnerability is CWE-300. The product does not adequately verify the identity of actors at both ends of a communication channel, or does not adequately ensure the integrity of the channel, in a way that allows the channel to be accessed or influenced by an actor that is not an endpoint. As an impact it is known to affect confidentiality. The summary by CVE is:

Bluetooth® Pairing in Bluetooth Core Specification v1.0B through v5.3 may permit an unauthenticated MITM to acquire credentials with two pairing devices via adjacent access when at least one device supports BR/EDR Secure Connections pairing and the other BR/EDR Legacy PIN code pairing if the MITM negotiates BR/EDR Secure Simple Pairing in Secure Connections mode using the Passkey association model with the pairing Initiator and BR/EDR Legacy PIN code pairing with the pairing Responder and brute forces the Passkey entered by the user into the Responder as a 6-digit PIN code. The MITM attacker can use the identified PIN code value as the Passkey value to complete authentication with the Initiator via Bluetooth pairing method confusion.

The weakness was released 12/12/2022. The advisory is shared at bluetooth.com. This vulnerability is known as CVE-2022-25837 since 02/24/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1557 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at EUVD (EUVD-2022-30477) and CERT Bund (WID-SEC-2026-1993). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Affected

  • Google Android

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.3

VulDB Base Score: 3.1
VulDB Temp Score: 3.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Channel accessible
CWE: CWE-300
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

02/24/2022 🔍
12/12/2022 +291 days 🔍
12/12/2022 +0 days 🔍
06/18/2026 +1284 days 🔍

Sourcesinfo

Advisory: bluetooth.com
Status: Not defined

CVE: CVE-2022-25837 (🔍)
GCVE (CVE): GCVE-0-2022-25837
GCVE (VulDB): GCVE-100-215281
EUVD: 🔍
CERT Bund: WID-SEC-2026-1993 - Android Patchday Juni 2026: Mehrere Schwachstellen

Entryinfo

Created: 12/12/2022 07:56
Updated: 06/18/2026 11:56
Changes: 12/12/2022 07:56 (38), 01/02/2023 15:16 (11), 04/23/2025 03:25 (16), 05/08/2026 11:15 (1), 06/18/2026 11:56 (7)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!