Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 43341

Summary: lpd fails to drop groups of root
Product: [Retired] Red Hat Linux Reporter: Need Real Name <empathy>
Component: LPRngAssignee: Crutcher Dunnavant <crutcher>
Status: CLOSED ERRATA QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: pekkas
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-06-20 14:47:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Need Real Name 2001-06-03 11:18:52 UTC 
lpd fails to drop groups of root when becoming a daemon.
=========================================================
If tetex-1.0.7-7 is installed, it is possible to exploit this
to gain (for example) gid disk, which allows pretty much anything
you want. 

# ps -ax|grep lpd|grep -v grep
20697 ?        SW     0:00 [lpd]
[root@clarity /]# cat /proc/20697/status 
Name:   lpd
State:  S (sleeping)
Pid:    20697[root@clarity /]
PPid:   1
Uid:    0       4       0       4
Gid:    7       7       7       7
Groups: 0 1 2 3 4 6 10 40 
...
...
...

(gid 40 is used on my system for the net connection program)
I would expect to see the groups that user lp is a member of.
[root@clarity /]# id lp
uid=4(lp) gid=7(lp) groups=7(lp)

--zen-parse
Comment 1 Need Real Name 2001-06-03 11:43:13 UTC 
tetex info:
 http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=43342

oops, nearly forgot
[root@clarity /]# rpm -qf /usr/sbin/lpd
LPRng-3.6.24-2
Comment 2 Pekka Savola 2001-06-20 14:47:02 UTC 
This is fixed in errata, now.
Comment 3 Need Real Name 2001-07-04 17:24:05 UTC 
Looks like someone forgot to mark this as RESOLVED ERRATA

(Its definately not NEW)
Kinda makes the bugzilla database pretty useless if its not used properly.

Also makes it look like you aren't solving the problems.
Might want to spend a few minutes checking what else is actually resolved.