Metrics
Affected Vendors & Products
Tue, 08 Jul 2025 15:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Yftech
Yftech coros Pace 3 Yftech coros Pace 3 Firmware |
|
| CPEs | cpe:2.3:h:yftech:coros_pace_3:-:*:*:*:*:*:*:* cpe:2.3:o:yftech:coros_pace_3_firmware:*:*:*:*:*:*:*:* |
|
| Vendors & Products |
Yftech
Yftech coros Pace 3 Yftech coros Pace 3 Firmware |
Tue, 24 Jun 2025 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
ssvc
|
Tue, 24 Jun 2025 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-306 | |
| Metrics |
cvssV3_1
|
Fri, 20 Jun 2025 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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 |
|
Status: PUBLISHED
Assigner: mitre
Published: 2025-06-20T00:00:00.000Z
Updated: 2025-06-24T15:27:06.224Z
Reserved: 2025-04-11T00:00:00.000Z
Link: CVE-2025-32876
Updated: 2025-06-24T13:49:54.056Z
Status : Analyzed
Published: 2025-06-20T14:15:27.877
Modified: 2025-07-08T14:32:59.510
Link: CVE-2025-32876
No data.
ReportizFlow