You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
(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)
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:
For example placing Apache Httpd/Nginx infront of Tomcat and configure it correctly to block this type of attack vector.