You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
create another file alongside test.py called evil.py. In evil.py, put print('malicious code')
while test.py is the active file, run the debugpy and enter the args one & python ./evil.py
See that ./evil.py gets run.
If someone malicious wanted to run their own python script, they could inject a call into the args. Perhaps we should be sanitizing the input in some way in case it can be interfered with?
The text was updated successfully, but these errors were encountered:
The security model for extensions is either you allow them in a trusted environment or you don't. Since this extension requires a trusted environment, you are already choosing to trust the code being debugged. Whether you bothered to sanitize your code is up to you and not us.
We also can't in any way sanitize the input as we have no idea what you plan to do with the file passed in. Are you parsing it? Are you just counting the number of letters? How do we to know what you plan to do with any file which you could read from and then choose to execute or do something with that could be considered malicious?
All of this is to say, "don't run code you don't trust". 😉
Testing #64
test.py
calledevil.py
. Inevil.py
, putprint('malicious code')
test.py
is the active file, run the debugpy and enter the argsone & python ./evil.py
./evil.py
gets run.If someone malicious wanted to run their own python script, they could inject a call into the args. Perhaps we should be sanitizing the input in some way in case it can be interfered with?
The text was updated successfully, but these errors were encountered: