{
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:o:yftech:coros_pace_3_firmware:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "76182C50-BA03-4620-A65E-532178F36676",
              "versionEndIncluding": "3.0808.0",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        },
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:h:yftech:coros_pace_3:-:*:*:*:*:*:*:*",
              "matchCriteriaId": "B4556211-076C-4EC0-A94E-5AB5C2D86DBB",
              "vulnerable": false
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ],
      "operator": "AND"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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."
    },
    {
      "lang": "es",
      "value": "Se detect\u00f3 un problema en los dispositivos COROS PACE 3 hasta la versi\u00f3n 3.0808.0. La implementaci\u00f3n BLE del reloj inteligente COROS no es compatible con las conexiones seguras LE y, en su lugar, aplica el emparejamiento heredado BLE. En el emparejamiento heredado BLE, la clave de corto plazo (STK) se puede adivinar f\u00e1cilmente. Esto requiere conocer la clave temporal (TK), que, en el caso del COROS Pace 3, est\u00e1 configurada a 0 debido al m\u00e9todo de emparejamiento Just Works. Por lo tanto, un atacante dentro del alcance de Bluetooth puede realizar ataques de rastreo, lo que permite interceptar la comunicaci\u00f3n."
    }
  ],
  "id": "CVE-2025-32876",
  "lastModified": "2025-07-08T14:32:59.510",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "ADJACENT_NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 6.8,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 1.6,
        "impactScore": 5.2,
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "type": "Secondary"
      }
    ]
  },
  "published": "2025-06-20T14:15:27.877",
  "references": [
    {
      "source": "cve@mitre.org",
      "tags": [
        "Release Notes"
      ],
      "url": "https://support.coros.com/hc/en-us/articles/20087694119828-COROS-PACE-3-Release-Notes"
    },
    {
      "source": "cve@mitre.org",
      "tags": [
        "Third Party Advisory"
      ],
      "url": "https://syss.de"
    },
    {
      "source": "cve@mitre.org",
      "tags": [
        "Exploit",
        "Third Party Advisory"
      ],
      "url": "https://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2025-023.txt"
    },
    {
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
      "tags": [
        "Exploit",
        "Third Party Advisory"
      ],
      "url": "https://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2025-023.txt"
    }
  ],
  "sourceIdentifier": "cve@mitre.org",
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-306"
        }
      ],
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
      "type": "Secondary"
    }
  ]
}