From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/wireshark: security bump to version 3.2.1
Date: Wed, 5 Feb 2020 20:35:14 +0100 [thread overview]
Message-ID: <20200205203514.3880713a@windsurf> (raw)
In-Reply-To: <20200205170532.32004-1-titouan.christophe@railnova.eu>
On Wed, 5 Feb 2020 18:05:32 +0100
Titouan Christophe <titouan.christophe@railnova.eu> wrote:
> This fixes CVE-2020-7044:
> In Wireshark 3.2.x before 3.2.1, the WASSP dissector could crash.
> This was addressed in epan/dissectors/packet-wassp.c by using
> >= and <= to resolve off-by-one errors.
>
> Also change the hash file to the new spacing convention introduced
> by Yann E. Morin.
>
> Signed-off-by: Titouan Christophe <titouan.christophe@railnova.eu>
> ---
> package/wireshark/wireshark.hash | 8 ++++----
> package/wireshark/wireshark.mk | 2 +-
> 2 files changed, 5 insertions(+), 5 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-02-05 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 17:05 [Buildroot] [PATCH 1/1] package/wireshark: security bump to version 3.2.1 Titouan Christophe
2020-02-05 19:35 ` Thomas Petazzoni [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=20200205203514.3880713a@windsurf \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox