T09 · Insecure Skill Coding Practices
- Location
SKILL.md:17- Finding
Browser Sandbox Disabled in Recommended Configuration
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 17–24
Vulnerability Type: Browser isolation disabled through unsafe configuration
Risk Level: HighComplete Code Snippet:
json { "browser": { "headless": true, "noSandbox": true } }Technical Analysis
The documented configuration sets
noSandboxtotrue, disabling browser process sandboxing. Browser sandboxing is a defense-in-depth boundary intended to restrict the filesystem, process, and operating-system access available to compromised browser processes.This skill is designed to visit search results and other websites, which may contain attacker-controlled HTML, JavaScript, media, or browser-rendered content. If such content exploits a browser vulnerability, disabling the sandbox removes an important containment layer. The setting is not required for the skill's stated search and login-detection functionality.
Exploitation depends on an additional browser or rendering-engine vulnerability; the configuration does not independently provide arbitrary code execution.
Attack Path
- An attacker publishes a malicious page and causes it to appear in Bing search results or supplies a link that the skill processes.
- The skill opens the attacker-controlled page using a browser launched with
noSandbox: true. - Malicious page content triggers a compatible vulnerability in the browser or rendering engine.
- Because browser sandboxing is disabled, successful exploit code operates without the normal sandbox containment boundary.
- The exploit may access resources available to the browser process or attempt further compromise of the host environment.
Impact Assessment
A successful browser exploit could obtain the privileges of the process running the browser. Depending on that process's operating-system permissions, the attacker could potentially read or modify accessible files, access browser data, intera ...[truncated 443 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove
"noSandbox": truefrom the recommended configuration and preserve browser sandboxing by default:json { "browser": { "headless": true } } - If a particular deployment cannot start the browser with sandboxing enabled, treat disabling it as a narrowly scoped compatibility exception rather than the default recommendation.
- For unavoidable exceptions, run the browser inside a dedicated, unprivileged container or virtual machine with:
- No host filesystem mounts unless strictly required.
- A read-only root filesystem where practical.
- Dropped Linux capabilities and
no-new-privileges. - Restricted network access.
- No access to host credentials, browser profiles, or sensitive environment variables.
- Document the security consequences of disabling the sandbox and require explicit administrator approval.
- Keep the browser and rendering engine fully patched to reduce exposure to known browser vulnerabilities.
- Remove
