Overview
This report details a critical vulnerability, identified as CVE-2025-48705, found within COROS PACE 3 versions through 3.0808.0. The vulnerability, a NULL pointer dereference, can be exploited to force the device to reboot, potentially compromising the system and leading to data leakage. Given the severity of this vulnerability, it is essential that affected systems are patched as soon as possible.
Vulnerability Summary
CVE ID: CVE-2025-48705
Severity: High (CVSS: 7.5)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Forced reboot of the device which could lead to system compromise or data leakage
Affected Products
A new way to communicate
Ameeba Chat is built on encrypted identity, not personal profiles.
Message, call, share files, and coordinate with identities kept separate.
- • Encrypted identity
- • Ameeba Chat authenticates access
- • Aliases and categories
- • End-to-end encrypted chat, calls, and files
- • Secure notes for sensitive information
Private communication, rethought.
Product | Affected Versions
COROS PACE 3 | Up to 3.0808.0
How the Exploit Works
The vulnerability stems from a NULL pointer dereference within the COROS PACE 3 device. By sending a specifically crafted BLE (Bluetooth Low Energy) message to the device, an attacker can exploit this vulnerability to force the device into a reboot. This can potentially compromise the system, and in worst-case scenarios, lead to data leakage.
Conceptual Example Code
The following is a conceptual example of a malicious BLE payload that could potentially exploit this vulnerability:
BLE /connect/device
Host: target.coros.com
{ "malicious_payload": "NULL_POINTER_DEREFERENCE_TRIGGER" }A crafted payload that triggers the NULL pointer dereference is sent to the device via a BLE connection. This forces the device to reboot, potentially compromising the system and leading to data leakage.
Mitigation Guidance
Users are advised to apply the vendor patch as soon as it is available to mitigate the risk associated with this vulnerability. In the meantime, using a Web Application Firewall (WAF) or Intrusion Detection System (IDS) can provide temporary mitigation. By monitoring network traffic for suspicious BLE messages, these systems can potentially prevent the exploitation of this vulnerability. However, these are merely temporary solutions and cannot replace the necessity of a proper patch from the vendor.