Bug 1348626 – CVE-2015-8842 systemd: improper use of tmpfiles.d to create persistent journal files

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1348626 - (CVE-2015-8842) CVE-2015-8842 systemd: improper use of tmpfiles.d to create persistent journal files

Summary:	CVE-2015-8842 systemd: improper use of tmpfiles.d to create persistent journa...

Status:	CLOSED NOTABUG

Aliases:	CVE-2015-8842

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=low,public=20160408,reported=2...
Keywords:	Security

Depends On:
Blocks:	1323985
	Show dependency tree / graph

Reported:	2016-06-21 11:43 EDT by Cedric Buissart
Modified:	2016-07-12 07:04 EDT (History)
CC List:	10 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-06-21 12:04:18 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Cedric Buissart 2016-06-21 11:43:12 EDT

tmpfiles.d/systemd.conf in systemd before v230 does not explicitely set ACLs on persistent system.journal. This could allow improper permission set on the file.

seclist report:
http://seclists.org/oss-sec/2016/q2/34

Suse BTS:
https://bugzilla.suse.com/show_bug.cgi?id=972612

Fixed in commit:
https://github.com/systemd/systemd/commit/afae249efa4774c6676738ac5de6aeb4daf4889f

For additional information:
https://github.com/systemd/systemd/issues/1397

Comment 1 Cedric Buissart 2016-06-21 12:01:54 EDT

The persistent journal logging, the feature at fault, is disabled by default : Default journald storage is set to "auto". To run into the bug, the storage value needs to be changed to "persistent" to force journald to create the /var/log/journal folder on its own. 

In RHEL documentation, enabling persistent storage is suggested by simply creating the /var/log/journal directory, which does not trigger the bug :
 ⁠
20.10.5. Enabling Persistent Storage
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/s1-Using_the_Journal.html

Note You need to log in before you can comment on or make changes to this bug.