Configurable allowlist-based Twig sandbox#18216
Merged
Merged
Conversation
brandonkelly
changed the title
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
1 participant
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.
Adds three new
Viewmethods:renderSandboxedTemplate()renderSandboxedString()renderSandboxedObjectTemplate()Twig’s Sandbox extension is now enabled when both:
enableTwigSandboxconfig setting is enabled (Disallow non-Closure arrow functions #18208)The Sandbox extension is now configured with a security policy that prevents tags, filters, functions, methods, and properties, based on built-in allowlist. Additional things can be added to the allowlist via
config/twig-sandbox.php, which will be merged into the default array (recursively).Only system message templates are currently rendered as sandboxed. Any plugins that have user-editable templates are recommended to use these new methods as well.