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:

This is a follow-up of BZ #1694962.

A customer executing oscap on all of his systems sees oscap consume all of the system memory while rule "file_permissions_unauthorized_world_writable" browses the GPFS file system which seems to be very deep in customer's case.
The rule executes because GPFS file systems are not considered as remote file systems.

Having such behaviour is just not acceptable.

A workaround to avoid browsing GPFS filesystems is described in KCS https://access.redhat.com/solutions/4193501 but the workaround doesn't apply to the customer because in his case the oscap execution is done through foreman which runs as a cron which was installed by Satellite.
Due to having a cron, it's not possible to limit the memory being used by oscap nor to exclude certain paths, at least on RHEL 7.

I'm hence requesting a hardening of the oscap tool to protect the system from possible bad behaviour **by default**.

A solution may be to have "oscap" re-execute itself in a scope with limited memory ("systemd-run --scope -p MemoryLimit=1G -- oscap ...").


Version-Release number of selected component (if applicable):

openscap-scanner-1.2.17-9.el7.x86_64 and later


How reproducible:

Always on customer site

Hello. Red Hat Enterprise Linux 7 has entered Maintenance Phase 2. This, as described here https://access.redhat.com/support/policy/updates/errata, means Critical and Important impact security advisories, and Urgent priority bugfix advisories are to be provided. As this bug is not of either criteria, I am closing it as CLOSED/DEFERRED, as it should be fixed in RHEL 8.3 release (see Bug 1870087).