Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,700
Community Members
 
Community Events
176
Community Groups

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

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)

1 answer

1 accepted

1 vote
Answer accepted
JustinK Rising Star May 07, 2014

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.

Thank you!

That's helpful.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events