# CVE-2011-1155: Denial of service in n/a

> Attackers can cause log rotation failure by using newline or backslash characters in log filenames, impacting system availability.

- **Severity:** Low 1.9 (`AV:L/AC:M/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Mar 2011
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-1155, GHSA-fcm8-m55c-7v4r

## What is CVE-2011-1155?

CVE-2011-1155 is a low-severity denial of service vulnerability in n/a, published on 30 Mar 2011. 

### Official description

The writeState function in logrotate.c in logrotate 3.7.9 and earlier might allow context-dependent attackers to cause a denial of service (rotation outage) via a (1) \n (newline) or (2) \ (backslash) character in a log filename, as demonstrated by a filename that is automatically constructed on the basis of a hostname or virtual machine name.

Weakness: CWE-399

## Which versions are affected by CVE-2011-1155?

It affects 1 product.


Products: Gentoo Logrotate.

## How do I fix CVE-2011-1155?

Upgrade to a fixed version.

## Is CVE-2011-1155 being exploited?

There is no known exploitation of CVE-2011-1155 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2011-1154](https://insights.sbomify.com/CVE-2011-1154/): Command injection in n/a (medium 6.9)
- [CVE-2011-1548](https://insights.sbomify.com/CVE-2011-1548/): Privilege escalation in n/a (medium 6.3)
- [CVE-2011-1549](https://insights.sbomify.com/CVE-2011-1549/): Privilege escalation in n/a (medium 6.3)
- [CVE-2011-1550](https://insights.sbomify.com/CVE-2011-1550/): Privilege escalation in n/a (medium 6.3)
- [CVE-2011-1098](https://insights.sbomify.com/CVE-2011-1098/): Race condition in n/a (low 1.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-1155 and fix it if it is affected.

What it is: CVE-2011-1155 is a low-severity denial of service vulnerability in n/a, published on 30 Mar 2011. 
Exploitation: There is no known exploitation of CVE-2011-1155 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2011-1155/ (Markdown: https://insights.sbomify.com/CVE-2011-1155/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2011-1155
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-1155
- OSV: https://osv.dev/vulnerability/CVE-2011-1155

---
From sbomify Insights: https://insights.sbomify.com/CVE-2011-1155/
Summaries are generated and may contain mistakes; the official description above is the record.