Bug 78291 - exec of setuid root program loses some environment variables
exec of setuid root program loses some environment variables
Status: CLOSED ERRATA
Product: Red Hat Linux
Classification: Retired
Component: glibc (Show other bugs)
7.3
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-11-20 15:24 EST by Need Real Name
Modified: 2016-11-24 09:55 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-11-20 15:25:40 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
description and test case to demonstrate bug (40.00 KB, application/octet-stream)
2002-11-20 15:25 EST, Need Real Name
no flags Details

  None (edit)
Description Need Real Name 2002-11-20 15:24:32 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Q312461)

Description of problem:
Certain environment variables
are removed from the environment of an exec'ed program, when that 
program is owned by root with the setuid bit set.

One such variable is LD_LIBRARY_PATH.  But this
is OK:  it is known that setuid programs delete LD_LIBRARY_PATH
from the environment list.  
(See /usr/src/redhat/SOURCES/glibc-2.2.5/sysdeps/generic/unsecvars.h)

The bug is that the environment variables G, H, L, M, N, R, and T
are also deleted from the environment.  Suspiciously, these happen
to be exactly the set of initial letters of the variables listed in 
unsecvars.h...

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


How reproducible:
Always

Steps to Reproduce:
See attachment for detailed information.


Additional info:
Comment 1 Need Real Name 2002-11-20 15:25:32 EST
Created attachment 85753 [details]
description and test case to demonstrate bug
Comment 2 Jakub Jelinek 2002-11-20 15:55:37 EST
This is fixed by glibc 7.3 errata.

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