{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-27841 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-27841 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-27841 is a medium-severity authentication bypass vulnerability in Samsung Pass, published on 11 Apr 2022. 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-2022-27841 and fix it if it is affected.\n\nWhat it is: CVE-2022-27841 is a medium-severity authentication bypass vulnerability in Samsung Pass, published on 11 Apr 2022. 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-2022-27841 in the wild and no public exploit code.\n\nAffected product: Samsung Pass. 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-2022-27841/ (Markdown: https://insights.sbomify.com/CVE-2022-27841/index.md)","id":"CVE-2022-27841","markdown":"https://insights.sbomify.com/CVE-2022-27841/index.md","name":"CVE-2022-27841","record":{"aliases":["GHSA-xxq8-w68p-wqxp"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung Pass app","requires_auth":"none","summary":"A physical attacker can bypass authentication to view previously running screens in Samsung Pass due to improper exception handling.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Samsung Mobile","cpe":[{"product":"samsung_pass","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-755","name":"Improper Handling of Exceptional Conditions"},{"id":"CWE-703","name":"Improper Check or Handling of Exceptional Conditions"}],"description":"Improper exception handling in Samsung Pass prior to version 3.7.07.5 allows physical attacker to view the screen that is previously running without authentication","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 Pass","id":"CVE-2022-27841","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Other in Smart Switch PC","id":"CVE-2022-27842"},"packages":[],"prev":{"headline":"Missing authorization in Samsung Recovery","id":"CVE-2022-27840"},"products":["Samsung Pass"],"published":"2022-04-11","related":[{"cvss_score":4.6,"headline":"Missing authorization in Samsung Pass","id":"CVE-2022-30730","kev_date_added":null,"published":"2022-06-07"},{"cvss_score":3.9,"headline":"Improper access control vulnerability in Samsung pass prior to version 4.0.03.1 allow physical attackers to access data of Samsung pass on a","id":"CVE-2022-36851","kev_date_added":null,"published":"2022-09-09"},{"cvss_score":3.3,"headline":"Auth bypass in Samsung Pass","id":"CVE-2021-25505","kev_date_added":null,"published":"2021-11-05"},{"cvss_score":1.8,"headline":"Missing authorization in Samsung Pass","id":"CVE-2022-36876","kev_date_added":null,"published":"2022-09-09"}],"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":"A physical attacker can bypass authentication to view previously running screens in Samsung Pass due to improper exception handling.","url":"https://insights.sbomify.com/CVE-2022-27841/"}