T09 · Insecure Skill Coding Practices
- Location
references/cli_reference.md:47- Finding
Sensitive credentials exposed through command-line arguments
- Content
View full analysis
` | string | No | `LGP_API_KEY` env var | API key for authentication (overrides environment variable) | | `--admin-key ` | string | No | `LGP_ADMIN_KEY` env var | Admin key to bypass rate limits (overrides environment variable) | ``` ```bash python lgp.py auth test --api-key lgp_abc123def456 ``` The EpsimoAI command documentation similarly instructs users to pass passwords and tokens directly as arguments: ```bash lgp epsimo activate --email --password lgp epsimo activate --cognito-token python lgp.py epsimo activate --email user@example.com --password secret python lgp.py epsimo activate --cognito-token eyJ... lgp epsimo info --token python lgp.py epsimo info --token eyJ... lgp epsimo credits --token python lgp.py epsimo credits --token eyJ... lgp epsimo purchase --token --amount python lgp.py epsimo purchase --token eyJ... --amount 10000 lgp epsimo threads --token python lgp.py epsimo threads --token eyJ... ``` ### Technical Analysis Command-line arguments are not an appropriate channel for long-lived API keys, passwords, administrative secrets, Cognito identity tokens, or bearer tokens. Depending on the host environment, process arguments can be exposed through: - Shell history files such as `.bash_history` or `.zsh_history` - Process inspection utilities and operating-system process metadata - Terminal session recording and audit systems - CI/CD job logs and command echoing - Endpoint detection and response telemetry - Wrapper scripts that log their full invocation - Crash diagnostics and support bundles Although enviro ...[truncated 2022 chars]- Remediation
View remediation
