{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-34101 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-34101 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-34101 is a high-severity vulnerability in contiki-ng, published on 14 Jun 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-34101 and fix it if it is affected.\n\nWhat it is: CVE-2023-34101 is a high-severity vulnerability in contiki-ng, published on 14 Jun 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-34101 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-2023-34101/ (Markdown: https://insights.sbomify.com/CVE-2023-34101/index.md)","id":"CVE-2023-34101","markdown":"https://insights.sbomify.com/CVE-2023-34101/index.md","name":"CVE-2023-34101","record":{"aliases":["GHSA-fp66-ff6x-7w2w"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IoT operating system","requires_auth":"none","summary":"An attacker can trigger an out-of-bounds read in Contiki-NG by sending truncated ICMP DAO packets, potentially exposing sensitive memory contents.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"contiki-ng","vendor":"contiki-ng"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"Contiki-NG is an operating system for internet of things devices. In version 4.8 and prior, when processing ICMP DAO packets in the `dao_input_storing` function, the Contiki-NG OS does not verify that the packet buffer is big enough to contain the bytes it needs before accessing them. Up to 16 bytes can be read out of bounds in the `dao_input_storing` function. An attacker can truncate an ICMP packet so that it does not contain enough data, leading to an out-of-bounds read on these lines. The problem has been patched in the \"develop\" branch of Contiki-NG, and is expected to be included in release 4.9. As a workaround, one can apply the changes in Contiki-NG pull request #2435 to patch the system.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Contiki-NG vulnerable to out-of-bounds read when processing ICMP DAO input","id":"CVE-2023-34101","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Possible unsafe reflection / partial denial of service in avo","id":"CVE-2023-34102"},"packages":[],"prev":{"headline":"Out-of-Bounds Read in contiki-ng","id":"CVE-2023-34100"},"products":["contiki-ng"],"published":"2023-06-14","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-12-30","vendors":["contiki-ng"]},"summary":"An attacker can trigger an out-of-bounds read in Contiki-NG by sending truncated ICMP DAO packets, potentially exposing sensitive memory contents.","url":"https://insights.sbomify.com/CVE-2023-34101/"}