COROS PACE 3 up to 3.0808.0 BLE Legacy Pairing prng seed

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.
3.1$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic was found in COROS PACE 3 up to 3.0808.0. The affected element is an unknown function of the component BLE Legacy Pairing. Such manipulation leads to prng seed. This vulnerability is listed as CVE-2025-32876. The attack must be carried out from within the local network. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in COROS PACE 3 up to 3.0808.0. Affected by this issue is an unknown function of the component BLE Legacy Pairing. The manipulation with an unknown input leads to a prng seed vulnerability. Using CWE to declare the problem leads to CWE-337. A Pseudo-Random Number Generator (PRNG) is initialized from a predictable seed, such as the process ID or system time. Impacted is confidentiality. CVE summarizes:

An issue was discovered on COROS PACE 3 devices through 3.0808.0. The BLE implementation of the COROS smartwatch does not support LE Secure Connections and instead enforces BLE Legacy Pairing. In BLE Legacy Pairing, the Short-Term Key (STK) can be easily guessed. This requires knowledge of the Temporary Key (TK), which, in the case of the COROS Pace 3, is set to 0 due to the Just Works pairing method. An attacker within Bluetooth range can therefore perform sniffing attacks, allowing eavesdropping on the communication.

This vulnerability is handled as CVE-2025-32876 since 04/11/2025. The exploitation is known to be difficult. The attack needs to approached within the local network. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1600.001 by the MITRE ATT&CK project.

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 vulnerability database at EUVD (EUVD-2025-18749). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.1
VulDB Meta Temp Score: 3.1

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

CVSSv2info

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

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

Exploitinginfo

Class: Prng seed
CWE: CWE-337 / CWE-331 / CWE-330
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

04/11/2025 🔍
06/20/2025 +70 days 🔍
06/20/2025 +0 days 🔍
06/25/2025 +5 days 🔍

Sourcesinfo

Status: Not defined

CVE: CVE-2025-32876 (🔍)
GCVE (CVE): GCVE-0-2025-32876
GCVE (VulDB): GCVE-100-313418
EUVD: 🔍

Entryinfo

Created: 06/20/2025 15:54
Updated: 06/25/2025 04:43
Changes: 06/20/2025 15:54 (52), 06/24/2025 18:24 (1), 06/25/2025 04:43 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!