From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Thomas Perale <thomas.perale@mind.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [2025.02.x, PATCH 3/3] package/wireshark: security bump to v4.2.14
Date: Fri, 27 Mar 2026 11:02:21 +0100 [thread overview]
Message-ID: <20260327100221.45925-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260316113716.208738-3-thomas.perale@mind.be>
In reply of:
> For more information on the version bump, see:
>
> - https://www.wireshark.org/docs/relnotes/wireshark-4.2.14.html
>
> Fixes the following vulnerability:
>
> - CVE-2025-11626:
> MONGO dissector infinite loop in Wireshark 4.4.0 to 4.4.9 and 4.2.0 to
> 4.2.13 allows denial of service
>
> For more information, see:
> - https://www.cve.org/CVERecord?id=CVE-2025-11626
>
> Signed-off-by: Thomas Perale <thomas.perale@mind.be>
Applied to 2025.02.x. Thanks
> ---
> package/wireshark/wireshark.hash | 6 +++---
> package/wireshark/wireshark.mk | 2 +-
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/package/wireshark/wireshark.hash b/package/wireshark/wireshark.hash
> index f1f2f58442..521fea662c 100644
> --- a/package/wireshark/wireshark.hash
> +++ b/package/wireshark/wireshark.hash
> @@ -1,6 +1,6 @@
> -# From https://www.wireshark.org/download/src/all-versions/SIGNATURES-4.2.13.txt
> -sha1 e5a08396a98d5dfba4078c66677aacd50d47ec90 wireshark-4.2.13.tar.xz
> -sha256 2454aa650276264d23aca28e1b62eb5d4bd12b64aa261d38c06b33f97b8fa3dd wireshark-4.2.13.tar.xz
> +# From https://www.wireshark.org/download/src/all-versions/SIGNATURES-4.2.14.txt
> +sha1 e972062abc0d15db34c3a0186c39511efb29ea34 wireshark-4.2.14.tar.xz
> +sha256 098177f021951638f5bdca5b01f284c14fcc3f6c804f7aa2ca00fdcb99c7a166 wireshark-4.2.14.tar.xz
>
> # Locally calculated
> sha256 edaef632cbb643e4e7a221717a6c441a4c1a7c918e6e4d56debc3d8739b233f6 COPYING
> diff --git a/package/wireshark/wireshark.mk b/package/wireshark/wireshark.mk
> index bd81224ae7..3a92c4cfa4 100644
> --- a/package/wireshark/wireshark.mk
> +++ b/package/wireshark/wireshark.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -WIRESHARK_VERSION = 4.2.13
> +WIRESHARK_VERSION = 4.2.14
> WIRESHARK_SOURCE = wireshark-$(WIRESHARK_VERSION).tar.xz
> WIRESHARK_SITE = https://www.wireshark.org/download/src/all-versions
> WIRESHARK_LICENSE = wireshark license
> --
> 2.53.0
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-03-27 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 11:37 [Buildroot] [2025.02.x, PATCH 1/3] package/mongoose: patch CVE-2025-65502 Thomas Perale via buildroot
2026-03-16 11:37 ` [Buildroot] [2025.02.x, PATCH 2/3] package/libheif: patch CVE-2025-68431 Thomas Perale via buildroot
2026-03-27 10:02 ` Thomas Perale via buildroot
2026-03-16 11:37 ` [Buildroot] [2025.02.x, PATCH 3/3] package/wireshark: security bump to v4.2.14 Thomas Perale via buildroot
2026-03-27 10:02 ` Thomas Perale via buildroot [this message]
2026-03-27 10:02 ` [Buildroot] [2025.02.x, PATCH 1/3] package/mongoose: patch CVE-2025-65502 Thomas Perale via buildroot
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=20260327100221.45925-1-thomas.perale@mind.be \
--to=buildroot@buildroot.org \
--cc=thomas.perale@mind.be \
/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