Zeek DNS TCP parser allocates memory eagerly, enabling exhaustion
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 is affected. When parsing DNS messages over TCP, Zeek allocates the full buffer for a message as soon as the two byte size prefix is read, before the remaining data arrives. A remote attacker can make a Zeek worker allocate 64k of memory by sending a size field and keeping the connection open.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Description of issue When sending DNS messages over TCP, every message is prefixed with a 2 byte message size. Zeek would eagerly allocate the buffer, even if the remaining data would never arrive, allowing an attacker to allocate 64k of memory in a Zeek worker by sending a two byte message size field and keeping the connection open. ### Impact/Category This is a memory exhaustion vulnerability in the DNS parser. ### Fix included The parser was to allocate the required memory lazily instead of upfront.
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-v2hr-vp3r-q7m2 |
- zeek (zeek) Vendor— Affected <=8.0.9, <=8.2.1 Fixed in 8.0.11, 9.0.1 Patch available GHSA-v2hr-vp3r-q7m2
Remediation
Upgrade to Zeek 8.0.11 or 9.0.1, which allocate the required memory lazily instead of upfront.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-v2hr-vp3r-q7m2 zeek (zeek) Fixed in 8.0.11, 9.0.1 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-v2hr-vp3r-q7m2
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences