[Crowd] Impact of Slowloris (Slow HTTP DoS) vulnerability on Atlassian Crowd

[Sameera Shaakunthala [inactive]]

We are going to use Crowd as the user management and SSO provider for several Atlassian applications (JIRA, Confluence, Stash, etc.). All these applications will connect to Crowd using HTTP protocol, and users will use the same to access their user profile using the same.

During a vulnerability assesment followed by manual verification we found that Crowd is vulnerable to Slowloris attack. I think that a successful attack may imapct the availability of all connected applications.

1. Are there any Crowd configuration best practices in place to mitigate the vulnerability?
2. A suggestion is to limit the number HTTP connections on client IP/host basis. Is this possible to with Tomcat?

(this vulnerability is found in many other web applications as well, but Crowd is critical as it is the centralized authentication server - which is why I'm asking this question)

[Justin Koke · Accepted solution]

This is more a problem with Tomcat and potentially the reverse proxy you have infront of Tomcat.

I would recommend that you follow the advice listed here:

http://security.stackexchange.com/a/52736

For example placing Apache Httpd/Nginx infront of Tomcat and configure it correctly to block this type of attack vector.

[Sameera Shaakunthala [inactive]]

Thank you!

That's helpful.