Taras, On Sun, Nov 15, 2009 at 12:27 PM, Taras <ta...@securityaudit.ru> wrote: > Andres, > >> Yes, a lot of sense to me in the case of the fuzzing, but not that >> much sense on the side of "finding a vulnerability" trying to send a >> request with maxlength-1 , maxlength, maxlength+1. Why not sending >> directly maxlength+whatever and see what happens? > > What about complex JavaScript client side checks? > Such maxlength check can be made on JavaScript. > And I think in most cases such checks will be on JavaScript because > simply it more powerful then HTML attributes like maxlength.
Adding support for maxlength field in HTML can be done in 8 hours of work (at most). Adding support for javascript parsing/running/analyzing will take 8 days (at least). Which problem would you prefer to tackle first? ;) > > -- > Taras - OSCP, OSWP > ---- > "Software is like sex: it's better when it's free." - Linus Torvalds > -- Andrés Riancho Founder, Bonsai - Information Security http://www.bonsai-sec.com/ http://w3af.sf.net/ ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ W3af-develop mailing list W3af-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/w3af-develop
