full-disclosure - Re: Session data pollution vulnerabilities inweb applications

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Thu Jan 12 19:20:03 2006
From: davek_throwaway at hotmail.com (Dave Korn)
Subject: Re: Session data pollution vulnerabilities inweb
	applications

Frank Knobbe wrote in news:1137084647.25372.13.camel@...alhost
>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....