Database queries should not be vulnerable to injection attacks

User provided data, such as URL parameters, should always be considered untrusted and tainted. Constructing SQL queries directly from tainted data enables attackers to inject specially crafted values that change the initial meaning of the query itself. Successful database query injection attacks can read, modify, or delete sensitive information from the database and sometimes even shut it down or execute arbitrary operating system commands.

Typically, the solution is to use prepared statements and to bind variables to SQL query parameters with dedicated methods like setParameter, which ensures that user provided data will be properly escaped. Another solution is to validate every parameter used to build the query. This can be achieved by transforming string values to primitive types or by validating them against a white list of accepted values.

See

• OWASP SQL Injection Prevention Cheat Sheet
• OWASP Top 10 2017 Category A1 - Injection
• MITRE, CWE-89 - Improper Neutralization of Special Elements used in an SQL Command
• MITRE, CWE-20 - Improper Input Validation
• MITRE, CWE-943 - Improper Neutralization of Special Elements in Data Query Logic
• CERT, IDS00-J. - Prevent SQL injection
• SANS Top 25 - Insecure Interaction Between Components