Skip to content

Commit 379aba1

Browse files
authored
doc: trust FFI in the threat model
Signed-off-by: Paolo Insogna <[email protected]> PR-URL: #62852 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Chengzhong Wu <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: Rafael Gonzaga <[email protected]>
1 parent 58a237b commit 379aba1

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

SECURITY.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -213,7 +213,7 @@ then untrusted input must not lead to arbitrary JavaScript code execution.
213213
along with anything under the control of the operating system.
214214
* The code it is asked to run, including JavaScript, WASM and native code, even
215215
if said code is dynamically loaded, e.g., all dependencies installed from the
216-
npm registry.
216+
npm registry or libraries loaded via `node:ffi`.
217217
The code run inherits all the privileges of the execution user.
218218
* Inputs provided to it by the code it is asked to run, as it is the
219219
responsibility of the application to perform the required input validations,

0 commit comments

Comments
 (0)