Most recent entries from all

Most recent entries from all https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 10 Oct 2026 12:35:21 +0000 cnvd-2019-34384 https://cve.radiocsirt.org/vuln/cnvd-2019-34384 cnvd-2019-34384 https://cve.radiocsirt.org/vuln/cnvd-2019-34384 EUVD-2026-57745 https://cve.radiocsirt.org/vuln/euvd-2026-57745 EUVD-2026-57745 https://cve.radiocsirt.org/vuln/euvd-2026-57745 fkie_cve-2019-16411 https://cve.radiocsirt.org/vuln/fkie_cve-2019-16411 <p>An issue was discovered in Suricata 4.1.4. By sending multiple IPv4 packets that have invalid IPv4Options, the function IPV4OptValidateTimestamp in decode-ipv4.c tries to access a memory region that is not allocated. There is a check for o->len < 5 (corresponding to 2 bytes of header and 3 bytes of data). Then, "flag = *(o->data + 3)" places one beyond the 3 bytes, because the code should have been "flag = *(o->data + 1)" instead.</p> <p>An issue was discovered in Suricata 4.1.4. By sending multiple IPv4 packets that have invalid IPv4Options, the function IPV4OptValidateTimestamp in decode-ipv4.c tries to access a memory region that is not allocated. There is a check for o->len < 5 (corresponding to 2 bytes of header and 3 bytes of data). Then, "flag = *(o->data + 3)" places one beyond the 3 bytes, because the code should have been "flag = *(o->data + 1)" instead.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2019-16411 GHSA-wrwg-3wxg-wppx https://cve.radiocsirt.org/vuln/ghsa-wrwg-3wxg-wppx <p>An issue was discovered in Suricata 4.1.4. By sending multiple IPv4 packets that have invalid IPv4Options, the function IPV4OptValidateTimestamp in decode-ipv4.c tries to access a memory region that is not allocated. There is a check for o->len < 5 (corresponding to 2 bytes of header and 3 bytes of data). Then, "flag = *(o->data + 3)" places one beyond the 3 bytes, because the code should have been "flag = *(o->data + 1)" instead.</p> <p>An issue was discovered in Suricata 4.1.4. By sending multiple IPv4 packets that have invalid IPv4Options, the function IPV4OptValidateTimestamp in decode-ipv4.c tries to access a memory region that is not allocated. There is a check for o->len < 5 (corresponding to 2 bytes of header and 3 bytes of data). Then, "flag = *(o->data + 3)" places one beyond the 3 bytes, because the code should have been "flag = *(o->data + 1)" instead.</p> https://cve.radiocsirt.org/vuln/ghsa-wrwg-3wxg-wppx gsd-2019-16411 https://cve.radiocsirt.org/vuln/gsd-2019-16411 gsd-2019-16411 https://cve.radiocsirt.org/vuln/gsd-2019-16411 UBUNTU-CVE-2019-16411 https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-16411 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: suricata, Ubuntu:18.04:LTS: suricata</p> <p>An issue was discovered in Suricata 4.1.4. By sending multiple IPv4 packets that have invalid IPv4Options, the function IPV4OptValidateTimestamp in decode-ipv4.c tries to access a memory region that is not allocated. There is a check for o->len < 5 (corresponding to 2 bytes of header and 3 bytes of data). Then, "flag = *(o->data + 3)" places one beyond the 3 bytes, because the code should have been "flag = *(o->data + 1)" instead.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: suricata, Ubuntu:18.04:LTS: suricata</p> <p>An issue was discovered in Suricata 4.1.4. By sending multiple IPv4 packets that have invalid IPv4Options, the function IPV4OptValidateTimestamp in decode-ipv4.c tries to access a memory region that is not allocated. There is a check for o->len < 5 (corresponding to 2 bytes of header and 3 bytes of data). Then, "flag = *(o->data + 3)" places one beyond the 3 bytes, because the code should have been "flag = *(o->data + 1)" instead.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-16411