Bug 117374 - rpm --recontext -q rpm segfaults as user_r:user_t
rpm --recontext -q rpm segfaults as user_r:user_t
Product: Fedora
Classification: Fedora
Component: rpm (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
Mike McLean
Depends On:
Blocks: FC2Blocker
  Show dependency treegraph
Reported: 2004-03-03 07:53 EST by Paul Nasrat
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-04-07 19:23:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Brief analysis of core (4.63 KB, text/plain)
2004-03-03 08:00 EST, Paul Nasrat
no flags Details

  None (edit)
Description Paul Nasrat 2004-03-03 07:53:48 EST
Description of problem:

rpm --recontext -q rpm causes segmentation fault whilst running in
enforcing mode

Version-Release number of selected component (if applicable):

How reproducible:


Steps to Reproduce:
1. setenforce 1
2. login as a user who is user_r:user_t
3.  rpm --recontext -q rpm
Actual results:

D: opening  db index       /var/lib/rpm/Packages rdonly mode=0x0

D: locked   db index       /var/lib/rpm/Packages

D: opening  db index       /var/lib/rpm/Name rdonly mode=0x0

D:  read h#    1842 Header SHA1 digest: OK

Permission denied

Segmentation fault

Expected results:

No segmentation fault.

Additional info:

Drops core - back trace to be attached.

avc error:

avc: denied { search } for pid 2655 exe=/usr/lib/rpm/rpmq name=selinux
dev=hda5 ino=1493914 scontext=victim:user_r:user_t
tcontext=system_u:object_r:policy_config_t tclass=dir

inode corresponds to /etc/security/selinux
Comment 1 Paul Nasrat 2004-03-03 08:00:08 EST
Created attachment 98235 [details]
Brief analysis of core

If you need any more analysis yell
Comment 2 Jeff Johnson 2004-04-07 19:23:23 EDT
Fixed in rpm-4.3.1-0.2 when built.

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