T09 · Insecure Skill Coding Practices
- Location
SKILL.md:220- Finding
Administrative Credentials and Bearer Tokens May Be Transmitted over Unencrypted LAN HTTP
- Content
View full analysis
/admin` (e.g., `http://192.168.1.100/admin`) For native binary install (default port 5102): - **Same machine**: `http://localhost:5102/admin` - **Other devices on LAN**: `http://:5102/admin` ### Onboarding Steps The Setup Wizard is identical to VPS Standalone mode (Steps 1-4 above). The only differences: - **No domain needed** — You access via `localhost` or LAN IP - **No HTTPS** — Local connections use HTTP (this is fine for LAN) - **MCP connects directly** — No SSH tunnel needed; use SSE at `http://localhost:5102/platform/v1/mcp/sse` ``` The same insecure HTTP access model is repeated in `references/access-modes.md`, including the local administrator and MCP URLs. ### Technical Analysis The skill directs users to perform the standalone onboarding workflow over plaintext HTTP when accessing a store from another LAN device. That workflow includes submitting the administrator password, requesting a bearer token, and using that token for subsequent privileged API requests. HTTP provides neither transport confidentiality nor server authentication. Treating HTTP as safe merely because it is used on a LAN is an unsafe assumption. A malicious or compromised LAN participant, wireless access point, router, proxy, or other network device may observe credentials and bearer tokens. An active attacker may also alter responses or redirect the user to a spoofed administration interface. Loopback-only HTTP has a narrower exposure, but the documented addresses explicitly permit access from other LAN devices. ### Attack Path 1. The operator opens `http:///admin` ...[truncated 949 chars]- Remediation
View remediation
