{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-21062 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-21062 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-21062 is a high-severity vulnerability in Samsung Mobile Smart Switch, published on 10 Oct 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-21062 and fix it if it is affected.\n\nWhat it is: CVE-2025-21062 is a high-severity vulnerability in Samsung Mobile Smart Switch, published on 10 Oct 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-21062 in the wild and no public exploit code.\n\nAffected product: Samsung Mobile Smart Switch. 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-21062/ (Markdown: https://insights.sbomify.com/CVE-2025-21062/index.md)","id":"CVE-2025-21062","markdown":"https://insights.sbomify.com/CVE-2025-21062/index.md","name":"CVE-2025-21062","record":{"aliases":["GHSA-44xv-7pq5-8px9"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung Smart Switch","requires_auth":"none","summary":"Local attackers can replace the restoring application via weak cryptography, requiring user interaction to execute code.","user_interaction":"required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SamsungMobile","cpe":[{"product":"smart_switch","vendor":"samsung"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"Use of a broken or risky cryptographic algorithm in Smart Switch prior to version 3.7.67.2 allows local attackers to replace the restoring application. User interaction is required for triggering this vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Weak cryptography in Smart Switch","id":"CVE-2025-21062","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in Samsung Voice Recorder","id":"CVE-2025-21063"},"packages":[],"prev":{"headline":"Information disclosure in Smart Switch","id":"CVE-2025-21061"},"products":["Smart Switch"],"published":"2025-10-10","related":[{"cvss_score":8.8,"headline":"Weak cryptography in Smart Switch","id":"CVE-2025-21078","kev_date_added":null,"published":"2025-11-05"},{"cvss_score":8.8,"headline":"Auth bypass in Smart Switch","id":"CVE-2025-21064","kev_date_added":null,"published":"2025-10-10"},{"cvss_score":7.1,"headline":"Weak cryptography in Smart Switch","id":"CVE-2026-20996","kev_date_added":null,"published":"2026-03-16"},{"cvss_score":7.1,"headline":"Auth bypass in Smart Switch","id":"CVE-2026-20998","kev_date_added":null,"published":"2026-03-16"},{"cvss_score":7.1,"headline":"Auth bypass in Smart Switch","id":"CVE-2026-20999","kev_date_added":null,"published":"2026-03-16"},{"cvss_score":7.1,"headline":"Path traversal in Smart Switch","id":"CVE-2026-21005","kev_date_added":null,"published":"2026-03-16"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["Samsung Mobile"]},"summary":"Local attackers can replace the restoring application via weak cryptography, requiring user interaction to execute code.","url":"https://insights.sbomify.com/CVE-2025-21062/"}