rsyslog multiple buxfixes released

Hi all,

There has a security issue been identified that can potentially lead to DoS. It is triggered by malformed RFC3164 messages. An abort only happens under very specific environmental trigger factors. Full details can be found in our security advisory here:


We would like to thank the Red Hat security team for finding this issue and working with us to resolve it.

As a consequence, we have updated all currently active versions. Please note that they do not only contain the fix for the security issue mentioned above but also other stability updates. For obvious reasons, updating to these versions is recommended. For details, please see the relevant ChangeLog.

  • v4-stable: 4.6.8
  • v4-beta: 4.7.5
  • v5-stable: 5.8.5
  • v5-devel: 5.9.3
  • v6-beta: 6.1.12
  • v6-devel: 6.3.5

All versions are available right now. If you do not want to update, you should consider applying an update to older versions. The fix is trivial, so it should apply to all vulnerable versions without problems (but we have not checked the myriad of versions out there). The security advisory contains the details.

The Changelogs and Download Links can be found below:

As always, feedback is appreciated.

Best regards,
Florian Riedl

Changelog for 4.6.8 (v4-stable)

Version 4.6.8  [v4-stable] (rgerhards), 2011-09-01

  • bugfix/security: off-by-two bug in legacy syslog parser, CVE-2011-3200
  • bugfix: potential misadressing in property replacer
  • bugfix: memcpy overflow can occur in allowed sender checking if a name is resolved to IPv4-mapped-on-IPv6 address
    Found by Ismail Dönmez at suse
  • bugfix: The NUL-Byte for the syslogtag was not copied in MsgDup (msg.c)
Scroll to top