bugtraq - RE: Unchecked buffer in mstask.dll

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.SGI.4.10.10407161109410.1328-100000@Sky.inp.nsk.su>
Date: Fri, 16 Jul 2004 11:22:28 +0700
From: "Dmitry Yu. Bolkhovityanov" <D.Yu.Bolkhovityanov@....nsk.su>
To: Paul Szabo <psz@...hs.usyd.edu.au>
Cc: bugtraq@...urityfocus.com, full-disclosure@...ts.netsys.com,
   tlarholm@...x.com, brett.moore@...urity-assessment.com
Subject: RE: Unchecked buffer in mstask.dll

On Thu, 15 Jul 2004, Paul Szabo wrote:

> Being curious, on Win2k, I copied cmd.exe (from winnt\system32) as xyz.pif;
> then (right-click) Properties, Program crashes explorer. Is this related to
> IconHandler, and is it exploitable?

	Right -- in Win2K SP4 clicking on [Program] tab of Properties
window causes "access violation" -- the memory at 0x00000000 could not be
"read" by SHELL32.DLL.  MSVC++, acting as a debugger, shows a mixture of
KERNEL32, COMCTL32, USER32, SHELL32 and SHLWAPI in stack trace.

	Disassembly window shows that there was an attempt to read dword
at [EAX] (EAX=0).  So at first glance this doesn't seem to be trivially
exploitable, but I'm not a win32 expert, and intuition suggests that there
must be a way.

	_________________________________________
	  Dmitry Yu. Bolkhovityanov
	  The Budker Institute of Nuclear Physics
	  Novosibirsk, Russia

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html