T09 · Insecure Skill Coding Practices
- Location
SKILL.md:51- Finding
Chrome Runs Without Its Security Sandbox
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill matches its stated VPS browser setup purpose, but it needs Review because it combines root-level setup, disabled Chrome sandboxing, unsafe proxy credential handling, and broad firewall changes.
Use this only on an isolated VPS you can rebuild. Before installing, remove Chrome --no-sandbox/noSandbox=true, run the browser stack as an unprivileged user, explicitly bind noVNC/websockify/CDP to loopback, avoid inline proxy credentials, and review firewall changes manually instead of applying the provided UFW block unchanged.
SKILL.md:51Chrome Runs Without Its Security Sandbox
SKILL.md:95Authenticated Proxy Credentials Are Embedded in Process Arguments and Transmitted Using Plaintext Basic Authentication
SKILL.md:160Skill Replaces Host-Wide Firewall Policy and Opens Unnecessary Inbound Ports
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
# Clean stale locks
rm -f /tmp/.X99-lock ~/.openclaw/browser/openclaw/user-data/SingletonLock 2>/dev/null
# Virtual display
Xvfb :99 -screen 0 1280x800x24 &
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
pkill -9 chrome
rm -f ~/.openclaw/browser/openclaw/user-data/SingletonLock
DISPLAY=:99 google-chrome-stable --no-sandbox --disable-gpu \
--remote-debugging-port=18800 \
--user-data-dir=~/.openclaw/browser/openclaw/user-data \
No suspicious patterns detected.