{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-21257 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-21257 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-21257 is a high-severity memory corruption vulnerability in contiki-ng, published on 18 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-21257 and fix it if it is affected.\n\nWhat it is: CVE-2021-21257 is a high-severity memory corruption vulnerability in contiki-ng, published on 18 Jun 2021. 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-2021-21257 in the wild and no public exploit code.\n\nAffected product: contiki-ng. 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-2021-21257/ (Markdown: https://insights.sbomify.com/CVE-2021-21257/index.md)","id":"CVE-2021-21257","markdown":"https://insights.sbomify.com/CVE-2021-21257/index.md","name":"CVE-2021-21257","record":{"aliases":[],"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":"Attackers can trigger out-of-bounds writes via crafted RPL packets in Contiki-NG, potentially leading to 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":"contiki-ng","vendor":"contiki-ng"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Contiki-NG is an open-source, cross-platform operating system for internet of things devices. The RPL-Classic and RPL-Lite implementations in the Contiki-NG operating system versions prior to 4.6 do not validate the address pointer in the RPL source routing header This makes it possible for an attacker to cause out-of-bounds writes with packets injected into the network stack. Specifically, the problem lies in the rpl_ext_header_srh_update function in the two rpl-ext-header.c modules for RPL-Classic and RPL-Lite respectively. The addr_ptr variable is calculated using an unvalidated CMPR field value from the source routing header. An out-of-bounds write can be triggered on line 151 in os/net/routing/rpl-lite/rpl-ext-header.c and line 261 in os/net/routing/rpl-classic/rpl-ext-header.c, which contain the following memcpy call with addr_ptr as destination. The problem has been patched in Contiki-NG 4.6. Users can apply a patch out-of-band as a workaround.","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":"Out-of-bounds write in RPL-Classic and RPL-Lite","id":"CVE-2021-21257","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"XSS injection in ajax/kanban","id":"CVE-2021-21258"},"packages":[],"prev":{"headline":"entities switch IDOR","id":"CVE-2021-21255"},"products":["contiki-ng"],"published":"2021-06-18","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2018-19417","kev_date_added":null,"published":"2018-11-21"},{"cvss_score":9.8,"headline":"Contiki-NG has off-by-one error in Antelope DBMS","id":"CVE-2023-30546","kev_date_added":null,"published":"2023-04-26"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-24336","kev_date_added":null,"published":"2020-12-11"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-14934","kev_date_added":null,"published":"2020-08-18"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-14935","kev_date_added":null,"published":"2020-08-18"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-14936","kev_date_added":null,"published":"2020-08-18"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-8359","kev_date_added":null,"published":"2020-04-23"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["contiki-ng"]},"summary":"Attackers can trigger out-of-bounds writes via crafted RPL packets in Contiki-NG, potentially leading to code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2021-21257/"}