Understanding SQL Injection

  • 8 March 2021
  • 1 min read

What is SQL Injection (SQLi)?

SQL injection is a web security vulnerability that allows an attacker to interfere with the queries that an application makes to database. The attacker can create input content, such content is often called a malicious payload. After the attacker uploads this content, malicious SQL commands are executed in the database. It generally allows an attacker to see data that they are not allowed to access. This data might be personal information of users, or any other data that application itself is able to access.

How dangerous are SQL Injections?

A successful SQL injection attack may compromise a system or the entire database, information such as passwords, credit card details, or personal user information can be exfiltrated. Many high-profile data breaches in recent years have been the result of SQL injection attack, leading to reputational damage.

Types of SQL Injections

SQL injection can be classified into three major categories

  1. In-band SQLi

  • Error-based SQLi

  • Union-based SQLi

2. Inferential SQLi

  • Boolean-based Blind SQLi

  • Time-based Blind SQLi

3. Out-band SQLi

How to detect SQL Injections

SQL injection can be detected manually by using a systematic set of tests against every entry point in the application and also can be done by using automation tools such as DAST tool (Dynamic Application Security Testing), Burp suite, etc. The majority of SQL injection vulnerabilities can be found quickly by using Burp Suite’s Web Vulnerability Scanner.

Need your application to be trusted by millions? Contact us regarding application security testing at contact@nexixsecuritylabs.com

Your Security | Our Concern

All research

Cookie preferences

Choose what this site may store on your device. Your choice is remembered for six months and you can change it any time from the footer. Nothing in the optional categories is stored until you turn it on.

Always active

Needed for the site to work and to remember this choice. It is a single first-party cookie recording which categories you allowed. It carries no identifier and is never sent to anyone else.

Google Analytics and PostHog, so we can see which pages are read and where people give up. This is what lets us recognise one visit across several pages instead of counting every page as a new person. Records are anonymous — we never attach your name or email, and form fields are masked before anything is recorded.

Lets Google measure whether an ad we paid for led to an enquiry, and build audiences for future campaigns. Turning this off does not change what you see on this site.