{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-25524 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-25524 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-25524 is a medium-severity vulnerability in Samsung Mobile Contacts, published on 8 Dec 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-25524 and fix it if it is affected.\n\nWhat it is: CVE-2021-25524 is a medium-severity vulnerability in Samsung Mobile Contacts, published on 8 Dec 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-25524 in the wild and no public exploit code.\n\nAffected product: Samsung Mobile Contacts. 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-25524/ (Markdown: https://insights.sbomify.com/CVE-2021-25524/index.md)","id":"CVE-2021-25524","markdown":"https://insights.sbomify.com/CVE-2021-25524/index.md","name":"CVE-2021-25524","record":{"aliases":["GHSA-qc9v-r7rw-wvm2"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung Contacts app","requires_auth":"none","summary":"An attacker can retrieve the Samsung Account ID due to insecure storage of device information in the Contacts application.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Samsung Mobile","cpe":[{"product":"contacts","vendor":"samsung"}],"cvss":{"score":4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-922","name":"Insecure Storage of Sensitive Information"}],"description":"Insecure storage of device information in Contacts prior to version 12.7.05.24 allows attacker to get Samsung Account ID.","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":"Information disclosure in Contacts","id":"CVE-2021-25524","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in Samsung Pay","id":"CVE-2021-25525"},"packages":[],"prev":{"headline":"Information disclosure in SamsungDialer","id":"CVE-2021-25523"},"products":["Contacts"],"published":"2021-12-08","related":[],"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":"An attacker can retrieve the Samsung Account ID due to insecure storage of device information in the Contacts application.","url":"https://insights.sbomify.com/CVE-2021-25524/"}