


Authentication: If poor SQL commands are used to check user names and passwords, it may be possible to connect to a system as another user with no previous knowledge of the password.Confidentiality: Since SQL databases generally hold sensitive data, loss of confidentiality is a frequent problem with SQL Injection vulnerabilities.The data is used to dynamically construct a SQL query.An unintended data enters a program from an untrusted source.See the OWASP Article on using SQL Injection to bypass a WAF Description How to Bypass Web Application Firewalls with SQLi See the OWASP Testing Guide for information on testing for SQL Injection vulnerabilities. How to Test for SQL Injection Vulnerabilities See the OWASP Code Review Guide article on how to Review Code for SQL Injection vulnerabilities. How to Review Code for SQL Injection Vulnerabilities See the OWASP Query Parameterization Cheat Sheet.

See the OWASP SQL Injection Prevention Cheat Sheet. Related Security Activities How to Avoid SQL Injection Vulnerabilities In general, consider SQL Injection a high impact severity. The severity of SQL Injection attacks is limited by the attacker’s skill and imagination, and to a lesser extent, defense in depth countermeasures, such as low privilege connections to the database server and so on.Due to the nature of programmatic interfaces available, J2EE and ASP.NET applications are less likely to have easily exploited SQL injections.

