Bug 111932 - root privileges can be executed by non-root imposter - at least for up2date
root privileges can be executed by non-root imposter - at least for up2date
Status: CLOSED DUPLICATE of bug 112419
Product: Red Hat Linux
Classification: Retired
Component: pam (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jindrich Novy
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-12-11 13:35 EST by Wolfram R. Jarisch
Modified: 2013-07-02 18:58 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-13 10:15:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Wolfram R. Jarisch 2003-12-11 13:35:19 EST
Description of problem: "up2date -u" does not always request root
privileges when logged in with ssh. Time since last request for
"up2date -u" may matter (, 2 minutes?). BUT: running up2date -u,
logging out, logging back in (all with ssh within a minute) would
allow someone else (using same username and passwd) to run up2date. I
guess this should not be.

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

How reproducible: elapsed time may matter, otherwise 90+%

Steps to Reproduce:
1.login with ssh. run "up2date -u" (answer root passwd). logout.
2.login again with ssh (within a minute?)
3.run "up2date -u" ... do not get request for root passwd
Actual results: root passwd not always needed to do privileged work
                may be a problem in other settings as well?

Expected results: should request root privileges EVERY time

Additional info: will keep watching this
Comment 1 Adrian Likins 2003-12-11 14:43:05 EST
up2date does no handling of aquiring root privs itself, thats
the userhelper/consolehelper utils from the "usermode" package
(and it sounds like in this case, the pam_timestamp setup).

reassigning to usermode
Comment 2 Matthew Miller 2004-04-06 23:26:12 EDT
Workaround: put "sudo -k" in your .bash_logout. That should clear the
Comment 3 Tomas Mraz 2005-09-13 10:15:54 EDT

*** This bug has been marked as a duplicate of 112419 ***

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