From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/wireshark: security bump to version 2.6.5
Date: Mon, 31 Dec 2018 14:31:55 +0100 [thread overview]
Message-ID: <20181231143155.1fea116e@windsurf> (raw)
In-Reply-To: <20181231083022.4370-1-peter@korsgaard.com>
Hello,
On Mon, 31 Dec 2018 09:30:21 +0100, Peter Korsgaard wrote:
> The following vulnerabilities have been fixed:
>
> - wnpa-sec-2018-51 The Wireshark dissection engine could crash. Bug 14466. CVE-2018-19625.
> - wnpa-sec-2018-52 The DCOM dissector could crash. Bug 15130. CVE-2018-19626.
> - wnpa-sec-2018-53 The LBMPDM dissector could crash. Bug 15132. CVE-2018-19623.
> - wnpa-sec-2018-54 The MMSE dissector could go into an infinite loop. Bug 15250. CVE-2018-19622.
> - wnpa-sec-2018-55 The IxVeriWave file parser could crash. Bug 15279. CVE-2018-19627.
> - wnpa-sec-2018-56 The PVFS dissector could crash. Bug 15280. CVE-2018-19624.
> - wnpa-sec-2018-57 The ZigBee ZCL dissector could crash. Bug 15281. CVE-2018-19628.
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> package/wireshark/wireshark.hash | 4 ++--
> package/wireshark/wireshark.mk | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-31 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 8:30 [Buildroot] [PATCH] package/wireshark: security bump to version 2.6.5 Peter Korsgaard
2018-12-31 13:31 ` Thomas Petazzoni [this message]
2019-01-23 15:14 ` 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=20181231143155.1fea116e@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