[Bug 1059592] Re: Message and memory corruption in rsyslog
Dave Gilbert
ubuntu at treblig.org
Sun Oct 7 16:11:50 UTC 2012
Triaged: since the reporter points to the upstream bug/fix
High: Corrupted log messages are going to confuse lots of people and make debugging other things harder
As a precaution I marked as security; memory corruptions in rsyslog
can't be good
** This bug has been flagged as a security vulnerability
** Changed in: rsyslog (Ubuntu)
Importance: Undecided => High
** Changed in: rsyslog (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1059592
Title:
Message and memory corruption in rsyslog
Status in “rsyslog” package in Ubuntu:
Triaged
Bug description:
When using the RFC5424 format, I've seen a number of corruptions in
the messages (missing messages and unprintable characters). I've also
had rsyslog crash out with "*** glibc detected *** rsyslogd: corrupted
double-linked list: ... ***". The message corruptions match this
upstream bug - http://bugzilla.adiscon.com/show_bug.cgi?id=296
Based on the bug fixes to rsyslog between 5.8.6 and 5.10.0, it appears
that there have been various race conditions and memory corruption
issues that have since been fixed (5.8.6 is now nearly a year old).
In addition, rsyslog has some errors in the RFC5424 format that would
also be fixed by an update to 5.10.0 (like the nil value for PID and
the hostname in "last message repeated X times")
System information:
Ubuntu 12.04 LTS
rsyslog 5.8.6-1ubuntu8
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1059592/+subscriptions
More information about the foundations-bugs
mailing list