{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-42581 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-42581 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-42581 is a high-severity cross-site scripting vulnerability in Samsung Mobile Galaxy Store, published on 5 Dec 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-42581 and fix it if it is affected.\n\nWhat it is: CVE-2023-42581 is a high-severity cross-site scripting vulnerability in Samsung Mobile Galaxy Store, published on 5 Dec 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-42581 in the wild and no public exploit code.\n\nAffected product: Samsung Mobile Galaxy Store. 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-2023-42581/ (Markdown: https://insights.sbomify.com/CVE-2023-42581/index.md)","id":"CVE-2023-42581","markdown":"https://insights.sbomify.com/CVE-2023-42581/index.md","name":"CVE-2023-42581","record":{"aliases":["GHSA-95m4-cmvc-pjh9"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Samsung Galaxy Store","requires_auth":"none","summary":"Attackers can execute JavaScript via improper URL validation in Galaxy Store deeplinks to access sensitive data.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SamsungMobile","cpe":[{"product":"galaxy_store","vendor":"samsung"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"Improper URL validation from InstantPlay deeplink in Galaxy Store prior to version 4.5.64.4 allows attackers to execute JavaScript API to access data.","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":"Cross-site scripting in Galaxy Store","id":"CVE-2023-42581","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Liferay Portal and Liferay DXP Vulnerable to XSS in the Commerce Module","id":"CVE-2023-42627"},"packages":[],"prev":{"headline":"Code injection in Galaxy Store","id":"CVE-2023-42580"},"products":["Galaxy Store"],"published":"2023-12-05","related":[{"cvss_score":7.8,"headline":"Missing authorization in Galaxy Store","id":"CVE-2023-21433","kev_date_added":null,"published":"2023-02-09"},{"cvss_score":7.8,"headline":"Privilege escalation in Galaxy Store","id":"CVE-2022-33708","kev_date_added":null,"published":"2022-07-11"},{"cvss_score":7.8,"headline":"Improper input validation vulnerability in ApexPackageInstaller in Galaxy Store prior to version 4.5.41.8 allows local attackers to launch a","id":"CVE-2022-33709","kev_date_added":null,"published":"2022-07-11"},{"cvss_score":7.8,"headline":"Privilege escalation in Galaxy Store","id":"CVE-2022-33710","kev_date_added":null,"published":"2022-07-11"},{"cvss_score":7.5,"headline":"Code injection in Galaxy Store","id":"CVE-2023-42580","kev_date_added":null,"published":"2023-12-05"},{"cvss_score":7.5,"headline":"Code injection in Galaxy Store","id":"CVE-2023-21514","kev_date_added":null,"published":"2023-05-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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-28","vendors":["Samsung Mobile"]},"summary":"Attackers can execute JavaScript via improper URL validation in Galaxy Store deeplinks to access sensitive data.","url":"https://insights.sbomify.com/CVE-2023-42581/"}