T09 · Insecure Skill Coding Practices
- Location
SKILL.md:99- Finding
Chromium Security Sandbox Explicitly Disabled
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 99-105
Vulnerability Type: Browser sandbox disabled through insecure launch flags
Risk Level: Mediumjs const browser = await puppeteer.launch({ headless: false, executablePath: process.env.CHROME_BIN || '/snap/bin/chromium', userDataDir: process.env.CHROME_PROFILE || `${process.env.HOME}/.cache/dice-chrome`, defaultViewport: null, args: ['--no-sandbox', '--disable-setuid-sandbox', '--disable-dev-shm-usage', '--start-maximized'] });Technical Analysis
The recommended Puppeteer configuration passes both
--no-sandboxand--disable-setuid-sandboxto Chromium. These flags disable important operating-system isolation boundaries intended to contain a compromised browser renderer.This workflow visits remote web content while using a persistent, authenticated Chromium profile and uploading sensitive employment documents. If malicious page content or a compromised third-party resource exploits a Chromium vulnerability, disabling the sandbox can make it easier for the exploit to reach the privileges and local resources available to the browser process. The configuration is therefore unsafe for routine execution on a workstation or host containing sensitive information.
Attack Path
- An operator launches the documented automation with the sandbox-disabling flags.
- Chromium loads Dice pages and remotely hosted browser resources while using a persistent authenticated profile.
- Malicious or compromised web content exploits a compatible Chromium vulnerability.
- Because the browser sandbox is disabled, the exploit has a reduced isolation barrier between renderer content and the agent user's environment.
- Successful host-level execution could access resources available to the browser process, including local files permitted to that user, uploaded documents, browser-profile data, and application state.
This path requires a ...[truncated 671 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove
--no-sandboxand--disable-setuid-sandboxfrom the Chromium arguments and retain the browser's supported sandbox configuration. - Run Chromium as a dedicated, unprivileged operating-system user rather than as root or an administrative account.
- Keep Chromium and Puppeteer patched to supported versions so known browser vulnerabilities are addressed promptly.
- Store the persistent profile with restrictive filesystem permissions and use it only for this workflow.
- Limit the automation account's access to the specific resume, cover letter, state directory, and required browser files.
- If sandbox-disabling flags are unavoidable in a constrained environment, run the browser in a disposable, strongly isolated container or virtual machine with no sensitive host mounts, no unnecessary credentials, restricted networking, dropped Linux capabilities, and a read-only filesystem wherever practical.
- Document the sandbox requirement as an exceptional compatibility fallback rather than presenting it as the default launch pattern.
- Remove
