[9.x] Fixed errors occurring when encrypted cookies has been tampered with - #45313
Merged
taylorotwell merged 3 commits intoDec 14, 2022
Merged
[9.x] Fixed errors occurring when encrypted cookies has been tampered with#45313taylorotwell merged 3 commits into
taylorotwell merged 3 commits into
Conversation
Contributor
Author
|
Oh sorry, it went so fast :) I forgot to commit a little fix to the test: So that each of the 4 values would be tested separately. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Dear maintainers,
we have faced several errors, while receiving seemingly malicious requests with tampered cookie data.
ErrorException: hash_equals(): Expected user_string to be a string, array givenErrorException: base64_decode() expects parameter 1 to be string, array givenErrorException: Array to string conversionAfter investigation, we came to a conclusion, that the validation of encrypted payload is insufficient, i.e. not checking if the value is scalar. In this PR I have extended the validation and added a test to cover the case.
As per requirement I send the PR to 9.x branch, but I would greatly appreciate it the fix would be backported to version 8.x. I can not estimate if this poses a significant security threat, yet I am concerned, that this behavior can be abused in some way.