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.
Description of problem:
sshd rules will pass when sshd_required is set to 0 (unset)
Version-Release number of selected component (if applicable):
scap-security-guide-0.1.36-4.el7.noarch
How reproducible:
reliably
Steps to Reproduce:
1. open scap workbench, select sshd_use_approved_ciphers
2. sshd_required set to 0
3. scan machine that has Ciphers line commented / not present at all
Actual results:
pass
Expected results:
fail
Additional info:
All sshd rules has more or less same pattern in the oval (this is snippet from source code):
<criteria operator="AND">
<extend_definition comment="Installed OS is certified" definition_ref="installed_OS_is_certified" />
<criteria comment="SSH is not installed or conditions are met"
operator="OR">
<extend_definition comment="sshd is not required and not installed, or requirement is unset"
definition_ref="sshd_not_required_or_unset" />
<criteria comment="sshd is installed and configured" operator="AND">
<extend_definition comment="sshd is required and installed, or requirement is unset"
definition_ref="sshd_required_or_unset" />
<criterion comment="Check the Cipers list in /etc/ssh/sshd_config"
test_ref="test_sshd_use_approved_ciphers" />
</criteria>
</criteria>
</criteria>
That criterion "sshd_not_required_or_unset" is the culprit - what we really want in this situation is different logic - "sshd is not installed and either not required or unset".
Verified in version scap-security-guide-0.1.36-7.el7.noarch `sshd_required` value works as expected.
1 - sshd_* rules pass when openssh-server package is not installed, fail otherwise
2 - sshd_* rules pass if openssh-server package is installed and sshd_config is configured properly
0 - configuration is checked if openssh-server is installed
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
Description of problem: sshd rules will pass when sshd_required is set to 0 (unset) Version-Release number of selected component (if applicable): scap-security-guide-0.1.36-4.el7.noarch How reproducible: reliably Steps to Reproduce: 1. open scap workbench, select sshd_use_approved_ciphers 2. sshd_required set to 0 3. scan machine that has Ciphers line commented / not present at all Actual results: pass Expected results: fail Additional info: All sshd rules has more or less same pattern in the oval (this is snippet from source code): <criteria operator="AND"> <extend_definition comment="Installed OS is certified" definition_ref="installed_OS_is_certified" /> <criteria comment="SSH is not installed or conditions are met" operator="OR"> <extend_definition comment="sshd is not required and not installed, or requirement is unset" definition_ref="sshd_not_required_or_unset" /> <criteria comment="sshd is installed and configured" operator="AND"> <extend_definition comment="sshd is required and installed, or requirement is unset" definition_ref="sshd_required_or_unset" /> <criterion comment="Check the Cipers list in /etc/ssh/sshd_config" test_ref="test_sshd_use_approved_ciphers" /> </criteria> </criteria> </criteria> That criterion "sshd_not_required_or_unset" is the culprit - what we really want in this situation is different logic - "sshd is not installed and either not required or unset".