Re:Innovative way to combat SQL injection
by gluejar on Thursday May 13, 2010 @04:32PM
(#1345559)
In case you have any confusion about this, please note that the term "Innovative" is used here to mean "likely to cause Hacker News readers to spew soda out their noses".
Re:Innovative way to combat SQL injection
by megablast on Thursday May 13, 2010 @06:42PM
(#1345952)
It is possible that they server is not given access to these functions, so they didn't need to be checked for, in the input.
This presents its own problems, if for some reason in the future they need to add one of these missing functions to the servers access, and don't recognise that they need to add the check as well.
But anyway, it is great to see the boss' nephew getting some work.
Re:Innovative way to combat SQL injection
by tptacek on Thursday May 13, 2010 @07:01PM
(#1345984)
They aren't using instructions to users to block SQL Injection. They're using a web application firewall to block SQL Injection, and they have it configured to take a shotgun approach to filtering form fields.
You could do the same thing with any application, secure or not, by applying a naive mod_security configuration to your Apache server.
That's not a great practice, but it doesn't tell you anything about how susceptible they are to SQLI.
Re:Innovative way to combat SQL injection
by rm-rf on Friday May 14, 2010 @09:16AM
(#1347233)
It may not be a direct indicator of their vulnerability to SQL injection, but it is a pretty good indicator of their placement on the clulessness scale.
We where laughing our asses of. My name and the name of the other in-house guy, both contain an 'and'. Just our boss, could login and had no problem. :)
Re:Innovative way to combat SQL injection
by petercooper on Thursday May 13, 2010 @06:27PM
(#1345915)
Except, the bad code as shown requires whitespace (\s) before and after the "bad" terms, so the names the Daily WTF post mentions should pass through it.
if (preg_match('/\s['.implode('|',$badSqlCode).']+\s/i', $sqlcode))
They probably didn't realize this wouldn't catch any of the bad terms at the very start or end of their code, though :-)
Re:Innovative way to combat SQL injection
by MartinCron on Thursday May 13, 2010 @06:37PM
(#1345939)
I'm guessing that they aren't using "honor-system SQL Injection protection", but they are hard-blocking all of that in the UI layer, which is not a terrible thing to do, but not the most sophisticated and user-friendly approach.
After they got a handful of calls about it, they had to put it in their FAQ.
Re:Innovative way to combat SQL injection
by PonyGumbo on Friday May 14, 2010 @09:08AM
(#1347222)
My bank recently dumped their .NET online banking system for what appears to be a homebrew job in "classic" ASP. I'm sure they had a good reason, but from the outside it certainly seems like an odd decision.
Re:Innovative way to combat SQL injection
by liedra on Friday May 14, 2010 @03:21AM
(#1346792)
Oh, and the time when my bank's netbank SSL certificate expired, and it took them 3 days to get it fixed because it seemed noone knew what was going on... that was great! lol.
This presents its own problems, if for some reason in the future they need to add one of these missing functions to the servers access, and don't recognise that they need to add the check as well.
But anyway, it is great to see the boss' nephew getting some work.
What it does is generate stupid alarms and break pageflows when you have an improperly configured web filter.
You could do the same thing with any application, secure or not, by applying a naive mod_security configuration to your Apache server.
That's not a great practice, but it doesn't tell you anything about how susceptible they are to SQLI.
clueless<-------------------->cluefull
Right about here I'd say.http://thedailywtf.com/Articles/Injection_Rejection.aspx
We where laughing our asses of. My name and the name of the other in-house guy, both contain an 'and'. Just our boss, could login and had no problem. :)
After they got a handful of calls about it, they had to put it in their FAQ.
Sorry, I just killed the joke.