CVE-2011-1154: The shred_file function in logrotate.c in logrotate 3.7.9 and earlier might allow context-dependent attacke...

Security readout for executives and security teams

Older logrotate versions could treat special characters in a log filename as shell syntax during shredding. In the wrong environment, a crafted hostname or virtual machine name could influence a log filename and lead to command execution. The issue is old, context-dependent, and source evidence does not show active exploitation. Exposure is most plausible on legacy Unix/Linux systems running logrotate 3.7.9 or earlier, especially where log names derive from externally controlled hostnames, VM names, or similar metadata and logrotate uses shredding behavior. Treat this as a legacy hygiene and privileged maintenance-process risk. It deserves prompt remediation where old logrotate packages remain, but urgency depends on whether untrusted names can shape log filenames. Mitigation focus: Inventory systems for logrotate 3.7.9 or earlier.; Apply vendor-supported logrotate updates where available.; Check vendor advisories for the fixed package version..

Prepared

Jun 24, 2026, 13:28 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.