News for hackers. Stuff that matters.
Re:GitHub Enterprise SQL Injection by tyingq on Sunday January 08, 2017 @10:55AM (#13350222)
Basically any language that has easy string interpolation and takes SQL via a string has this as a potential issue.

The implementations across languages are remarkably similar, I suppose due to the lineage of the original C apis from the various DB vendors.

I don't see any easy way to fix it. If it's possible, and easy to do, it will keep happening.

Re:GitHub Enterprise SQL Injection by bkor on Sunday January 08, 2017 @03:19PM (#13351740)
Perl has a tainted mode where any outside data is marked as tainted. You can only detained it in specific ways. Copying the data from one variable to another keeps the tainted flag.

Pretty much only explicit checks are able to remove the tainted flag from the data. As such you limit the security problems to faulty checks. It is impossible to forget to check something.

Above is used in Bugzilla. Despite all of that, it's still pretty easy to make mistakes. IMO it's rather unfortunate that not more languages have such a feature. This as Perl code if often pretty difficult to read (it doesn't have to be!).

Re:GitHub Enterprise SQL Injection by Illniyar on Monday January 09, 2017 @02:27AM (#13354643)
wow, that's a really great idea. I'm surprised that other languages or even frameworks haven't picked that up.

Maybe it can be pitched to Rust.

Re:GitHub Enterprise SQL Injection by jacobr1 on Monday January 09, 2017 @11:18AM (#13357416)
A lot of frameworks have picked up the notion of "html safe" strings. But this is generally limited html escaping and display rather than SQL.