References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [email protected].

Known Affected Software Configurations Switch to CPE 2.2

Change History

OR
     OR
          *cpe:2.3:o:yftech:coros_pace_3_firmware:*:*:*:*:*:*:*:* versions up to (including) 3.0808.0
     OR
          cpe:2.3:h:yftech:coros_pace_3:-:*:*:*:*:*:*:*

MITRE: https://support.coros.com/hc/en-us/articles/20087694119828-COROS-PACE-3-Release-Notes Types: Release Notes

MITRE: https://syss.de Types: Third Party Advisory

MITRE: https://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2025-030.txt Types: Exploit, Third Party Advisory

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE-295

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

https://support.coros.com/hc/en-us/articles/20087694119828-COROS-PACE-3-Release-Notes

https://syss.de

https://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2025-030.txt