mirror of
https://github.com/sqlmapproject/sqlmap.git
synced 2024-11-25 11:03:47 +03:00
27 lines
1.3 KiB
Markdown
27 lines
1.3 KiB
Markdown
## What's the problem (or question)?
|
|
<!--- If describing a bug, tell us what happens instead of the expected behavior -->
|
|
<!--- If suggesting a change/improvement, explain the difference from current behavior -->
|
|
|
|
## Do you have an idea for a solution?
|
|
<!--- Not obligatory, but suggest a fix/reason for the bug, -->
|
|
<!--- or ideas how to implement the addition or change -->
|
|
|
|
## How can we reproduce the issue?
|
|
<!--- Provide unambiguous set of steps to reproduce this bug. Include command to reproduce, if relevant (you can mask the sensitive data) -->
|
|
1.
|
|
2.
|
|
3.
|
|
4.
|
|
|
|
## What are the running context details?
|
|
<!--- Include as many relevant details about the running context you experienced the bug/problem in -->
|
|
* Installation method (e.g. `pip`, `apt-get`, `git clone` or `zip`/`tar.gz`):
|
|
* Client OS (e.g. `Microsoft Windows 10`)
|
|
* Program version (`python sqlmap.py --version` or `sqlmap --version` depending on installation):
|
|
* Target DBMS (e.g. `Microsoft SQL Server`):
|
|
* Detected WAF/IDS/IPS protection (e.g. `ModSecurity` or `unknown`):
|
|
* SQLi techniques found by sqlmap (e.g. `error-based` and `boolean-based blind`):
|
|
* Results of manual target assessment (e.g. found that the payload `query=test' AND 4113 IN ((SELECT 'foobar'))-- qKLV` works):
|
|
* Relevant console output (if any):
|
|
* Exception traceback (if any):
|