Bug 810436 - SELinux is preventing /bin/bash from 'execute' accesses on the fichier /bin/traceroute.
SELinux is preventing /bin/bash from 'execute' accesses on the fichier /bin/t...
Product: Fedora
Classification: Fedora
Component: fail2ban (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Axel Thimm
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-04-06 03:16 EDT by foxsite
Modified: 2013-02-13 03:59 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-13 03:59:21 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description foxsite 2012-04-06 03:16:55 EDT
libreport version: 2.0.8
executable:     /usr/bin/python
hashmarkername: setroubleshoot
kernel:         3.3.0-8.fc16.x86_64
reason:         SELinux is preventing /bin/bash from 'execute' accesses on the fichier /bin/traceroute.
time:           ven. 06 avril 2012 09:16:13 CEST

:SELinux is preventing /bin/bash from 'execute' accesses on the fichier /bin/traceroute.
:*****  Plugin catchall (100. confidence) suggests  ***************************
:If you believe that bash should be allowed execute access on the traceroute file by default.
:Then you should report this as a bug.
:You can generate a local policy module to allow this access.
:allow this access for now by executing:
:# grep sh /var/log/audit/audit.log | audit2allow -M mypol
:# semodule -i mypol.pp
:Additional Information:
:Source Context                system_u:system_r:fail2ban_t:s0
:Target Context                system_u:object_r:traceroute_exec_t:s0
:Target Objects                /bin/traceroute [ file ]
:Source                        sh
:Source Path                   /bin/bash
:Port                          <Inconnu>
:Host                          (removed)
:Source RPM Packages           bash-4.2.24-1.fc16.x86_64
:Target RPM Packages           traceroute-2.0.18-1.fc16.x86_64
:Policy RPM                    selinux-policy-3.10.0-80.fc16.noarch
:Selinux Enabled               True
:Policy Type                   targeted
:Enforcing Mode                Enforcing
:Host Name                     (removed)
:Platform                      Linux (removed) 3.3.0-8.fc16.x86_64 #1 SMP Thu Mar 29
:                              18:37:19 UTC 2012 x86_64 x86_64
:Alert Count                   4
:First Seen                    jeu. 05 avril 2012 10:02:20 CEST
:Last Seen                     ven. 06 avril 2012 07:29:45 CEST
:Local ID                      d8d7b632-8315-4b51-8232-ebaf8048401c
:Raw Audit Messages
:type=AVC msg=audit(1333690185.62:10090): avc:  denied  { execute } for  pid=21493 comm="sh" name="traceroute" dev="sdb3" ino=3948572 scontext=system_u:system_r:fail2ban_t:s0 tcontext=system_u:object_r:traceroute_exec_t:s0 tclass=file
:type=SYSCALL msg=audit(1333690185.62:10090): arch=x86_64 syscall=execve success=no exit=EACCES a0=21f44c0 a1=21f4590 a2=21f2040 a3=18 items=0 ppid=21492 pid=21493 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=sh exe=/bin/bash subj=system_u:system_r:fail2ban_t:s0 key=(null)
:Hash: sh,fail2ban_t,traceroute_exec_t,file,execute
:#============= fail2ban_t ==============
:#!!!! This avc is allowed in the current policy
:allow fail2ban_t traceroute_exec_t:file execute;
:audit2allow -R
:#============= fail2ban_t ==============
:#!!!! This avc is allowed in the current policy
:allow fail2ban_t traceroute_exec_t:file execute;
Comment 1 Daniel Walsh 2012-04-09 15:45:34 EDT
Is fail2ban expected to run traceroute?
Comment 2 Dmitry Butskoy 2012-04-11 08:51:56 EDT
Seems to no.
There is no word "traceroute" anywhere in the latest git source of the fail2ban.

Maybe ask fail2ban people for more investigations?
Comment 3 Fedora End Of Life 2013-01-16 05:21:43 EST
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 4 Fedora End Of Life 2013-02-13 03:59:24 EST
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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