CVE-2011-1018: Input Validation

Published 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] 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

Other sources

logwatch.pl in Logwatch 7.3.6 allows remote attackers to execute arbitrary commands via shell metacharacters in a log file name, as demonstrated via a crafted username to a Samba server.

MITRE

Affected Software

1 affected component
LogWatch LogWatch=7.3.6

Event History

Feb 24, 2011
Data Sourced
via Red Hat·06:52 PM
DescriptionSeverityAffected Software
Feb 25, 2011
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

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.

3

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

CVE-2011-1018 specifically affects Logwatch version 7.3.6.

4

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.

5

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203