full-disclosure - Re: Re: Microsoft Windows LoadImage API Integer Buffer overflow

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <6.2.0.14.2.20041225123311.0611b7b8@localhost>
From: brett at lariat.org (Brett Glass)
Subject: Re: Re: Microsoft Windows LoadImage API Integer
	Buffer overflow

I don't see why one would need a script to exploit the hole.

In any event, I'd like to shim the API to catch this bug, since the fat and sassy millionaire
monopolists at Microsoft are unlikely to get off their derrieres to fix the bug during
Christmas. Unfortunately, it's part of a big system DLL with tons of entry points. How best to 
shim it?

--Brett

At 07:19 PM 12/24/2004, flashsky wrote:

>    This vul can be exploited, at http://www.xfocus.net/flashsky/icoExp/index.html ,i give a test exp(open 28876 port) for windows xp sp1, but it need html sctipt run and allocate memory.