Bug 723362 - SELinux is preventing /sbin/iptables-multi from 'read' accesses on the file /var/log/messages-20110717.
Summary: SELinux is preventing /sbin/iptables-multi from 'read' accesses on the file /...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: fail2ban
Version: 14
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Axel Thimm
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: setroubleshoot_trace_hash:a4f8e834e71...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-19 23:39 UTC by mqc373u
Modified: 2012-08-16 12:10 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 12:10:29 UTC
Type: ---


Attachments (Terms of Use)

Description mqc373u 2011-07-19 23:39:35 UTC
SELinux is preventing /sbin/iptables-multi from 'read' accesses on the file /var/log/messages-20110717.

*****  Plugin catchall (100. confidence) suggests  ***************************

If you believe that iptables-multi should be allowed read access on the messages-20110717 file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep iptables /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:iptables_t:s0
Target Context                system_u:object_r:var_log_t:s0
Target Objects                /var/log/messages-20110717 [ file ]
Source                        iptables
Source Path                   /sbin/iptables-multi
Port                          <Okänd>
Host                          (removed)
Source RPM Packages           iptables-1.4.9-1.fc14
Target RPM Packages           
Policy RPM                    selinux-policy-3.9.7-42.fc14
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Permissive
Host Name                     (removed)
Platform                      Linux (removed)
                              2.6.35.13-92.fc14.x86_64 #1 SMP Sat May 21
                              17:26:25 UTC 2011 x86_64 x86_64
Alert Count                   1
First Seen                    sön 17 jul 2011 03.32.08
Last Seen                     sön 17 jul 2011 03.32.08
Local ID                      aa7936fe-37fe-44c2-b27a-81ab466b775d

Raw Audit Messages
type=AVC msg=audit(1310866328.44:5716): avc:  denied  { read } for  pid=20954 comm="iptables" path="/var/log/messages-20110717" dev=dm-0 ino=2360974 scontext=system_u:system_r:iptables_t:s0 tcontext=system_u:object_r:var_log_t:s0 tclass=file


type=SYSCALL msg=audit(1310866328.44:5716): arch=x86_64 syscall=execve success=yes exit=0 a0=203ca40 a1=203c760 a2=203b330 a3=1 items=0 ppid=20953 pid=20954 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=/sbin/iptables-multi subj=system_u:system_r:iptables_t:s0 key=(null)

Hash: iptables,iptables_t,var_log_t,file,read

audit2allow

#============= iptables_t ==============
allow iptables_t var_log_t:file read;

audit2allow -R

#============= iptables_t ==============
allow iptables_t var_log_t:file read;

Comment 1 Miroslav Grepl 2011-07-20 11:20:14 UTC
Any idea why iptables reads /var/log/messages?

Comment 2 Daniel Walsh 2011-07-21 13:34:56 UTC
This is a leak.  read of a file without an open on an execve is almost always a leak.

mqc373u,

Any idea what tool you were running when this happened?

Comment 3 Thomas Woerner 2011-07-21 13:51:35 UTC
iptables is not reading /var/log/messages. This has to be a leak.

Comment 4 mqc373u 2011-07-22 15:20:04 UTC
(In reply to comment #2)
> This is a leak.  read of a file without an open on an execve is almost always a
> leak.
> 
> mqc373u,
> 
> Any idea what tool you were running when this happened?

I am using Nagios with NagiosGraph, stopping nagios service then notify regarding iptables disappears.

Comment 5 Miroslav Grepl 2011-07-25 12:13:34 UTC
Ah, yes. This is obviously a leak.

Comment 6 Marco Guazzone 2011-08-05 09:54:00 UTC
Had the same problem.
The alert is appeared during a SSH attack to my PC.
So I think the alert has been caused by fail2ban.

Comment 7 Fedora End Of Life 2012-08-16 12:10:32 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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" (top right of this page) 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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