Bug 1404362

Summary:	/etc/mtab searched for bind mounts
Product:	Red Hat Enterprise Linux 7	Reporter:	Marek Haicman <mhaicman>
Component:	scap-security-guide	Assignee:	Watson Yuuma Sato <wsato>
Status:	CLOSED ERRATA	QA Contact:	Marek Haicman <mhaicman>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	mhaicman, mpreisle, openscap-maint
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	scap-security-guide-0.1.32-1.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 12:24:43 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 Marek Haicman 2016-12-13 16:31:51 UTC

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:

Comment 2 Watson Yuuma Sato 2017-03-13 09:07:05 UTC

Proposed fix upstream: https://github.com/OpenSCAP/scap-security-guide/pull/1740

Comment 6 Marek Haicman 2017-06-21 20:26:52 UTC

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

Comment 7 errata-xmlrpc 2017-08-01 12:24:43 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, 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