{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-21019 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-21019 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-21019 is a medium-severity missing authorization vulnerability in Samsung Health, published on 6 Aug 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-21019 and fix it if it is affected.\n\nWhat it is: CVE-2025-21019 is a medium-severity missing authorization vulnerability in Samsung Health, published on 6 Aug 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-21019 in the wild and no public exploit code.\n\nAffected product: Samsung Health. 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-21019/ (Markdown: https://insights.sbomify.com/CVE-2025-21019/index.md)","id":"CVE-2025-21019","markdown":"https://insights.sbomify.com/CVE-2025-21019/index.md","name":"CVE-2025-21019","record":{"aliases":["GHSA-63vc-r2j3-hjgj"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung Health app","requires_auth":"none","summary":"Local attackers can access Samsung Health data due to improper authorization, requiring user interaction to trigger.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SamsungMobile","cpe":[{"product":"health","vendor":"samsung"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"Improper authorization in Samsung Health prior to version 6.30.1.003 allows local attackers to access data in Samsung Health. 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":"Missing authorization in Samsung Health","id":"CVE-2025-21019","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Blockchain Keystore","id":"CVE-2025-21020"},"packages":[],"prev":{"headline":"Information disclosure in Blockchain Keystore","id":"CVE-2025-21018"},"products":["Samsung Health"],"published":"2025-08-06","related":[{"cvss_score":7.8,"headline":"Other in Samsung Health","id":"CVE-2021-25401","kev_date_added":null,"published":"2021-06-11"},{"cvss_score":6.9,"headline":"Missing authorization in Samsung Health","id":"CVE-2026-21076","kev_date_added":null,"published":"2026-08-10"},{"cvss_score":6.9,"headline":"Missing authorization in Samsung Health","id":"CVE-2026-21077","kev_date_added":null,"published":"2026-08-10"},{"cvss_score":6.9,"headline":"Path traversal in Samsung Health","id":"CVE-2026-21082","kev_date_added":null,"published":"2026-08-10"},{"cvss_score":6.2,"headline":"Missing authorization in Samsung Health","id":"CVE-2025-21059","kev_date_added":null,"published":"2025-10-10"},{"cvss_score":5.5,"headline":"Path traversal in Samsung Health","id":"CVE-2023-30723","kev_date_added":null,"published":"2023-09-06"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-06","vendors":["Samsung Mobile"]},"summary":"Local attackers can access Samsung Health data due to improper authorization, requiring user interaction to trigger.","url":"https://insights.sbomify.com/CVE-2025-21019/"}