T09 · Insecure Skill Coding Practices
- Location
textureartgenerator.js:10- Finding
API Token Exposed Through Command-Line Arguments
- Content
View full analysis
"your prompt" --token YOUR_TOKEN ``` ### Technical Analysis The skill only accepts the Neta API token through the `--token` command-line option. Command-line arguments are not an appropriate secret-transport mechanism because they may be exposed through: - Shell history files. - Process inspection utilities while the process is running. - Process accounting or endpoint-monitoring systems. - CI/CD logs and command tracing. - Wrapper scripts or terminal-session recordings. The token is subsequently sent as the `x-token` header to the documented API. The direct API transmission uses HTTPS and is consistent with the skill's declared purpose; the vulnerability is the local handling of the token before that request. ### Attack Path 1. A victim follows the documented usage and runs the skill with `--token YOUR_TOKEN`. 2. The shell records the command in its history, or the operating system exposes the active process arguments. 3. A local user, monitoring agent, log collector, or another process with sufficient local visibility reads the command arguments. 4. The observer extracts the Neta API token. 5. The observer reuses the token against the Neta API until it is revoked or expires. ### Impact Assessment An attacker who obtains the token may impersonate the victim to the Neta API and consume the victim's image-generation quota or access capabilities associated with that token. The exposed credential does not, by itself, grant operating-syste ...[truncated 98 chars]- Remediation
View remediation
