public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "thomas.jarosch at intra2net dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/13336] New: Add missing buffer termination in readlinkat() unit test
Date: Mon, 24 Oct 2011 14:56:00 -0000	[thread overview]
Message-ID: <bug-13336-131@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=13336

             Bug #: 13336
           Summary: Add missing buffer termination in readlinkat() unit
                    test
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper.fsp@gmail.com
        ReportedBy: thomas.jarosch@intra2net.com
    Classification: Unclassified


Created attachment 6028
  --> http://sourceware.org/bugzilla/attachment.cgi?id=6028
Patch to fix the issue

>From the patch:

Add missing buffer termination in readlinkat() unit test

readlinkat() never zero terminates the buffer.

Also make sure we don't overflow the buffer if readlinkat() returns
the full size of the buffer by reducing the supplied size.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2011-10-24 14:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-24 14:56 thomas.jarosch at intra2net dot com [this message]
2011-10-29 16:12 ` [Bug libc/13336] " drepper.fsp at gmail dot com
2014-06-27 11:49 ` 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-13336-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --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: 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).