BoxLite: Timeout Bypass Vulnerability
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| boxlite-ai | boxlite | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Boxlite-ai | Boxlite |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-xjhv-pp2r-6f82 | BoxLite has a Timeout Bypass Vulnerability |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.268% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Boxlite-ai
Boxlite-ai boxlite |
|
| Vendors & Products |
Boxlite-ai
Boxlite-ai boxlite |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Boxlite is a sandbox service that allows users to create lightweight virtual machines (Boxes) and launch OCI containers within them to run untrusted code. In versions 0.8.2 and prior, Boxlite allows users to configure a timeout for services running inside the virtual machine. When the timeout is triggered, Boxlite sends a signal to kill the process. However, instead of using the uncatchable SIGKILL signal, Boxlite uses the catchable SIGALRM signal. Malicious code running inside the sandbox can exploit this vulnerability to continue running after the timeout is triggered, leading to resource exhaustion within the virtual machine and affecting the availability of the Boxlite service. This issue has been patched via commit 28159fc. | |
| Title | BoxLite: Timeout Bypass Vulnerability | |
| Weaknesses | CWE-404 | |
| References |
| |
| Metrics |
cvssV3_1
|