# egg-security Security plugin in egg [![NPM version][npm-image]][npm-url] [![Node.js CI](https://github.com/eggjs/egg-security/actions/workflows/nodejs.yml/badge.svg)](https://github.com/eggjs/egg-security/actions/workflows/nodejs.yml) [![Test coverage][codecov-image]][codecov-url] [![Known Vulnerabilities][snyk-image]][snyk-url] [![npm download][download-image]][download-url] [npm-image]: https://img.shields.io/npm/v/egg-security.svg?style=flat-square [npm-url]: https://npmjs.org/package/egg-security [codecov-image]: https://codecov.io/gh/eggjs/egg-security/branch/master/graph/badge.svg [codecov-url]: https://codecov.io/gh/eggjs/egg-security [snyk-image]: https://snyk.io/test/npm/egg-security/badge.svg?style=flat-square [snyk-url]: https://snyk.io/test/npm/egg-security [download-image]: https://img.shields.io/npm/dm/egg-security.svg?style=flat-square [download-url]: https://npmjs.org/package/egg-security Egg's default security plugin, generally no need to configure. ## Install ```bash $ npm i egg-security ``` ## Usage & configuration - `config.default.js` ```js exports.security = { xframe: { value: 'SAMEORIGIN', }, }; ``` ### Disable security precautions If you want to disable some security precautions, set `enable` porperty to 'false' directly. For example, disable xframe defense: ```js exports.security = { xframe: { enable: false, }, }; ``` ### match & ignore If you want to set security config open for a certain path, you can configure `match` option. For example, just open csp when path contains `/example`, you can configure with the following configuration: ```js exports.security = { csp: { match: '/example', // match: /^\/api/, // support regexp // match: ctx => ctx.path.startsWith('/api'), // support function // match: [ ctx => ctx.path.startsWith('/api'), /^\/foo$/, '/bar'], // support Array policy: { //... }, }, }; ``` If you want to set security config disable for a certain path, you can configure `ignore` option. For example, just disable xframe when path contains `/example` while our pages can be embedded in cooperative businesses , you can configure with the following configuration: ```js exports.security = { xframe: { ignore: '/example', // ignore: /^\/api/, // support regexp // ignore: ctx => ctx.path.startsWith('/api'), // support function // ignore: [ ctx => ctx.path.startsWith('/api'), /^\/foo$/, '/bar'], // support Array // ... }, }; ``` __mention:`match` has higher priority than `ignore`__ ### Dynamic configuration for security plugins depend on context There are times when we want to be more flexible to configure security plugins.For example: 1. To decide whether to enable or disable the xframe security header from the context of the request. 2. To decide csp policies from different request urls. Then we can configure `ctx.securityOptions[name] opts` in the custom middleware or controller,then the current request configuration will overrides the default configuration (new configuration will be merged and override the default project configuration, but only take effect in the current request) ```js async ctx => { // if satisfied some condition // change configuration ctx.securityOptions.xframe = { value: 'ALLOW-FROM: https://domain.com', }; // disable configuration ctx.securityOptions.xssProtection = { enable: false, } } ``` Not all security plugins support dynamic configuration, only following plugins list support - csp - hsts - noopen - nosniff - xframe - xssProtection And in ` helper `: - shtml helper is the same way to configure. ```js ctx.securityOptions.shtml = { whiteList: { }, }; ``` #### Mention - Security is a big thing, please pay attention to the risk of changes in the security configuration (especially dynamic changes) - `ctx.securityOptions` the current request configuration will overrides the default configuration, but it does not make a deep copy,so pay attention to configure `csp.policy`, it will not be merged. - If you configure `ctx.securityOptions`,please write unit tests to ensure the code is correct. ## API ### ctx.isSafeDomain(domain) Whether or not the domain is in the whitelist of the configuration. See `ctx.redirect`. Note: [egg-cors](https://github.com/eggjs/egg-cors) module uses this function internally to determine whether or not send back an `Access-Control-Allow-Origin` response header with the value of safe domain. Otherwise, ignore the request with an error, `No 'Access-Control-Allow-Origin' header is present on the requested resource.` ```js exports.security = { domainWhiteList: ['http://localhost:4200'] }; ``` ## Interface restriction ### CSRF __usage__ * `ctx.csrf` getter for CSRF token Generally used when send POST form request. When page rendering, put `ctx.csrf` into form hidden field or query string.(`_csrf` is the key). When submitting the form, please submit with the `_csrf` token parameter. #### Using CSRF when upload by formData browser: ```html
title: file:
``` #### Using CSRF when request by AJAX CSRF token will also set to cookie by default, and you can send token through header: In jQuery: ```js var csrftoken = Cookies.get('csrftoken'); function csrfSafeMethod(method) { // these HTTP methods do not require CSRF protection return (/^(GET|HEAD|OPTIONS|TRACE)$/.test(method)); } $.ajaxSetup({ beforeSend: function(xhr, settings) { if (!csrfSafeMethod(settings.type) && !this.crossDomain) { xhr.setRequestHeader('x-csrf-token', csrftoken); } }, }); ``` #### Options there are some options that you can customize: ```js exports.security = { csrf: { type: 'ctoken', // can be ctoken, referer, all or any, default to ctoken useSession: false, // if useSession set to true, the secret will keep in session instead of cookie ignoreJSON: false, // skip check JSON requests if ignoreJSON set to true cookieName: 'csrfToken', // csrf token's cookie name sessionName: 'csrfToken', // csrf token's session name headerName: 'x-csrf-token', // request csrf token's name in header bodyName: '_csrf', // request csrf token's name in body queryName: '_csrf', // request csrf token's name in query refererWhiteList: [], // referer white list supportedRequests: [ // supported URL path and method, the package will match URL path regex patterns one by one until path matched. We recommend you set {path: /^\//, methods:['POST','PATCH','DELETE','PUT','CONNECT']} as the last rule in the list, which is also the default config. {path: /^\//, methods:['POST','PATCH','DELETE','PUT','CONNECT']} ], cookieOptions: {}, // csrf token's cookie options }, } ``` `methods` in `supportedRequests` can be empty, which means if you set `supportedRequests: [{path: /.*/, methods:[]}]`, the whole csrf protection will be disabled. #### Rotate CSRF secret Must call `ctx.rotateCsrfSecret()` when user login to ensure each user has independent secret. ### safe redirect * `ctx.redirect(url)` If url is not in the configuration of the white list, the redirect will be prohibited * `ctx.unsafeRedirect(url)` Not Recommended; Security plugin override `ctx.redirect` method,all redirects will be judged by the domain name. If you need to use `ctx.redirect`, you need to do the following configuration in the application configuration file: ```js exports.security = { domainWhiteList:['.domain.com'], // security whitelist, starts with '.' }; ``` If user do not configure `domainWhiteList` or `domainWhiteList` is empty, it will pass all redirects, equal to `ctx.unsafeRedirect(url)`. `domainWhiteList` and `url` are case insensitive. ### jsonp Based on [jsonp-body](https://github.com/node-modules/jsonp-body). Defense: * The longest callback function name limit of 50 characters. * Callback function only allows "[","]","a-zA-Z0123456789_", "$" "." to prevent `xss` or `utf-7` attack. Config: * callback function default name `_callback`. * limit - function name limit, default by 50. ## helper ### .escape() String xss filter, the most secure filtering mechanism. ```js const str = '><'; console.log(ctx.helper.escape(str)); // => ><script>alert("abc") </script>< ``` In nunjucks template, escape by default. ### .surl() url filter. Used for url in html tags (like ``),please do not call under other places. `helper.surl($value)`。 ** Mention: Particular attention, if you need to resolve URL use `surl`,`surl` need warpped in quotes, Otherwise will lead to XSS vulnerability.** Example: do not use surl ```html ``` output: ```html ``` Use surl ```html ``` output: ```html ``` #### protocolWhitelist If url's protocol is not in the protocol whitelist, it will return empty string. Protocol whitelist is `http`, `https`, `file`, `data`. So if you want `surl` support custom protocol, please extend the security `protocolWhitelist` config : ```js exports.security = { protocolWhitelist: ['test'] }; ``` ### .sjs() Used to output variables in javascript(include onload/event),it will do `JAVASCRIPT ENCODE` for the variable string.It will escape all characters to `\x` which are not in the whitelist to avoid XSS attack. ```js const foo = '"hello"'; // not use sjs console.log(`var foo = "${foo}";`); // => var foo = ""hello""; // use sjs console.log(`var foo = "${ctx.helper.sjs(foo)}";`); // => var foo = "\\x22hello\\x22"; ``` ### .shtml() If you want to output richtexts in views, you need to use `shtml` helper. It will do XSS filter, then output html tags to avoid illegal scripts. ** shtml is a very complex process, it will effect server performance, so if you do not need to output HTML, please do not use shtml.** Examples: ```js // js const value = `google`; // in your view ${helper.shtml($value)} // => google<script>evilcode…</script> ``` shtml based on [xss](https://github.com/leizongmin/js-xss/), and add filter by domain feature. - [default rule](https://github.com/leizongmin/js-xss/blob/master/lib/default.js) - custom rule http://jsxss.com/zh/options.html For example, only support `a` tag, and filter all attributes except for `title`: ```javascript whiteList: {a: ['title']} ``` options: > `config.helper.shtml.domainWhiteList` has been deprecated, please use `config.security.domainWhiteList` instead. Mention that `shtml` uses a strict white list mechanism, in addition to filtering out the XSS risk of the string,`tags` and `attrs` which are not in the [default rule](https://github.com/leizongmin/js-xss/blob/master/lib/default.js) will be filtered. For example `html` tag is not in the whitelist. ```js const html = ''; // html ${helper.shtml($html)} // output none ``` Commonly used `data-xx` property is not in the whitelist, so it will be filtered. So please check the applicable scenarios for `shtml`, it usually used for richtext submmited by user. A usage error will limit functions, also affect the performance of the server. Such scenes are generally forums, comments, etc. Even if the forum does not support the HTML content input, do not use this helper, you can directly use `escape` instead. ### .spath() If you want to use users input for a file path, please use spath for security check. If path is illegal, it will return null. Illegal path: - relative path starts with `..` - absolute path starts with `/` - above path try to use `url encode` to bypass the check ```js const foo = '/usr/local/bin'; console.log(ctx.helper.spath(foo2)); // => null ``` ### .sjson() json encode. If you want to output json in javascript without encoding, it will be a risk for XSS. sjson supports json encode,it will iterate all keys in json, then escape all characters in the value to `\x` to avoid XSS attack, and keep the json structure unchanged. If you want to output json string in your views, please use `${ctx.helper.sjson(var)}`to escape. **it has a very complex process and will lost performance, so avoid the use as far as possible** example: ```js ``` ### .cliFilter() It will cause remote command execution vulnerability, when user submit the implementation of the command by browser.because the server does not filter for the implementation of the function, resulting in the execution of the command can usually lead to the invasion of the server. If you want to get user submit for command's parameter, please use `cliFilter`。 before fix: ```js cp.exec("bash /home/admin/ali-knowledge-graph-backend/initrun.sh " + port); ``` after fix: ```js cp.exec("bash /home/admin/ali-knowledge-graph-backend/initrun.sh " + ctx.helper.cliFilter(port)); ``` ### .escapeShellArg() Escape command line arguments. Add single quotes around a string and quotes/escapes any existing single quotes allowing you to pass a string directly to a shell function and having it be treated as a single safe argument. ```js const ip = '127.0.0.1 && cat /etc/passwd' const cmd = 'ping -c 1 ' + this.helper.escapeShellArg(ip); console.log(cmd); //ping -c 1 '127.0.0.1 && cat /etc/passwd' ``` ### .escapeShellCmd() Command line escape to remove the following characters from the entered command line: ```#&;`|*?~<>^()[]{}$;'", 0x0A and 0xFF``` ```js const ip = '127.0.0.1 && cat /etc/passwd' const cmd = 'ping -c 1 ' + this.helper.escapeShellCmd(ip); console.log(cmd); //ping -c 1 127.0.0.1 cat /etc/passwd ``` ## Security Headers Refer to [lusca](https://github.com/krakenjs/lusca), appriciate for their works. ### hsts Strict-Transport-Security Disabled by default. If your website based on https, we recommend you should enable it. - maxAge one year by default `365 * 24 * 3600` - includeSubdomains false by default ### csp Default disabled. If you need to enable, please contact your security engineers and determine the opening strategy - policy policies used by csp ### X-Download-Options:noopen Default enabled, disable IE download dialog automatically open download file and will cause XSS ### X-Content-Type-Options:nosniff Disable IE8's auto MIME sniffing. E.g: take `text/plain` as `text/html` by mistake and render it, especially when there's something untrusted in the local service. ### X-Frame-Options Defaulting to "SAMEORIGIN", only allow iframe embed by same origin. - value Defaulting to `SAMEORIGIN` ### X-XSS-Protection - disable Defaulting to `false`,same as `1; mode=block`. ### SSRF Protection In a [Server-Side Request Forgery (SSRF)](https://www.owasp.org/index.php/Server_Side_Request_Forgery) attack, the attacker can abuse functionality on the server to read or update internal resources. `egg-security` provide `ctx.safeCurl`, `app.safeCurl` and `agent.safeCurl` to provide http request(like `ctx.curl`, `app.curl` and `agent.curl`) with SSRF protection. #### Configuration * ipBlackList(Array) - specific which ip are illegal when request with `safeCurl`. * ipExceptionList(Array) - specific which ip are legal within ipBlackList. * checkAddress(Function) - determine the ip by the function's return value, `false` means illegal ip. ```js // config/config.default.js exports.security = { ssrf: { // support both cidr subnet or specific ip ipBlackList: [ '10.0.0.0/8', '127.0.0.1', '0.0.0.0/32', ], // support both cidr subnet or specific ip ipExceptionList: [ '10.1.1.1', '10.10.0.1/24', ], // checkAddress has higher priority than ipBlackList checkAddress(ip) { return ip !== '127.0.0.1'; } }, }; ``` ## Other * Forbid `trace` `track` http methods. ## Contributors |[
dead-horse](https://github.com/dead-horse)
|[
fengmk2](https://github.com/fengmk2)
|[
jtyjty99999](https://github.com/jtyjty99999)
|[
popomore](https://github.com/popomore)
|[
shaoshuai0102](https://github.com/shaoshuai0102)
|[
whxaxes](https://github.com/whxaxes)
| | :---: | :---: | :---: | :---: | :---: | :---: | |[
atian25](https://github.com/atian25)
|[
ai](https://github.com/ai)
|[
Anemone95](https://github.com/Anemone95)
|[
guoshencheng](https://github.com/guoshencheng)
|[
p0sec](https://github.com/p0sec)
|[
pusongyang](https://github.com/pusongyang)
| [
ShadyZOZ](https://github.com/ShadyZOZ)
|[
viko16](https://github.com/viko16)
|[
brizer](https://github.com/brizer)
|[
EliYao](https://github.com/EliYao)
This project follows the git-contributor [spec](https://github.com/xudafeng/git-contributor), auto updated at `Tue Apr 05 2022 11:54:38 GMT+0800`. ## License [MIT](https://github.com/eggjs/egg-security/blob/master/LICENSE)