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

fix: use time-constant comparison for security tokens (#9896) (CP: 5.0) #9910

Merged
merged 1 commit into from
Feb 4, 2021

Conversation

vaadin-bot
Copy link
Collaborator

No description provided.

This is the same as #9875, but also applied for the upload security key
and the push id since both of those are also used to protect against
cross-site attacks. In addition, documentation for the push id is
clarified to point out its role.
@vaadin-bot
Copy link
Collaborator Author

SonarQube analysis reported 1 issue

Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

  1. INFO VaadinSession.java#L77: Do not forget to remove this deprecated code someday. rule

@tanbt tanbt merged commit ad15179 into 5.0 Feb 4, 2021
@tanbt tanbt deleted the cherry-pick-9896-to-5.0-1611843661207 branch February 4, 2021 08:47
tanbt pushed a commit that referenced this pull request Feb 5, 2021
This is the same as #9875, but also applied for the upload security key
and the push id since both of those are also used to protect against
cross-site attacks. In addition, documentation for the push id is
clarified to point out its role.

Co-authored-by: Leif Åstrand <leif@vaadin.com>
@tanbt tanbt added this to the 1.0.14 milestone Feb 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants