The first public discussions of SQL injection started appearing around 1998. SQL injection (SQLI) is considered one of the top 10 web application vulnerabilities of 2007 and 2010 by the Open Web Application Security Project. In 2013, SQLI was rated the number one attack on the OWASP top ten. Recent infamous victims of SQL Injection Attacks: Barracuda Networks, Heartland Payment Systems, NASA, Bell (Canada) & Many More.
SQL Injection Attack Threat Modeling
SQL injection errors occur when data enters a program from an untrusted source and the data used to dynamically construct a SQL query
- SQL Injection attack allow attackers to spoof identity, tamper with existing data, cause repudiation issues such as voiding transactions or changing balances, allow the complete disclosure of all data on the system, destroy the data or make it otherwise unavailable, and become administrators of the database server.
- SQL Injection is very common with PHP and ASP applications due to the prevalence of older functional interfaces. Due to the nature of programmatic interfaces available, J2EE and ASP.NET applications are less likely to have easily exploited SQL injections.
- The severity of SQL Injection attack 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. In general, consider SQL Injection a high impact severity.
Below infographic from Barricade will explain you about what is SQL Injection attack, how does it works.
There are four different types SQL Injection attack, Classic SQLI, Blind or Inference SQL injection, Database management system-specific SQLI and Compounded SQLI. We will explain it in details later. And we will also write an article about how to avoid SQL Injection vulnerabilities.