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 20:30:39 2006
From: frank at knobbe.us (Frank Knobbe)
Subject: Re: Session data pollution vulnerabilities
	inweb applications

On Thu, 2006-01-12 at 19:18 +0000, Dave Korn wrote:
>   Yes he is.  He's polluting sanitized data with tainted data.  It's a 
> fairly reasonable description if you ask me.

I didn't see any sanitized data. It's a POST input, not something clean
and trusted.

>   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. 

Where did that happen? I haven't seen a validation in his example.

>  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.

You're not telling me that $_POST['login'] is trusted data, are you?

-Frank

-- 
It is said that the Internet is a public utility. As such, it is best
compared to a sewer. A big, fat pipe with a bunch of crap sloshing
against your ports.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20060112/b088637b/attachment.bin