Docker Sandboxes
Docker Sandboxes sbx cp follows workspace symlinks outside the authorized host directory
Docker Sandboxes sbx cp does not safely confine host-side paths to a shared workspace. A malicious sandbox can create or replace a workspace symlink so that a later user-initiated copy reads a host file outside the workspace into the sandbox or writes sandbox-controlled data to a host path outside the workspace with the invoking user's permissions.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.4high · scored by CNA · CWE-59
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
Docker Docker Sandboxes
- >= 0.28.0, < 0.51.0
Fixed in 0.51.0
Mitigation
Upgrade Docker Sandboxes to version 0.51.0 or later.
Workaround
Until upgrading, do not use sbx cp with a host-side source or destination inside a workspace writable by untrusted sandbox code. Use a host-only path for the copy instead.
References
- Release notes github.com/docker/sbx-releases/releases/tag/v0…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.