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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I maintain a web application that uses Atlassian Crowd 4.2.5 (server). Because we utilize the "remote addresses" feature, I believe the application is effected by the CVE-2022-43782 vulnerability.
According to the the documentation I've read, the only ways to mitigate this vulnerability is to either disable/remove remote addresses (which is not an option for the application I administer) or to upgrade to version 4.4.4. However, Crowd v4.4.4 has disabled the ability for web applications to modify account email addresses using the Crowd REST API, and our application requires this functionality for users that wish to update/modify their email addresses in our application.
Is there any other way to mitigate CVE-2022-43782 besides the aforementioned options?
Hey @James Devos
We had issues with 4.4.4 or up as well due to the default behaviour change that doesn’t allow username changes by REST API, however we were given the below startup parameter to add and all has been fine since
-Dcrowd.email.change.by.external.apps=true
Add this, and you’ll be able to upgrade to 4.4.4 (or higher) and still change usernames using your existing process.
CCM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.