Skip to content

Commit c6f59d4

Browse files
RafaelGSSrichardlau
authored andcommitted
doc: clarify node binary misuse after compromise
Signed-off-by: RafaelGSS <[email protected]> PR-URL: #66530 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Ulises Gascón <[email protected]>
1 parent fa9fca4 commit c6f59d4

1 file changed

Lines changed: 6 additions & 1 deletion

File tree

‎SECURITY.md‎

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -264,7 +264,12 @@ then untrusted input must not lead to arbitrary JavaScript code execution.
264264

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

0 commit comments

Comments
 (0)