VuXML ID | Description |
96d6809a-81df-46d4-87ed-2f78c79f06b1 | zeek -- potential DoS vulnerabilities
Tim Wojtulewicz of Corelight reports:
Receiving DNS responses from async DNS requests (via
A specially-crafted stream of FTP packets containing a
command reply with many intermediate lines can cause Zeek
to spend a large amount of time processing data.
A specially-crafted set of packets containing extremely
large file offsets cause cause the reassembler code to
allocate large amounts of memory.
The DNS manager does not correctly expire responses
that don't contain any data, such those containing NXDOMAIN
or NODATA status codes. This can lead to Zeek allocating
large amounts of memory for these responses and never
deallocating them.
A specially-crafted stream of RDP packets can cause
Zeek to spend large protocol validation.
A specially-crafted stream of SMTP packets can cause
Zeek to spend large amounts of time processing data.
Discovery 2023-04-12 Entry 2023-04-12 zeek
< 5.0.8
https://github.com/zeek/zeek/releases/tag/v5.0.8
|
7a425536-74f7-4ce4-9768-0079a9d44d11 | zeek -- potential DoS vulnerabilities
Tim Wojtulewicz of Corelight reports:
Receiving DNS responses from async DNS requests (via
the lookup_addr, etc BIF methods) with the TTL set to
zero could cause the DNS manager to eventually stop being
able to make new requests.
Specially-crafted FTP packets with excessively long
usernames, passwords, or other fields could cause log
writes to use large amounts of disk space.
The find_all and find_all_ordered BIF methods could
take extremely large amounts of time to process incoming
data depending on the size of the input.
Discovery 2023-02-21 Entry 2023-02-21 zeek
< 5.0.7
https://github.com/zeek/zeek/releases/tag/v5.0.7
|
1ab7357f-a3c2-406a-89fb-fd00e49a71b5 | zeek -- potential DoS vulnerabilities
Tim Wojtulewicz of Corelight reports:
A specially-crafted series of FTP packets with a CMD
command with a large path followed by a very large number
of replies could cause Zeek to spend a long time processing
the data.
A specially-crafted with a truncated header can cause
Zeek to overflow memory and potentially crash.
A specially-crafted series of SMTP packets can cause
Zeek to generate a very large number of events and take
a long time to process them.
A specially-crafted series of POP3 packets containing
MIME data can cause Zeek to spend a long time dealing
with each individual file ID.
Discovery 2023-05-19 Entry 2023-05-19 zeek
< 5.0.9
https://github.com/zeek/zeek/releases/tag/v5.0.9
|
8eefa87f-31f1-496d-bf8e-2b465b6e4e8a | zeek -- potential DoS vulnerabilities
Tim Wojtulewicz of Corelight reports:
File extraction limits were not correctly enforced
for files containing large amounts of missing bytes.
Sessions are sometimes not cleaned up completely
within Zeek during shutdown, potentially causing a crash
when using the -B dpd flag for debug logging.
A specially-crafted HTTP packet can cause Zeek's
filename extraction code to take a long time to process
the data.
A specially-crafted series of FTP packets made up of
a CWD request followed by a large amount of ERPT requests
may cause Zeek to spend a long time logging the commands.
A specially-crafted VLAN packet can cause Zeek to
overflow memory and potentially crash.
Discovery 2023-09-12 Entry 2023-09-12 zeek
< 6.0.1
https://github.com/zeek/zeek/releases/tag/v6.0.1
|
fedf7e71-61bd-49ec-aaf0-6da14bdbb319 | zeek -- potential DoS vulnerability
Tim Wojtulewicz of Corelight reports:
A specially-crafted series of packets containing nested
MIME entities can cause Zeek to spend large amounts of
time parsing the entities.
Discovery 2024-01-22 Entry 2024-01-22 zeek
< 6.0.3
https://github.com/zeek/zeek/releases/tag/v6.0.3
|
386a14bb-1a21-41c6-a2cf-08d79213379b | zeek -- potential DoS vulnerabilities
Tim Wojtulewicz of Corelight reports:
A specially-crafted SSL packet could cause Zeek to
leak memory and potentially crash.
A specially-crafted series of FTP packets could cause
Zeek to log entries for requests that have already been
completed, using resources unnecessarily and potentially
causing Zeek to lose other traffic.
A specially-crafted series of SSL packets could cause
Zeek to output a very large number of unnecessary alerts
for the same record.
A specially-crafted series of SSL packets could cause
Zeek to generate very long ssl_history fields in the
ssl.log, potentially using a large amount of memory due
to unbounded state growth
A specially-crafted IEEE802.11 packet could cause
Zeek to overflow memory and potentially crash
Discovery 2023-10-27 Entry 2023-10-27 zeek
< 6.0.2
https://github.com/zeek/zeek/releases/tag/v6.0.2
|
2b5fc9c4-eaca-46e0-83d0-9b10c51c4b1b | zeek -- potential DoS vulnerabilities
Tim Wojtulewicz of Corelight reports:
A missing field in the SMB FSControl script-land record could
cause a heap buffer overflow when receiving packets containing
those header types.
Receiving a series of packets that start with HTTP/1.0
and then switch to HTTP/0.9 could cause Zeek to spend a
large amount of time processing the packets.
Receiving large numbers of FTP commands sequentially
from the network with bad data in them could cause Zeek
to spend a large amount of time processing the packets,
and generate a large amount of events.
Discovery 2023-02-01 Entry 2023-02-01 zeek
< 5.0.6
https://github.com/zeek/zeek/releases/tag/v5.0.6
|