{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2024-31959 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-31959 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-31959 is a high-severity vulnerability in Samsung Exynos 1480 Firmware, published on 7 Jun 2024. 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-2024-31959 and fix it if it is affected.\n\nWhat it is: CVE-2024-31959 is a high-severity vulnerability in Samsung Exynos 1480 Firmware, published on 7 Jun 2024. 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-2024-31959 in the wild and no public exploit code.\n\nAffected product: Samsung Exynos 1480 Firmware. 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-31959/ (Markdown: https://insights.sbomify.com/CVE-2024-31959/index.md)","id":"CVE-2024-31959","markdown":"https://insights.sbomify.com/CVE-2024-31959/index.md","name":"CVE-2024-31959","record":{"aliases":["GHSA-wjrj-f22p-hwqq"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Exynos mobile processor","requires_auth":"none","summary":"Attackers can execute arbitrary code on Samsung Exynos processors due to missing validation of native handles.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"exynos_1480_firmware","vendor":"samsung"},{"product":"exynos_2200_firmware","vendor":"samsung"},{"product":"exynos_2400_firmware","vendor":"samsung"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AC:L/AV:L/A:H/C:H/I:H/PR:N/S:U/UI:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"An issue was discovered in Samsung Mobile Processor Exynos 2200, Exynos 1480, Exynos 2400. It lacks a check for the validation of native handles, which can result in code execution.","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":"Other in n/a","id":"CVE-2024-31959","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"samsung:exynos_1480_firmware","products":["samsung:exynos_1480_firmware","samsung:exynos_2200_firmware","samsung:exynos_2400_firmware"],"type":"other","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Use after free in n/a","id":"CVE-2024-31960"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2024-31958"},"products":["n/a"],"published":"2024-06-07","related":[{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2025-23099","kev_date_added":null,"published":"2025-06-02"},{"cvss_score":8.6,"headline":"Memory corruption in n/a","id":"CVE-2025-23103","kev_date_added":null,"published":"2025-06-03"},{"cvss_score":8.6,"headline":"Memory corruption in n/a","id":"CVE-2025-23107","kev_date_added":null,"published":"2025-06-03"},{"cvss_score":8.4,"headline":"Memory corruption in n/a","id":"CVE-2024-31956","kev_date_added":null,"published":"2024-06-13"},{"cvss_score":7.8,"headline":"Use after free in n/a","id":"CVE-2025-23105","kev_date_added":null,"published":"2025-06-02"},{"cvss_score":7.8,"headline":"Use after free in n/a","id":"CVE-2024-31960","kev_date_added":null,"published":"2024-09-10"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code on Samsung Exynos processors due to missing validation of native handles.","url":"https://insights.sbomify.com/CVE-2024-31959/"}