T09 · Insecure Skill Coding Practices
- Location
scripts/setup.py:63- Finding
API Token Exposed Through Command-Line Arguments
- Content
View full analysis
[--webhook ]") print(" Get your token at https://wldpass.com/center\n") sys.exit(1) ``` The documented setup commands similarly instruct users to supply the bearer token directly: ```bash python3 {baseDir}/scripts/setup.py wldpass_YOUR_TOKEN python3 {baseDir}/scripts/setup.py wldpass_YOUR_TOKEN --webhook https://your-server.com/webhook ``` ### Technical Analysis The setup utility accepts `WLDPASS_API_TOKEN` as a positional command-line argument. Command-line secrets can be retained in interactive shell history and may be visible temporarily through process-inspection facilities, depending on the operating system and its process-access controls. The token authorizes access to WLdPass account and commerce APIs. Although transmitting it to the declared first-party HTTPS service is necessary for token verification, placing it in `argv` is not necessary. A secret environment variable, masked prompt, or credential store would avoid this exposure. This behavior violates secure secret-handling practices and exceeds the minimum exposure needed for the Skill's declared setup functionality. ### Attack Path 1. A user follows the documented setup ...[truncated 1094 chars]- Remediation
View remediation
