Date: Wed, 12 Aug 1998 23:05:27 +0200 (CEST) From: Stephane Legrand <stephane@lituus.fr> To: FreeBSD-stable@FreeBSD.ORG Subject: Huge Bug in FreeBSD not fixed? Message-ID: <199808122105.XAA00425@sequoia.lituus.fr> In-Reply-To: <Pine.BSF.4.02.9808110025020.216-200000@SchematiX.net> References: <Pine.BSF.4.02.9808110025020.216-200000@SchematiX.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Scott writes: > I ran across this bug a while back on rootshell, and then again by a user > on IRC who offered to take down my box. Soon after that, the bug was fixed > and things were fine. But just out of boredom, i decided to run the > exploit again. Sure enough, i had a kernel panic and that was it. All of > this from a normal user account. The bug has reoccured recently and may > cause problems on my server if the users find out about the vulnerability. > > I am running FreeBSD 2.2.7-STABLE (Last compiled on August 5th early in > the morning). The system is running on a PII233 with 64MB RAM. This bug > REALLY needs to be fixed ASAP. > > I would like to know if other systes are vulnerable as well. I discussed > this matter on IRC and everyone said they had similar problems. This bug > needs to be addressed soon. I would HATE switching to linux because my > system keeps crashing. > Just for information, this piece of code perfectly crash my freebsd current box. I must to specify that the "/etc" directory hasn't been updated to current one except for the "rc.conf" file. But it shows that this bug doesn't belong only to stable version. Stephane Legrand. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808122105.XAA00425>