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 libc/17079] nss_files mishandles small buffer (CVE-2015-5277)
Date: Mon, 14 Sep 2015 15:40:00 -0000 [thread overview]
Message-ID: <bug-17079-131-COyuOK5C81@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17079-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17079
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|nss_files mishandles small |nss_files mishandles small
|buffer |buffer (CVE-2015-5277)
Alias| |CVE-2015-5277
Flags|security- |security+
--- Comment #4 from Florian Weimer <fweimer at redhat dot com> ---
The description is misleading. This bug can theoretically result in
applications receiving wrong data from NSS, and the data could even be
attacker-controlled, which means that this is a security bug.
Introduced in glibc 2.19, fixed in 2.20. The broken fix which went into glibc
2.19 has been backported to earlier glibc versions by some distributions.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-09-14 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 8:18 [Bug libc/17079] New: nss_files mishandles small buffer schwab@linux-m68k.org
2014-06-23 8:20 ` [Bug libc/17079] " fweimer at redhat dot com
2014-06-23 10:31 ` schwab@linux-m68k.org
2015-09-14 15:40 ` fweimer at redhat dot com [this message]
2015-09-22 11:42 ` [Bug libc/17079] nss_files heap-based buffer overflow with small buffer (CVE-2015-5277) fweimer at redhat dot com
2015-09-22 11:49 ` cvs-commit at gcc dot gnu.org
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-17079-131-COyuOK5C81@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).