All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/wireshark: security bump to version 4.0.6
Date: Tue, 27 Jun 2023 08:16:08 +0200	[thread overview]
Message-ID: <87edlxxwev.fsf@48ers.dk> (raw)
In-Reply-To: <20230626065231.1967152-1-peter@korsgaard.com> (Peter Korsgaard's message of "Mon, 26 Jun 2023 08:52:31 +0200")

>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:

 > Fixes the following security issues:
 > - CVE-2023-1992: The RPC over RDMA dissector could crash
 >   https://www.wireshark.org/security/wnpa-sec-2023-09.html

 > - CVE-2023-1993: The LISP dissector could go into a large loop
 >   https://www.wireshark.org/security/wnpa-sec-2023-10.html

 > - CVE-2023-1994: The GQUIC dissector could crash
 >   https://www.wireshark.org/security/wnpa-sec-2023-11.html

 > - CVE-2023-2855: The Candump log file parser could crash
 >   https://www.wireshark.org/security/wnpa-sec-2023-12.html

 > - CVE-2023-2857: The BLF file parser could crash
 >   https://www.wireshark.org/security/wnpa-sec-2023-13.html

 > - The GDSDB dissector could go into an infinite loop
 >   https://www.wireshark.org/security/wnpa-sec-2023-14.html

 > - CVE-2023-2858: The NetScaler file parser could crash
 >   https://www.wireshark.org/security/wnpa-sec-2023-15.html

 > - CVE-2023-2856: The VMS TCPIPtrace file parser could crash
 >   https://www.wireshark.org/security/wnpa-sec-2023-16.html

 > - CVE-2023-2854: The BLF file parser could crash
 >   https://www.wireshark.org/security/wnpa-sec-2023-17.html

 > - CVE-2023-0666: The RTPS dissector could crash
 >   https://www.wireshark.org/security/wnpa-sec-2023-18.html

 > - CVE-2023-0668: The IEEE C37.118 Synchrophasor dissector could crash
 >   https://www.wireshark.org/security/wnpa-sec-2023-19.html

 > - The XRA dissector could go into an infinite loo
 >   https://www.wireshark.org/security/wnpa-sec-2023-20.html

 > The SIGNATURES-4.0.6.txt file seems to be corrupted, so instead refer to the
 > announcement mail.  Issue reported upstream:

 > https://gitlab.com/wireshark/wireshark/-/issues/19169

Upstream fixed that issue by restarting their reverse proxy, so I
changed it back to refer to the SIGNATURES file and committed, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-06-27  6:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26  6:52 [Buildroot] [PATCH] package/wireshark: security bump to version 4.0.6 Peter Korsgaard
2023-06-27  6:16 ` Peter Korsgaard [this message]
2023-07-16  9: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=87edlxxwev.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.