Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] wireshark: bump version to 2.2.16 (security)
Date: Thu, 9 Aug 2018 10:10:55 +0200	[thread overview]
Message-ID: <20180809101055.0d7fedc5@windsurf> (raw)
In-Reply-To: <20180808204005.24356-1-nerv@dawncrow.de>

Hello,

On Wed,  8 Aug 2018 22:40:05 +0200, Andr? Hentschel wrote:
> Security fixes since 2.2.15:
> 
> - wnpa-sec-2018-06
>   RPKI-Router infinite loop. Bug 14414. CVE-2018-7325.
> - wnpa-sec-2018-34
>   BGP dissector large loop. Bug 13741. CVE-2018-14342.
> - wnpa-sec-2018-35
>   ISMP dissector crash. Bug 14672. CVE-2018-14344.
> - wnpa-sec-2018-36
>   Multiple dissectors could crash. Bug 14675. CVE-2018-14340.
> - wnpa-sec-2018-37
>   ASN.1 BER dissector crash. Bug 14682. CVE-2018-14343.
> - wnpa-sec-2018-38
>   MMSE dissector infinite loop. Bug 14738. CVE-2018-14339.
> - wnpa-sec-2018-39
>   DICOM dissector crash. Bug 14742. CVE-2018-14341.
> - wnpa-sec-2018-40
>   Bazaar dissector infinite loop. Bug 14841.
> - wnpa-sec-2018-41
>   HTTP2 dissector crash. Bug 14869.
> 
> Full release notes:
> 
>   https://www.wireshark.org/docs/relnotes/wireshark-2.2.16.html
> 
> Signed-off-by: Andr? Hentschel <nerv@dawncrow.de>
> ---
>  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 (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-08-09  8:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-08 20:40 [Buildroot] [PATCH] wireshark: bump version to 2.2.16 (security) André Hentschel
2018-08-09  8:10 ` Thomas Petazzoni [this message]
2018-08-24  6:50 ` 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=20180809101055.0d7fedc5@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