Source: logrotate Version: 3.17.0-1 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team <t...@security.debian.org> Control: found -1 3.18.0-2 Control: found -1 3.19.0-2
Hi, The following vulnerability was published for logrotate. CVE-2022-1348[0]: | 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. Note that the issue is present as well in Debian even though we have the state file from almost the beginning in /var/lib/logrotate/state, as the /var/lib/logrotate directory has 0755 permissions allowing a user to aquire the lock. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-1348 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1348 [1] https://www.openwall.com/lists/oss-security/2022/05/25/3 [2] https://github.com/logrotate/logrotate/commit/1f76a381e2caa0603ae3dbc51ed0f1aa0d6658b9 (3.20.0) [3] https://github.com/logrotate/logrotate/commit/addbd293242b0b78aa54f054e6c1d249451f137d (3.20.1) Regards, Salvatore
