public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siddhesh at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/30843] potential use-after-free in getcanonname (CVE-2023-4806)
Date: Thu, 14 Sep 2023 09:56:29 +0000 [thread overview]
Message-ID: <bug-30843-131-iNyFP0AUX1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30843-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30843
--- Comment #3 from Siddhesh Poyarekar <siddhesh at sourceware dot org> ---
(In reply to Xi Ruoyao from comment #2)
> nss_wins from samba implements _nss_wins_gethostbyname_r and
> _nss_wins_gethostbyname2_r, but not _nss_wins_gethostbyname3_r. Is it
> problematic?
I should probably update the description; presence of a
_nss_wins_getcanonname_r hook is also necessary (that's the hook that
dereferences the freed memory after all) to trigger the user-after-free. The
nss wins plugin in samba doesn't seem to have that hook.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-09-14 9:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 15:32 [Bug network/30843] New: " siddhesh at sourceware dot org
2023-09-12 15:32 ` [Bug network/30843] " siddhesh at sourceware dot org
2023-09-13 3:18 ` sam at gentoo dot org
2023-09-14 6:45 ` xry111 at xry111 dot site
2023-09-14 9:56 ` siddhesh at sourceware dot org [this message]
2023-09-14 10:02 ` xry111 at xry111 dot site
2023-09-15 18:38 ` cvs-commit at gcc dot gnu.org
2023-09-15 19:19 ` cvs-commit at gcc dot gnu.org
2023-09-15 20:53 ` cvs-commit at gcc dot gnu.org
2023-09-15 22:25 ` cvs-commit at gcc dot gnu.org
2023-09-15 23:48 ` cvs-commit at gcc dot gnu.org
2023-09-16 0:50 ` cvs-commit at gcc dot gnu.org
2023-09-16 0:50 ` siddhesh at sourceware dot org
2023-09-25 0:40 ` romain.geissler at amadeus dot com
2023-09-25 5:55 ` fweimer at redhat dot com
2023-09-26 11:40 ` cvs-commit at gcc dot gnu.org
2023-09-26 22:52 ` cvs-commit at gcc dot gnu.org
2023-09-26 22:53 ` cvs-commit at gcc dot gnu.org
2023-09-26 22:54 ` cvs-commit at gcc dot gnu.org
2023-09-26 22:54 ` cvs-commit at gcc dot gnu.org
2023-09-26 22:54 ` cvs-commit at gcc dot gnu.org
2023-12-11 16:29 ` m.novosyolov at rosalinux dot ru
2023-12-11 16:37 ` 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-30843-131-iNyFP0AUX1@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).