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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Enabling
allow_pickleis necessary forrpyc.utils.classic.obtainto work, but it introduces a major security vulnerability. An attacker who can connect to this RPyC port can achieve Remote Code Execution (RCE) by sending a malicious pickled object.The
ThreadedServerdefaults to listening on all interfaces (0.0.0.0), which could expose this port to a wider network than intended.To mitigate this risk, consider the following:
Given the high risk, binding to localhost is strongly recommended if the architecture permits.