Date: 30 May 1998 10:08:41 +1000 From: Julian Assange <proff@iq.org> To: Cy Schubert - ITSD Open Systems Group <cschuber@uumail.gov.bc.ca> Cc: freebsd-security@FreeBSD.ORG, security-officer@FreeBSD.ORG Subject: Re: Kill(2) Vulnerability Message-ID: <wxlnrkiprq.fsf@polysynaptic.iq.org> In-Reply-To: Cy Schubert - ITSD Open Systems Group's message of "Fri, 29 May 1998 13:30:58 -0700" References: <199805292031.NAA18667@passer.osg.gov.bc.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Cy Schubert - ITSD Open Systems Group <cschuber@uumail.gov.bc.ca> writes: > One of my co-workers brought this to my attention from > http://www.openbsd.org/errata.html#kill. > > SECURITY FIX > The kill(2) system call previously would permit a large set > of signals to be delivered to setuid or setgid processes. If such > processes were using those signals in dubious ways, this could > have resulted in security problems of various kinds. The second > revision of a source code patch which solves the problem is > available. It's perfectly reasonable for kill(2) to deliver A Large Set Of Signals to s[gu]id programs running under the same process group. The issue here is that its possible to send signals that the code has trapped internally (like SIGALRM). This is a userland issue in my opinion. Either pull out of the process group, or deal with the signals concerned. Cheers, Julian. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?wxlnrkiprq.fsf>