Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 78291 - exec of setuid root program loses some environment variables
Summary: exec of setuid root program loses some environment variables
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: glibc
Version: 7.3
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2002-11-20 20:24 UTC by Need Real Name
Modified: 2016-11-24 14:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2002-11-20 20:25:40 UTC

Attachments (Terms of Use)
description and test case to demonstrate bug (deleted)
2002-11-20 20:25 UTC, Need Real Name
no flags Details

Description Need Real Name 2002-11-20 20:24:32 UTC
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 

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

How reproducible:

Steps to Reproduce:
See attachment for detailed information.

Additional info:

Comment 1 Need Real Name 2002-11-20 20:25:32 UTC
Created attachment 85753 [details]
description and test case to demonstrate bug

Comment 2 Jakub Jelinek 2002-11-20 20:55:37 UTC
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.