Opened 2 years ago

Closed 2 years ago

#16579 closed enhancement (fixed)

logrotate-3.20.1

Reported by: Douglas R. Reno Owned by: pierre
Priority: normal Milestone: 11.2
Component: BOOK Version: git
Severity: normal Keywords:
Cc:

Description

New point version

Change History (8)

comment:1 by pierre, 2 years ago

Owner: changed from blfs-book to pierre
Status: newassigned

comment:2 by pierre, 2 years ago

logrotate-3.20.1

drop world-readable permission on state file even when ACLs are enabled (#446)

Last edited 2 years ago by pierre (previous) (diff)

comment:3 by pierre, 2 years ago

logrotate-3.20.0

fix potential DoS from unprivileged users via the state file (CVE-2022-1348)
fix a misleading debug message with copytruncate and rotate 0 (#443)
add support for unsigned time_t (#438)
do not lock state file /dev/null (#433)

From https://nvd.nist.gov/vuln/detail/CVE-2022-1348

CVE-2022-1348 Detail

This vulnerability is currently awaiting analysis.

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.

Last edited 2 years ago by pierre (previous) (diff)

comment:4 by pierre, 2 years ago

Resolution: fixed
Status: assignedclosed

566ab83 Update to xwayland-22.1.2 bb9fc79 Update to cmake-3.23.2 bbb35d2 Update to logrotate-3.20.1 91331cb Update to nspr-4.34 72d2b98 Update to libqalculate-4.2.0 1ba06ad Update to libbytesize-2.7

comment:5 by pierre, 2 years ago

Resolution: fixed
Status: closedreopened

For SA. Reopening...

comment:6 by pierre, 2 years ago

Status: reopenednew

comment:7 by pierre, 2 years ago

Status: newassigned

comment:8 by pierre, 2 years ago

Resolution: fixed
Status: assignedclosed

SA at www repository commit 46b2ed2.

Note: See TracTickets for help on using tickets.