public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crushor at hotmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nscd/27462] double-free in nscd (CVE-2021-27645)
Date: Sat, 27 Feb 2021 06:02:40 +0000 [thread overview]
Message-ID: <bug-27462-131-zf9D1Hrcai@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27462-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27462
--- Comment #3 from crushor at hotmail dot com ---
(In reply to dj@redhat.com from comment #2)
> You're reading the documentation for realloc, not xrealloc. xrealloc cannot
> return NULL.
sure, you are right.
by the way , another question is: why redhat assigns a 7.5 score for it ?
AC is network, and AI is high.
nscd provides caching for accesses of the passwd(5), group(5),
hosts(5) services(5) and netgroup databases through standard libc
interfaces, such as getpwnam(3), getpwuid(3), getgrnam(3),
getgrgid(3), gethostbyname(3), and others.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-27 6:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 7:46 [Bug nscd/27462] New: double-free in nscd siddhesh at sourceware dot org
2021-02-24 15:52 ` [Bug nscd/27462] double-free in nscd (CVE-2021-27645) siddhesh at sourceware dot org
2021-02-24 19:16 ` sam at gentoo dot org
2021-02-24 20:22 ` carnil at debian dot org
2021-02-25 4:28 ` siddhesh at sourceware dot org
2021-02-25 4:30 ` siddhesh at sourceware dot org
2021-02-27 5:08 ` crushor at hotmail dot com
2021-02-27 5:43 ` dj at redhat dot com
2021-02-27 6:02 ` crushor at hotmail dot com [this message]
2021-03-01 2:22 ` siddhesh at sourceware dot org
2021-03-03 5:02 ` siddhesh at sourceware dot 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-27462-131-zf9D1Hrcai@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).