full-disclosure - Re: 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>] [day] [month] [year] [list]

Message-Id: <20070120235443.2B74D1D8F21@supertolla.itapac.net>
Date: Sun, 21 Jan 2007 00:53:53 +0100
From: "Michele Cicciotti" <mc@...msa.net>
To: "'eugeny gladkih'" <john@...eb.com>,
	"'Shiva Persaud'" <shivapd@...tin.ibm.com>
Cc: full-disclosure@...ts.grok.org.uk, bugtraq@...urityfocus.com
Subject: Re: Multiple OS kernel insecure handling of
	stdio	file descriptor

>  SP> The AIX Security Team can be reached at security-alert@...tin.ibm.com.
>  SP> We have investigated this issue and AIX is not affected. A privileged
>  SP> process will not inherit closed file descriptors for stdio, stdout and
>  SP> stderr.
> well, but what is used for stdout if it's closed in the parent
> process just before fork(2) call?!

I don't know what's the case for AIX, but the typical fix for this vulnerability is to reopen stdout and stderr to /dev/null for setuid processes

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/