Bug 552011 - SELinux is preventing /usr/sbin/snort-plain "write" access on 001.
Summary: SELinux is preventing /usr/sbin/snort-plain "write" access on 001.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: snort
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dennis Gilmore
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: setroubleshoot_trace_hash:dcd6bb4d07d...
: 552014 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-03 16:17 UTC by Retlaw Dlawso
Modified: 2010-11-08 15:07 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 15:07:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Retlaw Dlawso 2010-01-03 16:17:51 UTC
Summary:

SELinux is preventing /usr/sbin/snort-plain "write" access on 001.

Detailed Description:

[SELinux is in permissive mode. This access was not denied.]

SELinux denied access requested by snort. It is not expected that this access is
required by snort and this access may signal an intrusion attempt. It is also
possible that the specific version or configuration of the application is
causing it to require additional access.

Allowing Access:

You can generate a local policy module to allow this access - see FAQ
(http://fedora.redhat.com/docs/selinux-faq-fc5/#id2961385) Please file a bug
report.

Additional Information:

Source Context                system_u:system_r:snort_t:s0
Target Context                system_u:object_r:usb_device_t:s0
Target Objects                001 [ chr_file ]
Source                        snort
Source Path                   /usr/sbin/snort-plain
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           snort-2.8.5.1-1.fc12
Target RPM Packages           
Policy RPM                    selinux-policy-3.6.32-59.fc12
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Permissive
Plugin Name                   catchall
Host Name                     (removed)
Platform                      Linux (removed)
                              2.6.31.9-174.fc12.x86_64 #1 SMP Mon Dec 21
                              05:33:33 UTC 2009 x86_64 x86_64
Alert Count                   120
First Seen                    Tue 24 Nov 2009 06:18:34 PM CET
Last Seen                     Sun 03 Jan 2010 04:54:55 PM CET
Local ID                      9b0ef36b-7dde-4d33-84cd-ca9dfdaff899
Line Numbers                  

Raw Audit Messages            

node=(removed) type=AVC msg=audit(1262534095.923:11103): avc:  denied  { write } for  pid=1334 comm="snort" name="001" dev=tmpfs ino=2902 scontext=system_u:system_r:snort_t:s0 tcontext=system_u:object_r:usb_device_t:s0 tclass=chr_file

node=(removed) type=SYSCALL msg=audit(1262534095.923:11103): arch=c000003e syscall=2 success=yes exit=7 a0=7fff5a74f080 a1=2 a2=7fff5a74f094 a3=fffffffd items=0 ppid=1333 pid=1334 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="snort" exe="/usr/sbin/snort-plain" subj=system_u:system_r:snort_t:s0 key=(null)



Hash String generated from  selinux-policy-3.6.32-59.fc12,catchall,snort,snort_t,usb_device_t,chr_file,write
audit2allow suggests:
audit2allow is not installed.

Comment 1 Daniel Walsh 2010-01-04 15:28:53 UTC

*** This bug has been marked as a duplicate of bug 549446 ***

Comment 2 Daniel Walsh 2010-01-04 17:05:50 UTC
What device is at 001?

What usb devices do you have on this machine?

Comment 3 Daniel Walsh 2010-01-04 17:08:23 UTC
*** Bug 552014 has been marked as a duplicate of this bug. ***

Comment 4 Retlaw Dlawso 2010-01-04 19:46:42 UTC
USB1-1 = USB-Drive mass storage device 500GB VERBATIM JH8322/model#47510

Comment 5 Retlaw Dlawso 2010-01-04 20:35:36 UTC
on "HardInfo" however:
-port #0 is allocated to VERBATIM JH8322/model#47510   480mBit/s 2mA
-port #1 is allocated to a generic mass storage device 480mBit/s 100mA

the USB1-1 reference appears under Log Viewer

Comment 6 Daniel Walsh 2010-01-04 20:55:55 UTC
I have no idea why snort would need to write to these devices so I am reassigning to snort.

Comment 7 Daniel Walsh 2010-01-04 21:07:52 UTC
Are you doing this in a kvm guest?

Comment 8 Retlaw Dlawso 2010-01-05 10:12:45 UTC
no kvm installed

Comment 9 Daniel Walsh 2010-01-05 12:58:58 UTC
Ok Red Herring,  I saw similar access being requested by asterisk when run in a kvm environment.

Comment 10 Bug Zapper 2010-11-04 01:57:51 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Comment 11 Retlaw Dlawso 2010-11-06 15:47:10 UTC
Yes, close this bug; the newest Fedora versions are ever in use, anyway. Thanks.


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