Just confirmed this this, however, unless I missed it, or unless it isn't supposed to be there anyway, I couldn't find the signature 41414141's anywhere in the crash dump analysis of the event. I wonder if the crash is caused by some cascading events that were triggered by the oversized input. > -----Original Message----- > From: aT4r InsaN3 [mailto:at4rat_private] > Sent: Monday, April 28, 2003 1:35 PM > To: vuln-devat_private > Subject: Windows XP mmc.exe Crash > > > > I found a way to crash mmc.exe in my windowsxp profesional > SP1 b0x maybe > others systems afected. I dont know if this can be used to > execute code so > please take a look. > > steps: > first, execute Control Pannel / Administrative Tools / > Computer Managment or > just type into cmd.exe "%SystemRoot%\system32\compmgmt.msc /s" > > then right click and select connect to remote computer, an > type at least > 100chars ( AAAAAAAAAAAAA.. ) > mmc.exe will warn you that the remote computer > \\AAAAAAAAAA.... was not > found. Now, right click again and > select propierties. > > mmc.exe crash. > > > > aT4r [at] 3wdesign.es Security (c) > > _________________________________________________________________ > Multiplica por cinco el tamaño de tu buzón de correo y envía > adjuntos de > hasta 2 Mb con MSN Almacenamiento Extra. > http://join.msn.com/?pgmarket=es-es > >
This archive was generated by hypermail 2b30 : Wed Apr 30 2003 - 14:52:15 PDT