Personal patches
f57f99ffdc
security/bro: Update to 3.0.3 and address a number of potential denial of service issues: https://github.com/zeek/zeek/releases/tag/v3.0.2 https://github.com/zeek/zeek/releases/tag/v3.0.3 - Potential Denial of Service due to memory leak in DNS TSIG message parsing. - Potential Denial of Service due to memory leak (or assertion when compiling with assertions enabled) when receiving a second SSH KEX message after a first. - Potential Denial of Service due to buffer read overflow and/or memory leaks in Kerberos analyzer. The buffer read overflow could occur when the Kerberos message indicates it contains an IPv6 address, but does not send enough data to parse out a full IPv6 address. A memory leak could occur when processing KRB_KDC_REQ KRB_KDC_REP messages for message types that do not match a known/expected type. - Potential Denial of Service when sending many zero-length SSL/TLS certificate data. Such messages underwent the full Zeek file analysis treatment which is expensive (and meaninguless here) compared to how cheaply one can "create" or otherwise indicate many zero-length contained in an SSL message. - Potential Denial of Service due to buffer read overflow in SMB transaction data string handling. The length of strings being parsed from SMB messages was trusted to be whatever the message claimed instead of the actual length of data found in the message. - Potential Denial of Service due to null pointer dereference in FTP ADAT Base64 decoding. - Potential Denial of Service due buffer read overflow in FTP analyzer word/whitespace handling. This typically won't be a problem in most default deployments of Zeek since the FTP analyzer receives data from a ContentLine (NVT) support analyzer which first null-terminates the buffer used for further FTP parsing. Approved by: ler (mentor, implicit) Security: 4ae135f7-85cd-4c32-ad94-358271b31f7f Approved by: ports-secteam (joneum) |
||
|---|---|---|
| accessibility | ||
| arabic | ||
| archivers | ||
| astro | ||
| audio | ||
| base | ||
| benchmarks | ||
| biology | ||
| cad | ||
| chinese | ||
| comms | ||
| converters | ||
| databases | ||
| deskutils | ||
| devel | ||
| dns | ||
| editors | ||
| emulators | ||
| finance | ||
| french | ||
| ftp | ||
| games | ||
| german | ||
| graphics | ||
| hebrew | ||
| hungarian | ||
| irc | ||
| japanese | ||
| java | ||
| Keywords | ||
| korean | ||
| lang | ||
| math | ||
| misc | ||
| Mk | ||
| multimedia | ||
| net | ||
| net-im | ||
| net-mgmt | ||
| net-p2p | ||
| news | ||
| polish | ||
| ports-mgmt | ||
| portuguese | ||
| russian | ||
| science | ||
| security | ||
| shells | ||
| sysutils | ||
| Templates | ||
| textproc | ||
| Tools | ||
| ukrainian | ||
| vietnamese | ||
| www | ||
| x11 | ||
| x11-clocks | ||
| x11-drivers | ||
| x11-fm | ||
| x11-fonts | ||
| x11-servers | ||
| x11-themes | ||
| x11-toolkits | ||
| x11-wm | ||
| .arcconfig | ||
| .gitattributes | ||
| .gitauthors | ||
| .gitignore | ||
| .gitmessage | ||
| CHANGES | ||
| CONTRIBUTING.md | ||
| COPYRIGHT | ||
| GIDs | ||
| LEGAL | ||
| Makefile | ||
| MOVED | ||
| README | ||
| UIDs | ||
| UPDATING | ||
This is the FreeBSD Ports Collection. For an easy to use WEB-based interface to it, please see: https://www.FreeBSD.org/ports For general information on the Ports Collection, please see the FreeBSD Handbook ports section which is available from: https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/ports.html for the latest official version or: The ports(7) manual page (man ports). These will explain how to use ports and packages. If you would like to search for a port, you can do so easily by saying (in /usr/ports): make search name="<name>" or: make search key="<keyword>" which will generate a list of all ports matching <name> or <keyword>. make search also supports wildcards, such as: make search name="gtk*" For information about contributing to FreeBSD ports, please see the Porter's Handbook, available at: https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/ NOTE: This tree will GROW significantly in size during normal usage! The distribution tar files can and do accumulate in /usr/ports/distfiles, and the individual ports will also use up lots of space in their work subdirectories unless you remember to "make clean" after you're done building a given port. /usr/ports/distfiles can also be periodically cleaned without ill-effect.