ecosystem
stringclasses 14
values | vuln_id
stringlengths 10
19
| summary
stringlengths 4
267
⌀ | details
stringlengths 9
13.5k
| aliases
stringlengths 17
144
⌀ | modified_date
stringdate 2010-05-27 05:47:00
2022-05-10 08:46:52
| published_date
stringdate 2005-12-31 05:00:00
2022-05-10 08:46:50
| severity
stringclasses 5
values | score
float64 0
10
⌀ | cwe_id
stringclasses 988
values | refs
stringlengths 30
17.7k
⌀ | introduced
stringlengths 75
4.26k
⌀ |
|---|---|---|---|---|---|---|---|---|---|---|---|
npm
|
GHSA-v26w-gcxh-v4r7
|
Prototype polluation in just-safe-set
|
Prototype pollution vulnerability in ‘just-safe-set’ versions 1.0.0 through 2.2.1 allows an attacker to cause a denial of service and may lead to remote code execution.
|
{'CVE-2021-25952'}
|
2021-10-21T13:55:53Z
|
2021-12-10T18:50:40Z
|
CRITICAL
| null |
{'CWE-915', 'CWE-1321'}
|
{'https://github.com/angus-c/just/commit/dd57a476f4bb9d78c6f60741898dc04c71d2eb53', 'https://github.com/angus-c/just/pull/267', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25952', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25952', 'https://github.com/angus-c/just'}
| null |
npm
|
GHSA-5cv7-r488-wc5x
|
Hijacked Environment Variables in noderequest
|
The `noderequest` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.
All versions have been unpublished from the npm registry.
## Recommendation
As this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.
If you have found this installed in your environment, you should:
1. Delete the package
2. Clear your npm cache
3. Ensure it is not present in any other package.json files on your system
4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.
Additionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.
|
{'CVE-2017-16073'}
|
2020-08-31T18:25:57Z
|
2018-09-17T20:39:17Z
|
MODERATE
| null |
{'CWE-506'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2017-16073', 'https://www.npmjs.com/advisories/512', 'https://nodesecurity.io/advisories/512', 'https://github.com/advisories/GHSA-5cv7-r488-wc5x'}
| null |
npm
|
GHSA-4qhx-g9wp-g9m6
|
Failure to sanitize quotes which can lead to sql injection in squel
|
All versions of `squel` are vulnerable to sql injection.
The `squel` package does not properly escape user provided input when provided using the `setFields` method. This could lead to sql injection if the query was then executed.
Proof of concept demonstrating the injection of a single quote into a generated sql statement from user provided input.
```
> console.log(squel.insert().into('buh').setFields({foo: "bar'baz"}).toString());
INSERT INTO buh (foo) VALUES ('bar'baz')
```
## Recommendation
There is no fix at this time and the issue has been reported publicly. Consider using another query builder that provides strong guarantees for input sanitization to prevent sql injection attacks.
| null |
2021-09-16T21:00:23Z
|
2019-06-14T16:09:01Z
|
CRITICAL
| null |
{'CWE-74', 'CWE-89'}
|
{'https://github.com/hiddentao/squel/issues/350', 'https://www.npmjs.com/advisories/575', 'https://github.com/hiddentao/squel'}
| null |
npm
|
GHSA-x44x-r84w-8v67
|
Lack of URL normalization may lead to authorization bypass when URL access rules are used
|
### Impact
When access rules are used inside a protected host, some URL encodings may bypass filtering system.
### Patches
Version 0.5.2 includes a patch that fixes the vulnerability
### Workarounds
No way for users to fix or remediate the vulnerability without upgrading
### References
https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/issues/2290
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [this repository](https://github.com/LemonLDAPNG/node-lemonldap-ng-handler/issues) or [LemonLDAP::NG GitLab](https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/issues)
* Email us at [lemonldap-ng-users@ow2.org](mailto:lemonldap-ng-users@ow2.org)
|
{'CVE-2020-24660'}
|
2021-10-04T21:15:52Z
|
2020-09-09T18:45:55Z
|
MODERATE
| null |
{'CWE-287'}
|
{'https://github.com/LemonLDAPNG/node-lemonldap-ng-handler/security/advisories/GHSA-x44x-r84w-8v67', 'https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/issues/2290', 'https://github.com/LemonLDAPNG/node-lemonldap-ng-handler/commit/136aa83ed431462fa42ce17b7f9b24e056de06be', 'https://snyk.io/vuln/SNYK-JS-NODELEMONLDAPNGHANDLER-655999', 'https://www.debian.org/security/2020/dsa-4762', 'https://www.npmjs.com/package/lemonldap-ng-handler', 'https://nvd.nist.gov/vuln/detail/CVE-2020-24660', 'https://github.com/LemonLDAPNG/node-lemonldap-ng-handler/releases/tag/0.5.2', 'https://github.com/LemonLDAPNG/node-lemonldap-ng-handler'}
| null |
npm
|
GHSA-rwmv-c7v8-v9vf
|
Malicious Package in bitcoimd-rpc
|
All versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.
## Recommendation
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer.
The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
| null |
2021-10-01T20:40:15Z
|
2020-09-04T16:36:45Z
|
CRITICAL
| null |
{'CWE-506'}
|
{'https://www.npmjs.com/advisories/1363'}
| null |
npm
|
GHSA-j6p2-cx3w-6jcp
|
Cross-Site Scripting in backbone
|
Affected versions of `backbone` are vulnerable to cross-site scripting when users are allowed to supply input to the `Model#Escape` function, and the output is then written to the DOM.
The vulnerability occurs as a result of the regular expression used to encode metacharacters failing to take HTML Entities such as `<` into account.
## Recommendation
Update to version 0.5.0 or later.
|
{'CVE-2016-10537'}
|
2020-08-31T18:11:06Z
|
2019-02-18T23:39:55Z
|
HIGH
| null |
{'CWE-79'}
|
{'https://github.com/jashkenas/backbone/compare/0.3.3...0.5.0#diff-0d56d0d310de7ff18b3cef9c2f8f75dcL1008', 'https://nodesecurity.io/advisories/108', 'https://github.com/advisories/GHSA-j6p2-cx3w-6jcp', 'https://www.npmjs.com/advisories/108', 'https://backbonejs.org/#changelog', 'https://github.com/jashkenas/backbone/commit/0cdc525961d3fa98e810ffae6bcc8e3838e36d93', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10537'}
| null |
npm
|
GHSA-8cv5-p934-3hwp
|
Denial of service in fast-csv
|
### Impact
Possible ReDoS (Regular Expression Denial of Service) when using `ignoreEmpty` option when parsing.
### Patches
This has been patched in `v4.3.6`
### Workarounds
You will only be affected by this if you use the `ignoreEmpty` parsing option. If you do use this option it is recommended that you upgrade to the latest version `v4.3.6`
### References
This vulnerability was found using a [CodeQL](https://securitylab.github.com/tools/codeql) query which identified `EMPTY_ROW_REGEXP` regular expression as vulnerable.
[Link to query run](https://lgtm.com/query/8609731774537641779/).
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [fast-csv](https://github.com/C2FO/fast-csv)
|
{'CVE-2020-26256'}
|
2021-10-08T20:36:36Z
|
2020-12-08T21:42:53Z
|
LOW
| null |
{'CWE-400'}
|
{'https://github.com/C2FO/fast-csv/security/advisories/GHSA-8cv5-p934-3hwp', 'https://lgtm.com/query/8609731774537641779/', 'https://github.com/C2FO/fast-csv/issues/540', 'https://github.com/C2FO/fast-csv', 'https://github.com/C2FO/fast-csv/commit/4bbd39f26a8cd7382151ab4f5fb102234b2f829e', 'https://www.npmjs.com/advisories/1587', 'https://www.npmjs.com/advisories/1588', 'https://www.npmjs.com/package/fast-csv', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26256', 'https://www.npmjs.com/package/@fast-csv/parse'}
| null |
npm
|
GHSA-8pwx-j4r6-5v38
|
Malicious Package in hdkye
|
All versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.
## Recommendation
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer.
The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
| null |
2021-10-01T21:02:37Z
|
2020-09-03T17:05:25Z
|
CRITICAL
| null |
{'CWE-506'}
|
{'https://www.npmjs.com/advisories/1399'}
| null |
npm
|
GHSA-4vj3-f849-5r48
|
Arbitrary File Read in Snyk Broker
|
All versions of snyk-broker before 4.80.0 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users with access to Snyk's internal network by creating symlinks to match whitelisted paths.
|
{'CVE-2020-7653'}
|
2021-07-29T17:23:47Z
|
2020-06-03T22:02:21Z
|
MODERATE
| null |
{'CWE-59'}
|
{'https://updates.snyk.io/snyk-broker-security-fixes-152338', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7653', 'https://snyk.io/vuln/SNYK-JS-SNYKBROKER-570612'}
| null |
npm
|
GHSA-4v2w-h9jm-mqjg
|
Prototype Pollution in systeminformation
|
### Impact
command injection vulnerability by prototype pollution
### Patches
Problem was fixed with a rewrite of shell sanitations to avoid prototyper pollution problems. Please upgrade to version >= 4.30.2
### Workarounds
If you cannot upgrade, be sure to check or sanitize service parameter strings that are passed to si.inetChecksite()
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [systeminformation](https://github.com/sebhildebrandt/systeminformation/issues/new?template=bug_report.md)
|
{'CVE-2020-26245'}
|
2021-01-07T22:40:03Z
|
2020-11-27T16:07:15Z
|
MODERATE
| null |
{'CWE-471', 'CWE-78'}
|
{'https://github.com/sebhildebrandt/systeminformation/commit/8113ff0e87b2f422a5756c48f1057575e73af016', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26245', 'https://github.com/sebhildebrandt/systeminformation/security/advisories/GHSA-4v2w-h9jm-mqjg'}
| null |
npm
|
GHSA-c3h5-qchh-46hh
|
Directory Traversal in yyooopack
|
Affected versions of `yyooopack` resolve relative file paths, resulting in a directory traversal vulnerability. A malicious actor can use this vulnerability to access files outside of the intended directory root, which may result in the disclosure of private files on the vulnerable system.
Example request:
```
GET /../../../../../../../../../../etc/passwd HTTP/1.1
host:foo
```
## Recommendation
No patch is available for this vulnerability.
It is recommended that the package is only used for local development, and if the functionality is needed for production, a different package is used instead.
|
{'CVE-2017-16167'}
|
2020-08-31T18:21:53Z
|
2020-09-01T17:30:17Z
|
HIGH
| null |
{'CWE-22'}
|
{'https://nodesecurity.io/advisories/400', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16167', 'https://github.com/JacksonGL/NPM-Vuln-PoC/blob/master/directory-traversal/yyooopack', 'https://www.npmjs.com/advisories/400'}
| null |
npm
|
GHSA-593v-wcqx-hq2w
|
Incorrect version tags linked to external repository
|
### Impact
A security incident caused a number of incorrect version tags to be pushed to the Parse Server repository. These version tags linked to a personal fork of a contributor who had write access to the repository. The code to which these tags linked has not been reviewed or approved by Parse Platform. Even though no releases were published with these incorrect versions, it was possible to define a Parse Server dependency that pointed to these version tags, for example if you defined this dependency:
```js
"parse-server": "git@github.com:parse-community/parse-server.git#4.9.3"
```
We have since deleted the incorrect version tags, but they may still show up in your personal fork on GitHub or locally. We do not know when these tags have been pushed to the Parse Server repository, but we first became aware of this issue on July 21, 2021. We are not aware of any malicious code or concerns related to privacy, security or legality (e.g. proprietary code). However, it has been reported that some functionality does not work as expected and the introduction of security vulnerabilities cannot be ruled out.
You may be also affected if you used the Bitnami image for Parse Server. Bitnami picked up the incorrect version tag `4.9.3` and published a new Bitnami image for Parse Server.
**If you are using any of the affected versions, we urgently recommend to upgrade to version `4.10.0`.**
These are the incorrect tags:
```
4.0.0-beta1
4.0.0-beta2
4.0.0-beta3
4.0.0-beta4
4.0.0-beta5
4.0.0-beta6
4.0.10
4.0.11
4.0.12
4.0.13
4.0.14
4.0.3
4.0.4
4.0.6
4.0.7
4.0.8
4.0.9
4.6.0
4.6.0-beta
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.9.0
4.9.1
4.9.2
4.9.3
```
### Patches
Upgrade to version `4.10.0`.
### Workarounds
Downgrade to version `4.5.2`.
### References
n/a
| null |
2021-09-03T21:34:00Z
|
2021-09-07T22:57:58Z
|
CRITICAL
| null | null |
{'https://github.com/parse-community/parse-server/security/advisories/GHSA-593v-wcqx-hq2w', 'https://github.com/parse-community/parse-server'}
| null |
npm
|
GHSA-r36x-p5pv-9mfx
|
Downloads Resources over HTTP in prebuild-lwip
|
Affected versions of `prebuild-lwip` insecurely download resources over HTTP.
In scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.
## Recommendation
No patch is currently available for this vulnerability.
The best mitigation is currently to avoid using this package, using a different package if available.
Alternatively, the risk of exploitation can be reduced by ensuring that this package is not installed while connected to a public network. If the package is installed on a private network, the only people who can exploit this vulnerability are those who have compromised your network or those who have privileged access to your ISP, such as Nation State Actors or Rogue ISP Employees.
|
{'CVE-2016-10652'}
|
2021-01-08T01:58:10Z
|
2019-02-18T23:45:25Z
|
HIGH
| null |
{'CWE-311'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2016-10652', 'https://nodesecurity.io/advisories/248', 'https://github.com/advisories/GHSA-r36x-p5pv-9mfx', 'https://www.npmjs.com/advisories/248'}
| null |
npm
|
GHSA-332q-7ff2-57h2
|
Prototype Pollution in undefsafe
|
undefsafe before 2.0.3 is vulnerable to Prototype Pollution. The 'a' function could be tricked into adding or modifying properties of Object.prototype using a `__proto__` payload.
|
{'CVE-2019-10795'}
|
2022-02-24T18:21:34Z
|
2022-02-09T22:34:01Z
|
MODERATE
| null |
{'CWE-74'}
|
{'https://snyk.io/vuln/SNYK-JS-UNDEFSAFE-548940', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10795', 'https://github.com/remy/undefsafe/commit/f272681b3a50e2c4cbb6a8533795e1453382c822', 'https://github.com/remy/undefsafe'}
| null |
npm
|
GHSA-52mq-6jcv-j79x
|
User content sandbox can be confused into opening arbitrary documents
|
### Impact
The user content sandbox can be abused to trick users into opening unexpected documents after several user interactions. The content can be opened with a `blob` origin from the Matrix client, so it is possible for a malicious document to access user messages and secrets.
### Patches
This has been fixed by https://github.com/matrix-org/matrix-react-sdk/pull/5657, which is included in 3.15.0.
### Workarounds
There are no known workarounds.
|
{'CVE-2021-21320'}
|
2021-04-14T19:07:25Z
|
2021-03-03T02:23:56Z
|
LOW
| null |
{'CWE-345'}
|
{'https://www.npmjs.com/package/matrix-react-sdk', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21320', 'https://github.com/matrix-org/matrix-react-sdk/security/advisories/GHSA-52mq-6jcv-j79x', 'https://github.com/matrix-org/matrix-react-sdk/pull/5657', 'https://github.com/matrix-org/matrix-react-sdk/commit/b386f0c73b95ecbb6ea7f8f79c6ff5171a8dedd1'}
| null |
npm
|
GHSA-8687-vv9j-hgph
|
Improper Input Validation in Automattic Mongoose
|
Automattic Mongoose through 5.7.4 allows attackers to bypass access control (in some applications) because any query object with a _bsontype attribute is ignored. For example, adding "_bsontype":"a" can sometimes interfere with a query filter. NOTE: this CVE is about Mongoose's failure to work around this _bsontype special case that exists in older versions of the bson parser (aka the mongodb/js-bson project).
|
{'CVE-2019-17426'}
|
2021-07-27T22:16:01Z
|
2019-10-22T20:19:54Z
|
CRITICAL
| null |
{'CWE-20'}
|
{'https://github.com/Automattic/mongoose/commit/f3eca5b94d822225c04e96cbeed9f095afb3c31c', 'https://nvd.nist.gov/vuln/detail/CVE-2019-17426', 'https://github.com/Automattic/mongoose/issues/8222'}
| null |
npm
|
GHSA-m6j2-v3gq-45r5
|
Cross-site Scripting in aurelia-framework
|
The HTMLSanitizer class in html-sanitizer.ts in all released versions of the Aurelia framework 1.x repository is vulnerable to XSS. The sanitizer only attempts to filter SCRIPT elements, which makes it feasible for remote attackers to conduct XSS attacks via (for example) JavaScript code in an attribute of various other elements. An attacker might also exploit a bug in how the SCRIPT string is processed by splitting and nesting them for example.
|
{'CVE-2019-10062'}
|
2022-04-04T20:06:43Z
|
2022-02-10T23:42:39Z
|
MODERATE
| null |
{'CWE-79'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2019-10062', 'https://discourse.aurelia.io/t/xss-vulnerability-in-htmlsanitizer-might-be-insufficiently-handled/4219', 'https://github.com/aurelia/framework/issues/992', 'https://www.gosecure.net/blog/2021/05/12/aurelia-framework-insecure-default-allows-xss/', 'https://github.com/aurelia/templating-resources/blob/0cef07a8cac8e99146d8e1c4b734491bb3dc4724/src/html-sanitizer.js', 'https://github.com/aurelia/framework'}
| null |
npm
|
GHSA-cq77-8jpx-892g
|
Command Injection in killing
|
This affects all versions of package killing up to and including 1.0.6. If attacker-controlled user input is given, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
|
{'CVE-2021-23381'}
|
2021-04-19T21:07:27Z
|
2021-05-06T15:53:32Z
|
HIGH
| null |
{'CWE-77'}
|
{'https://www.npmjs.com/package/killing', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23381', 'https://snyk.io/vuln/SNYK-JS-KILLING-1078532', 'https://github.com/xudafeng/killing/blob/672ed164ccdd10c0a8fb93c5c6d2456f1dfab781/lib/killing.js%23L62'}
| null |
npm
|
GHSA-jcmh-9fvm-j39w
|
Malicious Package in body-parse-xml
|
This package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.
## Recommendation
Remove the package from your environment. There are no indications of further compromise.
| null |
2021-09-30T20:13:39Z
|
2020-09-03T19:42:23Z
|
CRITICAL
| null |
{'CWE-506'}
|
{'https://www.npmjs.com/advisories/1125'}
| null |
npm
|
GHSA-j3g2-m5jj-6336
|
Unsafe Merging of CORS Configuration Conflict in hapi
|
Versions of `hapi` prior to 11.1.4 are affected by a vulnerability that causes route-level CORS configuration to override connection-level or server-level CORS defaults. This may result in a situation where CORS permissions are less restrictive than intended.
## Recommendation
Update hapi to version 11.1.4 or later.
|
{'CVE-2015-9243'}
|
2020-08-31T18:09:51Z
|
2020-09-01T15:20:00Z
|
MODERATE
| null |
{'CWE-284'}
|
{'https://github.com/hapijs/hapi/issues/2980', 'https://www.npmjs.com/advisories/65', 'https://nvd.nist.gov/vuln/detail/CVE-2015-9243', 'https://nodesecurity.io/advisories/65'}
| null |
npm
|
GHSA-23fp-fmrv-f5px
|
Uncontrolled Resource Consumption in strapi
|
A denial of service exists in strapi v3.0.0-beta.18.3 and earlier that can be abused in the admin console using admin rights can lead to arbitrary restart of the application.
|
{'CVE-2020-8123'}
|
2021-03-30T13:53:18Z
|
2021-12-10T17:22:01Z
|
MODERATE
| null |
{'CWE-400'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-8123', 'https://hackerone.com/reports/768574', 'https://github.com/strapi/strapi/commit/c0c191c08f05fe10d7a6b1bf9475c1a651a89362'}
| null |
npm
|
GHSA-mh82-55cm-6gfh
|
Prototype pollution vulnerability in js-extend
|
Prototype pollution vulnerability in 'js-extend' versions 0.0.1 through 1.0.1 allows attacker to cause a denial of service and may lead to remote code execution.
|
{'CVE-2021-25945'}
|
2021-06-04T18:54:41Z
|
2021-06-08T23:16:03Z
|
CRITICAL
| null |
{'CWE-915', 'CWE-1321'}
|
{'https://github.com/vmattos/js-extend', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25945', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25945'}
| null |
npm
|
GHSA-cmcx-xhr8-3w9p
|
Denial of Service in uap-core when processing crafted User-Agent strings
|
### Impact
Some regexes are vulnerable to regular expression denial of service (REDoS) due to overlapping capture groups. This allows remote attackers to overload a server by setting the User-Agent header in an HTTP(S) request to maliciously crafted long strings.
### Patches
Please update uap-core to &amp;gt;= v0.7.3
Downstream packages such as uap-python, uap-ruby etc which depend upon uap-core follow different version schemes.
### Details
Each vulnerable regular expression reported here contains 3 overlapping capture groups. Backtracking has approximately cubic time complexity with respect to the length of the user-agent string.
#### Regex 1:
```
\bSmartWatch *\( *([^;]+) *; *([^;]+) *;
```
is vulnerable in portion ` *([^;]+) *` and can be attacked with
```python
&amp;quot;SmartWatch(&amp;quot; + (&amp;quot; &amp;quot; * 3500) + &amp;quot;z&amp;quot;
```
e.g.
```
SmartWatch( z
```
#### Regex 2:
```
; *([^;/]+) Build[/ ]Huawei(MT1-U06|[A-Z]+\d+[^\);]+)[^\);]*\)
```
is vulnerable in portion `\d+[^\);]+[^\);]*` and can be attacked with
```python
&amp;quot;;A Build HuaweiA&amp;quot; + (&amp;quot;4&amp;quot; * 3500) + &amp;quot;z&amp;quot;
```
#### Regex 3:
```
(HbbTV)/[0-9]+\.[0-9]+\.[0-9]+ \([^;]*; *(LG)E *; *([^;]*) *;[^;]*;[^;]*;\)
```
is vulnerable in portion ` *([^;]*) *` and can be attacked with
```python
&amp;quot;HbbTV/0.0.0 (;LGE;&amp;quot; + (&amp;quot; &amp;quot; * 3500) + &amp;quot;z&amp;quot;
```
#### Regex 4:
```
(HbbTV)/[0-9]+\.[0-9]+\.[0-9]+ \([^;]*; *(?:CUS:([^;]*)|([^;]+)) *; *([^;]*) *;.*;
```
is vulnerable in portions ` *(?:CUS:([^;]*)|([^;]+)) *` and ` *([^;]*) *` and can be attacked with
```python
&amp;quot;HbbTV/0.0.0 (;CUS:;&amp;quot; + (&amp;quot; &amp;quot; * 3500) + &amp;quot;z&amp;quot;
&amp;quot;HbbTV/0.0.0 (;&amp;quot; + (&amp;quot; &amp;quot; * 3500) + &amp;quot;z&amp;quot;
&amp;quot;HbbTV/0.0.0 (;z;&amp;quot; + (&amp;quot; &amp;quot; * 3500) + &amp;quot;z&amp;quot;
```
Reported by Ben Caller @bcaller
|
{'CVE-2020-5243'}
|
2021-01-08T20:28:57Z
|
2020-02-20T23:26:10Z
|
HIGH
| null |
{'CWE-20'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-5243', 'https://github.com/ua-parser/uap-core/commit/0afd61ed85396a3b5316f18bfd1edfaadf8e88e1', 'https://github.com/ua-parser/uap-core/security/advisories/GHSA-cmcx-xhr8-3w9p'}
| null |
npm
|
GHSA-549f-73hh-mj38
|
Command Injection in gitlabhook
|
All versions of `gitlabhook` are vulnerable to Command Injection. The package does not validate input the body of POST request and concatenates it to an exec call, allowing attackers to run arbitrary commands in the system.
## Recommendation
No fix is currently available. Consider using an alternative package until a fix is made available.
|
{'CVE-2019-5485'}
|
2020-08-31T18:49:59Z
|
2019-09-16T22:24:02Z
|
CRITICAL
| null |
{'CWE-78'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2019-5485', 'https://www.npmjs.com/advisories/1174', 'https://hackerone.com/reports/685447', 'http://packetstormsecurity.com/files/154598/NPMJS-gitlabhook-0.0.17-Remote-Command-Execution.html'}
| null |
npm
|
GHSA-c4qr-gmr9-v23w
|
Prefix escape
|
### Impact
By crafting a specific URL, it is possible to escape the prefix of the proxied backend service.
If the base url of the proxied server is `/pub/`, a user expect that accessing `/priv` on the target service would not be possible. Unfortunately, it is.
[CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N)
### Patches
All releases after v4.3.1 include the fix.
### Workarounds
There are no workaround available.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [fastify-reply-from](https://github.com/fastify/fastify-reply-from)
* Email us at [hello@matteocollina.com](mailto:hello@matteocollina.com)
|
{'CVE-2021-21322'}
|
2021-03-02T03:32:25Z
|
2021-03-03T02:18:08Z
|
LOW
| null |
{'CWE-20'}
|
{'https://www.npmjs.com/package/fastify-http-proxy', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21322', 'https://github.com/fastify/fastify-http-proxy/commit/02d9b43c770aa16bc44470edecfaeb7c17985016', 'https://github.com/fastify/fastify-http-proxy/security/advisories/GHSA-c4qr-gmr9-v23w'}
| null |
npm
|
GHSA-8j7x-pr59-m5h8
|
Malicious Package in whiteproject
|
All versions of `whiteproject` contain obfuscated malware that uploads Discord user tokens to a remote server. This allows attackers to make purchases on behalf of users if they have credit cards linked to their Discord accounts.
## Recommendation
Remove the package from your environment. Review your Discord account access and rotate tokens if possible. If a credit card was linked to a compromised account contact your credit card company.
| null |
2021-09-30T21:37:21Z
|
2020-09-02T21:31:18Z
|
CRITICAL
| null |
{'CWE-506'}
|
{'https://www.npmjs.com/advisories/898'}
| null |
npm
|
GHSA-7696-qr5q-pg37
|
Malicious Package in zs-sha3
|
Version 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.
## Recommendation
Remove the package from your environment. Ensure no Ethereum funds were compromised.
| null |
2021-10-01T16:10:59Z
|
2020-09-03T23:19:08Z
|
CRITICAL
| null |
{'CWE-506'}
|
{'https://www.npmjs.com/advisories/1299'}
| null |
npm
|
GHSA-7h43-gx24-p529
|
Prototype pollution in json8
|
This affects the package json8 before 1.0.3. The function adds in the target object the property specified in the path, however it does not properly check the key being set, leading to a prototype pollution.
|
{'CVE-2020-7770'}
|
2021-04-19T22:36:51Z
|
2021-05-10T19:17:05Z
|
CRITICAL
| null |
{'CWE-1321'}
|
{'https://github.com/sonnyp/JSON8/commit/2e890261b66cbc54ae01d0c79c71b0fd18379e7e', 'https://snyk.io/vuln/SNYK-JS-JSON8-1017116', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7770', 'https://www.npmjs.com/package/json8'}
| null |
npm
|
GHSA-jgqf-hwc5-hh37
|
Root Path Disclosure in send
|
Versions of `send` prior to 0.11.2 are affected by an information leakage vulnerability which may allow an attacker to enumerate paths on the server filesystem.
## Recommendation
Update to version 0.11.1 or later.
|
{'CVE-2015-8859'}
|
2021-09-14T19:42:25Z
|
2017-10-24T18:33:36Z
|
MODERATE
| null |
{'CWE-200'}
|
{'https://nodesecurity.io/advisories/56', 'https://github.com/advisories/GHSA-jgqf-hwc5-hh37', 'https://www.npmjs.com/advisories/56', 'http://www.openwall.com/lists/oss-security/2016/04/20/11', 'https://nvd.nist.gov/vuln/detail/CVE-2015-8859', 'https://github.com/pillarjs/send', 'https://github.com/expressjs/serve-static/blob/master/HISTORY.md#181--2015-01-20', 'http://www.securityfocus.com/bid/96435', 'https://github.com/pillarjs/send/pull/70'}
| null |
npm
|
GHSA-73wv-v82c-xmqv
|
Malicious Package in buffep-xor
|
Version 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.
## Recommendation
Remove the package from your environment. Ensure no Ethereum funds were compromised.
| null |
2021-09-29T20:58:02Z
|
2020-09-03T21:50:51Z
|
CRITICAL
| null |
{'CWE-506'}
|
{'https://www.npmjs.com/advisories/1240'}
| null |
npm
|
GHSA-rhc3-76jw-4f2x
|
Denial of Service in @commercial/ammo
|
Versions of `@commercial/ammo` prior to 2.1.1 are vulnerable to Denial of Service. The Range HTTP header parser has a vulnerability which will cause the function to throw a system error if the header is set to an invalid value. Because hapi is not expecting the function to ever throw, the error is thrown all the way up the stack. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.
## Recommendation
Upgrade to version 2.1.1 or later.
| null |
2020-08-31T19:00:35Z
|
2020-09-04T17:58:46Z
|
HIGH
| null | null |
{'https://www.npmjs.com/advisories/1473'}
| null |
npm
|
GHSA-hfc6-79wv-5hpw
|
Malicious Package in blingjs
|
Version 0.0.4 of `blingjs` contained malicious code. The code when executed in the browser would enumerate password, cvc, cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`
## Recommendation
If version 0.0.4 of this module is found installed you will want to replace it with a version before or after 0.0.4. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.
| null |
2021-09-24T16:47:49Z
|
2020-09-01T19:48:13Z
|
CRITICAL
| null |
{'CWE-506'}
|
{'https://github.com/jamiller619/blingjs', 'https://www.npmjs.com/advisories/619', 'https://snyk.io/vuln/SNYK-JS-BLINGJS-451007'}
| null |
npm
|
GHSA-6x77-rpqf-j6mw
|
High severity vulnerability that affects ejs
|
nodejs ejs version older than 2.5.5 is vulnerable to a denial-of-service due to weak input validation in the ejs.renderFile()
|
{'CVE-2017-1000189'}
|
2021-09-02T19:10:58Z
|
2018-03-05T18:54:33Z
|
HIGH
| null |
{'CWE-20'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2017-1000189', 'https://github.com/mde/ejs/commit/49264e0037e313a0a3e033450b5c184112516d8f', 'https://github.com/advisories/GHSA-6x77-rpqf-j6mw', 'http://www.securityfocus.com/bid/101893', 'https://github.com/mde/ejs'}
| null |
npm
|
GHSA-p788-rj37-357w
|
Insecure Defaults Leads to Potential MITM in ezseed-transmission
|
Affected versions of `ezseed-transmission` download and run a script over an HTTP connection.
An attacker in a privileged network position could launch a Man-in-the-Middle attack and intercept the script, replacing it with malicious code, completely compromising the system running `ezseed-transmission`.
## Recommendation
Update to version 0.0.15 or later.
|
{'CVE-2016-1000224'}
|
2021-09-23T21:28:12Z
|
2020-09-01T15:26:35Z
|
MODERATE
| null |
{'CWE-295', 'CWE-300'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2016-1000224', 'https://snyk.io/vuln/npm:ezseed-transmission:20160729', 'https://www.npmjs.com/advisories/114'}
| null |
npm
|
GHSA-jjv7-qpx3-h62q
|
Denial-of-Service Memory Exhaustion in qs
|
Versions prior to 1.0 of `qs` are affected by a denial of service condition. This condition is triggered by parsing a crafted string that deserializes into very large sparse arrays, resulting in the process running out of memory and eventually crashing.
## Recommendation
Update to version 1.0.0 or later.
|
{'CVE-2014-7191'}
|
2021-09-14T19:46:47Z
|
2017-10-24T18:33:36Z
|
HIGH
| null | null |
{'http://secunia.com/advisories/62170', 'https://access.redhat.com/errata/RHSA-2016:1380', 'https://github.com/advisories/GHSA-jjv7-qpx3-h62q', 'https://github.com/raymondfeng/node-querystring/commit/43a604b7847e56bba49d0ce3e222fe89569354d8', 'http://www-01.ibm.com/support/docview.wss?uid=swg21687928', 'http://secunia.com/advisories/60026', 'https://github.com/visionmedia/node-querystring', 'http://www-01.ibm.com/support/docview.wss?uid=swg21685987', 'https://nvd.nist.gov/vuln/detail/CVE-2014-7191', 'https://www.npmjs.com/advisories/29', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/96729', 'https://nodesecurity.io/advisories/qs_dos_memory_exhaustion', 'http://www-01.ibm.com/support/docview.wss?uid=swg21687263', 'https://github.com/visionmedia/node-querystring/issues/104'}
| null |
npm
|
GHSA-gwpf-62xp-vrg6
|
Information Exposure in cordova-android
|
Versions of `cordova-android` prior to 6.0.0 are vulnerable to Information Exposure through log files. The application calls methods of the Log class. Messages passed to these methods (Log.v(), Log.d(), Log.i(), Log.w(), and Log.e()) are stored in a series of circular buffers on the device. By default, a maximum of four 16 KB rotated logs are kept in addition to the current log. The logged data can be read using Logcat on the device. When using platforms prior to Android 4.1 (Jelly Bean), the log data is not sandboxed per application; any application installed on the device has the capability to read data logged by other applications.
## Recommendation
Upgrade to version 6.0.0 or later.
|
{'CVE-2016-6799'}
|
2021-09-28T16:53:04Z
|
2020-09-11T21:14:49Z
|
HIGH
| null |
{'CWE-532'}
|
{'https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6799', 'https://nvd.nist.gov/vuln/detail/CVE-2016-6799', 'https://snyk.io/vuln/SNYK-JS-CORDOVAANDROID-174935', 'http://www.securityfocus.com/bid/98365', 'https://github.com/apache/cordova-android', 'https://www.npmjs.com/advisories/964', 'https://lists.apache.org/thread.html/1f3e7b0319d64b455f73616f572acee36fbca31f87f5b2e509c45b69@%3Cdev.cordova.apache.org%3E', 'https://github.com/apache/cordova-android/commit/4a0a7bc424fae14c9689f4a8a2dc250ae3a47f82'}
| null |
npm
|
GHSA-p9vv-3945-x93h
|
Cross-Site Scripting in semantic-ui-search
|
All versions of `semantic-ui-search` are vulnerable to Cross-Site Scripting. Lack of output encoding on the selection dropdowns can lead to user input being executed instead of printed as text.
## Recommendation
No fix is currently available. Consider using an alternative module until a fix is made available.
| null |
2021-09-27T13:59:52Z
|
2020-09-02T15:47:10Z
|
HIGH
| null |
{'CWE-79'}
|
{'https://github.com/Semantic-Org/Semantic-UI', 'https://github.com/Semantic-Org/Semantic-UI/issues/4498', 'https://www.npmjs.com/advisories/760'}
| null |
npm
|
GHSA-mrx7-8hxf-f853
|
Cross-Site Scripting in swagger-ui
|
Affected versions of `swagger-ui` are vulnerable to cross-site scripting. This vulnerability exists because `swagger-ui` automatically executes external Javascript that is loaded in via the `url` query string parameter when a `Content-Type: application/javascript` header is included.
An attacker can create a server that replies with a malicious script and the proper content-type, and then craft a `swagger-ui` URL that includes the location to their server/script in the `url` query string parameter. When viewed, such a link would execute the attacker's malicious script.
## Recommendation
Update to 2.2.1 or later.
|
{'CVE-2016-1000233'}
|
2021-09-23T21:33:20Z
|
2020-09-01T15:36:27Z
|
HIGH
| null |
{'CWE-79'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2016-1000233', 'https://www.npmjs.com/advisories/131', 'https://github.com/swagger-api/swagger-ui/', 'https://github.com/swagger-api/swagger-ui/issues/1863'}
| null |
npm
|
GHSA-vrr3-5r3v-7xfw
|
Improperly Controlled Modification of Dynamically-Determined Object Attributes in casperjs
|
The mergeObjects utility function is susceptible to Prototype Pollution.
|
{'CVE-2020-7679'}
|
2022-01-04T19:27:22Z
|
2021-05-17T21:00:52Z
|
HIGH
| null |
{'CWE-915'}
|
{'https://github.com/casperjs/casperjs/blob/master/modules/utils.js%23L680', 'https://snyk.io/vuln/SNYK-JS-CASPERJS-572803', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7679', 'https://github.com/casperjs/casperjs', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-572804'}
| null |
npm
|
GHSA-7mc5-chhp-fmc3
|
Regular Expression Denial of Service in negotiator
|
Affected versions of `negotiator` are vulnerable to regular expression denial of service attacks, which trigger upon parsing a specially crafted `Accept-Language` header value.
## Recommendation
Update to version 0.6.1 or later.
|
{'CVE-2016-10539'}
|
2020-08-31T18:11:01Z
|
2018-10-09T00:30:30Z
|
HIGH
| null |
{'CWE-400'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2016-10539', 'https://github.com/advisories/GHSA-7mc5-chhp-fmc3', 'https://nodesecurity.io/advisories/106', 'https://www.npmjs.com/advisories/106'}
| null |
npm
|
GHSA-3c9c-2p65-qvwv
|
Prototype pollution in aurelia-path
|
### Impact
The vulnerability exposes Aurelia application that uses `aurelia-path` package to parse a string. The majority of this will be Aurelia applications that employ the `aurelia-router` package. An example is this could allow an attacker to change the prototype of base object class `Object` by tricking an application to parse the following URL: `https://aurelia.io/blog/?__proto__[asdf]=asdf`
### Patches
The problem should be patched in version `1.1.7`. Any version earlier than this is vulnerable.
### Workarounds
A partial work around is to free the Object prototype:
```ts
Object.freeze(Object.prototype)
```
|
{'CVE-2021-41097'}
|
2021-09-27T19:18:37Z
|
2021-09-27T20:12:16Z
|
HIGH
| null |
{'CWE-915', 'CWE-1321'}
|
{'https://github.com/aurelia/path/commit/7c4e235433a4a2df9acc313fbe891758084fdec1', 'https://github.com/aurelia/path/security/advisories/GHSA-3c9c-2p65-qvwv', 'https://www.npmjs.com/package/aurelia-path', 'https://github.com/aurelia/path', 'https://github.com/aurelia/path/releases/tag/1.1.7', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41097', 'https://github.com/aurelia/path/issues/44'}
| null |
npm
|
GHSA-73c6-vwjh-g3qh
|
Malicious Package in crpyto-js
|
All versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.
## Recommendation
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer.
The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
| null |
2021-10-01T21:00:05Z
|
2020-09-03T19:40:46Z
|
CRITICAL
| null |
{'CWE-506'}
|
{'https://www.npmjs.com/advisories/1390'}
| null |
npm
|
GHSA-8gr3-2gjw-jj7g
|
Hidden functionality in node-ipc
|
The package node-ipc version 9.2.2 is vulnerable to hidden functionality that was introduced by the maintainer. The package uses a dependency that writes a file to disk that does not pertain to the functionality of the package and is not included in versions < 9.2.2.
| null |
2022-03-16T23:54:33Z
|
2022-03-16T23:54:33Z
|
LOW
| null |
{'CWE-912'}
|
{'https://github.com/RIAEvangelist/node-ipc', 'https://github.com/RIAEvangelist/node-ipc/releases/tag/9.2.2'}
| null |
npm
|
GHSA-v63x-xc9j-hhvq
|
Sandbox Breakout / Arbitrary Code Execution in safer-eval
|
All versions of `safer-eval` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to restrict access to the main context and is not suited to process arbitrary user input. This may allow attackers to execute arbitrary code in the system.
## Recommendation
The package is not meant to receive user input. Consider using an alternative package until a fix is made available.
|
{'CVE-2019-10769'}
|
2021-07-28T16:43:29Z
|
2019-12-11T02:01:44Z
|
CRITICAL
| null |
{'CWE-94', 'CWE-20'}
|
{'https://www.npmjs.com/advisories/1428', 'https://github.com/commenthol/safer-eval/security/advisories/GHSA-v63x-xc9j-hhvq', 'https://github.com/advisories/GHSA-v63x-xc9j-hhvq', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10769', 'https://snyk.io/vuln/SNYK-JS-SAFEREVAL-534901'}
| null |
npm
|
GHSA-pxpf-v376-7xx5
|
tagify can pass a malicious placeholder to initiate the cross-site scripting (XSS) payload
|
This affects the package @yaireo/tagify before 4.9.8. The package is used for rendering UI components inside the input or text fields, and an attacker can pass a malicious placeholder value to it to fire the cross-site scripting (XSS) payload.
|
{'CVE-2022-25854'}
|
2022-05-03T04:55:32Z
|
2022-04-30T00:00:33Z
|
MODERATE
| null | null |
{'https://nvd.nist.gov/vuln/detail/CVE-2022-25854', 'https://snyk.io/vuln/SNYK-JS-YAIREOTAGIFY-2404358', 'https://github.com/yairEO/tagify/commit/198c0451fad188390390395ccfc84ab371def4c7', 'https://github.com/yairEO/tagify/issues/988', 'https://github.com/yairEO/tagify/releases/tag/v4.9.8', 'https://github.com/yairEO/tagify'}
| null |
npm
|
GHSA-48gc-5j93-5cfq
|
Path Traversal in serve
|
Versions of `serve` prior to 10.1.2 are vulnerable to Path Traversal. Explicitly ignored folders can be accessed through relative paths, which allows attackers to access hidden folders and files.
## Recommendation
Upgrade to version 10.1.2 or later.
| null |
2020-08-31T18:42:15Z
|
2020-09-11T21:15:54Z
|
HIGH
| null |
{'CWE-22'}
|
{'https://hackerone.com/reports/486933', 'https://www.npmjs.com/advisories/965'}
| null |
npm
|
GHSA-476p-r2wx-2wch
|
Downloads Resources over HTTP in ntfserver
|
Affected versions of `ntfserver` insecurely download an executable over an unencrypted HTTP connection.
In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running `ntfserver`.
## Recommendation
No patch is currently available for this vulnerability.
The best mitigation is currently to avoid using this package, using a different package if available.
Alternatively, the risk of exploitation can be reduced by ensuring that this package is not installed while connected to a public network. If the package is installed on a private network, the only people who can exploit this vulnerability are those who have compromised your network or those who have privileged access to your ISP, such as Nation State Actors or Rogue ISP Employees.
|
{'CVE-2016-10650'}
|
2021-01-08T19:56:27Z
|
2019-02-18T23:47:05Z
|
HIGH
| null |
{'CWE-311'}
|
{'https://github.com/advisories/GHSA-476p-r2wx-2wch', 'https://www.npmjs.com/advisories/253', 'https://nodesecurity.io/advisories/253', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10650'}
| null |
npm
|
GHSA-f8vf-6hwg-hw55
|
Malicious Package in bictore-lib
|
All versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.
## Recommendation
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer.
The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
| null |
2021-10-01T20:38:33Z
|
2020-09-04T15:38:21Z
|
CRITICAL
| null |
{'CWE-506'}
|
{'https://www.npmjs.com/advisories/1357'}
| null |
npm
|
GHSA-g7w9-vm5m-48q8
|
Downloads Resources over HTTP in arcanist
|
Affected versions of `arcanist` insecurely download an executable over an unencrypted HTTP connection.
In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running `arcanist`.
## Recommendation
No patch is currently available for this vulnerability.
The best mitigation is currently to avoid using this package, using a different package if available.
Alternatively, the risk of exploitation can be reduced by ensuring that this package is not installed while connected to a public network. If the package is installed on a private network, the only people who can exploit this vulnerability are those who have compromised your network or those who have privileged access to your ISP, such as Nation State Actors or Rogue ISP Employees.
|
{'CVE-2016-10683'}
|
2021-01-08T18:48:48Z
|
2019-02-18T23:42:09Z
|
MODERATE
| null |
{'CWE-311'}
|
{'https://www.npmjs.com/advisories/286', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10683', 'https://github.com/advisories/GHSA-g7w9-vm5m-48q8', 'https://nodesecurity.io/advisories/286'}
| null |
npm
|
GHSA-vm67-7vmg-66vm
|
Arbitrary Command Injection in portprocesses
|
### Impact
An Arbitrary Command Injection vulnerability was reported in `portprocesses` impacting versions <= 1.0.4.
### Example (Proof of Concept)
The following example demonstrates the vulnerability and will run `touch success` therefore creating a file named `success`.
```js
const portprocesses = require("portprocesses");
portprocesses.killProcess("$(touch success)");
```
|
{'CVE-2021-23348'}
|
2021-03-31T17:50:32Z
|
2021-04-06T17:24:50Z
|
MODERATE
| null |
{'CWE-77', 'CWE-78'}
|
{'https://snyk.io/vuln/SNYK-JS-PORTPROCESSES-1078536', 'https://github.com/rrainn/PortProcesses/blob/fffceb09aff7180afbd0bd172e820404b33c8299/index.js%23L23', 'https://github.com/rrainn/PortProcesses/security/advisories/GHSA-vm67-7vmg-66vm', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23348', 'https://github.com/rrainn/PortProcesses/commit/86811216c9b97b01b5722f879f8c88a7aa4214e1'}
| null |
npm
|
GHSA-prmc-5v5w-c465
|
Client TLS credentials sent raw to server in npm package nats
|
Nats is a Node.js client for the NATS messaging system.
## Problem Description
_Preview versions_ of two NPM packages and one Deno package from the NATS project contain an information disclosure flaw, leaking options to the NATS server; for one package, this includes TLS private credentials.
The _connection_ configuration options in these JavaScript-based implementations were fully serialized and sent to the server in the client's `CONNECT` message, immediately after TLS establishment.
The nats.js client supports Mutual TLS and the credentials for the TLS client key are included in the connection configuration options; disclosure of the client's TLS private key to the server has been observed.
Most authentication mechanisms are handled after connection, instead of as part of connection, so other authentication mechanisms are unaffected.
For clarity: NATS account NKey authentication **is NOT affected**.
Neither the nats.ws nor the nats.deno clients support Mutual TLS: the affected versions listed below are those where the logic flaw is
present. We are including the nats.ws and nats.deno versions out of an abundance of caution, as library maintainers, but rate as minimal the likelihood of applications leaking sensitive data.
## Affected versions
### Security impact
* NPM package nats.js:
+ **mainline is unaffected**
+ beta branch is vulnerable from 2.0.0-201, fixed in 2.0.0-209
### Logic flaw
* NPM package nats.ws:
+ status: preview
+ flawed from 1.0.0-85, fixed in 1.0.0-111
* Deno repository https://github.com/nats-io/nats.deno
+ status: preview
+ flawed in all git tags prior to fix
+ fixed with git tag v1.0.0-9
## Impact
For deployments using TLS client certificates (for mutual TLS), private key material for TLS is leaked from the client application to the
server. If the server is untrusted (run by a third party), or if the client application also disables TLS verification (and so the true identity of the server is unverifiable) then authentication credentials are leaked.
## Workaround
*None*
## Solution
Upgrade your package dependencies to fixed versions, and then reissue any TLS client credentials (with new keys, not just new certificates) and revoke the old ones.
| null |
2021-03-31T18:09:39Z
|
2021-04-06T17:32:38Z
|
CRITICAL
| null |
{'CWE-522'}
|
{'https://advisories.nats.io/CVE/CVE-2020-26149.txt', 'https://github.com/nats-io/nats.js/security/advisories/GHSA-prmc-5v5w-c465'}
| null |
npm
|
GHSA-7w7c-867m-4mqc
|
Malicious Package in rceat
|
All versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.
## Recommendation
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer.
The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
| null |
2021-10-01T21:04:09Z
|
2020-09-03T17:04:55Z
|
CRITICAL
| null |
{'CWE-506'}
|
{'https://www.npmjs.com/advisories/1402'}
| null |
npm
|
GHSA-2mvm-66q7-m256
|
Downloads Resources over HTTP in selenium-download
|
Affected versions of `selenium-download` insecurely download an executable over an unencrypted HTTP connection.
In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running `selenium-download`.
## Recommendation
Update to version 2.0.7 or later.
|
{'CVE-2016-10559'}
|
2021-01-08T20:07:08Z
|
2019-02-18T23:40:25Z
|
HIGH
| null |
{'CWE-311'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2016-10559', 'https://github.com/advisories/GHSA-2mvm-66q7-m256', 'https://nodesecurity.io/advisories/164', 'https://www.npmjs.com/advisories/164'}
| null |
npm
|
GHSA-23r4-5mxp-c7g5
|
New anonymous user session acts as if it's created with password
|
### Impact
Developers that use the REST API to signup users and also allow users to login anonymously. When an anonymous user is first signed up using REST, the server creates session incorrectly, particularly the `authProvider` field in `_Session` class under `createdWith` shows the user logged in creating a password. If a developer later depends on the `createdWith` field to provide a different level of access between a password user and anonymous user, the server incorrectly classified the session type as being created with a `password`.
The server currently doesn't use `createdWith` to make decisions on how things work internally, so if a developer isn't using `createdWith` directly, there's nothing to worry about. The vulnerability only affects users who depend on `createdWith` by using it directly.
### Patches
Upgrade to version 4.5.1.
### Workarounds
Don't use the `createdWith` Session field to make decisions if you allow anonymous login.
### References
n/a
|
{'CVE-2021-39138'}
|
2021-08-30T22:05:49Z
|
2021-08-23T19:41:52Z
|
MODERATE
| null |
{'CWE-287'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-39138', 'https://github.com/parse-community/parse-server/commit/147bd9a3dc43391e92c36e05d5db860b04ca27db', 'https://github.com/parse-community/parse-server/releases/tag/4.5.2', 'https://github.com/parse-community/parse-server', 'https://github.com/parse-community/parse-server/security/advisories/GHSA-23r4-5mxp-c7g5'}
| null |
npm
|
GHSA-4fr2-j4g9-mppf
|
Improperly Controlled Modification of Dynamically-Determined Object Attributes in deephas
|
Prototype pollution vulnerability in 'deephas' versions 1.0.0 through 1.0.5 allows attacker to cause a denial of service and may lead to remote code execution.
|
{'CVE-2020-28271'}
|
2021-07-26T18:25:52Z
|
2021-09-24T15:42:21Z
|
CRITICAL
| null |
{'CWE-915'}
|
{'https://github.com/sharpred/deepHas/commit/2fe011713a6178c50f7deb6f039a8e5435981e20', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2020-28271', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2020-28271,', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28271'}
| null |
npm
|
GHSA-559q-92vx-xvjp
|
Malicious Package in qingting
|
All versions of `qingting` contain malicious code. The package uploads system information to a remote server, downloads a file and executes it.
## Recommendation
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer.
The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
| null |
2021-09-30T20:00:23Z
|
2020-09-03T17:44:36Z
|
CRITICAL
| null |
{'CWE-506'}
|
{'https://www.npmjs.com/advisories/1060'}
| null |
npm
|
GHSA-cg42-4wrc-gp47
|
Code Injection in node-extend
|
node-extend through 0.2.0 is vulnerable to Arbitrary Code Execution. User input provided to the argument `A` of `extend` function`(A,B,as,isAargs)` located within `lib/extend.js` is executed by the `eval` function, resulting in code execution.
|
{'CVE-2020-7673'}
|
2021-07-29T18:12:49Z
|
2021-05-17T21:00:37Z
|
CRITICAL
| null |
{'CWE-94'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-7673', 'https://snyk.io/vuln/SNYK-JS-NODEEXTEND-571491'}
| null |
npm
|
GHSA-4w2v-q235-vp99
|
Server-Side Request Forgery in Axios
|
Axios NPM package 0.21.0 contains a Server-Side Request Forgery (SSRF) vulnerability where an attacker is able to bypass a proxy by providing a URL that responds with a redirect to a restricted host or IP address.
|
{'CVE-2020-28168'}
|
2021-01-04T20:57:20Z
|
2021-01-04T20:59:40Z
|
HIGH
| null |
{'CWE-918'}
|
{'https://www.npmjs.com/package/axios', 'https://github.com/axios/axios/commit/c7329fefc890050edd51e40e469a154d0117fc55', 'https://lists.apache.org/thread.html/r25d53acd06f29244b8a103781b0339c5e7efee9099a4d52f0c230e4a@%3Ccommits.druid.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28168', 'https://snyk.io/vuln/SNYK-JS-AXIOS-1038255', 'https://www.npmjs.com/advisories/1594', 'https://lists.apache.org/thread.html/rdfd2901b8b697a3f6e2c9c6ecc688fd90d7f881937affb5144d61d6e@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/r954d80fd18e9dafef6e813963eb7e08c228151c2b6268ecd63b35d1f@%3Ccommits.druid.apache.org%3E', 'https://github.com/axios/axios/issues/3369'}
| null |
npm
|
GHSA-j9f8-8h89-j69x
|
Remote Code Execution in node-os-utils
|
Versions of `node-os-utils` prior to 1.1.0 are vulnerable to Remote Code Execution. Due to insufficient input validation an attacker could run arbitrary commands on the server thus rendering the package vulnerable to Remote Code Execution.
## Recommendation
Upgrade to version 1.1.0 or later.
| null |
2021-08-04T21:06:49Z
|
2019-06-11T16:16:34Z
|
HIGH
| null |
{'CWE-94'}
|
{'https://github.com/SunilWang/node-os-utils/issues/2', 'https://www.npmjs.com/advisories/784', 'https://snyk.io/vuln/SNYK-JS-NODEOSUTILS-173696'}
| null |
npm
|
GHSA-xq8r-r72r-pqwm
|
Downloads Resources over HTTP in roslib-socketio
|
Affected versions of `roslib-socketio` insecurely download an executable over an unencrypted HTTP connection.
In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running `roslib-socketio`.
## Recommendation
No patch is currently available for this vulnerability.
The best mitigation is currently to avoid using this package, using a different package if available.
Alternatively, the risk of exploitation can be reduced by ensuring that this package is not installed while connected to a public network. If the package is installed on a private network, the only people who can exploit this vulnerability are those who have compromised your network or those who have privileged access to your ISP, such as Nation State Actors or Rogue ISP Employees.
|
{'CVE-2016-10681'}
|
2021-06-11T15:15:21Z
|
2020-09-01T16:13:18Z
|
HIGH
| null |
{'CWE-311'}
|
{'https://nodesecurity.io/advisories/292', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10681', 'https://www.npmjs.com/advisories/292'}
| null |
npm
|
GHSA-x4r7-m2q9-69c8
|
GraphiQL introspection schema template injection attack
|
- [1. Impact](#11-impact)
- [2. Scope](#12-scope)
- [3. Patches](#13-patches)
- [3.1 CDN bundle implementations may be automatically patched](#131-cdn-bundle-implementations-may-be-automatically-patched)
- [4. Workarounds for Older Versions](#14-workarounds-for-older-versions)
- [5. How to Re-create the Exploit](#15-how-to-re-create-the-exploit)
- [6. Credit](#16-credit)
- [7. References](#17-references)
- [8. For more information](#18-for-more-information)
This is a security advisory for an XSS vulnerability in `graphiql`.
A similar vulnerability affects `graphql-playground`, a fork of `graphiql`. There is a corresponding `graphql-playground` [advisory](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7) and [Apollo Server advisory](https://github.com/apollographql/apollo-server/security/advisories/GHSA-qm7x-rc44-rrqw).
## 1. Impact
All versions of `graphiql` older than [`graphiql@1.4.7`](https://github.com/graphql/graphiql/releases/tag/v1.4.7) are vulnerable to compromised HTTP schema introspection responses or `schema` prop values with malicious GraphQL type names, exposing a dynamic XSS attack surface that can allow code injection on operation autocomplete.
In order for the attack to take place, the user must load a vulnerable schema in `graphiql`. There are a number of ways that can occur.
By default, the schema URL is _not_ attacker-controllable in `graphiql` or in its suggested implementations or examples, leaving only very complex attack vectors.
If a custom implementation of `graphiql`'s `fetcher` allows the schema URL to be set dynamically, such as a URL query parameter like `?endpoint=` in `graphql-playground`, or a database provided value, then this custom `graphiql` implementation is _vulnerable to phishing attacks_, and thus much more readily available, low or no privelege level xss attacks. The URLs could look like any generic looking graphql schema URL.
Because this exposes an XSS attack surface, it would be possible for a threat actor to exfiltrate user credentials, data, etc. using arbitrary malicious scripts, without it being known to the user.
## 2. Scope
This advisory describes the impact on the `graphiql` package. The vulnerability also affects other projects forked from `graphiql` such as [`graphql-playground`](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7) and the `graphql-playground` fork distributed by Apollo Server. The impact is more severe in the `graphql-playground` implementations; see the [`graphql-playground` advisory](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7) and [Apollo Server advisory](https://github.com/apollographql/apollo-server/security/advisories/GHSA-qm7x-rc44-rrqw) for details.
This vulnerability does not impact `codemirror-graphql`, `monaco-graphql` or other dependents, as it exists in `onHasCompletion.ts` in `graphiql`. It does impact all forks of `graphiql`, and every released version of `graphiql`.
It should be noted that desktop clients such as Altair, Insomnia, Postwoman, do not appear to be impacted by this.
## 3. Patches
`graphiql@1.4.7` addresses this issue via defense in depth.
- **HTML-escaping text** that should be treated as text rather than HTML. In most of the app, this happens automatically because React escapes all interpolated text by default. However, one vulnerable component uses the unsafe `innerHTML` API and interpolated type names directly into HTML. We now properly escape that type name, which fixes the known vulnerability.
- **Validates the schema** upon receiving the introspection response or schema changes. Schemas with names that violate the GraphQL spec will no longer be loaded. (This includes preventing the Doc Explorer from loading.) This change is also sufficient to fix the known vulnerability. You can disable this validation by setting `dangerouslyAssumeSchemaIsValid={true}`, which means you are relying only on escaping values to protect you from this attack.
- **Ensuring that user-generated HTML is safe**. Schemas can contain Markdown in `description` and `deprecationReason` fields, and the web app renders them to HTML using the `markdown-it` library. As part of the development of `graphiql@1.4.7`, we verified that our use of `markdown-it` prevents the inclusion of arbitrary HTML. We use `markdown-it` without setting `html: true`, so we are comfortable relying on [`markdown-it`'s HTML escaping](https://github.com/markdown-it/markdown-it/blob/master/docs/security.md) here. We considered running a second level of sanitization over all rendered Markdown using a library such as `dompurify` but believe that is unnecessary as `markdown-it`'s sanitization appears to be adequate. `graphiql@1.4.7` does update to the latest version of `markdown-it` (v12, from v10) so that any security fixes in v11 and v12 will take effect.
### 3.1 CDN bundle implementations may be automatically patched
Note that if your implementation is depending on a CDN version of `graphiql`, and is pointed to the `latest` tag (usually the default for most cdns if no version is specified) then this issue is already mitigated, in case you were vulnerable to it before.
## 4. Workarounds for Older Versions
If you cannot use `graphiql@1.4.7` or later
- Always use a static URL to a trusted server that is serving a trusted GraphQL schema.
- If you have a custom implementation that allows using user-provided schema URLs via a query parameter, database value, etc, you must either disable this customization, or only allow trusted URLs.
## 5. How to Re-create the Exploit
You can see an example on [codesandbox](https://codesandbox.io/s/graphiql-xss-exploit-gr22f?file=/src/App.js). These are both fixed to the last `graphiql` release `1.4.6` which is the last vulnerable release; however it would work with any previous release of `graphiql`.
Both of these examples are meant to demonstrate the phishing attack surface, so they are customized to accept a `url` parameter. To demonstrate the phishing attack, add `?url=https://graphql-xss-schema.netlify.app/graphql` to the in-codesandbox browser.
Erase the contents of the given query and type `{u`. You will see an alert window open, showing that attacker-controlled code was executed.
Note that when React is in development mode, a validation exception is thrown visibly; however that exception is usually buried in the browser console in a production build of `graphiql`. This validation exception comes from `getDiagnostics`, which invokes `graphql` `validate()` which in turn will `assertValidSchema()`, as `apollo-server-core` does on executing each operation. This validation does not prevent the exploit from being successful.
Note that something like the `url` parameter is not required for the attack to happen if `graphiql`'s `fetcher` is configured in a different way to communicate with a compromised GraphQL server.
## 6. Credit
This vulnerability was discovered by [@Ry0taK](https://github.com/Ry0taK), thank you! :1st_place_medal:
Others who contributed:
- [@imolorhe](https://github.com/imolorhe)
- [@glasser](https://github.com/glasser)
- [@divyenduz](https://github.com/divyenduz)
- [@dotansimha](https://github.com/dotansimha)
- [@acao](https://github.com/acao)
- [@benjie](https://github.com/benjie) and many others who provided morale support
## 7. References
**The vulnerability has always been present**
[In the first commit](https://github.com/graphql/graphiql/commit/b9dec272d89d9c590727fd10d62e4a47e0317fc7#diff-855b77f6310b7e4fb1bcac779cd945092ed49fd759f4684ea391b45101166437R87)
[And later moved to onHasCompletion.js in 2016](https://github.com/graphql/graphiql/commit/6701b0b626e43800e32413590a295e5c1e3d5419#diff-d45eb76aebcffd27d3a123214487116fa95e0b5a11d70a94a0ce3033ce09f879R110) (now `.ts` after the typescript migration)
## 8. For more information
If you have any questions or comments about this advisory:
- Open an issue in [graphiql repo](https://github.com/graphql/graphiql/new/issues)
- Read [more details](https://github.com/graphql/graphiql/blob/main/docs/security/2021-introspection-schema-xss.md#2-more-details-on-the-vulnerability) on the vulnerability
|
{'CVE-2021-41248'}
|
2021-11-04T19:36:52Z
|
2021-11-08T18:03:50Z
|
HIGH
| null |
{'CWE-79'}
|
{'https://github.com/graphql/graphiql/commit/b9dec272d89d9c590727fd10d62e4a47e0317fc7#diff-855b77f6310b7e4fb1bcac779cd945092ed49fd759f4684ea391b45101166437R87', 'https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7', 'https://github.com/graphql/graphiql', 'https://github.com/graphql/graphiql/commit/6701b0b626e43800e32413590a295e5c1e3d5419#diff-d45eb76aebcffd27d3a123214487116fa95e0b5a11d70a94a0ce3033ce09f879R110', 'https://github.com/graphql/graphiql/security/advisories/GHSA-x4r7-m2q9-69c8', 'https://github.com/graphql/graphiql/commit/cb237eeeaf7333c4954c752122261db7520f7bf4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41248', 'https://github.com/graphql/graphiql/blob/main/docs/security/2021-introspection-schema-xss.md#2-more-details-on-the-vulnerability'}
| null |
npm
|
GHSA-m75h-cghq-c8h5
|
Heap Based Buffer Overflow in libyaml
|
Versions 0.2.2 and earlier depend on native libyaml version 0.1.5 or earlier. As such, they are affected by a heap-based buffer overflow vulnerability that may result in a crash or arbitrary code execution when parsing YAML tags.
## Recommendation
- Update to version 0.2.3 that includes a version of LibYAML that contains a fix for this issue.
|
{'CVE-2013-6393'}
|
2021-09-23T20:56:01Z
|
2020-08-31T22:51:50Z
|
CRITICAL
| null |
{'CWE-119'}
|
{'https://bugzilla.redhat.com/attachment.cgi?id=847926&action=diff', 'http://rhn.redhat.com/errata/RHSA-2014-0355.html', 'https://www.npmjs.com/advisories/21', 'https://bitbucket.org/xi/libyaml/commits/bce8b60f0b9af69fa9fab3093d0a41ba243de048', 'https://bitbucket.org/xi/libyaml', 'http://lists.opensuse.org/opensuse-updates/2016-04/msg00050.html', 'http://www.ubuntu.com/usn/USN-2098-1', 'http://lists.opensuse.org/opensuse-updates/2014-02/msg00064.html', 'http://cve.mitre.org/cgi-bin/cvename.cgi?name=2013-6393', 'http://lists.opensuse.org/opensuse-updates/2014-02/msg00065.html', 'http://www.debian.org/security/2014/dsa-2870', 'http://www.mandriva.com/security/advisories?name=MDVSA-2015:060', 'https://puppet.com/security/cve/cve-2013-6393', 'http://www.securityfocus.com/bid/65258', 'http://lists.opensuse.org/opensuse-updates/2015-02/msg00078.html', 'http://osvdb.org/102716', 'http://archives.neohapsis.com/archives/bugtraq/2014-10/0103.html', 'http://advisories.mageia.org/MGASA-2014-0040.html', 'https://nvd.nist.gov/vuln/detail/CVE-2013-6393', 'https://bugzilla.redhat.com/show_bug.cgi?id=1033990', 'http://archives.neohapsis.com/archives/bugtraq/2014-04/0134.html', 'https://bitbucket.org/xi/libyaml/commits/tag/0.1.5', 'http://rhn.redhat.com/errata/RHSA-2014-0353.html', 'http://rhn.redhat.com/errata/RHSA-2014-0354.html', 'https://support.apple.com/kb/HT6536', 'http://www.debian.org/security/2014/dsa-2850'}
| null |
npm
|
GHSA-fmvm-x8mv-47mj
|
Improper CSP in Image Optimization API for Next.js versions between 10.0.0 and 12.1.0
|
Next.js is a React framework. Starting with version 10.0.0 and prior to version 12.1.0, Next.js is vulnerable to User Interface (UI) Misrepresentation of Critical Information. In order to be affected, the `next.config.js` file must have an `images.domains` array assigned and the image host assigned in `images.domains` must allow user-provided SVG. If the `next.config.js` file has `images.loader` assigned to something other than default, the instance is not affected. Version 12.1.0 contains a patch for this issue. As a workaround, change `next.config.js` to use a different `loader configuration` other than the default.
### Impact
- **Affected**: All of the following must be true to be affected
- Next.js between version 10.0.0 and 12.0.10
- The `next.config.js` file has [images.domains](https://nextjs.org/docs/api-reference/next/image#domains) array assigned
- The image host assigned in [images.domains](https://nextjs.org/docs/api-reference/next/image#domains) allows user-provided SVG
- **Not affected**: The `next.config.js` file has [images.loader](https://nextjs.org/docs/api-reference/next/image#loader-configuration) assigned to something other than default
### Patches
[Next.js 12.1.0](https://github.com/vercel/next.js/releases/tag/v12.1.0)
### Workarounds
Change `next.config.js` to use a different [loader configuration](https://nextjs.org/docs/api-reference/next/image#loader-configuration) other than the default, for example:
```js
module.exports = {
images: {
loader: 'imgix',
path: 'https://example.com/myaccount/',
},
}
```
Or if you want to use the [`loader`](https://nextjs.org/docs/api-reference/next/image#loader) prop on the component, you can use `custom`:
```js
module.exports = {
images: {
loader: 'custom',
},
}
```
|
{'CVE-2022-23646'}
|
2022-02-23T15:26:32Z
|
2022-02-17T17:19:18Z
|
MODERATE
| null |
{'CWE-451'}
|
{'https://github.com/vercel/next.js/security/advisories/GHSA-fmvm-x8mv-47mj', 'https://github.com/vercel/next.js/releases/tag/v12.1.0', 'https://github.com/vercel/next.js/pull/34075', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23646', 'https://github.com/vercel/next.js'}
| null |
npm
|
GHSA-674r-xx4c-gj7x
|
Malicious Package in sb58
|
All versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.
## Recommendation
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer.
The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
| null |
2021-10-04T14:28:19Z
|
2020-09-03T17:04:05Z
|
CRITICAL
| null |
{'CWE-506'}
|
{'https://www.npmjs.com/advisories/1406'}
| null |
npm
|
GHSA-74cp-qw7f-7hpw
|
Path Traversal in statics-server
|
All versions of `statics-server` are vulnerable to Path Traversal. Due to insufficient input sanitization, attackers can access server files by using relative paths.
## Recommendation
No fix is currently available. Consider using an alternative module until a fix is made available.
| null |
2020-08-31T18:36:24Z
|
2019-06-05T14:10:23Z
|
MODERATE
| null |
{'CWE-22'}
|
{'https://hackerone.com/reports/355456', 'https://www.npmjs.com/advisories/805'}
| null |
npm
|
GHSA-h4mf-75hf-67w4
|
Information disclosure in parse-server
|
1. you can fetch all the users' objects, by using regex in the NoSQL query.
Using the NoSQL, you can use a regex on sessionToken `("_SessionToken":{"$regex":"r:027f"}}` and find valid accounts this way.
Using this method, it's possible to retrieve accounts without interaction from the users.
GET /parse/users/me HTTP/1.1
```
{
"_ApplicationId": "appName",
"_JavaScriptKey": "javascriptkey",
"_ClientVersion": "js2.10.0",
"_InstallationId": "ca713ee2-6e60-d023-a8fe-14e1bfb2f300",
"_SessionToken": {
"$regex": "r:5"
}
}
```
When trying it with an update query the same thing luckily doesn't seem to work:
POST /parse/classes/_User/PPNk59jPPZ
2. There is another similar vulnerability in verify email and the request password reset.
If you sign up with someone else's email address, you can simply use regex in the token param to verify the account: `http://localhost:1337/parse/apps/kickbox/verify_email?token[$regex]=a&username=some@email.com`
The same thing can be done for reset password: `http://localhost:1337/parse/apps/kickbox/request_password_reset?token[$regex]=a&username=some@email.com`
You may need to do it a few times with a different letter/number, but as long as the tokens contain the character it will succeed.
|
{'CVE-2020-5251'}
|
2021-01-08T20:27:29Z
|
2020-03-04T20:20:27Z
|
HIGH
| null |
{'CWE-285', 'CWE-200'}
|
{'https://github.com/parse-community/parse-server/security/advisories/GHSA-h4mf-75hf-67w4', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5251', 'https://github.com/parse-community/parse-server/commit/3a3a5eee5ffa48da1352423312cb767de14de269'}
| null |
npm
|
GHSA-9x7m-9hpg-xxmw
|
Prototype Pollution in putil-merge
|
Prototype pollution vulnerability in 'putil-merge' versions1.0.0 through 3.6.6 allows attacker to cause a denial of service and may lead to remote code execution.
|
{'CVE-2021-25953'}
|
2021-07-19T15:44:57Z
|
2021-12-10T17:24:16Z
|
CRITICAL
| null |
{'CWE-1321'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-25953', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25953'}
| null |
npm
|
GHSA-c6f3-3c98-2j2f
|
Malicious Package in jquerz
|
Version 1.0.1 of `jquerz` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.
## Recommendation
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer.
The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
| null |
2021-09-30T21:55:38Z
|
2020-09-02T21:39:46Z
|
CRITICAL
| null |
{'CWE-506'}
|
{'https://www.npmjs.com/advisories/907'}
| null |
npm
|
GHSA-7gc6-qh9x-w6h8
|
Incorrect Authorization in cross-fetch
|
When fetching a remote url with Cookie if it get Location response header then it will follow that url and try to fetch that url with provided cookie . So cookie is leaked here to thirdparty.
Ex: you try to fetch example.com with cookie and if it get redirect url to attacker.com then it fetch that redirect url with provided cookie .
|
{'CVE-2022-1365'}
|
2022-04-28T20:45:25Z
|
2022-04-17T00:00:32Z
|
MODERATE
| null |
{'CWE-359', 'CWE-863'}
|
{'https://github.com/lquixada/cross-fetch/commit/a3b3a9481091ddd06b8f83784ba9c4e034dc912a', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1365', 'https://huntr.dev/bounties/ab55dfdd-2a60-437a-a832-e3efe3d264ac', 'https://github.com/lquixada/cross-fetch/pull/135', 'https://github.com/lquixada/cross-fetch'}
| null |
npm
|
GHSA-q4v7-4rhw-9hqm
|
Code Execution through IIFE in node-serialize
|
Affected versions of `node-serialize` can be abused to execute arbitrary code via an [immediately invoked function expression](https://en.wikipedia.org/wiki/Immediately-invoked_function_expression) (IIFE) if untrusted user input is passed into `unserialize()`.
## Recommendation
There is no direct patch for this issue. The package author has reviewed this advisory, and provided the following recommendation:
```
To avoid the security issues, at least one of the following methods should be taken:
1. Make sure to send serialized strings internally, isolating them from potential hackers. For example, only sending the strings from backend to fronend and always using HTTPS instead of HTTP.
2. Introduce public-key cryptosystems (e.g. RSA) to ensure the strings not being tampered with.
```
|
{'CVE-2017-5941'}
|
2021-06-23T15:41:17Z
|
2018-07-18T18:27:56Z
|
CRITICAL
| null |
{'CWE-502'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2017-5941', 'http://www.securityfocus.com/bid/96225', 'https://github.com/advisories/GHSA-q4v7-4rhw-9hqm', 'https://www.npmjs.com/advisories/311', 'http://packetstormsecurity.com/files/161356/Node.JS-Remote-Code-Execution.html', 'https://opsecx.com/index.php/2017/02/08/exploiting-node-js-deserialization-bug-for-remote-code-execution/', 'http://packetstormsecurity.com/files/163222/Node.JS-Remote-Code-Execution.html', 'https://nodesecurity.io/advisories/311', 'https://github.com/luin/serialize/issues/4'}
| null |
npm
|
GHSA-23vw-mhv5-grv5
|
Denial of Service in @hapi/hapi
|
Versions of `@hapi/hapi` prior to 18.4.1 or 19.1.1 are vulnerable to Denial of Service. The CORS request handler has a vulnerability which will cause the function to throw a system error if the header contains some invalid values. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.
## Recommendation
Upgrade to versions 18.4.1, 19.1.1 or later.
| null |
2020-08-31T19:00:56Z
|
2020-09-03T15:48:43Z
|
HIGH
| null | null |
{'https://www.npmjs.com/advisories/1482'}
| null |
npm
|
GHSA-9cp3-fh5x-xfcj
|
Regular Expression Denial of Service in charset
|
Affected versions of `charset` are susceptible to a regular expression denial of service.
The amplification on this vulnerability is relatively low - it takes around 2 seconds for the engine to execute on a malicious input which is 50,000 characters in length.
If node was compiled using the `-DHTTP_MAX_HEADER_SIZE` however, the impact of the vulnerability can be significant, as the primary limitation for the vulnerability is the default max HTTP header length in node.
## Recommendation
Update to version 1.0.1 or later.
|
{'CVE-2017-16098'}
|
2020-08-31T18:26:23Z
|
2018-08-09T20:55:46Z
|
MODERATE
| null |
{'CWE-400'}
|
{'https://github.com/advisories/GHSA-9cp3-fh5x-xfcj', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16098', 'https://nodesecurity.io/advisories/524', 'https://github.com/node-modules/charset/issues/10', 'https://www.npmjs.com/advisories/524'}
| null |
npm
|
GHSA-545q-3fg6-48m7
|
Regular expression denial of service (ReDoS)
|
This affects the package html-parse-stringify before 2.0.1; all versions of package html-parse-stringify2. Sending certain input could cause one of the regular expressions that is used for parsing to backtrack, freezing the process.
|
{'CVE-2021-23346'}
|
2021-03-12T23:03:51Z
|
2021-03-18T19:39:31Z
|
MODERATE
| null |
{'CWE-400'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-23346', 'https://github.com/HenrikJoreteg/html-parse-stringify/releases/tag/v2.0.1', 'https://github.com/rayd/html-parse-stringify2/blob/master/lib/parse.js%23L2', 'https://snyk.io/vuln/SNYK-JS-HTMLPARSESTRINGIFY2-1079307', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1080633', 'https://github.com/HenrikJoreteg/html-parse-stringify/commit/c7274a48e59c92b2b7e906fedf9065159e73fe12', 'https://github.com/HenrikJoreteg/html-parse-stringify/blob/master/lib/parse.js%23L2', 'https://snyk.io/vuln/SNYK-JS-HTMLPARSESTRINGIFY-1079306'}
| null |
npm
|
GHSA-82v2-mx6x-wq7q
|
Incorrect Default Permissions in log4js
|
### Impact
Default file permissions for log files created by the file, fileSync and dateFile appenders are world-readable (in unix). This could cause problems if log files contain sensitive information. This would affect any users that have not supplied their own permissions for the files via the mode parameter in the config.
### Patches
Fixed by:
* https://github.com/log4js-node/log4js-node/pull/1141
* https://github.com/log4js-node/streamroller/pull/87
Released to NPM in log4js@6.4.0
### Workarounds
Every version of log4js published allows passing the mode parameter to the configuration of file appenders, see the documentation for details.
### References
Thanks to [ranjit-git](https://www.huntr.dev/users/ranjit-git) for raising the issue, and to @peteriman for fixing the problem.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [logj4s-node](https://github.com/log4js-node/log4js-node)
* Ask a question in the [slack channel](https://join.slack.com/t/log4js-node/shared_invite/enQtODkzMDQ3MzExMDczLWUzZmY0MmI0YWI1ZjFhODY0YjI0YmU1N2U5ZTRkOTYyYzg3MjY5NWI4M2FjZThjYjdiOGM0NjU2NzBmYTJjOGI)
* Email us at [gareth.nomiddlename@gmail.com](mailto:gareth.nomiddlename@gmail.com)
|
{'CVE-2022-21704'}
|
2022-01-25T19:05:06Z
|
2022-01-21T18:53:27Z
|
MODERATE
| null |
{'CWE-276'}
|
{'https://github.com/log4js-node/log4js-node/security/advisories/GHSA-82v2-mx6x-wq7q', 'https://github.com/log4js-node/streamroller/pull/87', 'https://github.com/log4js-node/log4js-node/pull/1141/commits/8042252861a1b65adb66931fdf702ead34fa9b76', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21704', 'https://github.com/log4js-node/log4js-node/blob/v6.4.0/CHANGELOG.md#640', 'https://github.com/log4js-node/log4js-node'}
| null |
npm
|
GHSA-8qp3-pvwc-2g4p
|
Hijacked Environment Variables in nodefabric
|
The `nodefabric` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.
All versions have been unpublished from the npm registry.
## Recommendation
As this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.
If you have found this installed in your environment, you should:
1. Delete the package
2. Clear your npm cache
3. Ensure it is not present in any other package.json files on your system
4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.
Additionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.
|
{'CVE-2017-16054'}
|
2020-08-31T18:25:04Z
|
2018-07-23T20:49:58Z
|
MODERATE
| null |
{'CWE-506'}
|
{'https://nodesecurity.io/advisories/488', 'https://www.npmjs.com/advisories/488', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16054', 'https://github.com/advisories/GHSA-8qp3-pvwc-2g4p'}
| null |
npm
|
GHSA-fhjf-83wg-r2j9
|
Prototype Pollution in mixin-deep
|
Versions of `mixin-deep` prior to 2.0.1 or 1.3.2 are vulnerable to Prototype Pollution. The `mixinDeep` function fails to validate which Object properties it updates. This allows attackers to modify the prototype of Object, causing the addition or modification of an existing property on all objects.
## Recommendation
If you are using `mixin-deep` 2.x, upgrade to version 2.0.1 or later.
If you are using `mixin-deep` 1.x, upgrade to version 1.3.2 or later.
|
{'CVE-2019-10746'}
|
2021-07-27T21:26:01Z
|
2019-08-27T17:42:33Z
|
CRITICAL
| null |
{'CWE-88'}
|
{'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BFNIVG2XYFPZJY3DYYBJASZ7ZMKBMIJT/', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10746', 'https://snyk.io/vuln/SNYK-JS-MIXINDEEP-450212', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UXRA365KZCUNXMU3KDH5JN5BEPNIGUKC/', 'https://www.npmjs.com/advisories/1013'}
| null |
npm
|
GHSA-h97f-5258-5593
|
Incorrect Authorization in serverless-offline
|
Serverless Offline 8.0.0 returns a 403 HTTP status code for a route that has a trailing / character, which might cause a developer to implement incorrect access control, because the actual behavior within the Amazon AWS environment is a 200 HTTP status code (i.e., possibly greater than expected permissions).
|
{'CVE-2021-38384'}
|
2021-09-01T18:33:32Z
|
2021-09-01T18:32:22Z
|
MODERATE
| null |
{'CWE-863'}
|
{'https://github.com/dherault/serverless-offline/issues/1259', 'https://github.com/dherault/serverless-offline', 'https://nvd.nist.gov/vuln/detail/CVE-2021-38384'}
| null |
npm
|
GHSA-cqp5-m4pq-gfgp
|
Prototype Pollution in defaults-deep
|
Versions of `default-deep` before 0.2.4 are vulnerable to prototype pollution
## Recommendation
Update to version 0.2.4 or later.
|
{'CVE-2018-3723'}
|
2020-08-31T18:28:39Z
|
2018-07-26T15:18:43Z
|
LOW
| null |
{'CWE-471'}
|
{'https://github.com/advisories/GHSA-cqp5-m4pq-gfgp', 'https://hackerone.com/reports/310514', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3723', 'https://www.npmjs.com/advisories/581', 'https://github.com/jonschlinkert/defaults-deep/commit/c873f341327ad885ff4d0f23b3d3bca31b0343e5'}
| null |
npm
|
GHSA-h3vq-wv8j-36gw
|
Cross-site Scripting in Scratch-Svg-Renderer
|
A DOM-based cross-site scripting (XSS) vulnerability in Scratch-Svg-Renderer v0.2.0 allows attackers to execute arbitrary web scripts or HTML via a crafted sb3 file.
|
{'CVE-2020-27428'}
|
2022-01-07T23:45:14Z
|
2022-01-08T00:44:33Z
|
MODERATE
| null |
{'CWE-79'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-27428', 'https://github.com/LLK/scratch-svg-renderer', 'https://github.com/LLK/scratch-svg-renderer/commit/7c74ec7de3254143ec3c557677f5355a90a3d07f'}
| null |
npm
|
GHSA-qr9h-vr5p-pwwx
|
Denial of Service (DoS) in restify-paginate
|
The restify-paginate package 0.0.5 for Node.js allows remote attackers to cause a Denial-of-Service by omitting the HTTP Host header. A Restify-based web service would crash with an uncaught exception.
|
{'CVE-2020-27543'}
|
2022-04-18T21:56:34Z
|
2021-04-12T18:59:11Z
|
HIGH
| null |
{'CWE-755'}
|
{'https://github.com/paulvarache/restify-paginate/', 'https://github.com/secoats/cve/tree/master/CVE-2020-27543_dos_restify-paginate', 'https://nvd.nist.gov/vuln/detail/CVE-2020-27543', 'https://security.netapp.com/advisory/ntap-20210401-0002/', 'https://www.npmjs.com/package/restify-paginate'}
| null |
npm
|
GHSA-cpp2-q66x-fq44
|
Directory Traversal in jikes
|
Affected versions of `jikes` resolve relative file paths, resulting in a directory traversal vulnerability. A malicious actor can use this vulnerability to access files outside of the intended directory root, which may result in the disclosure of private files on the vulnerable system.
Example request:
```
GET /../../../../../../../../../../etc/passwd HTTP/1.1
host:foo
```
## Recommendation
No patch is available for this vulnerability.
It is recommended that the package is only used for local development, and if the functionality is needed for production, a different package is used instead.
|
{'CVE-2017-16139'}
|
2020-08-31T18:24:36Z
|
2018-08-06T21:39:12Z
|
MODERATE
| null |
{'CWE-22'}
|
{'https://nodesecurity.io/advisories/476', 'https://github.com/advisories/GHSA-cpp2-q66x-fq44', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16139', 'https://www.npmjs.com/advisories/476', 'https://github.com/JacksonGL/NPM-Vuln-PoC/blob/master/directory-traversal/jikes'}
| null |
npm
|
GHSA-w23f-f3c5-r9qh
|
Downloads Resources over HTTP in ikst
|
Affected versions of `ikst` insecurely download resources over HTTP.
In scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.
## Recommendation
Upgrade to version 1.1.2 or greater.
|
{'CVE-2017-16041'}
|
2021-01-08T01:57:08Z
|
2018-07-24T15:56:19Z
|
HIGH
| null |
{'CWE-311'}
|
{'https://github.com/advisories/GHSA-w23f-f3c5-r9qh', 'https://www.npmjs.com/advisories/249', 'https://nodesecurity.io/advisories/249', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16041'}
| null |
npm
|
GHSA-m8gw-hjpr-rjv7
|
Prototype Pollution in dojo
|
All versions of package dojo are vulnerable to Prototype Pollution via the setObject function.
|
{'CVE-2021-23450'}
|
2022-01-04T17:43:26Z
|
2022-01-05T15:01:46Z
|
HIGH
| null |
{'CWE-1321'}
|
{'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBDOJO-2313034', 'https://snyk.io/vuln/SNYK-JS-DOJO-1535223', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-2313035', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://github.com/dojo/dojo/blob/4c39c14349408fc8274e19b399ffc660512ed07c/_base/lang.js%23L172', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-2313033', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23450', 'https://github.com/dojo/dojo', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARS-2313036'}
| null |
npm
|
GHSA-pv4c-p2j5-38j4
|
Open Redirect in url-parse
|
Versions of `url-parse` before 1.4.3 returns the wrong hostname which could lead to Open Redirect, Server Side Request Forgery (SSRF), or Bypass Authentication Protocol vulnerabilities.
## Recommendation
Update to version 1.4.3 or later.
|
{'CVE-2018-3774'}
|
2020-08-31T18:32:26Z
|
2018-08-13T15:02:15Z
|
HIGH
| null |
{'CWE-425'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2018-3774', 'https://github.com/unshiftio/url-parse/commit/d7b582ec1243e8024e60ac0b62d2569c939ef5de', 'https://github.com/unshiftio/url-parse/commit/53b1794e54d0711ceb52505e0f74145270570d5a', 'https://hackerone.com/reports/384029', 'https://www.npmjs.com/advisories/678', 'https://github.com/advisories/GHSA-pv4c-p2j5-38j4'}
| null |
npm
|
GHSA-phwq-j96m-2c2q
|
Template injection in ejs
|
The ejs (aka Embedded JavaScript templates) package 3.1.6 for Node.js allows server-side template injection in settings[view options][outputFunctionName]. This is parsed as an internal option, and overwrites the outputFunctionName option with an arbitrary OS command (which is executed upon template compilation).
|
{'CVE-2022-29078'}
|
2022-04-27T14:36:21Z
|
2022-04-26T00:00:40Z
|
HIGH
| null |
{'CWE-74'}
|
{'https://github.com/mde/ejs/commit/15ee698583c98dadc456639d6245580d17a24baf', 'https://eslam.io/posts/ejs-server-side-template-injection-rce/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-29078', 'https://github.com/mde/ejs'}
| null |
npm
|
GHSA-xw79-hhv6-578c
|
Cross-Site Scripting in serve
|
Versions of `serve` prior to 10.0.2 are vulnerable to Cross-Site Scripting (XSS). The package does not encode output, allowing attackers to execute arbitrary JavaScript in the victim's browser if user-supplied input is rendered.
## Recommendation
Upgrade to version 10.0.2 or later.
| null |
2021-09-28T16:54:33Z
|
2020-09-11T21:16:59Z
|
HIGH
| null |
{'CWE-79'}
|
{'https://github.com/zeit/serve-handler/commit/65b4d4183a31a8076c78c40118acb0ca1b64f620', 'https://hackerone.com/reports/358641', 'https://hackerone.com/reports/398285', 'https://github.com/zeit/serve-handler', 'https://www.npmjs.com/advisories/971'}
| null |
npm
|
GHSA-4m3j-h8f2-4xh4
|
Malicious Package in coinstrig
|
All versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.
## Recommendation
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer.
The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
| null |
2021-10-01T20:58:35Z
|
2020-09-03T19:41:31Z
|
CRITICAL
| null |
{'CWE-506'}
|
{'https://www.npmjs.com/advisories/1384'}
| null |
npm
|
GHSA-qm7x-rc44-rrqw
|
Cross-site Scripting Vulnerability in GraphQL Playground (distributed by Apollo Server)
|
### Impact
In certain configurations, Apollo Server serves the client-side web app "GraphQL Playground" from the same web server that executes GraphQL operations. This web app has access to cookies and other credentials associated with the web server's operations. There is a cross-site scripting vulnerability in GraphQL Playground that allows for arbitrary JavaScript code execution in your web server's origin. If a user clicks a specially crafted link to your GraphQL Playground page served by Apollo Server, an attacker can steal cookies and other private browser data.
Details of the underlying GraphQL Playground vulnerability are available in [this `graphql-playground` advisory](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7). (A [similar vulnerability](https://github.com/graphql/graphiql/security/advisories/GHSA-x4r7-m2q9-69c8) exists in the related `graphiql` project.) This advisory focuses on identifying whether *Apollo Server* installations are vulnerable and mitigating the vulnerability in Apollo Server; see the other advisories for details on the XSS vulnerability itself.
The impact of this vulnerability is more severe if (as is common) your GraphQL server's origin URL is an origin that is used to store sensitive data such as cookies.
In order for this vulnerability to affect your Apollo Server installation, it must actually serve GraphQL Playground. The integration between Apollo Server and GraphQL Playground is different in Apollo Server 2 and Apollo Server 3. You can tell which version of Apollo Server you are running by looking at the version of the [package from which you import the `ApolloServer` class](https://www.apollographql.com/docs/apollo-server/integrations/middleware/): this may be `apollo-server`, `apollo-server-express`, `apollo-server-lambda`, etc.
#### Apollo Server 3
Apollo Server 3 does not serve GraphQL Playground by default. It has a [landing page plugin system](https://www.apollographql.com/docs/apollo-server/api/plugin/landing-pages/) and the default plugin is a simple splash page that is not vulnerable to this exploit, linking to Apollo Sandbox Explorer. (We chose to change the default because GraphQL Playground is not actively maintained.)
If you are running Apollo Server 3, then you are *only* vulnerable if you *explicitly* import the [`ApolloServerPluginLandingPageGraphQLPlayground`](https://www.apollographql.com/docs/apollo-server/api/plugin/landing-pages/#graphql-playground-landing-page) plugin and pass it to your `ApolloServer`'s constructor in the `plugins` array. Otherwise, this advisory does not apply to your server.
#### Apollo Server 2
Apollo Server 2 serves GraphQL Playground by default, unless the `NODE_ENV` environment variable is set to `production`, or if you explicitly configure it via the `playground` option to the `ApolloServer` constructor.
Your Apollo Server 2 installation is vulnerable if *any* of the following is true:
- You pass `playground: true` to the `ApolloServer` constructor
- You pass some other object like `playground: {title: "Title"}` to the `ApolloServer` constructor
- You do *not* pass any `playground` option to the `ApolloServer` constructor, *and* the `NODE_ENV` environment variable is *not* set to `production`
#### Apollo Server 1
Apollo Server 1 included `graphiql` instead of `graphql-playground`. `graphiql` isn't automatically enabled in Apollo Server 1: you have to explicitly call a function such as `graphiqlExpress` to enable it. Because Apollo Server 1 is not commonly used, we have not done a detailed examination of whether the integration between Apollo Server 1 and `graphiql` is vulnerable to a similar exploit. If you are still using Apollo Server 1, we recommend you disable `graphiql` by removing the `graphiqlExpress` call, and then upgrade to a newer version of Apollo Server.
### Patches and workarounds
There are several approaches you can take to ensure that your server is not vulnerable to this issue.
#### Upgrade Apollo Server
The vulnerability has been patched in Apollo Server 2.25.3 and Apollo Server 3.4.1. To get the patch, upgrade your [Apollo Server entry point package](https://www.apollographql.com/docs/apollo-server/integrations/middleware/) to one of the fixed versions; this package may be `apollo-server`, `apollo-server-express`, `apollo-server-lambda`, etc. Additionally, if you depend directly on `apollo-server-core` in your `package.json`, make sure that you upgrade it to the same version.
#### Upgrade Playground version only
If upgrading to the latest version of Apollo Server 2 or 3 quickly will be challenging, you can configure your current version of Apollo Server to serve the latest version of the GraphQL Playground app. This will pin your app to serve a specific version of GraphQL Playground and you will not receive updates to it when you upgrade Apollo Server later, but this may be acceptable because GraphQL Playground is not actively maintained.
The way to do this depends on what version of Apollo Server you're using and if you're already configuring GraphQL Playground.
- **Apollo Server 3**: If you are using Apollo Server 3, then you are only vulnerable if your serve explicitly calls [`ApolloServerPluginLandingPageGraphQLPlayground`](https://www.apollographql.com/docs/apollo-server/api/plugin/landing-pages/#graphql-playground-landing-page) and passes it to the Apollo Server constructor in the `plugins` array. Add the option `version: '1.7.42'` to this call, so it looks like:
```
plugins: [ApolloServerPluginLandingPageGraphQLPlayground({version: '1.7.42'})]
```
- **Apollo Server 2 with no explicit `playground` option**: If you are using Apollo Server 2 and do not currently pass the `playground` option to `new ApolloServer`, add a `playground` option like so:
```
new ApolloServer({ playground: process.env.NODE_ENV === 'production' ? false : { version: '1.7.42' } })
```
- **Apollo Server 2 with `playground: true` or `playground: {x, y, z}`**: If you are using Apollo Server 2 and currently pass `true` or an object to `new ApolloServer`, pass the `version` option under the `playground` option like so:
```
new ApolloServer({ playground: { version: '1.7.42', x, y, z } })
```
#### Disable GraphQL Playground
If upgrading Apollo Server or GraphQL Playground is challenging, you can also disable GraphQL Playground.
In Apollo Server 3, remove the call to `ApolloServerPluginLandingPageGraphQLPlayground` from your `ApolloServer` constructor's `plugins` array. This will replace GraphQL Playground with a simple splash page. See [the landing page plugins docs](https://www.apollographql.com/docs/apollo-server/api/plugin/landing-pages/) for details.
In Apollo Server 2, add `playground: false` to your `ApolloServer` constructor: `new ApolloServer({ playground: false })`. This will replace GraphQL Playground with an attempt to execute a GraphQL operation, which will likely display an error in the browser.
If you disable GraphQL Playground, any users who rely on it to execute GraphQL operations will need an alternative, such as the [Apollo Studio Explorer's account-free Sandbox](https://www.apollographql.com/docs/studio/explorer/#account-free-sandbox).
### Credit
This vulnerability was discovered by @Ry0taK. Thank you!
The fix to GraphQL Playground was developed by @acao and @glasser with help from @imolorhe, @divyenduz, and @benjie.
### For more information
If you have any questions or comments about this advisory:
* Read the [`graphql-playground` advisory](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7)
* Open an issue in [the `apollo-server` repo](https://github.com/apollographql/apollo-server/)
* If the issue involves confidential information, email us at [security@apollographql.com](mailto:security@apollographql.com)
| null |
2021-11-04T19:46:00Z
|
2021-11-08T18:07:42Z
|
HIGH
| null |
{'CWE-79'}
|
{'https://github.com/apollographql/apollo-server/security/advisories/GHSA-qm7x-rc44-rrqw', 'https://github.com/apollographql/apollo-server'}
| null |
npm
|
GHSA-4c87-gg2q-fc6m
|
Malicious Package in rc-calendar-jhorst
|
Version 8.4.3 of `rc-calendar-jhorst` contained malicious code. The code when executed in the browser would enumerate password, cvc, cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`
## Recommendation
If version 8.4.3 of this module is found installed you will want to replace it with a version before or after 8.4.3. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.
| null |
2020-08-31T18:30:40Z
|
2020-09-01T20:31:04Z
|
CRITICAL
| null | null |
{'https://www.npmjs.com/advisories/633'}
| null |
npm
|
GHSA-pmpr-vc5q-h3jw
|
Exposure of Resource to Wrong Sphere in valib
|
valib through 2.0.0 allows Internal Property Tampering. A maliciously crafted JavaScript object can bypass several inspection functions provided by valib. Valib uses a built-in function (hasOwnProperty) from the unsafe user-input to examine an object. It is possible for a crafted payload to overwrite this function to manipulate the inspection results to bypass security checks.
|
{'CVE-2019-10805'}
|
2021-04-09T22:21:38Z
|
2021-04-13T15:21:59Z
|
MODERATE
| null |
{'CWE-668'}
|
{'https://www.npmjs.com/package/valib', 'https://snyk.io/vuln/SNYK-JS-VALIB-559015', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10805'}
| null |
npm
|
GHSA-pp7h-53gx-mx7r
|
Remote Memory Exposure in bl
|
A buffer over-read vulnerability exists in bl <4.0.3, <3.0.1, <2.2.1, and <1.2.3 which could allow an attacker to supply user input (even typed) that if it ends up in consume() argument and can become negative, the BufferList state can be corrupted, tricking it into exposing uninitialized memory via regular .slice() calls.
|
{'CVE-2020-8244'}
|
2021-05-10T16:25:30Z
|
2020-09-02T15:26:19Z
|
HIGH
| null |
{'CWE-126', 'CWE-125'}
|
{'https://github.com/rvagg/bl/commit/8a8c13c880e2bef519133ea43e0e9b78b5d0c91e', 'https://hackerone.com/reports/966347', 'https://github.com/rvagg/bl/commit/dacc4ac7d5fcd6201bcf26fbd886951be9537466', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8244', 'https://github.com/rvagg/bl/commit/d3e240e3b8ba4048d3c76ef5fb9dd1f8872d3190'}
| null |
npm
|
GHSA-vh8f-xw5v-8993
|
Command Injection in macfromip
|
All versions of npm package macfromip are affected by a command injection vulnerability. The injection point is located in line 66 in macfromip.js.
|
{'CVE-2020-7786'}
|
2021-04-12T19:01:01Z
|
2021-04-12T19:01:20Z
|
CRITICAL
| null |
{'CWE-74'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-7786', 'https://snyk.io/vuln/SNYK-JS-MACFROMIP-1048336', 'https://www.npmjs.com/package/macfromip'}
| null |
npm
|
GHSA-mxmj-84q8-34r7
|
Command Injection in expressfs
|
All versions of `expressfs` are vulnerable to Command Injection. The package does not validate user input on several API endpoints, allowing attackers to run arbitrary commands in the system. The affected endpoints are: `expressfs.appendFile`, `expressfs.cp`, `expressfs.create` and `expressfs.rmdir`.
## Recommendation
No fix is currently available. Consider using an alternative module until a fix is made available.
| null |
2020-08-31T18:41:47Z
|
2020-09-03T02:39:49Z
|
HIGH
| null |
{'CWE-77'}
|
{'https://www.npmjs.com/advisories/953'}
| null |
npm
|
GHSA-c8h6-89q2-mgv8
|
Malicious Package in dossier
|
Version 0.0.4 of `dossier` contained malicious code. The code when executed in the browser would enumerate password, cvc, cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`
## Recommendation
If version 0.0.4 of this module is found installed you will want to replace it with a version before or after 0.0.4. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.
| null |
2021-09-24T17:24:28Z
|
2020-09-01T19:55:48Z
|
CRITICAL
| null |
{'CWE-506'}
|
{'https://snyk.io/vuln/SNYK-JS-DOSSIER-450994', 'https://github.com/advisories/GHSA-c8h6-89q2-mgv8', 'https://www.npmjs.com/advisories/625'}
| null |
npm
|
GHSA-2r7f-4h2c-5x73
|
Arbitrary File Read in fury-adapter-swagger
|
Affected versions of `fury-adapter-swagger` have a weakness that allows an attacker to read arbitrary files off of the system. This can be used to read sensitive data, or to cause a denial of service condition by attempting to read something like `/dev/zero`.
## Proof of Concept:
```
---
swagger: '2.0'
info:
title: Read local files
version: '1.0'
paths:
/foo:
get:
responses:
200:
description: Some description
examples:
text/html:
example:
$ref: '/etc/passwd'
```
## Recommendation
Upgrade to version 0.9.7 or later
|
{'CVE-2016-1000249'}
|
2020-08-31T18:18:37Z
|
2020-09-01T16:38:33Z
|
CRITICAL
| null | null |
{'https://www.npmjs.com/advisories/305'}
| null |
npm
|
GHSA-5634-rv46-48jf
|
Cross-Site Scripting in bleach
|
All versions of `bleach` are vulnerable to Cross-Site Scripting. It is possible to bypass the package's HTML sanitization with payloads such as `"<<script><</script>script>alert('xss');</<script><</script>script>"` regardless of the passed options. This may allow attackers to execute arbitrary JavaScript in the victim's browser.
## Recommendation
No fix is currently available. Consider using an alternative package until a fix is made available.
| null |
2020-08-31T18:44:51Z
|
2020-09-03T17:13:45Z
|
HIGH
| null |
{'CWE-79'}
|
{'https://www.npmjs.com/advisories/1034'}
| null |
npm
|
GHSA-45q2-34rf-mr94
|
Code Injection in mquery
|
lib/utils.js in mquery before 3.2.3 allows a pollution attack because a special property (e.g., __proto__) can be copied during a merge or clone operation.
|
{'CVE-2020-35149'}
|
2020-12-17T22:54:00Z
|
2020-12-18T18:23:43Z
|
MODERATE
| null |
{'CWE-94'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-35149', 'https://github.com/aheckmann/mquery/commit/792e69fd0a7281a0300be5cade5a6d7c1d468ad4'}
| null |
npm
|
GHSA-9wx7-jrvc-28mm
|
Signature verification vulnerability in Stark Bank ecdsa libraries
|
An attacker can forge signatures on arbitrary messages that will verify for any public key. This may allow attackers to authenticate as any user within the Stark Bank platform, and bypass signature verification needed to perform operations on the platform, such as send payments and transfer funds. Additionally, the ability for attackers to forge signatures may impact other users and projects using these libraries in different and unforeseen ways.
| null |
2022-03-03T05:13:29.259203Z
|
2021-11-08T21:51:18Z
|
HIGH
| null |
{'CWE-347'}
|
{'https://github.com/starkbank/ecdsa-java', 'https://github.com/starkbank/ecdsa-python', 'https://research.nccgroup.com/2021/11/08/technical-advisory-arbitrary-signature-forgery-in-stark-bank-ecdsa-libraries/', 'https://github.com/starkbank/ecdsa-node', 'https://github.com/starkbank/ecdsa-dotnet', 'https://github.com/starkbank/ecdsa-python/releases/tag/v2.0.1'}
| null |
npm
|
GHSA-mjxr-4v3x-q3m4
|
Improper Input Validation in sanitize-html
|
Apostrophe Technologies sanitize-html before 2.3.2 does not properly validate the hostnames set by the "allowedIframeHostnames" option when the "allowIframeRelativeUrls" is set to true, which allows attackers to bypass hostname whitelist for iframe element, related using an src value that starts with "/\\example.com".
|
{'CVE-2021-26540'}
|
2021-03-29T23:13:11Z
|
2021-05-06T16:10:19Z
|
MODERATE
| null |
{'CWE-20'}
|
{'https://github.com/apostrophecms/sanitize-html/blob/main/CHANGELOG.md#232-2021-01-26', 'https://github.com/apostrophecms/sanitize-html/pull/460', 'https://advisory.checkmarx.net/advisory/CX-2021-4309', 'https://nvd.nist.gov/vuln/detail/CVE-2021-26540'}
| null |
npm
|
GHSA-f757-9c4x-chff
|
Downloads Resources over HTTP in poco
|
Affected versions of `poco` insecurely download an executable over an unencrypted HTTP connection.
In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running `poco`.
## Recommendation
No patch is currently available for this vulnerability.
The best mitigation is currently to avoid using this package, using a different package if available.
Alternatively, the risk of exploitation can be reduced by ensuring that this package is not installed while connected to a public network. If the package is installed on a private network, the only people who can exploit this vulnerability are those who have compromised your network or those who have privileged access to your ISP, such as Nation State Actors or Rogue ISP Employees.
|
{'CVE-2016-10659'}
|
2021-01-08T18:54:11Z
|
2019-02-18T23:54:44Z
|
HIGH
| null |
{'CWE-311'}
|
{'https://github.com/advisories/GHSA-f757-9c4x-chff', 'https://www.npmjs.com/advisories/271', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10659', 'https://nodesecurity.io/advisories/271'}
| null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.