CWE
20
Advisory Published
CVE Published
Updated

CVE-2011-1018: Input Validation

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&amp;aid=3184223&amp;group_id=312875&amp;atid=1316824">http://sourceforge.net/tracker/?func=detail&amp;aid=3184223&amp;group_id=312875&amp;atid=1316824</a> Related patch: [2] <a href="http://logwatch.svn.sourceforge.net/viewvc/logwatch?view=revision&amp;revision=26">http://logwatch.svn.sourceforge.net/viewvc/logwatch?view=revision&amp;revision=26</a> Other references: [3] <a href="http://sourceforge.net/mailarchive/forum.php?thread_name=4D604843.7040303%40mblmail.net&amp;forum_name=logwatch-devel">http://sourceforge.net/mailarchive/forum.php?thread_name=4D604843.7040303%40mblmail.net&amp;forum_name=logwatch-devel</a>

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
Swatch=7.3.6

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2011-1018?

    CVE-2011-1018 has been classified as a critical vulnerability due to its potential to allow remote code execution with root privileges.

  • How do I fix CVE-2011-1018?

    To fix CVE-2011-1018, upgrade Logwatch to version 7.4 or later, where the vulnerability has been patched.

  • What software versions are affected by CVE-2011-1018?

    CVE-2011-1018 specifically affects Logwatch version 7.3.6.

  • Can CVE-2011-1018 be exploited remotely?

    Yes, CVE-2011-1018 can be exploited remotely by an attacker who creates specially crafted log file names.

  • What are the potential consequences of CVE-2011-1018?

    The potential consequences of CVE-2011-1018 include arbitrary code execution on the affected system, which could lead to full system compromise.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203