T09 · Insecure Skill Coding Practices
- Location
SKILL.md:34- Finding
Chromium Sandbox Explicitly Disabled
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 34–36
Vulnerability Type: Insecure browser configuration
Risk Level: MediumVulnerable Code
markdown **Rules:** - ✅ `--no-sandbox` — always required on Linux - ❌ `--disable-gpu` — **DO NOT USE** — breaks GUITechnical Analysis
The skill explicitly requires launching the Electron/Chromium-based Tandem Browser with
--no-sandbox. Chromium's sandbox is a defense-in-depth boundary that restricts compromised renderer processes and reduces their ability to interact with host resources.Disabling this protection does not by itself execute malicious code, but it materially increases the severity of a browser-engine or renderer compromise. This is particularly relevant because the skill is designed to navigate arbitrary websites and process potentially hostile web content. The document does not prescribe an equivalent compensating control such as execution inside a restricted container or virtual machine.
Attack Path
- Tandem Browser is launched according to the skill's instructions with
--no-sandbox. - The agent navigates to an attacker-controlled or compromised website.
- The website exploits a vulnerability in Chromium, Electron, or a renderer-accessible browser component.
- Because the Chromium sandbox is disabled, normal renderer isolation is absent or substantially weakened.
- Exploit code accesses resources available to the Tandem process under the current operating-system account.
Successful exploitation depends on a separate browser vulnerability; the documented flag weakens containment rather than independently providing code execution.
Impact Assessment
A successful browser compromise could expose files, credentials, browser state, authentication sessions, and other resources accessible to the operating-system account running Tandem. It could also permit arbitrary actions with that account's privileges.
The potential scope is the user's account and ...[truncated 181 chars]
- Tandem Browser is launched according to the skill's instructions with
- Remediation
View remediation
Remediation Suggestions
- Remove the unconditional requirement to launch Tandem with
--no-sandbox. - Configure the host so Chromium can use a supported sandbox mechanism, such as unprivileged user namespaces or the appropriately installed setuid sandbox.
- If sandbox disablement is unavoidable, run Tandem in a dedicated container or virtual machine with:
- A non-root, dedicated operating-system account.
- A read-only or narrowly scoped filesystem.
- No access to unrelated home-directory files, SSH keys, cloud credentials, or host browser profiles.
- Restricted network access appropriate to the browsing task.
- Dropped Linux capabilities and
no-new-privileges. - Resource and process limits.
- Use isolated Tandem sessions for untrusted browsing and avoid inheriting authenticated session state unless required.
- Document why sandbox disablement is necessary, the affected platforms, and all mandatory compensating controls.
- Keep Electron and Chromium patched to reduce exposure to known renderer and browser-engine vulnerabilities.
- Remove the unconditional requirement to launch Tandem with
