Re:Sqlmap: Automatic SQL injection and database takeover tool
by bni on Thursday July 05, 2012 @01:57PM
(#4204089)
How about a black listing solution? commit block on anything containing the full word "Statement" (or equivalent in in your language of choice).
Also code review, of which there will be need for plenty, when bare minimum developers is involved.
Re:Sqlmap: Automatic SQL injection and database takeover tool
by j_s on Thursday July 05, 2012 @02:19PM
(#4204209)
For the record, it's my understanding that white-listing is normally better than black-listing. I didn't mean that white-listing wasn't the best option, just that it sounded like it was being used.
I've implemented a [complex?] white-listing solution to a problem in a domain where there is a long history of developer mistakes, passing user input to a 3rd-party technology most developers only know the minimum required for their job. Isn't injection impossible?
Edit: Sorry for any confusion; this was my way of saying 'this is only bulletproof if you got every edge case 100% right; few security experts make guarantees of impossibility of failure'.