T09 · Insecure Skill Coding Practices
- Location
SKILL.md:61- Finding
App-Key May Be Transmitted to an Unvalidated Configurable Endpoint
- Content
View full analysis
``` Example (`base_url` is the full snapshot URL for the user’s region): ```bash curl -sS -X GET "${base_url}" \ -H "App-Key: ${app_key}" ``` ``` The custom endpoint behavior is also explicitly permitted at `SKILL.md:22` and `SKILL.md:46`: ```markdown - **Never** send the App-Key to any host other than the API base in use (official Photon hosts: `photon-prod.leaptic.tech`, `photon-eu.leaptic.tech`, `photon-us.leaptic.tech`, or another `base_url` the user explicitly configured). ``` ```markdown **Recommended:** `~/.config/leaptic/credentials.json` with **both** `base_url` (copy the row for the user’s region) and `app_key`. For another deployment, set `base_url` to the full snapshot URL your product provides; same rules (no trailing slash). ``` ### Technical Analysis Reading the dedicated Leaptic App-Key is necessary for the declared device-snapshot functionality and does not itself exceed the required privilege scope. The Skill limits credential lookup to `LEAPTIC_APP_KEY` and the dedicated `~/.config/leaptic/credentials.json` file, rather than searching unrelated credential locations. However, the destination receiving that credential is selected from `LEAPTIC_BASE_URL` or `base_url` in the credentials file. Although three official hosts are documented, arbitrary custom deployment URLs are also permitted. The instructions ...[truncated 2557 chars]- Remediation
View remediation
