T09 · Insecure Skill Coding Practices
- Location
SKILL.md:498- Finding
Unauthenticated Development Dashboard Exposed on All Network Interfaces
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 498-532
Vulnerability Type: Unauthenticated network exposure of sensitive project data
Risk Level: HighVulnerable Code
bash # CORRECT — detached, survives exec timeout cd "$SKILL_DIR/web" setsid pnpm dev --port 3000 --host 0.0.0.0 </dev/null > /tmp/tick-board.log 2>&1 & echo $! > /tmp/tick-board.pidThe accompanying instructions explicitly state:
text The dev server binds to `0.0.0.0`, making it available on all network interfaces.They also acknowledge that the development server has no built-in authentication or encryption and that task data may contain sensitive project information.
Technical Analysis
Binding the dashboard to
0.0.0.0exposes it through every available network interface rather than limiting access to the local machine. The server is also launched as a detached background process, increasing the likelihood that it will continue running after the user finishes inspecting the board.The dashboard is described as read-only, but it displays project lists, task details, task history, priorities, tags, and coordination data. Such records can contain confidential project plans, internal endpoints, implementation decisions, employee or agent identities, and security-related notes.
The documentation includes warnings against public exposure, but these warnings do not correct the insecure default command. Local dashboard inspection only requires binding to
127.0.0.1; therefore, exposing all interfaces exceeds the minimum network privileges necessary for the declared functionality.The referenced
scripts/tick-board.shimplementation is not included in the audited package, so it was not possible to verify whether that script adds authentication, restricts network binding, validates ports, or reliably terminates stale processes.Attack Path
- A user follows the Skill instructions ...[truncated 1391 chars]
- Remediation
View remediation
Remediation Suggestions
-
Bind to the loopback interface by default:
bash setsid pnpm dev --port 3000 --host 127.0.0.1 </dev/null > /tmp/tick-board.log 2>&1 & -
Require explicit user confirmation and a separate opt-in flag before binding to a LAN, VPN, or public-facing interface.
-
For remote access, place the dashboard behind an authenticated reverse proxy with TLS rather than exposing the development server directly.
-
Add startup checks that detect public-facing interfaces, permissive firewall rules, occupied ports, and stale PID files.
-
Implement automatic shutdown after an inactivity timeout or at the end of the inspection session.
-
Ensure the stop operation validates that the PID belongs to the expected dashboard process before terminating it.
-
Avoid placing credentials or sensitive data in process arguments, URLs, or logs.
-
Include and audit
scripts/tick-board.shin the distributed package so its binding, authentication, process-management, and cleanup behavior can be verified. -
Clearly separate safe local operation from remote deployment guidance; remote deployment should require authentication, encrypted transport, and restrictive network access controls.
-
