ecosystem
stringclasses 11
values | vuln_id
stringlengths 10
19
| summary
stringlengths 4
220
⌀ | details
stringlengths 34
13.5k
| aliases
stringlengths 17
87
⌀ | modified_date
stringdate 2019-03-26 14:13:00
2022-05-10 08:46:52
| published_date
stringdate 2012-06-17 03:41:00
2022-05-10 08:46:50
| severity
stringclasses 5
values | score
float64 0
10
⌀ | cwe_id
stringclasses 581
values | refs
stringlengths 82
11.6k
| introduced
stringclasses 843
values | code_refs
stringlengths 46
940
| commits
stringlengths 46
940
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
npm | GHSA-jgpq-g82g-6c39 | confinit vulnerable to prototype pollution | confinit through 0.3.0 is vulnerable to Prototype Pollution.The 'setDeepProperty' function could be tricked into adding or modifying properties of 'Object.prototype' using a '__proto__' payload. | {'CVE-2020-7638'} | 2021-07-28T23:16:44Z | 2020-04-07T15:52:05Z | MODERATE | null | {'CWE-915'} | {'https://snyk.io/vuln/SNYK-JS-CONFINIT-564433', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7638', 'https://github.com/davideicardi/confinit/commit/a34e06ca5c1c8b047ef112ef188b2fe30d2a1eab'} | null | {'https://github.com/davideicardi/confinit/commit/a34e06ca5c1c8b047ef112ef188b2fe30d2a1eab'} | {'https://github.com/davideicardi/confinit/commit/a34e06ca5c1c8b047ef112ef188b2fe30d2a1eab'} |
npm | GHSA-gvcj-pfq2-wxj7 | High severity vulnerability that affects electron | Untrusted search path vulnerability in Atom Electron before 0.33.5 allows local users to gain privileges via a Trojan horse Node.js module in a parent directory of a directory named on a require line. | {'CVE-2016-1202'} | 2021-09-13T12:46:47Z | 2017-10-24T18:33:35Z | HIGH | null | {'CWE-426'} | {'https://github.com/electron/electron/commit/9a2e2b365d061ec10cd861391fd5b1344af7194d', 'https://github.com/electron/electron', 'https://github.com/advisories/GHSA-gvcj-pfq2-wxj7', 'https://github.com/electron/electron/pull/2976', 'http://jvndb.jvn.jp/jvndb/JVNDB-2016-000054', 'http://jvn.jp/en/jp/JVN00324715/index.html', 'https://nvd.nist.gov/vuln/detail/CVE-2016-1202'} | null | {'https://github.com/electron/electron/commit/9a2e2b365d061ec10cd861391fd5b1344af7194d'} | {'https://github.com/electron/electron/commit/9a2e2b365d061ec10cd861391fd5b1344af7194d'} |
npm | GHSA-7w54-gp8x-f33m | Potential exposure of tokens to an Unauthorized Actor | ### Impact
When using this library as a way to programmatically communicate with Replit in a standalone fashion, if there are multiple failed attempts to contact Replit through a WebSocket, the library will attempt to communicate using a fallback poll-based proxy. The URL of the proxy has changed, so any communication done to the previous URL could potentially reach a server that is outside of Replit's control and the token used to connect to the Repl could be obtained by an attacker, leading to full compromise of that Repl (not of the account).
### Patches
This was patched in 7.3.1, by updating the address of the fallback WebSocket polling proxy to the new one.
### Workarounds
Specify the new address for the polling host (`gp-v2.replit.com`) in the `ConnectArgs`:
```typescript
const connectOptions: ConnectArgs = {
// ...
pollingHost: 'gp-v2.replit.com',
};
client.connect(connectOptions);
```
### For more information
Thanks to https://hackerone.com/orlserg for disclosing this.
If you have any questions or comments about this advisory:
* Open an issue in [replit/crosis](https://github.com/replit/crosis)
* Email us at [security@replit.com](mailto:security@replit.com) | {'CVE-2022-21671'} | 2022-01-10T23:18:10Z | 2022-01-12T22:44:47Z | HIGH | null | {'CWE-200'} | {'https://github.com/replit/crosis/security/advisories/GHSA-7w54-gp8x-f33m', 'https://github.com/replit/crosis', 'https://github.com/replit/crosis/commit/e44b6a8f5fa28cb2872e3c19bb8a205bb5bfc281', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21671'} | null | {'https://github.com/replit/crosis/commit/e44b6a8f5fa28cb2872e3c19bb8a205bb5bfc281'} | {'https://github.com/replit/crosis/commit/e44b6a8f5fa28cb2872e3c19bb8a205bb5bfc281'} |
npm | GHSA-6hwh-rqwf-cxxr | Improperly Controlled Modification of Dynamically-Determined Object Attributes in vega-util | vega-util prior to 1.13.1 allows manipulation of object prototype. The 'vega.mergeConfig' method within vega-util could be tricked into adding or modifying properties of the Object.prototype. | {'CVE-2019-10806'} | 2021-07-28T18:36:56Z | 2021-05-07T16:32:02Z | MODERATE | null | {'CWE-915', 'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-10806', 'https://github.com/vega/vega/commit/8f33a0b5170d7de4f12fc248ec0901234342367b', 'https://snyk.io/vuln/SNYK-JS-VEGAUTIL-559223'} | null | {'https://github.com/vega/vega/commit/8f33a0b5170d7de4f12fc248ec0901234342367b'} | {'https://github.com/vega/vega/commit/8f33a0b5170d7de4f12fc248ec0901234342367b'} |
npm | GHSA-9m6j-fcg5-2442 | Path traversal in url-parse | url-parse before 1.5.0 mishandles certain uses of backslash such as http:\/ and interprets the URI as a relative path. | {'CVE-2021-27515'} | 2021-05-06T16:31:23Z | 2021-05-06T16:10:51Z | HIGH | null | {'CWE-23'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-27515', 'https://github.com/unshiftio/url-parse/compare/1.4.7...1.5.0', 'https://advisory.checkmarx.net/advisory/CX-2021-4306', 'https://github.com/unshiftio/url-parse/commit/d1e7e8822f26e8a49794b757123b51386325b2b0', 'https://github.com/unshiftio/url-parse/pull/197'} | null | {'https://github.com/unshiftio/url-parse/commit/d1e7e8822f26e8a49794b757123b51386325b2b0'} | {'https://github.com/unshiftio/url-parse/commit/d1e7e8822f26e8a49794b757123b51386325b2b0'} |
npm | GHSA-hwch-749c-rv63 | Potential Command Injection in hubot-scripts | Versions 2.4.3 and earlier of hubot-scripts are vulnerable to a command injection vulnerablity in the `hubot-scripts/package/src/scripts/email.coffee` module.
### Mitigating Factors
The email script is not enabled by default, it has to be manually added to hubot's list of loaded scripts.
## Recommendation
Update hubot-scripts to version 2.4.4 or later. | {'CVE-2013-7378'} | 2021-04-12T21:34:54Z | 2020-08-31T22:46:38Z | CRITICAL | null | {'CWE-74'} | {'https://nodesecurity.io/advisories/Hubot_Potential_command_injection_in_email.coffee', 'https://www.npmjs.com/advisories/13', 'https://nvd.nist.gov/vuln/detail/CVE-2013-7378', 'https://github.com/github/hubot-scripts/commit/feee5abdb038a229a98969ae443cdb8a61747782', 'https://web.archive.org/web/20140731222413/', 'https://', 'http://www.openwall.com/lists/oss-security/2014/05/15/2', 'http://www.openwall.com/lists/oss-security/2014/05/13/1'} | null | {'https://github.com/github/hubot-scripts/commit/feee5abdb038a229a98969ae443cdb8a61747782'} | {'https://github.com/github/hubot-scripts/commit/feee5abdb038a229a98969ae443cdb8a61747782'} |
npm | GHSA-8vv3-jxm8-f4vf | Prototype Pollution in connie-lang | The package connie-lang before 0.1.1 are vulnerable to Prototype Pollution in the configuration language library used by connie. | {'CVE-2020-7706'} | 2021-05-05T21:19:56Z | 2021-05-06T17:29:25Z | CRITICAL | null | {'CWE-915'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-7706', 'https://snyk.io/vuln/SNYK-JS-CONNIELANG-598853', 'https://github.com/mattinsler/connie-lang/commit/ef376d404c712dd28309ba07f28a8f87f24a015a'} | null | {'https://github.com/mattinsler/connie-lang/commit/ef376d404c712dd28309ba07f28a8f87f24a015a'} | {'https://github.com/mattinsler/connie-lang/commit/ef376d404c712dd28309ba07f28a8f87f24a015a'} |
npm | GHSA-5w65-6875-rhq8 | Undefined Behavior in sailsjs-cacheman | All versions of `sailsjs-cacheman` have a vulnerability that may lead to Undefined Behavior. The config variable is exposing to the global scope which may overwrite other variables and cause the application to misbehave.
## Recommendation
No fix is currently available. Consider using an alternative module until a fix is made available. | null | 2020-08-31T18:34:32Z | 2019-09-11T23:01:57Z | LOW | null | null | {'https://github.com/gayanhewa/sailsjs-cacheman/pull/10', 'https://www.npmjs.com/advisories/752', 'https://github.com/gayanhewa/sailsjs-cacheman/commit/4a456f44141ae2d5aed8cb32a82063356dcc318f'} | null | {'https://github.com/gayanhewa/sailsjs-cacheman/commit/4a456f44141ae2d5aed8cb32a82063356dcc318f'} | {'https://github.com/gayanhewa/sailsjs-cacheman/commit/4a456f44141ae2d5aed8cb32a82063356dcc318f'} |
npm | GHSA-98pq-pmw9-4gpm | SQL Injection in sequelize | Affected versions of `sequelize` are vulnerable to SQL Injection in locations where user input is passed into the `limit` or `order` parameters of `sequelize` query calls, such as `findOne` or `findAll`.
## Recommendation
Update to version 3.17.0 or later. | {'CVE-2016-10550'} | 2020-08-31T18:11:11Z | 2019-02-18T23:54:34Z | HIGH | null | {'CWE-89'} | {'https://github.com/advisories/GHSA-98pq-pmw9-4gpm', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10550', 'https://www.npmjs.com/advisories/112', 'https://github.com/sequelize/sequelize/pull/5167/commits/f282d85e60e3df5e57ecdb82adccb4eaef404f03', 'https://nodesecurity.io/advisories/112'} | null | {'https://github.com/sequelize/sequelize/pull/5167/commits/f282d85e60e3df5e57ecdb82adccb4eaef404f03'} | {'https://github.com/sequelize/sequelize/pull/5167/commits/f282d85e60e3df5e57ecdb82adccb4eaef404f03'} |
npm | GHSA-w8h4-vw8f-rvvj | Improper Control of Dynamically-Managed Code Resources in config-shield | scripts/cli.js in the GoDaddy node-config-shield (aka Config Shield) package before 0.2.2 for Node.js calls eval when processing a set command. NOTE: the vendor reportedly states that this is not a vulnerability. The set command was not intended for use with untrusted data. | {'CVE-2021-26276'} | 2022-04-27T20:27:30Z | 2021-04-13T15:30:09Z | MODERATE | null | {'CWE-913'} | {'https://github.com/godaddy/node-config-shield', 'https://github.com/godaddy/node-config-shield/commit/cdba5d3a7accd661ffbc52e208153464bd0d9da6', 'https://advisory.checkmarx.net/advisory/CX-2021-4773', 'https://nvd.nist.gov/vuln/detail/CVE-2021-26276'} | null | {'https://github.com/godaddy/node-config-shield/commit/cdba5d3a7accd661ffbc52e208153464bd0d9da6'} | {'https://github.com/godaddy/node-config-shield/commit/cdba5d3a7accd661ffbc52e208153464bd0d9da6'} |
npm | GHSA-2mm9-c2fx-c7m4 | XSS in docsify | This affects the package docsify before 4.12.0. It is possible to bypass the remediation done by CVE-2020-7680 and execute malicious JavaScript through the following methods 1) When parsing HTML from remote URLs, the HTML code on the main page is sanitized, but this sanitization is not taking place in the sidebar. 2) The isURL external check can be bypassed by inserting more “////” characters | {'CVE-2021-23342'} | 2021-03-15T23:55:40Z | 2021-03-01T19:44:27Z | HIGH | null | {'CWE-79'} | {'https://github.com/docsifyjs/docsify/commit/ff2a66f12752471277fe81a64ad6c4b2c08111fe', 'http://seclists.org/fulldisclosure/2021/Feb/71', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23342', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1076593', 'http://packetstormsecurity.com/files/161495/docsify-4.11.6-Cross-Site-Scripting.html', 'https://www.npmjs.com/package/docsify', 'https://snyk.io/vuln/SNYK-JS-DOCSIFY-1066017'} | null | {'https://github.com/docsifyjs/docsify/commit/ff2a66f12752471277fe81a64ad6c4b2c08111fe'} | {'https://github.com/docsifyjs/docsify/commit/ff2a66f12752471277fe81a64ad6c4b2c08111fe'} |
npm | GHSA-cxjc-r2fp-7mq6 | XSS in dijit editor's LinkDialog plugin | ### Impact
XSS possible for users of the Dijit Editor's LinkDialog plugin
### Patches
Yes, 1.11.11, 1.12.9, 1.13.8, 1.14.7, 1.15.4, 1.16.3
### Workarounds
Users may apply the patch made in these releases.
### For more information
If you have any questions or comments about this advisory, open an issue in [dojo/dijit](https://github.com/dojo/dijit/) | {'CVE-2020-4051'} | 2021-01-08T20:11:17Z | 2020-06-15T21:53:12Z | LOW | null | {'CWE-79'} | {'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://github.com/dojo/dijit/commit/462bdcd60d0333315fe69ab4709c894d78f61301', 'https://security.netapp.com/advisory/ntap-20201023-0003/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-4051', 'https://github.com/dojo/dijit/security/advisories/GHSA-cxjc-r2fp-7mq6'} | null | {'https://github.com/dojo/dijit/commit/462bdcd60d0333315fe69ab4709c894d78f61301'} | {'https://github.com/dojo/dijit/commit/462bdcd60d0333315fe69ab4709c894d78f61301'} |
npm | GHSA-7375-vjr2-3g7w | Cross-Site Scripting in glance | Versions of `glance` before 3.0.8 are vulnerable to Stored Cross-Site Scripting (XSS). This is only exploitable if the attacker is able to control the name of a file that is served by the `glance` package. | {'CVE-2018-3748'} | 2021-09-02T19:13:45Z | 2018-09-27T11:37:19Z | MODERATE | null | {'CWE-79'} | {'https://hackerone.com/reports/310133', 'https://github.com/jarofghosts/glance/commit/cdc68bb68d785343ddb829f1adc130cdd6169533', 'https://www.npmjs.com/advisories/610', 'https://github.com/jarofghosts/glance', 'https://github.com/advisories/GHSA-7375-vjr2-3g7w', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3748'} | null | {'https://github.com/jarofghosts/glance/commit/cdc68bb68d785343ddb829f1adc130cdd6169533'} | {'https://github.com/jarofghosts/glance/commit/cdc68bb68d785343ddb829f1adc130cdd6169533'} |
npm | GHSA-x2fc-mxcx-w4mf | Prototype Pollution in mathjs | The package mathjs before 7.5.1 are vulnerable to Prototype Pollution via the deepExtend function that runs upon configuration updates. | {'CVE-2020-7743'} | 2021-04-21T19:47:53Z | 2021-05-10T18:39:04Z | HIGH | null | {'CWE-915'} | {'https://github.com/josdejong/mathjs/blob/develop/HISTORY.md#2020-10-10-version-751', 'https://snyk.io/vuln/SNYK-JS-MATHJS-1016401', 'https://www.npmjs.com/package/mathjs', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARS-1017113', 'https://github.com/josdejong/mathjs/commit/ecb80514e80bce4e6ec7e71db8ff79954f07c57e', 'https://github.com/josdejong/mathjs/blob/develop/src/utils/object.js%23L82', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7743'} | null | {'https://github.com/josdejong/mathjs/commit/ecb80514e80bce4e6ec7e71db8ff79954f07c57e'} | {'https://github.com/josdejong/mathjs/commit/ecb80514e80bce4e6ec7e71db8ff79954f07c57e'} |
npm | GHSA-gcv8-gh4r-25x6 | Authorization Bypass Through User-Controlled Key in urijs | Attacker can use case-insensitive protocol schemes like HTTP, htTP, HTtp etc. in order to bypass the patch for CVE-2021-3647. | {'CVE-2022-0613'} | 2022-04-01T18:06:53Z | 2022-02-17T00:00:35Z | MODERATE | null | {'CWE-639'} | {'https://huntr.dev/bounties/f53d5c42-c108-40b8-917d-9dad51535083', 'https://github.com/medialize/uri.js/commit/6ea641cc8648b025ed5f30b090c2abd4d1a5249f', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0613', 'https://github.com/medialize/uri.js', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MXSSATHALUSXXD2KT6UFZAX7EG4GR332/'} | null | {'https://github.com/medialize/uri.js/commit/6ea641cc8648b025ed5f30b090c2abd4d1a5249f'} | {'https://github.com/medialize/uri.js/commit/6ea641cc8648b025ed5f30b090c2abd4d1a5249f'} |
npm | GHSA-pw2r-vq6v-hr8c | Exposure of Sensitive Information to an Unauthorized Actor in follow-redirects | Exposure of Sensitive Information to an Unauthorized Actor in NPM follow-redirects prior to 1.14.8. | {'CVE-2022-0536'} | 2022-02-14T22:27:56Z | 2022-02-10T00:00:31Z | MODERATE | null | {'CWE-200'} | {'https://github.com/follow-redirects/follow-redirects', 'https://github.com/follow-redirects/follow-redirects/commit/62e546a99c07c3ee5e4e0718c84a6ca127c5c445', 'https://huntr.dev/bounties/7cf2bf90-52da-4d59-8028-a73b132de0db', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0536'} | null | {'https://github.com/follow-redirects/follow-redirects/commit/62e546a99c07c3ee5e4e0718c84a6ca127c5c445'} | {'https://github.com/follow-redirects/follow-redirects/commit/62e546a99c07c3ee5e4e0718c84a6ca127c5c445'} |
npm | GHSA-9g9w-hmvj-5h57 | Prototype Pollution in merge-deep | Versions of `merge-deep` before 3.0.1 are vulnerable to prototype pollution via merging functions.
## Recommendation
Update to version 3.0.1 or later. | {'CVE-2018-3722'} | 2020-08-31T18:28:36Z | 2018-07-26T15:17:15Z | LOW | null | {'CWE-471'} | {'https://github.com/jonschlinkert/merge-deep/commit/2c33634da7129a5aefcc262d2fec2e72224404e5', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3722', 'https://www.npmjs.com/advisories/580', 'https://github.com/advisories/GHSA-9g9w-hmvj-5h57', 'https://hackerone.com/reports/310708'} | null | {'https://github.com/jonschlinkert/merge-deep/commit/2c33634da7129a5aefcc262d2fec2e72224404e5'} | {'https://github.com/jonschlinkert/merge-deep/commit/2c33634da7129a5aefcc262d2fec2e72224404e5'} |
npm | GHSA-3q32-j57w-q4w7 | Path Traversal in total.js | Affected versions of `total.js` are vulnerable to Path Traversal. Due to insufficient input sanitization in URLs, attackers can access server files outside the `/public` folder by using relative paths.
The files served are limited to these file types: `flac`, `jpg`, `jpeg`, `png`, `gif`, `ico`, `js`, `css`, `txt`, `xml`, `woff`, `woff2`, `otf`, `ttf`, `eot`, `svg`, `zip`, `rar`, `pdf`, `docx`, `xlsx`, `doc`, `xls`, `html`, `htm`, `appcache`, `manifest`, `map`, `ogv`, `ogg`, `mp4`, `mp3`, `webp`, `webm`, `swf`, `package`, `json`, `md`, `m4v`, `jsx`, `heif`, `heic`.
## Recommendation
- If you are using version 2.1.x, upgrade to 2.1.1 or later.
- If you are using version 2.2.x, upgrade to 2.2.1 or later.
- If you are using version 2.3.x, upgrade to 2.3.1 or later.
- If you are using version 2.4.x, upgrade to 2.4.1 or later.
- If you are using version 2.5.x, upgrade to 2.5.1 or later.
- If you are using version 2.6.x, upgrade to 2.6.3 or later.
- If you are using version 2.7.x, upgrade to 2.7.1 or later.
- If you are using version 2.8.x, upgrade to 2.8.1 or later.
- If you are using version 2.9.x, upgrade to 2.9.5 or later.
- If you are using version 3.0.x, upgrade to 3.0.1 or later.
- If you are using version 3.1.x, upgrade to 3.1.1 or later.
- If you are using version 3.2.x, upgrade to 3.2.4 or later. | {'CVE-2019-8903'} | 2021-08-31T21:22:06Z | 2019-02-20T15:40:13Z | HIGH | null | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-8903', 'https://github.com/totaljs/framework/commit/de16238d13848149f5d1dae51f54e397a525932b', 'https://github.com/advisories/GHSA-3q32-j57w-q4w7', 'https://github.com/totaljs/framework', 'https://www.npmjs.com/advisories/1026', 'https://github.com/totaljs/framework/commit/c37cafbf3e379a98db71c1125533d1e8d5b5aef7', 'https://blog.certimetergroup.com/it/articolo/security/total.js-directory-traversal-cve-2019-8903'} | null | {'https://github.com/totaljs/framework/commit/c37cafbf3e379a98db71c1125533d1e8d5b5aef7', 'https://github.com/totaljs/framework/commit/de16238d13848149f5d1dae51f54e397a525932b'} | {'https://github.com/totaljs/framework/commit/c37cafbf3e379a98db71c1125533d1e8d5b5aef7', 'https://github.com/totaljs/framework/commit/de16238d13848149f5d1dae51f54e397a525932b'} |
npm | GHSA-3j9m-hcv9-rpj8 | XSS vulnerability allowing arbitrary JavaScript execution | Today we are releasing Grafana 8.2.3. This patch release includes an important security fix for an issue that affects all Grafana versions from 8.0.0-beta1.
[Grafana Cloud](https://grafana.com/cloud) instances have already been patched and an audit did not find any usage of this attack vector. [Grafana Enterprise](https://grafana.com/products/enterprise) customers were provided with updated binaries under embargo.
## CVE-2021-41174 XSS vulnerability on unauthenticated pages
### Summary
CVSS Score: 6.9 Medium
CVSS:[CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:N/E:U/RL:O/RC:R/CR:L/MAV:N/MAC:H/MPR:N/MUI:R/MS:C/MC:N/MI:H/MA:L](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:N/E:U/RL:O/RC:R/CR:L/MAV:N/MAC:H/MPR:N/MUI:R/MS:C/MC:N/MI:H/MA:L)
We received a security report to security@grafana.com on 2021-10-21 about a vulnerability in Grafana regarding the XSS vulnerability.
It was later identified as affecting Grafana versions from 8.0.0-beta1 to 8.2.2. [CVE-2021-41174](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41174) has been assigned to this vulnerability.
### Impact
If an attacker is able to convince a victim to visit a URL referencing a vulnerable page, arbitrary JavaScript content may be executed within the context of the victim's browser.
The user visiting the malicious link must be unauthenticated and the link must be for a page that contains the login button in the menu bar.
There are two ways an unauthenticated user can open a page in Grafana that contains the login button:
- Anonymous authentication is enabled. This means all pages in Grafana would be open for the attack.
- The link is to an unauthenticated page. The following pages are vulnerable:
- `/dashboard-solo/snapshot/*`
- `/dashboard/snapshot/*`
- `/invite/:code`
The url has to be crafted to exploit AngularJS rendering and contain the interpolation binding for AngularJS expressions. AngularJS uses double curly braces for interpolation binding: {{ }}
An example of an expression would be: `{{constructor.constructor(‘alert(1)’)()}}`. This can be included in the link URL like this:
https://play.grafana.org/dashboard/snapshot/%7B%7Bconstructor.constructor('alert(1)')()%7D%7D?orgId=1
When the user follows the link and the page renders, the login button will contain the original link with a query parameter to force a redirect to the login page. The URL is not validated and the AngularJS rendering engine will execute the JavaScript expression contained in the URL.
### Attack audit
We can not guarantee that the below will identify all attacks, so if you find something using the audit process described below, you should consider doing a full assessment.
#### Through reverse proxy/load balancer logs
To determine if your Grafana installation has been exploited for this vulnerability, search through your reverse proxy/load balancer access logs for instances where the path contains `{{` followed by something that would invoke JavaScript code. For example, this could be code that attempts to show a fake login page or to steal browser or session data. The [OWASP cheat sheet](https://cheatsheetseries.owasp.org/cheatsheets/XSS_Filter_Evasion_Cheat_Sheet.html) has several examples of XSS attacks.
#### Through the Grafana Enterprise audit feature
If you enabled “Log web requests” in your configuration with `router_logging = true`, look for requests where `path` contains `{{` followed by something that would invoke JavaScript code.
### Patched versions
Release 8.2.3:
- [Download Grafana 8.2.3](https://grafana.com/grafana/download/8.2.3)
- [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-8-2-3/)
### Solutions and mitigations
Download and install the appropriate patch for your version of Grafana.
[Grafana Cloud](https://grafana.com/cloud) instances have already been patched, and [Grafana Enterprise](https://grafana.com/products/enterprise) customers were provided with updated binaries under embargo.
### Workaround
If for some reason you cannot upgrade, you can use a reverse proxy or similar to block access to block the literal string `{{` in the path.
Example of an Nginx rule to block the literal string `{{`:
```
location ~ \{\{ {
deny all;
}
```
### Timeline and postmortem
Here is a detailed timeline starting from when we originally learned of the issue. All times in UTC.
* 2021-10-21 23:13: Security researcher sends the initial report about an XSS vulnerability.
* 2021-10-21 23:13: Confirmed to be reproducible in at least versions 8.0.5 and 8.2.2.
* 2021-10-22 02:02 MEDIUM severity declared.
* 2021-10-22 09:22: it is discovered that Grafana instances with anonymous auth turned on are vulnerable. This includes https://play.grafana.org/ .
* 2021-10-22 09:50: Anonymous access disabled for all instances on Grafana Cloud as a mitigation measure.
* 2021-10-22 11:15: Workaround deployed on Grafana Cloud that blocks malicious requests.
* 2021-10-22 12:35: Enabled anonymous access for instances on Grafana Cloud.
* 2021-10-22 12:51: All instances protected by the workaround. From this point forward, Grafana Cloud is no longer affected.
* 2021-10-22 14:05 Grafana Cloud instances updated with a fix.
* 2021-10-22 19:23 :Determination that no weekend work is needed as the issue is of MEDIUM severity and the root cause has been identified.
* 2021-10-25 14:13: Audit of Grafana Cloud concluded, no evidence of exploitation.
* 2021-10-27 12:00: Grafana Enterprise images released to customers under embargo.
* 2021-11-03 12:00: Public release.
## Reporting security issues
If you think you have found a security vulnerability, please send a report to [security@grafana.com](mailto:security@grafana.com). This address can be used for all of
Grafana Labs' open source and commercial products (including but not limited to Grafana, Tempo, Loki, k6, Tanka, and Grafana Cloud, Grafana Enterprise, and grafana.com). We only accept vulnerability reports at this address. We would prefer that you encrypt your message to us using our PGP key. The key fingerprint is:
F988 7BEA 027A 049F AE8E 5CAA D125 8932 BE24 C5CA
The key is available from [ keyserver.ubuntu.com]( https://keyserver.ubuntu.com/pks/lookup?op=get&fingerprint=on&search=0xD1258932BE24C5CA) by searching for [security@grafana]( https://keyserver.ubuntu.com/pks/lookup?search=security@grafana&fingerprint=on&op=index).
## Security announcements
There is a Security [category](https://grafana.com/tags/security/) on the Grafana blog where we will post a summary, remediation, and mitigation details for any patch containing security fixes and you can subscribe to updates from our [Security Announcements RSS feed](https://grafana.com/tags/security/index.xml). | {'CVE-2021-41174'} | 2021-11-29T15:05:31Z | 2021-11-08T18:13:19Z | MODERATE | null | {'CWE-79'} | {'https://security.netapp.com/advisory/ntap-20211125-0003/', 'https://github.com/grafana/grafana/commit/3cb5214fa45eb5a571fd70d6c6edf0d729983f82', 'https://github.com/grafana/grafana/commit/fb85ed691290d211a5baa44d9a641ab137f0de88', 'https://github.com/grafana/grafana/commit/31b78d51c693d828720a5b285107a50e6024c912', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41174', 'https://github.com/grafana/grafana/security/advisories/GHSA-3j9m-hcv9-rpj8', 'https://github.com/grafana/grafana'} | null | {'https://github.com/grafana/grafana/commit/fb85ed691290d211a5baa44d9a641ab137f0de88', 'https://github.com/grafana/grafana/commit/31b78d51c693d828720a5b285107a50e6024c912', 'https://github.com/grafana/grafana/commit/3cb5214fa45eb5a571fd70d6c6edf0d729983f82'} | {'https://github.com/grafana/grafana/commit/3cb5214fa45eb5a571fd70d6c6edf0d729983f82', 'https://github.com/grafana/grafana/commit/31b78d51c693d828720a5b285107a50e6024c912', 'https://github.com/grafana/grafana/commit/fb85ed691290d211a5baa44d9a641ab137f0de88'} |
npm | GHSA-3crj-w4f5-gwh4 | Processing untrusted theming resources might execute arbitrary code (ACE) | ### Impact
When processing theming resources (i.e. `*.less` files) with less-openui5 that originate from an untrusted source, those resources might contain JavaScript code which will be executed in the context of the build process.
While this is a [feature](http://lesscss.org/usage/#less-options-enable-inline-javascript-deprecated-) of the [Less.js library](https://github.com/less/less.js), it is an unexpected behavior in the context of OpenUI5 and SAPUI5 development.
Especially in the context of [UI5 Tooling](https://github.com/SAP/ui5-tooling), which relies on less-openui5, this poses a security threat:
An attacker might create a [library](https://sap.github.io/ui5-tooling/pages/Builder/#library) or [theme-library](https://sap.github.io/ui5-tooling/pages/Builder/#theme-library) containing a custom control or theme, hiding malicious JavaScript code in one of the `.less` files.
This is an example of inline JavaScript in a Less file:
```less
.rule {
@var: `(function(){console.log('Hello from JavaScript'); process.exit(1);})()`;
color: @var;
}
```
Starting with Less.js version 3.0.0, the Inline JavaScript feature is disabled by default. less-openui5 however currently uses [a fork](https://github.com/SAP/less-openui5/tree/master/lib/thirdparty/less) of Less.js v1.6.3.
Note that disabling the Inline JavaScript feature in Less.js versions 1.x, still evaluates code has additional double codes around it:
```less
.rule {
@var: "`(function(){console.log('Hello from JavaScript'); process.exit(1);})()`";
color: @var;
}
```
### Patches
We decided to remove the inline JavaScript evaluation feature completely from the code of our Less.js fork.
This fix is available in less-openui5 version [v0.10.0](https://github.com/SAP/less-openui5/releases/tag/v0.10.0)
### Workarounds
Only process trusted theming resources.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/SAP/less-openui5
* Email us at secure@sap.com | {'CVE-2021-21316'} | 2021-02-16T17:35:25Z | 2021-01-29T20:51:37Z | HIGH | null | {'CWE-74'} | {'https://github.com/SAP/less-openui5/releases/tag/v0.10.0', 'https://github.com/SAP/less-openui5/security/advisories/GHSA-3crj-w4f5-gwh4', 'https://www.npmjs.com/package/less-openui5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21316', 'https://github.com/SAP/less-openui5/commit/c0d3a8572974a20ea6cee42da11c614a54f100e8', 'http://lesscss.org/usage/#less-options-enable-inline-javascript-deprecated-'} | null | {'https://github.com/SAP/less-openui5/commit/c0d3a8572974a20ea6cee42da11c614a54f100e8'} | {'https://github.com/SAP/less-openui5/commit/c0d3a8572974a20ea6cee42da11c614a54f100e8'} |
npm | GHSA-p6mc-m468-83gw | Prototype Pollution in lodash | Versions of lodash prior to 4.17.19 are vulnerable to Prototype Pollution. The function zipObjectDeep allows a malicious user to modify the prototype of Object if the property identifiers are user-supplied. Being affected by this issue requires zipping objects based on user-provided property arrays.
This vulnerability causes the addition or modification of an existing property that will exist on all objects and may lead to Denial of Service or Code Execution under specific circumstances. | {'CVE-2020-8203'} | 2022-02-08T22:04:28Z | 2020-07-15T19:15:48Z | HIGH | null | {'CWE-1321', 'CWE-770'} | {'https://hackerone.com/reports/712065', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8203', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://github.com/lodash/lodash/issues/4874', 'https://github.com/lodash/lodash', 'https://security.netapp.com/advisory/ntap-20200724-0006/', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://github.com/lodash/lodash/issues/4744', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://github.com/lodash/lodash/commit/c84fe82760fb2d3e03a63379b297a1cc1a2fce12', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://www.npmjs.com/advisories/1523', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/lodash/lodash/commit/c84fe82760fb2d3e03a63379b297a1cc1a2fce12'} | {'https://github.com/lodash/lodash/commit/c84fe82760fb2d3e03a63379b297a1cc1a2fce12'} |
npm | GHSA-cwx2-736x-mf6w | Prototype pollution in object-path | ### Impact
A prototype pollution vulnerability has been found in `object-path` <= 0.11.4 affecting the `set()` method. The vulnerability is limited to the `includeInheritedProps` mode (if version >= 0.11.0 is used), which has to be explicitly enabled by creating a new instance of `object-path` and setting the option `includeInheritedProps: true`, or by using the default `withInheritedProps` instance. The default operating mode is not affected by the vulnerability if version >= 0.11.0 is used. Any usage of `set()` in versions < 0.11.0 is vulnerable.
### Patches
Upgrade to version >= 0.11.5
### Workarounds
Don't use the `includeInheritedProps: true` options or the `withInheritedProps` instance if using a version >= 0.11.0.
### References
[Read more about the prototype pollution vulnerability](https://codeburst.io/what-is-prototype-pollution-49482fc4b638)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [object-path](https://github.com/mariocasciaro/object-path) | {'CVE-2020-15256'} | 2021-11-19T14:05:56Z | 2020-10-19T20:55:55Z | HIGH | null | {'CWE-471', 'CWE-20'} | {'https://github.com/mariocasciaro/object-path/security/advisories/GHSA-cwx2-736x-mf6w', 'https://github.com/mariocasciaro/object-path/commit/2be3354c6c46215c7635eb1b76d80f1319403c68', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15256', 'https://github.com/mariocasciaro/object-path'} | null | {'https://github.com/mariocasciaro/object-path/commit/2be3354c6c46215c7635eb1b76d80f1319403c68'} | {'https://github.com/mariocasciaro/object-path/commit/2be3354c6c46215c7635eb1b76d80f1319403c68'} |
npm | GHSA-x949-7cm6-fm6p | Code Injection in md-to-pdf. | The package md-to-pdf before 5.0.0 are vulnerable to Remote Code Execution (RCE) due to utilizing the library gray-matter to parse front matter content, without disabling the JS engine. | {'CVE-2021-23639'} | 2021-12-15T15:22:46Z | 2021-12-16T14:34:40Z | CRITICAL | null | {'CWE-94'} | {'https://snyk.io/vuln/SNYK-JS-MDTOPDF-1657880', 'https://github.com/simonhaenisch/md-to-pdf/commit/a716259c548c82fa1d3b14a3422e9100619d2d8a', 'https://github.com/simonhaenisch/md-to-pdf/issues/99', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23639', 'https://github.com/simonhaenisch/md-to-pdf'} | null | {'https://github.com/simonhaenisch/md-to-pdf/commit/a716259c548c82fa1d3b14a3422e9100619d2d8a'} | {'https://github.com/simonhaenisch/md-to-pdf/commit/a716259c548c82fa1d3b14a3422e9100619d2d8a'} |
npm | GHSA-pg97-ww7h-5mjr | XSS in dojox due to insufficient escape in dojox.xmpp.util.xmlEncode | ### Impact
_What kind of vulnerability is it? Who is impacted?_
Potential XSS vulnerability for users of `dojox/xmpp` and `dojox/dtl`.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
Yes, patches are available for the 1.11 through 1.16 versions. Users should upgrade to one of these versions of Dojo:
* 1.16.1
* 1.15.2
* 1.14.5
* 1.13.6
* 1.12.7
* 1.11.9
Users of Dojo 1.10.x and earlier should review this change and determine if it impacts them, and backport the change as appropriate.
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
The change applied in https://github.com/dojo/dojox/pull/315 could get added separately as a patch.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [dojo/dojox](https://github.com/dojo/dojox/) | {'CVE-2019-10785'} | 2021-08-19T17:21:06Z | 2020-02-13T22:21:06Z | MODERATE | null | {'CWE-79'} | {'https://snyk.io/vuln/SNYK-JS-DOJOX-548257,', 'https://github.com/dojo/dojox/pull/315', 'https://lists.debian.org/debian-lts-announce/2020/02/msg00033.html', 'https://github.com/dojo/dojox/commit/abd033a787c718abc1a390f480ac3ea61288e5ee', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10785', 'https://snyk.io/vuln/SNYK-JS-DOJOX-548257', 'https://github.com/dojo/dojox/security/advisories/GHSA-pg97-ww7h-5mjr'} | null | {'https://github.com/dojo/dojox/commit/abd033a787c718abc1a390f480ac3ea61288e5ee'} | {'https://github.com/dojo/dojox/commit/abd033a787c718abc1a390f480ac3ea61288e5ee'} |
npm | GHSA-3949-f494-cm99 | Cross-site Scripting in Prism | ### Impact
Prism's [Command line plugin](https://prismjs.com/plugins/command-line/) can be used by attackers to achieve an XSS attack. The Command line plugin did not properly escape its output, leading to the input text being inserted into the DOM as HTML code.
Server-side usage of Prism is not impacted. Websites that do not use the Command Line plugin are also not impacted.
### Patches
This bug has been fixed in v1.27.0.
### Workarounds
Do not use the Command line plugin on untrusted inputs, or sanitized all code blocks (remove all HTML code text) from all code blocks that use the Command line plugin.
### References
- https://github.com/PrismJS/prism/pull/3341 | {'CVE-2022-23647'} | 2022-02-22T19:32:18Z | 2022-02-22T19:32:18Z | HIGH | null | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-23647', 'https://github.com/PrismJS/prism/security/advisories/GHSA-3949-f494-cm99', 'https://github.com/PrismJS/prism', 'https://github.com/PrismJS/prism/commit/e002e78c343154e1c0ddf9d6a0bb85689e1a5c7c', 'https://github.com/PrismJS/prism/pull/3341'} | null | {'https://github.com/PrismJS/prism/commit/e002e78c343154e1c0ddf9d6a0bb85689e1a5c7c'} | {'https://github.com/PrismJS/prism/commit/e002e78c343154e1c0ddf9d6a0bb85689e1a5c7c'} |
npm | GHSA-7r28-3m3f-r2pr | Regular Expression Denial of Service (ReDoS) | The is-svg package 2.1.0 through 4.2.1 for Node.js uses a regular expression that is vulnerable to Regular Expression Denial of Service (ReDoS). If an attacker provides a malicious string, is-svg will get stuck processing the input for a very long time. | {'CVE-2021-28092'} | 2021-03-25T00:18:05Z | 2021-03-19T21:25:50Z | HIGH | null | {'CWE-400'} | {'https://github.com/sindresorhus/is-svg/releases', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28092', 'https://github.com/sindresorhus/is-svg/releases/tag/v4.2.2', 'https://www.npmjs.com/package/is-svg', 'https://security.netapp.com/advisory/ntap-20210513-0008/', 'https://github.com/sindresorhus/is-svg/commit/01f8a087fab8a69c3ac9085fbb16035907ab6a5b'} | null | {'https://github.com/sindresorhus/is-svg/commit/01f8a087fab8a69c3ac9085fbb16035907ab6a5b'} | {'https://github.com/sindresorhus/is-svg/commit/01f8a087fab8a69c3ac9085fbb16035907ab6a5b'} |
npm | GHSA-pp7m-6j83-m7r6 | Cross-site Scripting in video.js | This affects the package video.js before 7.14.3.
The src attribute of track tag allows to bypass HTML escaping and execute arbitrary code.
| {'CVE-2021-23414'} | 2021-08-31T21:01:29Z | 2021-08-10T16:09:36Z | MODERATE | null | {'CWE-79'} | {'https://snyk.io/vuln/SNYK-JS-VIDEOJS-1533429', 'https://github.com/videojs/video.js', 'https://github.com/videojs/video.js/commit/b3acf663641fca0f7a966525a72845af7ec5fab2', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1533587', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23414', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-1533588'} | null | {'https://github.com/videojs/video.js/commit/b3acf663641fca0f7a966525a72845af7ec5fab2'} | {'https://github.com/videojs/video.js/commit/b3acf663641fca0f7a966525a72845af7ec5fab2'} |
npm | GHSA-rf54-44jr-q5vf | Improper Input Validation in url-js | The package url-js before 2.1.0 is vulnerable to Improper Input Validation due to improper parsing, which makes it is possible for the hostname to be spoofed. http://\\\\\\\\localhost and http://localhost are the same URL. However, the hostname is not parsed as localhost, and the backslash is reflected as it is. | {'CVE-2022-25839'} | 2022-03-28T22:33:07Z | 2022-03-12T00:00:26Z | MODERATE | null | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-25839', 'https://github.com/duzun/URL.js/commit/9dc9fcc99baa4cbda24403d81a589e9b0f4121d0', 'https://snyk.io/vuln/SNYK-JS-URLJS-2414030', 'https://github.com/duzun/URL.js'} | null | {'https://github.com/duzun/URL.js/commit/9dc9fcc99baa4cbda24403d81a589e9b0f4121d0'} | {'https://github.com/duzun/URL.js/commit/9dc9fcc99baa4cbda24403d81a589e9b0f4121d0'} |
npm | GHSA-x9p2-fxq6-2m5f | Reverse Tabnapping in swagger-ui | Versions of `swagger-ui` prior to 3.18.0 are vulnerable to [Reverse Tabnapping](https://www.owasp.org/index.php/Reverse_Tabnabbing). The package uses `target='_blank'` in anchor tags, allowing attackers to access `window.opener` for the original page. This is commonly used for phishing attacks.
## Recommendation
Upgrade to version 3.18.0 or later. | null | 2021-08-16T23:44:47Z | 2019-06-20T14:33:07Z | MODERATE | null | {'CWE-1022'} | {'https://github.com/swagger-api/swagger-ui/pull/4789', 'https://github.com/swagger-api/swagger-ui/commit/3f4cae3334fdd492a373f4453bd03a9ebd87becf', 'https://github.com/swagger-api/swagger-ui/releases/tag/v3.18.0', 'https://snyk.io/vuln/SNYK-JS-SWAGGERUI-449808', 'https://www.npmjs.com/advisories/975'} | null | {'https://github.com/swagger-api/swagger-ui/commit/3f4cae3334fdd492a373f4453bd03a9ebd87becf'} | {'https://github.com/swagger-api/swagger-ui/commit/3f4cae3334fdd492a373f4453bd03a9ebd87becf'} |
npm | GHSA-jcpv-g9rr-qxrc | Regular Expression Denial of Service in hawk | Versions of `hawk` prior to 3.1.3, or 4.x prior to 4.1.1 are affected by a regular expression denial of service vulnerability related to excessively long headers and URI's.
## Recommendation
Update to hawk version 4.1.1 or later. | {'CVE-2016-2515'} | 2021-09-14T19:39:20Z | 2018-07-31T22:52:00Z | HIGH | null | null | {'https://github.com/advisories/GHSA-jcpv-g9rr-qxrc', 'https://github.com/hueniverse/hawk/commit/0833f99ba64558525995a7e21d4093da1f3e15fa', 'https://github.com/hueniverse/hawk', 'https://bugzilla.redhat.com/show_bug.cgi?id=1309721', 'https://nvd.nist.gov/vuln/detail/CVE-2016-2515', 'https://nodesecurity.io/advisories/77', 'https://github.com/hueniverse/hawk/issues/168', 'http://www.openwall.com/lists/oss-security/2016/02/20/1', 'http://www.openwall.com/lists/oss-security/2016/02/20/2', 'https://www.npmjs.com/advisories/77'} | null | {'https://github.com/hueniverse/hawk/commit/0833f99ba64558525995a7e21d4093da1f3e15fa'} | {'https://github.com/hueniverse/hawk/commit/0833f99ba64558525995a7e21d4093da1f3e15fa'} |
npm | GHSA-6rv4-4qv6-88g2 | Prototype Pollution in set-or-get | Prototype pollution vulnerability in ‘set-or-get’ version 1.0.0 through 1.2.10 allows an attacker to cause a denial of service and may lead to remote code execution. | {'CVE-2021-25913'} | 2021-04-12T17:39:01Z | 2021-04-12T17:39:19Z | CRITICAL | null | {'CWE-1321'} | {'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25913', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25913', 'https://github.com/IonicaBizau/set-or-get.js/commit/82ede5cccb2e8d13e4f62599203a4389f6d8e936', 'https://www.npmjs.com/package/set-or-get'} | null | {'https://github.com/IonicaBizau/set-or-get.js/commit/82ede5cccb2e8d13e4f62599203a4389f6d8e936'} | {'https://github.com/IonicaBizau/set-or-get.js/commit/82ede5cccb2e8d13e4f62599203a4389f6d8e936'} |
npm | GHSA-84g3-cv89-m9gm | Prototype pollution vulnerability in 'patchmerge' | Prototype pollution vulnerability in 'patchmerge' versions 1.0.0 through 1.0.1 allows an attacker to cause a denial of service and may lead to remote code execution. | {'CVE-2021-25916'} | 2021-10-06T22:34:42Z | 2021-10-13T15:33:20Z | CRITICAL | null | {'CWE-1321'} | {'https://github.com/pjshumphreys/patchmerge/commit/5b383c537eae7a00ebd26d3f7211dac99ddecb12', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25916', 'https://github.com/pjshumphreys/patchmerge', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25916'} | null | {'https://github.com/pjshumphreys/patchmerge/commit/5b383c537eae7a00ebd26d3f7211dac99ddecb12'} | {'https://github.com/pjshumphreys/patchmerge/commit/5b383c537eae7a00ebd26d3f7211dac99ddecb12'} |
npm | GHSA-pgcr-7wm4-mcv6 | Sensitive Data Exposure in pem | Versions of `pem` before 1.13.2 expose sensitive data when the `readPkcs12` is used.
The `readPkcs12` function reads the certificate and key data from a pkcs12 file using the encryption password. As part of this process it creates a globally readable file with a filename of 20 random 0-f characters in the temporary directory containing the password which is then read by OpenSSL. The file containing the password is never cleaned up after it is used giving access to the pkcs12 password to any other users with access to read files from the system.
## Recommendation
Update to version 1.13.2 or later. | null | 2021-08-04T21:28:00Z | 2019-06-04T15:42:45Z | CRITICAL | null | {'CWE-200'} | {'https://github.com/Dexus/pem/pull/217', 'https://snyk.io/vuln/SNYK-JS-PEM-173687', 'https://www.npmjs.com/advisories/723', 'https://github.com/Dexus/pem/commit/bed1190e4a08692ac903ae6043489f1f76bc67eb'} | null | {'https://github.com/Dexus/pem/commit/bed1190e4a08692ac903ae6043489f1f76bc67eb'} | {'https://github.com/Dexus/pem/commit/bed1190e4a08692ac903ae6043489f1f76bc67eb'} |
npm | GHSA-cxm3-v4mv-6mh8 | Cross-site Scripting in vditor | vditor does not filter user input | {'CVE-2021-4103'} | 2022-01-28T21:55:58Z | 2022-01-28T22:04:11Z | MODERATE | null | {'CWE-79'} | {'https://github.com/vanessa219/vditor/commit/8d4d0889dd72b2f839e93a49db3da3a370416c7d', 'https://github.com/vanessa219/vditor', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4103', 'https://huntr.dev/bounties/67b980af-7357-4879-9448-a926c6474225', 'https://github.com/Vanessa219/vditor/issues/1133'} | null | {'https://github.com/vanessa219/vditor/commit/8d4d0889dd72b2f839e93a49db3da3a370416c7d'} | {'https://github.com/vanessa219/vditor/commit/8d4d0889dd72b2f839e93a49db3da3a370416c7d'} |
npm | GHSA-8mrf-64fw-2x75 | Command injection in fs-path | fs-path node module before 0.0.25 is vulnerable to command injection by way of user-supplied inputs via the `copy`, `copySync`, `remove`, and `removeSync` methods. | {'CVE-2020-8298'} | 2021-03-25T21:05:18Z | 2021-03-25T21:06:41Z | CRITICAL | null | {'CWE-77'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-8298', 'https://hackerone.com/reports/324491', 'https://github.com/pillys/fs-path/pull/6', 'https://github.com/pillys/fs-path/commit/88ff5ee51046bb2c5d5e9c5afe6819b032092ce7'} | null | {'https://github.com/pillys/fs-path/commit/88ff5ee51046bb2c5d5e9c5afe6819b032092ce7'} | {'https://github.com/pillys/fs-path/commit/88ff5ee51046bb2c5d5e9c5afe6819b032092ce7'} |
npm | GHSA-xfhh-g9f5-x4m4 | Resource exhaustion in socket.io-parser | The `socket.io-parser` npm package before versions 3.3.2 and 3.4.1 allows attackers to cause a denial of service (memory consumption) via a large packet because a concatenation approach is used. | {'CVE-2020-36049'} | 2021-06-30T16:53:56Z | 2021-06-30T16:51:31Z | HIGH | null | {'CWE-400'} | {'https://github.com/socketio/socket.io-parser/commit/dcb942d24db97162ad16a67c2a0cf30875342d55', 'https://github.com/bcaller/kill-engine-io', 'https://github.com/socketio/socket.io-parser/releases/tag/3.4.1', 'https://blog.caller.xyz/socketio-engineio-dos/', 'https://github.com/socketio/socket.io-parser/releases/tag/3.3.2', 'https://www.npmjs.com/package/socket.io-parser', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36049'} | null | {'https://github.com/socketio/socket.io-parser/commit/dcb942d24db97162ad16a67c2a0cf30875342d55'} | {'https://github.com/socketio/socket.io-parser/commit/dcb942d24db97162ad16a67c2a0cf30875342d55'} |
npm | GHSA-8g7p-74h8-hg48 | Denial of Service in https-proxy-agent | Versions of `https-proxy-agent` before 2.2.0 are vulnerable to denial of service. This is due to unsanitized options (proxy.auth) being passed to `Buffer()`.
## Recommendation
Update to version 2.2.0 or later. | {'CVE-2018-3739'} | 2021-09-07T19:45:18Z | 2018-07-27T17:04:52Z | CRITICAL | null | {'CWE-400', 'CWE-125'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-3736', 'https://www.npmjs.com/advisories/593', 'https://github.com/TooTallNate/node-https-proxy-agent/commit/1c24219df87524e6ed973127e81f30801d658f07', 'https://github.com/advisories/GHSA-8g7p-74h8-hg48', 'https://github.com/TooTallNate/node-https-proxy-agent', 'https://hackerone.com/reports/319532'} | null | {'https://github.com/TooTallNate/node-https-proxy-agent/commit/1c24219df87524e6ed973127e81f30801d658f07'} | {'https://github.com/TooTallNate/node-https-proxy-agent/commit/1c24219df87524e6ed973127e81f30801d658f07'} |
npm | GHSA-qxg5-2qff-p49r | Passing in a non-string 'html' argument can lead to unsanitized output | A type-confusion vulnerability can cause `striptags` to concatenate unsanitized strings when an array-like object is passed in as the `html` parameter. This can be abused by an attacker who can control the shape of their input, e.g. if query parameters are passed directly into the function.
### Impact
XSS
### Patches
`3.2.0`
### Workarounds
Ensure that the `html` parameter is a string before calling the function.
| {'CVE-2021-32696'} | 2021-06-18T19:31:21Z | 2021-06-18T19:31:35Z | MODERATE | null | {'CWE-241', 'CWE-79', 'CWE-843'} | {'https://www.npmjs.com/package/striptags', 'https://github.com/ericnorris/striptags/commit/f252a6b0819499cd65403707ebaf5cc925f2faca', 'https://github.com/ericnorris/striptags/security/advisories/GHSA-qxg5-2qff-p49r', 'https://github.com/ericnorris/striptags/releases/tag/v3.2.0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32696'} | null | {'https://github.com/ericnorris/striptags/commit/f252a6b0819499cd65403707ebaf5cc925f2faca'} | {'https://github.com/ericnorris/striptags/commit/f252a6b0819499cd65403707ebaf5cc925f2faca'} |
npm | GHSA-8v63-cqqc-6r2c | Prototype Pollution in object-path | object-path is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') | {'CVE-2021-3805'} | 2021-09-20T20:13:12Z | 2021-09-20T20:46:43Z | HIGH | null | {'CWE-915', 'CWE-1321'} | {'https://github.com/mariocasciaro/object-path/commit/4f0903fd7c832d12ccbe0d9c3d7e25d985e9e884', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3805', 'https://huntr.dev/bounties/571e3baf-7c46-46e3-9003-ba7e4e623053', 'https://github.com/mariocasciaro/object-path'} | null | {'https://github.com/mariocasciaro/object-path/commit/4f0903fd7c832d12ccbe0d9c3d7e25d985e9e884'} | {'https://github.com/mariocasciaro/object-path/commit/4f0903fd7c832d12ccbe0d9c3d7e25d985e9e884'} |
npm | GHSA-w7q9-p3jq-fmhm | Uncontrolled resource consumption in jpeg-js | Uncontrolled resource consumption in `jpeg-js` before 0.4.0 may allow attacker to launch denial of service attacks using specially a crafted JPEG image. | {'CVE-2020-8175'} | 2020-07-27T15:48:40Z | 2020-07-27T15:46:57Z | MODERATE | null | {'CWE-400'} | {'https://github.com/eugeneware/jpeg-js/commit/135705b1510afb6cb4275a4655d92c58f6843e79', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8175', 'https://hackerone.com/reports/842462'} | null | {'https://github.com/eugeneware/jpeg-js/commit/135705b1510afb6cb4275a4655d92c58f6843e79'} | {'https://github.com/eugeneware/jpeg-js/commit/135705b1510afb6cb4275a4655d92c58f6843e79'} |
npm | GHSA-h47j-hc6x-h3qq | Remote Code Execution Vulnerability in NPM mongo-express | ### Impact
Remote code execution on the host machine by any authenticated user.
### Proof Of Concept
Launching mongo-express on a Mac, pasting the following into the "create index" field will pop open the Mac calculator:
```javascript
this.constructor.constructor("return process")().mainModule.require('child_process').execSync('/Applications/Calculator.app/Contents/MacOS/Calculator')
```
### Patches
Users should upgrade to version `0.54.0`
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
### References
[Snyk Security Advisory](https://snyk.io/vuln/SNYK-JS-MONGOEXPRESS-473215)
[CVE](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10758)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [example link to repo](http://example.com)
* Email us at [example email address](mailto:example@example.com)
#### Thanks
@JLLeitschuh for finding and reporting this vulnerability | {'CVE-2019-10758'} | 2019-12-30T19:29:02Z | 2019-12-30T19:30:31Z | HIGH | null | null | {'https://nvd.nist.gov/vuln/detail/CVE-2019-10758', 'https://github.com/mongo-express/mongo-express/commit/7d365141deadbd38fa961cd835ce68eab5731494', 'https://github.com/mongo-express/mongo-express/security/advisories/GHSA-h47j-hc6x-h3qq', 'https://snyk.io/vuln/SNYK-JS-MONGOEXPRESS-473215', 'https://github.com/mongo-express/mongo-express/pull/522'} | null | {'https://github.com/mongo-express/mongo-express/commit/7d365141deadbd38fa961cd835ce68eab5731494'} | {'https://github.com/mongo-express/mongo-express/commit/7d365141deadbd38fa961cd835ce68eab5731494'} |
npm | GHSA-pjh3-jv7w-9jpr | Command Injection in gm | Versions of `gm` prior to 1.21.1 are affected by a command injection vulnerability. The vulnerability is triggered when user input is passed into `gm.compare()`, which fails to sanitize input correctly before calling the graphics magic binary.
## Recommendation
Update to version 1.21.1 or later. | {'CVE-2015-7982'} | 2021-09-23T21:23:47Z | 2020-09-01T15:18:55Z | CRITICAL | null | {'CWE-77'} | {'https://github.com/aheckmann/gm/commit/5f5c77490aa84ed313405c88905eb4566135be31', 'https://github.com/aheckmann/gm', 'https://www.npmjs.com/advisories/54', 'https://nvd.nist.gov/vuln/detail/CVE-2015-7982'} | null | {'https://github.com/aheckmann/gm/commit/5f5c77490aa84ed313405c88905eb4566135be31'} | {'https://github.com/aheckmann/gm/commit/5f5c77490aa84ed313405c88905eb4566135be31'} |
npm | GHSA-4fc4-4p5g-6w89 | Cross-site Scripting in CKEditor4 | ### Affected packages
The vulnerability has been discovered in the core HTML processing module and may affect all plugins used by CKEditor 4.
### Impact
A potential vulnerability has been discovered in CKEditor 4 HTML processing core module. The vulnerability allowed to inject malformed HTML bypassing content sanitization, which could result in executing JavaScript code. It affects all users using the CKEditor 4 at version < 4.18.0.
### Patches
The problem has been recognized and patched. The fix will be available in version 4.18.0.
### For more information
Email us at security@cksource.com if you have any questions or comments about this advisory.
### Acknowledgements
The CKEditor 4 team would like to thank GHSL team member Kevin Backhouse ([@kevinbackhouse](https://github.com/kevinbackhouse)) for recognizing and reporting this vulnerability. | {'CVE-2022-24728'} | 2022-03-30T20:05:59Z | 2022-03-16T22:47:55Z | MODERATE | null | {'CWE-79'} | {'https://securitylab.github.com/advisories/GHSL-2022-009_ckeditor4/', 'https://github.com/ckeditor/ckeditor4/commit/d158413449692d920a778503502dcb22881bc949', 'https://ckeditor.com/cke4/release/CKEditor-4.18.0', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24728', 'https://github.com/ckeditor/ckeditor4/security/advisories/GHSA-4fc4-4p5g-6w89', 'https://github.com/ckeditor/ckeditor4', 'https://www.drupal.org/sa-core-2022-005'} | null | {'https://github.com/ckeditor/ckeditor4/commit/d158413449692d920a778503502dcb22881bc949'} | {'https://github.com/ckeditor/ckeditor4/commit/d158413449692d920a778503502dcb22881bc949'} |
npm | GHSA-49rv-g7w5-m8xx | Cross-Site Scripting in @novnc/novnc | Versions of `@novnc/novnc` prior to 0.6.2 are vulnerable to Cross-Site Scripting (XSS). The package fails to validate input from the remote VNC server such as the VNC server name. This allows an attacker in control of the remote server to execute arbitrary JavaScript in the noVNC web page. It affects any users of `include/ui.js` and users of `vnc_auto.html` and `vnc.html`.
## Recommendation
Upgrade to version 0.6.2 or later. | {'CVE-2017-18635'} | 2021-09-23T19:08:01Z | 2020-08-28T21:24:59Z | MODERATE | null | {'CWE-79'} | {'https://lists.debian.org/debian-lts-announce/2021/12/msg00024.html', 'https://github.com/novnc/noVNC/commit/6048299a138e078aed210f163111698c8c526a13#diff-286f7dc7b881e942e97cd50c10898f03L534', 'https://github.com/novnc/noVNC/issues/748', 'https://access.redhat.com/errata/RHSA-2020:0754', 'https://www.shielder.it/blog/exploiting-an-old-novnc-xss-cve-2017-18635-in-openstack/', 'https://www.npmjs.com/advisories/1204', 'https://lists.debian.org/debian-lts-announce/2019/10/msg00004.html', 'https://bugs.launchpad.net/horizon/+bug/1656435', 'https://github.com/novnc/noVNC', 'https://snyk.io/vuln/SNYK-JS-NOVNCNOVNC-469136', 'https://github.com/novnc/noVNC/releases/tag/v0.6.2', 'https://usn.ubuntu.com/4522-1/', 'https://nvd.nist.gov/vuln/detail/CVE-2017-18635', 'https://github.com/ShielderSec/cve-2017-18635'} | null | {'https://github.com/novnc/noVNC/commit/6048299a138e078aed210f163111698c8c526a13#diff-286f7dc7b881e942e97cd50c10898f03L534'} | {'https://github.com/novnc/noVNC/commit/6048299a138e078aed210f163111698c8c526a13#diff-286f7dc7b881e942e97cd50c10898f03L534'} |
npm | GHSA-xwg4-93c6-3h42 | Directory Traversal in send | Versions 0.8.3 and earlier of `send` are affected by a directory traversal vulnerability. When relying on the root option to restrict file access it may be possible for an application consumer to escape out of the restricted directory and access files in a similarly named directory.
For example, `static(_dirname + '/public')` would allow access to `_dirname + '/public-restricted'`.
## Recommendation
Update to version 0.8.4 or later. | {'CVE-2014-6394'} | 2021-09-22T17:58:56Z | 2017-10-24T18:33:36Z | LOW | null | {'CWE-22'} | {'https://github.com/advisories/GHSA-xwg4-93c6-3h42', 'https://github.com/visionmedia/send/commit/9c6ca9b2c0b880afd3ff91ce0d211213c5fa5f9a', 'http://www.securityfocus.com/bid/70100', 'http://lists.fedoraproject.org/pipermail/package-announce/2014-October/140020.html', 'https://bugzilla.redhat.com/show_bug.cgi?id=1146063', 'https://github.com/visionmedia/send', 'http://lists.apple.com/archives/security-announce/2015/Sep/msg00002.html', 'http://www.openwall.com/lists/oss-security/2014/09/30/10', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/96727', 'https://nodesecurity.io/advisories/send-directory-traversal', 'https://support.apple.com/HT205217', 'http://lists.fedoraproject.org/pipermail/package-announce/2014-October/139938.html', 'https://nvd.nist.gov/vuln/detail/CVE-2014-6394', 'https://www.npmjs.com/advisories/32', 'http://www-01.ibm.com/support/docview.wss?uid=swg21687263', 'http://secunia.com/advisories/62170', 'http://lists.fedoraproject.org/pipermail/package-announce/2014-September/139415.html', 'https://github.com/visionmedia/send/pull/59', 'http://www.openwall.com/lists/oss-security/2014/09/24/1'} | null | {'https://github.com/visionmedia/send/commit/9c6ca9b2c0b880afd3ff91ce0d211213c5fa5f9a'} | {'https://github.com/visionmedia/send/commit/9c6ca9b2c0b880afd3ff91ce0d211213c5fa5f9a'} |
npm | GHSA-r5cq-9537-9rpf | Prototype Pollution in mixme | Node.js mixme 0.5.0, an attacker can add or alter properties of an object via '__proto__' through the mutate() and merge() functions. The polluted attribute will be directly assigned to every object in the program. This will put the availability of the program at risk causing a potential denial of service (DoS). | {'CVE-2021-28860'} | 2021-12-13T21:33:52Z | 2022-02-10T23:52:01Z | CRITICAL | null | {'CWE-1321'} | {'https://github.com/adaltas/node-mixme/issues/1', 'https://www.npmjs.com/~david', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28860', 'https://github.com/adaltas/node-mixme/commit/cfd5fbfc32368bcf7e06d1c5985ea60e34cd4028', 'https://github.com/adaltas/node-mixme', 'https://github.com/adaltas/node-mixme/security/advisories/GHSA-79jw-6wg7-r9g4', 'http://nodejs.com', 'https://security.netapp.com/advisory/ntap-20210618-0005/'} | null | {'https://github.com/adaltas/node-mixme/commit/cfd5fbfc32368bcf7e06d1c5985ea60e34cd4028'} | {'https://github.com/adaltas/node-mixme/commit/cfd5fbfc32368bcf7e06d1c5985ea60e34cd4028'} |
npm | GHSA-7c7g-72q7-4xhm | Prototype pollution vulnerability in 'deepref' | Prototype pollution vulnerability in 'deepref' versions 1.1.1 through 1.2.1 allows attacker to cause a denial of service and may lead to remote code execution. | {'CVE-2020-28274'} | 2021-10-08T22:15:48Z | 2021-10-12T16:27:35Z | CRITICAL | null | null | {'https://github.com/isaymatato/deepref', 'https://github.com/isaymatato/deepref/commit/24935e6a1060cb09c641d3075982f0b44cfca4c2', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28274', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2020-28274'} | null | {'https://github.com/isaymatato/deepref/commit/24935e6a1060cb09c641d3075982f0b44cfca4c2'} | {'https://github.com/isaymatato/deepref/commit/24935e6a1060cb09c641d3075982f0b44cfca4c2'} |
npm | GHSA-9534-h433-2rjf | Improperly Controlled Modification of Dynamically-Determined Object Attributes in utilitify | utilitify prior to 1.0.3 allows modification of object properties. The merge method could be tricked into adding or modifying properties of the Object.prototype. | {'CVE-2019-10808'} | 2021-07-28T18:40:29Z | 2021-05-07T16:28:47Z | HIGH | null | {'CWE-915'} | {'https://snyk.io/vuln/SNYK-JS-UTILITIFY-559497', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10808', 'https://github.com/xcritical-software/utilitify/commit/88d6e27009823338bf319ffb768fe6b08e8ad2d1,'} | null | {'https://github.com/xcritical-software/utilitify/commit/88d6e27009823338bf319ffb768fe6b08e8ad2d1,'} | {'https://github.com/xcritical-software/utilitify/commit/88d6e27009823338bf319ffb768fe6b08e8ad2d1,'} |
npm | GHSA-3329-pjwv-fjpg | Hostname spoofing via backslashes in URL | ### Impact
If using affected versions to determine a URL's hostname, the hostname can be spoofed by using a backslash (`\`) character followed by an at (`@`) character. If the hostname is used in security decisions, the decision may be incorrect.
Depending on library usage and attacker intent, impacts may include allow/block list bypasses, SSRF attacks, open redirects, or other undesired behavior.
Example URL: `https://expected-example.com\@observed-example.com`
Escaped string: `https://expected-example.com\\@observed-example.com` (JavaScript strings must escape backslash)
Affected versions incorrectly return `observed-example.com`. Patched versions correctly return `expected-example.com`. Patched versions match the behavior of other parsers which implement the [WHATWG URL specification](https://url.spec.whatwg.org/), including web browsers and [Node's built-in URL class](https://nodejs.org/api/url.html).
### Patches
Version 1.19.4 is patched against all known payload variants. Version 1.19.3 has a partial patch but is still vulnerable to a payload variant.
### References
https://github.com/medialize/URI.js/releases/tag/v1.19.4 (complete fix for this bypass)
https://github.com/medialize/URI.js/releases/tag/v1.19.3 (partial fix for this bypass)
[PR #233](https://github.com/medialize/URI.js/pull/233) (initial fix for backslash handling)
### For more information
If you have any questions or comments about this advisory, open an issue in https://github.com/medialize/URI.js
### Reporter credit
[Alesandro Ortiz](https://AlesandroOrtiz.com) | {'CVE-2020-26291'} | 2021-01-08T20:55:21Z | 2020-12-30T23:40:48Z | MODERATE | null | {'CWE-20'} | {'https://www.npmjs.com/package/urijs', 'https://github.com/medialize/URI.js/commit/b02bf037c99ac9316b77ff8bfd840e90becf1155', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26291', 'https://github.com/medialize/URI.js/releases/tag/v1.19.4', 'https://www.npmjs.com/advisories/1595', 'https://github.com/medialize/URI.js/security/advisories/GHSA-3329-pjwv-fjpg'} | null | {'https://github.com/medialize/URI.js/commit/b02bf037c99ac9316b77ff8bfd840e90becf1155'} | {'https://github.com/medialize/URI.js/commit/b02bf037c99ac9316b77ff8bfd840e90becf1155'} |
npm | GHSA-vgrx-w6rg-8fqf | Forgeable Public/Private Tokens in jwt-simple | Affected versions of the `jwt-simple` package allow users to select what algorithm the server will use to verify a provided JWT. A malicious actor can use this behaviour to arbitrarily modify the contents of a JWT while still passing verification. For the common use case of the JWT, the end result is a complete authentication bypass with minimal effort.
## Recommendation
Update to version 0.3.1 or later.
Additionally, be sure to always specify an algorithm in calls to `.decode()`. | {'CVE-2016-10555'} | 2020-08-31T18:10:20Z | 2018-11-06T23:12:07Z | CRITICAL | null | {'CWE-20'} | {'https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/', 'https://github.com/hokaccha/node-jwt-simple/commit/957957cfa44474049b4603b293569588ee9ffd97', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10555', 'https://www.npmjs.com/advisories/87', 'https://github.com/hokaccha/node-jwt-simple/pull/16', 'https://github.com/hokaccha/node-jwt-simple/pull/14', 'https://nodesecurity.io/advisories/87'} | null | {'https://github.com/hokaccha/node-jwt-simple/commit/957957cfa44474049b4603b293569588ee9ffd97'} | {'https://github.com/hokaccha/node-jwt-simple/commit/957957cfa44474049b4603b293569588ee9ffd97'} |
npm | GHSA-7x7c-qm48-pq9c | Cross-site Scripting in karma | karma prior to version 6.3.14 contains a cross-site scripting vulnerability. | {'CVE-2022-0437'} | 2022-02-11T19:59:48Z | 2022-02-06T00:00:54Z | MODERATE | null | {'CWE-79'} | {'https://github.com/karma-runner/karma/releases/tag/v6.3.14', 'https://huntr.dev/bounties/64b67ea1-5487-4382-a5f6-e8a95f798885', 'https://github.com/karma-runner/karma/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0437', 'https://github.com/karma-runner/karma/commit/839578c45a8ac42fbc1d72105f97eab77dd3eb8a'} | null | {'https://github.com/karma-runner/karma/commit/839578c45a8ac42fbc1d72105f97eab77dd3eb8a'} | {'https://github.com/karma-runner/karma/commit/839578c45a8ac42fbc1d72105f97eab77dd3eb8a'} |
npm | GHSA-qm28-7hqv-wg5j | OS Command Injection in ng-packagr | The package ng-packagr before 10.1.1 are vulnerable to Command Injection via the styleIncludePaths option. | {'CVE-2020-7735'} | 2021-10-05T16:28:05Z | 2021-05-07T16:47:32Z | MODERATE | null | {'CWE-78'} | {'https://snyk.io/vuln/SNYK-JS-NGPACKAGR-1012427', 'https://github.com/ng-packagr/ng-packagr', 'https://github.com/ng-packagr/ng-packagr/commit/bda0fff3443301f252930a73fdc8fb9502de596d', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7735'} | null | {'https://github.com/ng-packagr/ng-packagr/commit/bda0fff3443301f252930a73fdc8fb9502de596d'} | {'https://github.com/ng-packagr/ng-packagr/commit/bda0fff3443301f252930a73fdc8fb9502de596d'} |
npm | GHSA-vwjj-2852-3765 | Cross-Site Scripting in forms | Affected versions of `forms` do not properly escape HTML in generated forms, which may result in cross-site scripting.
## Recommendation
Update to version 1.3.0 or later. | {'CVE-2017-16015'} | 2020-08-31T18:12:53Z | 2018-11-09T17:46:27Z | MODERATE | null | {'CWE-80'} | {'https://github.com/advisories/GHSA-vwjj-2852-3765', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16015', 'https://www.npmjs.com/advisories/158', 'https://nodesecurity.io/advisories/158', 'https://github.com/caolan/forms/commit/bc01e534a0ff863dedb2026a50bd03153bbc6a5d'} | null | {'https://github.com/caolan/forms/commit/bc01e534a0ff863dedb2026a50bd03153bbc6a5d'} | {'https://github.com/caolan/forms/commit/bc01e534a0ff863dedb2026a50bd03153bbc6a5d'} |
npm | GHSA-gpqq-952q-5327 | XSS in the `of` option of the `.position()` util in jquery-ui | ### Impact
Accepting the value of the `of` option of the [`.position()`](https://api.jqueryui.com/position/) util from untrusted sources may execute untrusted code. For example, invoking the following code:
```js
$( "#element" ).position( {
my: "left top",
at: "right bottom",
of: "<img onerror='window.globalOf=true' src='/404' />",
collision: "none"
} );
```
will call the `doEvilThing()` function.
### Patches
The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `of` option is now treated as a CSS selector.
### Workarounds
A workaround is to not accept the value of the `of` option from untrusted sources.
### For more information
If you have any questions or comments about this advisory, search for a relevant issue in [the jQuery UI repo](https://github.com/jquery/jquery-ui/issues). If you don't find an answer, open a new issue. | {'CVE-2021-41184'} | 2021-10-27T16:59:45Z | 2021-10-26T14:55:12Z | MODERATE | null | {'CWE-79'} | {'https://github.com/jquery/jquery-ui/commit/effa323f1505f2ce7a324e4f429fa9032c72f280', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NXIUUBRVLA4E7G7MMIKCEN75YN7UFERW/', 'https://github.com/jquery/jquery-ui', 'https://security.netapp.com/advisory/ntap-20211118-0004/', 'https://www.drupal.org/sa-core-2022-001', 'https://blog.jqueryui.com/2021/10/jquery-ui-1-13-0-released/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41184', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/O74SXYY7RGXREQDQUDQD4BPJ4QQTD2XQ/', 'https://www.tenable.com/security/tns-2022-09', 'https://github.com/jquery/jquery-ui/security/advisories/GHSA-gpqq-952q-5327', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SNXA7XRKGINWSUIPIZ6ZBCTV6N3KSHES/'} | null | {'https://github.com/jquery/jquery-ui/commit/effa323f1505f2ce7a324e4f429fa9032c72f280'} | {'https://github.com/jquery/jquery-ui/commit/effa323f1505f2ce7a324e4f429fa9032c72f280'} |
npm | GHSA-qmm9-x5gr-4gfm | Open Redirect in hekto | Versions of `hekto` before 0.2.4 are vulnerable to open redirect when a domain name is used as part of the `.html` filename.
## Recommendation
Update to version 0.2.4 or later. | {'CVE-2018-3743'} | 2020-08-31T18:32:05Z | 2018-07-18T21:20:12Z | LOW | null | {'CWE-601'} | {'https://github.com/herber/hekto/commit/1e5c75f8259ba0daf9b2600db3c246cda1934c46', 'https://github.com/advisories/GHSA-qmm9-x5gr-4gfm', 'https://github.com/herber/hekto/pull/3', 'https://www.npmjs.com/advisories/669', 'https://hackerone.com/reports/320693', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3743'} | null | {'https://github.com/herber/hekto/commit/1e5c75f8259ba0daf9b2600db3c246cda1934c46'} | {'https://github.com/herber/hekto/commit/1e5c75f8259ba0daf9b2600db3c246cda1934c46'} |
npm | GHSA-2pqj-h3vj-pqgw | Cross-Site Scripting in jquery | Affected versions of `jquery` are vulnerable to cross-site scripting. This occurs because the main `jquery` function uses a regular expression to differentiate between HTML and selectors, but does not properly anchor the regular expression. The result is that `jquery` may interpret HTML as selectors when given certain inputs, allowing for client side code execution.
## Proof of Concept
```
$("#log").html(
$("element[attribute='<img src=\"x\" onerror=\"alert(1)\" />']").html()
);
```
## Recommendation
Update to version 1.9.0 or later. | {'CVE-2012-6708'} | 2022-03-03T05:13:33.982770Z | 2020-09-01T16:41:46Z | HIGH | null | {'CWE-79', 'CWE-64'} | {'http://packetstormsecurity.com/files/161972/Linksys-EA7500-2.0.8.194281-Cross-Site-Scripting.html', 'https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@%3Cdev.drill.apache.org%3E', 'https://github.com/jquery/jquery/commit/05531fc4080ae24070930d15ae0cea7ae056457d', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16011', 'http://packetstormsecurity.com/files/153237/RetireJS-CORS-Issue-Script-Execution.html', 'https://help.ecostruxureit.com/display/public/UADCE725/Security+fixes+in+StruxureWare+Data+Center+Expert+v7.6.0', 'https://bugs.jquery.com/ticket/11290', 'https://nvd.nist.gov/vuln/detail/CVE-2012-6708', 'https://snyk.io/vuln/npm:jquery:20120206', 'https://bugs.jquery.com/ticket/12531', 'https://bugs.jquery.com/ticket/6429', 'http://www.securityfocus.com/bid/102792', 'https://www.npmjs.com/advisories/329', 'https://bugs.jquery.com/ticket/9521', 'http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00041.html'} | null | {'https://github.com/jquery/jquery/commit/05531fc4080ae24070930d15ae0cea7ae056457d'} | {'https://github.com/jquery/jquery/commit/05531fc4080ae24070930d15ae0cea7ae056457d'} |
npm | GHSA-r92x-f52r-x54g | regular expression denial of service (ReDoS) | date-and-time is an npm package for manipulating date and time. In date-and-time before version 0.14.2, there a regular expression involved in parsing which can be exploited to to cause a denial of service. This is fixed in version 0.14.2. | {'CVE-2020-26289'} | 2021-01-07T22:33:12Z | 2020-12-24T20:49:02Z | HIGH | null | {'CWE-400'} | {'https://github.com/knowledgecode/date-and-time/security/advisories/GHSA-r92x-f52r-x54g', 'https://github.com/knowledgecode/date-and-time/commit/9e4b501eacddccc8b1f559fb414f48472ee17c2a', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26289', 'https://www.npmjs.com/package/date-and-time', 'https://www.npmjs.com/advisories/1592'} | null | {'https://github.com/knowledgecode/date-and-time/commit/9e4b501eacddccc8b1f559fb414f48472ee17c2a'} | {'https://github.com/knowledgecode/date-and-time/commit/9e4b501eacddccc8b1f559fb414f48472ee17c2a'} |
npm | GHSA-xh2p-7p87-fhgh | Incorrect TCR calculation in batchLiquidateTroves() during Recovery Mode | TCR is temporarily miscalculated in the `batchLiquidateTroves` function during Recovery Mode.
The bug lies in [`batchLiquidateTroves` of `TroveManager`](https://github.com/liquity/dev/blob/7c83ea11378454629618b3808b16fbfda69ee3e5/packages/contracts/contracts/TroveManager.sol#L722).
When calculating system's entire collateral, we should also exclude the liquidated trove's surplus collateral, since liquidation closes the trove and makes the surplus collateral claimable by the trove owner. This means, this line of code should look like this:
```
vars.entireSystemColl = vars.entireSystemColl.sub(singleLiquidation.collToSendToSP).sub(singleLiquidation.collSurplus);
```
### Impact
The miscalculated entire collateral is used only to calculate the TCR and check if the system has been able to exit Recovery Mode. The miscalulation only persists temporarily, and within the`batchLiquidateTroves` transaction. Once the transaction completes the TCR and Recovery Mode will be calculated properly again. However, the bug could negatively impact the liquidation throughput and the gas efficiency gains from batching multiple liquidations in a single transaction.
In normal situations, the impact of the collateral surplus of a Trove on the global TCR would be tiny. For instance, we have calculated that liquidating a trove with a collateral representing 1% of the total system collateral (so in the order of at least $10M at current values), would lead to an extra 0.53% in the temporary miscalculation of TCR. So for this bug to be meaningful, in such a scenario, the resulting real TCR must be already be very close to the Recovery Mode boundary anyway - i.e. between 149.47% and 150%. The batch liquidation transaction should also be executed with a particular trove ordering to achieve the TCR distortion. When a different trove order for the liquidation transaction is selected, the bug has no impact. In summary, the bug only has a non-negligible impact in a very narrow, specific set of circumstances.
The potential effects of the bug after it occurs are:
- The next trove in the sequence is not liquidated because the `batchLiquidateTroves` function calculates a premature exit from Recovery Mode. It could be liquidated in a subsequent transaction if the price of Ether doesn’t recover.
- The next trove in the sequence has an ICR below 100% and it’s offset against the Stability Pool instead of redistributed among other troves because the function calculates a premature exit from Recovery Mode. For this to happen, the Ether price must have instantly plummeted by more than 10% (otherwise, the trove would have been already liquidated before).
- The next trove in the sequence is liquidated while its ICR is over the real TCR: the function calculates the TCR as being slightly too high, and thus can liquidate a trove that has ICR less than the calculated TCR, but greater than the true TCR. This is probably the worst outcome - however it is already possible to achieve the same effect, regardless of the bug. A liquidator can craft a `batchLiquidateTroves` transaction whereby they select troves for liquidation such that the TCR increases and makes a given trove liquidateable. To liquidate trove A, they can order troves such that they first liquidate troves which raise the TCR to between A's ICR and 150%. This is intended and expected behavior. As clearly stated in Liquity documentation, to be completely safe and guarantee immunity from liquidation in Recovery Mode, borrowers should keep their ICR above 150%.
We don't believe this bug creates a profitable exploit. Theoretically, and only in a very narrow set of circumstances, a liquidator could try to send a batch liquidation during Recovery Mode that lets the system very temporarily return to Normal Mode earlier than it should. In that case - _and only if the Ether price also happens to suddenly plummet by more than 10%_ - stability providers might take the haircut that should be taken by the borrowers (through redistribution).
### Patches
The problem has been patched in the source code but not on mainnet contracts. Liquity protocol is immutable, and this issue is not critical, so it doesn't merit a launch of a new version.
### Bug bounty
A reward of $1,000 (the maximum for its category) was awarded to Xiahong (`gaoxh06`) for reporting this bug.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [our repo](https://github.com/liquity/dev)
* Email us at [security@liquity.org](mailto:security@liquity.org)
| null | 2021-07-29T20:43:48Z | 2021-08-05T16:56:58Z | LOW | null | {'CWE-682'} | {'https://github.com/liquity/dev/commit/c69d0bae30b5457e89724d880851a03ba7477905', 'https://github.com/liquity/dev/blob/7c83ea11378454629618b3808b16fbfda69ee3e5/packages/contracts/contracts/TroveManager.sol#L722', 'https://www.npmjs.com/package/@liquity/contracts', 'https://github.com/liquity/dev/security/advisories/GHSA-xh2p-7p87-fhgh'} | null | {'https://github.com/liquity/dev/commit/c69d0bae30b5457e89724d880851a03ba7477905'} | {'https://github.com/liquity/dev/commit/c69d0bae30b5457e89724d880851a03ba7477905'} |
npm | GHSA-rp2c-jrgp-cvr8 | Code injection in plupload | This affects the package plupload before 2.3.9. A file name containing JavaScript code could be uploaded and run. An attacker would need to trick a user to upload this kind of file. | {'CVE-2021-23562'} | 2021-12-06T22:08:43Z | 2021-12-16T15:32:31Z | MODERATE | null | {'CWE-434', 'CWE-75'} | {'https://github.com/moxiecode/plupload', 'https://github.com/moxiecode/plupload/commit/d12175d4b5fa799b994ee1bb17bfbeec55b386fb', 'https://snyk.io/vuln/SNYK-JS-PLUPLOAD-1583909', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23562', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBMOXIECODE-2306664', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARS-2306665', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-2306663', 'https://github.com/moxiecode/plupload/blob/master/js/jquery.plupload.queue/jquery.plupload.queue.js%23L226'} | null | {'https://github.com/moxiecode/plupload/commit/d12175d4b5fa799b994ee1bb17bfbeec55b386fb'} | {'https://github.com/moxiecode/plupload/commit/d12175d4b5fa799b994ee1bb17bfbeec55b386fb'} |
npm | GHSA-x2w5-725j-gf2g | Prototype Pollution in convict | An attacker can inject attributes that are used in other components and override existing attributes with ones that have incompatible type, which may lead to a crash.
The main use case of Convict is for handling server-side configurations written by the admins owning the servers, and not random users. So it's unlikely that an admin would deliberately sabotage their own server. Still a situation can happen where an admin not knowledgeable about JavaScript could be tricked by an attacker into writing the malicious JavaScript code into some config files.
The problem is patched in `convict@6.2.2`. Users should upgrade to `convict@6.2.2`. There is no way for users to fix or remediate the vulnerability without upgrading. | {'CVE-2022-22143'} | 2022-04-20T16:21:03Z | 2022-04-20T16:21:03Z | HIGH | null | {'CWE-1321'} | {'https://github.com/mozilla/node-convict/blob/5eb1314f85346760a3c31cb14510f2f0af11d0d3/packages/convict/src/main.js%23L569', 'https://github.com/mozilla/node-convict/', 'https://snyk.io/vuln/SNYK-JS-CONVICT-2340604', 'https://www.huntr.dev/bounties/1-npm-convict/', 'https://github.com/mozilla/node-convict/releases/tag/v6.2.2', 'https://github.com/mozilla/node-convict/pull/384', 'https://github.com/mozilla/node-convict/commit/3b86be087d8f14681a9c889d45da7fe3ad9cd880', 'https://github.com/mozilla/node-convict/security/advisories/GHSA-x2w5-725j-gf2g', 'https://nvd.nist.gov/vuln/detail/CVE-2022-22143'} | null | {'https://github.com/mozilla/node-convict/commit/3b86be087d8f14681a9c889d45da7fe3ad9cd880'} | {'https://github.com/mozilla/node-convict/commit/3b86be087d8f14681a9c889d45da7fe3ad9cd880'} |
npm | GHSA-hf2m-j98r-4fqw | API token verification can be bypassed in NodeBB | ### Impact
Incorrect logic present in the token verification step unintentionally allowed master token access to the API.
### Patches
The vulnerability has been patch as of v1.18.5.
### Workarounds
Cherry-pick commit hash 04dab1d550cdebf4c1567bca9a51f8b9ca48a500 to receive this patch in lieu of a full upgrade.
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@nodebb.org](mailto:security@nodebb.org)
| {'CVE-2021-43786'} | 2021-12-01T15:06:58Z | 2021-11-30T22:21:05Z | CRITICAL | null | {'CWE-287'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-43786', 'https://github.com/NodeBB/NodeBB/releases/tag/v1.18.5', 'https://github.com/NodeBB/NodeBB/security/advisories/GHSA-hf2m-j98r-4fqw', 'https://github.com/NodeBB/NodeBB/commit/04dab1d550cdebf4c1567bca9a51f8b9ca48a500', 'https://github.com/NodeBB/NodeBB'} | null | {'https://github.com/NodeBB/NodeBB/commit/04dab1d550cdebf4c1567bca9a51f8b9ca48a500'} | {'https://github.com/NodeBB/NodeBB/commit/04dab1d550cdebf4c1567bca9a51f8b9ca48a500'} |
npm | GHSA-v88g-cgmw-v5xw | Prototype Pollution in Ajv | An issue was discovered in ajv.validate() in Ajv (aka Another JSON Schema Validator) 6.12.2. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code.) | {'CVE-2020-15366'} | 2021-05-10T21:23:41Z | 2022-02-10T23:30:59Z | MODERATE | null | {'CWE-915'} | {'https://github.com/ajv-validator/ajv/commit/65b2f7d76b190ac63a0d4e9154c712d7aa37049f', 'https://hackerone.com/bugs?subject=user&report_id=894259', 'https://github.com/ajv-validator/ajv/releases/tag/v6.12.3', 'https://github.com/ajv-validator/ajv/tags', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15366'} | null | {'https://github.com/ajv-validator/ajv/commit/65b2f7d76b190ac63a0d4e9154c712d7aa37049f'} | {'https://github.com/ajv-validator/ajv/commit/65b2f7d76b190ac63a0d4e9154c712d7aa37049f'} |
npm | GHSA-jxfh-8wgv-vfr2 | Prototype pollution in dojo | In affected versions of dojo (NPM package), the deepCopy method is vulnerable to Prototype Pollution.
Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects.
An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values.
This has been patched in versions 1.12.8, 1.13.7, 1.14.6, 1.15.3 and 1.16.2 | {'CVE-2020-5258'} | 2022-02-08T22:06:45Z | 2020-03-10T18:03:14Z | HIGH | null | {'CWE-74', 'CWE-94', 'CWE-1321'} | {'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://lists.apache.org/thread.html/r665fcc152bd0fec9f71511a6c2435ff24d3a71386b01b1a6df326fd3@%3Cusers.qpid.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2020/03/msg00012.html', 'https://github.com/dojo/dojo/commit/20a00afb68f5587946dc76fbeaa68c39bda2171d', 'https://www.oracle.com/security-alerts/cpujul2020.html', 'https://github.com/dojo/dojo', 'https://lists.apache.org/thread.html/rf481b3f25f05c52ba4e24991a941c1a6e88d281c6c9360a806554d00@%3Cusers.qpid.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://lists.apache.org/thread.html/r3638722360d7ae95f874280518b8d987d799a76df7a9cd78eac33a1b@%3Cusers.qpid.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5258', 'https://github.com/dojo/dojo/security/advisories/GHSA-jxfh-8wgv-vfr2', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/dojo/dojo/commit/20a00afb68f5587946dc76fbeaa68c39bda2171d'} | {'https://github.com/dojo/dojo/commit/20a00afb68f5587946dc76fbeaa68c39bda2171d'} |
npm | GHSA-832h-xg76-4gv6 | ReDoS in brace-expansion | Affected versions of `brace-expansion` are vulnerable to a regular expression denial of service condition.
## Proof of Concept
```
var expand = require('brace-expansion');
expand('{,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,\n}');
```
## Recommendation
Update to version 1.1.7 or later. | {'CVE-2017-18077'} | 2021-09-03T22:10:24Z | 2018-01-29T15:50:46Z | HIGH | null | {'CWE-20'} | {'https://www.npmjs.com/advisories/338', 'https://github.com/juliangruber/brace-expansion/issues/33', 'https://nvd.nist.gov/vuln/detail/CVE-2017-18077', 'https://nodesecurity.io/advisories/338', 'https://github.com/juliangruber/brace-expansion/pull/35/commits/b13381281cead487cbdbfd6a69fb097ea5e456c3', 'https://github.com/juliangruber/brace-expansion/pull/35', 'https://bugs.debian.org/862712', 'https://github.com/juliangruber/brace-expansion', 'https://github.com/advisories/GHSA-832h-xg76-4gv6'} | null | {'https://github.com/juliangruber/brace-expansion/pull/35/commits/b13381281cead487cbdbfd6a69fb097ea5e456c3'} | {'https://github.com/juliangruber/brace-expansion/pull/35/commits/b13381281cead487cbdbfd6a69fb097ea5e456c3'} |
npm | GHSA-5jpf-pj32-xx53 | Authorization header is not sanitized in an error object in auth0 | ### Overview
Versions before and including `2.27.0` use a block list of specific keys that should be sanitized from the request object contained in the error object. When a request to Auth0 management API fails, the key for `Authorization` header is not sanitized and the `Authorization` header value can be logged exposing a bearer token.
### Am I affected?
You are affected by this vulnerability if all of the following conditions apply:
- You are using `auth0` npm package
- You are using a Machine to Machine application authorized to use Auth0's management API https://auth0.com/docs/flows/concepts/client-credentials
### How to fix that?
Upgrade to version `2.27.1`
### Will this update impact my users?
The fix provided in patch will not affect your users.
### Credit
http://github.com/osdiab | {'CVE-2020-15125'} | 2021-01-07T23:44:25Z | 2020-07-29T16:26:22Z | HIGH | null | {'CWE-209'} | {'https://github.com/auth0/node-auth0/tree/v2.27.1', 'https://github.com/auth0/node-auth0/pull/507/commits/62ca61b3348ec8e74d7d00358661af1a8bc98a3c', 'https://github.com/auth0/node-auth0/pull/507', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15125', 'https://github.com/auth0/node-auth0/security/advisories/GHSA-5jpf-pj32-xx53'} | null | {'https://github.com/auth0/node-auth0/pull/507/commits/62ca61b3348ec8e74d7d00358661af1a8bc98a3c'} | {'https://github.com/auth0/node-auth0/pull/507/commits/62ca61b3348ec8e74d7d00358661af1a8bc98a3c'} |
npm | GHSA-43ch-2h55-2vj7 | Server-Side Request Forgery in private-ip | Insufficient RegEx in private-ip npm package v1.0.5 and below insufficiently filters reserved IP ranges resulting in indeterminate SSRF. An attacker can perform a large range of requests to ARIN reserved IP ranges, resulting in an indeterminable number of critical attack vectors, allowing remote attackers to request server-side resources or potentially execute arbitrary code through various SSRF techniques. | {'CVE-2020-28360'} | 2021-03-29T21:49:55Z | 2021-04-13T15:18:17Z | CRITICAL | null | {'CWE-918'} | {'https://github.com/frenchbread/private-ip', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28360', 'https://www.npmjs.com/package/private-ip', 'https://github.com/frenchbread/private-ip/commit/840664c4b9ba7888c41cfee9666e9a593db133e9', 'https://johnjhacking.com/blog/cve-2020-28360/'} | null | {'https://github.com/frenchbread/private-ip/commit/840664c4b9ba7888c41cfee9666e9a593db133e9'} | {'https://github.com/frenchbread/private-ip/commit/840664c4b9ba7888c41cfee9666e9a593db133e9'} |
npm | GHSA-xf7w-r453-m56c | Arbitrary File Overwrite in fstream | Versions of `fstream` prior to 1.0.12 are vulnerable to Arbitrary File Overwrite. Extracting tarballs containing a hardlink to a file that already exists in the system and a file that matches the hardlink will overwrite the system's file with the contents of the extracted file. The `fstream.DirWriter()` function is vulnerable.
## Recommendation
Upgrade to version 1.0.12 or later. | {'CVE-2019-13173'} | 2021-08-04T20:12:16Z | 2019-05-30T17:19:34Z | HIGH | null | {'CWE-59'} | {'https://www.npmjs.com/advisories/886', 'https://github.com/npm/fstream/commit/6a77d2fa6e1462693cf8e46f930da96ec1b0bb22', 'https://nvd.nist.gov/vuln/detail/CVE-2019-13173', 'http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00010.html', 'https://usn.ubuntu.com/4123-1/', 'http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00052.html'} | null | {'https://github.com/npm/fstream/commit/6a77d2fa6e1462693cf8e46f930da96ec1b0bb22'} | {'https://github.com/npm/fstream/commit/6a77d2fa6e1462693cf8e46f930da96ec1b0bb22'} |
npm | GHSA-xqp8-w826-hh6x | Crash server with query parameter | ### Impact
Parse Server crashes when if a query request contains an invalid value for the `explain` option. This is due to a bug in the MongoDB Node.js driver which throws an exception that Parse Server cannot catch.
### Patches
Upgrade to Parse Server 4.10.3 | {'CVE-2021-39187'} | 2021-09-03T20:35:12Z | 2021-09-02T16:51:14Z | HIGH | null | {'CWE-74', 'CWE-20', 'CWE-755'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-39187', 'https://jira.mongodb.org/browse/NODE-3463', 'https://github.com/parse-community/parse-server', 'https://github.com/parse-community/parse-server/commit/308668c89474223e2448be92d6823b52c1c313ec', 'https://github.com/parse-community/parse-server/security/advisories/GHSA-xqp8-w826-hh6x', 'https://github.com/parse-community/parse-server/releases/tag/4.10.3'} | null | {'https://github.com/parse-community/parse-server/commit/308668c89474223e2448be92d6823b52c1c313ec'} | {'https://github.com/parse-community/parse-server/commit/308668c89474223e2448be92d6823b52c1c313ec'} |
npm | GHSA-gmjw-49p4-pcfm | Prototype poisoning | ### Impact
The issue is as follows: when `msgpack5` decodes a map containing a
key `"__proto__"`, it assigns the decoded value to `__proto__`. As you
are no doubt aware, `Object.prototype.__proto__` is an accessor
property for the receiver's prototype. If the value corresponding to
the key `__proto__` decodes to an object or `null`, `msgpack5` sets
the decoded object's prototype to that value.
An attacker who can submit crafted MessagePack data to a service can
use this to produce values that appear to be of other types; may have
unexpected prototype properties and methods (for example `length`,
numeric properties, and `push` et al if `__proto__`'s value decodes to
an `Array`); and/or may throw unexpected exceptions when used (for
example if the `__proto__` value decodes to a `Map` or `Date`). Other
unexpected behavior might be produced for other types.
There is no effect on the global prototype.
An example:
```js
const msgpack5 = require('msgpack5')();
const payload = {};
Object.defineProperty(payload, '__proto__', {
value: new Map().set(1, 2),
enumerable: true
});
const encoded = msgpack5.encode(payload);
console.log(encoded); // <Buffer 81 a9 5f 5f 70 72 6f 74 6f 5f 5f 81 01 02>
const decoded = msgpack5.decode(encoded);
// decoded's prototype has been overwritten
console.log(Object.getPrototypeOf(decoded)); // Map(1) { 1 => 2 }
console.log(decoded.get); // [Function: get]
// decoded appears to most common typechecks to be a Map
console.log(decoded instanceof Map); // true
console.log(decoded.toString()); // [object Map]
console.log(Object.prototype.toString.call(decoded)); // [object Map]
console.log(decoded.constructor.name); // Map
console.log(Object.getPrototypeOf(decoded).constructor.name); // Map
// decoded is not, however, a Map
console.log(Object.getPrototypeOf(decoded) === Map.prototype); // false
// using decoded as though it were a Map throws
try {
decoded.get(1);
} catch (error) {
console.log(error); // TypeError: Method Map.prototype.get called
// on incompatible receiver #<Map>
}
try {
decoded.size;
} catch (error) {
console.log(error); // TypeError: Method get Map.prototype.size
// called on incompatible receiver #<Map>
}
// re-encoding the decoded value throws
try {
msgpack5.encode(decoded);
} catch (error) {
console.log(error); // TypeError: Method Map.prototype.entries
// called on incompatible receiver #<Map>
}
```
This "prototype poisoning" is sort of a very limited inversion of a
prototype pollution attack. Only the decoded value's prototype is
affected, and it can only be set to `msgpack5` values (though if the
victim makes use of custom codecs, anything could be a `msgpack5`
value). We have not found a way to escalate this to true prototype
pollution (absent other bugs in the consumer's code).
### Patches
Versions v5.2.1, v4.5.1, v3.6.1 include the fix.
### Workarounds
Always validate incoming data after parsing before doing any processing.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [example link to repo](http://example.com)
* Email us at [example email address](mailto:example@example.com) | {'CVE-2021-21368'} | 2021-03-12T16:57:44Z | 2021-03-12T22:44:17Z | MODERATE | null | {'CWE-915'} | {'https://www.npmjs.com/package/msgpack5', 'https://github.com/mcollina/msgpack5/security/advisories/GHSA-gmjw-49p4-pcfm', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21368', 'https://github.com/mcollina/msgpack5/releases/tag/v5.2.1', 'https://github.com/mcollina/msgpack5/releases/tag/v4.5.1', 'https://github.com/mcollina/msgpack5/releases/tag/v3.6.1', 'https://github.com/mcollina/msgpack5/commit/d4e6cb956ae51c8bb2828e71c7c1107c340cf1e8'} | null | {'https://github.com/mcollina/msgpack5/commit/d4e6cb956ae51c8bb2828e71c7c1107c340cf1e8'} | {'https://github.com/mcollina/msgpack5/commit/d4e6cb956ae51c8bb2828e71c7c1107c340cf1e8'} |
npm | GHSA-236h-rqv8-8q73 | GraphQL: Security breach on Viewer query | ### Impact
An authenticated user using the viewer GraphQL query can bypass all read security on his User object and can also bypass all objects linked via relation or Pointer on his User object.
### Patches
This vulnerability has been patched in Parse Server 4.3.0.
### Workarounds
No
### References
See [commit 78239ac](https://github.com/parse-community/parse-server/commit/78239ac9071167fdf243c55ae4bc9a2c0b0d89aa) for details. | {'CVE-2020-15126'} | 2021-01-07T23:46:50Z | 2020-07-22T23:06:47Z | HIGH | null | {'CWE-863'} | {'https://github.com/parse-community/parse-server/commit/78239ac9071167fdf243c55ae4bc9a2c0b0d89aa', 'https://github.com/parse-community/parse-server/security/advisories/GHSA-236h-rqv8-8q73', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15126', 'https://github.com/parse-community/parse-server/blob/master/CHANGELOG.md#430'} | null | {'https://github.com/parse-community/parse-server/commit/78239ac9071167fdf243c55ae4bc9a2c0b0d89aa'} | {'https://github.com/parse-community/parse-server/commit/78239ac9071167fdf243c55ae4bc9a2c0b0d89aa'} |
npm | GHSA-7wwv-vh3v-89cq | ReDOS vulnerabities: multiple grammars | ### Impact: Potential ReDOS vulnerabilities (exponential and polynomial RegEx backtracking)
[oswasp](https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS):
> The Regular expression Denial of Service (ReDoS) is a Denial of Service attack, that exploits the fact that most Regular Expression implementations may reach extreme situations that cause them to work very slowly (exponentially related to input size). An attacker can then cause a program using a Regular Expression to enter these extreme situations and then hang for a very long time.
If are you are using Highlight.js to highlight user-provided data you are possibly vulnerable. On the client-side (in a browser or Electron environment) risks could include lengthy freezes or crashes... On the server-side infinite freezes could occur... effectively preventing users from accessing your app or service (ie, Denial of Service).
This is an issue with grammars shipped with the parser (and potentially 3rd party grammars also), not the parser itself. If you are using Highlight.js with any of the following grammars you are vulnerable. If you are using `highlightAuto` to detect the language (and have any of these grammars registered) you are vulnerable. Exponential grammars (C, Perl, JavaScript) are auto-registered when using the common grammar subset/library `require('highlight.js/lib/common')` as of 10.4.0 - see https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@10.4.0/build/highlight.js
All versions prior to 10.4.1 are vulnerable, including version 9.18.5.
**Grammars with exponential backtracking issues:**
- c-like (c, cpp, arduino)
- handlebars (htmlbars)
- gams
- perl
- jboss-cli
- r
- erlang-repl
- powershell
- routeros
- livescript (10.4.0 and 9.18.5 included this fix)
- javascript & typescript (10.4.0 included partial fixes)
And of course any aliases of those languages have the same issue. ie: `hpp` is no safer than `cpp`.
**Grammars with polynomial backtracking issues:**
- kotlin
- gcode
- d
- aspectj
- moonscript
- coffeescript/livescript
- csharp
- scilab
- crystal
- elixir
- basic
- ebnf
- ruby
- fortran/irpf90
- livecodeserver
- yaml
- x86asm
- dsconfig
- markdown
- ruleslanguage
- xquery
- sqf
And again: any aliases of those languages have the same issue. ie: `ruby` and `rb` share the same ruby issues.
### Patches
- Version 10.4.1 resolves these vulnerabilities. Please upgrade.
### Workarounds / Mitigations
- Discontinue use the affected grammars. (or perhaps use only those with poly vs exponential issues)
- Attempt cherry-picking the grammar fixes into older versions...
- Attempt using newer CDN versions of any affected languages. (ie using an older CDN version of the library with newer CDN grammars). Your mileage may vary.
### References
- https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS
### For more information
If you have any questions or comments about this advisory:
* Open an issue: https://github.com/highlightjs/highlight.js/issues
* Email us at [security@highlightjs.com](mailto:security@highlightjs.com) | null | 2022-05-03T08:27:45Z | 2020-12-04T16:47:20Z | MODERATE | null | {'CWE-400', 'CWE-20'} | {'https://www.npmjs.com/package/@highlightjs/cdn-assets', 'https://github.com/highlightjs/highlight.js/security/advisories/GHSA-7wwv-vh3v-89cq', 'https://www.npmjs.com/package/highlight.js', 'https://github.com/highlightjs/highlight.js/commit/373b9d862401162e832ce77305e49b859e110f9c'} | null | {'https://github.com/highlightjs/highlight.js/commit/373b9d862401162e832ce77305e49b859e110f9c'} | {'https://github.com/highlightjs/highlight.js/commit/373b9d862401162e832ce77305e49b859e110f9c'} |
npm | GHSA-8462-q7x7-g2x4 | High severity vulnerability that affects bson | The MongoDB bson JavaScript module (also known as js-bson) versions 0.5.0 to 1.0.x before 1.0.5 is vulnerable to a Regular Expression Denial of Service (ReDoS) in lib/bson/decimal128.js. The flaw is triggered when the Decimal128.fromString() function is called to parse a long untrusted string. | {'CVE-2018-13863'} | 2021-09-03T22:29:39Z | 2018-09-17T20:44:58Z | HIGH | null | {'CWE-400', 'CWE-185'} | {'https://github.com/mongodb/js-bson', 'https://github.com/advisories/GHSA-8462-q7x7-g2x4', 'https://github.com/mongodb/js-bson/commit/bd61c45157c53a1698ff23770160cf4783e9ea4a', 'https://snyk.io/vuln/npm:bson:20180225', 'https://nvd.nist.gov/vuln/detail/CVE-2018-13863'} | null | {'https://github.com/mongodb/js-bson/commit/bd61c45157c53a1698ff23770160cf4783e9ea4a'} | {'https://github.com/mongodb/js-bson/commit/bd61c45157c53a1698ff23770160cf4783e9ea4a'} |
npm | GHSA-xmh9-rg6f-j3mr | Verification flaw in Solid identity-token-verifier | ### Impact
#### Severity
Any Pod on a Solid server using a vulnerable version of the identity-token-verifier library is at risk of a spoofed Demonstration of Proof-of-Possession (DPoP) token binding. This vulnerability could give total and complete access to a targeted Pod.
#### Summary
A verification flaw in the implementation of the identity token verifier library (https://github.com/solid/identity-token-verifier) allows DPoP proofs to be spoofed.
DPoP proofs are used to bind access tokens to a private key meant to be in sole possession of a specific user. Instead of verifying against the hash of an embedded public key, the library instead verifies against a field that an attacker can modify to spoof another user’s DPoP.
A stolen DPoP proof, when used in the right context, therefore allows the rebinding of a DPoP-bound access token. Any attacker in possession of a targeted access token could build an attack environment to replay it on any Pod service with this vulnerability.
### Patches
A new version 0.5.2 of identity-token-verifier fixes the verification: https://github.com/solid/identity-token-verifier/blob/7e18d86d65ee681e8ae912b6a032a1bae3cae570/src/lib/DPoP.ts#L25-L35
### Workarounds
None
### References
_Are there any links users can visit to find out more?_
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [identity-token-verifier](https://github.com/solid/identity-token-verifier/) repository.
* Email: info@solidproject.org | null | 2021-03-10T04:01:48Z | 2021-03-12T22:39:01Z | MODERATE | null | {'CWE-290'} | {'https://github.com/solid/identity-token-verifier/commit/fbdeb4aa8c12694b3744cd0454acb826817d9e6c', 'https://www.npmjs.com/package/@solid/identity-token-verifier', 'https://github.com/solid/identity-token-verifier/releases/tag/0.5.2', 'https://github.com/solid/identity-token-verifier/security/advisories/GHSA-xmh9-rg6f-j3mr'} | null | {'https://github.com/solid/identity-token-verifier/commit/fbdeb4aa8c12694b3744cd0454acb826817d9e6c'} | {'https://github.com/solid/identity-token-verifier/commit/fbdeb4aa8c12694b3744cd0454acb826817d9e6c'} |
npm | GHSA-6gg3-pmm7-97xc | DOM-based XSS in auth0-lock | ### Overview
Versions before and including `11.25.1` are using `dangerouslySetInnerHTML` to display an informational message when used with a Passwordless or Enterprise connection.
- For Passwordless connection, the value of the input (email or phone number) is displayed back to the user while waiting for verification code input.
- For Enterprise connection, the value of the input (IdP Domain) from the Enterprise connection setup screen (Auth0 Dashboard) is displayed back to the user when the `lock` widget opens.
When Passwordless or Enterprise connection is used, the application and its users might be exposed to cross-site scripting (XSS) attacks.
### Am I affected?
You are affected by this vulnerability if all of the following conditions apply:
- You are using auth0-lock
- You are using Passwordless or Enterprise connection mode
### How to fix that?
Upgrade to version `11.26.3`
### Will this update impact my users?
The fix provided in patch will not affect your users.
### Credit
https://github.com/mvisat | {'CVE-2020-15119'} | 2021-01-07T23:40:43Z | 2020-08-19T21:05:03Z | LOW | null | {'CWE-79'} | {'https://github.com/auth0/lock/commit/3711fb5b42afd40073a61a58759251f51e768b1b', 'https://github.com/auth0/lock/security/advisories/GHSA-6gg3-pmm7-97xc', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15119'} | null | {'https://github.com/auth0/lock/commit/3711fb5b42afd40073a61a58759251f51e768b1b'} | {'https://github.com/auth0/lock/commit/3711fb5b42afd40073a61a58759251f51e768b1b'} |
npm | GHSA-fg5w-w99f-rj6w | Command Injection in @ronomon/opened | The @ronomon/opened library before 1.5.2 is vulnerable to a command injection vulnerability which would allow a remote attacker to execute commands on the system if the library was used with untrusted input. | {'CVE-2021-29300'} | 2021-05-28T16:56:53Z | 2021-06-08T23:15:35Z | CRITICAL | null | {'CWE-77'} | {'https://advisory.checkmarx.net/advisory/CX-2021-4775', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29300', 'https://github.com/ronomon/opened/commit/7effe011d4fea8fac7f78c00615e0a6e69af68ec'} | null | {'https://github.com/ronomon/opened/commit/7effe011d4fea8fac7f78c00615e0a6e69af68ec'} | {'https://github.com/ronomon/opened/commit/7effe011d4fea8fac7f78c00615e0a6e69af68ec'} |
npm | GHSA-6fc8-4gx4-v693 | ReDoS in Sec-Websocket-Protocol header | ### Impact
A specially crafted value of the `Sec-Websocket-Protocol` header can be used to significantly slow down a ws server.
### Proof of concept
```js
for (const length of [1000, 2000, 4000, 8000, 16000, 32000]) {
const value = 'b' + ' '.repeat(length) + 'x';
const start = process.hrtime.bigint();
value.trim().split(/ *, */);
const end = process.hrtime.bigint();
console.log('length = %d, time = %f ns', length, end - start);
}
```
### Patches
The vulnerability was fixed in ws@7.4.6 (https://github.com/websockets/ws/commit/00c425ec77993773d823f018f64a5c44e17023ff) and backported to ws@6.2.2 (https://github.com/websockets/ws/commit/78c676d2a1acefbc05292e9f7ea0a9457704bf1b) and ws@5.2.3 (https://github.com/websockets/ws/commit/76d47c1479002022a3e4357b3c9f0e23a68d4cd2).
### Workarounds
In vulnerable versions of ws, the issue can be mitigated by reducing the maximum allowed length of the request headers using the [`--max-http-header-size=size`](https://nodejs.org/api/cli.html#cli_max_http_header_size_size) and/or the [`maxHeaderSize`](https://nodejs.org/api/http.html#http_http_createserver_options_requestlistener) options.
### Credits
The vulnerability was responsibly disclosed along with a fix in private by [Robert McLaughlin](https://github.com/robmcl4) from University of California, Santa Barbara.
| {'CVE-2021-32640'} | 2021-10-06T22:05:51Z | 2021-05-28T19:19:03Z | MODERATE | null | {'CWE-345', 'CWE-400'} | {'https://github.com/websockets/ws', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32640', 'https://lists.apache.org/thread.html/rdfa7b6253c4d6271e31566ecd5f30b7ce1b8fb2c89d52b8c4e0f4e30@%3Ccommits.tinkerpop.apache.org%3E', 'https://github.com/websockets/ws/security/advisories/GHSA-6fc8-4gx4-v693', 'https://github.com/websockets/ws/commit/00c425ec77993773d823f018f64a5c44e17023ff', 'https://github.com/websockets/ws/issues/1895'} | null | {'https://github.com/websockets/ws/commit/00c425ec77993773d823f018f64a5c44e17023ff'} | {'https://github.com/websockets/ws/commit/00c425ec77993773d823f018f64a5c44e17023ff'} |
npm | GHSA-9r27-994c-4xch | discord-html not escaping HTML code blocks when lacking a language identifier | ### Impact
Any website using discord-markdown with user-generated markdown is vulnerable to having code injected into the page where the markdown is displayed.
### Patches
This has been patched in version 2.3.1
### Workarounds
Escape the characters `<>&` before sending plain code blocks to discord-markdown.
### References
https://github.com/brussell98/discord-markdown/issues/13 | null | 2020-02-21T20:20:53Z | 2020-02-24T17:34:02Z | HIGH | null | null | {'https://github.com/brussell98/discord-markdown/security/advisories/GHSA-9r27-994c-4xch', 'https://github.com/brussell98/discord-markdown/commit/7ce2eb66520815dcf5e97ef2bc8a2d5979da66e7', 'https://github.com/brussell98/discord-markdown/issues/13'} | null | {'https://github.com/brussell98/discord-markdown/commit/7ce2eb66520815dcf5e97ef2bc8a2d5979da66e7'} | {'https://github.com/brussell98/discord-markdown/commit/7ce2eb66520815dcf5e97ef2bc8a2d5979da66e7'} |
npm | GHSA-582f-p4pg-xc74 | Regular Expression Denial of Service in csv-parse | Versions of `csv-parse` prior to 4.4.6 are vulnerable to Regular Expression Denial of Service. The `__isInt()` function contains a malformed regular expression that processes large specially-crafted input very slowly, leading to a Denial of Service. This is triggered when using the `cast` option.
## Recommendation
Upgrade to version 4.4.6 or later. | {'CVE-2019-17592'} | 2022-01-04T19:51:33Z | 2019-10-15T20:06:16Z | HIGH | null | {'CWE-400', 'CWE-20'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Z36UKPO5F3PQ3Q2POMF5LEKXWAH5RUFP/', 'https://nvd.nist.gov/vuln/detail/CVE-2019-17592', 'https://github.com/adaltas/node-csv-parse', 'https://www.npmjs.com/advisories/1171', 'https://github.com/adaltas/node-csv-parse/commit/b9d35940c6815cdf1dfd6b21857a1f6d0fd51e4a', 'https://security.netapp.com/advisory/ntap-20191127-0002/'} | null | {'https://github.com/adaltas/node-csv-parse/commit/b9d35940c6815cdf1dfd6b21857a1f6d0fd51e4a'} | {'https://github.com/adaltas/node-csv-parse/commit/b9d35940c6815cdf1dfd6b21857a1f6d0fd51e4a'} |
npm | GHSA-3wj8-vp9h-rm6m | Remote Code Execution (RCE) | The package total.js before 3.4.8 are vulnerable to Remote Code Execution (RCE) via set. | {'CVE-2021-23344'} | 2021-03-12T22:42:43Z | 2021-03-19T21:32:20Z | CRITICAL | null | {'CWE-94'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-23344', 'https://snyk.io/vuln/SNYK-JS-TOTALJS-1077069', 'https://github.com/totaljs/framework/commit/c812bbcab8981797d3a1b9993fc42dad3d246f04'} | null | {'https://github.com/totaljs/framework/commit/c812bbcab8981797d3a1b9993fc42dad3d246f04'} | {'https://github.com/totaljs/framework/commit/c812bbcab8981797d3a1b9993fc42dad3d246f04'} |
npm | GHSA-vh5w-fg69-rc8m | Improper Input Validation in Google Closure Library | A URL parsing issue in goog.uri of the Google Closure Library versions up to and including v20200224 allows an attacker to send malicious URLs to be parsed by the library and return the wrong authority. Mitigation -- update your library to version v20200315. | {'CVE-2020-8910'} | 2021-05-06T20:57:55Z | 2021-05-07T16:06:34Z | MODERATE | null | {'CWE-20'} | {'https://github.com/google/closure-library/commit/294fc00b01d248419d8f8de37580adf2a0024fc9', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8910', 'https://github.com/google/closure-library/releases/tag/v20200315'} | null | {'https://github.com/google/closure-library/commit/294fc00b01d248419d8f8de37580adf2a0024fc9'} | {'https://github.com/google/closure-library/commit/294fc00b01d248419d8f8de37580adf2a0024fc9'} |
npm | GHSA-5xjx-4xcm-hpcm | Prototype Pollution in ts-nodash | `ts-nodash` before version 1.2.7 is vulnerable to Prototype Pollution via the Merge() function due to lack of validation input. | {'CVE-2021-23403'} | 2021-12-10T18:53:36Z | 2021-12-10T18:53:42Z | HIGH | null | {'CWE-915', 'CWE-1321'} | {'https://github.com/BadOPCode/NoDash/commit/b9cc2b3b49f6cd5228e406bc57e17a28b998fea5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23403', 'https://github.com/BadOPCode/NoDash/blob/master/src/Merge.ts', 'https://snyk.io/vuln/SNYK-JS-TSNODASH-1311009'} | null | {'https://github.com/BadOPCode/NoDash/commit/b9cc2b3b49f6cd5228e406bc57e17a28b998fea5'} | {'https://github.com/BadOPCode/NoDash/commit/b9cc2b3b49f6cd5228e406bc57e17a28b998fea5'} |
npm | GHSA-c6rp-xvqv-mwmf | Cross-site Scripting in epubjs | managers/views/iframe.js in FuturePress EPub.js before 0.3.89 allows XSS. | {'CVE-2021-33040'} | 2022-01-19T14:07:11Z | 2022-01-21T23:52:17Z | HIGH | null | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-33040', 'https://github.com/futurepress/epub.js/blob/5c7f21d648d9d20d44c6c365d164b16871847023/src/managers/views/iframe.js#L373', 'https://github.com/futurepress/epub.js/compare/v0.3.88...v0.3.89', 'https://github.com/futurepress/epub.js/commit/ab4dd46408cce0324e1c67de4a3ba96b59e5012e', 'https://github.com/futurepress/epub.js'} | null | {'https://github.com/futurepress/epub.js/commit/ab4dd46408cce0324e1c67de4a3ba96b59e5012e'} | {'https://github.com/futurepress/epub.js/commit/ab4dd46408cce0324e1c67de4a3ba96b59e5012e'} |
npm | GHSA-q26w-wjj2-22vv | Cross-site scripting in Joplin | Joplin allows XSS via a LINK element in a note. | {'CVE-2020-28249'} | 2021-04-20T19:38:53Z | 2021-05-10T18:47:36Z | MODERATE | null | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-28249', 'https://github.com/fhlip0/JopinXSS', 'https://www.npmjs.com/package/joplin', 'https://github.com/laurent22/joplin/commit/fd90a490c0e5cacd17bfe0ffc422be1d2a9b1c13', 'https://github.com/laurent22/joplin/releases/tag/v1.3.11'} | null | {'https://github.com/laurent22/joplin/commit/fd90a490c0e5cacd17bfe0ffc422be1d2a9b1c13'} | {'https://github.com/laurent22/joplin/commit/fd90a490c0e5cacd17bfe0ffc422be1d2a9b1c13'} |
npm | GHSA-8f9f-pc5v-9r5h | Malicious takeover of previously owned ENS names | ### Impact
A user who owns an ENS domain can set a "trapdoor", allowing them to transfer ownership to another user, and later regain ownership without the new owner's consent or awareness.
### Patches
A new ENS deployment is being rolled out that fixes this vulnerability in the ENS registry. The registry is newly deployed at [0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e](https://etherscan.io/address/0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e).
### Workarounds
Do not accept transfers of ENS domains from other users on the old registrar. | {'CVE-2020-5232'} | 2021-01-08T20:31:45Z | 2020-01-30T23:55:04Z | CRITICAL | null | {'CWE-285'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-5232', 'https://github.com/ensdomains/ens/commit/36e10e71fcddcade88646821e0a57cc6c19e1ecf', 'https://github.com/ensdomains/ens/security/advisories/GHSA-8f9f-pc5v-9r5h'} | null | {'https://github.com/ensdomains/ens/commit/36e10e71fcddcade88646821e0a57cc6c19e1ecf'} | {'https://github.com/ensdomains/ens/commit/36e10e71fcddcade88646821e0a57cc6c19e1ecf'} |
npm | GHSA-r628-mhmh-qjhw | Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning | ### Impact
Arbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution
`node-tar` aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary `stat` calls to determine whether a given path is a directory, paths are cached when directories are created.
This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory. This order of operations resulted in the directory being created and added to the `node-tar` directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where `node-tar` checks for symlinks occur.
By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass `node-tar` symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite.
This issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.
### Patches
3.2.3 || 4.4.15 || 5.0.7 || 6.1.2
### Workarounds
Users may work around this vulnerability without upgrading by creating a custom `filter` method which prevents the extraction of symbolic links.
```js
const tar = require('tar')
tar.x({
file: 'archive.tgz',
filter: (file, entry) => {
if (entry.type === 'SymbolicLink') {
return false
} else {
return true
}
}
})
```
Users are encouraged to upgrade to the latest patch versions, rather than attempt to sanitize tar input themselves. | {'CVE-2021-32803'} | 2021-08-30T23:14:33Z | 2021-08-03T19:00:40Z | HIGH | null | {'CWE-23', 'CWE-22'} | {'https://github.com/npm/node-tar/security/advisories/GHSA-r628-mhmh-qjhw', 'https://github.com/npm/node-tar', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32803', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://www.npmjs.com/package/tar', 'https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf', 'https://github.com/npm/node-tar/commit/9dbdeb6df8e9dbd96fa9e84341b9d74734be6c20', 'https://www.npmjs.com/advisories/1771'} | null | {'https://github.com/npm/node-tar/commit/9dbdeb6df8e9dbd96fa9e84341b9d74734be6c20'} | {'https://github.com/npm/node-tar/commit/9dbdeb6df8e9dbd96fa9e84341b9d74734be6c20'} |
npm | GHSA-62gr-4qp9-h98f | Regular Expression Denial of Service in Handlebars | Handlebars before 4.4.5 allows Regular Expression Denial of Service (ReDoS) because of eager matching. The parser may be forced into an endless loop while processing crafted templates. This may allow attackers to exhaust system resources. | {'CVE-2019-20922'} | 2021-04-22T23:31:21Z | 2022-02-10T20:38:22Z | HIGH | null | {'CWE-400'} | {'https://www.npmjs.com/advisories/1300', 'https://nvd.nist.gov/vuln/detail/CVE-2019-20922', 'https://github.com/handlebars-lang/handlebars.js/commit/8d5530ee2c3ea9f0aee3fde310b9f36887d00b8b', 'https://snyk.io/vuln/SNYK-JS-HANDLEBARS-480388', 'https://www.npmjs.com/package/handlebars'} | null | {'https://github.com/handlebars-lang/handlebars.js/commit/8d5530ee2c3ea9f0aee3fde310b9f36887d00b8b'} | {'https://github.com/handlebars-lang/handlebars.js/commit/8d5530ee2c3ea9f0aee3fde310b9f36887d00b8b'} |
npm | GHSA-g6ww-v8xp-vmwg | Prototype pollution in pathval | A prototype pollution vulnerability affects all versions of package pathval under 1.1.1. | {'CVE-2020-7751'} | 2022-04-18T21:58:49Z | 2022-02-10T20:21:24Z | HIGH | null | {'CWE-20', 'CWE-1321'} | {'https://github.com/chaijs/pathval', 'https://github.com/chaijs/pathval/pull/58/commits/21a9046cfa0c2697cb41990f3b4316db410e6c8a', 'https://github.com/chaijs/pathval/pull/58/files', 'https://snyk.io/vuln/SNYK-JS-PATHVAL-596926', 'https://github.com/chaijs/pathval/releases/tag/v1.1.1', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7751'} | null | {'https://github.com/chaijs/pathval/pull/58/commits/21a9046cfa0c2697cb41990f3b4316db410e6c8a'} | {'https://github.com/chaijs/pathval/pull/58/commits/21a9046cfa0c2697cb41990f3b4316db410e6c8a'} |
Hex | GHSA-5653-437f-5hmc | Denial of service | The use of `String.to_atom/1` in PowAssent is susceptible to denial of service attacks. In `PowAssent.Phoenix.AuthorizationController` a value is fetched from the user provided params, and `String.to_atom/1` is used to convert the binary value to an atom so it can be used to fetch the provider configuration value. This is unsafe as it is user provided data, and can be used to fill up the whole atom table of ~1M which will cause the app to crash. | {'CVE-2019-16764'} | 2022-04-12T21:29:30Z | 2022-04-12T21:29:30Z | MODERATE | null | {'CWE-400'} | {'http://erlang.org/doc/efficiency_guide/commoncaveats.html#list_to_atom-1', 'https://github.com/pow-auth/pow_assent/commit/026105eeecc0e3c2f807e7109e745ea93c0fd9cf', 'https://github.com/pow-auth/pow_assent', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16764', 'https://github.com/pow-auth/pow_assent/security/advisories/GHSA-368c-xvrv-x986', 'https://hex.pm/packages/pow_assent'} | null | {'https://github.com/pow-auth/pow_assent/commit/026105eeecc0e3c2f807e7109e745ea93c0fd9cf'} | {'https://github.com/pow-auth/pow_assent/commit/026105eeecc0e3c2f807e7109e745ea93c0fd9cf'} |
Hex | GHSA-2xxx-fhc8-9qvq | Missing `is_nil` requirement | Ecto will not raise on queries with non-explicit nil comparisons (ie if they aren't checked with `is_nil`). | null | 2022-04-12T19:42:45Z | 2022-04-12T19:42:45Z | MODERATE | null | null | {'https://github.com/elixir-ecto/ecto/pull/2125', 'https://github.com/elixir-ecto/ecto/commit/db55b0cba6525c24ebddc88ef9ae0c1c00620250', 'https://groups.google.com/forum/#!topic/elixir-ecto/0m4NPfg_MMU', 'https://github.com/elixir-ecto/ecto'} | null | {'https://github.com/elixir-ecto/ecto/commit/db55b0cba6525c24ebddc88ef9ae0c1c00620250'} | {'https://github.com/elixir-ecto/ecto/commit/db55b0cba6525c24ebddc88ef9ae0c1c00620250'} |
Hex | GHSA-w98m-2xqg-9cvj | Remote Code Execution in paginator | There is a vulnerability in Paginator which makes it susceptible to Remote Code Execution (RCE) attacks via input parameters to the `paginate()` function.
### Impact
There is a vulnerability in Paginator which makes it susceptible to Remote Code Execution (RCE) attacks via input parameters to the `paginate()` function. This will potentially affect all current users of `Paginator` prior to version >= 1.0.0.
### Patches
The vulnerability has been patched in version 1.0.0 and all users should upgrade to this version immediately. Note that this patched version uses a dependency that requires an Elixir version >=1.5.
### Credits
Thank you to Peter Stöckli. | {'CVE-2020-15150'} | 2022-04-12T19:36:39Z | 2022-04-12T19:36:39Z | CRITICAL | null | null | {'https://github.com/duffelhq/paginator/security/advisories/GHSA-w98m-2xqg-9cvj', 'https://hex.pm/packages/paginator', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15150', 'https://github.com/duffelhq/paginator/blob/ccf0f37fa96347cc8c8a7e9eb2c64462cec4b2dc/README.md#security-considerations', 'https://github.com/duffelhq/paginator', 'https://github.com/duffelhq/paginator/commit/bf45e92602e517c75aea0465efc35cd661d9ebf8'} | null | {'https://github.com/duffelhq/paginator/commit/bf45e92602e517c75aea0465efc35cd661d9ebf8'} | {'https://github.com/duffelhq/paginator/commit/bf45e92602e517c75aea0465efc35cd661d9ebf8'} |
Hex | GHSA-j3gg-r6gp-95q2 | XSS in HEEx class attributes | The `class` attribute was not protected against XSS attacks when using HEEx. | null | 2022-04-12T20:22:57Z | 2022-04-12T20:22:57Z | MODERATE | null | {'CWE-79'} | {'https://github.com/phoenixframework/phoenix_html/commit/62a0139fb716bcdce697f6221244bd81d321d620', 'https://github.com/phoenixframework/phoenix_html'} | null | {'https://github.com/phoenixframework/phoenix_html/commit/62a0139fb716bcdce697f6221244bd81d321d620'} | {'https://github.com/phoenixframework/phoenix_html/commit/62a0139fb716bcdce697f6221244bd81d321d620'} |
Hex | GHSA-v2wf-c3j6-wpvw | Session fixation | ### Impact
The use of `Plug.Session` in `Pow.Plug.Session` is susceptible to session fixation attacks if a persistent session store is used for `Plug.Session`, such as Redis or a database. Cookie store, which is used in most Phoenix apps, doesn't have this vulnerability.
### Workarounds
Call `Plug.Conn.configure_session(conn, renew: true)` periodically and after privilege change. A custom authorization plug can be written where the `create/3` method should return the `conn` only after `Plug.Conn.configure_session/2` have been called on it.
### References
https://github.com/danschultzer/pow/commit/578ffd3d8bb8e8a26077b644222186b108da474f
https://www.owasp.org/index.php/Session_fixation | {'CVE-2020-5205'} | 2022-04-12T21:27:49Z | 2022-04-12T21:27:49Z | MODERATE | null | {'CWE-384'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-5205', 'https://github.com/danschultzer/pow/commit/578ffd3d8bb8e8a26077b644222186b108da474f', 'https://github.com/danschultzer/pow/security/advisories/GHSA-v2wf-c3j6-wpvw', 'https://github.com/danschultzer/pow', 'https://github.com/danschultzer/pow/blob/master/CHANGELOG.md#v1016-2020-01-07'} | null | {'https://github.com/danschultzer/pow/commit/578ffd3d8bb8e8a26077b644222186b108da474f'} | {'https://github.com/danschultzer/pow/commit/578ffd3d8bb8e8a26077b644222186b108da474f'} |
Hex | GHSA-9h73-w7ch-rh73 | Header Injection | Elixir Plug Plug version All contains a Header Injection vulnerability in Connection that can result in Given a cookie value, Headers can be added. This attack appear to be exploitable via Crafting a value to be sent as a cookie. This vulnerability appears to have been fixed in >= 1.3.5 or ~> 1.2.5 or ~> 1.1.9 or ~> 1.0.6. | {'CVE-2018-1000883'} | 2022-04-12T21:26:27Z | 2022-04-12T21:26:27Z | MODERATE | null | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-1000883', 'https://github.com/dependabot/elixir-security-advisories/blob/master/packages/plug/2017-04-17.yml', 'https://github.com/elixir-plug/plug', 'https://github.com/elixir-plug/plug/commit/8857f8ab4acf9b9c22e80480dae2636692f5f573'} | null | {'https://github.com/elixir-plug/plug/commit/8857f8ab4acf9b9c22e80480dae2636692f5f573'} | {'https://github.com/elixir-plug/plug/commit/8857f8ab4acf9b9c22e80480dae2636692f5f573'} |
Packagist | GHSA-2ccx-2gf3-8xvv | .dev domains and some reverse proxy setups were treated as local in Kirby | ### Impact
#### About our registration block
In order to protect new installations on public servers that don't have an admin account for the Panel yet, we block account registration there by default. This is a security feature, which we implemented years ago in Kirby 2. It helps to avoid that you forget registering your first admin account on a public server.
In this case – without our security block – someone else might theoretically be able to find your site, find out it's running on Kirby, find the Panel and then register the account first. It's an unlikely situation, but it's still a certain risk.
To be able to register the first Panel account on a public server, you have to enforce the installer via a config setting. This helps to push all users to the best practice of registering your first Panel account on your local machine and upload it together with the rest of the site.
#### The issue
As noted by [Jukka Rautanen](https://github.com/jukra), this installation block implementation in Kirby versions before 3.3.6 still assumed that .dev domains are local domains, which is no longer true. In the meantime, those domains became publicly available. This means that our installation block is no longer working as expected if you use a .dev domain for your Kirby site.
In fixing this issue, we've also found out that the local installation check may also fail if your site is behind a reverse proxy.
#### Am I affected?
You are only affected if:
1. you use a .dev domain or your site is behind a reverse proxy &
2. you have not yet registered your first Panel account on the public server &
3. someone finds your site and tries to login at `yourdomain.dev/panel` before you register your first account.
You are not affected if you have already created one or multiple Panel accounts (no matter if on a .dev domain or behind a reverse proxy).
### Patches
The problem has been patched in [Kirby 2.5.14](https://github.com/getkirby-v2/panel/releases/tag/2.5.14) and [Kirby 3.3.6](https://github.com/getkirby/kirby/releases/tag/3.3.6). Please update to one of these or a [later version](https://github.com/getkirby/kirby/releases) to fix the vulnerability.
**Note:** Kirby 2 reaches end of life on December 31, 2020. We therefore recommend to upgrade your Kirby 2 sites to Kirby 3. If you cannot upgrade, we still recommend to update to Kirby 2.5.14.
### Workarounds
Kirby 2 sites on older releases can also be patched by applying the [changes from this commit](https://github.com/getkirby-v2/panel/commit/7f9ac1876bacb89fd8f142f5e561a02ebb725baa). | {'CVE-2020-26253'} | 2021-07-02T16:52:32Z | 2021-01-14T19:15:19Z | MODERATE | null | {'CWE-346'} | {'https://github.com/getkirby-v2/panel/commit/7f9ac1876bacb89fd8f142f5e561a02ebb725baa', 'https://github.com/getkirby/kirby/security/advisories/GHSA-2ccx-2gf3-8xvv', 'https://packagist.org/packages/getkirby/panel', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26253', 'https://packagist.org/packages/getkirby/cms', 'https://github.com/getkirby/kirby/releases/tag/3.3.6'} | null | {'https://github.com/getkirby-v2/panel/commit/7f9ac1876bacb89fd8f142f5e561a02ebb725baa'} | {'https://github.com/getkirby-v2/panel/commit/7f9ac1876bacb89fd8f142f5e561a02ebb725baa'} |
Packagist | GHSA-vvmr-8829-6whx | CSRF token missing in Symfony | Description
-----------
The Symfony form component provides a CSRF protection mechanism by using a random token injected in the form and using the session to store and control the token submitted by the user.
When using the FrameworkBundle, this protection can be enabled or disabled with the configuration. If the configuration is not specified, by default, the mechanism is enabled as long as the session is enabled.
In a recent change in the way the configuration is loaded, the default behavior has been dropped and, as a result, the CSRF protection is not enabled in form when not explicitly enabled, which makes the application sensible to CSRF attacks.
Resolution
----------
Symfony restored the default configuration to enable the CSRF protection by default.
The patch for this issue is available [here](https://github.com/symfony/symfony/commit/f0ffb775febdf07e57117aabadac96fa37857f50) for branch 5.3.
Credits
-------
We would like to thank Catalin Dan and David Lochner for reporting the issue and Jérémy Derussé for fixing the issue. | {'CVE-2022-23601'} | 2022-02-07T22:11:10Z | 2022-02-01T00:46:57Z | HIGH | null | {'CWE-352'} | {'https://github.com/symfony/symfony/', 'https://github.com/symfony/symfony/commit/f0ffb775febdf07e57117aabadac96fa37857f50', 'https://github.com/symfony/symfony/security/advisories/GHSA-vvmr-8829-6whx', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23601'} | null | {'https://github.com/symfony/symfony/commit/f0ffb775febdf07e57117aabadac96fa37857f50'} | {'https://github.com/symfony/symfony/commit/f0ffb775febdf07e57117aabadac96fa37857f50'} |
Packagist | GHSA-26rr-v2j2-25fh | Layout XML Arbitrary Code Fix | ### Impact
Layout XML enabled admin users to execute arbitrary commands via block methods. | {'CVE-2021-32758'} | 2021-08-30T16:42:41Z | 2021-08-30T17:20:52Z | HIGH | null | {'CWE-91'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-32758', 'https://github.com/OpenMage/magento-lts/security/advisories/GHSA-26rr-v2j2-25fh', 'https://github.com/OpenMage/magento-lts/commit/b99307d00b59c4a226a1e3e4083f02cf2fc8fce7', 'https://github.com/OpenMage/magento-lts/releases/tag/v20.0.13', 'https://github.com/OpenMage/magento-lts/releases/tag/v19.4.15'} | null | {'https://github.com/OpenMage/magento-lts/commit/b99307d00b59c4a226a1e3e4083f02cf2fc8fce7'} | {'https://github.com/OpenMage/magento-lts/commit/b99307d00b59c4a226a1e3e4083f02cf2fc8fce7'} |
Packagist | GHSA-8c76-mxv5-w4g8 | Stored Cross-site Scripting in Microweber | Microweber 1.2.11 and prior contains multiple stored cross-site scripting vulnerabilities in Shop's Other Settings, Shop's Autorespond E-mail Settings and Shops' Payments Methods. | {'CVE-2022-0954'} | 2022-03-28T17:25:37Z | 2022-03-16T00:00:48Z | MODERATE | null | {'CWE-79'} | {'https://huntr.dev/bounties/b99517c0-37fc-4efa-ab1a-3591da7f4d26', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0954', 'https://github.com/microweber/microweber/commit/955471c27e671c49e4b012e3b120b004082ac3f7', 'https://github.com/microweber/microweber'} | null | {'https://github.com/microweber/microweber/commit/955471c27e671c49e4b012e3b120b004082ac3f7'} | {'https://github.com/microweber/microweber/commit/955471c27e671c49e4b012e3b120b004082ac3f7'} |
Packagist | GHSA-h86j-6h6m-qjqw | Cross-Site Request Forgery in remdex/livehelperchat | An attacker is able to log out a user if a logged-in user visits the attacker's website. While this cannot harm a user's account, it can be a great annoyance and is a valid CSRF. | {'CVE-2021-4049'} | 2021-12-09T17:55:01Z | 2021-12-10T20:26:34Z | LOW | null | {'CWE-352'} | {'https://github.com/livehelperchat/livehelperchat/commit/e7fe1aa6a087d4d21b2e8a0dadd2e08f42acbb57', 'https://github.com/livehelperchat/livehelperchat', 'https://huntr.dev/bounties/62408fa4-2c16-4fcd-8b34-41fcdccb779e', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4049'} | null | {'https://github.com/livehelperchat/livehelperchat/commit/e7fe1aa6a087d4d21b2e8a0dadd2e08f42acbb57'} | {'https://github.com/livehelperchat/livehelperchat/commit/e7fe1aa6a087d4d21b2e8a0dadd2e08f42acbb57'} |
Packagist | GHSA-5mv2-rx3q-4w2v | Code injection in Twig | # Description
When in a sandbox mode, the `arrow` parameter of the `sort` filter must be a closure to avoid attackers being able to run arbitrary PHP functions.
# Resolution
We now disallow calling non Closure in the `sort` filter like we already did for some other filters.
# Credits
We would like to thank Marlon Starkloff for reporting the issue and Fabien Potencier for fixing the issue.
| {'CVE-2022-23614'} | 2022-02-11T19:16:32Z | 2022-02-10T22:21:48Z | HIGH | null | {'CWE-74'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PECHIY2XLWUH2WLCNPDGNFMPHPRPCEDZ/', 'https://www.debian.org/security/2022/dsa-5107', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23614', 'https://github.com/twigphp/Twig/', 'https://github.com/twigphp/Twig/commit/22b9dc3c03ee66d7e21d9ed2ca76052b134cb9e9', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/I2PVV5DUTRUECTIHMTWRI5Z7DVNYQ2YO/', 'https://github.com/twigphp/Twig/commit/2eb33080558611201b55079d07ac88f207b466d5', 'https://github.com/twigphp/Twig/security/advisories/GHSA-5mv2-rx3q-4w2v', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OTN4273U4RHVIXED64T7DSMJ3VYTPRE7/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SIGZCFSYLPP7UVJ4E4NLHSOQSKYNXSAD/'} | null | {'https://github.com/twigphp/Twig/commit/22b9dc3c03ee66d7e21d9ed2ca76052b134cb9e9', 'https://github.com/twigphp/Twig/commit/2eb33080558611201b55079d07ac88f207b466d5'} | {'https://github.com/twigphp/Twig/commit/22b9dc3c03ee66d7e21d9ed2ca76052b134cb9e9', 'https://github.com/twigphp/Twig/commit/2eb33080558611201b55079d07ac88f207b466d5'} |
Packagist | GHSA-cpxc-67rc-c775 | Cross Site Scripting in baserCMS | baserCMS 4.3.6 and earlier is affected by Cross Site Scripting (XSS).
* Impact: XSS via Arbitrary script execution.
* Attack vector is: Administrator must be logged in.
* Components are: content_fields.php, content_info.php, content_options.php, content_related.php, index_list_tree.php, jquery.bcTree.js
* Tested baserCMS Version : 4.3.6 (Latest)
* Affected baserCMS Version : 4.0.0 ~ 4.3.6
* Patches : https://basercms.net/security/20200827
Found by Aquilao Null | {'CVE-2020-15154'} | 2021-01-07T23:39:30Z | 2020-08-28T20:48:12Z | LOW | null | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15154', 'https://basercms.net/security/20200827', 'https://github.com/baserproject/basercms/security/advisories/GHSA-cpxc-67rc-c775', 'https://github.com/baserproject/basercms/commit/7f4b905b90954e394ec10dd35bad2a5dec505371'} | null | {'https://github.com/baserproject/basercms/commit/7f4b905b90954e394ec10dd35bad2a5dec505371'} | {'https://github.com/baserproject/basercms/commit/7f4b905b90954e394ec10dd35bad2a5dec505371'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.