231 matches found
PT-2022-23145 · Unknown · Contiki-Ng
Name of the Vulnerable Software and Affected Versions: Contiki-NG versions prior to 4.8 Description: The low-power IPv6 network stack of Contiki-NG has a buffer module that processes IPv6 extension headers in incoming data packets. The function uipbuf get next header casts a pointer to a uip ext...
PT-2022-36848
Name of the Vulnerable Software and Affected Versions No specific software or versions are mentioned in the provided description. Description A heap buffer overflow read issue is identified, associated with the handling of IPv6 extension headers. The crash occurs in the ndpi handle ipv6 extension...
ndpi:fuzz_ndpi_reader: Heap-buffer-overflow in ndpi_handle_ipv6_extension_headers
Project: https://github.com/ntop/nDPI.git Detailed Report: https://oss-fuzz.com/testcase?key=6390337302560768 Project: ndpi Fuzzing Engine: libFuzzer Fuzz Target: fuzzndpireader Job Type: libfuzzerasanndpi Platform Id: linux Crash Type: Heap-buffer-overflow READ 1 Crash Address: 0x60d000000f67...
CVE-2021-21280
Contiki-NG is an open-source, cross-platform operating system for internet of things devices. It is possible to cause an out-of-bounds write in versions of Contiki-NG prior to 4.6 when transmitting a 6LoWPAN packet with a chain of extension headers. Unfortunately, the written header is not checke...
Design/Logic Flaw
Contiki-NG is an open-source, cross-platform operating system for internet of things devices. It is possible to cause an out-of-bounds write in versions of Contiki-NG prior to 4.6 when transmitting a 6LoWPAN packet with a chain of extension headers. Unfortunately, the written header is not checke...
CVE-2021-21280
Contiki-NG is an open-source, cross-platform operating system for internet of things devices. It is possible to cause an out-of-bounds write in versions of Contiki-NG prior to 4.6 when transmitting a 6LoWPAN packet with a chain of extension headers. Unfortunately, the written header is not checke...
PT-2021-14386
Name of the Vulnerable Software and Affected Versions: Contiki-NG versions prior to 4.6 Description: The issue affects Contiki-NG, an open-source operating system for internet of things devices. It is possible to cause an out-of-bounds write when transmitting a 6LoWPAN packet with a chain of...
CVE-2021-21280: Out-of-bounds Write
Contiki-NG is an open-source, cross-platform operating system for internet of things devices. It is possible to cause an out-of-bounds write in versions of Contiki-NG prior to 4.6 when transmitting a 6LoWPAN packet with a chain of extension headers. Unfortunately, the written header is not checke...
Contiki-NG buffer error vulnerability
"Contiki-NG is an open source cross-platform operating system for next-generation IoT devices. An out-of-bounds write vulnerability exists in Contiki-NG versions prior to 4.6 when processing 6LoWPAN extension headers. The vulnerability stems from a failure to check whether the written header is...
CVE-2021-28362
An issue was discovered in Contiki through 3.0. When sending an ICMPv6 error message because of invalid extension header options in an incoming IPv6 packet, there is an attempt to remove the RPL extension headers. Because the packet length and the extension header length are unchecked with respec...
CVE-2021-28362
An issue was discovered in Contiki through 3.0. When sending an ICMPv6 error message because of invalid extension header options in an incoming IPv6 packet, there is an attempt to remove the RPL extension headers. Because the packet length and the extension header length are unchecked with respec...
CVE-2021-28362
An issue was discovered in Contiki through 3.0. When sending an ICMPv6 error message because of invalid extension header options in an incoming IPv6 packet, there is an attempt to remove the RPL extension headers. Because the packet length and the extension header length are unchecked with respec...
CVE-2020-17442
An issue was discovered in picoTCP 1.7.0. The code for parsing the hop-by-hop IPv6 extension headers does not validate the bounds of the extension header length value, which may result in Integer Wraparound. Therefore, a crafted extension header length value may cause Denial-of-Service because it...
CVE-2020-17468
An issue was discovered in FNET through 4.6.4. The code for processing the hop-by-hop header in the IPv6 extension headers doesn't check for a valid length of an extension header, and therefore an out-of-bounds read can occur in fnetip6extheaderhandleroptions in fnetip6.c, leading to...
Design/Logic Flaw
An issue was discovered in FNET through 4.6.4. The code for processing the hop-by-hop header in the IPv6 extension headers doesn't check for a valid length of an extension header, and therefore an out-of-bounds read can occur in fnetip6extheaderhandleroptions in fnetip6.c, leading to...
Design/Logic Flaw
An issue was discovered in picoTCP 1.7.0. The code for parsing the hop-by-hop IPv6 extension headers does not validate the bounds of the extension header length value, which may result in Integer Wraparound. Therefore, a crafted extension header length value may cause Denial-of-Service because it...
Buffer overflow
An issue was discovered in picoTCP 1.7.0. The routine for processing the next header field and deducing whether the IPv6 extension headers are valid doesn't check whether the header extension length field would overflow. Therefore, if it wraps around to zero, iterating through the extension heade...
CVE-2020-17468
An issue was discovered in FNET through 4.6.4. The code for processing the hop-by-hop header in the IPv6 extension headers doesn't check for a valid length of an extension header, and therefore an out-of-bounds read can occur in fnetip6extheaderhandleroptions in fnetip6.c, leading to...
CVE-2020-17442
An issue was discovered in picoTCP 1.7.0. The code for parsing the hop-by-hop IPv6 extension headers does not validate the bounds of the extension header length value, which may result in Integer Wraparound. Therefore, a crafted extension header length value may cause Denial-of-Service because it...
CVE-2020-17442
CVE-2020-17442 affects picoTCP (and picoTCP-NG) 1.7.0. The issue is in parsing IPv6 hop-by-hop extension headers, where the header length bound is not validated, enabling integer wraparound and a potential DoS in pico_ipv6_process_hopbyhop(). Public details are provided in the SUSE/FORESA advisor...