{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-37281 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-37281 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-37281 is a medium-severity vulnerability in contiki-ng, published on 15 Sep 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-37281 and fix it if it is affected.\n\nWhat it is: CVE-2023-37281 is a medium-severity vulnerability in contiki-ng, published on 15 Sep 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-37281 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-37281/ (Markdown: https://insights.sbomify.com/CVE-2023-37281/index.md)","id":"CVE-2023-37281","markdown":"https://insights.sbomify.com/CVE-2023-37281/index.md","name":"CVE-2023-37281","record":{"aliases":["GHSA-2v4c-9p48-g9pr"],"analysis":{"component_type":"operating_system","fix_type":"workaround","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Contiki-NG IoT OS","requires_auth":"none","summary":"An attacker can trigger an out-of-bounds read in Contiki-NG by sending a crafted IPv6 packet, potentially leaking memory or causing a crash.","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":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","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 versions 4.9 and prior, when processing the various IPv6 header fields during IPHC header decompression, Contiki-NG confirms the received packet buffer contains enough data as needed for that field. But no similar check is done before decompressing the IPv6 address. Therefore, up to 16 bytes can be read out of bounds on the line with the statement `memcpy(\u0026ipaddr-\u003eu8[16 - postcount], iphc_ptr, postcount);`. The value of `postcount` depends on the address compression used in the received packet and can be controlled by the attacker. As a result, an attacker can inject a packet that causes an out-of-bound read. As of time of publication, a patched version is not available. As a workaround, one can apply the changes in Contiki-NG pull request #2509 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":"Out-of-bounds read during IPHC address decompression","id":"CVE-2023-37281","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":"Memory corruption in GTKWave","id":"CVE-2023-37282"},"packages":[],"prev":{"headline":"Pimcore admin UI vulnerable to Cross-site Scripting in two factor authentication setup page","id":"CVE-2023-37280"},"products":["contiki-ng"],"published":"2023-09-15","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-09-25","vendors":["contiki-ng"]},"summary":"An attacker can trigger an out-of-bounds read in Contiki-NG by sending a crafted IPv6 packet, potentially leaking memory or causing a crash.","url":"https://insights.sbomify.com/CVE-2023-37281/"}