News for hackers. Stuff that matters.

A comment on Exec($_GET.

Re:Exec($_GET by WestCoastJustin on Tuesday April 29, 2014 @02:30AM (#7665347)
As a side note, this is how many SQL injection attacks happen too. You almost never want unfiltered user input to directly interact with your system. A while back, I did an episode on how SQL injection can lead to code execution by using unfiltered user input on a LAMP stack. See it @ http://sysadmincasts.com/episodes/21-anatomy-of-a-sql-inject...
[ Parent | on HN ]
Re:Exec($_GET by ASneakyFox on Tuesday April 29, 2014 @04:32AM (#7665722)
Side side note. This same carelessness is what caused the heart bleed bug.
[ Parent | on HN ]
Re:Exec($_GET by Kim_Bruning on Tuesday April 29, 2014 @04:50AM (#7665763)
Well, in a sense maybe, but not on purpose there. The programmer had missed a bounds check.
[ Parent | on HN ]
Re:Exec($_GET by ASneakyFox on Thursday May 01, 2014 @05:21AM (#7678894)
I think you're giving him too much credit. The input was not sanitized. Now its no one programmers fault. It was a long living bug many had a chance to see it and correct it for a long time. It was rooted in the same carelessness as exec(GET)
[ Parent | on HN ]