T09 · Insecure Skill Coding Practices
- Location
SKILL.md:179- Finding
TLS Certificate Verification Is Globally Disabled for Flight Searches
- Content
View full analysis
⚠️ FlyAI commands must use the `NODE_TLS_REJECT_UNAUTHORIZED=0` prefix. ``` ```markdown | SSL certificate verification failure | Ensure the command uses the `NODE_TLS_REJECT_UNAUTHORIZED=0` prefix | ``` ### Technical Analysis Setting `NODE_TLS_REJECT_UNAUTHORIZED=0` disables TLS certificate verification for the Node.js process running the FlyAI command. The client will therefore accept expired, self-signed, untrusted, or hostname-mismatched certificates. This removes the server-authentication guarantee normally provided by HTTPS. Encryption alone does not protect the request if the client cannot verify which server it is communicating with. A network-positioned attacker can terminate the TLS connection using an arbitrary certificate and proxy or modify the traffic. The weakness is particularly significant because FlyAI responses contain flight data and `jumpUrl` booking links that are later presented to users and embedded in generated HTML reports. ### Attack Path 1. The Skill starts a FlyAI search with `NODE_TLS_REJECT_UNAUTHORIZED=0`. 2. An attacker gains a network interception position, such as through a hostile Wi-Fi access point, compromised proxy, DNS manipulation, or local network gateway. 3. The attacker presents an untrusted TLS certificate while impersonating the FlyAI endpoint ...[truncated 1073 chars]- Remediation
View remediation
