Read the docs

Memory exhaustion in Zeek SIP handling from many VIA headers

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 8.0.9 and earlier and 8.2.1 and earlier are affected by a memory exhaustion flaw in its SIP handling. Excessive memory use occurs when a SIP session contains a large number of VIA headers, because Zeek does not limit how many are processed. A remote attacker can send a specially crafted series of SIP packets to make Zeek use large amounts of memory and potentially crash.

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

Description from the GitHub advisory

### Description of issue A specially-crafted series of SIP packets containing large number of VIA headers can cause Zeek to use large amounts of memory 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 fix included adds configurable constants to set limits to the number of these headers per SIP session, as well as a set of weird for reporting when they are exceeded.

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-wjf9-326g-m9h3
  • zeek (zeek) Vendor— Affected <=8.0.9, <=8.2.1 Fixed in 8.0.10, 8.2.2, 9.0.0 Patch available GHSA-wjf9-326g-m9h3

Remediation

Upgrade Zeek to version 8.0.10, 8.2.2 or 9.0.0, which fix the flaw by adding configurable limits on the number of VIA headers per SIP session.

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

  • Fix · GHSA-wjf9-326g-m9h3 zeek (zeek) Fixed in 8.0.10, 8.2.2, 9.0.0 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-wjf9-326g-m9h3

References

Sources

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