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 2081708

Summary: Removal of some network sysctl-related rules from OSPP SCAP profile
Product: Red Hat Enterprise Linux 9 Reporter: Jan Pazdziora (Red Hat) <jpazdziora>
Component: scap-security-guideAssignee: Watson Yuuma Sato <wsato>
Status: CLOSED ERRATA QA Contact: Milan Lysonek <mlysonek>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0CC: ggasparb, jpazdziora, matyc, mhaicman, mlysonek, openscap-maint, vpolasek
Target Milestone: rcKeywords: AutoVerified, Triaged, ZStream
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: scap-security-guide-0.1.62-2.el9 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 2117613 (view as bug list) Environment:
Last Closed: 2022-11-15 10:25:25 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: 2117613    

Description Jan Pazdziora (Red Hat) 2022-05-04 12:49:47 UTC
Description of problem:

After reviewing the sysctl_net_* SCAP rules in the OSPP profile, we propose removing the following groups of rules from the profile as they are not related to OSPP specific requirements. More detailed reasons are listed below:

Remove rules that just reenforce the RHEL 9 default without any specific OSPP requirement:

- sysctl_net_ipv4_conf_all_accept_source_route
- sysctl_net_ipv4_conf_default_accept_source_route
- sysctl_net_ipv6_conf_all_accept_source_route
- sysctl_net_ipv6_conf_default_accept_source_route

- sysctl_net_ipv4_conf_all_rp_filter
- sysctl_net_ipv4_conf_default_rp_filter

- sysctl_net_ipv4_icmp_ignore_bogus_error_responses

- sysctl_net_ipv4_icmp_echo_ignore_broadcasts

Remove rules that reenforce the RHEL 9 default, are not related to any specific OSPP requirement and affect important functionality:

- sysctl_net_ipv4_tcp_syncookies

  The TCP SYN cookies can prevent some TCP options from working.

Remove rules that change the RHEL 9 default value but are not related to any specific OSPP requirement and affect important functionality:

- sysctl_net_ipv6_conf_all_accept_ra
- sysctl_net_ipv6_conf_default_accept_ra

  Without accepting Router Advertisements (or without using DHCPv6 or static configuration), ability of hosts to use IPv6 becomes severely limited.

Remove rules that change the RHEL 9 default value but are not related to any specific OSPP requirement:

- sysctl_net_ipv4_conf_all_accept_redirects
- sysctl_net_ipv4_conf_default_accept_redirects
- sysctl_net_ipv6_conf_all_accept_redirects
- sysctl_net_ipv6_conf_default_accept_redirects

  While the need for accepting ICMP redirects often stems from suboptimal network layout and RHEL default should likely be changed to 0, accepting the redirects does not break any of the OSPP requirements.

Remove rules that change the RHEL 9 default but don't impact the security of the security of the TOE in any way:

- sysctl_net_ipv4_conf_all_send_redirects
- sysctl_net_ipv4_conf_default_send_redirects

Remove rules that change the RHEL 9 default value for wrong reason:

- sysctl_net_ipv4_conf_all_secure_redirects
- sysctl_net_ipv4_conf_default_secure_redirects

  This sysctl allows redirects only when they are considered secure. So the RHEL default (1) is more secure than what the SCAP rules actually try to achieve.

Remove rules that might help with detecting network issues but not related to TOE security:

- sysctl_net_ipv4_conf_all_log_martians
- sysctl_net_ipv4_conf_default_log_martians

Remove rules that prevent routing which is a valid use-case, also needed for containerized and VM-hosting setups:

- sysctl_net_ipv4_ip_forward

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

scap-security-guide-0.1.60-6.el9_0

How reproducible:

Deterministic.

Steps to Reproduce:
1. Run
   oscap xccdf eval --profile xccdf_org.ssgproject.content_profile_ospp /usr/share/xml/scap/ssg/content/ssg-rhel9-ds.xml
   and check for any of the rules above.

Actual results:

They are listed.

Expected results:

None should be listed.

Additional info:

Comment 4 Watson Yuuma Sato 2022-07-04 12:16:18 UTC
https://github.com/ComplianceAsCode/content/pull/9092

Comment 16 errata-xmlrpc 2022-11-15 10:25:25 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 (scap-security-guide bug fix and enhancement update), 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-2022:8131