T09 · Insecure Skill Coding Practices
- Location
src/server-client.js:8- Finding
Default Plaintext HTTP Transport Exposes User Data and Bearer Credentials
- Content
View full analysis
{ const lib = url.protocol === 'https:' ? https : http; const req = lib.request({ hostname: url.hostname, port: url.port || (url.protocol === 'https:' ? 443 : 80), path: url.pathname + url.search, method: 'POST', headers: { 'Content-Type': 'application/json', 'Content-Length': Buffer.byteLength(payload), ...(secret ? { 'Authorization': `Bearer ${secret}` } : {}), }, timeout: 10000, }, (res) => { ``` The complete incoming message is forwarded at `src/server-client.js:56-58`: ```js async function plan(message, skillConfig) { return postJson('/plan', { ...message, skillConfig: skillConfig || null }); } ``` ### Technical Analysis The default backend is a hard-coded public IP using plaintext HTTP. The client explicitly supports both HTTP and HTTPS but does not enforce HTTPS or reject insecure URLs. The request body contains the complete message object and may therefore include the user's identifier, travel request, origin location, context, action payload, and skill configuration. When `PLANIT_SECRET` is set, the same plain ...[truncated 1659 chars]- Remediation
View remediation
