From ${URL} : systemd-journald from systemd v213 started creating world readable journals, allowing local users to read sensitive system log entries. While spotted by our users in https://bugzilla.suse.com/show_bug.cgi?id=972612 the problem was present and fixed in upstream systemd git... Introduced by this commit in v213: https://github.com/systemd/systemd/commit/a606871da508995f5ede113a8fc6538afd98966c Fixed for volatile journals was done by this commit in v214: https://github.com/systemd/systemd/commit/176f2acf8dee45fee832fd2ab07243f63783a238 Fixed for the current persistent journal by this commit in v229: https://github.com/systemd/systemd/commit/afae249efa4774c6676738ac5de6aeb4daf4889f @maintainer(s): since the fixed package is already in the tree, please let us know if it is ready for the stabilization or not.
The summary from the oss-security list is a bit misleading. This issue only affects users that had been running systmed-213 at some point. The tmpfiles fragment in that version would recursively set the world access bits. This was fixed in systemd-214 by not setting permissions recursively in the tmpfiles fragment. Another tmpfiles change in 229 partially addresses the issue of permissions on archived journal files. Given the limited scope and minor severity of this issue, I see no real reason to stabilize 229. If you want to release a GLSA for this, you can tell users to run the following to fix the permissions on existing files. chmod -R o-rwx /var/log/journal/{machineid}/* {machineid} is a UUID that is unique to each system.
Based on comment #1 we are waiting that >=sys-apps/systemd-229 goes stable. Bug 595476 is the current bug to handle that.
GLSA Vote: No
