public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aurelien at aurel32 dot net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug network/28768] Buffer overflow in svcunix_create with long pathnames (CVE-2022-23218) Date: Sat, 15 Jan 2022 15:41:44 +0000 [thread overview] Message-ID: <bug-28768-131-IgdAzBOwOE@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28768-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28768 Aurelien Jarno <aurelien at aurel32 dot net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aurelien at aurel32 dot net -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-01-15 15:41 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-12 9:40 [Bug network/28768] New: Buffer overflow in svcunix_create with long pathnames fweimer at redhat dot com 2022-01-12 9:40 ` [Bug network/28768] " fweimer at redhat dot com 2022-01-14 8:14 ` [Bug network/28768] Buffer overflow in svcunix_create with long pathnames (CVE-2022-23218) siddhesh at sourceware dot org 2022-01-14 21:21 ` sam at gentoo dot org 2022-01-15 15:41 ` aurelien at aurel32 dot net [this message] 2022-01-17 9:09 ` pgowda.cve at gmail dot com 2022-01-17 13:07 ` 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-28768-131-IgdAzBOwOE@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: linkBe 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).