Memory amplification in Zeek reassembler for blocks after a hole
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 up to and including 8.0.9 and up to and including 8.2.1 are affected. The Reassembler creates a new block object for each block received after a hole, which bypasses the existing block count limits. A remote attacker who sends many very small blocks can make Zeek use a large amount of memory for little data, causing denial of service.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Summary When blocks are received by the Reassembler after a hole, they create new block objects for each block. This bypasses the existing limits for the number of blocks. With many very small blocks, this can amplify into a large amount of memory used for small amounts of data received. This issue was reported the Canadian Communications Security Establishment. ### Details The reassembler code was slightly restructured to handle contiguous blocks. Instead of creating new block objects for each one, it will attempt to find a block that comes directly before the new one. If one is found, the data from the new block is added to the existing block object. This reuses all of the existing ancillary tracking data for that existing block instead of creating a whole new object. ### Proof of concept There is no proof of concept for this issue since an additional btest and associated pcap was not added. For an example of how it works, see the changes for the btest baseline for the core.reassembly btest. ### Impact This is a denial-of-service risk due to the possibility of receiving these packets from remote systems.
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 (zeek) | <=8.0.9, <=8.2.1 | 8.0.11, 9.0.1 | Patch available | GHSA-gxg9-7vfv-qq5f |
- zeek (zeek) Vendor— Affected <=8.0.9, <=8.2.1 Fixed in 8.0.11, 9.0.1 Patch available GHSA-gxg9-7vfv-qq5f
Remediation
Upgrade Zeek to version 8.0.11 or 9.0.1, which fix this issue.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-gxg9-7vfv-qq5f zeek (zeek) Fixed in 8.0.11, 9.0.1 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-gxg9-7vfv-qq5f
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences