CVE-2022-1348 is a medium-severity vulnerability affecting logrotate versions prior to 3.20.0, including various Fedora distributions. The flaw lies in how logrotate creates its state file, which is used for locking to prevent parallel executions. When this file is absent, it's created with world-readable permissions, allowing an unprivileged attacker to lock the file and prevent log rotation. The CVSS score of 6.5 indicates a medium severity, with a low attack complexity and requiring low privileges to achieve a high impact on availability (denial of service). There is no impact on confidentiality or integrity. Currently, there is no known active exploitation, publicly available exploit code (Metasploit, Nuclei, ExploitDB), or significant community discussion or media coverage surrounding this vulnerability. It is not listed in the CISA KEV catalog.
| Vendor | Product | Version(s) | CPE |
|---|---|---|---|
>= 3.17.0, < 3.20.0CPE matchmatch criteria | cpe:2.3:a:logrotate_project:logrotate:*:*:*:*:*:*:*:* | ||
35CPE matchmatch criteria | cpe:2.3:o:fedoraproject:fedora:35:*:*:*:*:*:*:* | ||
36CPE matchmatch criteria | cpe:2.3:o:fedoraproject:fedora:36:*:*:*:*:*:*:* |
CVSS version used by this source: 3.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
No social media mentions found for this CVE.
The average CVE in this peer group has 0.0 Twitter, 0.0 Reddit, 0.1 Bluesky, 0.0 Mastodon, and 0.1 GitHub mentions.
No media coverage found for this CVE.
The average CVE in this peer group has 0.0 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.
CVE-2022-1348
Jun 14, 2022logrotate: potential DoS from unprivileged users via the state file
May 25, 2022A 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.
May 10, 2022