{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-25506 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-25506 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-25506 is a medium-severity missing authorization vulnerability in Samsung Health, published on 5 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-25506 and fix it if it is affected.\n\nWhat it is: CVE-2021-25506 is a medium-severity missing authorization vulnerability in Samsung Health, published on 5 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-25506 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-2021-25506/ (Markdown: https://insights.sbomify.com/CVE-2021-25506/index.md)","id":"CVE-2021-25506","markdown":"https://insights.sbomify.com/CVE-2021-25506/index.md","name":"CVE-2021-25506","record":{"aliases":["GHSA-cmpr-j6rp-9r78"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung Health app","requires_auth":"none","summary":"Attackers can access non-existent providers in Samsung Health to read data or cause denial of service via malicious content providers.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Samsung Mobile","cpe":[{"product":"health","vendor":"samsung"}],"cvss":{"score":4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"Non-existent provider in Samsung Health prior to 6.19.1.0001 allows attacker to access it via malicious content provider or lead to denial of service.","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-2021-25506","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in Samsung Flow","id":"CVE-2021-25507"},"packages":[],"prev":{"headline":"Auth bypass in Samsung Pass","id":"CVE-2021-25505"},"products":["Samsung Health"],"published":"2021-11-05","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":"Missing authorization in Samsung Health","id":"CVE-2025-21019","kev_date_added":null,"published":"2025-08-06"},{"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Samsung Mobile"]},"summary":"Attackers can access non-existent providers in Samsung Health to read data or cause denial of service via malicious content providers.","url":"https://insights.sbomify.com/CVE-2021-25506/"}