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 1805931 - allow chronyc_t self:tcp_socket create;
Summary: allow chronyc_t self:tcp_socket create;
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Zdenek Pytela
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
: 1868415 (view as bug list)
Depends On:
Blocks: 1872304
TreeView+ depends on / blocked
 
Reported: 2020-02-21 17:42 UTC by Alois Mahdal
Modified: 2020-08-25 13:07 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1872304 (view as bug list)
Environment:
Last Closed: 2020-02-22 15:52:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Alois Mahdal 2020-02-21 17:42:56 UTC
Description of problem
======================

We're seeing a chrony-related AVC during early stage of upgrade from RHEL-7.6.

    type=PROCTITLE msg=audit(1582284305.953:151): proctitle=6368726F6E796300736F757263657374617473
    type=SYSCALL msg=audit(1582284305.953:151): arch=c000003e syscall=41 success=no exit=-13 a0=2 a1=80001 a2=0 a3=7fffaf496e1a items=0 ppid=21781 pid=21786 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="chronyc" exe="/usr/bin/chronyc" subj=unconfined_u:unconfined_r:chronyc_t:s0-s0:c0.c1023 key=(null)
    type=AVC msg=audit(1582284305.953:151): avc:  denied  { create } for  pid=21786 comm="chronyc" scontext=unconfined_u:unconfined_r:chronyc_t:s0-s0:c0.c1023 tcontext=unconfined_u:unconfined_r:chronyc_t:s0-s0:c0.c1023 tclass=tcp_socket permissive=0

This happens after /CoreOS/chrony/Upgrade/basic is run in source mode, ie.
a test scenario has been set up.

Before upgrade we're running sosreport; since sosreport has some chrony related
plugins, my guess is that one of them could be causing this.


Version-Release number of selected component
============================================

selinux-policy-3.13.1-229.el7_6.15.noarch


How reproducible
================

At times


Steps to Reproduce
==================

Run setup from this task (distribution_upgrade__at_src is true,
distribution_upgrade__at_dst is false).

    http://pkgs.devel.redhat.com/cgit/tests/chrony/tree/Upgrade/basic/runtest.sh

Reboot

Run sosreport


Actual results
==============

AVC is seen


Expected results
================

No AVC


Additional info
===============

Audit2alow says:

    allow chronyc_t self:tcp_socket create;

Comment 2 Lukas Vrabec 2020-02-22 15:52:38 UTC
This issue was not selected to be included in Red Hat Enterprise Linux 7 because it is seen either as low or moderate impact to a small number of use-cases. Red Hat Enterprise Linux 7 is in Maintenance Support 1 Phase, which means that qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available.

We will now close this issue, but if you believe that it qualifies for the Maintenance Support 1 Phase, please re-open; otherwise, we recommend moving the request to Red Hat Enterprise Linux 8 if applicable.

Comment 3 Lukas Vrabec 2020-08-12 15:15:42 UTC
*** Bug 1868415 has been marked as a duplicate of this bug. ***


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