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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20070120211814.GA23240@goliath.austin.ibm.com>
Date: Sat, 20 Jan 2007 15:18:14 -0600
From: Troy Bollinger <troy@...tin.ibm.com>
To: eugeny gladkih <john@...eb.com>
Cc: Shiva Persaud <shivapd@...tin.ibm.com>,
	full-disclosure@...ts.grok.org.uk, bugtraq@...urityfocus.com
Subject: Re: [Full-disclosure] Multiple OS kernel insecure handling of stdio file descriptor

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@...tin.ibm.com>
Network Security Analyst
PGP keyid: 1024/0xB7783129
Troy's opinions are not IBM policy