mirror of https://github.com/OISF/suricata
defrag: check tracker/packet family in compare
Ticket: 8510
Without this check, in case of a hash collision, and the other
fields are equal, we could end up consider adding an IPv6 packet
to a IPv4 tracker (or vice versa).
Doing so, we end up interpreting an IPv6 packet as an IPv4 one,
and we do not benefit from the bounds checks from ipv4/ipv6 decoder.
(cherry picked from commit 24527d662a)
pull/15433/head
parent
654f5fa64f
commit
97d6fa9e14
Loading…
Reference in New Issue