Docker Sandboxes
Docker Sandboxes host Git executes repository-controlled programs
Docker Sandboxes versions 0.31.0 before 0.50.0 do not neutralize repository-controlled Git configuration when running certain host-side Git commands. An attacker who can modify a host repository's Git configuration, for example through a direct-mode sandbox with the repository mounted read-write, can configure core.fsmonitor or another Git setting that invokes an external program. Git can execute the program during a later clone-mode fetch or, starting in version 0.39.0, an sbx kit push initiated by the user. The program runs on the host with the invoking user's permissions, outside the sandbox's microVM isolation. The read-only host repository mount provided to a clone-mode sandbox does not itself allow that sandbox to modify the host repository's Git configuration. The issue is fixed in version 0.50.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 0.31.0, < 0.50.0
Fixed in 0.50.0
Mitigation
Upgrade Docker Sandboxes to version 0.50.0 or later.
Workaround
Until upgrading, do not run clone-mode sandbox creation or start, or sbx kit push, in repositories whose Git configuration or .git metadata can be modified by untrusted code, such as a repository mounted read-write into another sandbox.
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.