From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] wireshark: security bump to version 2.2.15
Date: Tue, 17 Jul 2018 09:31:06 +0200 [thread overview]
Message-ID: <87y3eal3np.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180604215910.0158d37f@windsurf> (Thomas Petazzoni's message of "Mon, 4 Jun 2018 21:59:10 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> Hello,
> On Sun, 3 Jun 2018 23:31:00 +0200, Peter Korsgaard wrote:
>> Fixes the following security issues:
>>
>> CVE-2018-11362: LDSS dissector crash
>> https://www.wireshark.org/security/wnpa-sec-2018-25.html
>>
>> CVE-2018-11357: Multiple dissectors could consume excessive memory
>> https://www.wireshark.org/security/wnpa-sec-2018-28.html
>>
>> CVE-2018-11356: DNS dissector crash
>> https://www.wireshark.org/security/wnpa-sec-2018-29.html
>>
>> CVE-2018-11360: GSM A DTAP dissector crash
>> https://www.wireshark.org/security/wnpa-sec-2018-30.html
>>
>> CVE-2018-11358: Q.931 dissector crash
>> https://www.wireshark.org/security/wnpa-sec-2018-31.html
>>
>> CVE-2018-11359: Multiple dissectors could crash
>> https://www.wireshark.org/security/wnpa-sec-2018-33.html
>>
>> 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(-)
Committed to 2018.05.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2018-07-17 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-03 21:31 [Buildroot] [PATCH] wireshark: security bump to version 2.2.15 Peter Korsgaard
2018-06-04 19:59 ` Thomas Petazzoni
2018-06-17 15:49 ` Peter Korsgaard
2018-07-17 7:31 ` Peter Korsgaard [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=87y3eal3np.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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