Skip to content

Python Security Policy: Add note on sandboxes #1874

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
StanFromIreland wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −0
Open

Python Security Policy: Add note on sandboxes #1874

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions security/policy.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,10 @@ and :func:`exec` are documented to execute arbitrary Python code that is
supplied as data. The :mod:`ctypes` module is documented to enable modifying
arbitrary locations in memory.

CPython does not support sandboxing untrusted Python code as a security
boundary, so escapes from such a sandbox are not vulnerabilities in Python
and should be reported to the sandbox's developers instead.

Vulnerabilities must not depend on malicious control of Python's launch
conditions, including (but not limited to) command line arguments, environment variables, or
modifications to files on the target system. We assume that, at the time Python
Expand Down
Loading