{"answers":{"affected":"It affects 16 products.","exploited":"There is no known exploitation of CVE-2023-41111 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-41111 is a high-severity memory corruption vulnerability in Samsung Exynos 1080 Firmware, published on 8 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-41111 and fix it if it is affected.\n\nWhat it is: CVE-2023-41111 is a high-severity memory corruption vulnerability in Samsung Exynos 1080 Firmware, published on 8 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-41111 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-2023-41111/ (Markdown: https://insights.sbomify.com/CVE-2023-41111/index.md)","id":"CVE-2023-41111","markdown":"https://insights.sbomify.com/CVE-2023-41111/index.md","name":"CVE-2023-41111","record":{"aliases":["A-292004859","GHSA-44j5-cggq-4pgj","PUB-A-292004859"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Samsung Exynos processor","requires_auth":"low_privilege","summary":"Attackers can cause abnormal termination of mobile devices via improper handling of length parameters in the RLC module of Samsung Exynos processors.","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_2100_firmware","vendor":"samsung"},{"product":"exynos_2200_firmware","vendor":"samsung"},{"product":"exynos_850_firmware","vendor":"samsung"},{"product":"exynos_9110_firmware","vendor":"samsung"},{"product":"exynos_9610_firmware","vendor":"samsung"},{"product":"exynos_980_firmware","vendor":"samsung"},{"product":"exynos_9810_firmware","vendor":"samsung"},{"product":"exynos_9820_firmware","vendor":"samsung"},{"product":"exynos_auto_t5123_firmware","vendor":"samsung"},{"product":"exynos_modem_5123_firmware","vendor":"samsung"},{"product":"exynos_modem_5300_firmware","vendor":"samsung"},{"product":"exynos_w920_firmware","vendor":"samsung"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AC:L/AV:N/A:H/C:N/I:L/PR:L/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, Automotive Processor, and Modem (Exynos 9810, 9610, 9820, 980, 850, 1080, 2100, 2200, 1280, 1380, 1330, 9110, W920, Modem 5123, Modem 5300, and Auto T5123). Improper handling of a length parameter inconsistency can cause abnormal termination of a mobile phone. This occurs in the RLC task and RLC module.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Memory corruption in n/a","id":"CVE-2023-41111","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_2100_firmware","samsung:exynos_2200_firmware","samsung:exynos_850_firmware","samsung:exynos_980_firmware","samsung:exynos_modem_5300_firmware","samsung:exynos_w920_firmware"],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2023-41112"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2023-41109"},"products":["n/a"],"published":"2023-11-08","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":"partial"},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Attackers can cause abnormal termination of mobile devices via improper handling of length parameters in the RLC module of Samsung Exynos processors.","url":"https://insights.sbomify.com/CVE-2023-41111/"}