SQLi Cheatsheet
SQL injection cheat sheet
This SQL injection cheat sheet contains examples of useful syntax that you can use to perform a variety of tasks that often arise when performing SQL injection attacks.
String concatenation
You can concatenate together multiple strings to make a single string.
Oracle |
|
Microsoft |
|
PostgreSQL |
|
MySQL |
|
Substring
You can extract part of a string, from a specified offset with a specified length. Note that the offset index is 1-based. Each of the following expressions will return the string ba
.
Oracle |
|
Microsoft |
|
PostgreSQL |
|
MySQL |
|
Comments
You can use comments to truncate a query and remove the portion of the original query that follows your input.
Oracle |
|
Microsoft |
|
PostgreSQL |
|
MySQL |
|
Database version
You can query the database to determine its type and version. This information is useful when formulating more complicated attacks.
Oracle |
|
Microsoft |
|
PostgreSQL |
|
MySQL |
|
Database contents
You can list the tables that exist in the database, and the columns that those tables contain.
Oracle |
|
Microsoft |
|
PostgreSQL |
|
MySQL |
|
Conditional errors
You can test a single boolean condition and trigger a database error if the condition is true.
Oracle |
|
Microsoft |
|
PostgreSQL |
|
MySQL |
|
Extracting data via visible error messages
You can potentially elicit error messages that leak sensitive data returned by your malicious query.
Microsoft |
|
PostgreSQL |
|
MySQL |
|
Batched (or stacked) queries
You can use batched queries to execute multiple queries in succession. Note that while the subsequent queries are executed, the results are not returned to the application. Hence this technique is primarily of use in relation to blind vulnerabilities where you can use a second query to trigger a DNS lookup, conditional error, or time delay.
Oracle |
|
Microsoft |
|
PostgreSQL |
|
MySQL |
|
Note
With MySQL, batched queries typically cannot be used for SQL injection. However, this is occasionally possible if the target application uses certain PHP or Python APIs to communicate with a MySQL database.
Time delays
You can cause a time delay in the database when the query is processed. The following will cause an unconditional time delay of 10 seconds.
Oracle |
|
Microsoft |
|
PostgreSQL |
|
MySQL |
|
Conditional time delays
You can test a single boolean condition and trigger a time delay if the condition is true.
Oracle |
|
Microsoft |
|
PostgreSQL |
|
MySQL |
|
DNS lookup
You can cause the database to perform a DNS lookup to an external domain. To do this, you will need to use Burp Collaborator to generate a unique Burp Collaborator subdomain that you will use in your attack, and then poll the Collaborator server to confirm that a DNS lookup occurred.
Oracle | (XXE) vulnerability to trigger a DNS lookup. The vulnerability has been patched but there are many unpatched Oracle installations in existence:
The following technique works on fully patched Oracle installations, but requires elevated privileges:
|
Microsoft |
|
PostgreSQL |
|
MySQL | The following techniques work on Windows only:
|
DNS lookup with data exfiltration
You can cause the database to perform a DNS lookup to an external domain containing the results of an injected query. To do this, you will need to use Burp Collaborator to generate a unique Burp Collaborator subdomain that you will use in your attack, and then poll the Collaborator server to retrieve details of any DNS interactions, including the exfiltrated data.
Oracle |
|
Microsoft |
|
PostgreSQL |
|
MySQL | The following technique works on Windows only:
|
Last updated