Fix SSTI vulnerability in FreemarkerTemplateEngine and add security #706
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.
fix: add security validation to FreemarkerTemplateEngine to prevent SSTI
This patch introduces a validation step before processing Freemarker templates
to detect and block potentially dangerous expressions that could lead to
Server-Side Template Injection (SSTI).
Specifically, the new
validateTemplateSecurity()method scans the templatecontent for forbidden patterns such as:
If any of these are detected, an XDocReportException is thrown to stop template
execution.
This fix does not change normal template rendering behavior and remains fully
backward compatible for safe templates.