Read the docs

DNS analyzer in Zeek hides records after WKS records in logs

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 contain a flaw in the DNS analyzer. The analyzer does not skip the data of the long-deprecated WKS resource record, so any resource record that follows it in a reply is ignored and not logged. An attacker can use this to evade Zeek's analysis capabilities.

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

Description from the GitHub advisory

### Description of issue The long-deprecated WKS RR isn't properly skipped by the DNS analyzer, which causes any RR in a reply after one to be ignored and not logged. ### Impact/Category This is an evasion of Zeek's analysis capabilities. ### Fix included The data for an WKS RR is not completely skipped. A basic event is still sent to indicate one as received, but Zeek does not parse the data since the RR type has been deprecated forever.

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-rx99-gxqp-gm4w
  • zeek (zeek) Vendor— Affected <=8.0.9, <=8.2.1 Fixed in 8.0.11, 9.0.1 Patch available GHSA-rx99-gxqp-gm4w

Remediation

Upgrade Zeek to version 8.0.11 or 9.0.1, which fix the flaw.

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

  • Fix · GHSA-rx99-gxqp-gm4w zeek (zeek) Fixed in 8.0.11, 9.0.1 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-rx99-gxqp-gm4w

References

Sources

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