{"answers":{"affected":"It affects 19 products.","exploited":"There is no known exploitation of CVE-2024-39890 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-39890 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-39890 is a high-severity memory corruption vulnerability in Samsung Exynos 1080 Firmware, published on 2 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-39890 and fix it if it is affected.\n\nWhat it is: CVE-2024-39890 is a high-severity memory corruption vulnerability in Samsung Exynos 1080 Firmware, published on 2 Dec 2024. 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-2024-39890 in the wild and no public exploit code.\n\nAffected product: Samsung Exynos 1080 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-39890/ (Markdown: https://insights.sbomify.com/CVE-2024-39890/index.md)","id":"CVE-2024-39890","markdown":"https://insights.sbomify.com/CVE-2024-39890/index.md","name":"CVE-2024-39890","record":{"aliases":["GHSA-2qph-2p52-g49j"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Exynos baseband firmware","requires_auth":"none","summary":"Attackers can exploit an out-of-bounds write in Exynos baseband software to execute arbitrary code or escalate privileges.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"exynos_1080_firmware","vendor":"samsung"},{"product":"exynos_1280_firmware","vendor":"samsung"},{"product":"exynos_1330_firmware","vendor":"samsung"},{"product":"exynos_1380_firmware","vendor":"samsung"},{"product":"exynos_1480_firmware","vendor":"samsung"},{"product":"exynos_2100_firmware","vendor":"samsung"},{"product":"exynos_2200_firmware","vendor":"samsung"},{"product":"exynos_2400_firmware","vendor":"samsung"},{"product":"exynos_850_firmware","vendor":"samsung"},{"product":"exynos_9110_firmware","vendor":"samsung"},{"product":"exynos_980_firmware","vendor":"samsung"},{"product":"exynos_9820_firmware","vendor":"samsung"},{"product":"exynos_9825_firmware","vendor":"samsung"},{"product":"exynos_990_firmware","vendor":"samsung"},{"product":"exynos_modem_5123_firmware","vendor":"samsung"},{"product":"exynos_modem_5300_firmware","vendor":"samsung"},{"product":"exynos_w1000_firmware","vendor":"samsung"},{"product":"exynos_w920_firmware","vendor":"samsung"},{"product":"exynos_w930_firmware","vendor":"samsung"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AC:H/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"An issue was discovered in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 9820, 9825, 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 9110, W920, W930, W1000, Modem 5123, Modem 5300. The baseband software does not properly check the length specified by the CC (Call Control). This can lead to an Out-of-Bounds write.","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":"Memory corruption in n/a","id":"CVE-2024-39890","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"samsung:exynos_1080_firmware","products":["samsung:exynos_1080_firmware","samsung:exynos_1280_firmware","samsung:exynos_1330_firmware","samsung:exynos_1380_firmware","samsung:exynos_1480_firmware","samsung:exynos_2100_firmware","samsung:exynos_2200_firmware","samsung:exynos_2400_firmware","samsung:exynos_850_firmware","samsung:exynos_980_firmware","samsung:exynos_990_firmware","samsung:exynos_modem_5300_firmware","samsung:exynos_w920_firmware","samsung:exynos_w930_firmware"],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Twilio Authy Information Disclosure","id":"CVE-2024-39891"},"packages":[],"prev":{"headline":"A vulnerability has been identified in Mendix Encryption (All versions \u003e= V10.0.0 \u003c V10.0.2).","id":"CVE-2024-39888"},"products":["n/a"],"published":"2024-12-02","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2025-54328","kev_date_added":null,"published":"2026-04-06"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2025-62818","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":9.1,"headline":"Denial of service in n/a","id":"CVE-2025-58349","kev_date_added":null,"published":"2026-04-06"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2025-27807","kev_date_added":null,"published":"2026-01-05"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2025-47202","kev_date_added":null,"published":"2025-07-07"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2025-27891","kev_date_added":null,"published":"2025-05-14"},{"cvss_score":8.8,"headline":"Use after free in n/a","id":"CVE-2025-23102","kev_date_added":null,"published":"2025-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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-12-03","vendors":["n/a"]},"summary":"Attackers can exploit an out-of-bounds write in Exynos baseband software to execute arbitrary code or escalate privileges.","url":"https://insights.sbomify.com/CVE-2024-39890/"}