Permissions can be used to control what system resources the\nNode.js process has access to or what actions the process can take\nwith those resources.
\nThe permission model implements a \"seat belt\" approach, which prevents trusted\ncode from unintentionally changing files or using resources that access has\nnot explicitly been granted to. It does not provide security guarantees in the\npresence of malicious code. Malicious code can bypass the permission model and\nexecute arbitrary code without the restrictions imposed by the permission\nmodel.
\nIf you find a potential security vulnerability, please refer to our\nSecurity Policy.
", "modules": [ { "textRaw": "Process-based permissions", "name": "process-based_permissions", "stability": 1, "stabilityText": ".1 - Active development", "miscs": [ { "textRaw": "Permission Model", "name": "Permission Model", "type": "misc", "stability": 1, "stabilityText": ".1 - Active development", "desc": "\nThe Node.js Permission Model is a mechanism for restricting access to specific\nresources during execution.\nThe API exists behind a flag --experimental-permission which when enabled,\nwill restrict access to all available permissions.
The available permissions are documented by the --experimental-permission\nflag.
When starting Node.js with --experimental-permission,\nthe ability to access the file system through the fs module, spawn processes,\nuse node:worker_threads, use native addons, use WASI, and enable the runtime inspector\nwill be restricted.
$ node --experimental-permission index.js\nnode:internal/modules/cjs/loader:171\n const result = internalModuleStat(receiver, filename);\n ^\n\nError: Access to this API has been restricted\n at stat (node:internal/modules/cjs/loader:171:18)\n at Module._findPath (node:internal/modules/cjs/loader:627:16)\n at resolveMainPath (node:internal/modules/run_main:19:25)\n at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:76:24)\n at node:internal/main/run_main_module:23:47 {\n code: 'ERR_ACCESS_DENIED',\n permission: 'FileSystemRead',\n resource: '/home/user/index.js'\n}\nAllowing access to spawning a process and creating worker threads can be done\nusing the --allow-child-process and --allow-worker respectively.
To allow native addons when using permission model, use the --allow-addons\nflag. For WASI, use the --allow-wasi flag.
When enabling the Permission Model through the --experimental-permission\nflag a new property permission is added to the process object.\nThis property contains one function:
API call to check permissions at runtime (permission.has())
process.permission.has('fs.write'); // true\nprocess.permission.has('fs.write', '/home/rafaelgss/protected-folder'); // true\n\nprocess.permission.has('fs.read'); // true\nprocess.permission.has('fs.read', '/home/rafaelgss/protected-folder'); // false\nThe Permission Model, by default, restricts access to the file system through the node:fs module.\nIt does not guarantee that users will not be able to access the file system through other means,\nsuch as through the node:sqlite module.
To allow access to the file system, use the --allow-fs-read and\n--allow-fs-write flags:
$ node --experimental-permission --allow-fs-read=* --allow-fs-write=* index.js\nHello world!\n(node:19836) ExperimentalWarning: Permission is an experimental feature\n(Use `node --trace-warnings ...` to show where the warning was created)\nThe valid arguments for both flags are:
\n* - To allow all FileSystemRead or FileSystemWrite operations,\nrespectively.,) to allow only matching FileSystemRead or\nFileSystemWrite operations, respectively.Example:
\n--allow-fs-read=* - It will allow all FileSystemRead operations.--allow-fs-write=* - It will allow all FileSystemWrite operations.--allow-fs-write=/tmp/ - It will allow FileSystemWrite access to the /tmp/\nfolder.--allow-fs-read=/tmp/ --allow-fs-read=/home/.gitignore - It allows FileSystemRead access\nto the /tmp/ folder and the /home/.gitignore path.Wildcards are supported too:
\n--allow-fs-read=/home/test* will allow read access to everything\nthat matches the wildcard. e.g: /home/test/file1 or /home/test2After passing a wildcard character (*) all subsequent characters will\nbe ignored. For example: /home/*.js will work similar to /home/*.
When the permission model is initialized, it will automatically add a wildcard\n(*) if the specified directory exists. For example, if /home/test/files\nexists, it will be treated as /home/test/files/*. However, if the directory\ndoes not exist, the wildcard will not be added, and access will be limited to\n/home/test/files. If you want to allow access to a folder that does not exist\nyet, make sure to explicitly include the wildcard:\n/my-path/folder-do-not-exist/*.
There are constraints you need to know before using this system:
\n--env-file or --openssl-config are designed\nto read files before environment initialization. As a result, such flags are\nnot subject to the rules of the Permission Model. The same applies for V8\nflags that can be set via runtime through v8.setFlagsFromString.node:fs module bypasses the\nPermission Model.