Predictable temporary file path
What an insecure-temp-file finding of fallow security means, why it matters and how to fix it.
What it reports
Catalogue security candidate for CWE-377.
Security explains how fallow finds it.
Why it matters
Other users can predict a fixed path in a shared temporary folder. They can create the file first or link it to another file, so the application reads or overwrites the wrong data.
Example
fs.writeFileSync('/tmp/report.json', data);
Fix
Review the candidate trace before acting. Confirm attacker control, missing sanitization, and reachable runtime context, then fix with the category-appropriate safer API or add a reviewed suppression.
Facts
| Fact | Value |
|---|---|
| Issue type | insecure-temp-file |
| Rule id in SARIF output | security/insecure-temp-file |
| Command | fallow security |
| Default severity | off |
| Suppression comment | // fallow-ignore-next-line security-sink |
Fixable with fallow fix | No |
| Opt-in | Yes |
Note. Tainted-sink catalogue category; the security-sink suppression token covers every category.