From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Perale <thomas.perale@mind.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/igmpproxy: add patch for CVE-2025-50681
Date: Thu, 26 Feb 2026 21:10:00 +0100 [thread overview]
Message-ID: <736ac09605c2511121e9dd5b0e071a4c@free.fr> (raw)
In-Reply-To: <20260226080651.19171-1-thomas.perale@mind.be>
On 26/02/2026 09:06, Thomas Perale via buildroot wrote:
> Fixes the following vulnerability:
>
> - CVE-2025-50681:
> igmpproxy 0.4 before commit 2b30c36 allows remote attackers to
> cause a
> denial of service (application crash) via a crafted IGMPv3
> membership
> report packet with a malicious source address. Due to insufficient
> validation in the `recv_igmp()` function in src/igmpproxy.c, an
> invalid group record type can trigger a NULL pointer dereference
> when
> logging the address using `inet_fmtsrc()`. This vulnerability can
> be
> exploited by sending malformed multicast traffic to a host running
> igmpproxy, leading to a crash. igmpproxy is used in various
> embedded
> networking environments and consumer-grade IoT devices (such as
> home
> routers and media gateways) to handle multicast traffic for IPTV
> and
> other streaming services. Affected devices that rely on unpatched
> versions of igmpproxy may be vulnerable to remote denial-of-service
> attacks across a LAN .
>
> For more information, see:
> - https://www.cve.org/CVERecord?id=CVE-2025-50681
> -
> https://github.com/younix/igmpproxy/commit/2b30c36e6ab5b21defb76ec6458ab7687984484c
>
> Signed-off-by: Thomas Perale <thomas.perale@mind.be>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-02-26 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 8:06 [Buildroot] [PATCH] package/igmpproxy: add patch for CVE-2025-50681 Thomas Perale via buildroot
2026-02-26 20:10 ` Julien Olivain via buildroot [this message]
2026-03-06 19:53 ` 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=736ac09605c2511121e9dd5b0e071a4c@free.fr \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--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