T09 · Insecure Skill Coding Practices
- Location
scripts/write_memory.sh:12- Finding
Configurable API Base Allows Plaintext Transmission of Credentials and Memory Data
- Content
View full analysis
- Remediation
View remediation
&2 exit 1 ;; esac ``` 2. Restrict curl to HTTPS and require a modern TLS version: ```bash curl --proto '=https' --tlsv1.2 --fail-with-body \ -X POST "$API_BASE/memory" \ -H "Authorization: Bearer $API_KEY" \ -H "Content-Type: application/json" \ --data "$PAYLOAD" ``` 3. If plaintext HTTP is required for local development, require an explicit opt-in such as `AGENTMM_ALLOW_INSECURE_HTTP=1`, display a prominent warning, and preferably restrict it to loopback destinations. 4. Apply the same centralized URL validation to every API script so that individual commands cannot diverge in security behavior. 5. Update the documentation to state the enforced transport requirements and avoid claiming HTTPS protection when a custom plaintext endpoint is permitted. ]]>
