Read the docs

Memory exhaustion in Zeek file analysis via tiny blocks

Priority LOW 38Published · Updated

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.10 and 9.0.0 limits file reassembly buffers to 512KB but does not limit the number of blocks per file. An attacker can send about 500,000 tiny non-contiguous blocks for one file, for example with HTTP Content-Range requests, to stay under the byte limit while exhausting memory through per-block tracking overhead. The attacker can also keep multiple connections open to increase the impact.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the GitHub advisory

### Summary Zeek has a default reassembly buffer limit of 512KB for files. An attacker can bypass that limit and send ~500.000 non-contiguous blocks for a single file (e.g. using HTTP Content-Range) to stay under the limit buffer limit, but still exhaust memory due to the overhead required to keep track of each block. ### Details Besides the number of bytes, Zeek now limits the number of blocks allowed per file to a configurable value (Files::reassembly_buffer_blocks, default: 10000) and when the limit is reached, raises the existing `file_reassembly_overflow()` event. Setting the limit to 0 disables the limit and restores the old behavior. ### Proof of concept See testing/btest/Traces/http/file-reassembly-odd-offset-ranges.pcap.py for an example payload using HTTP Content-Range requests. And attacker can open multiple connections and keep them open. ### Impact This is a memory exhaustion vulnerability in the file analysis framework.

Why it matters now

Fix Fixed zeek: 8.0.11, 9.0.1

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—zeek<=8.0.10,<=9.0.08.0.11, 9.0.1Patch availableGHSA-q2jp-3x4p-fp6c
  • zeek Vendor— Affected <=8.0.10,<=9.0.0 Fixed in 8.0.11, 9.0.1 Patch available GHSA-q2jp-3x4p-fp6c

Remediation

Upgrade Zeek to version 8.0.11 or 9.0.1, which add a configurable limit on blocks per file (Files::reassembly_buffer_blocks, default 10000).

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · GHSA-q2jp-3x4p-fp6c zeek Fixed in 8.0.11, 9.0.1 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-q2jp-3x4p-fp6c

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences