Contiki Ng
Approved changes feed: RSS · Atom
cpe:2.3:o:contiki-ng:contiki-ng:*:*:*:*:*:*:*:*
part: o version: * update: *
| Vendor | Contiki Ng (d6c3e92f-926f-5c64-9991-9584713f46f2) |
|---|---|
| Product | Contiki Ng (116de565-8030-5c48-9674-6498962ef901) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:bitbucket/dgiovane/contiki-ng |
purl2cpe | 2026-06-01 10:11:07.437008 |
pkg:github/contiki-ng/contiki-ng |
purl2cpe | 2026-06-01 10:11:07.437010 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-47181 |
vulnerable | 2026-06-08 06:48:11.548133 |
Unaligned memory access in RPL option processing in Contiki-NG
HIGH (7.5)
Contiki-NG is an open-source, cross-platform operating system for IoT devices. An unaligned memory access can be triggered in the two RPL implementations of the Contiki-NG operating system. The problem can occur when either one of these RPL implementations is enabled and connected to an RPL instance. If an IPv6 packet containing an odd number of padded bytes before the RPL option, it can cause the rpl_ext_header_hbh_update function to read a 16-bit integer from an odd address. The impact of this unaligned read is architecture-dependent, but can potentially cause the system to crash. The problem has not been patched as of release 4.9, but will be included in the next release. One can apply the changes in Contiki-NG pull request #2962 to patch the system or wait for the next release.
Published: 2024-11-27T18:20:41.583Z
Updated: 2024-11-27T19:20:07.764Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-41126 |
vulnerable | 2026-06-08 06:43:54.032469 |
Out-of-bounds read when decoding SNMP messages in Contiki-NG
HIGH (8.4)
Contiki-NG is an open-source, cross-platform operating system for IoT devices. An out-of-bounds read of 1 byte can be triggered when sending a packet to a device running the Contiki-NG operating system with SNMP enabled. The SNMP module is disabled in the default Contiki-NG configuration. The vulnerability exists in the os/net/app-layer/snmp/snmp-message.c module, where the snmp_message_decode function fails to check the boundary of the message buffer when reading a byte from it immediately after decoding an object identifier (OID). The problem has been patched in Contiki-NG pull request 2937. It will be included in the next release of Contiki-NG. Users are advised to either apply the patch manually or to wait for the next release. A workaround is to disable the SNMP module in the Contiki-NG build configuration.
Published: 2024-11-27T18:20:43.701Z
Updated: 2024-11-27T19:22:41.923Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-41125 |
vulnerable | 2026-06-08 06:43:54.031866 |
Out-of-bounds read in SNMP when decoding a string in Contiki-NG
HIGH (8.4)
Contiki-NG is an open-source, cross-platform operating system for IoT devices. An out-of-bounds read of 1 byte can be triggered when sending a packet to a device running the Contiki-NG operating system with SNMP enabled. The SNMP module is disabled in the default Contiki-NG configuration. The vulnerability exists in the os/net/app-layer/snmp/snmp-ber.c module, where the function snmp_ber_decode_string_len_buffer decodes the string length from a received SNMP packet. In one place, one byte is read from the buffer, without checking that the buffer has another byte available, leading to a possible out-of-bounds read. The problem has been patched in Contiki-NG pull request #2936. It will be included in the next release of Contiki-NG. Users are advised to apply the patch manually or to wait for the next release. A workaround is to disable the SNMP module in the Contiki-NG build configuration.
Published: 2024-11-27T18:20:45.613Z
Updated: 2024-11-27T19:22:42.056Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-50927 |
vulnerable | 2026-06-08 06:16:17.044479 |
Insufficient boundary checks for DIO and DAO messages in RPL-Lite in Contiki-NG
HIGH (8.6)
Contiki-NG is an open-source, cross-platform operating system for Next-Generation IoT devices. An attacker can trigger out-of-bounds reads in the RPL-Lite implementation of the RPL protocol in the Contiki-NG operating system. This vulnerability is caused by insufficient control of the lengths for DIO and DAO messages, in particular when they contain RPL sub-option headers. The problem has been patched in Contiki-NG 4.9. Users are advised to upgrade. Users unable to upgrade should manually apply the code changes in PR #2484.
Published: 2024-02-14T19:22:05.243Z
Updated: 2025-04-24T15:15:35.777Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-50926 |
vulnerable | 2026-06-08 06:16:17.043279 |
Unvalidated DIO prefix info length in RPL-Lite in Contiki-NG
HIGH (7.5)
Contiki-NG is an open-source, cross-platform operating system for Next-Generation IoT devices. An out-of-bounds read can be caused by an incoming DIO message when using the RPL-Lite implementation in the Contiki-NG operating system. More specifically, the prefix information of the DIO message contains a field that specifies the length of an IPv6 address prefix. The value of this field is not validated, which means that an attacker can set a value that is longer than the maximum prefix length. Subsequently, a memcmp function call that compares different prefixes can be called with a length argument that surpasses the boundary of the array allocated for the prefix, causing an out-of-bounds read. The problem has been patched in the "develop" branch of Contiki-NG, and is expected to be included in the next release. Users are advised to update as soon as they are able to or to manually apply the changes in Contiki-NG pull request #2721.
Published: 2024-02-14T19:28:11.556Z
Updated: 2024-08-02T22:23:44.103Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-48229 |
vulnerable | 2026-06-08 06:14:26.333684 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-37459 |
vulnerable | 2026-06-08 06:08:15.339198 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-37281 |
vulnerable | 2026-06-08 06:08:15.070803 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-34101 |
vulnerable | 2026-06-08 06:06:24.504116 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-34100 |
vulnerable | 2026-06-08 06:06:24.503421 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-31129 |
vulnerable | 2026-06-08 06:04:41.894120 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-30546 |
vulnerable | 2026-06-08 06:04:39.850971 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-29001 |
vulnerable | 2026-06-08 06:02:37.899628 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-28116 |
vulnerable | 2026-06-08 06:01:09.686443 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-23609 |
vulnerable | 2026-06-08 05:56:03.771424 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-41972 |
vulnerable | 2026-06-08 05:49:29.018709 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-41873 |
vulnerable | 2026-06-08 05:49:28.781434 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-36054 |
vulnerable | 2026-06-08 05:46:06.227056 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-36053 |
vulnerable | 2026-06-08 05:46:06.226497 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-36052 |
vulnerable | 2026-06-08 05:46:06.226027 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-35927 |
vulnerable | 2026-06-08 05:46:05.992788 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-35926 |
vulnerable | 2026-06-08 05:46:05.992184 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-32771 |
vulnerable | 2026-06-08 05:32:08.009319 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-21410 |
vulnerable | 2026-06-08 05:29:11.973991 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-21282 |
vulnerable | 2026-06-08 05:29:11.505052 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-21281 |
vulnerable | 2026-06-08 05:29:11.504717 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-21280 |
vulnerable | 2026-06-08 05:29:11.504372 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-21279 |
vulnerable | 2026-06-08 05:29:11.504003 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-21257 |
vulnerable | 2026-06-08 05:29:11.468604 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-24336 |
vulnerable | 2026-06-08 05:22:32.810628 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-14937 |
vulnerable | 2026-06-08 05:19:25.011835 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-14936 |
vulnerable | 2026-06-08 05:19:25.011499 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-14935 |
vulnerable | 2026-06-08 05:19:25.011012 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-14934 |
vulnerable | 2026-06-08 05:19:25.010580 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-13988 |
vulnerable | 2026-06-08 05:18:01.683796 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-12141 |
vulnerable | 2026-06-08 05:17:56.608718 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-12140 |
vulnerable | 2026-06-08 05:17:56.608288 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2019-9183 |
vulnerable | 2026-06-08 05:14:25.085813 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2019-8359 |
vulnerable | 2026-06-08 05:14:23.943418 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.