Docker Sandboxes privilege escalation through untrusted state directories
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Docker | Docker Sandboxes | unknown |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Docker | Docker Sandboxes |
|
Vendor Solution
Upgrade Docker Sandboxes to version 0.53.0 or later.
Vendor Workaround
Avoid running sbx or sandboxd as root. If a privileged invocation is required, use HOME and XDG_STATE_HOME values belonging to the target account and ensure its state and configuration directories are not controlled by another user.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.103% probability within 30 days)
Key SSVC decision points have not yet been added.
| Link | Providers |
|---|---|
| https://docs.docker.com/ai/sandboxes/ |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Docker
Docker docker Sandboxes |
|
| Vendors & Products |
Docker
Docker docker Sandboxes |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Docker Sandboxes reuses existing state and configuration directories without verifying their ownership. If sbx or sandboxd is run as root with HOME or, on Linux, XDG_STATE_HOME pointing to an attacker-controlled location, a local unprivileged user can substitute control-plane sockets and configuration trusted by the root process, potentially executing commands as root. Exploitation requires a privileged invocation with an attacker-influenced environment. The issue affects Linux and macOS and is fixed in version 0.53.0. | |
| Title | Docker Sandboxes privilege escalation through untrusted state directories | |
| Weaknesses | CWE-282 | |
| References |
| |
| Metrics |
cvssV4_0
|