First published: Thu Feb 24 2011(Updated: )
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] <a href="http://sourceforge.net/tracker/?func=detail&aid=3184223&group_id=312875&atid=1316824">http://sourceforge.net/tracker/?func=detail&aid=3184223&group_id=312875&atid=1316824</a> Related patch: [2] <a href="http://logwatch.svn.sourceforge.net/viewvc/logwatch?view=revision&revision=26">http://logwatch.svn.sourceforge.net/viewvc/logwatch?view=revision&revision=26</a> Other references: [3] <a href="http://sourceforge.net/mailarchive/forum.php?thread_name=4D604843.7040303%40mblmail.net&forum_name=logwatch-devel">http://sourceforge.net/mailarchive/forum.php?thread_name=4D604843.7040303%40mblmail.net&forum_name=logwatch-devel</a>
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Swatch | =7.3.6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2011-1018 has been classified as a critical vulnerability due to its potential to allow remote code execution with root privileges.
To fix CVE-2011-1018, upgrade Logwatch to version 7.4 or later, where the vulnerability has been patched.
CVE-2011-1018 specifically affects Logwatch version 7.3.6.
Yes, CVE-2011-1018 can be exploited remotely by an attacker who creates specially crafted log file names.
The potential consequences of CVE-2011-1018 include arbitrary code execution on the affected system, which could lead to full system compromise.