Read the docs

Unbounded state growth in Zeek DHCP join_data table

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 versions up to and including 8.0.9 and up to and including 8.2.1 are affected. DHCP log aggregation stores one DHCP::Info record per transaction ID in the join_data table, with no global entry cap or eviction policy, so its state grows without bound. A remote sender can choose fresh transaction IDs and keep all entries live within the expiry window, which causes a denial of service.

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

Description from the GitHub advisory

### Description of issue DHCP log aggregation stores one DHCP::Info record per transaction ID in DHCP::join_data. A remote sender can choose fresh XIDs and keep all entries live inside the create-expire window; there is no global entry cap or eviction policy for the table. ### Impact/Category his is a denial-of-service risk due to the possibility of receiving these packets from remote systems. ### Fix included A new `DHCP::max_tracked_transactions` script-level constant was added to cap the size of the `DHCP::join_data_table`. If the limit is reached, a `DHCP_max_tracked_transactions_exceeded` weird is generated, and least-recently-added DHCP transaction is logged and evicted from the table.

Why it matters now

Fix Fixed zeek (zeek): 8.0.10, 8.2.2, 9.0.0

SSVC decision points

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

Affected products

VendorProductAffected versionsFixed inStatusSource
—zeek (zeek)<=8.0.9, <=8.2.18.0.10, 8.2.2, 9.0.0Patch availableGHSA-qf53-234m-7vhq
  • zeek (zeek) Vendor— Affected <=8.0.9, <=8.2.1 Fixed in 8.0.10, 8.2.2, 9.0.0 Patch available GHSA-qf53-234m-7vhq

Remediation

Zeek fixed versions are 8.0.10, 8.2.2 and 9.0.0. The fix adds a DHCP::max_tracked_transactions constant that caps the table, and when the limit is reached a DHCP_max_tracked_transactions_exceeded weird is generated and the least-recently-added transaction is logged and evicted.

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

  • Fix · GHSA-qf53-234m-7vhq zeek (zeek) Fixed in 8.0.10, 8.2.2, 9.0.0 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-qf53-234m-7vhq

References

Sources

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