Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backporting: #483 Jwt Cookie set with SameSite=Strict (#486) #487

Merged
merged 1 commit into from
Apr 6, 2021

Conversation

symphony-hong
Copy link
Contributor

Backporting change: Jwt Cookie set with SameSite=Strict (#486)

* EIS-2766: Jwt Cookie set with SameSite=Strict

The request to /bdk/v1/app/auth appears to be vulnerable
to cross-site request forgery (CSRF) attacks against authenticated users.

The request can be issued cross-domain.
The BDK relies solely on HTTP cookies to identify the user that issued the request.
The request performs some privileged action within the application, which returns a token.
The attacker can determine all the parameters required to construct a request that
performs the action. If the request contains any values that the attacker cannot
determine or predict, then it is not vulnerable.

Setting the SameSite=Strict will prevent sending the cookie when the request is done from another domain.

* Make sameSite attribute configurable with default value = Strict
@symphony-hong symphony-hong requested a review from thibauult April 5, 2021 19:31
@symphony-hong symphony-hong requested a review from a team as a code owner April 5, 2021 19:31
@symphony-hong symphony-hong merged commit f7d449b into finos:2.1-rc Apr 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants