{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-6742 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-6742 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-6742 is a critical code injection vulnerability in Samsung Galaxy S9, published on 3 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-6742 and fix it if it is affected.\n\nWhat it is: CVE-2019-6742 is a critical code injection vulnerability in Samsung Galaxy S9, published on 3 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-6742 in the wild and no public exploit code.\n\nAffected product: Samsung Galaxy S9. 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-2019-6742/ (Markdown: https://insights.sbomify.com/CVE-2019-6742/index.md)","id":"CVE-2019-6742","markdown":"https://insights.sbomify.com/CVE-2019-6742/index.md","name":"CVE-2019-6742","record":{"aliases":["GHSA-q778-9mxh-6vxg"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Samsung Galaxy S9","requires_auth":"none","summary":"Remote attackers can execute arbitrary code on Samsung Galaxy S9 devices via the GameServiceReceiver update mechanism without authentication.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"zdi","cpe":[{"product":"galaxy_s9_firmware","vendor":"samsung"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-358","name":"Improperly Implemented Security Check for Standard"}],"description":"This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Samsung Galaxy S9 prior to 1.4.20.2. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of the GameServiceReceiver update mechanism. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-7477.","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":"Code injection in Galaxy S9","id":"CVE-2019-6742","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Browser","id":"CVE-2019-6743"},"packages":[],"prev":{"headline":"Open redirect in Galaxy S9","id":"CVE-2019-6741"},"products":["Galaxy S9"],"published":"2019-06-03","related":[{"cvss_score":9.6,"headline":"Memory corruption in Galaxy S9","id":"CVE-2019-6740","kev_date_added":null,"published":"2019-06-03"},{"cvss_score":6.5,"headline":"Open redirect in Galaxy S9","id":"CVE-2019-6741","kev_date_added":null,"published":"2019-06-03"}],"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-04","vendors":["Samsung"]},"summary":"Remote attackers can execute arbitrary code on Samsung Galaxy S9 devices via the GameServiceReceiver update mechanism without authentication.","url":"https://insights.sbomify.com/CVE-2019-6742/"}