GHSA-w5pc-m664-r62v A PinchTab Security Policy Bypass in /wait Allows Arbitrary JavaScript Execution
SummaryPinchTab `v0.8.3` through `v0.8.5` allow arbitrary JavaScript execution through `POST /wait` and `POST /tabs/{id}/wait` when the request uses `fn` mode, even if `security.allowEvaluate` is disabled.`POST /evaluate` correctly enforces the `security.allowEvaluate` guard, which is disabled by default. However, in the affected releases, `POST /wait` accepted a user-controlled `fn` expression, embedded it directly into executable JavaScript, and evaluated it in the browser context without checking the same policy.This is a security-policy bypass rather than a separate authentication bypass. Exploitation still requires authenticated API access, but a caller with the server token can execute arbitrary JavaScript in a tab context even when the operator explicitly disabled JavaScript evaluation.The current worktree fixes this by applying the same policy boundary to `fn` mode in `/wait` that already exists on `/evaluate`, while preserving the non-code wait modes.Details**Issue 1 — `/evaluate` enforced the guard, `/wait` did not (`v0.8.3` through `v0.8.5`):**
The dedicated evaluate endpoint rejected requests when `security.allowEvaluate` was disabled:In the same releases, `/wait` did not apply that guard before evaluating `fn`:**Issue 2 — `fn` mode evaluated caller-supplied JavaScript directly:**
The `fn` branch built executable JavaScript from the request field and passed it to `chromedp.Evaluate`:Because `req.Fn` was interpolated directly into evaluated JavaScript, a caller could supply expressions with side effects, not just passive predicates.**Issue 3 — Current worktree contains an unreleased fix:**
The current worktree closes this gap by making `fn` mode in `/wait` respect the same `security.allowEvaluate` policy boundary that `/evaluate` already enforced. The underlying non-code wait modes remain available.PoC**Prerequisites**PinchTab `v0.8.3`, `v0.8.4`, or `v0.8.5`A configured API token`security.allowEvaluate = false`A reachable tab context, created by the caller or already present**Step 1 — Confirm `/evaluate` is blocked by policy**Expected:**Step 2 — Open a tab**Example result:**Step 3 — Execute JavaScript through `/wait` using `fn` mode**Example result:**Step 4 — Verify the side effect**Example result:**Observation**`/evaluate` returns `evaluate_disabled` when `security.allowEvaluate` is off.`/wait` still evaluates caller-supplied JavaScript through `fn` mode in the affected releases.The first `/wait` request introduces a side effect in page state.The second `/wait` request confirms that the side effect occurred, demonstrating arbitrary JavaScript execution despite the disabled evaluate policy.ImpactBypass of the explicit `security.allowEvaluate` control in `v0.8.3` through `v0.8.5`.Arbitrary JavaScript execution in the reachable browser tab context for callers who already possess the server API token.Ability to read or modify page state and act within authenticated browser sessions available to that tab context.Inconsistent security boundaries between `/evaluate` and `/wait`, making the configured execution policy unreliable.This is not an unauthenticated issue. Practical risk depends on who can access the API and whether the deployment exposes tabs containing sensitive authenticated state.Suggested RemediationMake `fn` mode in `/wait` enforce the same policy check as `/evaluate`.Keep non-code wait modes available when JavaScript evaluation is disabled.Add regression coverage so the policy boundary remains consistent across endpoints.
CVSS v4.0 score: 6.1