T09 · Insecure Skill Coding Practices
- Location
SKILL.md:19- Finding
TLS Certificate Verification Disabled for Administrative API Traffic
- Content
View full analysis
" \ "https:///api/auth/login" ``` ```text - Response `ok: true` with a `token` indicates successful login; the auth_token is also saved in the cookie. - Response with `two_step_required: true` means waiting for two-step approval. - All subsequent requests must include `-b /tmp/glkvm_cookies.txt`. **All requests use HTTPS with `-k` (ignore certificate errors).** ``` ### Technical Analysis The `curl -k` option, also known as `--insecure`, disables TLS certificate-chain and hostname verification. Although traffic remains encrypted, the client does not authenticate the GLKVM endpoint. This behavior is applied to the login request and, according to the skill instructions, every subsequent authenticated API request. Consequently, any attacker capable of intercepting or redirecting network traffic can present an arbitrary certificate without causing the connection to fail. The login request transmits the fixed administrative username and the user-supplied administrator password. A successful interception can therefore expose either the administrator password or the resulting authentication token. Manipulated API responses could also mislead the agent about the state or outcome of security-sensitive operations. ### Attack Path 1. The victim invokes the skill and supplies the GLKVM IP address and administrator password. 2. An attacker obtains a network interception or redirection position, such as through a compromised gateway, malicious access point, DNS manipulation, or local network spoofing. 3. The attacker impersonates the GLKVM endpoint using an untrusted TLS certificate. 4. Because every documented request uses `-k`, certificate and hostname verification failures are ignor ...[truncated 1348 chars]- Remediation
View remediation
