Read the docs

SSL: Unbounded certificate state growth in Zeek

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's SSL parsers did not cap the certificate list in the initial handshake. A remote attacker could send a large number of certificates and exhaust Zeek's memory, causing an out-of-memory crash. This is a denial-of-service risk. Kara Zaffarano and Kyle Elliott of Trail of Bits found the issue in collaboration with OpenAI.

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

Description from the GitHub advisory

### Summary Neither of the possible SSL parsers capped the certificate list in the initial handshake. An attacker could send a large number of certificates and exhaust Zeek's memory, causing an out-of-memory crash. Found by Kara Zaffarano and Kyle Elliott of Trail of Bits, in collaboration with OpenAI. ### Details The maximum number of SSL certificates is now capped by `SSL::max_certificates`. If this cap is exceeded, a weird is emit and an `X` added to the connection history (for the default analyzer only). The remaining certificates are skipped. ### Proof of concept Proof of concept PCAP generator script can be found in the Zeek source code, used for the test: testing/btest/Traces/tls/tls-certificate-chain-limit.pcap.py ### Impact This is a denial-of-service risk due to the possibility of receiving these packets from remote systems.

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-rmv9-rq35-fw28
  • zeek Vendor— Affected <=8.0.10, 9.0.0 Fixed in 8.0.11, 9.0.1 Patch available GHSA-rmv9-rq35-fw28

Remediation

Upgrade to Zeek 8.0.11 or 9.0.1. The fix caps the certificate count with SSL::max_certificates. Certificates beyond the cap are skipped, a weird is emitted, and an X is added to the connection history (default analyzer only).

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

  • Fix · GHSA-rmv9-rq35-fw28 zeek Fixed in 8.0.11, 9.0.1 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-rmv9-rq35-fw28

References

Sources

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