During an out of memory condition syslog.c generated and "out of memory" message
to syslog. This message was supposed to contain the pid, but not only contained
the pid but garbage characters as well. The message it generated is the following:

Aug 20 05:25:07 mdd200 out of memory [617ÿÿÿÿout o]

The bug appears to be at line 158 of the 2.2.5 version of syslog.c which is the
following:

endp = __mempcpy (endp, nump, (nump + sizeof (numbuf)) - nump);

The same source code appears at line 159 of the 2.3.2 version of syslog c which
is the following:

endp = __mempcpy (endp, nump, (nump + sizeof (numbuf)) - nump);

The fix should be the following:

endp = __mempcpy (endp, nump, (numbuf + sizeof (numbuf)) - nump);

The offset into numbuf is not being properly calculated and therefore the wrong
number of bytes are being copied which accounts for the unprintable (garbage
characters).

The company I work for creates software that needs to generate email
notifications when failures occur in our product. The failure we were trying to
report was the out of memory condition. Part of our emails include the syslog
messages file. Due to this bug the email got truncated at the first unprintable
character and we lost the critical, informative data that we include after the
message file content.

Quick attention to fixing this bug ASAP is greatly appreciated.

-- 
           Summary: During out of memory condition syslog.c generates
                    message with unprintable characters
           Product: glibc
           Version: 2.2.5
            Status: NEW
          Severity: critical
          Priority: P2
         Component: libc
        AssignedTo: gotom at debian dot or dot jp
        ReportedBy: egreen at datadomain dot com
                CC: glibc-bugs at sources dot redhat dot com


http://sources.redhat.com/bugzilla/show_bug.cgi?id=365

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.