Unbounded connection history growth in Zeek
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
Zeek is affected in versions up to and including 8.0.10 and 9.0.0. A missing limit on the internal connection history lets an attacker append characters to it without bound during a flood of FIN packets with alternating sequence numbers, causing memory exhaustion in the Connection class. The logging framework caps the logged history field to 4K by default, but the internal member is not capped.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Summary Zeek could be tricked into appending a new `F` character to the Connection's internal history member using a FIN flood with alternating sequence numbers. While the logging framework would cap the history field to 4K by default (Log::default_max_field_string_bytes), the internal history member would grow unbounded in the face of such abnormal traffic. ### Details A new script-level constant max_connection_history_size was introduced. When reached, Zeek will ensure to put an X into the connection's history and raise a new max_connection_history_size_reached weird. Setting max_connection_history_size to 0 disables the limit. ### Proof of concept Proof of concept PCAP generator script can be found in the Zeek source code, used for the test: testing/btest/Traces/tcp/fin-flood.pcap.py ### Impact This is a memory exhaustion vulnerability in Zeek's Connection class.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | zeek | <=8.0.10,<=9.0.0 | 8.0.11, 9.0.1 | Patch available | GHSA-256v-q24v-rm42 |
- zeek Vendor— Affected <=8.0.10,<=9.0.0 Fixed in 8.0.11, 9.0.1 Patch available GHSA-256v-q24v-rm42
Remediation
Upgrade Zeek to version 8.0.11 or 9.0.1, which fix the issue. Setting max_connection_history_size to 0 disables the new limit, so keep it at its default value to retain the protection.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-256v-q24v-rm42 zeek Fixed in 8.0.11, 9.0.1 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-256v-q24v-rm42
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences