Home → Questions →

unable to get --http-proxy working

• Edit

Piyush

23 Dec, 2016 01:58 PM

Hello,

I want scanner traffic to pass through ZAP proxy. So, I used --http-proxy option but it didn't work. However, I can successfully connect to ZAP proxy from my firefox browser. I am using "Arachni 2.0dev (ruby 2.2.3p173) [x86_64-linux]" on RHEL 7.

I tried following combinations without any success:

--http-proxy="http://10.13.35.151:8080" --http-proxy='http://10.13.35.151:8080' --http-proxy= http://10.13.35.151:8080 --http-proxy http://10.13.35.151:8080 --http-proxy="10.13.35.151:8080" --http-proxy='10.13.35.151:8080' --http-proxy= 10.13.35.151:8080 --http-proxy 10.13.35.151:8080

Am I doing something wrong here.

1. Support Staff 1 Posted by Tasos Laskos on 23 Dec, 2016 02:05 PM

   

   --http-proxy=10.13.35.151:8080 should have worked but I'm not aware of any issues with that option. Have you tried setting the --http-proxy-type to the right type? Automatic detection can fail sometimes.

   • Edit

2. 2 Posted by Piyush on 23 Dec, 2016 02:10 PM

   

   yes I tried that as well. Unfortunately, it didn't help too.

   • Edit

3. Support Staff 3 Posted by Tasos Laskos on 23 Dec, 2016 02:21 PM

   

   I'm not sure what's going on but I can confirm that the option works properly, I just verified it using an intercepting HTTP proxy.

   • Edit

4. 4 Posted by Piyush on 23 Dec, 2016 03:27 PM

   

   I just ran straight away scan on target without any vector feed and other customization and I am getting timeout error for all 6 browsers spawned. Any possibility of timeout due to HTTPS certificate issue. I didn't receive any request in my proxy tool.

   command used
   ./arachni https://example.com/test/ --http-proxy=10.13.35.151:8080

   • Edit

5. Support Staff 5 Posted by Tasos Laskos on 24 Dec, 2016 07:13 AM

   

   It's probably because the browser processes took a long time to spawn, the nightlies allow a larger timeout that should resolve the issue.

   • Edit

6. 6 Posted by Piyush on 27 Dec, 2016 12:52 PM

   

   I believe browser processes are spawned correctly but due to proxy switch there is some communication issue between scanner and proxy. Hence, timeout occurred.

   command used
   ./arachni https://example.com/test/ --http-proxy=10.13.35.151:8080 --http-proxy-type=http

    BrowserCluster: Initializing 6 browsers...
    [*] BrowserCluster: Spawned #1 with PID 23313 [lifeline at PID 23310].
    [*] BrowserCluster: Spawned #2 with PID 23336 [lifeline at PID 23333].
    [*] BrowserCluster: Spawned #3 with PID 23358 [lifeline at PID 23355].
    [*] BrowserCluster: Spawned #4 with PID 23380 [lifeline at PID 23377].
    [*] BrowserCluster: Spawned #5 with PID 23402 [lifeline at PID 23399].
    [*] BrowserCluster: Spawned #6 with PID 23424 [lifeline at PID 23421].
    [*] BrowserCluster: Initialization completed with 6 browsers in the pool.
    [-] Retrying for: https://example.com/test [Timeout was reached]
    [-] Retrying for: https://example.com/test [Timeout was reached]
    [-] Retrying for: https://example.com/test [Timeout was reached]
    [-] Retrying for: https://example.com/test [Timeout was reached]
    [-] Retrying for: https://example.com/test [Timeout was reached]
    [-] Retrying for: https://example.com/test [Timeout was reached]
   [-] [framework/parts/data#pop_page_from_url_queue:147] Giving up trying to audit: https://example.com/test
   [-] [framework/parts/data#pop_page_from_url_queue:148] Couldn't get a response after 5 tries: Timeout was reached.
   

   Just to reconfirm on --http-proxy switch. This means arachni ---> proxy ----> target

   • Edit

7. Support Staff 7 Posted by Tasos Laskos on 27 Dec, 2016 12:56 PM

   

   That's not the browsers, that's the system in general. Something's wrong with the proxy, there's no com between arachni and the target.

   • Edit

8. 8 Posted by Piyush on 27 Dec, 2016 01:33 PM

   

   Any way to debug. I tried both burp & zap proxy and result is same; timeout. I tried running proxy on different systems too without any success. Additionally, in both the cases traffic from browser went well to proxy.

   Is there any requirement of running scanner with admin privileges?

   • Edit

9. Support Staff 9 Posted by Tasos Laskos on 27 Dec, 2016 03:28 PM

   

   No it's not a privilege issue and there's not much to debug, there's no response at all from either the proxy of the target.
   I'm not sure how I can help you since I'm pretty certain that proxy support works in Arachni as I was able to ran a proxied scan.

   • Edit

10. 10 Posted by Piyush on 28 Dec, 2016 07:40 AM

    

    I found that there was a network issue with that host. Tried on a different host and it is working good. I can run a proxied scan now. Thanks!

    • Edit

11. Tasos Laskos closed this discussion on 28 Dec, 2016 08:13 AM.