Integer overflow in Zeek SMTP MIME parsing enables denial of service
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 through 8.0.10 and through 9.0.0 are affected. A signed integer overflow occurs because Zeek buffers unbounded MIME entity data for the mime_entity_data() and mime_all_data() events, so a later large allocation fails with an out-of-memory error. A remote attacker can cause a denial of service by sending an SMTP transaction with a MIME entity longer than 2G. This applies only when those events are implemented, which is not the default.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Summary When enabling the mime_entity_data() or mime_all_data() event, a signed integer could be triggered followed due to Zeek accumulating an unbounded amount of data into separate String objects, concatenating these when creating the Event objects. Due to the overflow, a subsequent large allocation would trigger and immediate out-of-memory error. ### Details The amount of data buffered for the mime_entity_data() and mime_all_data() events is now capped to a default of 128M. This is configurable using the new script-level variables MIME::max_mime_entity_data_size and MIME::max_mime_all_data_size. Setting these variables to 0 disables the limit. Not that the `length` parameter of the events continues to represent the full length. Reaching either size results in Zeek producing a exceeded_max_mime_entity_data_size or exceeded_max_mime_all_data_size and marking the corresponding connection's history with an X. The ZeekString::concatenate() method was hardened to report and error and a dummy string when the length would exceed Zeek's maximum supported string length. ### Proof of concept Implement either of the following events and read/send an SMTP transaction transporting a MIME entity that's longer than 2G. ``` event mime_entity_data(c: connection, length: count, data: string) { print "mime_entity_data", c$uid, length, |data|, data[:16]; } event mime_all_data(c: connection, length: count, data: string) { print "mime_all_data", c$uid, length, |data|, data[:16]; } ``` ### Impact Exploitable denial of service if mime_all_data() and mime_entity_data() events are implemented. Not enabled by default.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | zeek | <=8.0.10,<=9.0.0 | 8.0.11, 9.0.1 | Patch available | GHSA-cg6p-j73j-76jm |
- zeek Vendor— Affected <=8.0.10,<=9.0.0 Fixed in 8.0.11, 9.0.1 Patch available GHSA-cg6p-j73j-76jm
Remediation
Upgrade Zeek to version 8.0.11 or 9.0.1, which fix this flaw.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-cg6p-j73j-76jm zeek Fixed in 8.0.11, 9.0.1 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-cg6p-j73j-76jm
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences