[dead]
Meh. Even smart people do dumb things with languages other than PHP.
Any language with string interpolation can create sql injection vulnerabilities, for example. PHP's docs encourage the right pattern, as do Ruby's, but... https://github.com/gitlabhq/gitlabhq/issues/2464
Re:Simply Secure PHP Cryptography
by peterwwillis on Thursday July 13, 2017 @07:44PM
(#14766265)
There are best practices for handling dynamite, too, but I wouldn't build a safe with it.
Nobody should be writing code that queries databases using tainted strings. Perl has had a taint mode for almost 30 years. Ruby supposedly has a taint mode, but I'm not a Ruby dev so I don't know how it affects the vuln you mention.
3/4 of the Perl scripts I have audited have had bad input sanitation in front of open() or exec(). I'll take SQLi over RCE any day.
Re:Simply Secure PHP Cryptography
by peterwwillis on Thursday July 13, 2017 @08:40PM
(#14766576)
....so enable Taint mode and fix the errors? And why would you think your code is vulnerable to SQLi and not RCE, or any other user input-related exploit?
Was that a typo? Serious question.