{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-24819 exists.","fix":"No fix has been published for CVE-2023-24819 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-24819 is a critical memory corruption vulnerability in RIOT-OS RIOT, published on 24 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-24819 and fix it if it is affected.\n\nWhat it is: CVE-2023-24819 is a critical memory corruption vulnerability in RIOT-OS RIOT, published on 24 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-24819 exists.\n\nAffected product: RIOT-OS RIOT. 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-24819/ (Markdown: https://insights.sbomify.com/CVE-2023-24819/index.md)","id":"CVE-2023-24819","markdown":"https://insights.sbomify.com/CVE-2023-24819/index.md","name":"CVE-2023-24819","record":{"aliases":["GHSA-fv97-2448-gcf6"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"IoT operating system","requires_auth":"none","summary":"An attacker can send crafted 6LoWPAN frames to RIOT-OS devices to trigger a buffer overflow, potentially leading to arbitrary code execution or denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"riot","vendor":"riot-os"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-131","name":"Incorrect Calculation of Buffer Size"}],"description":"RIOT-OS, an operating system that supports Internet of Things devices, contains a network stack with the ability to process 6LoWPAN frames. Prior to version 2022.10, an attacker can send a crafted frame to the device resulting in an out of bounds write in the packet buffer. The overflow can be used to corrupt other packets and the allocator metadata. Corrupting a pointer will easily lead to denial of service. While carefully manipulating the allocator metadata gives an attacker the possibility to write data to arbitrary locations and thus execute arbitrary code. Version 2022.10 fixes this issue. As a workaround, disable support for fragmented IP datagrams or apply the patches manually.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"RIOT-OS vulnerable to Buffer Overflow during IPHC receive","id":"CVE-2023-24819","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"RIOT-OS vulnerable to Integer Underflow during IPHC receive","id":"CVE-2023-24820"},"packages":[],"prev":{"headline":"RIOT-OS vulnerable to null pointer dereference during fragment forwarding","id":"CVE-2023-24818"},"products":["RIOT"],"published":"2023-04-24","related":[{"cvss_score":9.8,"headline":"Buffer overflows in RIOT","id":"CVE-2024-32017","kev_date_added":null,"published":"2024-05-01"},{"cvss_score":9.8,"headline":"RIOT-OS vulnerable to Out of Bounds Write in _rbuf_add","id":"CVE-2023-33975","kev_date_added":null,"published":"2023-05-30"},{"cvss_score":9.8,"headline":"RIOT-OS vulnerable to Packet Type Confusion during IPHC send","id":"CVE-2023-24823","kev_date_added":null,"published":"2023-04-24"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-27357","kev_date_added":null,"published":"2021-04-06"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-27697","kev_date_added":null,"published":"2021-04-06"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-27698","kev_date_added":null,"published":"2021-04-06"}],"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-04","vendors":["RIOT-OS"]},"summary":"An attacker can send crafted 6LoWPAN frames to RIOT-OS devices to trigger a buffer overflow, potentially leading to arbitrary code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2023-24819/"}