Page History

This guide will describe the SQL injection attack in more detail. 

Contents: 

SQL Injection (CWE-89)

Any SQL -Injection injection attack basically consists of insertion (or “injection”) of malicious code within the SQL command executed by the app. 

Effects of such malicious code injections can be unpredictable, depending on the attacker’s intelligence and SQL-interpreter’s characteristics, but the most common are:

• Read/modify sensitive data
• Execute administrative operations
• Execute commands on the underlying OS

Let’s suppose an app that display displays the user’s data based on the user’s name as typed from the application user in a web form.

Dynamically constructed SQL in-app code might be something as look something like: 

"select * from users where name = '" + userName + "'";

userName is user-supplied data that is directly inserted into the query and it will be sent to SQL-engine to be executed.

Let’s imagine the result when the attacker supplies next the following text:

' or '1'='1

In  In this case, sqlSQL-engine will return all users’ data because 1=1 will always be TRUE.

This attack would the attacker be able to access users’ data (involving a privacy breach), but consequences can be more serious combining query chaining with administrative commands such as

 Smith';drop table users; truncate audit_log;--

In this case, the attacker would be able to delete the users table or truncate system tables. Everything depends on the concrete case, but “the door is open” and, as you can imagine, imagination is the limit. How does the attacker know the app database tables? Depending on the error messages the application produces when a SQL - injection attack happens, a smart attacker might be “inferring” database structure information from the error page. It’s Discovering useful information is a matter of patience to discover useful information.

You could be thinking on of a common app error management approach consisting on of providing a generic error page, not displaying any exploitable information about the app’s internals.

Even in this case, the app is still vulnerable to sql-SQL injection. In these cases, attackers Attackers can use a technique known as “Blind SQL Injection”injection.

This hacking technique is based on asking the database questions and determines the answer based on the applications application's response. This attack is often used when the web application is configured to show generic error messages , but has not mitigated the code that is vulnerable to SQL injection.

Some variants of SQL -Injection injection apply to specific frameworks or conditions:

• CWE-564: SQL Injectioninjection: Hibernate
• CWE-566: Authorization Bypass Through User-Controlled SQL Primary Key

You can find Find further information on SQL Injection injection at https://www.kiuwan.com/blog/sql-SQL injection-avoid/

SQL

injection (CWE-89) coverage by Kiuwan

Kiuwan incorporates next the following rules for SQL -Injection injection (CWE-89) for the following languages.

Please, visit the documentation page for every rule to obtain detailed information on functionality, coverage, parameterization, remediation, example codes, etc.

:

To read more detailed information about the rule on functionality, coverage, parameterization, remediation, example codes, etc., do the following: 

1. Log into your Kiuwan Account
2. Go to Models Management 
   Image Added
3. Select Rules from the upper menu
   Image Added
4. Search for the CWE rule in the Tag field
   Image Added
5. Click on the question mark
   Image Added
6. A new window will open with more detailed information about the rule
   Image Added