169 – Use parameterized queries

Summary

The system must use parameterized queries or stored procedures to create dynamic sentences (e.g., java.sql.PreparedStatement).

Description

One of the main reasons for using parameterized queries or stored procedures is to prevent SQL injection attacks. When applications concatenate user input directly into SQL statements, attackers may inject malicious SQL code, potentially leading to unauthorized access or data manipulation. Parameterized queries ensure that user input is treated as data, not as executable code, mitigating the risk of SQL injection.

Supported In

Essential: True

Advanced: True

References

• CAPEC-7. Blind SQL injection
• CAPEC-248. Command injection
• CWE-89. Improper neutralization of special elements used in an SQL command ("SQL injection")
• CWE-130. Buffer copy without checking size of input ("classic buffer overflow")
• CWE-598. Use of GET request method with sensitive query strings
• OWASP10-A3. Injection
• AGILE-9. Continuous attention to technical excellence and good design
• BIZEC-APP-02. OS command injection
• BIZEC-APP-06. Direct database modifications
• BIZEC-APP-08. Open SQL injection
• CERTJ-IDS00-J. Prevent SQL injection
• MITRE-M1013. Application developer guidance
• PADSS-5_2_1. Injection flaws, particularly SQL injection
• SANS25-3. Improper neutralization of special elements used in an SQL command (SQL injection)
• WASSEC-5_5. Extraction of dynamic content
• WASSEC-6_2_4_4. Command execution - SQL injection
• WASC-A_19. SQL injection
• WASC-W_20. Improper input handling
• ISSAF-T_6_6. Web application assessment - Identifying web server vendor and version (by error)
• ISSAF-T_17. Web application assessment - Test SQL injection
• ISSAF-U_15. Web application SQL injections – Countermeasures
• PTES-5_2_3_1. Vulnerability analysis - Web application scanners (application flaw scanners)
• PTES-7_4_2_3. Post exploitation - Pillaging (database servers)
• OWASPSCP-11. Database security
• CWE25-89. Improper neutralization of special elements used in an SQL command (SQL injection)
• ASVS-5_3_4. Output encoding and injection prevention
• PCI-6_2_4. Software engineering techniques to prevent or mitigate common software attacks
• ASVS-5_3_5. Output encoding and injection prevention
• CASA-5_3_4. Output Encoding and Injection Prevention
• OWASPMASVS-CODE-4. The app validates and sanitizes all untrusted inputs

Weaknesses

• 105 – Apache lucene query injection
• 106 – NoSQL injection
• 112 – SQL injection - Java SQL API
• 146 – SQL injection
• 154 – Time-based SQL Injection
• 155 – SQL Injection - Headers
• 297 – SQL injection - Code
• 438 – Error-based SQL Injection
• 450 – Blind-based SQL injection
• 451 – OData injection
• 001 – SQL injection - C Sharp SQL API
• 012 – SQL injection - Java Persistence API

Last updated

2024/01/18