{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32878 exists.","fix":"No fix has been published for CVE-2025-32878 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-32878 is a critical vulnerability in n/a, published on 20 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-32878 and fix it if it is affected.\n\nWhat it is: CVE-2025-32878 is a critical vulnerability in n/a, published on 20 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32878 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-32878/ (Markdown: https://insights.sbomify.com/CVE-2025-32878/index.md)","id":"CVE-2025-32878","markdown":"https://insights.sbomify.com/CVE-2025-32878/index.md","name":"CVE-2025-32878","record":{"aliases":["GHSA-8hrq-vv4f-qvxr"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"COROS PACE 3 watch","requires_auth":"none","summary":"Attackers can intercept HTTPS traffic to steal API tokens due to missing TLS certificate validation on COROS PACE 3 watches.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"coros_pace_3_firmware","vendor":"yftech"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2025-32878","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in n/a","id":"CVE-2025-32879"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2025-32877"},"products":["n/a"],"published":"2025-06-20","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2025-32877","kev_date_added":null,"published":"2025-06-20"},{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2025-32880","kev_date_added":null,"published":"2025-06-20"},{"cvss_score":9.1,"headline":"Denial of service in n/a","id":"CVE-2025-48706","kev_date_added":null,"published":"2025-06-20"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2025-32879","kev_date_added":null,"published":"2025-06-20"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2025-48705","kev_date_added":null,"published":"2025-06-20"},{"cvss_score":6.8,"headline":"Weak cryptography in n/a","id":"CVE-2025-32876","kev_date_added":null,"published":"2025-06-20"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-06-20","vendors":["n/a"]},"summary":"Attackers can intercept HTTPS traffic to steal API tokens due to missing TLS certificate validation on COROS PACE 3 watches.","url":"https://insights.sbomify.com/CVE-2025-32878/"}