-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
web_spider sslv3 handshake failure #5802
Comments
Conditions of satisfaction:
|
Test script:
Recommend enabling DEBUG in keepalive.py Strange...
Why does it say |
@andersonDadario any idea on the last question? |
Some ideia I guess. The TLS 1.0 is similiar, but different from SSLv3, so there may be some confusion. I'm not a crypto specialist it's just a little research at google, as you can see at [1] and [2] saying the same thing. Note: My blog (dadario.com.br) is hosted at AWS (static website served from S3) so I will not be able to print the server config here if you need to :( [1] http://serverfault.com/questions/178561/what-are-the-exact-protocol-level-differences-between-ssl-and-tls |
But you can test against a nginx web server that mitigates Poodle [1] in case you need to know the web server config. "How to test for SSL POODLE vulnerability? How to disable the SSLv3 support on Nginx? [1] http://blog.adityapatawari.com/2014/10/how-to-check-for-ssl-poodle-sslv3-bug.html |
@andersonDadario maybe it's an ubuntu bug? Which OS do you use? Can you checkout 4d3da21 and run the script above to see if you get the same results? The messages will appear if you set DEBUG to True in keepalive.py |
As I told you it's a managed service From AWS to serve static sites from S3 (actually CloudFront is on the front), so I don't have access to it, but I will test against my servers that disabled sslv3 and let you know (maybe tonight). Right now there is no way, unfortunately, but I'll do it. Enviado via iPhone Anderson Dadario
|
I was asking about your desktop OS, not the server where the domain is at. |
Sorry I misunderstood, it's Ubuntu. The result after changing keepalive.py and running the script above: ./w3af_console -s test.w3af Re-sending request "<HTTPRequest "https://dadario.com.br/" (cookies:True, cache:False)>" after initial exception: "Unable to create a SSL connection using protocol: 2" strategy.start() is raising exception "The remote web server is not answering our HTTP requests, multiple errors have been found while trying to GET a response from the server. In most cases this means that the configured target is incorrect, the port is closed, there is a firewall blocking our packets or there is no HTTP daemon listening on that port. Please verify your target configuration and try again." IMPORTANT The following error was detected by w3af and couldn't be resolved: In most cases this means that the configured target is incorrect, the port is closed, there is a firewall blocking our packets or there is no HTTP daemon listening on that port. Please verify your target configuration and try again. Scan finished in 0 seconds. Liked it? Sponsor the project! |
Trying to fix this once again could you give me the output of running https://gist.github.com/andresriancho/77d1d163c9987966ce77 in your system please? Also log the OS and version, thanks! |
My output is:
|
Mine is: $ python
2015-01-30 22:39 GMT-02:00 Andres Riancho [email protected]:
Anderson Dadario https://www.linkedin.com/in/andersondadario@andersonmvd |
@andersonDadario which OS and version on your workstation? (I know I asked this before, but not specifically for this test) Anderson sent data over email, same OS and version as mine. |
Read somewhere that this could be because of SNI (requests module had this issue)
These guys say it works? |
http://my.gauntlet.io/ has SSLv3 disabled and the test script works well against it |
After some more tests:
This guides us in the direction of a SNI error, and not the initial assessment from Anderson about "As servers mitigate POODLE attack (sslv3), the web_spider can't connect anymore. Need add support for TLSv1.2 TLSv1.1 TLSv1" |
|
You're amazing. Congratulations for the fix :P 2015-02-01 22:18 GMT-02:00 Andres Riancho [email protected]:
Anderson Dadario https://www.linkedin.com/in/andersondadario@andersonmvd |
Latest commit has the following features:
Missing tests:
|
Just need to make all tests pass at circleci and I'll merge this into develop |
Fuc**** never ending story! Now httpretty doesn't support openssl so all my mocked tests which use https are failing! A list of all the feature/poodle builds can be found here This reproduces the OpenSSL un-mocked issue:
Sent some tweets to the httpretty maintainer asking if there was openssl support for his project, waiting answer. |
Much better but still not PASS: |
Looks much better, only one test is failing 👍 |
All tests but the |
Fixed in 03eaf0b |
OMGWTFBBQ |
Nice job :) Anderson Dadario https://www.linkedin.com/in/andersondadario@andersonmvd 2015-02-04 19:08 GMT-02:00 Andres Riancho [email protected]:
|
The web_spider plugin got an error while requesting "https://dadario.com.br/blog/apple-entenda-o-vazamento-de-udids-parte-1/". Reason: "[Errno 1] _ssl.c:510: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure"
As servers mitigate POODLE attack (sslv3), the web_spider can't connect anymore. Need add support for TLSv1.2 TLSv1.1 TLSv1
The text was updated successfully, but these errors were encountered: