Microsandbox
Monthly
Local information disclosure in microsandbox before 0.5.10 exposes sandbox secret values - host-side API keys, tokens and environment secrets - to any other local user or co-resident process on the same host, which can simply read them from the sandbox process command line while the sandbox is running. The Rust SDK serializes NetworkConfig secret values into the --network-config argument and passes per-sandbox secrets through repeated --env arguments, keeping them visible in /proc/<pid>/cmdline on Linux and process listings on macOS for the entire sandbox lifetime, with no code execution inside the sandbox and no access to the spawning user's session required. Rated CVSS 3.1 6.5 (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N, medium), the flaw is only exploitable on shared/multi-tenant hosts, CI runners and developer systems where an adversary holds a separate local account or co-tenant process, and only leaks data when secrets were actually configured; no public exploit code has been identified at time of analysis, and the issue is fixed in 0.5.10.
Local information disclosure in microsandbox before 0.5.10 exposes sandbox secret values - host-side API keys, tokens and environment secrets - to any other local user or co-resident process on the same host, which can simply read them from the sandbox process command line while the sandbox is running. The Rust SDK serializes NetworkConfig secret values into the --network-config argument and passes per-sandbox secrets through repeated --env arguments, keeping them visible in /proc/<pid>/cmdline on Linux and process listings on macOS for the entire sandbox lifetime, with no code execution inside the sandbox and no access to the spawning user's session required. Rated CVSS 3.1 6.5 (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N, medium), the flaw is only exploitable on shared/multi-tenant hosts, CI runners and developer systems where an adversary holds a separate local account or co-tenant process, and only leaks data when secrets were actually configured; no public exploit code has been identified at time of analysis, and the issue is fixed in 0.5.10.