Skip to content
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.

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

file sandbox escape via container volume mount #9303

Closed
tgross opened this issue Nov 10, 2020 · 3 comments · Fixed by #9321
Closed

file sandbox escape via container volume mount #9303

tgross opened this issue Nov 10, 2020 · 3 comments · Fixed by #9321
Milestone

Comments

@tgross
Copy link
Member

tgross commented Nov 10, 2020

CVE-2020-28348 Nomad File Sandbox Escape via Container Volume Mount

A vulnerability was discovered in Nomad and Nomad Enterprise (“Nomad”) such that an operator with job submission capabilities can mount the host file system of a client agent and subvert the default Docker file sandbox feature when not explicitly disabled or when using a volume mount type. This vulnerability affects version 0.9.0 up to 0.12.7, and is fixed in the 0.12.8, 0.11.7, and 0.10.8 releases.

Nomad disables host filesystem access by default in 0.12.0 and above to prevent job operators from accessing the client filesystem used to persistently store any required data on disk. The Docker task driver provides a volume mount type which can be used to access the client host filesystem from within a container, but clients must be configured to enable mounting directories outside an allocation’s path to prevent abuse from unprivileged operators.

This issue is identified publicly as CVE-2020-28348.

@tgross tgross changed the title placeholder file sandbox escape via container volume mount Nov 11, 2020
@tgross tgross added this to the 1.0 milestone Nov 11, 2020
@shantanugadgil
Copy link
Contributor

just curious, will there be a 1.0.0-beta3 for this as well? 😃

@tgross
Copy link
Member Author

tgross commented Nov 12, 2020

@shantanugadgil as noted in the release notes, this is in master and will ship in the next beta release.

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants