Pensar - auto fix for Exposed Remote Debug Interface with Arbitrary Code Execution Risk #853
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.
--listen 0.0.0.0:5678, exposing the debug port to all network interfaces. Updated it to--listen 127.0.0.1:5678, so the debug server only listens on localhost and is not accessible from outside the container.More Details
debugpyserver on0.0.0.0exposes a remote-debugging interface that grants arbitrary code execution to anyone who can reach the container. Because activation is governed only by environment variables (ENVIRONMENT,DEBUG), a misconfiguration or maliciously supplied value could enable this path in production. Remote attackers who discover the open port (5678) can attach a debugger and execute arbitrary Python code inside the running application.