{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2023-28613 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-28613 is a medium-severity vulnerability in Samsung Exynos 1280 Firmware, published on 4 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-28613 and fix it if it is affected.\n\nWhat it is: CVE-2023-28613 is a medium-severity vulnerability in Samsung Exynos 1280 Firmware, published on 4 Apr 2023. 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-2023-28613 in the wild and no public exploit code.\n\nAffected product: Samsung Exynos 1280 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-28613/ (Markdown: https://insights.sbomify.com/CVE-2023-28613/index.md)","id":"CVE-2023-28613","markdown":"https://insights.sbomify.com/CVE-2023-28613/index.md","name":"CVE-2023-28613","record":{"aliases":["A-269655868","GHSA-v2w5-mxw3-ccwc","PUB-A-269655868"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Exynos mobile processor","requires_auth":"none","summary":"Integer overflow in IPv4 fragment handling allows attackers to cause denial of service or execute code on affected Exynos processors.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"exynos_1280_firmware","vendor":"samsung"},{"product":"exynos_2200_firmware","vendor":"samsung"},{"product":"exynos_modem_5300_firmware","vendor":"samsung"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AC:H/AV:N/A:H/C:N/I:N/PR:N/S:C/UI:N","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"An issue was discovered in Samsung Exynos Mobile Processor and Baseband Modem Processor for Exynos 1280, Exynos 2200, and Exynos Modem 5300. An integer overflow in IPv4 fragment handling can occur due to insufficient parameter validation when reassembling these fragments.","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":"Integer overflow in n/a","id":"CVE-2023-28613","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"samsung:exynos_1280_firmware","products":["samsung:exynos_1280_firmware","samsung:exynos_2200_firmware","samsung:exynos_modem_5300_firmware"],"type":"integer_overflow","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"Command injection in n/a","id":"CVE-2023-28614"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2023-28611"},"products":["n/a"],"published":"2023-04-04","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2025-52908","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2025-52909","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2025-52910","kev_date_added":null,"published":"2025-11-04"},{"cvss_score":7.6,"headline":"Memory corruption in n/a","id":"CVE-2023-26076","kev_date_added":null,"published":"2023-03-13"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2025-62814","kev_date_added":null,"published":"2026-03-03"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2025-62817","kev_date_added":null,"published":"2026-03-03"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2025-54326","kev_date_added":null,"published":"2025-12-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":"2025-02-13","vendors":["n/a"]},"summary":"Integer overflow in IPv4 fragment handling allows attackers to cause denial of service or execute code on affected Exynos processors.","url":"https://insights.sbomify.com/CVE-2023-28613/"}