Bug 2132775

Summary:	avahi package has incorrect owner:group defined in payload for /var/run/avahi-daemon
Product:	Red Hat Enterprise Linux 8	Reporter:	Neil Garrett <ngarrett>
Component:	avahi	Assignee:	Michal Sekletar <msekleta>
Status:	CLOSED MIGRATED	QA Contact:	qe-baseos-daemons
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.6	Keywords:	MigratedToJIRA
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2132779 (view as bug list)		Environment:
Last Closed:	2023-09-20 19:22:50 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:
Bug Depends On:
Bug Blocks:	2132779

Description Neil Garrett 2022-10-06 15:54:51 UTC

Description of problem:
When installing the avahi rpm, the provided /var/run/avahi-daemon directory has root:root ownership as seen in 'rpm -qlv | grep avahi' output. Once the service is started, ownership is changed to avahi:avahi. This causes a CAT I STIG security finding.

Version-Release number of selected component (if applicable):
avahi-0.7-20.el8.x86_64


How reproducible:
Every time

Steps to Reproduce:
1. dnf install avahi
2. "rpm -qlv avahi | grep 'var/run/avahi-daemon'" and note ownership
3. systemctl start avahi-daemon
4. "ls -ld /var/run/avahi-daemon" and note difference in ownership

Actual results:
Ownership in provided /var/run/avahi-daemon differ from /var/run/avahi-daemon after starting the service

Expected results:
Ownership in provided /var/run/avahi-daemon match the same after starting the service

Additional info:
The same or similar issue was previously reported in RHEL 7 but was designated 'wontfix'. Bug 1770402. I could not find this reported in RHEL 8, but hopefully I did not miss something if it has been.

Comment 2 RHEL Program Management 2023-09-20 19:17:48 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 3 RHEL Program Management 2023-09-20 19:22:50 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.