From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] glibc: security bump to the latest commit on 2.26 branch
Date: Thu, 8 Feb 2018 23:22:42 +0100 [thread overview]
Message-ID: <20180208232242.2882a9dd@windsurf.lan> (raw)
In-Reply-To: <20180206153032.903-1-peter@korsgaard.com>
Hello,
On Tue, 6 Feb 2018 16:30:32 +0100, Peter Korsgaard wrote:
> Fixes the following security issues according to NEWS:
>
> CVE-2017-1000408: Incorrect array size computation in _dl_init_paths leads
> to the allocation of too much memory. (This is not a security bug per se,
> it is mentioned here only because of the CVE assignment.) Reported by
> Qualys.
>
> CVE-2017-1000409: Buffer overflow in _dl_init_paths due to miscomputation of
> the number of search path components. (This is not a security vulnerability
> per se because no trust boundary is crossed if the fix for CVE-2017-1000366
> has been applied, but it is mentioned here only because of the CVE
> assignment.) Reported by Qualys.
>
> CVE-2017-16997: Incorrect handling of RPATH or RUNPATH containing $ORIGIN
> for AT_SECURE or SUID binaries could be used to load libraries from the
> current directory.
>
> CVE-2018-1000001: Buffer underflow in realpath function when getcwd function
> succeeds without returning an absolute path due to unexpected behaviour of
> the Linux kernel getcwd syscall. Reported by halfdog.
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> package/glibc/glibc.hash | 2 +-
> package/glibc/glibc.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-02-08 22:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 15:30 [Buildroot] [PATCH] glibc: security bump to the latest commit on 2.26 branch Peter Korsgaard
2018-02-08 22:22 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-15 23:01 Peter Korsgaard
2018-02-18 20:56 ` 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=20180208232242.2882a9dd@windsurf.lan \
--to=thomas.petazzoni@bootlin.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