A security flaw was found in the way the logrotate utility performed administration of log files, located in group / world writable directories. A local attacker could use this flaw to disclose sensitive information, execute arbitrary code or cause a denial of service, via unintended / unprivileged later modifications of log file directory in question. Different vulnerability than: [1] https://bugzilla.redhat.com/show_bug.cgi?id=680787 , [2] https://bugzilla.redhat.com/show_bug.cgi?id=680789 , [3] https://bugzilla.redhat.com/show_bug.cgi?id=680790 , [4] https://bugzilla.redhat.com/show_bug.cgi?id=680792 , [5] https://bugzilla.redhat.com/show_bug.cgi?id=680795 , [6] https://bugzilla.redhat.com/show_bug.cgi?id=680796 , [7] https://bugzilla.redhat.com/show_bug.cgi?id=680797 , and [8] https://bugzilla.redhat.com/show_bug.cgi?id=680798 .
Created attachment 483400 [details] Adds "su" option This patch adds "su" option variable which can be used to tell logrotate to switch EUID/EGID to specified user/group for rotation of particular log set. We can't use setfsuid/setfsgid because it's Linux specific and logrotate should run also on different posix systems. With this patch, logrotate does not rotate logs in unsafe directories (world-writable directories or group-writable directories where group is not "root"). It shows error message and skip rotation of log files in unsafe directory.