Read the docs

NTLM challenge parsing in Zeek allows excessive memory allocation

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 8.2.1 are affected. The NTLM analyzer reads Challenge messages up to the next end of line pair or end of file, ignoring the length fields in the message. A remote attacker who can send NTLM Challenge packets can make Zeek allocate large amounts of memory, causing denial of service.

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

Description from the GitHub advisory

### Description of issue Parsing of NTLM Challenge packets reads to the next EOL pair or EOF, ignoring the length data that comes with the packets. This can cause Zeek to allocate large amounts of memory to store the record objects. ### Impact/Category This is a denial-of-service risk due to the possibility of receiving these packets from remote systems. ### Fix included Additional checks were added to the NTLM analyzer to limit the amount of parsing to the length information that comes in the messages, as well as checks for the validity of those lengths.

Why it matters now

Fix Fixed zeek (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 (zeek)<=8.0.9, <=8.2.18.0.11, 9.0.1Patch availableGHSA-j24f-fcr2-2fj4
  • zeek (zeek) Vendor— Affected <=8.0.9, <=8.2.1 Fixed in 8.0.11, 9.0.1 Patch available GHSA-j24f-fcr2-2fj4

Remediation

Upgrade Zeek to version 8.0.11 or 9.0.1, which add checks that limit NTLM parsing to the lengths in the message.

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

  • Fix · GHSA-j24f-fcr2-2fj4 zeek (zeek) Fixed in 8.0.11, 9.0.1 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-j24f-fcr2-2fj4

References

Sources

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