Skip to content
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

Empty scan findings #2

Closed
wvdongen opened this issue Sep 26, 2014 · 4 comments
Closed

Empty scan findings #2

wvdongen opened this issue Sep 26, 2014 · 4 comments

Comments

@wvdongen
Copy link

image

The sqlmapapi reported:
[23:23:09] [DEBUG] [9fb2cdda8d37dd3e] Retrieved scan data and error messages

Burp extender output reported:
Scan for task 9fb2cdda8d37dd3e completed. Gathering results.
If the page was vulnerable, then findings for task 9fb2cdda8d37dd3e have been reported.

@codewatchorg
Copy link
Owner

Is the tested page actually vulnerable? You can connect to the API and retrieve the log information with:
GET /scan/9fb2cdda8d37dd3e/log

If there were results, you can check with:
GET /scan/9fb2cdda8d37dd3e/data

My guess is that the scan completed successfully but that there were no results. If that is the case, I need to update the code to not add anything to the Burp scan results tab if the results are empty.

@codewatchorg
Copy link
Owner

Yeah, I just confirmed, it is adding a result even if the results were empty. Will work on a fix.

@codewatchorg
Copy link
Owner

I believe this is fixed now. If you run a scan and the page is not vulnerable to SQL injection, then nothing will be added to the Burp scanner results tab.

@wvdongen
Copy link
Author

Just tested it, no more empty results present.

Thanks!

@wvdongen wvdongen closed this as completed Oct 3, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants