CVE-2025-32878

An issue was discovered on COROS PACE 3 devices through 3.0808.0. It implements a function to connect the watch to a WLAN. This function is mainly for downloading firmware files. Before downloading firmware files, the watch requests some information about the firmware via HTTPS from the back-end API. However, the X.509 server certificate within the TLS handshake is not validated by the device. This allows an attacker within an active machine-in-the-middle position, using a TLS proxy and a self-signed certificate, to eavesdrop and manipulate the HTTPS communication. This could be abused, for example, for stealing the API access token of the assigned user account.

CVSS v3 9.8 CRITICAL

9.8^/10

CVSS v3 : CRITICAL

Vector :

Exploitability : 3.9 / Impact : 5.9

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact HIGH

Scope UNCHANGED

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-030.txt	Exploit Third Party Advisory

Configurations

Configuration 1 (hide)

AND

cpe:2.3:o:yftech:coros_pace_3_firmware:*:*:*:*:*:*:*:*

cpe:2.3:h:yftech:coros_pace_3:-:*:*:*:*:*:*:*

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-32878

Mitre link : CVE-2025-32878

CVE.ORG link : CVE-2025-32878

JSON object : View

Products Affected

yftech

coros_pace_3
coros_pace_3_firmware

CWE

CWE-295

Improper Certificate Validation

{"id": "CVE-2025-32878", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 9.8, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 3.9}]}, "published": "2025-06-20T14:15:28.490", "references": [{"url": "https://support.coros.com/hc/en-us/articles/20087694119828-COROS-PACE-3-Release-Notes", "tags": ["Release Notes"], "source": "cve@mitre.org"}, {"url": "https://syss.de", "tags": ["Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2025-030.txt", "tags": ["Exploit", "Third Party Advisory"], "source": "cve@mitre.org"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "description": [{"lang": "en", "value": "CWE-295"}]}], "descriptions": [{"lang": "en", "value": "An issue was discovered on COROS PACE 3 devices through 3.0808.0. It implements a function to connect the watch to a WLAN. This function is mainly for downloading firmware files. Before downloading firmware files, the watch requests some information about the firmware via HTTPS from the back-end API. However, the X.509 server certificate within the TLS handshake is not validated by the device. This allows an attacker within an active machine-in-the-middle position, using a TLS proxy and a self-signed certificate, to eavesdrop and manipulate the HTTPS communication. This could be abused, for example, for stealing the API access token of the assigned user account."}, {"lang": "es", "value": "Se detect\u00f3 un problema en dispositivos COROS PACE 3 a trav\u00e9s de la versi\u00f3n 3.0808.0. Este problema implementa una funci\u00f3n para conectar el reloj a una red WLAN. Esta funci\u00f3n se utiliza principalmente para descargar archivos de firmware. Antes de descargarlos, el reloj solicita informaci\u00f3n sobre el firmware mediante HTTPS desde la API de backend. Sin embargo, el certificado del servidor X.509 del protocolo de enlace TLS no es validado por el dispositivo. Esto permite a un atacante en una posici\u00f3n de intermediario (MCI) activa, utilizando un proxy TLS y un certificado autofirmado, interceptar y manipular la comunicaci\u00f3n HTTPS. Esto podr\u00eda utilizarse, por ejemplo, para robar el token de acceso a la API de la cuenta de usuario asignada."}], "lastModified": "2025-07-08T14:32:47.210", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:o:yftech:coros_pace_3_firmware:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "76182C50-BA03-4620-A65E-532178F36676", "versionEndIncluding": "3.0808.0"}], "operator": "OR"}, {"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:h:yftech:coros_pace_3:-:*:*:*:*:*:*:*", "vulnerable": false, "matchCriteriaId": "B4556211-076C-4EC0-A94E-5AB5C2D86DBB"}], "operator": "OR"}], "operator": "AND"}], "sourceIdentifier": "cve@mitre.org"}