From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] tcpdump: security bump to version 4.9.2
Date: Sat, 9 Sep 2017 22:12:29 +0200 [thread overview]
Message-ID: <20170909221229.57da435a@windsurf.lan> (raw)
In-Reply-To: <20170908121903.11830-1-peter@korsgaard.com>
Hello,
On Fri, 8 Sep 2017 14:19:03 +0200, Peter Korsgaard wrote:
> Fixes the following security issues (descriptions not public yet):
>
> Fix buffer overflow vulnerabilities:
> CVE-2017-11543 (SLIP)
> CVE-2017-13011 (bittok2str_internal)
> Fix infinite loop vulnerabilities:
> CVE-2017-12989 (RESP)
> CVE-2017-12990 (ISAKMP)
> CVE-2017-12995 (DNS)
> CVE-2017-12997 (LLDP)
> Fix buffer over-read vulnerabilities:
> CVE-2017-11541 (safeputs)
> CVE-2017-11542 (PIMv1)
> CVE-2017-12893 (SMB/CIFS)
> CVE-2017-12894 (lookup_bytestring)
> CVE-2017-12895 (ICMP)
> CVE-2017-12896 (ISAKMP)
> CVE-2017-12897 (ISO CLNS)
> CVE-2017-12898 (NFS)
> CVE-2017-12899 (DECnet)
> CVE-2017-12900 (tok2strbuf)
> CVE-2017-12901 (EIGRP)
> CVE-2017-12902 (Zephyr)
> CVE-2017-12985 (IPv6)
> CVE-2017-12986 (IPv6 routing headers)
> CVE-2017-12987 (IEEE 802.11)
> CVE-2017-12988 (telnet)
> CVE-2017-12991 (BGP)
> CVE-2017-12992 (RIPng)
> CVE-2017-12993 (Juniper)
> CVE-2017-11542 (PIMv1)
> CVE-2017-11541 (safeputs)
> CVE-2017-12994 (BGP)
> CVE-2017-12996 (PIMv2)
> CVE-2017-12998 (ISO IS-IS)
> CVE-2017-12999 (ISO IS-IS)
> CVE-2017-13000 (IEEE 802.15.4)
> CVE-2017-13001 (NFS)
> CVE-2017-13002 (AODV)
> CVE-2017-13003 (LMP)
> CVE-2017-13004 (Juniper)
> CVE-2017-13005 (NFS)
> CVE-2017-13006 (L2TP)
> CVE-2017-13007 (Apple PKTAP)
> CVE-2017-13008 (IEEE 802.11)
> CVE-2017-13009 (IPv6 mobility)
> CVE-2017-13010 (BEEP)
> CVE-2017-13012 (ICMP)
> CVE-2017-13013 (ARP)
> CVE-2017-13014 (White Board)
> CVE-2017-13015 (EAP)
> CVE-2017-11543 (SLIP)
> CVE-2017-13016 (ISO ES-IS)
> CVE-2017-13017 (DHCPv6)
> CVE-2017-13018 (PGM)
> CVE-2017-13019 (PGM)
> CVE-2017-13020 (VTP)
> CVE-2017-13021 (ICMPv6)
> CVE-2017-13022 (IP)
> CVE-2017-13023 (IPv6 mobility)
> CVE-2017-13024 (IPv6 mobility)
> CVE-2017-13025 (IPv6 mobility)
> CVE-2017-13026 (ISO IS-IS)
> CVE-2017-13027 (LLDP)
> CVE-2017-13028 (BOOTP)
> CVE-2017-13029 (PPP)
> CVE-2017-13030 (PIM)
> CVE-2017-13031 (IPv6 fragmentation header)
> CVE-2017-13032 (RADIUS)
> CVE-2017-13033 (VTP)
> CVE-2017-13034 (PGM)
> CVE-2017-13035 (ISO IS-IS)
> CVE-2017-13036 (OSPFv3)
> CVE-2017-13037 (IP)
> CVE-2017-13038 (PPP)
> CVE-2017-13039 (ISAKMP)
> CVE-2017-13040 (MPTCP)
> CVE-2017-13041 (ICMPv6)
> CVE-2017-13042 (HNCP)
> CVE-2017-13043 (BGP)
> CVE-2017-13044 (HNCP)
> CVE-2017-13045 (VQP)
> CVE-2017-13046 (BGP)
> CVE-2017-13047 (ISO ES-IS)
> CVE-2017-13048 (RSVP)
> CVE-2017-13049 (Rx)
> CVE-2017-13050 (RPKI-Router)
> CVE-2017-13051 (RSVP)
> CVE-2017-13052 (CFM)
> CVE-2017-13053 (BGP)
> CVE-2017-13054 (LLDP)
> CVE-2017-13055 (ISO IS-IS)
> CVE-2017-13687 (Cisco HDLC)
> CVE-2017-13688 (OLSR)
> CVE-2017-13689 (IKEv1)
> CVE-2017-13690 (IKEv2)
> CVE-2017-13725 (IPv6 routing headers)
>
> While we're at it, add a hash for the license file.
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> package/tcpdump/tcpdump.hash | 5 +++--
> package/tcpdump/tcpdump.mk | 2 +-
> 2 files changed, 4 insertions(+), 3 deletions(-)
Applied to master, thanks. Interesting number of CVEs being fixed here.
Are they trying to generate an integer overflow in the CVE
database ? :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-09-09 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 12:19 [Buildroot] [PATCH] tcpdump: security bump to version 4.9.2 Peter Korsgaard
2017-09-09 20:12 ` Thomas Petazzoni [this message]
2017-09-10 21:47 ` Peter Korsgaard
2017-09-21 10:05 ` Peter Korsgaard
2017-10-16 21:52 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170909221229.57da435a@windsurf.lan \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox