T09 · Insecure Skill Coding Practices
Warning
- Location
scripts/script.sh:6- Finding
Content Logs Are Created Without Explicitly Restrictive Permissions
- Content
View full analysis
> "$DATA_DIR/history.log"; } ``` ### Technical Analysis The script creates its data directory and log files without setting a restrictive `umask` or explicitly assigning secure permissions. Consequently, permissions depend entirely on the environment from which the script is invoked. Under a commonly used `022` umask, the directory may be created with mode `0755` and new log files with mode `0644`. This can make stored content readable by other local users. The issue affects both command-specific logs and `history.log`. Content supplied to commands is duplicated into the history file by `_log`, increasing the number of files containing potentially sensitive material. The vulnerability does not provide remote access or privilege escalation. Exploitation requires another local account or process with filesystem access to the affected user's home directory. ### Attack Path 1. A user invokes a command such as `deadline draft`, `deadline schedule`, or `deadline translate` with confidential content. 2. The script creates `~/.local/share/deadline` and associated log files using permissions derived from the current `umask`. 3. With a permissive `umask`, the resulting files are readable by other local users. 4. Another local account enumerates or directly reads files such as `draft.log`, `schedule.log`, or `history.log`. 5. The attacker obtains the stored content and its timestamps. ### Impact Assessment A successful attacker can disclose content stored by the affected operating-system account, including drafts, schedules, translations, and other user-provided text. The scope is limited to locally stored De ...[truncated 163 chars]- Remediation
View remediation