Openclaude
Monthly
Path traversal in OpenClaude CLI versions before 0.5.1 allows local authenticated users to bypass sandbox directory restrictions and access arbitrary filesystem paths. A logic flaw in the bash permission handler causes path constraint checks to be skipped when sandbox auto-allow is enabled without explicit deny rules, permitting traversal sequences like '../../../etc/passwd' to escape containment boundaries. EPSS score of 0.01% indicates low probability of widespread exploitation, and no active exploitation has been reported.
Denial-of-service in Gitlawb openclaude (all versions up to 0.30.0) arises from improper resource handling in the `waitForCallback` function of the xAI OAuth Callback Handler (`src/services/api/xaiOAuthCallback.ts`), where a manipulated Error argument causes availability degradation. The attack is network-reachable but requires user interaction (CVSS 4.0 UI:P), resulting in a low availability impact with no confidentiality or integrity consequences. A publicly available proof-of-concept exists as GitHub issue #2101; the vendor has been notified but has not yet responded to the disclosure.
Path traversal in OpenClaude CLI versions before 0.5.1 allows local authenticated users to bypass sandbox directory restrictions and access arbitrary filesystem paths. A logic flaw in the bash permission handler causes path constraint checks to be skipped when sandbox auto-allow is enabled without explicit deny rules, permitting traversal sequences like '../../../etc/passwd' to escape containment boundaries. EPSS score of 0.01% indicates low probability of widespread exploitation, and no active exploitation has been reported.
Denial-of-service in Gitlawb openclaude (all versions up to 0.30.0) arises from improper resource handling in the `waitForCallback` function of the xAI OAuth Callback Handler (`src/services/api/xaiOAuthCallback.ts`), where a manipulated Error argument causes availability degradation. The attack is network-reachable but requires user interaction (CVSS 4.0 UI:P), resulting in a low availability impact with no confidentiality or integrity consequences. A publicly available proof-of-concept exists as GitHub issue #2101; the vendor has been notified but has not yet responded to the disclosure.