See how logwatch compares to other vendors in security performance
A security flaw was found in the way logwatch, a log file analysis program, pre-processed log files, containing certain special characters in their names. A remote attacker could use this flaw to execute arbitrary code with the privileges of the privileged system user (root) by creating a specially-crafted log file, subsequently analyzed by the logwatch script.
Upstream bug report: [1] http://sourceforge.net/tracker/?func=detail&aid=3184223&groupid=312875&atid=1316824
Related patch: [2] http://logwatch.svn.sourceforge.net/viewvc/logwatch?view=revision&revision=26
Other references: [3] http://sourceforge.net/mailarchive/forum.php?threadname=4D604843.7040303%40mblmail.net&forumname=logwatch-devel
A security flaw was found in the way logwatch, a log file analysis program, pre-processed log files, containing certain special characters in their names. A remote attacker could use this flaw to execute arbitrary code with the privileges of the privileged system user (root) by creating a specially-crafted log file, subsequently analyzed by the logwatch script.
Upstream bug report: [1] http://sourceforge.net/tracker/?func=detail&aid=3184223&groupid=312875&atid=1316824
Related patch: [2] http://logwatch.svn.sourceforge.net/viewvc/logwatch?view=revision&revision=26
Other references: [3] http://sourceforge.net/mailarchive/forum.php?threadname=4D604843.7040303%40mblmail.net&forumname=logwatch-devel
The secure script in LogWatch before 2.6-2 allows attackers to prevent LogWatch from detecting malicious activity via certain strings in the secure file that are later used as part of a regular expression, which causes the parser to crash, aka "logwatch log processing regular expression DoS."
LogWatch 2.5 allows local users to gain root privileges via a symlink attack, a different vulnerability than CVE-2002-0162.
LogWatch before 2.5 allows local users to execute arbitrary code via a symlink attack on the logwatch temporary directory.