full-disclosure - Session data pollution vulnerabilities in web 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 for Android: free password hash cracker in your pocket

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

Date: Thu Jan 12 16:52:45 2006
From: email-fulldisclosure at hotmail.com (mailinglist mailinglist)
Subject: Session data pollution vulnerabilities in web
	applications

Hi Alla Bezroutchko,

Good recommendations.

This is not new - my guess, it's old. I have noted a few scripts/examples 
vulnerable to this previously, and would guess that we are not alone to have 
seen it before. "Yet another bad way to code PHP / ASP / Whatever" (TM).

But I never noticed the subtle variant you describe (perhaps since I never 
looked for it!), but a much more general/stupid variant:

$var = $_GET["something"];
$_SESSION["$var"] = $var2;

Yes. People do really code like that. Noted that one in some example posted 
in some php forum.

Anyway, there are probably a quite a lot of scripts which are vulnerable to 
this issue if php.ini is misconfigured (register_globals = on).  Then we get 
the classic "if value not assigned, request parameter value will be 
injected" scenario which allready is known to enable several SQL Injections.

if (condition1) {
$var = 'SOMETHING';
}
if (condition2) {
$var = 'OTHER';
}
$_SESSION["$var"] = $var2;

Regards,
/someone

_________________________________________________________________
Hitta r?tt p? n?tet med MSN Search http://search.msn.se/