From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2, 1/1] package/bind: security bump to version 9.16.44
Date: Thu, 28 Sep 2023 11:26:35 +0200 [thread overview]
Message-ID: <874jjey7g4.fsf@48ers.dk> (raw)
In-Reply-To: <20230927204329.626845-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Wed, 27 Sep 2023 22:43:29 +0200")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> Fix CVE-2023-3341: The code that processes control channel messages sent
> to `named` calls certain functions recursively during packet parsing.
> Recursion depth is only limited by the maximum accepted packet size;
> depending on the environment, this may cause the packet-parsing code to
> run out of available stack memory, causing `named` to terminate
> unexpectedly. Since each incoming control channel message is fully
> parsed before its contents are authenticated, exploiting this flaw does
> not require the attacker to hold a valid RNDC key; only network access
> to the control channel's configured TCP port is necessary. This issue
> affects BIND 9 versions 9.2.0 through 9.16.43, 9.18.0 through 9.18.18,
> 9.19.0 through 9.19.16, 9.9.3-S1 through 9.16.43-S1, and 9.18.0-S1
> through 9.18.18-S1.
> https://ftp.isc.org/isc/bind9/9.16.44/CHANGES
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> Changes v1 -> v2:
> - fix tarball hash
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-09-28 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 20:43 [Buildroot] [PATCH v2, 1/1] package/bind: security bump to version 9.16.44 Fabrice Fontaine
2023-09-28 9:26 ` Peter Korsgaard [this message]
2023-09-30 10:27 ` 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=874jjey7g4.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
/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.