Full Disclosure mailing list archives
Re: Re: Re: Microsoft Windows LoadImage API Integer Buffer overflow
From: Brett Glass <brett () lariat org>
Date: Sat, 25 Dec 2004 21:43:40 -0700
At 06:23 PM 12/25/2004, Valdis.Kletnieks () vt 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 _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
Current thread:
- Re: Re: Microsoft Windows LoadImage API Integer Buffer overflow Brett Glass (Jan 06)
- Message not available
- Re: Re: Re: Microsoft Windows LoadImage API Integer Buffer overflow Brett Glass (Jan 06)
- Message not available