{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-20956 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-20956 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-20956 is a medium-severity missing authorization vulnerability in Samsung Mobile Devices, published on 7 May 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-20956 and fix it if it is affected.\n\nWhat it is: CVE-2025-20956 is a medium-severity missing authorization vulnerability in Samsung Mobile Devices, published on 7 May 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-20956 in the wild and no public exploit code.\n\nAffected product: Samsung Mobile Devices. 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-20956/ (Markdown: https://insights.sbomify.com/CVE-2025-20956/index.md)","id":"CVE-2025-20956","markdown":"https://insights.sbomify.com/CVE-2025-20956/index.md","name":"CVE-2025-20956","record":{"aliases":["GHSA-72gp-564x-qvpp"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung Galaxy Watch","requires_auth":"none","summary":"Physical attackers can access developer settings on Samsung Galaxy Watch devices due to improper component export in Settings.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SamsungMobile","cpe":[{"product":"wear_os","vendor":"samsung"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[],"description":"Improper export of android application components in Settings in Galaxy Watch prior to SMR May-2025 Release 1 allows physical attackers to access developer settings.","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 Mobile Devices","id":"CVE-2025-20956","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":"Missing authorization in Samsung Mobile Devices","id":"CVE-2025-20957"},"packages":[],"prev":{"headline":"Information disclosure in Samsung Mobile Devices","id":"CVE-2025-20955"},"products":["Samsung Mobile Devices"],"published":"2025-05-07","related":[{"cvss_score":8.8,"headline":"Security feature bypass in Samsung Mobile Devices","id":"CVE-2025-20946","kev_date_added":null,"published":"2025-04-08"},{"cvss_score":6.8,"headline":"Missing authorization in Samsung Mobile Devices","id":"CVE-2025-20984","kev_date_added":null,"published":"2025-06-04"},{"cvss_score":6.2,"headline":"Misconfiguration in Samsung Mobile Devices","id":"CVE-2025-20997","kev_date_added":null,"published":"2025-07-08"},{"cvss_score":6.2,"headline":"Missing authorization in Samsung Mobile Devices","id":"CVE-2025-21004","kev_date_added":null,"published":"2025-07-08"},{"cvss_score":6.2,"headline":"Missing authorization in Samsung Mobile Devices","id":"CVE-2025-20910","kev_date_added":null,"published":"2025-03-06"},{"cvss_score":6.2,"headline":"Information disclosure in Samsung Mobile Devices","id":"CVE-2025-20912","kev_date_added":null,"published":"2025-03-06"},{"cvss_score":5.5,"headline":"Information disclosure in Samsung Mobile Devices","id":"CVE-2025-20998","kev_date_added":null,"published":"2025-07-08"}],"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-05-07","vendors":["Samsung Mobile"]},"summary":"Physical attackers can access developer settings on Samsung Galaxy Watch devices due to improper component export in Settings.","url":"https://insights.sbomify.com/CVE-2025-20956/"}