Skip to content

Commit b1009b5

Browse files
RafaelGSSmarco-ippolito
authored andcommitted
doc: explicit mention arbitrary code execution as a vuln
This request came from Github Open Source Secure and it's always welcome to clarify the policy PR-URL: #57426 Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
1 parent f5b293a commit b1009b5

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

SECURITY.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -141,6 +141,9 @@ a security vulnerability. Examples of unwanted actions are polluting globals,
141141
causing an unrecoverable crash, or any other unexpected side effects that can
142142
lead to a loss of confidentiality, integrity, or availability.
143143

144+
For example, if trusted input (like secure application code) is correct,
145+
then untrusted input must not lead to arbitrary JavaScript code execution.
146+
144147
**Node.js trusts everything else**. Examples include:
145148

146149
* The developers and infrastructure that runs it.

0 commit comments

Comments
 (0)