Suricata ippair: hash collision can cause incorrect state reuse across IPv4 and IPv6
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.3epss 0.4%
exploitation probability
0.4%top 62% 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, crafted IPv4 and IPv6 address pairs can collide in the IPPair hash because src/ippair.c did not compare the IP address family before reusing IPPair-backed state. This can apply state from one IP family to another for xbits track ip_pair, FTP data expectations, and, on the 7.0 release line, thresholding, detection_filter, and rate_filter rules using track by_both, causing incorrect detection state. This issue is fixed in versions 8.0.6 and 7.0.17.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Affected products
OISF · suricataReferences
https://github.com/OISF/suricata/commit/4a728464e6eb9e273bb02e3df0c28929b28db71dhttps://github.com/OISF/suricata/commit/9d788575c5d22a34eeed50d56557ed12b05e0aechttps://github.com/OISF/suricata/commit/c92e270c4a795c52bce610aa1ce9ebaf065c49e6https://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-2r8x-23fw-hgcghttps://redmine.openinfosecfoundation.org/issues/8559