{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-20856 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-20856 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-20856 is a medium-severity authentication bypass vulnerability in Samsung Android, published on 7 May 2024. 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-2024-20856 and fix it if it is affected.\n\nWhat it is: CVE-2024-20856 is a medium-severity authentication bypass vulnerability in Samsung Android, published on 7 May 2024. 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-2024-20856 in the wild and no public exploit code.\n\nAffected product: Samsung Android. 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-2024-20856/ (Markdown: https://insights.sbomify.com/CVE-2024-20856/index.md)","id":"CVE-2024-20856","markdown":"https://insights.sbomify.com/CVE-2024-20856/index.md","name":"CVE-2024-20856","record":{"aliases":["GHSA-x67c-fh4p-7v8m"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung Secure Folder","requires_auth":"none","summary":"Physical attackers can bypass authentication to access Secure Folder data on Samsung mobile devices.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SamsungMobile","cpe":[{"product":"android","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:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Improper Authentication vulnerability in Secure Folder prior to SMR May-2024 Release 1 allows physical attackers to access Secure Folder without proper authentication in a specific scenario.","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":"Auth bypass in Samsung Mobile Devices","id":"CVE-2024-20856","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"samsung:android","products":["samsung:android"],"type":"auth_bypass","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in Samsung Mobile Devices","id":"CVE-2024-20857"},"packages":[],"prev":{"headline":"Auth bypass in Samsung Mobile Devices","id":"CVE-2024-20855"},"products":["Samsung Mobile Devices"],"published":"2024-05-07","related":[{"cvss_score":8.8,"headline":"Samsung Mobile Devices Out-of-Bounds Write","id":"CVE-2025-21042","kev_date_added":"2025-11-10","published":"2025-09-12"},{"cvss_score":8.8,"headline":"Samsung Mobile Devices Out-of-Bounds Write","id":"CVE-2025-21043","kev_date_added":"2025-10-02","published":"2025-09-12"},{"cvss_score":7.3,"headline":"Samsung Mobile Devices Out-of-Bounds Read","id":"CVE-2021-25487","kev_date_added":"2023-06-29","published":"2021-10-06"},{"cvss_score":6.4,"headline":"Samsung Mobile Devices Race Condition","id":"CVE-2021-25394","kev_date_added":"2023-06-29","published":"2021-06-11"},{"cvss_score":6.4,"headline":"Samsung Mobile Devices Race Condition","id":"CVE-2021-25395","kev_date_added":"2023-06-29","published":"2021-06-11"},{"cvss_score":6.2,"headline":"Samsung Mobile Devices Improper Access Control","id":"CVE-2021-25369","kev_date_added":"2022-11-08","published":"2021-03-26"},{"cvss_score":6.1,"headline":"Samsung Mobile Devices Memory Corruption","id":"CVE-2021-25370","kev_date_added":"2022-11-08","published":"2021-03-26"}],"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":"partial"},"state":"PUBLISHED","updated":"2024-08-01","vendors":["Samsung Mobile"]},"summary":"Physical attackers can bypass authentication to access Secure Folder data on Samsung mobile devices.","url":"https://insights.sbomify.com/CVE-2024-20856/"}