[Full-disclosure] Re: Buffer overflow vulnerability in dsocks

["Dave \"No, not that one\" Korn" <davek_throwaway@xxxxxxxxxxx>]

Michael Adams wrote:
> A buffer overflow in variable 'buf' exists due to insufficient
> validation of variable 'name' in function tor_resolve line 218 of
> software at http://www.monkey.org/~dugsong/dsocks/

  At a quick glance, this looks like it could indeed be overflowed quite
trivially by passing an overlong name to any of the host lookup functions
proxied by dsocks.  It therefore seems that it could quite easily be
triggered remotely by, for example, a web page with an include/iframe using
an overlong URL.

  I would advise anyone currently using dsocks to click here:

http://foo.12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890.AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAveryverylongname.com.invalid/

and if they crash their dsocks-enabled web-browser, to stop using it very
quickly indeed.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....




_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/