BoxLite: Path Traversal Vulnerability in boxlite Leads to Arbitrary File Write on the Host
boxlite-ai boxlite
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| boxlite PyPI |
|
|
| boxlite-cli crates.io |
|
|
| boxlite crates.io |
|
boxlite-ai boxlite
| Product | Affected | Fixed in |
|---|---|---|
| boxlite PyPI |
|
|
| boxlite-cli crates.io |
|
|
| boxlite crates.io |
|
≥ 0.0.0-0 · < 0.9.0
|
| @boxlite-ai/boxlite npm |
|
|
| github.com/boxlite-ai/boxlite/sdks/go Go |
|
|
Boxlite is a sandbox service that allows users to create lightweight virtual machines (Boxes) and launch OCI containers within them to run untrusted code. Prior to version 0.9.0, Boxlite allows users to specify the OCI image used by containers in the sandbox. However, when processing tar entries in OCI images, Boxlite does not account for the possibility that entries may be symlinks pointing to absolute paths. An attacker can craft a malicious OCI image and distribute it on image hosting platforms such as DockerHub, tricking users into using it. Once a user loads the malicious image, the attacker can write arbitrary content to any path on the host, which can further lead to remote code execution on the host. This issue has been patched in version 0.9.0.
From the CVE record · GitHub_M
Boxlite does not safely handle OCI image tar entries that are symlinks to absolute paths. An attacker can distribute a malicious image; if a user loads it, the attacker can write arbitrary content to host paths, potentially leading to remote code execution.
Anyone running Boxlite or using PyPI boxlite, crates.io boxlite-cli or boxlite, npm @boxlite-ai/boxlite, or the Boxlite Go SDK at versions earlier than 0.9.0 should check their deployments.