Attributed metadata history

v8.0.9

Thank you to Jan Grashöfer (@J-Gras), h4r4kIR1, Javid Khan (@dxbjavid), @jmestwa-coder, and @uwezkhan for their contributions to this release. This release fixes the following security issues: HIGH: The NVT, Rlogin, and RSH analyzers have received fixes to avoid unbounded state growth. Due to the fact that these packets can be received from remote hosts, these are considered DoS risks. The fixes include additional length-checking when processing packets, as well as a new set of weirds for when the standard Content-Line limits are exceeded. HIGH: A specially crafted WebSocket payload can cause the Spicy WebSocket analyzer to use excessive memory when processing close, ping, and pong frames. Due to the fact that these packets can be received from remote hosts, these are considered a DoS risk. The fix caps the size of those frames as per RFC 6455 (to 125 bytes) and adds a new weird for when that limit is exceeded. HIGH: A specially crafted series of Finger packets can cause the Spicy Finger analyzer to use excessive amounts of memory and potentially crash Zeek. Due to the fact that these packets can be received from remote hosts, this is considered a DoS risk. The fix includes a new Finger::max_line_length script constant. Spicy will report protocol violations if this limit is exceeded. HIGH: A specially crafted Kerberos packet can cause the Kerberos analyzer to enter an invalid state and potentially crash Zeek. Due to the fact that these packets can be received from remote hosts, this is considered a DoS risk. The fix includes additional checks for the state reported by the Kerberos packets. HIGH: A specially crafted series of RDP packets can cause the RDP analyzer to use excessive amounts of memory and potentially crash Zeek. Due to the fact that these packets can be received from remote hosts, this is considered a DoS risk. The fix includes a new rpc_max_pending_calls script constant. If this limit is exceeded, a new rpc_discarded_pending_calls event is emitted and a weird is reported. HIGH: A specially crafted IP packet can cause the IP analyzer to read past the end of the contents of the packet when emitting the packet_contents event and possibly crash. Due to the fact that these packets can be received from remote hosts, this is considered a DoS risk. The fix changes how Zeek checks the remaining length of the packet when emitting the event. The packet_contents event typically isn't used in production setups. HIGH: A specially crafted IP packet can cause the packet discarding code to read off the end of the packet when looking for follow-on header data. This may potentially lead to a crash of Zeek. Due to the fact that these packets can be received from remote hosts, this is considered a DoS risk. Note that this only applies if the user enables the discarder by implementing one of the discarder_check_* script functions. The fix includes additional length checks to the IP_HDr::ToPktHdrVal method to skip looking for additional headers if there isn’t enough data. HIGH: A specially crafted series of Gnutella packets may cause Zeek to continue accumulating memory and eventually crash. Due to the fact that these packets can be received from remote hosts, this is considered a DoS risk. Note that the Gnutella analyzer is disabled by default. The fix includes new Gnutella::max_line_length and Gnutella::max_header_length script constant values to control the maximum size of data processed, as well as new weirds for when the limits are exceeded. MEDIUM: A specially crafted ICMPv6 packet can cause the ICMP analyzer to skip part of the packet and not report corresponding events and logs. Due to the fact that these packets can be received from remote hosts, this is considered an evasion risk. The fix includes additional length-checking and five new weirds to cover the cases where the checks fail. MEDIUM: A specially crafted SSH packet can cause the SSH analyzer to throw BinPAC exceptions for extremely large packets

This record contains metadata and attribution only. It does not host, download, unpack, render, or execute malware samples.