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 1520493 - open-scap reports an "error" when checking "Set Daemon Umask"
Summary: open-scap reports an "error" when checking "Set Daemon Umask"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: scap-security-guide
Version: 7.3
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Jan Černý
QA Contact: Marek Haicman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-04 15:14 UTC by SHAURYA
Modified: 2021-06-10 13:49 UTC (History)
6 users (show)

Fixed In Version: scap-security-guide-0.1.36-6.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 12:21:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Openscap scan full result (4.43 MB, text/html)
2017-12-04 15:14 UTC, SHAURYA 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0761 0 None None None 2018-04-10 12:21:55 UTC

Description SHAURYA 2017-12-04 15:14:20 UTC 
Created attachment 1362712 [details]
Openscap scan full result

Description of problem:

The "Set Daemon Umask" test says "error" in the oscap report. The "hover text" says that "the checking engine could not complete the evaluation". I can't work out why this is erroring as the /etc/init.d/functions file looks OK to me.


Version-Release number of selected component (if applicable):
using openscap-1.2.10-2


Actual results:

Provides false report for /etc/init.d/functions file.

Expected results:
Should not provide false positive report for a scan.


Additional info:
San results attached
Comment 2 Jan Černý 2017-12-05 16:17:08 UTC 
Thank you for reporting this bug. It's a bug in SCAP Security Guide in rule 'xccdf_org.ssgproject.content_rule_umask_for_daemons'.

I have a patch submitted that fixes this bug  to upstream https://github.com/OpenSCAP/scap-security-guide/pull/2476 .

You can temporarily workaround this issue by manually removing "<external_variable>" elements with id="oval:ssg-var_umask_for_daemons_umask_as_number:var:1" from the datastream.
Comment 3 Marek Haicman 2017-12-05 17:33:51 UTC 
PR merged -> POST state
Comment 9 Marek Haicman 2018-01-15 20:52:56 UTC 
Verified with SSG Test Suite https://github.com/OpenSCAP/scap-security-guide/tree/master/tests
[Please note I had to add rule_umask_for_daemons to C2S profile for SSG Test Suite to consume it, and update scenarios accordingly. It won't work with profile out of the box.]

OLD (scap-security-guide-0.1.33-6.el7.noarch)
INFO - xccdf_org.ssgproject.content_rule_umask_for_daemons
ERROR - Script adequate.pass.sh using profile xccdf_org.ssgproject.content_profile_C2S found issue:
ERROR - Scan has exited with return code 2, instead of expected 0 during stage initial
ERROR - The initial scan failed for rule 'xccdf_org.ssgproject.content_rule_umask_for_daemons'.
INFO - Script comment.fail.sh using profile xccdf_org.ssgproject.content_profile_C2S OK
ERROR - Scan has exited with return code 2, instead of expected 0 during stage remediation
ERROR - The remediation failed for rule 'xccdf_org.ssgproject.content_rule_umask_for_daemons'.
INFO - Script strong_weak.fail.sh using profile xccdf_org.ssgproject.content_profile_C2S OK
ERROR - Scan has exited with return code 2, instead of expected 0 during stage remediation
ERROR - The remediation failed for rule 'xccdf_org.ssgproject.content_rule_umask_for_daemons'.
ERROR - Script super_strong.pass.sh using profile xccdf_org.ssgproject.content_profile_C2S found issue:
ERROR - Scan has exited with return code 2, instead of expected 0 during stage initial
ERROR - The initial scan failed for rule 'xccdf_org.ssgproject.content_rule_umask_for_daemons'.
INFO - Script line_not_there.fail.sh using profile xccdf_org.ssgproject.content_profile_C2S OK
ERROR - Scan has exited with return code 2, instead of expected 0 during stage remediation
ERROR - The remediation failed for rule 'xccdf_org.ssgproject.content_rule_umask_for_daemons'.
INFO - All snapshots reverted successfully


NEW (scap-security-guide-0.1.36-7.el7.noarch)
INFO - xccdf_org.ssgproject.content_rule_umask_for_daemons
INFO - Script adequate.pass.sh using profile xccdf_org.ssgproject.content_profile_C2S OK
INFO - Script comment.fail.sh using profile xccdf_org.ssgproject.content_profile_C2S OK
INFO - Script strong_weak.fail.sh using profile xccdf_org.ssgproject.content_profile_C2S OK
INFO - Script super_strong.pass.sh using profile xccdf_org.ssgproject.content_profile_C2S OK
INFO - Script line_not_there.fail.sh using profile xccdf_org.ssgproject.content_profile_C2S OK
INFO - All snapshots reverted successfully


PR with test coverage: https://github.com/OpenSCAP/scap-security-guide/pull/2541
Comment 10 Jan Černý 2018-01-16 08:34:34 UTC 
The test was merged in upstream test suite.
Comment 13 errata-xmlrpc 2018-04-10 12:21:26 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-2018:0761
Note You need to log in before you can comment on or make changes to this bug.