Timeline for SQL injection is 17 years old. Why is it still around?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 8, 2016 at 7:01 | comment | added | niilzon | The uneducated usually do. It reminds me of a post on this very site, where a student was having issues with queries. I showed him how to made the code work, and pointed out that it was SQLi-prone, suggesting to refactor the code with PreparedStatements. His answer was "but it is just for a class exercise, this code won't be reused, I don't care". This is the kind of attitude we must fight against. Coding as properly as possible on all occasions is important, especially if you don't highly master what you are doing. | |
| Jun 29, 2016 at 14:45 | comment | added | Stephan | Sometimes, some developers underestimate the risk of SQLi. | |
| Jun 29, 2016 at 11:18 | history | answered | niilzon | CC BY-SA 3.0 |