Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
Re: [Full-Disclosure] Re: Re: Microsoft Windows LoadImage API Integer Buffer overflow
From: Brett Glass (brettlariat.org)
Date: Sat Dec 25 2004 - 22:43:40 CST
At 06:23 PM 12/25/2004, Valdis.Kletnieksvt.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
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.
Full-Disclosure - We believe in it.