Incoming frame larger than log_msg_size() about syslog-ng

[bazsi]

If the log-msg-size() is otherwise set to a larger value (or unset in which case it is 8192 by default), this is probably fixed by this patch (on 3.6, but this was actually backported to earlier versions too):

commit a6958ac
Author: Balazs Scheidler [email protected]
Date: Sat Nov 2 20:19:12 2013 +0100

LogProtoServer: fixed a use-after-free after reload

self->options is a borrowed memory area, managed by the owning driver
that constructed the given LogProtoServer instance. During reload however,
the driver object itself is freed, while the LogProtoServer instance
is kept alive, thereby causing the options pointer to point into the
void.

The solution is to update the options pointer whenever the owner is changed,
chaining into a similar solution in the LogReader code which does exactly
that.

Signed-off-by: Balazs Scheidler <[email protected]>

[bazsi]

closing this as I think this is already fixed.

[sb-relaxt-at]

I have been the original reporter at balabit's forum. The issue indeed seems to be solved after upgrading to 3.4.7 (which should include the named fix). Thanks a lot :-)

[bazsi]

Thanks for the feedback. It is rare to get this information but is important to know that things went smoothly.

Thanks again.