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.
Upstream:
13801962073f ("fix(firewalld): keep linux capability CAP_SYS_MODULE")
Comment 8Jan Pazdziora (Red Hat)
2021-12-06 08:44:47 UTC
Would it be possible to isolate loading the kernel modules to separate helper utility with separate capabilities, so that the daemon itself would not need them?
(In reply to Jan Pazdziora from comment #8)
> Would it be possible to isolate loading the kernel modules to separate
> helper utility with separate capabilities, so that the daemon itself would
> not need them?
Probably possible. What is the intent?
Some of the module loading happens by firewalld itself (e.g. nf_nat_ftp). But invoking iptables-legacy (maybe this counts as a helper utility) also causes some modules to implicitly load. The change mentioned in comment 2 address both.
Comment 10Jan Pazdziora (Red Hat)
2021-12-06 16:11:53 UTC
The intent would be to separate the security domains of distinct types of operations and separate them through interfaces (albeit invoking script via sudo with certain parameters), with the goal of minimizing attack surface. A daemon loading modules itself could be tricked to load different module. It that operation is moved to a narrow-purpose utility that cannot do anything but load three or four modules whose names it checks, any potential future vulnerability in the daemon itself would have smaller impact.
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 (new packages: firewalld), 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:3993