From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2, 1/1] package/nbd: security bump to version 3.24
Date: Sun, 27 Mar 2022 22:28:58 +0200 [thread overview]
Message-ID: <87r16nb0mt.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220313113333.1125977-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Sun, 13 Mar 2022 12:33:33 +0100")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> Fix CVE-2022-26495: In nbd-server in nbd before 3.24, there is an
> integer overflow with a resultant heap-based buffer overflow. A value of
> 0xffffffff in the name length field will cause a zero-sized buffer to be
> allocated for the name, resulting in a write to a dangling pointer. This
> issue exists for the NBD_OPT_INFO, NBD_OPT_GO, and NBD_OPT_EXPORT_NAME
> messages.
> Fix CVE-2022-26496: In nbd-server in nbd before 3.24, there is a
> stack-based buffer overflow. An attacker can cause a buffer overflow in
> the parsing of the name field by sending a crafted NBD_OPT_INFO or
> NBD_OPT_GO message with an large value as the length of the name.
> https://github.com/NetworkBlockDevice/nbd/compare/nbd-3.21...nbd-3.24
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> Changes v1 -> v2:
> - Tag as a security bump and add CVEs
Committed to 2021.02.x and 2022.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-03-27 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 11:33 [Buildroot] [PATCH v2, 1/1] package/nbd: security bump to version 3.24 Fabrice Fontaine
2022-03-23 20:26 ` Arnout Vandecappelle
2022-03-27 20:28 ` 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=87r16nb0mt.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=yann.morin.1998@free.fr \
/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.