@gitlawb/openclaude
Affected
- introduced
0, fixed0.5.1(semver)
Fixed versions
0.5.1
Fix
- Fixed version
0.5.1npm install @gitlawb/[email protected]
Advisory
Also known as: CVE-2026-35570
OpenClaude: Sandbox Bypass via Early-Exit Logic Flaw Allows Path Traversal
A logic flaw exists in bashToolHasPermission() inside src/tools/BashTool/bashPermissions.ts. When the sandbox auto-allow feature is active and no explicit deny rule is configured, the function returns an allow result immediately — before the path constraint filter (checkPathConstraints) is ever evaluated. This allows commands containing path traversal sequences (e.g., ../../../../../etc/passwd) to bypass directory restrictions entirely.
Affected Component
src/tools/BashTool/bashPermissions.tsbashToolHasPermissionVulnerable Code Flow
bashToolHasPermission()
│
├─ [~1445] Sandbox auto-allow block
│ └─ No deny rule found → return ALLOW ⚠️ Early exit
│
└─ [~1644] checkPathConstraints() ❌ Never reached
The sandbox block was designed to skip interactive permission prompts in sandboxed environments. However, it unintentionally also skips the path traversal filter, which is a separate and critical security control.
Impact
Any process or user operating in a sandboxed session with no explicit deny rules can:
/etc/passwd, /etc/shadow, .env files, SSH private keys)Steps to Reproduce
SandboxManager.isSandboxingEnabled() = trueSandboxManager.isAutoAllowBashIfSandboxedEnabled() = true cat ../../../../../etc/passwd
behavior: allow without triggering checkPathConstraintsRecommended Fix
The sandbox auto-allow block should never short-circuit the full permission pipeline. It may suppress interactive prompts, but path constraint validation must always execute.
Option 1 — Preferred: Continue pipeline on allow
Only return early for deny or ask behaviors. Let allow fall through to checkPathConstraints:
if (
SandboxManager.isSandboxingEnabled() &&
SandboxManager.isAutoAllowBashIfSandboxedEnabled() &&
shouldUseSandbox(input)
) {
const sandboxAutoAllowResult = checkSandboxAutoAllow(
input,
appState.toolPermissionContext,
);
if (sandboxAutoAllowResult.behavior !== 'allow') {
// Only block or prompt — never skip path checks on allow
return sandboxAutoAllowResult;
}
// If 'allow', continue to checkPathConstraints below
}
Option 2 — Defense in depth: Run path check before returning
Run checkPathConstraints explicitly inside the sandbox block before returning:
if (sandboxAutoAllowResult.behavior !== 'passthrough') {
const pathCheck = checkPathConstraints(input, appState.toolPermissionContext);
if (pathCheck.behavior !== 'allow') {
return pathCheck; // Block traversal attempts even in sandbox
}
return sandboxAutoAllowResult;
}
Option 3 — Minimal change: Move sandbox block after path check
Reorder the function so checkPathConstraints always runs first, and the sandbox block only handles the prompt-suppression logic afterward.
---
Credit: Elvin Latifli (@Rickidevs )
High Basis: The source's own band: HIGH
0, fixed 0.5.1 (semver)0.5.1
0.5.1npm install @gitlawb/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0