CVE-2017-7177Published Mar 18, 2017 · Mar 18Updated Oct 20
Suricata before 3.2.1 has an IPv4 defragmentation evasion issue caused by lack of a check for the IP protocol during…
High7.5Fix available
Suricata before 3.2.1 does not check the IP protocol when matching IPv4 fragments. This can allow an attacker to evade detection through network traffic; the input does not specify authentication or user-interaction requirements.
Operators running Suricata versions before 3.2.1 should check their deployments.