[21963] in bugtraq

home help back first fref pref prev next nref lref last post

Re: bug w2k

daemon@ATHENA.MIT.EDU (Carl Livitt)
Sat Jul 28 23:09:31 2001

X-Apparently-From: <carllivitt@yahoo.com>
Content-Type: text/plain;
  charset="iso-8859-1"
From: Carl Livitt <carl@ititc.com>
To: bugtraq@securityfocus.com
Date: Sat, 28 Jul 2001 11:25:20 +0100
In-Reply-To: <4DA5F46097F3D411A30600508BE390521A563D@sulu>
MIME-Version: 1.0
Message-Id: <01072811234300.00540@europa>
Content-Transfer-Encoding: 8bit

> Just ping
> Now press F7 and Enter (try a couple of times quickly...less than ten , and
> you can see what a meaning)
> The machine reboots, from nothing a warm reboot.

Confirmed on Win2K Pro SP2, English. The reboot would not happen when there 
was no ping process. As soon as a ping was in progress, *boom*.

I did notice there was a STOP, Fatal Error blue screen that appeared briefly, 
but I could not catch what it said before the machine rebooted. Perhaps 
someone else will have more luck?

Does anyone know: is the F7 key (used in CMD.EXE as to bring up a 
most-recently-used command list) implemented in kernel or user space? If its 
in user space, then this is a doubly worrying bug as it hints that it would 
be possible for a non-privileged user to write code that could cause a BSOD 
and reboot. If it's in kernel space, well I just hope that this situation is 
not caused by an unchecked buffer....

Carl Livitt
Code Monkey
IT in the Community
England

-- 
Free Dmitry!
http://www.boycottadobe.com

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


home help back first fref pref prev next nref lref last post