T09 · Insecure Skill Coding Practices
- Location
references/config.md:44- Finding
Unsafe API-Key Interpolation and Plaintext Credential Storage
- Content
View full analysis
"$HOME/.finder/config.json" <", "last_project_id": null } EOF ``` The documented Windows PowerShell implementation similarly places the value in executable PowerShell source: ```powershell $finderDir = Join-Path $HOME ".finder" $configPath = Join-Path $finderDir "config.json" New-Item -ItemType Directory -Force -Path $finderDir | Out-Null $config = @{ base_url = "https://finder.optell.com" api_key = "" last_project_id = $null } | ConvertTo-Json Set-Content -Path $configPath -Value $config -Encoding UTF8 ``` ### Technical Analysis The Skill expects an agent to replace the API-key placeholder with user-controlled content and execute the resulting Bash or PowerShell command. The value is neither validated against an expected API-key format nor passed through a non-executable data channel. In the Bash example, the here-document delimiter is unquoted. Consequently, shell expansions such as command substitution are processed inside the here-document. If an untrusted value containing shell syntax such as `$(command)` is inserted into the generated command, that command may be evaluated while the configuration file is created. A value containing a newline and the `EOF` delimiter could also terminate the i ...[truncated 2660 chars]- Remediation
View remediation
