Bug 16172 - LPRng has setuid/setgid, group membership issues.
Summary: LPRng has setuid/setgid, group membership issues.
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: LPRng   
(Show other bugs)
Version: 7.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Crutcher Dunnavant
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-08-14 17:00 UTC by Crutcher Dunnavant
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-08-14 19:54:25 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Crutcher Dunnavant 2000-08-14 17:00:36 UTC
Well, this should be fun to fix. It seems we have setuid/setgid, group
membership issues for LPRNG, and this is bad (though not in an exploits
way). Here is the email that pointed it out:

      In porting the Pinstripe srpms to Linuxppc I discovered what I
think is a flaw in the
LPRng spec. On my machine running the Pinstripe rpms I find that the
stock LPRng
spec results in users being unable to print files from their own
directories when their
directories have restricted permissions like drwx------. In such cases I
an error message that the lpr can't open the file to be printed. What I
noticed was that
the LPRng.spec had...
%attr(4755,lp,lp) %{_bindir}/lpq
%attr(4755,lp,lp) %{_bindir}/lprm
%attr(4755,lp.lp) %{_bindir}/lpr
%attr(4755,lp,lp) %{_bindir}/lpstat
in the file list. Shouldn't this be....
%attr(4755,root,lp) %{_bindir}/lpq
%attr(4755,root,lp) %{_bindir}/lprm
%attr(4755,root,lp) %{_bindir}/lpr
%attr(4755,root,lp) %{_bindir}/lpstat
On my machine that change solves the problem and matches what was in the
spec from RedHat 6.2....
%attr(6555,root,lp) /usr/bin/lpq
%attr(6555,root,lp) /usr/bin/lpr
%attr(6555,root,lp) /usr/bin/lprm

Comment 1 Crutcher Dunnavant 2000-08-14 19:54:23 UTC
I think that this, and many other issues are handled by removing the sticky bits
from the client programs. So that's what I did.

I also removed the bit from the lpc control program.

Comment 2 Crutcher Dunnavant 2000-08-14 19:55:02 UTC
I think this is all closed up now.

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