[Full-disclosure] Re: Session data pollution vulnerabilities inweb applications

["Dave Korn" <davek_throwaway@xxxxxxxxxxx>]

Frank Knobbe wrote in 1137084647.25372.13.camel@localhost">news:1137084647.25372.13.camel@localhost
>These type of bugs stem from bad program design. (BTW: I wouldn't call
>it session data pollution... your not polluting anything).

  Yes he is.  He's polluting sanitized data with tainted data.  It's a 
fairly reasonable description if you ask me.

> The proposed fix is -- besides being only specific to this example --
>equally flawed. The underlying issue is that you trust user supplied
>data.

  NO!  You've /completely/ failed to understand the post.

  The underlying issue is not that the user-supplied data is trusted, 
because it isn't, it gets validated.  The _underlying_ issue is that the 
*same* location is used to store both trusted and non-trusted data, and 
there's no way for the application to know which kind of data was last 
stored in that location.

    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/