I encountered a situation where the console - I am running usally at debug level 2 or 3 is flooded with HTTP 400 (which are kind of annoying): ``` [15:02:41] [DEBUG] got HTTP error code: 400 (Bad Request) [15:02:41] [DEBUG] got HTTP error code: 400 (Bad Request) [15:02:42] [DEBUG] got HTTP error code: 400 (Bad Request) [15:02:42] [DEBUG] got HTTP error code: 400 (Bad Request) [15:02:42] [DEBUG] got HTTP error code: 400 (Bad Request) [15:02:43] [DEBUG] got HTTP error code: 400 (Bad Request) [15:02:43] [DEBUG] got HTTP error code: 400 (Bad Request) [15:02:44] [DEBUG] got HTTP error code: 400 (Bad Request) [15:02:44] [DEBUG] got HTTP error code: 400 (Bad Request) [15:02:44] [DEBUG] got HTTP error code: 400 (Bad Request) [15:02:45] [DEBUG] got HTTP error code: 400 (Bad Request) [15:02:45] [DEBUG] got HTTP error code: 400 (Bad Request) [15:02:46] [DEBUG] got HTTP error code: 400 (Bad Request) [15:02:46] [DEBUG] got HTTP error code: 400 (Bad Request) [15:02:46] [DEBUG] got HTTP error code: 400 (Bad Request) [15:02:47] [DEBUG] got HTTP error code: 400 (Bad Request) [15:02:47] [DEBUG] got HTTP error code: 400 (Bad Request) [15:02:48] [DEBUG] got HTTP error code: 400 (Bad Request) [15:02:52] [DEBUG] got HTTP error code: 400 (Bad Request) ``` as this is triggered by almost every request. This is a workaround for the above scenario so that on the console I see only what I wanted to, like: ``` [18:51:18] [INFO] testing 'OR boolean-based blind - WHERE or HAVING clause (Generic comment)' [18:51:41] [INFO] testing 'OR boolean-based blind - WHERE or HAVING clause (Generic comment) (NOT)' [18:52:06] [INFO] testing 'Boolean-based blind - Parameter replace (DUAL)' [18:52:06] [INFO] testing 'Boolean-based blind - Parameter replace (DUAL) (original value)' [18:52:07] [INFO] testing 'Boolean-based blind - Parameter replace (CASE)' [18:52:08] [INFO] testing 'Boolean-based blind - Parameter replace (CASE) (original value)' [18:52:08] [INFO] testing 'Oracle AND boolean-based blind - WHERE or HAVING clause (CTXSYS.DRITHSX.SN)' [18:52:34] [INFO] testing 'Oracle OR boolean-based blind - WHERE or HAVING clause (CTXSYS.DRITHSX.SN)' [18:52:57] [INFO] testing 'Oracle boolean-based blind - Parameter replace' [18:52:57] [INFO] testing 'Oracle boolean-based blind - Parameter replace (original value)' [18:52:58] [INFO] testing 'Oracle boolean-based blind - ORDER BY, GROUP BY clause' [18:52:59] [INFO] testing 'Oracle boolean-based blind - ORDER BY, GROUP BY clause (original value)' [18:53:00] [INFO] testing 'Oracle boolean-based blind - Stacked queries' [18:53:23] [INFO] testing 'Oracle AND error-based - WHERE or HAVING clause (XMLType)' [18:53:41] [INFO] testing 'Oracle OR error-based - WHERE or HAVING clause (XMLType)' [18:53:57] [INFO] testing 'Oracle AND error-based - WHERE or HAVING clause (UTL_INADDR.GET_HOST_ADDRESS)' [18:54:13] [INFO] testing 'Oracle OR error-based - WHERE or HAVING clause (UTL_INADDR.GET_HOST_ADDRESS)' [18:54:26] [INFO] testing 'Oracle AND error-based - WHERE or HAVING clause (CTXSYS.DRITHSX.SN)' [18:54:43] [INFO] testing 'Oracle OR error-based - WHERE or HAVING clause (CTXSYS.DRITHSX.SN)' [18:54:57] [INFO] testing 'Oracle AND error-based - WHERE or HAVING clause (DBMS_UTILITY.SQLID_TO_SQLHASH)' [18:55:13] [INFO] testing 'Oracle OR error-based - WHERE or HAVING clause (DBMS_UTILITY.SQLID_TO_SQLHASH)' [18:55:27] [INFO] testing 'Oracle error-based - Parameter replace' [18:55:27] [INFO] testing 'Oracle error-based - ORDER BY, GROUP BY clause' ``` Admittedly this is may seem a bit hackish as it only addresses HTTP 400 and doesn't cover other app specific errors which can happen in other scenarios. It could also be that ``--suppress-400`` would sound better as it would describe better what it does but as there's ``--ignore-401`` so I settled for ``--ignore-400``. |
||
---|---|---|
doc | ||
extra | ||
lib | ||
plugins | ||
procs | ||
shell | ||
tamper | ||
thirdparty | ||
txt | ||
udf | ||
waf | ||
xml | ||
.gitattributes | ||
.gitignore | ||
.travis.yml | ||
ISSUE_TEMPLATE.md | ||
README.md | ||
sqlmap.conf | ||
sqlmap.py | ||
sqlmapapi.py |
sqlmap
sqlmap is an open source penetration testing tool that automates the process of detecting and exploiting SQL injection flaws and taking over of database servers. It comes with a powerful detection engine, many niche features for the ultimate penetration tester and a broad range of switches lasting from database fingerprinting, over data fetching from the database, to accessing the underlying file system and executing commands on the operating system via out-of-band connections.
Screenshots
You can visit the collection of screenshots demonstrating some of features on the wiki.
Installation
You can download the latest tarball by clicking here or latest zipball by clicking here.
Preferably, you can download sqlmap by cloning the Git repository:
git clone --depth 1 https://github.com/sqlmapproject/sqlmap.git sqlmap-dev
sqlmap works out of the box with Python version 2.6.x and 2.7.x on any platform.
Usage
To get a list of basic options and switches use:
python sqlmap.py -h
To get a list of all options and switches use:
python sqlmap.py -hh
You can find a sample run here. To get an overview of sqlmap capabilities, list of supported features and description of all options and switches, along with examples, you are advised to consult the user's manual.
Links
- Homepage: http://sqlmap.org
- Download: .tar.gz or .zip
- Commits RSS feed: https://github.com/sqlmapproject/sqlmap/commits/master.atom
- Issue tracker: https://github.com/sqlmapproject/sqlmap/issues
- User's manual: https://github.com/sqlmapproject/sqlmap/wiki
- Frequently Asked Questions (FAQ): https://github.com/sqlmapproject/sqlmap/wiki/FAQ
- Twitter: @sqlmap
- Demos: http://www.youtube.com/user/inquisb/videos
- Screenshots: https://github.com/sqlmapproject/sqlmap/wiki/Screenshots