Bug 1276903 - SELinux is preventing /usr/libexec/abrt-hook-ccpp from 'getattr' accesses on the file /usr/libexec/packagekitd.
Summary: SELinux is preventing /usr/libexec/abrt-hook-ccpp from 'getattr' accesses on ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 22
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6f677fbe5e5e680a7ded72d9b2e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-01 04:55 UTC by Michael Wiktowy
Modified: 2016-07-19 20:44 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 20:44:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michael Wiktowy 2015-11-01 04:55:32 UTC
Description of problem:
SELinux is preventing /usr/libexec/abrt-hook-ccpp from 'getattr' accesses on the file /usr/libexec/packagekitd.

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

If you believe that abrt-hook-ccpp should be allowed getattr access on the packagekitd 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 abrt-hook-ccpp /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:abrt_dump_oops_t:s0
Target Context                system_u:object_r:rpm_exec_t:s0
Target Objects                /usr/libexec/packagekitd [ file ]
Source                        abrt-hook-ccpp
Source Path                   /usr/libexec/abrt-hook-ccpp
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           abrt-addon-coredump-helper-2.6.1-6.fc22.x86_64
Target RPM Packages           PackageKit-1.0.10-1.fc22.x86_64
Policy RPM                    selinux-policy-3.13.1-128.18.fc22.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.2.3-200.fc22.x86_64 #1 SMP Thu
                              Oct 8 03:23:55 UTC 2015 x86_64 x86_64
Alert Count                   1
First Seen                    2015-11-01 00:52:19 EDT
Last Seen                     2015-11-01 00:52:19 EDT
Local ID                      dd2255f5-4bb7-4f67-aac5-e9e3f1207356

Raw Audit Messages
type=AVC msg=audit(1446353539.131:655): avc:  denied  { getattr } for  pid=7361 comm="abrt-hook-ccpp" path="/usr/libexec/packagekitd" dev="sdb3" ino=3951664 scontext=system_u:system_r:abrt_dump_oops_t:s0 tcontext=system_u:object_r:rpm_exec_t:s0 tclass=file permissive=0


type=SYSCALL msg=audit(1446353539.131:655): arch=x86_64 syscall=stat success=no exit=EACCES a0=55853a00b260 a1=7ffc48b14f90 a2=7ffc48b14f90 a3=7aa items=0 ppid=6 pid=7361 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=abrt-hook-ccpp exe=/usr/libexec/abrt-hook-ccpp subj=system_u:system_r:abrt_dump_oops_t:s0 key=(null)

Hash: abrt-hook-ccpp,abrt_dump_oops_t,rpm_exec_t,file,getattr

Version-Release number of selected component:
selinux-policy-3.13.1-128.18.fc22.noarch

Additional info:
reporter:       libreport-2.6.3
hashmarkername: setroubleshoot
kernel:         4.2.3-200.fc22.x86_64
type:           libreport

Comment 1 Fedora End Of Life 2016-07-19 20:44:33 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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.