What is CVE-2011-1154?A medium-severity flaw in Logrotate, explained.
CVE-2011-1154 is a medium-severity flaw (CVSS 6.9) in Logrotate from Gentoo, published on 30 March 2011. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.4%. If you run an affected version, plan in the vendor’s fix.
Published 30 March 2011. Record last updated 11 April 2025. We keep this page's data up to date.
What is CVE-2011-1154? In plain terms.
An attacker has to be already on the device without logging in. If it works, the attacker can read data, change data and take it offline.
The shred_file function in logrotate.c in logrotate 3.7.9 and earlier might allow context-dependent attackers to execute arbitrary commands via shell metacharacters in a log filename, as demonstrated by a filename that is automatically constructed on the basis of a hostname or virtual machine name.
What kind of flaw is it?
- CWE-20Improper Input Validation
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAlready on the device
- How hard it is to pull offSome conditions needed
- Login needed firstNo login needed
- What an attacker getsCan read data, change data and take it offline
Severity vector: AV:L/AC:M/Au:N/C:C/I:C/A:C
Is CVE-2011-1154 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.4%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2011-1154 scores 20. Action: Monitor.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2011-1154 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →How do I fix CVE-2011-1154? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
References
43 links- March (opens in a new tab)fedoraproject.org · 2011
- oss-security mailing list post, 7 Mar 2011 (opens in a new tab)openwall.com · 2011
- Show Bug.cgi (opens in a new tab)redhat.com
- English (opens in a new tab)vupen.com · 2011
- April (opens in a new tab)fedoraproject.org · 2011
- oss-security mailing list post, 4 Mar 2011 (opens in a new tab)openwall.com · 2011
Does CVE-2011-1154 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
The shred_file function in logrotate.c in logrotate 3.7.9 and earlier might allow context-dependent attackers to execute arbitrary commands via shell metacha...
- Matched to
- Logrotate on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2011-1154 is a medium-severity flaw in Logrotate from Gentoo, published on 30 March 2011. An attacker has to be already on the device without logging in. If it works, the attacker can read data, change data and take it offline.
It scores 6.9 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2011-1154 is 20 out of 100, which is Low. Its action is "Monitor". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.4%. That can change at any time, which is why we keep watching.
For Logrotate from Gentoo: up to 3.7.9.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.