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 1611119 - (CVE-2018-14348) CVE-2018-14348 libcgroup: cgrulesengd creates log files with insecure permissions
CVE-2018-14348 libcgroup: cgrulesengd creates log files with insecure permiss...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20180725,repor...
: Security
Depends On: 1612122 1611121 1611122
Blocks: 1611124
  Show dependency treegraph
 
Reported: 2018-08-02 02:03 EDT by Sam Fowler
Modified: 2018-08-21 03:35 EDT (History)
21 users (show)

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


Attachments (Terms of Use)

  None (edit)
Description Sam Fowler 2018-08-02 02:03:28 EDT
The cgrulesengd daemon (cgred) in libcgroup through version 0.41 creates log files (/var/log/cgred) with world readable and writable permissions (0o666) due to a reset of the file mode creation mask (umask(0)) in the daemon/cgrulesengd.c:cgre_start_daemon() function.


Upstream Patch:

https://sourceforge.net/p/libcg/libcg/ci/0d88b73d189ea3440ccaab00418d6469f76fa590/
Comment 1 Sam Fowler 2018-08-02 02:04:14 EDT
Created libcgroup tracking bugs for this issue:

Affects: fedora-all [bug 1611121]
Comment 3 Riccardo Schirone 2018-08-03 09:08:31 EDT
Fedora is not affected as it disables the daemon, through the `--disable-daemon` option in the configure script, thus it does not contain the cgrulesengd binary.
Comment 5 Riccardo Schirone 2018-08-03 10:32:34 EDT
In RHEL 7 default options in /etc/sysconfig/cgred, which are used when the daemon is started through systemd, use the syslog facility, thus the log file is not created by the daemon itself, making it not vulnerable to this flaw by default.

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