fix(docker-jupyter): restrict bind directory to 0o700#7872
Open
camgrimsec wants to merge 1 commit into
Open
Conversation
The DockerJupyterServer bind directory was created with 0o777 (world read/write/execute), exposing agent-generated code and Jupyter session artifacts to any local user on the host. Docker bind mounts preserve host ownership, so the container process (uid 1000 / jovyan) retains the access it needs regardless of host-side mode. 0o700 keeps the container fully functional while removing the unnecessary host-side exposure. Refs CWE-732 (Incorrect Permission Assignment for Critical Resource).
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
1 participant
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.
The DockerJupyterServer bind directory was created with 0o777 (world read/write/execute), exposing agent-generated code and Jupyter session artifacts to any local user on the host.
Docker bind mounts preserve host ownership, so the container process (uid 1000 / jovyan) retains the access it needs regardless of host-side mode. 0o700 keeps the container fully functional while removing the unnecessary host-side exposure.
Refs CWE-732 (Incorrect Permission Assignment for Critical Resource).
Why are these changes needed?
Related issue number
Checks