Read the docs

Nested SOCKS tunnels can exhaust memory and stack 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

The SOCKS analyzer in Zeek keeps a stack of analyzer objects for each SOCKS tunnel it processes, so many nested tunnels can exhaust memory and stack. A remote attacker can send such packets, which causes a denial of service and can crash Zeek.

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

Description from the GitHub advisory

### Description of issue The SOCKS analyzer keeps a stack of PIA and SOCKS analyzer objects for each SOCKS tunnel that it encounters while processing a packet. With enough nested tunnels, this can lead to memory/stack exhaustion in Zeek and potentially crash. ### Impact/Category This is a denial-of-service risk due to the possibility of receiving these packets from remote systems ### Fix included The SOCKS analyzer now looks at the chain of analyzers and keeps a count of how many instances exist with each new tunnel. If the count reaches the value of the existing `Tunnel::max_depth` script-level constant, a `exceeded_tunnel_max_depth` weird is reported and analysis stops.

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.10, 9.0.08.0.11, 9.0.1Patch availableGHSA-jmgg-6f63-qccp
  • zeek (zeek) Vendor— Affected 8.0.10, 9.0.0 Fixed in 8.0.11, 9.0.1 Patch available GHSA-jmgg-6f63-qccp

Remediation

Upgrade Zeek to 8.0.11 or 9.0.1, which contain the fix. The last known affected versions are 8.0.10 and 9.0.0.

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

  • Fix · GHSA-jmgg-6f63-qccp zeek (zeek) Fixed in 8.0.11, 9.0.1 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-jmgg-6f63-qccp

References

Sources

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