Skip to content

doc: clarify node binary misuse after compromise #66530

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
RafaelGSS wants to merge 1 commit into
base: main
Choose a base branch
from
+6 −1
Open

doc: clarify node binary misuse after compromise #66530

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -264,7 +264,12 @@ then untrusted input must not lead to arbitrary JavaScript code execution.

* The developers and infrastructure that run it.
* The operating system that Node.js is running under and its configuration,
along with anything under the control of the operating system.
along with anything under the control of the operating system. An attacker
who can already run commands on the host and uses an official, signed
Node.js binary to execute malicious JavaScript does not exploit a
vulnerability in Node.js. A code signature identifies the publisher of the
Node.js binary; it is not a statement about the trustworthiness of the
scripts that binary executes.
* The deployment network environment for the privacy of traffic and routing
decisions, including internal networks through which Node.js traffic passes
and configured HTTP(S) proxy servers. Built-in proxy support is intended to
Expand Down
Loading