-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Include script / endpoint prominently in output #5782
Comments
well, there is a way:
and then:
|
story is that people should give the proper sqlmap command, along with that output, so the other side could reproduce it. just giving the URI would not help much as there are complex cases where you have to get the complete picture (e.g. headers being sent, POST body, content type, etc.) |
anyhow, i feel your pain, but I won't put the complete command line into that "injection point" section as it would be just plain ugly. in all cases when I needed to prove the existence of SQLi with sqlmap, used command line was A MUST |
Rather than adding that which isn't a pretty solution, where the output shows the vulnerable parameter is where I was thinking. Here's an example: https://packetstormsecurity.com/files/173874/Online-Diagnostic-Lab-Management-1.0-SQL-Injection.html We know the affected parameter, but there is no script mentioned by the researcher. This is where I feel SQLmap could make a lot of disclosure analyst's lives easier if it injected the endpoint being tested in the output, in that specific section of it. |
Is your feature request related to a problem? Please describe.
The current SQLmap output includes the parameter being injected to. It does not appear to, by default at least, include the script or endpoint. e.g. /sqlmap.php or /randoendpoint
Describe the solution you'd like
Included in the line that highlights the parameter being injected, include the script or endpoint.
Describe alternatives you've considered
Banging my head against the wall.
Additional context
There are a -lot- of script kiddies using this to find vulnerabilities. They have taken to just including SQLmap output as proof of their discovery. Which is good, it gives more confidence it is a legit SQL injection so that is awesome. But them not including the script/endpoint in disclosure, and it not being in the output, makes it living hell trying to determine if this is a new vulnerability or the same one disclosed months/years prior.
Thank you for your consideration. I am happy to offer a $100 bounty to whoever tackles this in a satisfactory way! =)
The text was updated successfully, but these errors were encountered: