From owner-freebsd-security Fri May 17 04:02:02 1996 Return-Path: owner-security Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA07510 for security-outgoing; Fri, 17 May 1996 04:02:02 -0700 (PDT) Received: from ptavv.nsta.org (ptavv.gfoster.com [199.0.2.254]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA07499 for ; Fri, 17 May 1996 04:01:58 -0700 (PDT) Received: (from gfoster@localhost) by ptavv.nsta.org (8.7.5/8.6.12) id HAA00301; Fri, 17 May 1996 07:00:35 -0400 (EDT) Date: Fri, 17 May 1996 07:00:35 -0400 (EDT) From: Glen Foster Message-Id: <199605171100.HAA00301@ptavv.nsta.org> To: jkh@time.cdrom.com CC: coredump@nervosa.com, freebsd-security@FreeBSD.ORG In-reply-to: <13642.832322039@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: very bad Sender: owner-security@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I, for one, am very happy that he announced it to the group rather than attempting STO. I was able fix the systems for which I have responsibility immediately. Thanks to Chris for getting the word out! It will be interesting to see an announcement coming from CERT two or three months from now about a "new" security bug. Now the big question, except for the obvious, why was mount_union suid in the first place? --- Glen Foster > Date: Fri, 17 May 1996 01:33:59 -0700 > From: "Jordan K. Hubbard" > > > Too bad it's already on BUGTRAQ and BoS which is way more than 1000 :-( > > Ah well, what's done is done. > > > of such an address. The prepared fix is chmod u-s /sbin/mount_union. > > It should at least return EPERM! :-) > > Jordan > > >