Memory exhaustion in Zeek DNP3 parser from large fragments
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 buffers DNP3 application layer fragments in its DNP3 parser without a size limit before parsing them. Large fragments allocate many internal DNP3 objects, which can exhaust the memory of the process that runs Zeek.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Summary Zeek buffered DNP3 application layer fragments without a size constraint before actual parsing. Parsing large application layer fragments would easily exhaust memory due to allocation of large internal DNP3 objects in arrays. ### Details A new script-level variable DNP3::max_application_layer_fragment_size (default: 100 KB) was introduced to cap the maximum supported application layer fragment size, thereby bounding the number of internal objects. When reached, Zeek will mark the connection's history with an X and raise a new dnp3_max_application_layer_fragment_size_exceeded weird. The DNP3 parser is then switched into "skpping mode". Setting the value to 0 disables the limit. Additionally, the DNP3's BinPAC implementation was switched to use the &transient attribute on various arrays to avoid accumulating unused and short-lived DNP3 objects during parsing. ### Proof of concept Proof of concept PCAP generator script can be found in the Zeek source code, used for the test: testing/btest/Traces/dnp3/dnp3-response-object-count-amplification.pcap.py ### Impact This is a memory exhaustion vulnerability in Zeek's DNP3 parser.
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 (zeek) | <=8.0.10, <=9.0.0 | 8.0.11, 9.0.1 | Patch available | GHSA-v6w4-3pj6-p4ch |
- zeek (zeek) Vendor— Affected <=8.0.10, <=9.0.0 Fixed in 8.0.11, 9.0.1 Patch available GHSA-v6w4-3pj6-p4ch
Remediation
Upgrade Zeek to 8.0.11 or 9.0.1. Versions up to and including 8.0.10 and 9.0.0 are affected. The DNP3::max_application_layer_fragment_size script variable (default 100 KB) caps fragment size in the fixed releases; setting it to 0 disables that limit.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-v6w4-3pj6-p4ch zeek (zeek) Fixed in 8.0.11, 9.0.1 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-v6w4-3pj6-p4ch
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences