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 2083109

Summary:	issues with xccdf_org.ssgproject.content_rule_sudo_custom_logfile rule and remediation
Product:	Red Hat Enterprise Linux 8	Reporter:	Welterlen Benoit <bwelterl>
Component:	scap-security-guide	Assignee:	Jan Černý <jcerny>
Status:	CLOSED ERRATA	QA Contact:	Milan Lysonek <mlysonek>
Severity:	medium	Docs Contact:	Jan Fiala <jafiala>
Priority:	unspecified
Version:	8.5	CC:	ggasparb, jafiala, jcerny, matyc, mhaicman, mlysonek, wsato
Target Milestone:	rc	Keywords:	AutoVerified, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	scap-security-guide-0.1.63-2.el8	Doc Type:	Bug Fix
Doc Text:	.Remediation of `sudo_custom_logfile` works for custom `sudo` log files Previously, remediation of the SCAP Security Guide rule `xccdf_org.ssgproject.content_sudo_custom_logfile` did not work for custom `sudo` log files with a different path than `/var/log/sudo.log`. With this update, the rule is fixed so that it can properly remediate if the system has a custom `sudo` log file that does not match the expected path.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-11-08 09:40:01 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 Welterlen Benoit 2022-05-09 10:19:27 UTC

Description of problem:

Multiple issues:

- when /etc/sudoers file contains already a line with "Defaults logfile=" but not the default logfile=/var/log/sudo.log, the test fails 
=> then when the remediation is applied and a new line with default value is added:

~~~
Defaults logfile=/var/log/sudofile.log
Defaults logfile=/var/log/sudo.log
~~~

=> and then the test still fails, because only one entry is expected


- The test to check the validity of the line is broken, because "Defaults_fake logfile=/var/log/sudo.log" will pass


Version-Release number of selected component (if applicable):
scap-security-guide-0.1.57-5.el8.noarch

How reproducible:
always

Steps to Reproduce:
1. scap xccdf eval --verbose DEVEL  --verbose-log-file oval.log --rule xccdf_org.ssgproject.content_rule_sudo_custom_logfile --profile xccdf_org.ssgproject.content_profile_cis  --results scan_resultsAfterRemediation.xml --report scan_reportAfterRemediation.html /usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml
2. ansible-playbook -b -k -K --become-user root   --become-method 'sudo' -i localhost, PlaybookToRemediatesudo.yml |& tee PlaybookToRemediate.output
3.

Actual results:
- Fault positive test
- Wrond remediation which leads to fail test

Expected results:
- Good remediation
- Failed test if Defaults_fake is used

Additional info:
Thank you !

Comment 2 Jan Černý 2022-08-05 11:11:03 UTC

A pull request has been opened in upstream: https://github.com/ComplianceAsCode/content/pull/9299

Comment 3 Jan Černý 2022-08-05 13:50:03 UTC

https://github.com/ComplianceAsCode/content/pull/9299 has been merge to upstream

Comment 18 errata-xmlrpc 2022-11-08 09:40:01 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 (scap-security-guide 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-2022:7563