Suricata flow: IPv4/IPv6 hash collision can reuse wrong flow state
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.9epss 0.3%
exploitation probability
0.3%top 76% of all CVEs
observed exploitation
nono source reports it
Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. Prior to 7.0.17 and 8.0.6, src/flow-hash.c can treat an IPv4 and IPv6 flow as equal without comparing the IP family when their raw address words, ports, protocol, VLAN, recursion level, live device, and hash bucket align. An IPv6 packet can therefore reuse IPv4 flow state or the reverse, causing incorrect flowbit state, detection bypass, or IP-only bypass. This issue is fixed in versions 8.0.6 and 7.0.17.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Affected products
OISF · suricataReferences
https://github.com/OISF/suricata/commit/181b3b2fdd1fe87e4534de4fc79e29a083ef125fhttps://github.com/OISF/suricata/commit/4e2f23d031fbcfd72883bacd3d723c9874f23701https://github.com/OISF/suricata/commit/bc41dcc854e24487d3786ce578a8a86a8350ab20https://github.com/OISF/suricata/releases/tag/suricata-7.0.17https://github.com/OISF/suricata/releases/tag/suricata-8.0.6https://github.com/OISF/suricata/security/advisories/GHSA-fvwh-wjcq-2586https://redmine.openinfosecfoundation.org/issues/8558