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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSuricata Ids Suricata
APPSuricata-Ids4.1.4
Related vulnerabilities
Suricata: out-of-bounds read przy składaniu fragmentów IPv4 (defrag.c)
Out-of-bounds read w parserze SSLv3/TLS 1.2 w Suricata 4.1.4
Suricata: heap-based buffer over-read w parserze banerów SSH
An issue was discovered in Suricata 4.1.3. The function process_reply_record_v3 lacks a check for the length o...
An issue was discovered in Suricata 4.1.3. If the function filetracker_newchunk encounters an unsafe "Some(sfc...