Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2017.02.x] musl: add upstream security fix for CVE-2017-15650
Date: Wed, 25 Oct 2017 09:41:33 +0200	[thread overview]
Message-ID: <8760b365ea.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20171021092515.5812-1-peter@korsgaard.com> (Peter Korsgaard's message of "Sat, 21 Oct 2017 11:25:15 +0200")

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

 > From the upstream announcement:
 > http://www.openwall.com/lists/oss-security/2017/10/19/5

 > Felix Wilhelm has discovered a flaw in the dns response parsing for
 > musl libc 1.1.16 that leads to overflow of a stack-based buffer.
 > Earlier versions are also affected.

 > When an application makes a request via getaddrinfo for both IPv4 and
 > IPv6 results (AF_UNSPEC), an attacker who controls or can spoof the
 > nameservers configured in resolv.conf can reply to both the A and AAAA
 > queries with A results. Since A records are smaller than AAAA records,
 > it's possible to fit more addresses than the precomputed bound, and a
 > buffer overflow occurs.

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

Committed to 2017.02.x, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2017-10-25  7:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-21  9:25 [Buildroot] [PATCH 2017.02.x] musl: add upstream security fix for CVE-2017-15650 Peter Korsgaard
2017-10-21 16:29 ` Peter Korsgaard
2017-10-25  7:41 ` 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=8760b365ea.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