====== Hacking - SQL Injection (SQLi) ======

All SQL Injection is due to dynamic SQL queries.

Strongly consider prohibiting dynamic SQL queries completely.

Injection flaws occur when an application sends untrusted data to an interpreter.

Injection flaws are very prevalent, particularly in legacy code.

They are often found in SQL, LDAP, Xpath, or NoSQL queries; OS commands; XML parsers, SMTP Headers, program arguments, etc.

Injection flaws are easy to discover when examining code, but frequently hard to discover via testing.

Scanners and fuzzers can help attackers find injection flaws.

----

[[Hacking:SQL Injection:Basic types of SQL injections|Basic types of SQL injections]]

[[Hacking:SQL Injection:Check if a website is vulnerable to SQL Injection|Check if a website is vulnerable to SQL Injection]]

[[Hacking:SQL Injection:Example attacks|Example attacks]]

[[Hacking:SQL Injection:False measures and bad practices|False measures and bad practices]]

[[Hacking:SQL Injection:Oracle|Oracle]]

[[Hacking:SQL Injection:PostgreSQL|PostgreSQL]]

[[Hacking:SQL Injection:MSSQL|MSSQL]]

[[Hacking:SQL Injection:MySQL|MySQL]]

[[Hacking:SQL Injection:What is SQL Injection|What is SQL Injection]]

[[Hacking:SQL Injection:Why not to use escape quotes as a defence|Why not to use escape quotes as a defence]]

----

[[Hacking:SQL Injection Cheat Sheet (DB2)|SQL Injection Cheat Sheet (DB2)]]

[[Hacking:SQL Injection Cheat Sheet (Informix)|SQL Injection Cheat Sheet (Informix)]]

[[Hacking:SQL Injection Cheat Sheet (MSSQL)|SQL Injection Cheat Sheet (MSSQL)]]

[[Hacking:SQL Injection Cheat Sheet (ORACLE)|SQL Injection Cheat Sheet (ORACLE)]]

[[Hacking:SQL Injection Cheat Sheet (PostgreSQL)|SQL Injection Cheat Sheet (PostgreSQL)]]