T09 · Insecure Skill Coding Practices
- Location
SKILL.md:93- Finding
Owner Tokens Exposed Through URL Query Parameters
- Content
View full analysis
&limit=50" ``` Returns the array of files with `file_id` and `filename`. To get a download URL for one of them: ```sh curl -sS "https://api.sendbl.com/v1/fileDownloadLink?token=&file_id=" ``` ### 5. Delete a link Requires the `owner_token`. Removes the link **and all uploaded files**. ```sh curl -sS -X DELETE "https://api.sendbl.com/v1/uploadLink?token=" ``` ``` ### Technical Analysis The documented API commands place the capability-bearing `owner_token` directly in URL query parameters. Query strings are commonly retained in: - Shell command history - Process command-line information - HTTP proxy and gateway access logs - Server request logs - Monitoring and telemetry platforms - Terminal transcripts and diagnostic output HTTPS protects the URL while it is in transit, but it does not prevent disclosure through these local or server-side recording mechanisms. According to the documented behavior, possession of an owner token is sufficient to list uploaded files, generate file download links, and delete the associated link and all its files. The token therefore functions as a sensitive bearer credential. ### Attack Path 1. A user or agent executes one of the documented commands with a real owner token. 2. The full command or requested URL is retained in shell history, process telemetry, proxy logs, server access logs, or monitoring data. 3. An attacker with access to one of those records extracts the `owner_token`. 4. The attacker submits the token to the unauthenticated owner-token endpoints. 5. The attacker lists file metadata, obtains download links for uploaded files, or ...[truncated 576 chars]- Remediation
View remediation
