Hi
This time I tried --flush-session as well and now it is showing that the
parameter is not injectable; however when I'm using old session with (-s
old_sessionfile.sqlite) it is not showing this.
Observed similar issue when few days back I tried to sqlinject same
vulnerable parameter using sqlma
In your case, 404 is indication that file has not been found in the
expected place.
Now I see that the temporary file path is not being "refreshed" by the
--fresh-queries. Please rerun the whole case with the --flush-session
Bye
p.s. in your case sqlmap tried to upload the file to the trashy loc
Hi,
Thanks for your reply.
This time I tried with --fresh-queries without specific --techniques.
why am I getting error "page not found (404)" again and again? Does it
indicate that file is being written but is deleted by Anti-Virus control or
something and that's why while calling the uploaded f
Hi.
1) First of all, please don't restrain sqlmap to only use "stacked" SQLi.
That way you'll kill the possibility to get perfectly valid results with
other techniques
2) In current state, you've got some "trashy" characters (because of
combination of laggy connection and stacked SQLi), like: "D:/
Hi All,
In first phase of our test we discovered Target URL is vulnerable and we
managed to retrieved lots of information such as --users, --dbs, some of
--tables and lots more. All this retrieval was very slow probably due to
time-based vulnerability; however tried through all (BEUSTQ) and found
