# CVE-2022-1348: Denial of service in logrotate

> An unprivileged user can lock the logrotate state file due to world-readable permissions, preventing log rotation and causing denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 May 2022
- **Updated:** 9 Jun 2025
- **Also known as:** ALPINE-CVE-2022-1348, ALSA-2022:8393, AZL-9845, DEBIAN-CVE-2022-1348, GHSA-4c4j-w8hm-rjgv, MGASA-2022-0217, OESA-2022-1724, RHSA-2022:8393, RLSA-2022:8393, SUSE-SU-2022:2396-1, UBUNTU-CVE-2022-1348, USN-5447-1, openSUSE-SU-2024:12108-1

## What is CVE-2022-1348?

CVE-2022-1348 is a medium-severity denial of service vulnerability in Fedoraproject Fedora, published on 25 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in logrotate in how the state file is created. The state file is used to prevent parallel executions of multiple instances of logrotate by acquiring and releasing a file lock. When the state file does not exist, it is created with world-readable permission, allowing an unprivileged user to lock the state file, stopping any rotation. This flaw affects logrotate versions before 3.20.0.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2022-1348?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `logrotate` | AlmaLinux:9 | All versions | 3.18.0-7.el9 |
| `logrotate` | Red Hat:enterprise_linux:9::baseos | All versions | 0:3.18.0-7.el9 |
| `logrotate-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:3.18.0-7.el9 |
| `logrotate-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:3.18.0-7.el9 |
| `logrotate` | Rocky Linux:9 | All versions | 0:3.18.0-7.el9 |
| `logrotate` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 3.18.1-150400.3.7.1 |
| `logrotate` | openSUSE:Leap 15.4 | All versions | 3.18.1-150400.3.7.1 |
| `logrotate` | openSUSE:Tumbleweed | All versions | 3.20.1-1.1 |

Products: Fedoraproject Fedora, Logrotate Project Logrotate.

## How do I fix CVE-2022-1348?

Upgrade to a fixed version.

## Is CVE-2022-1348 being exploited?

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

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1348 and fix it if it is affected.

What it is: CVE-2022-1348 is a medium-severity denial of service vulnerability in Fedoraproject Fedora, published on 25 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1348 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. 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-2022-1348/ (Markdown: https://insights.sbomify.com/CVE-2022-1348/index.md)
```

## Sources

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

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