T09 · Insecure Skill Coding Practices
- Location
scripts/hitem3d.sh:151- Finding
Bearer Token Exposed Through Standard Output
- Content
View full analysis
&2 _die "Auth failed" fi } ``` ### Technical Analysis The public `auth` command returns the Hitem3D bearer token directly through standard output. This conflicts with the security rule in `SKILL.md` that bearer tokens must never be echoed. Standard output may be retained in Agent transcripts, CI logs, terminal capture systems, shell automation, or observability platforms. The token is therefore exposed outside the minimum internal scope required to authenticate subsequent API calls. Although internal command substitution also relies on this output, the same function is directly accessible through the command dispatcher as `scripts/hitem3d.sh auth`, making accidental disclosure straightforward. ### Attack Path 1. A user, Agent, diagnostic process, or CI job invokes `scripts/hitem3d.sh auth`. 2. The script authenticates with the configured AK/SK credentials. 3. The returned bearer token is printed to standard output. 4. A transcript, build log, terminal recorder, or other output collector stores the token. 5. A party with access to that output retrieves the token. 6. ...[truncated 639 chars]- Remediation
View remediation
