Bugtraq mailing list archives

Re: [Full-disclosure] Multiple OS kernel insecure handling of stdio file descriptor

From: Troy Bollinger <troy () austin ibm com>
Date: Sat, 20 Jan 2007 15:18:14 -0600

On Sat, Jan 20, 2007 at 08:43:33PM +0300, eugeny gladkih wrote:

well, but what is used for stdout if it's closed in the parent
process just before fork(2) call?!


If I recall correctly, setuid and setgid programs with closed stdin,
stdout or stderr will open /dev/null during exec.

This fix was added to AIX back in 1999 or so.

-- 
Troy Bollinger <troy () austin ibm com>
Network Security Analyst
PGP keyid: 1024/0xB7783129
Troy's opinions are not IBM policy

Current thread:

Multiple OS kernel insecure handling of stdio file descriptor XFOCUS Security Team (Jan 18)
- Re: Multiple OS kernel insecure handling of stdio file descriptor 3APA3A (Jan 18)
- Re: Multiple OS kernel insecure handling of stdio file descriptor Peter Jeremy (Jan 18)
  - Re: Multiple OS kernel insecure handling of stdio file descriptor Carson Gaspar (Jan 22)
- Re: Multiple OS kernel insecure handling of stdio file descriptor Shiva Persaud (Jan 20)
  - Re: Multiple OS kernel insecure handling of stdio file descriptor eugeny gladkih (Jan 23)
    - Re: [Full-disclosure] Multiple OS kernel insecure handling of stdio file descriptor Troy Bollinger (Jan 22)