Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
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

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,467,374
Community Members
 
Community Events
177
Community Groups

Struts security updates for Crowd

Edited
Edmon Uyan
Edmon Uyan Apr 02, 2018

Hi there,

My first time to post regarding my setup. Basically I have the following set up on premise.

  • Crowd 2.8.3 (Build:#648 - 2015-06-01)
  • JIRA (v7.4.2#74004-sha1:586975d)
  • Confluence 5.5.2
  • Stash v3.8.0

Upon closer inspection at my deployment, my Crowd is using Struts, and worst, it's vulnerable. I could be using perhaps Struts version 2.3.29.

It states here that Struts can be updated separately without impacting Crowd. However, upon testing, Crowd stopped working after updating struts only. So my only option is to upgrade Crowd to a non-vulnerable version.

There have been a couple of major security updates with Struts that have been released even after the advisory above, with the latest one released only a few days ago which requires me to update to the latest Struts 2.5.16.

Now, I am at a dilemma, that I may need to upgrade both Crowd as well as Struts!

I am however, hesitant to upgrade/patch as it might break or change the way my users (JIRA, Confluence, Stash) operate which I would not want to take risk at.

My question is:

  • Will upgrading Crowd not impose any operational changes that the users will have to adjust to? They operate only in JIRA/Confluence/Stash
  • Follow-up to my question above... which version of Crowd do I apply that can support Struts 2.5.16?

Thank you.

Regards,

Edmon

Answer
Watch
Like Be the first to like this
800 views

1 answer

0 votes
kennyngkk
kennyngkk Atlassian Team Apr 10, 2018

Hi Edmon, 

From the look at your question, I have verified that the version of Crowd you are using is Struts version 2.3.20.1.

  • I have also checked the latest version of Crowd, it is currently using Struts version 2.5.13.
  • it looks like Crowd 3.2 is under development with Struts 2.5.16 with estimation time of release about the end of this month or beginning of next month. 

 

You will not need to update struts as this is in build into the crowd. All you need to do is update Crowd and it will be updated. 

For functionality wise, I don't think it will impact any operational. However is always better be safe the sorry

  • Have a look at the changed summary Crowd Change Summary
  • Do the changes in a test instance before proceeding with production

 

Let us know if you have any further inquiry. 

View More Comments
Like
Reply

Suggest an answer

Log in or Sign up to answer
Crowd
Crowd
TAGS

Atlassian Community Events

See all events