Fix IDOR tokens generation #3474
Merged
Conversation
This file contains 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
|
I expect that he dropdownfield class will also need a similar change. There is also a call to Session::getNewIDORToken |
Indeed. I fixed it. |
cedric-anne
force-pushed
the
fix/idor-glpi-10.0.13
branch
from
921388c
to
0f228ce
Compare
AdrienClairembault
approved these changes
Mar 13, 2024
btry
approved these changes
Mar 13, 2024
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.
Changes description
In GLPI 10.0.13, to be validated, a IDOR token must contains the condition parameter used by the dropdown, unless this parameter is empty.
Without this change, the corresponding dropdown values could not be loaded.
Checklist
Please check if your PR fulfills the following specifications:
References
Closes #N/A