Unserialize cache data #1576
Closed
Unserialize cache data #1576
+3
−0
Conversation
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
systemsolutionweb
approved these changes
Sep 9, 2024
Owner
|
Hmmm I'm not a fan of unserialize. Are we 100% sure the value is serialized by the driver? Because otherwise a string posing as a serialized string could lead to issues (eg https://www.invicti.com/blog/web-security/untrusted-data-unserialize-php/ and more) |
Contributor
Author
|
then it is better not to risk it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
On redis driver, cache comes serialized
After
unserialize