public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/27389] getaddrinfo in chroot broken by added dlopen block
Date: Tue, 16 Feb 2021 14:50:52 +0000	[thread overview]
Message-ID: <bug-27389-131-Kw0wdVO9Em@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27389-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27389

--- Comment #4 from Florian Weimer <fweimer at redhat dot com> ---
It's CVE-2019-14271:

https://nvd.nist.gov/vuln/detail/CVE-2019-14271

(The Docker fix is likely incomplete depending on nsswitch.conf contents.)

That issue is of no concern once the service is running, it applies to the
construction of the chroot contents from the outside.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-02-16 14:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10  8:19 [Bug network/27389] New: " sjon at hortensius dot net
2021-02-10  8:41 ` [Bug network/27389] " sjon at hortensius dot net
2021-02-16 12:45 ` fweimer at redhat dot com
2021-02-16 14:47 ` hyc at symas dot com
2021-02-16 14:50 ` fweimer at redhat dot com [this message]
2021-02-17 13:37 ` [Bug network/27389] NSS chroot hardening causes regressions in chroot deployments fweimer at redhat dot com
2021-02-17 13:37 ` fweimer at redhat dot com
2021-02-17 14:20 ` stli at linux dot ibm.com
2021-03-04 11:46 ` fweimer at redhat dot com
2021-03-11  8:13 ` crosser at average dot org
2021-09-01  9:25 ` fweimer at redhat dot com

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=bug-27389-131-Kw0wdVO9Em@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).