Skip to content

doc: clarify build environment is trusted in threat model#61865

Open
mcollina wants to merge 1 commit intonodejs:mainfrom
mcollina:doc/security-build-env-non-vulnerability
Open

doc: clarify build environment is trusted in threat model#61865
mcollina wants to merge 1 commit intonodejs:mainfrom
mcollina:doc/security-build-env-non-vulnerability

Conversation

@mcollina
Copy link
Member

Summary

  • Add build system attacks to the "Examples of non-vulnerabilities" section in SECURITY.md
  • Clarify that the build environment (environment variables, filesystem, locally installed tools) is a trusted element
  • Command injection via env vars in build scripts (CC, CXX, PKG_CONFIG, RUSTC), path hijacking in build output directories, and file permissions of build artifacts are not considered vulnerabilities

This addresses a recurring class of HackerOne reports that claim vulnerabilities in configure.py or other build scripts by manipulating environment variables or the local filesystem. These scenarios require the attacker to already control the build environment, which is a trusted element per the existing threat model.

@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/tsc

@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to the documentations. label Feb 17, 2026
Add build system attacks (command injection via environment
variables, path hijacking, file permissions) to the list of
non-vulnerabilities. The build environment is a trusted element
and these scenarios require an already-compromised system.
@mcollina mcollina force-pushed the doc/security-build-env-non-vulnerability branch from 54981ca to 85e6c7b Compare February 17, 2026 16:36
@RafaelGSS RafaelGSS added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. commit-queue Add this label to land a pull request using GitHub Actions. labels Feb 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author ready PRs that have at least one approval, no pending requests for changes, and a CI started. commit-queue Add this label to land a pull request using GitHub Actions. doc Issues and PRs related to the documentations.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants