Hide Forgot
Description of problem: Rule xccdf_org.ssgproject.content_rule_mount_option_var_tmp_bind tries to check whether mount is binded or not by searching /etc/mtab for bind option. For some time now, /etc/mtab reflects kernel view - that there is no difference between binded and not binded - thus bind is not mentioned there. Version-Release number of selected component (if applicable): scap-security-guide-0.1.30-3.el7.noarch How reproducible: reliably Steps to Reproduce: 1. 2. 3. Actual results: rule check contents of /etc/mtab Expected results: rule utilize different approach (comparison of inodes?) Additional info:
Proposed fix upstream: https://github.com/OpenSCAP/scap-security-guide/pull/1740
Verified for version scap-security-guide-0.1.33-5.el7.noarch Verification performed using SSG Test Suite https://github.com/OpenSCAP/scap-security-guide/commits/ba02d65857f02c824e18878e238ff8a9aea657c1 OLD: scap-security-guide-0.1.30-3.el7.noarch INFO - xccdf_org.ssgproject.content_rule_mount_option_var_tmp_bind INFO - Script binded.pass.sh using profile xccdf_org.ssgproject.content_profile_C2S ERROR - Scan has exited with return code 2, instead of expected 0 during stage initial ERROR - Rule result should have been "pass", but is "fail"! WARNING - Skipping to the next scenario INFO - Script separate.fail.sh using profile xccdf_org.ssgproject.content_profile_C2S ERROR - Scan has exited with return code 2, instead of expected 0 during stage remediation ERROR - Rule result should have been "fixed", but is "fail"! INFO - All snapshots reverted successfully NEW: INFO - xccdf_org.ssgproject.content_rule_mount_option_var_tmp_bind INFO - Script binded.pass.sh using profile xccdf_org.ssgproject.content_profile_C2S INFO - Script separate.fail.sh using profile xccdf_org.ssgproject.content_profile_C2S ERROR - Scan has exited with return code 2, instead of expected 0 during stage remediation ERROR - Rule result should have been "fixed", but is "fail, error"! INFO - All snapshots reverted successfully Note: Important part is binded.pass.sh scenario in this case - error is due to discrepancy between how scan and remediation are performed. See Bug 1463829
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, 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-2017:2064