Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] rpcbind: add upstream security fix for CVE-2017-8779
Date: Wed, 17 May 2017 22:36:31 +0200	[thread overview]
Message-ID: <87tw4j43w0.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170515210124.6657-1-peter@korsgaard.com> (Peter Korsgaard's message of "Mon, 15 May 2017 23:01:24 +0200")

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

 > CVE-2017-8779: rpcbind through 0.2.4, LIBTIRPC through 1.0.1 and 1.0.2-rc
 > through 1.0.2-rc3, and NTIRPC through 1.4.3 do not consider the maximum RPC
 > data size during memory allocation for XDR strings, which allows remote
 > attackers to cause a denial of service (memory consumption with no
 > subsequent free) via a crafted UDP packet to port 111, aka rpcbomb.

 > For more details, see:
 > https://guidovranken.wordpress.com/2017/05/03/rpcbomb-remote-rpcbind-denial-of-service-patches/

 > Backport upstream fix to version 0.2.3 and unconditionally include syslog.h
 > to fix a build issue when RPCBIND_DEBUG is disabled (which it is in
 > Buildroot).

 > Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

Committed to 2017.02.x, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2017-05-17 20:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15 21:01 [Buildroot] [PATCH] rpcbind: add upstream security fix for CVE-2017-8779 Peter Korsgaard
2017-05-16  7:25 ` Thomas Petazzoni
2017-05-17 20:36 ` 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=87tw4j43w0.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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