Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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

Summary:	/var/lib/chrony permissions triggering enterprise security scanners
Product:	Red Hat Enterprise Linux 8	Reporter:	peter.clark
Component:	chrony	Assignee:	Miroslav Lichvar <mlichvar>
Status:	CLOSED ERRATA	QA Contact:	Ondrej Mejzlik <omejzlik>
Severity:	low	Docs Contact:	Prerana Sharma <presharm>
Priority:	medium
Version:	CentOS Stream	CC:	bstinson, carl, jwboyer, omejzlik
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	All
OS:	Linux
Whiteboard:
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.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-09 19:51:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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