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.
Hi,
It has been identified that the forms do not have mechanisms to
prevent CSRF attacks, because of this, a malicious user can force the browser to
a victim user to generate and send requests that the application interprets as legitimate
from the victim. A successful CSRF attack can compromise the data of a
end user and through this enter "valid" requests that modify the
behavior of the application in favor of the attacker
We have a lastest versión of crowd 4.1.0 dockerized with mysql database
Thank you.
Regards
Right. So have you reported this? Is it possibly fixed in a later version?
It has not been fixed in the latest version, we have reported it
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
yes, and also in the RelayState parameter, they are lacking the business logic of the anti-CSRF.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.