{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-30742 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-30742 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-30742 is a low-severity vulnerability in Samsung Mobile Find My Mobile, published on 7 Jun 2022. 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-2022-30742 and fix it if it is affected.\n\nWhat it is: CVE-2022-30742 is a low-severity vulnerability in Samsung Mobile Find My Mobile, published on 7 Jun 2022. 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-2022-30742 in the wild and no public exploit code.\n\nAffected product: Samsung Mobile Find My Mobile. 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-30742/ (Markdown: https://insights.sbomify.com/CVE-2022-30742/index.md)","id":"CVE-2022-30742","markdown":"https://insights.sbomify.com/CVE-2022-30742/index.md","name":"CVE-2022-30742","record":{"aliases":["GHSA-75g9-xg49-wc86"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung Find My Mobile","requires_auth":"low_privilege","summary":"Local attackers with log access can extract SIM card information from Samsung Find My Mobile application logs.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Samsung Mobile","cpe":[{"product":"find_my_mobile","vendor":"samsung"}],"cvss":{"score":3.3,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Sensitive information exposure vulnerability in FmmExtraOperation of Find My Mobile prior to 7.2.24.12 allows local attackers with log access permissio to get sim card information through device log.","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 Find My Mobile","id":"CVE-2022-30742","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in Samsung Account","id":"CVE-2022-30743"},"packages":[],"prev":{"headline":"Information disclosure in Find My Mobile","id":"CVE-2022-30741"},"products":["Find My Mobile"],"published":"2022-06-07","related":[{"cvss_score":7.6,"headline":"Auth bypass in Find My Mobile","id":"CVE-2023-42571","kev_date_added":null,"published":"2023-12-05"},{"cvss_score":5.3,"headline":"Information disclosure in FindMyMobile","id":"CVE-2022-33707","kev_date_added":null,"published":"2022-07-11"},{"cvss_score":3.3,"headline":"Information disclosure in Find My Mobile","id":"CVE-2022-36878","kev_date_added":null,"published":"2022-09-09"},{"cvss_score":3.3,"headline":"Information disclosure in Find My Mobile","id":"CVE-2022-30741","kev_date_added":null,"published":"2022-06-07"}],"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":"Local attackers with log access can extract SIM card information from Samsung Find My Mobile application logs.","url":"https://insights.sbomify.com/CVE-2022-30742/"}