From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] wireshark: security bump to version 2.0.2
Date: Sat, 27 Feb 2016 16:28:06 +0100 [thread overview]
Message-ID: <20160227162806.47925dcc@free-electrons.com> (raw)
In-Reply-To: <1456578313-31287-1-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Sat, 27 Feb 2016 10:05:13 -0300, Gustavo Zacarias wrote:
> CVE-2016-2521 - DLL hijacking vulnerability.
> CVE-2016-2522 - ASN.1 BER dissector crash.
> CVE-2016-2523 - DNP dissector infinite loop.
> CVE-2016-2524 - X.509AF dissector crash.
> CVE-2016-2525 - HTTP/2 dissector crash.
> CVE-2016-2526 - HiQnet dissector crash.
> CVE-2016-2527 - 3GPP TS 32.423 Trace file parser crash.
> CVE-2016-2528 - LBMC dissector crash.
> CVE-2016-2529 - iSeries file parser crash.
> CVE-2016-2530 - RSL dissector crash.
> CVE-2016-2531 - RSL dissector crash.
> CVE-2016-2532 - LLRP dissector crash.
> wnpa-sec-2016-12 - Ixia IxVeriWave file parser crash.
> wnpa-sec-2016-13 - IEEE 802.11 dissector crash.
> wnpa-sec-2016-14 - GSM A-bis OML dissector crash.
> wnpa-sec-2016-15 - ASN.1 BER dissector crash.
> wnpa-sec-2016-16 - SPICE dissector large loop.
> wnpa-sec-2016-17 - NFS dissector crash.
> wnpa-sec-2016-18 - ASN.1 BER dissector crash.
Nice set of CVEs :-)
Applied to master, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-02-27 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 13:05 [Buildroot] [PATCH] wireshark: security bump to version 2.0.2 Gustavo Zacarias
2016-02-27 15:28 ` 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=20160227162806.47925dcc@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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