eBay remote code execution
secalert.net
eBay remote code execution
1–10 of 17 posts
Re: eBay remote code execution
#2I wonder if doing "$cast = (string) $input" prior to the rest will avoid it? I do things like that, as well as making sure all methods use type hinting, which would hopefully make this harder?
Re: eBay remote code execution
#3Re: eBay remote code execution
#4Presumably the bounty was distributed without incident which is worth noting the recent threads of bounties being forfeited.
Re: eBay remote code execution
#5Re: eBay remote code execution
#6$a = '{${phpinfo()}}'; $b = [$a]; $c = "$b";
Will execute phpinfo()... which it won't.
Re: eBay remote code execution
#7I'm pretty sure the error is when they later take the input and eval it, and the author's managed to dodge their filtering rather than execute arbitrary code in the context of an array-to-string cast (which I was lead to believe when reading that post, at least). Otherwise it implies that some permutation of: $a = '{${phpinfo()}}'; $b = [$a]; $c = "$b"; Will execute phpinfo()... which it won't.
$variable = "{${phpinfo()}}";
echo "$variable is fish";
I feel I've missed the point.Re: eBay remote code execution
#8I'm curious if corporations like ebay respond with a grateful "thank you" or rather threaten to throw you in prison?
Re: eBay remote code execution
#9I'm pretty sure the error is when they later take the input and eval it, and the author's managed to dodge their filtering rather than execute arbitrary code in the context of an array-to-string cast (which I was lead to believe when reading that post, at least). Otherwise it implies that some permutation of: $a = '{${phpinfo()}}'; $b = [$a]; $c = "$b"; Will execute phpinfo()... which it won't.
I'm not quite sure I understand it either, though this does execute phpinfo. $variable = "{${phpinfo()}}"; echo "$variable is fish"; I feel I've missed the point.
Re: eBay remote code execution
#10I'm pretty sure the error is when they later take the input and eval it, and the author's managed to dodge their filtering rather than execute arbitrary code in the context of an array-to-string cast (which I was lead to believe when reading that post, at least). Otherwise it implies that some permutation of: $a = '{${phpinfo()}}'; $b = [$a]; $c = "$b"; Will execute phpinfo()... which it won't.
I'm not quite sure I understand it either, though this does execute phpinfo. $variable = "{${phpinfo()}}"; echo "$variable is fish"; I feel I've missed the point.
$variable = "{${phpinfo()}}"; //
If you pass a "{${phpinfo()}}" via GET, it is not executed. The execution has to happen later - e.g. by eval() or /e.