# Sqlninja user manual

##

rel. svn-0.2.ff

This is the user manual of sqlninja, and you should have received it with the sqlninja tarball. Check http://sqlninja.sourceforge.net for the latest version.

## 1. Introduction

- 1.1 Requirements
- 1.2 Background
- 1.3 How to use it

## 2. Attack modes

- 2.1 test
- 2.2 fingerprint
- 2.3 bruteforce
- 2.4 escalation
- 2.5 resurrectxp
- 2.6 upload
- 2.7 dirshell
- 2.8 backscan
- 2.9 revshell
- 2.10 icmpshell
- 2.11 dnstunnel
- 2.12 metasploit
- 2.13 sqlcmd
- 2.14 getdata
- 2.15 Other attacks

## 3. Configuration file

- 3.1 Basic options
- 3.2 Data extration options
- 3.3 Advanced options

## 4. Other useful information

- 4.1 Credits
- 4.2 Disclaimer
- 4.3 Feedback
- 4.4 Wisdom
- 4.5 Authors

## 1. Introduction

Sqlninja's goal is to exploit SQL injection vulnerabilities on web applications that use Microsoft SQL Server as back end. It is released under the GPLv3.

Sqlninja's main goal is to get interactive OS-level access on the remote DB server and to use it as a foothold in the target network. As an experimental feature, it can also extract data from the database. In a nutshell, here's what it does:

- Fingerprint of the remote SQL Server (version, user performing the queries, user privileges, xp_cmdshell availability, DB Server authentication mode)
- Bruteforce of the 'sa' password (SQL Server 2000 only)
- Privilege escalation to 'sa' (SQL Server 2000 only)
- Creation of a custom xp_cmdshell if the original one has been disabled
- Upload of executables
- Reverse scan in order to look for a port that can be used for a reverse shell
- Direct and reverse shell, both TCP and UDP
- DNS tunneled pseudoshell, when no ports are available for a bindshell
- ICMP tunneled shell, if the target DBMS can communicate via ICMP Echo with the attacking machine
- Metasploit wrapping, when you want to use Meterpreter or even want to get GUI access on the remote DB server
- OS privilege escalation on the remote DB server using token kidnapping or through CVE-2010-0232
- Extraction of data from the remote DB, using WAITFOR-based inference or DNS-based tunnels
- All of the above can be done with obfuscated SQL code, in order to confuse IDS/IPS systems

As you probably have figured out, sqlninja does not look for SQL injection vulnerabilities. Again, there are already several tools that perform that task already, like BurpSuite.

For the latest release and two flash demos, check out the address http://sqlninja.sourceforge.net. The demos refer to a previous version but are still perfectly good to get a better understanding of the tool.

Read this manual carefully (yes, I mean all of it), as it will explain you what it is all about and how to make your way through all sqlninja options. Yes, I know that it's terribly long and boring, but since sqlninja has a plethora of options to play with (and no shiny green buttons), try to read the whole thing: it will help you to get the most of the tool and will save you a lot of time later.

## 1.1 Requirements

Since sqlninja is completely written in Perl, there is not much to install, except Perl itself and the following modules, if missing:

- NetPacket
- Net-Pcap
- Net-DNS
- Net-RawIP
- IO-Socket-SSL
- Net-Pcap
- DBI

You will also need the Metasploit Framework 3 on your box to use the metasploit attack mode, and also a VNC client if you use the VNC payload.

If something goes wrong, activating verbose output (`-v` option) and/or debugging (`-d`) should provide some hints. Developed on a Gentoo box, sqlninja has been reported to work on the following operating systems:

- Linux
- FreeBSD
- Mac OS X
- iOS

## 1.2 Background

Sometimes, when you find a SQL Injection vulnerability in a web application which uses SQL Server, it is all 2001 again: you find that your queries are run as 'sa', you verify that xp_cmdshell has not been disabled, then you make the server download netcat (via ftp or tftp) and finally obtain your direct or reverse shell. Most of the time, however, things are different: maybe the firewall filters all inbound/outbound connections, or a reverse shell is only allowed on some obscure service, or xp_cmdshell isn't there, or your queries are executed with low privileges. Or maybe all these things together ;). Sqlninja offers some help in getting the deserved remote shell even in these cases. And if that fails, it can still help you to squeeze some data out of the remote DBMS.

I am assuming that you have a good grasp of SQL Injection techniques and of Microsoft SQL Server internals. If you have trouble understanding what follows, I recommend you that you read this, this and this. I am also assuming you understand what protocol tunneling is, in particular over ICMP and DNS. If you don't, a good introduction to the concept for DNS is here.

## 1.3 How to use it

Sqlninja's behaviour is controlled via the configuration file (default: `sqlninja.conf`), which tells sqlninja what to attack and how (target host, vulnerable page, exploit strings, ...), and some command line options, which tell sqlninja what action to perform. These command line options are the following:

- -m <attack mode> : specifies the attack mode. Basically, tells sqlninja what to do. Possible values are:
  - test
  - fingerprint
  - bruteforce
  - escalation
  - resurrectxp
  - upload
  - dirshell
  - backscan
  - revshell
  - dnstunnel
  - icmpshell
  - metasploit
  - sqlcmd
  - getdata
- -v : verbose output
- -f <configuration file> : specifies a configuration file to use.
- -p <'sa' password> : used in escalation mode to add current DB user to the sysadmin group, and in other modes to run the query as administrator, if the DB user does not belong to such group. This option is rarely used, as bruteforce mode by default adds the DB user to the sysadmin group when the 'sa' password is found. For more information about when to use this parameter, refer to the escalation mode
- -w <wordlist> : wordlist to use in bruteforce mode
- -g : combined with upload mode, generate debug script and exit
- -d <debug mode> : activates debug, to see what is going on under the hood. Possible values are:
  - 1 : print each SQL command that is being injected
  - 2 : print each HTTP request that is sent to the target
  - 3 : print each HTTP response that is received from the target
  - all : all of the above

See the description of the various modes to see when each parameter must be used.

## 2. Attack modes

Sqlninja has currently 14 attack modes. The mode to use can be specified by its name:

> `sqlninja -m upload`

or by its shortcut:

> `sqlninja -m u`

The list with the available modes and their corresponding shortcuts can be retrieved by launching sqlninja with no parameters.

To get a first grasp of the different attack modes, here's a typical way of using sqlninja:

1. Setup the configuration file, and use test mode to check that SQL code is being correctly injected
2. Fingerprint the remote DB server, using fingerprint mode
3. If needed, use bruteforce mode to find the 'sa' password and escalate privileges (SQL Server 2000 only)
4. If needed, use resurrectxp mode to re-create the xp_cmdshell extended procedure (SQL Server 2000 only)
5. Upload netcat, using upload mode
6. If it is possible to contact the DB Server on some port, use dirshell mode and get a direct shell. Alternatively, if the port is TCP, use metasploit mode to get graphical access
7. Otherwise, use backscan mode to find an allowed "outbound" tcp/udp port
8. If step 7 is successful, use revshell mode to obtain a reverse shell. Alternatively, if the port is TCP, use metasploit mode to get graphical access
9. If step 8 failed, upload icmpsh.exe and try icmpshell mode to obtain an icmp-tunneled shell
10. If step 9 failed, upload dnstun.exe and start dnstunnel mode to obtain a dns-tunneled pseudo-shell
11. If step 10 failed, crank up getdata mode and start extracting some tables!

## 2.1 test

- Shortcut: t
- Parameters: none

This mode simply injects a simple `WAITFOR DELAY` and checks whether it is successfully executed by the remote server. Use this mode to test whether your configuration file is correct and the injection is working.

## 2.2 fingerprint

- Shortcut: f
- Parameters: -p <sa password> (optional)

Using WAITFOR-based blind injection, this mode fingerprints the remote server. The following pieces of information can be obtained:

- Database version (2000/2005/2008/2012)
- User that is performing the queries
- Whether that user belongs to the sysadmin group
- Whether xp_cmdshell is available to that user
- Whether the remote server uses mixed or Windows-only authentication (you need to know this if you want to bruteforce the 'sa' password)
- Whether the remote SQL Server runs as SYSTEM. This can also be used to check whether churrasco.exe has been correctly uploaded and is able to escalate privileges through token kidnapping.
- Name of current DB

If you are attacking SQL Server 2000, the current DB user does not belong to the sysadmin group, but the right 'sa' password is specified as a parameter, the fingerprint is performed with administrative rights. The WAITFOR technique is much slower compared to other inference methods, but it's by far the most flexible. However, since external factors like network traffic and server load could interfere with the time measurements, you might want to repeat the fingerprint a couple of times, if the first result doesn't look right, or play with the `blindtime` parameter in the configuration file. Note that in order to use fingerprint the user running SQL Server the following must be available on the remote box:

- xp_cmdshell (or an equivalent procedure)
- `whoami.exe`. This is present by default on Windows 2003, but if you suspect that this utility is not on the remote box, just download it from microsoft.com and upload it.

## 2.3 bruteforce

- Shortcut: b
- Parameters: -w <wordlist> (optional)

This mode is to be used if the user that performs the queries does not belong to the sysadmin group (see fingerprint mode). If this is the case, we need to escalate our privileges. Since by using OPENROWSET we can make the target database connect to itself with alternate credentials, we can attempt to bruteforce the 'sa' password. If the correct password is found, current user is automatically added to the sysadmin group. For this attack to work, the remote SQL Server must use "mixed authentication". Use fingerprint mode to check if this is the case.

This attack mode can use two different methods: "dictionary" and "incremental". You are free to use the method that best suits your needs.

### Dictionary

This method is used when a wordlist is specified, using the `-w` option. Using this method, potential passwords are fetched from the wordlist, and each one is tried in a separate request. Be sure that your wordlist contains 'sa' and the empty password, two all-times favourites for MS SQL Server installations.

Pros:

- Very effective if the password is a dictionary word
- Does not put a heavy load on the DB Server

Cons:

- Not effective against passwords that are not dictionary based. If the password is not in your wordlist, you are out of the game
- Needs a lot of network connections, so the attack is very easy to spot by looking at the logs of the web server

### Incremental

This method is used when a wordlist is not specified. Sqlninja submits a set of queries that try *ALL* possible combinations of characters up to a certain length that is specified by the user. The cool aspect of this tactic is that since the queries run on the DB server, the bruteforce is actually performed using the target's CPU resources.

Pros:

- Extremely effective in finding passwords that are not dictionary based
- Needs relatively few connections, so there are very few entries in the web server logs

Cons:

- If the password is long, it might take ages
- It might push the CPU usage of the DB Server up to 100% for the whole time, which can be dangerous with a live application. Also keep in mind that critical servers have alarms that are triggered if the CPU usage remains very high for a certain time. As a security measure, sqlninja splits the task in small chunks (each chunk trying n^3 passwords, with n being the length of the charset used). If something goes wrong, just stop sqlninja, and the remote bruteforce will stop at the end of the current chunk
- Depending on how the application connects to the DB Server, this technique might not work (e.g.: ODBC is known to create trouble). Sqlninja tries to figure it out almost immediately and alerts the user, so no precious time is lost

### Important notes

- Starting with SQL Server 2005, OPENROWSET is disabled by default for non-administrative users. If the fingerprint mode told you that you are dealing with SQL Server 2005/2008/2012 and that you are not 'sa', then you are likely out of luck (but you can still extract data with the getdata mode
- In SQL Server 2000, passwords are case insensitive, which massively simplifies the cracking job.
- The escalation bit might be impacted if the application uses ODBC (see escalation mode)

## 2.4 escalation

- Shortcut: e
- Parameters: -p <sa password> (required)

When the correct 'sa' password is specified, the current DB user is added to the sysadmin group.

In general, you should not need this method, as sqlninja takes care of the escalation in the bruteforce mode already. However, there might be cases in which you need to perform this bit independently (maybe you found the password with a social engineering attack).

If you want to know how the escalation works, or if you have found the 'sa' password but the escalation seems not to work, keep reading. Otherwise, you can skip to resurrectxp mode.

The escalation is performed combining OPENROWSET, the right 'sa' password, and sp_addsrvrolemember, by adding the current DB user to the sysadmin group. It is quite unlikely that sp_addsrvrolemember has been disabled, so the trick should work pretty much always. If it doesn't work, there might be 2 cases:

1. The server uses ODBC, and you are using old ODBC connections from the connection pool, which still use the old privileges
2. The sp_addsrvrolemember procedure has been disabled

In the first case, you can just have a couple of pints waiting for the old ODBC connection to timeout and be dropped: by default, an ODBC connection is dropped after 60 idle seconds, and the chance of such an event depends on how many clients are connecting to the web application and how this number varies over time.

In the second case (or also in the first, if you don't want to wait), you only need to specify the `-p <sa password>` parameter in all the following steps of the attack: that will tell sqlninja to use OPENROWSET in each connection, running each command as 'sa' rather than as the current user.

## 2.5 resurrectxp

- Shortcut: x
- Parameters: -p <sa password> (optional)

This mode is to be used when the following conditions are both met:

- We have sysadmin privileges or we know the 'sa' password
- xp_cmdshell has been disabled

The goal of this mode is, of course, to recreate the xp_cmdshell extended procedure. There are quite a lot of variables that come to play here and depending on them this mode will behave in different ways. So read carefully, as here are the things you must keep in mind:

- The methods: there are two ways to get the xp_cmdshell back:
  1. restore it with a stored procedure (sp_addextendedproc on SQLServer 2000 and sp_configure on SQLServer 2005). This method requires one simple SQL command, but requires xplog70.dll to still be there
  2. create a custom one with "CREATE PROCEDURE", sp_oacreate, sp_oamethod and sp_oadestroy. This method requires more code, but works no matter if xplog70.dll has been removed for security reasons.
- The xp_cmdshell name: re-enabling xp_cmdshell might not go unnoticed. Or maybe the application developers might have strictly followed what MS recommends, which is to filter the "xp_*" string, without saying nothing about "sp_*" (check http://msdn.microsoft.com/library/en-us/bldgapps/ba_highprog_11kk.asp). In these cases, we can use CREATE PROCEDURE and a more discrete name (e.g.: "sp_sqlbackup"). You can choose the procedure name with the xp_name option of the configuration file.
- The user privileges: if the privilege escalation didn't work (see escalation mode for the possible reasons), then you must use the `-p <sa password>` parameter, in order to use OPENROWSET to escalate privileges in each connection, and this leads to the following point
- OPENROWSET and CREATE PROCEDURE cannot be combined. Therefore, if you are using the `-p` parameter you cannot use the "CREATE PROCEDURE" trick. However, there is a workaround: you can include the whole procedure code in each request that is sent to the DB Server, without creating an extended procedure at all. Let's call this trick "inline procedure injection".

That said, here are the steps that sqlninja follows when this method is used:

1. If the extended procedure name, specified in the configuration file, is `xp_cmdshell` (which is the default value), then sqlninja starts by trying to re-enable it with sp_addextendedproc/sp_configure. You will be asked the version of the remote SQL Server. If you forgot to use fingerprint mode, sqlninja will find this info on its own. If this whole thing works, we have our xp_cmdshell back.
2. If the extended procedure name is not set to `xp_cmdshell` (maybe because you want to be more sneaky) in the configuration file, or step #1 has failed (e.g.: because xplog70.dll has been removed), then:
   - if we have native admin privileges (meaning we didn't have to specify the password in the command line) the CREATE PROCEDURE method is attempted. If it works, we have our custom procedure, whatever we have named it
   - if we do not have native admin privileges (meaning we had to specify the password in the command line) the inline procedure injection is tried. If it works, then you will have to set xp_name to `NULL` in the configuration file. This will tell sqlninja to use the inline procedure injection in all subsequent steps

I hope it is clear. If it is, you should not have any problem in having back your xp_cmdshell (or something perfectly equivalent) in almost every situation. If it is not clear, I am afraid you will have to read the whole thing again.

Note: the code used by sqlninja for the custom procedure is a slight modification of Antonin Foller's code, that you can find at the address http://www.motobit.com/tips/detpg_cmdshell/

## 2.6 upload

- Shortcut: u
- Parameters: -p <sa password> (optional)
- Parameterd: -g (optional)

This mode uploads a binary file using only GET or POST HTTP requests to the web server, so no FTP/TFTP or whatever other connection is needed. The file is uploaded to the directory specified by the server's `%TEMP%` variable, so that the attack works even when MSSQL cannot write on the default directory (which seems to be sometimes the case with MSDE). There are two upload methods available, controlled by the upload_method option:

- debug script: This method is the traditional one, and uses the old `DEBUG.EXE` 16bits debugger. The binary file is encoded as a debug script (`.scr` extension) the script is uploaded and feeded to the debugger. The script basically allocates an area of memory, writes the needed bytes in it, and saves the result to disk. Being a 16bits debugger there is obviously a 64k bytes limitation in the size, but sqlninja bypasses it by splitting the original executable in chunks of 64k bytes, uploading them separately, and then finally merging them together. Sqlninja uses the same algorithm used in Jussi's great dbgtool.exe (which you can find at the address http://www.toolcrypt.org) which is capable of creating very compact scripts.
- vbscript: This is the new method: basically, it encodes the binary file in base64 format, uploads it, and then feeds it to a tiny vbscript decoder previously uploaded. On average it uses fewer requests, it does not need to split the original file, and has higher chances to work on recent systems. Therefore, although the old method is much

No matter what method you select for the upload, you will be prompted for the file name to upload and things will be completely automated. If the file appears to be already in `.scr` or `.base64` format, sqlninja will perform the upload anyway, but some checks (e.g.: the uploaded binary file has the correct size) will not be possible. In general, it is always better to provide sqlninja with the original binary.

For your comfort, netcat.exe, dnstun.exe, icmpsh.exe, churrasco.exe, vdmallowed.exe and vdmexploit.dll are already available in the `apps` and `scripts` directories, respectively in binary and debug+base64 format. The executables have been packed with UPX in order to minimize their size (and the upload time). You need to upload netcat to use backscan/dirshell/revshell, whereas dnstun.exe and icmpsh.exe are used to create a DNS and ICMP tunneled pseudoshell respectively. Churrasco.exe is used to attempt a privilege escalation via token kidnapping if SQL Server is not running as SYSTEM. Vdmallowed.exe and vdmexploit.dll attempt the same attack using CVE-2010-0232.

Keep in mind that a lot of things can go wrong here: if a single line of the encoded file fails to get uploaded, the executable will not be correctly generated. Therefore, at the end of the process sqlninja checks whether the executable file is there, and if it is not it also tries to figure out how many lines have been uploaded: this should provide some hints on what went wrong. For instance, during a pen-test it turned out that the resulting number of lines was exactly twice the correct value, meaning that each injected query was executed twice. The trick was to create a temporary table that acted as a counter, appending the line to the script file only when the counter was even.

If you only want to generate the debug script or the base64 file without uploading it (for instance to use it with some other tool), start the upload mode with the `-g` option, and sqlninja will generate the file in the `/tmp` directory and exit. You need to specify the password parameter when you do not have native sysadmin privileges (see escalation mode).

## 2.7 dirshell

- Shortcut: s
- Parameters: -p <sa password> (optional)

Use this method when the remote DB Server is directly reachable on some TCP or UDP port. Sqlninja asks for the remote port, the protocol, tells the DB server to bind a command prompt to such port and then starts the connection. Of course, netcat must have been uploaded on the remote server. The password parameter is to be used when we do not have native sysadmin privileges (see escalation mode).

## 2.8 backscan

- Shortcut: k
- Parameters: -p <sa password> (optional)

Tipically, when the DB Server is behind a firewall it is not possible to directly contact it. However, it might be possible that the server is allowed to access the outside world on some port (e.g.: DNS, HTTP). This mode tells the DB Server to send SYN packets or UDP packets to our machine on a range of ports, in order to look for one that is allowed. Sqlninja will tell the user whether packets are received and on which port(s).

You need to specify, in the configuration file, the IP address of your machine ( lhost parameter) and the interface to listen on ( device parameter). Sqlninja will ask you about the protocol to use (TCP/UDP) and for the ports, that must be specified with the common netcat syntax (e.g.: "23 25 80-100" will try ports 23, 25 and all ports between 80 to 100). The password parameter is to be used when we do not have native sysadmin privileges (see escalation). In order to use this mode, netcat must have been uploaded first, and since pcap libraries need to be used you also need to be root.

## 2.9 revshell

- Shortcut: r
- Parameters: -p <sa password> (optional)

If a direct shell is not possible but backscan mode found an open port from the DB Server to our machine, then a reverse shell is possible. When using this mode, sqlninja asks for the local port, the protocol and then starts the connection. You need to specify, in the configuration file, the IP address of your machine ( lhost parameter). Of course, netcat must have been uploaded on the remote server. As usual, the password parameter is to be used when we do not have native sysadmin privileges (see escalation mode).

## 2.10 icmpshell

- Shortcut: i
- Parameters: -p <sa password> (optional)

When no direct or reverse shell are allowed by the firewall, but the remote DBMS can ping our box, we can tunnel our shell into an ICMP tunnel. Just upload icmpsh.exe, start icmpshell mode, and enjoy your shell. All the traffic from and to the remote DBMS will be tunneled through ICMP packets.

When starting this attack mode, sqlninja will ask the following information:

- Data buffer size: the amount of data that will be encapsulated into a single ICMP packet. The default is 64 bytes, but you can use larger values to obtain a faster tunnel. Just be careful to the maximum MTU (Maximum Transfer Unit) between you and the DBMS. A value up to 1300-1400 bytes should be considered, by today's standards, fairly reliable. Use smaller packets if you want to play safe
- Send delay: the amount of time between contiguous ICMP Echo requests. The default is 300 milliseconds, but you can use lower values to obtain a faster tunnel. Keep in mind that a very low value might generate a ping flood that might be noticed, or automatically throttled down by some anti-DoS device between you and your target.
- Response timeout: the amount of time that will be waited by icmpshell.exe before re-sending an ICMP request. The default is 3000 milliseconds

Important: make sure that your box is configured to not respond to ICMP Echo requests. For instance, on Linux the following command will do the trick:

`sysctl -w net.ipv4.icmp_echo_ignore_all=1`

## 2.11 dnstunnel

- Shortcut: d
- Parameters: -p <sa password> (optional)

When no direct or reverse shell are allowed by the firewall, and the ICMP shell does not work either, we can try to establish a DNS tunnel. The only requirements are:

- The DB server must be able to resolve external hostnames (which is very often the case)
- Our IP must be the authoritative DNS server of some domain (you can buy one for a few bucks). We will use `sqlninja.net` in our example

If both conditions are met, upload dnstun.exe, start dnstunnel mode, and launch your commands. What happens is more or less the following:

1. The command is passed via SQL Injection to dnstun.exe (which acts as our remote agent) and is executed by the remote DB Server. The output is intercepted and encoded in a slightly modified base32 format
2. The encoded output is split in a series of hostnames of the domain we control (e.g.: `encoded_output.sqlninja.net`)
3. Those hostnames are passed to `gethostbyname()`, so that the DB server contacts its DNS Server to resolve them
4. The DNS Server looks for the authoritative server of sqlninja.net (our IP) and forwards the requests to our workstation
5. sqlninja receives the requests, re-orders them if necessary, decodes the hostnames and finally prints the command output. Of course, sqlninja also responds to the DNS requests (with a fake IP address) in order to make `gethostbyname()` quickly return.

The whole process is streamed, which means that if the command output is very long you will start seeing its output before the command has finished.

The domain to use must be specified in the configuration file. Of course, since sqlninja must create a fake DNS server and bind port 53, you need root privileges to use this mode. Keep in mind that DNS uses UDP, so packet loss might be an issue, here.

The executable version of the agent has been compiled with Msys. As always, the password parameter is to be used when we do not have native sysadmin privileges (see escalation mode).

## 2.12 metasploit

- Shortcut: m
- Parameters: none

Not happy with a simple DOS prompt? Want to impress your friends with a full GUI access? If you have administrative privileges, xp_cmdshell works and you have found an allowed TCP port (either inbound or outbound), you can also use sqlninja as a wrapper for Metasploit, in order to either use Meterpreter or inject a VNC server. Think of Meterpreter as a DOS prompt but far more powerful, providing you with an almost complete control over the remote OS, including immediate access to password hashes, the possibility of changing routing tables, perform port forwarding and even more. Alternatively, if you have enough bandwidth, you can also inject a VNC server and be provided with a nice graphical access to the remote DB.

This attack mode is fully automated, and in a nutshell here's what happens:

1. Sqlninja asks you to specify if you want to use Meterpreter or VNC, whether the connection will be direct or inverse, and the host/port to connect to (or local port to bind, in case of a reverse connection)
2. Sqlninja will call `msfpayload` to create an appropriate executable that will act as a stager
3. Sqlninja will then convert it to a debug script and upload it
4. Since we will need to inject a DLL, we might need to disable Data Execution Prevention (aka 'DEP', enabled by default starting from Windows 2003 SP1) on the remote box. Recent versions of Metasploit handle this bit automatically, but you can also tell sqlninja will try to do it for you, by accessing the registry and whitelisting our executable (see the `checkdep` parameter)
5. Finally, Sqlninja will call `msfcli` to inject the needed DLL and complete the exploitation

You can watch a flash demo of this attack on the sqlninja website.

Of course, in order to use this attack mode you need to have Metasploit3 available on your box. If Metasploit executables (namely `msfpayload`, `msfcli` and `msfencode`) are not in your path, you can specify their absolute location in the configuration file. Also, if you use the VNC mode, be sure to have a VNC client installed.

## 2.13 sqlcmd

- Shortcut: c
- Parameters: none

Sometimes, even if we have sysadmin privileges and xp_cmdshell works, it is still not possible to get a shell, maybe because the executable upload fails, or because ports are all filtered and external DNS resolving is not allowed. In these cases, it can still be useful to issue single commands to the DB server, even without being able to see the output. For instance, you might want to add a local user (maybe you can RDP to the box), or a domain user, if SQL Server runs with such privileges (yes, it happens more often than one would expect). In such cases, you can use this mode: simply enter a DOS command and let sqlninja execute it remotely. Just remember: it gets executed even if you don't see its output.

Of course, you can still use timing to know what is going on:

> `if exist filename (ping -n 5 127.0.0.1)`

If the command takes around 5 seconds to execute, the file is there.

To know whether a command succeeded, also check the value of the ERRORLEVEL variable, which is usually set to 0 if the last command did not produce an error. So, for instance, if we want to know whether the remote SQL Server is running as SYSTEM, we can use the following command:

> `whoami > who.txt & find /i "\system " who.txt & if not errorlevel = 1 ping -n 5 127.0.0.1 & del who.txt`

If the command takes around 5 seconds to execute, you know that SQL Server is running as SYSTEM (`whoami.exe` is installed by default on Windows 2003 and can be found on Windows 2000 if the Resource Kit has been installed). Refresh your DOS-shaolin skills and use your fantasy: from appending commands in `AUTOEXEC.BAT` to starting/stopping services and adding rogue users, you can get pretty far with this!

This mode can also be useful when some other mode fails, in order to understand what went wrong and how to fix the problem. Finally, this command is also very useful to show a client that you owned their DB server even if you didn't get the shell:

> `echo You have been owned by sqlninja > c:\sqlninja.txt`

## 2.14 getdata

- Shortcut: g
- Parameters: -s <filename> (optional)

Let us start by pointing out that this is still very experimental, it is likely to contain more bugs than a Win95 beta, and therefore you should not expect its reliability to be bomb-proof. With that out of the way, let's get down to business: this module is 100% interactive, so it should be fairly intuitive. Sqlninja currently supports two extraction channels, time-based and DNS-based, described below.

### Time-based

This channel is used when `data_channel` is set to `time` in the configuration file, and uses the slow but reliable WAITFOR DELAY command to extract information. Sqlninja can exploit time-based injection in two ways, detailed in the following paragraphs.

Time-based binary search

This method is activated when `data_extraction` is set to `binary` in the configuration file. If you are even marginally into computers, you should know how a binary search algorithm works, so we am not going to get much into detail here. Basically, this method minimizes the number of requests to the application, which makes it useful if you want to keep your footprint to a minimum. However, approximately half of the queries will trigger a delay, which means that this method might not be the fastest.

Time-based serial/optimized search

This method is activated when `data_extraction` is set to `optimized` (default) or `serial` in the configuration file. With this method, all possible values are tried in sequence until the right one is guessed. The difference between `serial` and `optimized` is in the order of the attempts: while the former just tries all values following their ASCII value, the latter starts with the most common values. The exact order is specified with the `language_map` parameter, and such order is modified in real-time, adapting to the actual frequency of characters being extracted, if the `language_map_adaptive` parameter is set to to `yes`.

DNS-based extraction

You have control over a DNS domain or subdomain? You can get DNS servers to shoot "Type A" requests to your box? Does the remote DBMS resolve external names? If so, you can forget about that sluggish inference-based extraction and start pulling data almost at light speed (well, comparatively speaking). Make sure you run sqlninja as root, set `domain` in the configuration file, and you are ready to go.

Additional info

By default, sqlninja stores all extracted information in a local SQLite database, whose filename is specified via command line with the `-s` parameter. The default name is `session.db`. For all other parameters and details, see data extraction options.

## 2.15 Other attacks

Quite often, SQL Server does not run as SYSTEM but as a less-privileged user (very often "Network Service"). This creates limitations in what the attacker can do (e.g.: extract password hashes). It also creates problems with the VNC Injection, causing a black screen to be returned. However, with sqlninja we can try to escalate privileges to SYSTEM, using two different attacks techniques.

### CVE-2010-0232

If SQL Server runs as a low-privileged user, and the machine is not patched against CVE-2010-0232, we can try to elevate its privileges to SYSTEM. Sqlninja ships with a version of the original exploit by Tavis Ormandy that has been specifically customized: while the original exploit spawns a DOS prompt, our version looks for the sqlservr.exe process and forces it to run as SYSTEM. In order to launch the attack, the following steps are required:

1. Upload `vdmallowed.exe` and `vdmexploit.dll`, which are available in the `apps` directory in executable format and in the `scripts` directory (in debug script format)
2. Using the sqlcmd attack mode, run the following command: `%TEMP%\vdmallowed sql`
3. If the attack was successful, fingerprint mode should tell you that SQL Server is now running as SYSTEM

### Token kidnapping

On Windows 2003 we can also attempt to escalate our privileges using token kidnapping, a technique researched by Cesar Cerrudo. As a proof of concept he developed churrasco.exe, which is included in the sqlninja tarball in a slightly modified version. If you need to escalate to SYSTEM simply upload it to the remote server using the `upload` mode and then set the usechurrasco option to `yes`: all commands will then be wrapped with churrasco.exe. Keep in mind that this will not work if the remote DBMS has been patched against the attack, but you can check whether things are working using the fingerprint mode while this option is enabled.

Important: be sure to use the modified version of churrasco (yes, the one in the sqlninja tarball), or things are likely to break. You can see the differences in the C source in the `sources` directory, but basically they boil down to:

1. No verbose output unless the `-d` option is used. Verbose output would interfere with option 5 of the fingerprint mode, which uses a temporary table to store the results of a churrasco.exe execution.
2. `CreateProcessAsUser()` is called passing the original (unprivileged) user's %TEMP% directory as the `lpCurrentDirectory` parameter, which is where our executables (e.g.: netcat) are uploaded (and not in the %TEMP% directory of SYSTEM).

## 3. Configuration file

The configuration file (default: `sqlninja.conf`) controls most of sqlninja behaviour. All options are in the form:

> `option_name = option_value`

The only exception is `httprequest`, which defines the HTTP request and the injection point and which spans multiple lines (see below).

Options can be roughly divided into the following categories:

- Basic: used to configure the attack
- Data extraction: used to configure the data extraction mode
- Advanced: used for additional fine-tuning

Options are, more often than not, case sensitive (e.g.: URL values). The same option can be used multiple times: sqlninja does not care and will simply use the last declaration, overriding the previous ones. Comments are allowed anywhere except between `--httprequest_start--` and `--httprequest_end--` (see below), and they are prepended by the '#' character. A quick recap of what follows can also be found in `sqlninja.conf.example`.

## 3.1 Basic options

### httprequest

Starting from version 0.2.6, sqlninja uses a new way to configure the HTTP request and the relative injection string. Instead of separate parameters for host, port, page, HTTP method, exploitation string and additional headers, the whole HTTP request is specified at once, with a marker (by default `__SQL2INJECT__`) that indicates where the SQL commands need to be injected. This simplifies things a lot, and most importantly allows complete freedom in where the injection vector can be: now you are not limited to a GET or POST parameter, but you can inject wherever you need (e.g.: in a cookie). Sqlninja will consider as the HTTP request everything that is included between the lines `--httprequest_start--` and `--httprequest_end--`.

In general, the following elements must be included:

- The HTTP Method (usually POST or GET)
- The full URL to the resources, including `http://` or `https://`
- The port, if not standard (e.g.: `http://www.victim.com:8080`)
- The HTTP version
- All necessary headers
- The body after an empty line, if the request uses POST

In general, the best strategy is just to use a proxy (e.g. Burpsuite) to intercept the request that triggers the SQL Injection and copy it into `sqlninja.conf`

For instance, a GET-based injection over plaintext HTTP will look like the following:

> `

>     --httprequest_start--
>     GET http://www.victim.com/page.asp?string_param=aaa';__SQL2INJECT__&other_param=blah HTTP/1.1
>     Host: www.victim.com
>     User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060418 Firefox/1.0.8
>     Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*
>     Accept-Language: en-us,en;q=0.7,it;q=0.3
>     Accept-Charset: ISO-8859-15,utf-8;q=0.7,*;q=0.7
>     Connection: close
>     --httprequest_end--

> `

Alternatively, a POST-based injection over HTTPS will probably look like the following (note the Content-Type header and the empty line between headers and body):

> `

>     --httprequest_start--
>     POST https://www.victim.com/page.asp HTTP/1.0
>     Host: www.victim.com
>     User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060418 Firefox/1.0.8
>     Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*
>     Accept-Language: en-us,en;q=0.7,it;q=0.3
>     Accept-Charset: ISO-8859-15,utf-8;q=0.7,*;q=0.7
>     Content-Type: application/x-www-form-urlencoded
>     Cookie: ASPSESSIONID=xxxxxxxxxxxxxxxxxxxx
>     Connection: close

> `

> `

>     numeric_param=12;__SQL2INJECT__
>     --httprequest_end--

> `

Note that the Content-Length header is not included: sqlninja will calculate the appropriate value and add the header automatically.

Finally, a cookie-based injection will look like the following:

> `

>     --httprequest_start--
>     GET http://www.victim.com:8080/page.asp?param1=aaa&param2=blah HTTP/1.0
>     Host: www.victim.com
>     User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060418 Firefox/1.0.8
>     Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*
>     Accept-Language: en-us,en;q=0.7,it;q=0.3
>     Accept-Charset: ISO-8859-15,utf-8;q=0.7,*;q=0.7
>     Cookie: ASPSESSIONID=xxxxx'%3B__SQL2INJECT__
>     Connection: close
>     --httprequest_end--

> `

Note how the semicolon after the apostrophe has been encoded to %3B: this is because otherwise the server would parse the semicolon as a separator between different cookies.

Before the `__SQL2INJECT__` marker, you need to include everything that is needed to close the original query and start a new one, such as the vulnerable parameter and the character sequence that allows us to start injecting commands. This usually means, at least:

1. the vulnerable parameter (name+value)
2. a single quote (if the parameter is a string)
3. a semicolon (to end the original query)

It must also include everything that is needed to properly close the original query, as an appropriate number of closing brackets. For instance, if want to inject the following TSQL command:

> `param1=1&param2=x'));exec+master..xp_cmdshell+'dir+c:'`

the HTTP request in the configuration file should contain the following:

> `param1=1&param2=x'));__SQL2INJECT__`

Important things to remember:

- In general, a good technique is to replicate as closely as possible the HTTP request that you used to originally detect the SQL Injection flaw (with a web browser or another tool), as in some edge cases a slightly different header can make a big difference. The only suggested and usually safe modification is to use HTTP/1.0 in order to avoid problems with connections remaining open
- In order to give you full power and flexibility in crafting your exploit, sqlninja does not try to meddle in any way: this means that it will not modify your HTTP request (apart from the code to inject where the marker is, obviously), but it also means that it will not try to correct your syntax, so make sure your HTTP request is correct (including all needed URL-encoding). For more information, see RFC 1945, RFC 2068 and RFC 2616.
- Sometimes you might also need to add some more SQL code after the injected query (and therefore after the marker). Usually this is not needed, since sqlninja simply appends two hyphens and comments out the remainder of the original query, but there are some (rare) cases when you need to append additional SQL code for the batched queries to work correctly. In this case, don't forget to also set `appendcomment = no`, otherwise the two hyphens will be appended and the SQL code specified here will be considered a comment
- If you are injecting in a cookie, and you need a semicolon to close the original query, remember to encode it (%3B), otherwise it will be parsed as the end of the cookie value
- Do not leave spaces at the beginning of each line!
- Do not leave comment lines! They would be parsed as part of the request!
- Finally, if you don't specify the port to connect to, sqlninja will assume 80 for HTTP and 443 for HTTPS

### proxyhost

An HTTP proxy to connect to the target host, if needed. For example:

> `proxyhost = 192.168.1.233`

### proxyport

The port of the HTTP proxy that we connect to. Default is 8080. For example:

> `proxyport = 3128`

### domain

The attacker's controlled domain or subdomain to be used with the dnstunnel mode and DNS-based data extraction mode. The IP address from which sqlninja is launched must be the authoritative DNS server for that domain. For example:

> `domain = sqlninja.net`

### msfpath

The absolute path to Metasploit executables (`msfpayload` and `msfcli`). You don't need this if they are already in your default path. For example:

> `msfpath = /home/icesurfer/tools/framework-3.1`

### evasion

Sqlninja can use a few evasion techniques, in order to confuse and bypass signature-based IPS/IDS. Currently, four techniques are implemented, which can be freely combined together:

1. Query hex-encoding: the query is hex-encoded before being run
2. Comments as separators: all spaces are substituted by the string `/**/`
3. Random case
4. Random URI encoding

The first technique is particularly useful. For instance, if we want to inject the following command:

> `exec master..xp_cmdshell 'cmd /C ping 127.0.0.1'`

The actual query will become:

> `declare @a varchar(8000) set @a=0x65786563206d61737465722e2e78705f636d647368656c6c2027636d64202f432070696e67203132372e302e302e31273b exec (@a)`

A much longer string, but notice the following:

- No SQL commands except DECLARE and EXEC, so bye-bye IPS's looking for xp_cmdshell and the like
- No single quotes either! This evasion technique is therefore extremely useful if you find a vulnerable numeric parameter and single quotes are filtered

As mentioned, you can combine all the techniques together with the following option:

> `evasion = 1234`

This will generate quite cryptic code, as the following one:

> `%64ECl%41RE%2F%2A%2A%2F%40%61%2F%2A%2A%2F%76Ar%63%48aR%288000%29%2F%2A%2A%2F%73 ET%2F%2A%2A%2F%40A%3D%30%586%35786%3563%3206d617%33746%35%372%32e2%457870%35F63 6d647368%36%35%36%63%36c2%302%37636D%3642%30%32f%34320%37%3069%36%65%36720%331% 332372E%330%32E3%30%32%45%3312%373b%2F%2A%2A%2FeX%65%43%2F%2A%2A%2F%28%40A%29`

As a default, sqlninja sets `evasion` to zero, and no evasion technique will be used.

Important: avoid using unnecessary obfuscation if you are using GET requests, as this might lead to URLs that are too long and that are not successfully parsed by the web server!

### msfencoder

The encoder to use for the Metasploit stager. If not specified, no encoding is performed. However, a good encoder is always recommended. For example:

> `msfencoder = x86/shikata_ga_nai`

### upload_method

The method to use to upload binary files. Possible values are `debug` or `vbscript` (default). For example:

> `upload_method = vbscript`

## 3.2 Data extration options

### data_channel

The channel to use to extract data. It can be `time` (default) to use a WAITFOR-based extraction channel (very slow, but always works) or `dns` (much faster, but you need to control a domain or subdomain to be resolved to your public IP address. For example:

> `data_channel = time`

### data_extraction

When using time-based extraction, there are three possible extraction methods. When choosing `binary`, sqlninja will perform a binary search, minimizing the number of requests. When choosing `serial`, sqlninja will try all possible values, which will probably be faster (since WAITFOR will be triggered only once) but will leave more entries in the remote logs. When choosing `serial_optimized`, sqlninja will try all possible values, starting from most likely candidates. The default is `serial_optimized`

### language_map

If you are using time-based extraction and you have selected `serial_optimized` as your extraction method, you can specify a language map where you can specify the orders of characters that should be tried when extracting data. You can find some pre-defined maps under lib/langs, where included maps for English, French, Italian, German, Spanish and Portuguese. Such maps are based on the letter frequency in the respective languages and include also a whitespace and some common punctuation characters. If you need a custom map, just list the characters in a single line. You don't need to specify all possible characters: the ones not in the map will simply be tried if none of the specified ones is successful. For example:

> `language_map = lib/langs/en.maps`

### language_map_adaptive

When using a serial-optimized extraction, sqlninja can use an adaptive approach: basically, each character in the language map is given a "weight" and every time a character is successfully extracted by the remote database, the weight of this character in the language map is increased by one. When the weight of the caracter in position N is higher than the weight of the character in position N-1, their places are switched in the map itself, so that the character with the higher weight (which is therefore more frequent) will be tried first when extracting following characters. Values here are either `yes` or `no`, but in general you should always stick to `yes` for better results. For example:

> `language_map_adaptive = yes`

### store_session

By default, sqlninja stores all extracted information in a local SQLite database, specified via command line (default: session.db). This allows you locally save all extracted data and to retrieve it at a later moment. In general, leave this to `yes`. For instance:

> `store_session = yes`

### sanity_check

When using time-based extraction, network latency can limit the accuracy if extracted data. Sqlninja can check the accuracy of extracted information (currently DBs, users, tables, columns but not rows yet) and retry to extract the same piece of information if a problem is detected. The check involves only one query, is performed at the end of the extraction of a whole string (e.g.: a column name), and uses a WAITFOR that is executed only if the information is incorrect. Therefore, the check has a very limited performance impact. In general, leave this to `yes`. For example:

> `sanity_check = yes`

## 3.3 Advanced options

### lhost

The IP addresses or hostname that the target must try to contact in backscan and revshell mode. That is *your* machine. Of course, if the attack is performed over the Internet, this must be a public address. For example:

> `lhost = tester.sqlninja.net`

### device

The device to use for sniffing packets when in backscan mode (default: eth0). For example:

> `device = ppp0`

### filter

A valid pcap expression to filter incoming packets in backscan mode. By default, when performing such attack, sqlninja listens for packets coming from the IP address of the remote web server and directed to the host specified in `lhost`. This might not work in all cases: for instance, the outbound connections of the DB server could be NATed to an IP address which is different from the IP address of the web server. Therefore, we need to override the default pcap filter with this parameter, for instance indicating the whole public subnet of the target. You only need to specify hosts/networks here, as the protocol details (e.g.: tcp flags) are handled by sqlninja. For example:

> `filter = src host nat.victim.com`

### timeout

This parameter is used when in backscan mode. It specifies how many seconds to wait for further packets after the web request has completed (default: 5 seconds). This is especially useful when specifying a very large range of ports to scan, because the web request might timeout before netcat has completed. In this case, you should increase this value. For example:

> `timeout = 30`

However, try to avoid very large port ranges: better to split the job in multiple scans.

### hostnamelength

Maximum length of FQDN of the fake hostnames that the target will try to resolve in dnstunnel mode. RFCs state that 255 characters is the limit, but I bumped into a few DNS servers that refused names longer than 253. The default value is therefore 250, which should be accepted by every DNS server, and at the same time keep an almost optimal tunnel speed. Minimum value is 40. Maximum is obviously 255. For example:

> `hostnamelength = 250`

You can also tune this parameter to lower values when you think that very long DNS requests might be spotted. Of course, shorter values mean a slower tunnel. If unsure, leave the default value.

### msfencodecount

Number of times that the stager must be encoded. Default is 5. For example:

> `msfencodecount = 8`

### usechurrasco

This setting is used to escalate privileges through token kidnapping. The default of this setting is `no`. For example:

> `usechurrasco = yes`

### resolvedip

In dnstunnel mode, the IP address that is sent back to each DNS request (since we don't want gethostbyname() to hang). In general, it is advisable to set this to 127.0.0.1 (which is the default), to avoid spurious network traffic generated after the remote DBMS receives a fake DNS response.

> `resolvedip = 10.255.255.254`

### xp_name

Name of the extended procedure that executes our commands. The default is obviously `xp_cmdshell`. This parameter is used in two different ways, depending on the current attack mode:

- resurrectxp: `xp_name` contains the name of the extended procedure to create. If you believe that re-enabling xp_cmdshell might be spotted, use another name here (e.g.: `sp_sqlbackup`)
- all other modes: the extended procedure name to use. It goes without saying that it must be the same name previously used with the resurrectxp mode.

xp_name can be set to `NULL` to use the inline procedure injection technique (see resurrect_xp mode for more details). For example:

> `xp_name = sp_sqlbackup`

### blindtime

The value for the WAITFOR DELAY calls that are used in fingerprint and bruteforce modes for the inference-based injection. Default value is 5 seconds, but this might be too low for very slow servers and lead to wrong results. If that happens, try increasing this value. On the other hand, if the server response time is very short, you can set a lower value to make things faster (minimum: 3). For example:

> `blindtime = 4`

If you have no clue about what inference-based injection means, enjoy some time in the background section.

### lines_per_request

With this parameter you can control how many lines of the debug script are uploaded in a single request. A higher value obviously means a faster upload, but it might be risky if you use GET requests, since the URL might become too long. The default here is 10, and the maximum is 30. Example:

> `lines_per_request = 15`

### errorstring

Sqlninja alerts the user when an HTTP error code is received (e.g.: 500 Server Error), but some applications return a custom page with a 200 OK message. In such cases, it is wise to provide sqlninja with a string that is present in that error page (and only in that page). The parameter value must be put between double quotes. For example:

> `errorstring = "an error has occurred"`

### appendcomment

By default, sqlninja appends two hyphens to the injected query in order to comment out any spurious SQL code. This is good and works in approximately 99% of the cases. However, you might want to change this behavior in some very specific scenarios. For example:

> `appendcomment = yes`

Change this setting only if you really know what you are doing.

### checkdep

Recent versions of Metasploit automatically disable DEP with the stager before injecting the DLL. However, if for some reason this does not work you can roll back to the old behavior: sqlninja will check the DEP setting on the remote machine and will try to whitelist the Metasploit stager by calling xp_regread. By default this setting is set no `no` but it is perfectly safe to re-enable the check. It will just make things a little slower, and obviously will leave a slightly larger footprint on the remote system. Example:

> `checkdep = no`

### sqlmarker

You can also override the value of the marker that is used to tell sqlninja where to inject the code (default: `__SQL2INJECT__`). It is extremely unlikely you will ever need to change this.

> `sqlmarker = SOME_WEIRD_STRING_HERE`

### b64decoder

You can override the name that sqlninja uses for the script used to decode base64 files once they are uploaded. The default is `b64decoder.vbs`. It is extremely unlikely you will ever need to change this.

> `b64decoder = somename.vbs`

## 4. Other useful information

- Sqlninja is released under the GPLv3. See the LICENSE file for details.
- Netcat is included in the sqlninja package, already in scr format.
- In verbose mode you might get a "Bareword NetPacket::IP::IP_PROTO_UDP not allowed...blah blah" error. You can safely ignore it, as it seems a harmless bug of NetPacket. If you want to get rid of it, set `$proto=17` in UDP.pm.
- All rights for the papers referenced in the background section belong to Next Generation Security Software, now part of NCC Group. I am hosting them on my website simply because I don't like this manual having dead links, and the originals were constantly moved/deleted.
- Unless you are a beginner, snowboarding on piste is lame.

## 4.1 Credits

If sqlninja has been useful to you, either because it helped in a penetration test or because you just became a millionaire stealing credit cards from e-commerce sites, be aware that it's also thanks to:

- julie - for the discussions about DNS tunneling, and a lot more
- David Litchfield and Chris Anley, authors of the papers listed in the background section
- lele - for the SQL sorcery
- pentestmonkey.net - for more SQL sorcery
- sp0nge - for all the discussions and the coding hints
- hobbit - for netcat, of course
- The Metasploit development team - for.... well, obvious
- Cesar Cerrudo - for the token kidnapping attack
- Antonin Foller - for the original custom xp_cmdshell code
- Nmonkey - for a bunch of tips, tricks and feedback, and for letting me steal a bunch of stuff from his bobcat tool.
- Tavis Ormandy - for the original KiTrap0d exploit
- Birillo and cima-asso.it - for taking sqlninja to the top of a 6130m mountain in Ladakh (don't ask)
- The Spike Riders Team - see you at the snowpark, dudes!

Additional credits for {ideas|suggestions|patches|support|alcohol} go to: s4tan, Stefano Di Paola, Elliot Kendall, geese, Philippe Schaeffer, Angelo Dell'Aera, WarGame, jussi, bambam, Ross Bushby, Konrad Malewski, Hubert Seiwert, Raul Siles, and a guy from #uncon that prefers to remain anonymous

## 4.2 Disclaimer

Sqlninja is not trivial to setup, so it should be of no use for script kiddies. In any case, what you do with this tool is uniquely your business. In order to use it you are supposed to be a professional penetration tester with some written document that authorizes you to punch holes in the network you are attacking. If you don't have such authorization, feel free to have fun anyway but be aware that this might get you in trouble with a lot of law enforcement agencies. That means you. Not us.

## 4.3 Feedback

If you have some constructive observations or ideas about current or new functionalities, or if you want to report a bug, or if sqlninja was useful in some way, please drop us a line :). Also, if you successfully used this tool in a penetration test, and that made your boss win a few more projects that will help him buying a new Porsche or bringing his trophy wife to Vegas, convince him that the hacking community deserves a donation to pay some bills and buy some booze.

## 4.4 Wisdom

Any damn fool can beg up some kind of job; it takes a wise man to make it without working -- Charles Bukowski

## 4.5 Authors

icesurfer - < r00t -at- northernfortress -dot- net >

nico - < nico -at- leidecker -dot- info >