Bug 704060

Summary: upx is 'unconfined' and cannot run with SELinux enabled
Product: [Fedora] Fedora Reporter: Paul Bransford <draeath>
Component: upxAssignee: Gwyn Ciesla <gwync>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 19CC: gwync
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 13:44:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Paul Bransford 2011-05-12 02:23:28 UTC
Description of problem:
upx cannot be used out-of-the-box with SELinux enabled, as it is unconfined and requires stack execution.

Version-Release number of selected component (if applicable):
3.04-2.fc13

Steps to Reproduce:
1. install UPX
2. ensure SELinux is enabled
3. attempt to use upx, or run 'ldd' on it
  
Actual results:
SELinux denial

Expected results:
normal operation

Additional info:
I have run a full filesystem relabel, just in case. This did not change anything.

audit log excerpt:
type=AVC msg=audit(1305166250.701:21): avc:  denied  { execstack } for  pid=2049 comm="upx" scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tclass=process

type=SYSCALL msg=audit(1305166250.701:21): arch=40000003 syscall=125 success=no exit=-13 a0=bfdfd000 a1=1000 a2=1000007 a3=bfdfd11c items=0 ppid=2047 pid=2049 auid=500 uid=500 gid=500 euid=500 suid=500 fsuid=500 egid=500 sgid=500 fsgid=500 tty=pts0 ses=1 comm="upx" exe="/usr/bin/upx" subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=(null)

Comment 1 Paul Bransford 2011-05-12 02:25:34 UTC
Odd. upx itself and libucl have what looks like a normal context:
-rwxr-xr-x. root root system_u:object_r:bin_t:s0       /usr/bin/upx
-rwxr-xr-x. root root system_u:object_r:lib_t:s0       /usr/lib/libucl.so.1.0.0

Comment 2 Fedora End Of Life 2013-04-03 15:52:42 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 3 Fedora End Of Life 2015-01-09 16:39:42 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 4 Fedora End Of Life 2015-02-17 13:44:54 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.