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.
References
Link | Resource |
---|---|
https://support.coros.com/hc/en-us/articles/20087694119828-COROS-PACE-3-Release-Notes | Release Notes |
https://syss.de | Third Party Advisory |
https://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2025-023.txt | Exploit Third Party Advisory |
https://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2025-023.txt | Exploit Third Party Advisory |
Configurations
Configuration 1 (hide)
AND |
|
History
08 Jul 2025, 14:32
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2025-06-20 14:15
Updated : 2025-07-08 14:32
NVD link : CVE-2025-32876
Mitre link : CVE-2025-32876
CVE.ORG link : CVE-2025-32876
JSON object : View
Products Affected
yftech
- coros_pace_3
- coros_pace_3_firmware
CWE
CWE-306
Missing Authentication for Critical Function