fix(security): Predictable global cache directory in /tmp enables symlink/hijack risks#1314
Merged
styfle merged 3 commits intoMay 12, 2026
Conversation
styfle
reviewed
Apr 3, 2026
Timer
approved these changes
May 12, 2026
08aeeef to
e905a9f
Compare
The cache directory is a fixed, shared path (`/tmp/ncc-cache`). On multi-user systems this can be pre-created or manipulated by another user (symlink/hardlink attacks), potentially causing cache poisoning, unintended file writes, or data leakage between builds/users depending on how cache files are later written. Affected files: ncc-cache-dir.js Signed-off-by: tuanaiseo <221258316+tuanaiseo@users.noreply.github.com>
e905a9f to
69acee2
Compare
…che-directory-in-tm
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The cache directory is a fixed, shared path (
/tmp/ncc-cache). On multi-user systems this can be pre-created or manipulated by another user (symlink/hardlink attacks), potentially causing cache poisoning, unintended file writes, or data leakage between builds/users depending on how cache files are later written.Severity:
mediumFile:
src/utils/ncc-cache-dir.jsSolution
Use a per-user/per-project cache directory with secure creation semantics (e.g.,
fs.mkdtempunder user-owned base dir), enforce permissions (0700), and verify path is not a symlink before writing.Changes
src/utils/ncc-cache-dir.js(modified)Testing