Skip to main content
VulnerabilityPublished Updated

CVE-2022-1348: logrotate · Incorrect Permissions

Affects logrotateSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium : upgrade to 3.20.0 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.6% chance of exploitation in 30 days – higher than 76% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.20.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 May 2022

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade the Debian logrotate package to 3.20.0.

Affected software

ProductAffectedFixed in
Debianlogrotatepkg:deb/logrotateOther threatsAffected
  • <3.20.0
Fixed in
  • 3.20.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, European organizations should first ensure that all systems running logrotate are updated to version 3.20.0 or later, where the issue is resolved by correcting the permissions on the state file. If immediate upgrading is not feasible, administrators should manually verify and correct the permissions of the logrotate state file to restrict access to privileged users only (e.g., root). Implementing file system access controls such as SELinux or AppArmor policies to restrict unprivileged user access to the logrotate state file can provide additional protection. Monitoring disk usage and setting alerts for abnormal log file growth can help detect exploitation attempts early. Additionally, restricting unprivileged user access on critical systems and employing least privilege principles reduce the attack surface. Regular auditing of system utilities and their configurations should be part of security hygiene to prevent similar issues.

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.

References

Community reviews

Loading reviews…