sqlmapproject/sqlmap
1
1
Fork 0
mirror of https://github.com/sqlmapproject/sqlmap.git synced 2025-05-29 18:23:16 +03:00
Code Issues Packages Projects Releases Wiki Activity

Updated sqlmap user's manual (markdown)

Browse Source
This commit is contained in:
stamparm 2012-06-29 07:52:12 -07:00
parent 28ece24a3a
commit e444d89912
1 changed files with 313 additions and 216 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

119
sqlmap-user's-manual.md
View File

@ -229,37 +229,33 @@ limited support for MySQL added.
# Download and update
sqlmap can be downloaded from its (http://sourceforge.net/projects/sqlmap/files/ "SourceForge File List page). It is available in two formats:
* (http://downloads.sourceforge.net/sqlmap/sqlmap-0.9.tar.gz"
name="Source gzip compressed).
* (http://downloads.sourceforge.net/sqlmap/sqlmap-0.9.zip"
name="Source zip compressed).
sqlmap can be downloaded from its [SourceForge File List page](http://sourceforge.net/projects/sqlmap/files/). It is available in two formats:
* [Source gzip compressed](http://downloads.sourceforge.net/sqlmap/sqlmap-0.9.tar.gz)
* [Source zip compressed](http://downloads.sourceforge.net/sqlmap/sqlmap-0.9.zip)
You can also checkout the latest development version from the (https://github.com/sqlmapproject/sqlmap "git)
You can also checkout the latest development version from the [Git](https://github.com/sqlmapproject/sqlmap)
repository:
```$ git clone https://github.com/sqlmapproject/sqlmap.git sqlmap-dev```
You can update it at any time to the latest development version by running:
```$ python sqlmap.py --update```
Or:
```$ git pull```
This is strongly recommended **before** reporting any bug to the [mailing list](http://www.sqlmap.org/#ml).
# Usage
```
$ python sqlmap.py -h
sqlmap/1.0-dev - automatic SQL injection and database takeover tool
http://www.sqlmap.org
[!] legal disclaimer: usage of sqlmap for attacking targets without prior mutual consent is illegal. It is the end user's responsibility to obey all applicable local, state and federal laws. Authors assume no liability and are not responsible for any misuse or damage caused by this program
[*] starting at 16:38:25
Usage: python sqlmap.py [options]
Options:
@ -466,4 +462,105 @@ Options:
--smart Conduct through tests only if positive heuristic(s)
--test-filter=TSTF Select tests by payloads and/or titles (e.g. ROW)
--wizard Simple wizard interface for beginner users
## Output verbosity
Switch: `-v`
This switch can be used to set the verbosity level of output messages. There exist **seven** levels of verbosity. The default level is **1** in which information, warning, error and critical messages and Python tracebacks (if any occur) will be displayed.
* **0**: Show only Python tracebacks, error and critical messages.
* **1**: Show also information and warning messages.
* **2**: Show also debug messages.
* **3**: Show also payloads injected.
* **4**: Show also HTTP requests.
* **5**: Show also HTTP responses' headers.
* **6**: Show also HTTP responses' page content.
A reasonable level of verbosity to further understand what sqlmap does under the hood is level **2**, primarily for the detection phase and the take-over functionalities. Whereas if you want to see the SQL payloads the tools sends, level **3** is your best choice. In order to further debug potential bugs or unexpected behaviours, we recommend you to set the verbosity to level **4** or above. This level is recommended to be used when you feed the developers with a bug report too.
## Target
At least one of these options has to be provided.
### Target URL
Switch: `-u` or `--url`
Run sqlmap against a single target URL. This switch requires an argument which is the target URL in the form `http(s)://targeturl[:port]/[...]`.
### Parse targets from Burp or WebScarab proxy logs
Switch: `-l`
Rather than providing a single target URL, it is possible to test and inject against HTTP requests proxied through [Burp proxy](http://portswigger.net/suite/) or
[WebScarab proxy](http://www.owasp.org/index.php/Category:OWASP_WebScarab_Project). This switch requires an argument which is the proxy's HTTP requests log file.
### Load HTTP request from a file
Switch: `-r`
One of the possibilities of sqlmap is loading of complete HTTP request from a textual file. That way you can skip usage of bunch of other options (e.g. setting of cookies, POSTed data, etc).
Sample content of a HTTP request file provided as argument to this switch:
```
POST /sqlmap/mysql/post_int.php HTTP/1.1
Host: 192.168.136.131
User-Agent: Mozilla/4.0
id=1
```
### Process Google dork results as target addresses
Switch: `-g`
It is also possible to test and inject on `GET` parameters on the results of your Google dork.
This option makes sqlmap negotiate with the search engine its session cookie to be able to perform a search, then sqlmap will retrieve Google first 100 results for the Google dork expression with `GET` parameters asking you if you want to test and inject on each possible affected URL.
### Load options from a configuration INI file
Switch: `-c`
It is possible to pass user's options from a configuration INI file, an example is `sqlmap.conf`.
Note that if you also provide other options from command line, those are evaluated when running sqlmap and overwrite those provided in the configuration file.
## Request
These options can be used to specify how to connect to the target url.
### HTTP data
Option: `--data`
By default the HTTP method used to perform HTTP requests is `GET`, but you can implicitly change it to `POST` by providing the data to be sent in the `POST` requests. Such data, being those parameters, are tested for SQL injection as well as any provided `GET` parameters.
### HTTP `Cookie` header
Switches: `--cookie`, `--drop-set-cookie` and `--cookie-urlencode`
This feature can be useful in two ways:
* The web application requires authentication based upon cookies and you have such data.
* You want to detect and exploit SQL injection on such header values.
Either reason brings you to need to send cookies with sqlmap requests, the steps to go through are the following:
* Login to the application with your favourite browser.
* Get the HTTP Cookie from the browser's preferences or from the HTTP proxy screen and copy to the clipboard.
* Go back to your shell and run sqlmap by pasting your clipboard as the argument of the `--cookie` switch.
Note that the HTTP `Cookie` header values are usually separated by a `;` character, **not** by an `&`. sqlmap can recognize these as separate sets of `parameter=value` too, as well as GET and POST parameters.
If at any time during the communication, the web application responds with `Set-Cookie` headers, sqlmap will automatically use its value in all further HTTP requests as the `Cookie` header. sqlmap will also automatically test those values for SQL injection. This can be avoided by providing the switch `--drop-set-cookie` - sqlmap will ignore any coming `Set-Cookie` header.
Vice versa, if you provide a HTTP `Cookie` header with `--cookie` switch and the target URL sends an HTTP
`Set-Cookie` header at any time, sqlmap will ask you which set of cookies to use for the following HTTP requests.
sqlmap by default does **not** URL-encode generated cookie payloads, but you can force it by using the `--cookie-urlencode` switch. Cookie content encoding is not declared by HTTP protocol standard in any way, so it is solely the matter of web application's behaviour.
Note that also the HTTP `Cookie` header is tested against SQL injection if the `--level` is set to **2** or above. Read below for details.
### HTTP `User-Agent` header
[TODO]