public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kukuk at suse dot de" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/661] New: getgrouplist memory corruption Date: Fri, 14 Jan 2005 13:22:00 -0000 [thread overview] Message-ID: <20050114132151.661.kukuk@suse.de> (raw) If you call getgrouplist with ngroups=0 as argument to find out, how big the buffer needs to be, it will corrupt the stack. The problem is, that internal_getgrouplist will always add the main group at first, without checking for enough space. -- Summary: getgrouplist memory corruption Product: glibc Version: 2.3.4 Status: NEW Severity: critical Priority: P2 Component: libc AssignedTo: gotom at debian dot or dot jp ReportedBy: kukuk at suse dot de CC: glibc-bugs at sources dot redhat dot com http://sources.redhat.com/bugzilla/show_bug.cgi?id=661 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2005-01-14 13:22 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-14 13:22 kukuk at suse dot de [this message] 2005-01-14 13:23 ` [Bug libc/661] " kukuk at suse dot de 2005-03-29 23:40 ` cvs-commit at gcc dot gnu dot org 2005-03-29 23:40 ` cvs-commit at gcc dot gnu dot org 2005-03-29 23:41 ` roland at gnu dot org 2006-08-03 15:25 ` cvs-commit at gcc dot gnu 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=20050114132151.661.kukuk@suse.de \ --to=sourceware-bugzilla@sources.redhat.com \ --cc=glibc-bugs@sources.redhat.com \ /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).