Date: Sun, 16 Aug 1998 20:36:30 -0600 From: Brett Glass <brett@lariat.org> To: 026809r@dragon.acadiau.ca (Michael Richards), security@FreeBSD.ORG Subject: Re: Why don't winblows program have buffer overruns? Message-ID: <199808170244.UAA18362@lariat.lariat.org> In-Reply-To: <199808162301.UAA09103@dragon.acadiau.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808170244.UAA18362>