Bug 1821343

Summary: Ansible remediations for mount_option_dev_shm_noexec and openssl_use_strong_entropy not aligned with OVAL
Product: Red Hat Enterprise Linux 8 Reporter: Matus Marhefka <mmarhefk>
Component: scap-security-guideAssignee: Vojtech Polasek <vpolasek>
Status: CLOSED ERRATA QA Contact: Matus Marhefka <mmarhefk>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.2CC: ggasparb, matyc, mhaicman, wsato
Target Milestone: rcKeywords: Triaged
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: scap-security-guide-0.1.50-4.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-04 02:29:53 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 Matus Marhefka 2020-04-06 15:40:40 UTC 
Description of problem:
Ansible remediations for mount_option_dev_shm_noexec and openssl_use_strong_entropy are not aligned with their counterpart OVAL checks. Scan after applying these Ansible remediations produce fail result while scan after Bash remediations produces pass.

For the rule openssl_use_strong_entropy the reason is that Ansible remediation is not including a newline at the end of the produced /etc/profile.d/openssl-rand.sh file which makes its sha256 different than expected by OVAL.


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


How reproducible:
always


Steps to Reproduce:
1. Run Ansible remediations for mount_option_dev_shm_noexec and openssl_use_strong_entropy rules.
2. Scan after applying the Ansible remediations.


Actual results:
The mount_option_dev_shm_noexec and openssl_use_strong_entropy rules are not fixed by Ansible remediations with respect to their OVAL checks.

Expected results:
The mount_option_dev_shm_noexec and openssl_use_strong_entropy rules are fixed by Ansible remediations with respect to their OVAL checks.
Comment 2 Watson Yuuma Sato 2020-05-19 16:10:48 UTC 
The issue with mount_option_dev_shm_noexec should be fixed by:
- https://github.com/ComplianceAsCode/content/pull/5765
- https://github.com/ComplianceAsCode/content/pull/5752
Comment 3 Watson Yuuma Sato 2020-05-19 16:12:44 UTC 
The issue with openssl_use_strong_entropy should be fixed by:
- https://github.com/ComplianceAsCode/content/pull/5577
Comment 4 Matěj Týč 2020-05-28 08:43:08 UTC 
Swithching to Modified, as the patch is part of the 0.1.50 version, which is the current one after the May rebase.
Comment 10 errata-xmlrpc 2020-11-04 02:29:53 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-2020:4626