Docs: Add a chapter on security - #75
Open
hilman2 wants to merge 1 commit into
Open
Conversation
Cheetah compiles a template into a Python module and runs it, so a template built from user input is remote code execution. No compiler setting prevents it: the example in the chapter runs unchanged with useNameMapper=False and with every directive disabled. The chapter says where user input belongs instead, and what to do when templates really are untrusted. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
2 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.
Addresses #68.
New chapter in the User's Guide: a template is code, where user input belongs instead, and why compiler settings are not a security boundary. The PoC from the issue runs unchanged with
useNameMapper=Falseand with every directive indisabledDirectives, so the chapter says so.Also a short paragraph in the README, which is where people land first.
No sandbox is proposed. Restricting Python expressions inside the same interpreter has a long history of escapes, so the chapter points at process isolation instead.