T09 · Insecure Skill Coding Practices
- Location
SKILL.md:8- Finding
Plaintext Bark Credential Stored Without Required Access Controls
- Content
View full analysis
- Remediation
View remediation
"$HOME/.bark/key" chmod 600 "$HOME/.bark/key" ``` 3. Before reading the credential, verify that: - The file is a regular file and not a symbolic link. - The current user owns the file. - Group and other users have no permissions. - The parent directory is owned by the current user and is not writable by untrusted users. 4. Refuse to use the credential until unsafe ownership or permissions are corrected. 5. Prefer an operating-system credential manager or secret store where available. If file storage remains necessary, document its security requirements explicitly. 6. Avoid examples containing literal keys. Prevent shell tracing and verbose request logging from recording credential-bearing URLs. 7. Warn users that the Bark key is a sensitive bearer credential and that notification contents and metadata are transmitted to the configured Bark server. 8. Support credential rotation and instruct users to replace the Bark key if file, process-list, shell-history, proxy-log, or monitoring-system exposure is suspected. ]]>
