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
Old session not working #3799
Comments
A) There have been major changes inside sqlmap in preparing for Python3. Hence, session had to be adjusted for both Python2 and Python3. Last irreversible change has been with |
Thank you for the prompt support. However I have another question using 1.2.3#stable I can use session file but I sqlmap doesn't appear to exploit the vulnerability. I ran sqlmap with -v3 and following is the output
Performing the payloads in given by sqlmap, I can see the data but for some reason sqlmap always shuts down with
Is there are way this can be prevented? |
A) Sites tend to "patch" or "modify" stuff. You have an error-based SQLi, best one for debugging on YOUR side. Because of A) and C) I won't respond any more to this issue (as there was no issue in the first place) |
Leaving this here so that anyone having similar issue can find it. |
Describe the bug
I tried running sqlmap 1.2.25#stable (installed with brew) on vulnerable website and got valid injection point, fetching row from table was taking time so I decided to update sqlmap using brew upgrade sqlmap (running 1.3.7#stable now). I tried running sqlmap on same website but the detection phase starts from scratch instead of resuming from session.sqlite file. I tried supplying session file with -s argument but that didn't work as well. This could be issue with a using different version? I couldn't find 1.2.25 so installed 1.2.3, it runs fine(?) with the session file. The injection is resumed but sqlmap is never able to fetch any data. Even running with --hex or --no-cast didn't help.
Expected behavior
Perform injection successfully based on previous session?
Running environment:
Additional context
The text was updated successfully, but these errors were encountered: