From owner-freebsd-security Sun Aug 16 19:44:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28972 for freebsd-security-outgoing; Sun, 16 Aug 1998 19:44:54 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28966 for ; Sun, 16 Aug 1998 19:44:52 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id UAA18362; Sun, 16 Aug 1998 20:44:12 -0600 (MDT) Message-Id: <199808170244.UAA18362@lariat.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.44 (Beta) Date: Sun, 16 Aug 1998 20:36:30 -0600 To: 026809r@dragon.acadiau.ca (Michael Richards), security@FreeBSD.ORG From: Brett Glass Subject: Re: Why don't winblows program have buffer overruns? In-Reply-To: <199808162301.UAA09103@dragon.acadiau.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 08:01 PM 8/16/98 -0300, Michael Richards wrote: >Hi! >I have been following the buffer overrun discussions for quite some time. >One thing that I have always wondered is: >Why aren't there buffer overruns for winblows that overrun the stack and >execute nasty code? There are. However, Windows machines are not generally run as servers, and therefore do not, for the most part, have daemons running that are easy to exploit (e.g. QPopper). You can still confuse them and possibly crash them via things like Winnuke (a program which exploits a flaw in Windows' built-in NetBIOS over TCP/IP implementation). But it's actually harder to take over the machine. This is why the recently published Outlook e-mail buffer overflow is a big deal; it's one of the few known holes that can potentially be used to take over a Windows machine that's a CLIENT rather than a SERVER. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message