T05 · Unauthorized Access and Privilege Escalation
- Location
browser-fetch.mjs:169- Finding
Unrestricted Browser Navigation Enables Server-Side Request Forgery
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This browser-fetch skill does what it says, but it gives agents a powerful unsandboxed browser that can reach arbitrary network locations and may expose proxy credentials in output.
Use this only in a tightly isolated environment with no access to localhost services, private networks, cloud metadata, or sensitive mounted files. Avoid ambient authenticated proxy variables unless output is controlled, and review any --output or --metadata path before running it. This needs maintainer fixes before routine installation in a privileged or network-trusted agent environment.
browser-fetch.mjs:169Unrestricted Browser Navigation Enables Server-Side Request Forgery
browser-fetch.mjs:280Chromium Sandbox Is Unconditionally Disabled for Untrusted Web Content
browser-fetch.mjs:167Proxy Credentials May Be Disclosed Through Metadata Output
The skill exposes network access and can inherit proxy-related environment variables, but it declares no explicit tool scope or permission boundary. That creates an authorization and review gap: downstream agents or operators may not realize the skill can make external requests and consume ambient environment configuration, which can lead to unintended data egress or misuse of privileged network paths.
This code fetches arbitrary URLs via Playwright and may persist results through --output or --metadata, but the executable flow contains no confirmation prompt, user-facing notice, or inline warning comment/docstring about these potentially privacy- or data-affecting actions. For a code file, network transmission and file writes are safety-relevant operations that should have some explicit disclosure unless already clearly warned elsewhere.
The documented --output PATH and --metadata PATH options allow writing files locally, but the skill provides no warning about overwriting existing files or modifying the local workspace. In an agent setting, that omission can contribute to accidental clobbering of important files or writing attacker-influenced content to sensitive locations if paths are not carefully controlled.
No suspicious patterns detected.