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 1571315 - Rule xccdf_org.ssgproject.content_rule_aide_scan_notification fails when email ID other than root@. is given [rhel-7.5.z]
Summary: Rule xccdf_org.ssgproject.content_rule_aide_scan_notification fails when emai...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: scap-security-guide
Version: 7.4
Hardware: x86_64
OS: Linux
high
urgent
Target Milestone: rc
: ---
Assignee: Watson Yuuma Sato
QA Contact: Marek Haicman
Mirek Jahoda
URL:
Whiteboard:
Depends On: 1540505
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-24 13:48 UTC by Oneata Mircea Teodor
Modified: 2021-09-09 13:50 UTC (History)
7 users (show)

Fixed In Version: scap-security-guide-0.1.36-9.el7_5
Doc Type: Bug Fix
Doc Text:
Previously, the Open Vulnerability and Assessment Language (OVAL) check for the aide_scan_notification rule allow Advanced Intrusion Detection Environment (AIDE) notification e-mails to be sent only to root@*. As a consequence, scanning with the rule returned fail if the notification e-mail recipient was not root. The OVAL check has been fixed to allow also other e-mail addresses than root, and aide_scan_notification now works properly for all email addresses.
Clone Of: 1540505
Environment:
Last Closed: 2018-05-14 16:13:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1410 0 None None None 2018-05-14 16:13:55 UTC

Description Oneata Mircea Teodor 2018-04-24 13:48:31 UTC
This bug has been copied from bug #1540505 and has been proposed to be backported to 7.5 z-stream (EUS).

Comment 3 Marek Haicman 2018-04-30 04:25:33 UTC
Verified fix in version scap-security-guide-0.1.36-9.el7_5.noarch through SSG Test Suite on commit https://github.com/OpenSCAP/scap-security-guide/commit/04ddc39b88f5756bf078b28b78fe11226096b438

NEW (scap-security-guide-0.1.36-9.el7_5.noarch):
[dahaic@machine tests]$ sudo ./test_suite.py rule --hypervisor qemu:///system --domain ssg-test-suite-rhel7 --datastream ./ssg-0.1.36-9.xml --xccdf-id scap_org.open-scap_cref_ssg-rhel7-xccdf-1.2.xml aide_scan_notification
Setting console output to log level INFO
INFO - xccdf_org.ssgproject.content_rule_aide_scan_notification
INFO - Script cron_weekly_configured.pass.sh using profile xccdf_org.ssgproject.content_profile_stig-rhel7-disa OK
INFO - Script crontab_configured.pass.sh using profile xccdf_org.ssgproject.content_profile_stig-rhel7-disa OK
INFO - Script crontab_just_periodic_checking.fail.sh using profile xccdf_org.ssgproject.content_profile_stig-rhel7-disa OK
INFO - Script default.fail.sh using profile xccdf_org.ssgproject.content_profile_stig-rhel7-disa OK
INFO - Script var_cron_configured.pass.sh using profile xccdf_org.ssgproject.content_profile_stig-rhel7-disa OK
INFO - All snapshots reverted successfully

OLD (scap-security-guide-0.1.36-7.el7.noarch):
[dahaic@machine tests]$ sudo ./test_suite.py rule --hypervisor qemu:///system --domain ssg-test-suite-rhel7 --datastream ./ssg-0.1.36-7.xml --xccdf-id scap_org.open-scap_cref_ssg-rhel7-xccdf-1.2.xml aide_scan_notification
Setting console output to log level INFO
INFO - xccdf_org.ssgproject.content_rule_aide_scan_notification
ERROR - Script cron_weekly_configured.pass.sh using profile xccdf_org.ssgproject.content_profile_stig-rhel7-disa 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_aide_scan_notification'.
ERROR - Script crontab_configured.pass.sh using profile xccdf_org.ssgproject.content_profile_stig-rhel7-disa 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_aide_scan_notification'.
INFO - Script crontab_just_periodic_checking.fail.sh using profile xccdf_org.ssgproject.content_profile_stig-rhel7-disa 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_aide_scan_notification'.
INFO - Script default.fail.sh using profile xccdf_org.ssgproject.content_profile_stig-rhel7-disa OK
ERROR - Script var_cron_configured.pass.sh using profile xccdf_org.ssgproject.content_profile_stig-rhel7-disa 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_aide_scan_notification'.
INFO - All snapshots reverted successfully

Comment 6 errata-xmlrpc 2018-05-14 16:13:49 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:1410


Note You need to log in before you can comment on or make changes to this bug.