T09 · Insecure Skill Coding Practices
- Location
publish.py:57- Finding
Chromium Runs Without Its Security Sandbox
- Content
View full analysis
Vulnerability Details
File Location:
publish.py:57-60andpublish.py:111-114
Vulnerability Type: Browser sandbox disabled
Risk Level: Highpython subprocess.Popen( [str(CHROME_PATH), f"--remote-debugging-port={DEBUG_PORT}", f"--user-data-dir={str(USER_DATA_DIR)}", "--no-sandbox", "--disable-gpu", "--disable-dev-shm-usage", "https://creator.douyin.com/"], stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL, env={**os.environ, "DISPLAY": ":99"} )The same insecure
--no-sandboxoption is also used bystart_browser():python subprocess.Popen( [str(CHROME_PATH), f"--remote-debugging-port={DEBUG_PORT}", f"--user-data-dir={str(USER_DATA_DIR)}", "--no-sandbox", "--disable-gpu", "--disable-dev-shm-usage", "https://creator.douyin.com/"], stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL, env={**os.environ, "DISPLAY": ":1"} )Technical Analysis
Chromium's sandbox separates renderer processes handling untrusted web content from the host operating system. Passing
--no-sandboxremoves this important security boundary. If malicious or compromised web content exploits a Chromium vulnerability, the resulting code may run directly with the privileges of the user who invoked the Skill rather than remaining confined to a restricted renderer process.The impact is amplified because the browser uses a persistent profile under
chrome_profile/. This profile can contain authenticated Douyin cookies, tokens, local storage, and other account state. The browser is also exposed through a remote debugging port. Although the script connects through127.0.0.1, the launch command does not explicitly set--remote-debugging-address=127.0.0.1.Attack Path
- The user invokes the Skill, which launches Chromium with
--no-sandbox. - Chromium loads the Douyin creator site and its associated web resources.
- An attacker ...[truncated 920 chars]
- The user invokes the Skill, which launches Chromium with
- Remediation
View remediation
Remediation Suggestions
- Remove
--no-sandboxand run Chromium with its standard sandbox enabled. - Run the browser as a dedicated, unprivileged operating-system user.
- If the hosting environment cannot support Chromium's sandbox, isolate the entire process in a hardened container or virtual machine with:
- No privileged mode.
- Minimal Linux capabilities.
- A read-only root filesystem where practical.
- Only explicitly required writable mounts.
- No access to unrelated host files or credentials.
- Restricted outbound network access.
- Explicitly add
--remote-debugging-address=127.0.0.1. - Use a random or dynamically allocated debugging port and prevent access by unrelated local processes where possible.
- Restrict the permissions of
chrome_profile/to the owning user. - Keep Chromium and Playwright updated to reviewed, pinned security releases.
- Remove
