BoxLite: Permission Bypass in boxlite Allows Modification of Read-Only Files
boxlite-ai boxlite
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| boxlite PyPI |
|
|
| @boxlite-ai/boxlite npm |
|
|
| github.com/boxlite-ai/boxlite/sdks/go Go |
boxlite-ai boxlite
| Product | Affected | Fixed in |
|---|---|---|
| boxlite PyPI |
|
|
| @boxlite-ai/boxlite npm |
|
|
| github.com/boxlite-ai/boxlite/sdks/go Go |
< 0.9.0
|
| boxlite crates.io |
|
|
| boxlite-cli crates.io |
|
|
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 does not restrict the kernel capabilities available inside the container, malicious code can remount the directory in rw mode, thereby gaining write access to that directory. This allows malicious code to perform arbitrary write operations on directories that should be read-only. This issue has been patched in version 0.9.0.
From the CVE record · GitHub_M
Before 0.9.0, Boxlite does not restrict kernel capabilities inside containers. Malicious code running in a container can remount a directory as read-write and write to directories intended to be read-only; the input does not specify authentication requirements or user interaction.
Anyone running boxlite-ai Boxlite or its PyPI, npm, Go, or crates.io packages at versions before 0.9.0 should check their installations.