From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] tcpreplay: security bump to version 4.3.1
Date: Thu, 24 Jan 2019 12:30:38 +0100 [thread overview]
Message-ID: <87va2efg2p.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <a85a18e1c92657beb563b238ffdd8548c3408b6b.1546964038.git.baruch@tkos.co.il> (Baruch Siach's message of "Tue, 8 Jan 2019 18:13:58 +0200")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> Upstream CHANGELOG entry for 4.3.0 lists these fixes:
> - CVE-2018-18408 use-after-free in post_args (#489)
> - CVE-2018-18407 heap-buffer-overflow csum_replace4 (#488)
> - CVE-2018-17974 heap-buffer-overflow dlt_en10mb_encode (#486)
> - CVE-2018-17580 heap-buffer-overflow fast_edit_packet (#485)
> - CVE-2018-17582 heap-buffer-overflow in get_next_packet (#484)
> - CVE-2018-13112 heap-buffer-overflow in get_l2len (#477 dup #408)
> Drop tr_cv_libpcap_version and ac_cv_have_bpf; unused in current
> configure script.
> Make configure script use pcap-config to list library dependencies.
> Unfortunately, pcap-config is not entirely correct, so we still need to
> set the LIBS variable for static linking.
> Use the smaller tar.xz archive.
> Add license file hash.
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Committed to 2018.02.x and 2018.11.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2019-01-24 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 16:13 [Buildroot] [PATCH] tcpreplay: security bump to version 4.3.1 Baruch Siach
2019-01-08 20:07 ` Peter Korsgaard
2019-01-24 11:30 ` Peter Korsgaard [this message]
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=87va2efg2p.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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