Summary
NVIDIA OpenShell Sandbox for Linux contains a path traversal vulnerability that can bypass Layer 7 REST network policy controls. An attacker who can submit or influence relevant REST requests may access unintended paths, potentially exposing information or modifying data.
Affected context
The vulnerability occurs in NVIDIA OpenShell Sandbox deployments that enforce Layer 7 REST network policies while handling attacker-influenced resource paths. Risk depends on whether requests can reach the affected policy enforcement path and whether the sandbox process has access to sensitive files or writable data outside the intended REST resource scope.
Exploit preconditions
- Attack surface: Layer 7 REST request handling in the Linux sandbox
- Required access: Ability to send or influence requests processed by the affected REST policy
- Trigger point: Path resolution and authorization of a REST resource
- Why exploitation is possible: Improper path validation may allow traversal sequences or equivalent path representations to escape the policy's intended resource boundary
Why this happens
The underlying bug is insufficient canonicalization and validation of user-influenced paths before applying access-control decisions. When a system checks a non-canonical path but later resolves it differently, an attacker may reference resources outside the permitted directory or endpoint scope. This behavior maps to CWE-22: Improper Limitation of a Pathname to a Restricted Directory, commonly known as path traversal.
Potential impact
- An attacker may disclose files or REST-accessible information outside the intended policy scope.
- An attacker could tamper with writable data reachable through the sandbox.
- Sensitive configuration, metadata, or application content may be exposed.
- The affected service may experience integrity loss if unauthorized resources can be modified.
General mitigation guidance
Mitigation generally focuses on enforcing authorization after secure path normalization and limiting requests to an explicit resource scope.
Common defensive patterns include:
- Canonicalizing paths before authorization decisions.
- Rejecting traversal sequences, ambiguous encodings, and alternate path representations.
- Resolving requested resources against a fixed permitted root and verifying the resulting path remains within that root.
- Preferencing allowlisted REST routes and resource identifiers over filesystem-like path construction.
- Running the sandbox with least-privilege filesystem permissions and minimizing writable locations.
- Applying read-only mounts and separation of sensitive data where practical.
- Treating client-supplied paths as untrusted even when they pass initial format validation.
How teams detect issues like this
Detection approaches commonly include:
- Static analysis checks for path joins, normalization, and authorization performed in an unsafe order.
- Code review of REST handlers that concatenate user input into filesystem or resource paths.
- Tests covering encoded separators, dot segments, nested traversal, symlink resolution, and platform-specific path forms.
- Runtime logging and policy alerts for rejected traversal patterns and requests resolving outside approved resource roots.
- Automated security testing and code review tools that identify path traversal and authorization-boundary weaknesses.

