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] [day] [month] [year] [list]

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

At 06:23 PM 12/25/2004, Valdis.Kletnieks@...edu wrote:

>I smell blood in the water - the sharks will be here soon... ;)

Well, of COURSE they will. Unlike the lazy dudes at Microsoft, no self-respecting 
worm or spyware author would goof off on Christmas when there was such a tempting
vulnerability to exploit. I expect to see half a dozen worms, spyware programs,
"phishing" spams, and hacked Web sites to be infecting users within the week.

What's more, McAfee and Symantec say that they won't be automatically updating
users' machines to block exploits (Some? All? Who knows?) until the 29th. (I realize 
that antivirus vendors have an incentive to allow a delay before they update their 
patterns, because a rash of infections can help business.... However, this is 
downright irresponsible.)

Which is why I'd like to capture the API entry point and put in the bounds
check that should have been there in the first place. Alas, I don't have the
Windows programming tools to do it here, so I'm looking for a bit of help.

--Brett