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.

Bug 1825810

Summary:	Remediation of sysctl_net_ipv4_ip_forward rule breaks the sysctl_net_ipv4_conf_all_accept_redirects rule
Product:	Red Hat Enterprise Linux 7	Reporter:	Matus Marhefka <mmarhefk>
Component:	scap-security-guide	Assignee:	Vojtech Polasek <vpolasek>
Status:	CLOSED WORKSFORME	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.9	CC:	ggasparb, matyc, mhaicman, wsato
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1929805 (view as bug list)		Environment:
Last Closed:	2020-06-02 10:50:30 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:
Bug Depends On:
Bug Blocks:	1929805

Description Matus Marhefka 2020-04-20 10:21:15 UTC

Description of problem:
Remediation of sysctl_net_ipv4_ip_forward rule breaks the sysctl_net_ipv4_conf_all_accept_redirects rule, this happens only when tested on "Server with GUI" installation.


Version-Release number of selected component (if applicable):
scap-security-guide-0.1.49-2.el7


How reproducible:
always


Steps to Reproduce:
1. Install RHEL-7.9 with "Server with GUI" package group
2. Scan of a machine after installation reports a failing rule - sysctl_net_ipv4_ip_forward
3. Fixing the rule (with `oscap xccdf eval --remediate --rule sysctl_net_ipv4_ip_forward`) makes the other rule to fail - sysctl_net_ipv4_conf_all_accept_redirects


Actual results:
Remediation of sysctl_net_ipv4_ip_forward rule breaks the sysctl_net_ipv4_conf_all_accept_redirects rule.


Expected results:
Remediation of sysctl_net_ipv4_ip_forward rule does not influence the result of sysctl_net_ipv4_conf_all_accept_redirects rule (maybe these rules cannot be selected in a profile together).

Comment 3 Matus Marhefka 2020-04-20 14:23:28 UTC

Forgot to add which profile this applies to, it is the OSPP.

Comment 15 Matus Marhefka 2020-05-21 14:45:21 UTC

This issue also affects CIS profile (when using "Server with GUI" package group).

Comment 16 Vojtech Polasek 2020-06-02 08:30:43 UTC

I was not able to reproduce the problem locally. I used the official profile kickstart and added the group to install "server with GUI". None of mentioned rules were failing after installation. So the only case where we managed to reproduce this problem were our tests in Beaker.

Comment 17 Marek Haicman 2020-06-02 10:50:30 UTC

We are very deep in the maintenance phase of RHEL7, so this issue, given it couldn't be reproduced in the wilds (see Comment 16) I am closing it as WORKSFORME.

Second point is - our profiles are not really meant to harden "Server with GUI" package set to the expected level of compliance. They are for non-GUI installations mainly. So the severity of a bug like this one is expected to be lower.