public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug nscd/31679] nscd: netgroup cache may terminate daemon on memory allocation failure Date: Thu, 25 Apr 2024 13:52:42 +0000 [thread overview] Message-ID: <bug-31679-131-YP0Suhk1Gm@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31679-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31679 --- Comment #10 from Sourceware Commits <cvs-commit at gcc dot gnu.org> --- The release/2.35/master branch has been updated by Florian Weimer <fw@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=7a5864cac60e06000394128a5a2817b03542f5a3 commit 7a5864cac60e06000394128a5a2817b03542f5a3 Author: Florian Weimer <fweimer@redhat.com> Date: Thu Apr 25 15:01:07 2024 +0200 CVE-2024-33601, CVE-2024-33602: nscd: netgroup: Use two buffers in addgetnetgrentX (bug 31680) This avoids potential memory corruption when the underlying NSS callback function does not use the buffer space to store all strings (e.g., for constant strings). Instead of custom buffer management, two scratch buffers are used. This increases stack usage somewhat. Scratch buffer allocation failure is handled by return -1 (an invalid timeout value) instead of terminating the process. This fixes bug 31679. Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org> (cherry picked from commit c04a21e050d64a1193a6daab872bca2528bda44b) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-04-25 13:52 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-24 8:32 [Bug nscd/31679] New: " fweimer at redhat dot com 2024-04-24 8:32 ` [Bug nscd/31679] " fweimer at redhat dot com 2024-04-24 20:25 ` carlos at redhat dot com 2024-04-24 20:29 ` carlos at redhat dot com 2024-04-24 20:36 ` carlos at redhat dot com 2024-04-24 20:44 ` fweimer at redhat dot com 2024-04-25 13:32 ` cvs-commit at gcc dot gnu.org 2024-04-25 13:35 ` fweimer at redhat dot com 2024-04-25 13:39 ` cvs-commit at gcc dot gnu.org 2024-04-25 13:40 ` cvs-commit at gcc dot gnu.org 2024-04-25 13:42 ` cvs-commit at gcc dot gnu.org 2024-04-25 13:47 ` cvs-commit at gcc dot gnu.org 2024-04-25 13:52 ` cvs-commit at gcc dot gnu.org [this message] 2024-04-25 13:53 ` sam at gentoo dot org 2024-04-25 13:55 ` cvs-commit at gcc dot gnu.org 2024-04-25 14:10 ` cvs-commit at gcc dot gnu.org 2024-04-25 14:12 ` cvs-commit at gcc dot gnu.org 2024-04-25 14:13 ` cvs-commit at gcc dot gnu.org 2024-04-25 21:00 ` carnil at debian 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-31679-131-YP0Suhk1Gm@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).