API token theft via unvalidated TLS certificate
Published Jun 20, 2025 · Updated Jun 20, 2025
Improper certificate validation in COROS PACE 3 firmware 3.1008.0 and earlier allows attackers to steal API tokens through intercepted WLAN traffic. The firmware-metadata request accepts a self-signed X.509 server certificate during the TLS handshake, exposing the access token and request body to a TLS proxy. An unauthenticated attacker must control the watch's WLAN traffic during an update check; that position permits reading or altering the assigned account's HTTPS exchange.
Summary
What happened
Improper certificate validation in COROS PACE 3 firmware 3.1008.0 and earlier allows attackers to steal API tokens through intercepted WLAN traffic. The firmware-metadata request accepts a self-signed X.509 server certificate during the TLS handshake, exposing the access token and request body to a TLS proxy. An unauthenticated attacker must control the watch's WLAN traffic during an update check; that position permits reading or altering the assigned account's HTTPS exchange.
The record
- CVE
- CVE-2025-32878
- Published
- Jun 20, 2025
- Updated
- Jun 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 20, 2025CVE publishedPublication date reported by the CVE source.
- Jun 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- TLS proxy interception proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo