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 1689255 - don't allow a container to connect to random services
Summary: don't allow a container to connect to random services
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: container-selinux
Version: 8.0
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: 8.0
Assignee: Lokesh Mandvekar
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1695248 1814146 1944083
TreeView+ depends on / blocked
 
Reported: 2019-03-15 14:18 UTC by Qian Cai
Modified: 2021-03-29 09:11 UTC (History)
6 users (show)

Fixed In Version: containre-selinux-2.94
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1695248 (view as bug list)
Environment:
Last Closed: 2019-11-05 21:01:58 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:3403 0 None None None 2019-11-05 21:02:34 UTC

Description Qian Cai 2019-03-15 14:18:06 UTC
Description of problem:
# sesearch --allow | grep 'svirt_sandbox_domain unconfined_service_t'
allow svirt_sandbox_domain unconfined_service_t:fd use;
allow svirt_sandbox_domain unconfined_service_t:fifo_file { append getattr ioctl lock open read write };
allow svirt_sandbox_domain unconfined_service_t:process sigchld;

Those rules (unsafe) were dropped in RHEL-7.6.2 but still are there in RHEL8.

"We don't want to allow a container to connect to random services on the
host system if they escape confinement." -- Dan Walsh

Version-Release number of selected component (if applicable):
container-selinux-2.75-1.git99e2cfd.module+el8+2769+577ad176.noarch
container-selinux-2.87-3.git891a85f.module+el8+2851+dbc75b3b.noarch

Comment 3 Daniel Walsh 2019-03-28 23:53:17 UTC
Fixed in container-selinux-2.94

Comment 7 Joy Pu 2019-09-27 12:44:04 UTC
Test with container-selinux-2.107-2.module+el8.1.0+4081+b29780af.noarch, the rules are already dropped. So set this to verified.

Details:
# sesearch --allow | grep 'svirt_sandbox_domain unconfined_service_t'
#

Comment 9 errata-xmlrpc 2019-11-05 21:01:58 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/RHSA-2019:3403


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