Bug 1316678
Summary: | avc: denied { dac_override } comm="fail2ban-client" | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Orion Poplawski <orion> |
Component: | selinux-policy | Assignee: | Simon Sekidde <ssekidde> |
Status: | CLOSED ERRATA | QA Contact: | Jan Zarsky <jzarsky> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7.2 | CC: | lvrabec, mgrepl, mmalik, orion, plautrba, pvrabec, ssekidde |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | selinux-policy-3.13.1-83.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-04 02:44:36 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: |
Description
Orion Poplawski
2016-03-10 18:29:22 UTC
Could you try to turn the full auditing on? # echo "-w /etc/shadow -p w" >> /etc/audit/audit.rules # systemctl reload auditd and reproduce it and attach AVC? Thank you. Still the same, although I get two at a time: type=AVC msg=audit(1458759692.434:727): avc: denied { dac_override } for pid=11037 comm="fail2ban-client" capability=1 scontext=system_u:system_r:fail2ban_client_t:s0 tcontext=system_u:system_r:fail2ban_client_t:s0 tclass=capability type=AVC msg=audit(1458759692.434:728): avc: denied { dac_override } for pid=11037 comm="fail2ban-client" capability=1 scontext=system_u:system_r:fail2ban_client_t:s0 tcontext=system_u:system_r:fail2ban_client_t:s0 tclass=capability After a reboot, also saw: type=AVC msg=audit(1458763089.252:871): avc: denied { net_admin } for pid=27651 comm="firewall-cmd" capability=12 scontext=system_u:system_r:fail2ban_t:s0 tcontext=system_u:system_r:fail2ban_t:s0 tclass=capability Any chance you see also a SYSCALL part of the audit message? Ah, yes, sorry used to just searching for denial messages: type=AVC msg=audit(1459434281.689:1219): avc: denied { dac_override } for pid=11539 comm="fail2ban-client" capability=1 scontext=system_u:system_r:fail2ban_client_t:s0 tcontext=system_u:system_r:fail2ban_client_t:s0 tclass=capability type=SYSCALL msg=audit(1459434281.689:1219): arch=c000003e syscall=6 success=yes exit=0 a0=24b78e0 a1=7ffd87faf0d0 a2=7ffd87faf0d0 a3=3 items=0 ppid=1 pid=11539 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="fail2ban-client" exe="/usr/bin/python2.7" subj=system_u:system_r:fail2ban_client_t:s0 key=(null) type=AVC msg=audit(1459434281.689:1220): avc: denied { dac_override } for pid=11539 comm="fail2ban-client" capability=1 scontext=system_u:system_r:fail2ban_client_t:s0 tcontext=system_u:system_r:fail2ban_client_t:s0 tclass=capability type=SYSCALL msg=audit(1459434281.689:1220): arch=c000003e syscall=4 success=yes exit=0 a0=24b78e0 a1=7ffd87faf490 a2=7ffd87faf490 a3=0 items=0 ppid=1 pid=11539 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="fail2ban-client" exe="/usr/bin/python2.7" subj=system_u:system_r:fail2ban_client_t:s0 key=(null) type=SERVICE_START msg=audit(1459434282.018:1221): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fail2ban comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' type=NETFILTER_CFG msg=audit(1459434282.272:1222): table=filter family=2 entries=93 type=SYSCALL msg=audit(1459434282.272:1222): arch=c000003e syscall=54 success=yes exit=0 a0=4 a1=0 a2=40 a3=16d92e0 items=0 ppid=703 pid=11588 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-multi" subj=system_u:system_r:iptables_t:s0 key=(null) Could you follow comment2, then reproduce the issue and attach AVC and SYSCALL msgs? I believe some of files on your system have too tight permission flags. Thank you type=AVC msg=audit(1462222429.189:8573): avc: denied { dac_override } for pid=7501 comm="fail2ban-client" capability=1 scontext=system_u:system_r:fail2ban_client_t:s0 tcontext=system_u:system_r:fail2ban_client_t:s0 tclass=capability type=SYSCALL msg=audit(1462222429.189:8573): arch=c000003e syscall=6 success=yes exit=0 a0=1ad2980 a1=7ffee77b6de0 a2=7ffee77b6de0 a3=3 items=0 ppid=1 pid=7501 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="fail2ban-client" exe="/usr/bin/python2.7" subj=system_u:system_r:fail2ban_client_t:s0 key=(null) type=AVC msg=audit(1462222429.190:8574): avc: denied { dac_override } for pid=7501 comm="fail2ban-client" capability=1 scontext=system_u:system_r:fail2ban_client_t:s0 tcontext=system_u:system_r:fail2ban_client_t:s0 tclass=capability type=SYSCALL msg=audit(1462222429.190:8574): arch=c000003e syscall=4 success=yes exit=0 a0=1ad2980 a1=7ffee77b71a0 a2=7ffee77b71a0 a3=0 items=0 ppid=1 pid=7501 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="fail2ban-client" exe="/usr/bin/python2.7" subj=system_u:system_r:fail2ban_client_t:s0 key=(null) type=SERVICE_START msg=audit(1462222429.745:8575): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fail2ban comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' type=NETFILTER_CFG msg=audit(1462222430.449:8576): table=filter family=2 entries=93 type=SYSCALL msg=audit(1462222430.449:8576): arch=c000003e syscall=54 success=yes exit=0 a0=4 a1=0 a2=40 a3=b922e0 items=0 ppid=659 pid=7814 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-multi" subj=system_u:system_r:iptables_t:s0 key=(null) I could not reproduce this bug on RHEL-7.2, so I added a testphase in /CoreOS/selinux-policy/Regression/fail2ban-and-similar which just checks for proper allow rule. 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://rhn.redhat.com/errata/RHBA-2016-2283.html |