diff options
| author | leres <leres@FreeBSD.org> | 2019-06-01 03:23:07 +0800 |
|---|---|---|
| committer | leres <leres@FreeBSD.org> | 2019-06-01 03:23:07 +0800 |
| commit | 9f5e99a2de1d2f9991c98a77893638962cb0d4fb (patch) | |
| tree | b692786162d77509bc41a5c9af6adaac807be5a4 /security/bro | |
| parent | 4d04633bd38d4f8d3e4f58c62f1011584c52360f (diff) | |
| download | freebsd-ports-gnome-9f5e99a2de1d2f9991c98a77893638962cb0d4fb.tar.gz freebsd-ports-gnome-9f5e99a2de1d2f9991c98a77893638962cb0d4fb.tar.zst freebsd-ports-gnome-9f5e99a2de1d2f9991c98a77893638962cb0d4fb.zip | |
security/bro: Update to 2.6.2 and address several denial of service
vulnerabilities:
https://raw.githubusercontent.com/zeek/zeek/bb979702cf9a2fa67b8d1a1c7f88d0b56c6af104/NEWS
- Integer type mismatches in BinPAC-generated parser code and Bro
analyzer code may allow for crafted packet data to cause
unintentional code paths in the analysis logic to be taken due
to unsafe integer conversions causing the parser and analysis
logic to each expect different fields to have been parsed. One
such example, reported by Maksim Shudrak, causes the Kerberos
analyzer to dereference a null pointer. CVE-2019-12175 was
assigned for this issue.
- The Kerberos parser allows for several fields to be left
uninitialized, but they were not marked with an &optional attribute
and several usages lacked existence checks. Crafted packet data
could potentially cause an attempt to access such uninitialized
fields, generate a runtime error/exception, and leak memory.
Existence checks and &optional attributes have been added to the
relevent Kerberos fields.
- BinPAC-generated protocol parsers commonly contain fields whose
length is derived from other packet input, and for those that
allow for incremental parsing, BinPAC did not impose a limit on
how large such a field could grow, allowing for remotely-controlled
packet data to cause growth of BinPAC's flowbuffer bounded only
by the numeric limit of an unsigned 64-bit integer, leading to
memory exhaustion. There is now a generalized limit for how
large flowbuffers are allowed to grow, tunable by setting
"BinPAC::flowbuffer_capacity_max".
Approved by: ler (mentor, implicit)
MFH: 2019Q2
Security: 177fa455-48fc-4ded-ba1b-9975caa7f62a
Diffstat (limited to 'security/bro')
| -rw-r--r-- | security/bro/Makefile | 3 | ||||
| -rw-r--r-- | security/bro/distinfo | 6 |
2 files changed, 4 insertions, 5 deletions
diff --git a/security/bro/Makefile b/security/bro/Makefile index abfd705c920d..9dcfabbea489 100644 --- a/security/bro/Makefile +++ b/security/bro/Makefile @@ -2,8 +2,7 @@ # $FreeBSD$ PORTNAME= bro -PORTVERSION= 2.6.1 -PORTREVISION= 2 +PORTVERSION= 2.6.2 CATEGORIES= security MASTER_SITES= https://www.zeek.org/downloads/ DISTFILES= ${DISTNAME}${EXTRACT_SUFX} diff --git a/security/bro/distinfo b/security/bro/distinfo index ac630908811d..2422966a02dc 100644 --- a/security/bro/distinfo +++ b/security/bro/distinfo @@ -1,5 +1,5 @@ -TIMESTAMP = 1545247794 -SHA256 (bro-2.6.1.tar.gz) = d9718b83fdae0c76eea5254a4b9470304c4d1d3778687de9a4fe0b5dffea521b -SIZE (bro-2.6.1.tar.gz) = 28432762 +TIMESTAMP = 1559318790 +SHA256 (bro-2.6.2.tar.gz) = 6df6876f3f7b1dd8afeb3d5f88bfb9269f52d5d796258c4414bdd91aa2eac0a6 +SIZE (bro-2.6.2.tar.gz) = 28477996 SHA256 (bro-bro-netmap-cf88debf487b31ab30dc3b5bac64783b4e49997e_GH0.tar.gz) = 383423f92932c3ef244194954708b3a237b4f37ebc358014f51dcb3b9786896b SIZE (bro-bro-netmap-cf88debf487b31ab30dc3b5bac64783b4e49997e_GH0.tar.gz) = 24630 |