ashenchowthee / zaproxy

Automatically exported from code.google.com/p/zaproxy
0 stars 0 forks source link

Quick Scan attack not starting and blocking Attack button access #1471

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Open ZAProxy
2. Enter localhost URL to attack (this case, it was openam:808/xxx/redirecturl)
3. Click attack

What is the expected output? What do you see instead?
Expected it to attack the URL, or fail with a message and give a chance to 
re-attack

Instead:
the attack button greys out, the stop button is enabled and Progress: is "Not 
Started"
Clicking the stop button greys out the start button, but the attack button is 
no longer available.

What version of the product are you using? On what operating system?
OS X 10.9.5 - ZAP - 2.3.1 (2)

Please provide any additional information below.
Changing the mode from standard to protected, then back to standard makes the 
attack button accessible again

Original issue reported on code.google.com by StevenJC...@gmail.com on 17 Dec 2014 at 2:20

GoogleCodeExporter commented 9 years ago
Are there any errors in the zap.log file?
https://code.google.com/p/zaproxy/wiki/FAQhelp

Original comment by psii...@gmail.com on 17 Dec 2014 at 2:29

GoogleCodeExporter commented 9 years ago
Firstly, apologies about the lack of log. I am still getting to grips with ZAP.

Secondly, apologies but it has started working now (even after numerous 
restarting etc while it didn't!)

I will keep the log tailed why I play about with the application. 

Would it be best to close this for now and create another issue when I 
encounter it again or update this issue?

Argh, frustration with it playing nice with an openam 302 redirect!!! :)

Original comment by StevenJC...@gmail.com on 17 Dec 2014 at 2:57

GoogleCodeExporter commented 9 years ago
Okay, I restarted ZAP and reproduced the error. This is all that appears in the 
log while this occurs:

2014-12-17 14:59:22,081 INFO  HttpSessionsSite - Created a new session as no 
match was found: HttpSession [name=Session 0, active=false, tokenValues='']
2014-12-17 14:59:22,249 INFO  ExtensionHttpSessions - Added new session token 
for site 'www.google.co.uk:443': SID
2014-12-17 14:59:22,471 INFO  HttpSessionsSite - Created a new session as no 
match was found: HttpSession [name=Session 1, active=false, tokenValues='']
2014-12-17 14:59:29,003 INFO  Control - Discard Session
2014-12-17 14:59:29,040 INFO  Control - Create and Open Untitled Db
2014-12-17 14:59:29,061 INFO  ENGINE - dataFileCache commit start
2014-12-17 14:59:29,065 INFO  ENGINE - Database closed
2014-12-17 14:59:29,239 INFO  ENGINE - dataFileCache open start
2014-12-17 14:59:29,240 INFO  ENGINE - dataFileCache open end
2014-12-17 14:59:29,649 INFO  Control - New Session
2014-12-17 15:00:08,456 INFO  ExtensionHttpSessions - Added new session token 
for site 'code.google.com:443': SID
2014-12-17 15:00:09,693 INFO  HttpSessionsSite - Created a new session as no 
match was found: HttpSession [name=Session 0, active=false, tokenValues='']
2014-12-17 15:00:10,392 INFO  ExtensionHttpSessions - Added new session token 
for site 'apis.google.com:443': SID
2014-12-17 15:00:10,633 INFO  HttpSessionsSite - Created a new session as no 
match was found: HttpSession [name=Session 1, active=false, tokenValues='']

Original comment by StevenJC...@gmail.com on 17 Dec 2014 at 3:01

GoogleCodeExporter commented 9 years ago
Nothing there then :(
Can you explain a little bit more about how you can reproduce it?
And what you are doing differently from when it worked ok?

Original comment by psii...@gmail.com on 18 Dec 2014 at 9:42

GoogleCodeExporter commented 9 years ago
ZAP has been migrated to github

This issue will be on github issues with the same ID: 
https://github.com/zaproxy/zaproxy/issues

Original comment by psii...@gmail.com on 5 Jun 2015 at 9:17