From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/tcpreplay: security bump to version 4.3.3
Date: Wed, 17 Jun 2020 22:00:54 +0200 [thread overview]
Message-ID: <20200617220054.694d6590@windsurf.home> (raw)
In-Reply-To: <20200617195654.39410-1-fontaine.fabrice@gmail.com>
On Wed, 17 Jun 2020 21:56:54 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> - Fix CVE-2020-12740: tcprewrite in Tcpreplay through 4.3.2 has a
> heap-based buffer over-read during a get_c operation. The issue is
> being triggered in the function get_ipv6_next() at common/get.c.
> - Update indentation in hash file (two spaces)
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/tcpreplay/tcpreplay.hash | 6 +++---
> package/tcpreplay/tcpreplay.mk | 2 +-
> 2 files changed, 4 insertions(+), 4 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-06-17 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 19:56 [Buildroot] [PATCH 1/1] package/tcpreplay: security bump to version 4.3.3 Fabrice Fontaine
2020-06-17 20:00 ` Thomas Petazzoni [this message]
2020-07-15 19:40 ` 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=20200617220054.694d6590@windsurf.home \
--to=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.