{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-39888 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-39888 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-39888 is a medium-severity vulnerability in Samsung Mobile Devices, published on 4 Sep 2025. 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-39888 and fix it if it is affected.\n\nWhat it is: CVE-2022-39888 is a medium-severity vulnerability in Samsung Mobile Devices, published on 4 Sep 2025. 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-39888 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-2022-39888/ (Markdown: https://insights.sbomify.com/CVE-2022-39888/index.md)","id":"CVE-2022-39888","markdown":"https://insights.sbomify.com/CVE-2022-39888/index.md","name":"CVE-2022-39888","record":{"aliases":["GHSA-6prq-7mwm-7mpr"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung mobile OS","requires_auth":"none","summary":"A local attacker can access Proxy information due to improper access control in the MiscPolicy component of Samsung mobile devices.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SamsungMobile","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N","version":"3.1"},"cwes":[],"description":"Improper access control vulnerability in retrieveExternalProxy in MiscPolicy prior to SMR Nov-2022 Release 1 allows local attacker to access to Proxy information.","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 Samsung Mobile Devices","id":"CVE-2022-39888","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 GalaxyWatch4Plugin","id":"CVE-2022-39889"},"packages":[],"prev":{"headline":"Missing authorization in Samsung Mobile Devices","id":"CVE-2022-39887"},"products":["Samsung Mobile Devices"],"published":"2025-09-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-04","vendors":["Samsung Mobile"]},"summary":"A local attacker can access Proxy information due to improper access control in the MiscPolicy component of Samsung mobile devices.","url":"https://insights.sbomify.com/CVE-2022-39888/"}