rsyslog uses weak permissions for generating log files, which allows local users to obtain sensitive information by reading files in /var/log/cron.
The MITRE CVE dictionary describes this issue as:
Find out more about CVE-2015-3243 from the MITRE CVE dictionary dictionary and NIST NVD.
This issue affects the versions of rsyslog as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Additionally a workaround is available (https://bugzilla.redhat.com/show_bug.cgi?id=1232826#c3).
NOTE: The following CVSS v2 metrics and score provided are preliminary and subject to review.
| Base Score | 2.1 |
|---|---|
| Base Metrics | AV:L/AC:L/Au:N/C:P/I:N/A:N |
| Access Vector | Local |
| Access Complexity | Low |
| Authentication | None |
| Confidentiality Impact | Partial |
| Integrity Impact | None |
| Availability Impact | None |
Find out more about Red Hat support for the Common Vulnerability Scoring System (CVSS).
| Platform | Package | State |
|---|---|---|
| Red Hat Gluster Storage 2.1 | rsyslog | Will not fix |
| Red Hat Enterprise Linux 7 | rsyslog | Will not fix |
| Red Hat Enterprise Linux 6 | rsyslog | Not affected |
| Red Hat Enterprise Linux 5 | rsyslog | Not affected |
Please add:
create 0600 root root
to the /etc/logrotate.d/syslog file, this will ensure the file is created with permissions when logrotate runs. It is also recommended that users manually set the permissions on existing or newly installed log files in order to prevent access by untrusted users.
Vulmon