From d662292906ccd8647eac89c06447f18981996049 Mon Sep 17 00:00:00 2001 From: Liran Tal Date: Wed, 21 Aug 2024 20:08:03 +0300 Subject: [PATCH] Add resource for node.js (#6731) Update `child_process` module entry with insight about security implications of using this in Node.js apps --- .../nodejs/content/child-process@lzPrWD3pxQmpbqgYPL-zW.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/data/roadmaps/nodejs/content/child-process@lzPrWD3pxQmpbqgYPL-zW.md b/src/data/roadmaps/nodejs/content/child-process@lzPrWD3pxQmpbqgYPL-zW.md index c8b5b69b1..a00b29b7f 100644 --- a/src/data/roadmaps/nodejs/content/child-process@lzPrWD3pxQmpbqgYPL-zW.md +++ b/src/data/roadmaps/nodejs/content/child-process@lzPrWD3pxQmpbqgYPL-zW.md @@ -10,3 +10,4 @@ The three main methods inside this module are : Visit the following resources to learn more: - [@official@Child Process Docs](https://nodejs.org/api/child_process.html#child-process) +- [@article@Securing Node.js Against Command Injection](https://www.nodejs-security.com/blog/securing-your-nodejs-apps-by-analyzing-real-world-command-injection-examples)