It's total crap. There are two malloc calls in one of the files, but no free calls anywhere. Meaning that you leak memory every time the code gets called. Also, there are all sorts of unchecked string calls; the writer seems to assume that any URL that gets passed in is at most 256 characters. Thus, there could be expolitable buffer overflows in the patch. Plus, I understand that the patch redirects people to the writer's web server when a possible attack is detected - this is a dubious practice, at best.
I'm no security expert, and know jack about Windows programming; does anyone understand the patch any better? |
