OISF Suricata
Suricata app-layer: passed flows can retain transactions, causing resource exhaustion
Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. From 8.0.0 until 8.0.6, AppLayerParserSetTransactionInspectId() in src/app-layer-parser.c uses an inverted guard and marks only already-inspected transactions as inspected. On flows passed by a pass rule or pass-the-flow exception policy, detection is skipped, so completed transactions remain unmarked, are never freed, and are repeatedly rescanned. The per-flow list can grow without bound with quadratic cleanup cost, causing CPU and memory exhaustion. This issue is fixed in version 8.0.6.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 8.0.0, < 8.0.6
Fixed in 8.0.6
Mitigation
Upgrade suricata to 8.0.6 or later.
References
- Vendor advisory github.com/OISF/suricata/security/advisories/G…
- Patch github.com/OISF/suricata/pull/15726
- Patch github.com/OISF/suricata/commit/006e21c1ccc38c…
2 more
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.