{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-49419 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-49419 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-49419 is a medium-severity vulnerability in Samsung Mobile GamingHub, published on 3 Dec 2024. 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-2024-49419 and fix it if it is affected.\n\nWhat it is: CVE-2024-49419 is a medium-severity vulnerability in Samsung Mobile GamingHub, published on 3 Dec 2024. 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-2024-49419 in the wild and no public exploit code.\n\nAffected product: Samsung Mobile GamingHub. 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-49419/ (Markdown: https://insights.sbomify.com/CVE-2024-49419/index.md)","id":"CVE-2024-49419","markdown":"https://insights.sbomify.com/CVE-2024-49419/index.md","name":"CVE-2024-49419","record":{"aliases":["GHSA-58c5-c843-5528"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Samsung GamingHub","requires_auth":"none","summary":"Remote attackers can load arbitrary URLs in the GamingHub webview due to insufficient URL verification, potentially bypassing security controls.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SamsungMobile","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[],"description":"Insufficient verification of url authenticity in GamingHub prior to version 6.1.03.4 in Korea, 7.1.02.4 in Global allows remote attackers to load an arbitrary URL in its webview.","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":"Open redirect in GamingHub","id":"CVE-2024-49419","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"open_redirect","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Other in GamingHub","id":"CVE-2024-49420"},"packages":[],"prev":{"headline":"Cross-site scripting in GamingHub","id":"CVE-2024-49418"},"products":["GamingHub"],"published":"2024-12-03","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":"2024-12-03","vendors":["Samsung Mobile"]},"summary":"Remote attackers can load arbitrary URLs in the GamingHub webview due to insufficient URL verification, potentially bypassing security controls.","url":"https://insights.sbomify.com/CVE-2024-49419/"}