T09 · Insecure Skill Coding Practices
- Location
scripts/bitpanda.sh:38- Finding
Bitpanda API Key Exposed Through Process Command-Line Arguments
- Content
View full analysis
/dev/null) ``` ### Technical Analysis The script expands the Bitpanda API key directly into the argument list passed to `curl`. Although transmitting the key to the official Bitpanda HTTPS endpoint is necessary for authenticated portfolio operations, including it in a command-line argument is not required. While each request is active, the expanded `X-Api-Key` header may be observable through local process-inspection mechanisms such as `ps`, `/proc//cmdline`, process-monitoring software, debugging tools, or audit systems. Exploitability depends on the operating system's process-visibility configuration and the attacker's local privileges. On systems where users can inspect another process's arguments—or where another compromised process runs under the same account—the credential can be recovered. HTTPS protects the key in transit but does not protect it from local process-argument disclosure before transmission. ### Attack Path 1. The user invokes a command such as `bitpanda portfolio`, `bitpanda wallets`, `bitpanda transactions`, or `bitpanda asset BTC`. 2. The script loads the API key from `BITPANDA_API_KEY` or `~/.openclaw/credentials/bitpanda/config.json`. 3. The script interpolates the key into `curl`'s `-H` command-line argument. 4. A local attacker or comprom ...[truncated 1198 chars]- Remediation
View remediation
