RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1939295 - /var/lib/chrony permissions triggering enterprise security scanners
Summary: /var/lib/chrony permissions triggering enterprise security scanners
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: chrony
Version: CentOS Stream
Hardware: All
OS: Linux
medium
low
Target Milestone: rc
: ---
Assignee: Miroslav Lichvar
QA Contact: Ondrej Mejzlik
Prerana Sharma
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-16 00:21 UTC by peter.clark
Modified: 2021-11-10 09:31 UTC (History)
4 users (show)

Fixed In Version: chrony-4.1-1.el8
Doc Type: Bug Fix
Doc Text:
.Permissions of the `/var/lib/chrony` have changed Previously, enterprise security scanners would flag the `/var/lib/chrony` directory for having world-readable and executable permissions. With this update, the permissions of the `/var/lib/chrony` directory have changed to limit access only to the root and chrony users.
Clone Of:
Environment:
Last Closed: 2021-11-09 19:51:57 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:4462 0 None None None 2021-11-09 19:52:05 UTC

Description peter.clark 2021-03-16 00:21:04 UTC
Description of problem:

Enterprise security scanners have been flagging home directories with permissions looser than 750.   The package-owned directory /var/lib/chrony is mode 755 and only contains the drift file, presumably only needed by chronyd

This appears to have been fixed on Fedora 33


Version-Release number of selected component (if applicable):

chrony-3.5-2.el8.x86_64

How reproducible:


Steps to Reproduce:
1. # ls -ld /var/lib/chrony/
drwxr-xr-x. 2 chrony chrony 19 Mar 15 19:30 /var/lib/chrony/
2. Run an enterprise security scanner against a CentOS Stream 8 system
3. Verify that /var/lib/chrony is flagged as an insecure home directory

Actual results:

/var/lib/chrony is world-readable and executable


Expected results:

/var/lib/chrony is mode 750

Additional info:

Comment 1 Miroslav Lichvar 2021-03-16 09:35:53 UTC
This should be fixed with rebase to 4.0, which can save to that directory more sensitive files, like NTS keys and cookies.

Comment 10 errata-xmlrpc 2021-11-09 19:51:57 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (chrony bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:4462


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