ecosystem
stringclasses 11
values | vuln_id
stringlengths 10
19
| summary
stringlengths 4
220
⌀ | details
stringlengths 34
13.5k
| aliases
stringlengths 17
87
⌀ | modified_date
stringdate 2019-03-26 14:13:00
2022-05-10 08:46:52
| published_date
stringdate 2012-06-17 03:41:00
2022-05-10 08:46:50
| severity
stringclasses 5
values | score
float64 0
10
⌀ | cwe_id
stringclasses 581
values | refs
stringlengths 82
11.6k
| introduced
stringclasses 843
values | code_refs
stringlengths 46
940
| commits
stringlengths 46
940
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
npm | GHSA-257v-vj4p-3w2h | Regular Expression Denial of Service (ReDOS) | In the npm package `color-string`, there is a ReDos (Regular Expression Denial of Service) vulnerability regarding an exponential time complexity for
linearly increasing input lengths for `hwb()` color strings.
Strings reaching more than 5000 characters would see several
milliseconds of processing time; strings reaching more than
50,000 characters began seeing 1500ms (1.5s) of processing time.
The cause was due to a the regular expression that parses
hwb() strings - specifically, the hue value - where
the integer portion of the hue value used a 0-or-more quantifier
shortly thereafter followed by a 1-or-more quantifier.
This caused excessive backtracking and a cartesian scan,
resulting in exponential time complexity given a linear
increase in input length. | {'CVE-2021-29060'} | 2021-06-30T18:03:29Z | 2021-06-22T01:14:09Z | MODERATE | null | {'CWE-770'} | {'https://github.com/yetingli/SaveResults/blob/main/js/color-string.js', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29060', 'https://github.com/Qix-/color-string/commit/0789e21284c33d89ebc4ab4ca6f759b9375ac9d3', 'https://github.com/Qix-/color-string/releases/tag/1.5.5', 'https://www.npmjs.com/package/color-string', 'https://github.com/yetingli/PoCs/blob/main/CVE-2021-29060/Color-String.md'} | null | {'https://github.com/Qix-/color-string/commit/0789e21284c33d89ebc4ab4ca6f759b9375ac9d3'} | {'https://github.com/Qix-/color-string/commit/0789e21284c33d89ebc4ab4ca6f759b9375ac9d3'} |
npm | GHSA-8px5-63x9-5c7p | Command Injection in pullit | Versions of `pullit` prior to 1.4.0 are vulnerable to Command Injection. The package does not validate input on git branch names and concatenates it to an exec call, allowing attackers to run arbitrary commands in the system.
## Recommendation
Upgrade to version 1.4.0 or later.
## Credits
This vulnerability was discovered by @lirantal | null | 2022-04-01T19:35:31Z | 2020-09-03T16:47:30Z | HIGH | null | {'CWE-77'} | {'https://github.com/jkup/pullit', 'https://github.com/jkup/pullit/issues/23', 'https://hackerone.com/reports/315773', 'https://www.npmjs.com/advisories/1004', 'https://github.com/jkup/pullit/commit/4fec455774ee08f4dce0ef2ef934ffcc37219bfb'} | null | {'https://github.com/jkup/pullit/commit/4fec455774ee08f4dce0ef2ef934ffcc37219bfb'} | {'https://github.com/jkup/pullit/commit/4fec455774ee08f4dce0ef2ef934ffcc37219bfb'} |
npm | GHSA-r9w3-g83q-m6hq | Prototype Pollution in deepmerge-ts | deepmerge-ts is used to merge 2 or more objects respecting type information. deepmerge-ts is vulnerable to Prototype Pollution via file deepmerge.ts, function defaultMergeRecords(). A fix was released in version 4.0.2. Currently, there is no known workaround. | {'CVE-2022-24802'} | 2022-04-13T16:28:10Z | 2022-04-01T17:26:03Z | HIGH | null | {'CWE-915', 'CWE-1321'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-24802', 'https://github.com/RebeccaStevens/deepmerge-ts', 'https://github.com/RebeccaStevens/deepmerge-ts/commit/b39f1a93d9e1c3541bd2fe159fd696a16dbe1c72', 'https://github.com/RebeccaStevens/deepmerge-ts/commit/d637db7e4fb2bfb113cb4bc1c85a125936d7081b', 'https://github.com/RebeccaStevens/deepmerge-ts/security/advisories/GHSA-r9w3-g83q-m6hq'} | null | {'https://github.com/RebeccaStevens/deepmerge-ts/commit/b39f1a93d9e1c3541bd2fe159fd696a16dbe1c72', 'https://github.com/RebeccaStevens/deepmerge-ts/commit/d637db7e4fb2bfb113cb4bc1c85a125936d7081b'} | {'https://github.com/RebeccaStevens/deepmerge-ts/commit/b39f1a93d9e1c3541bd2fe159fd696a16dbe1c72', 'https://github.com/RebeccaStevens/deepmerge-ts/commit/d637db7e4fb2bfb113cb4bc1c85a125936d7081b'} |
npm | GHSA-55xv-f85c-248q | Regular Expression Denial of Service (ReDoS) in jsx-slack | jsx-slack v4.5.1 and earlier versions are vulnerable to a regular expression denial-of-service (ReDoS) attack.
### Impact
If attacker can put a lot of JSX elements into `<blockquote>` tag, an internal regular expression for escaping characters may consume an excessive amount of computing resources.
```javascript
/** @jsxImportSource jsx-slack */
import { Section } from 'jsx-slack'
console.log(
<Section>
<blockquote>
{[...Array(40)].map((_, i) => (
<p>{i + 1}</p>
))}
</blockquote>
</Section>
)
```
### Patches
_See also: https://github.com/yhatt/jsx-slack/security/advisories/GHSA-hp68-xhvj-x6j6_
jsx-slack v4.5.2 has updated regular expressions to prevent catastrophic backtracking.
jsx-slack v4.5.1 also had patched a workaround. It has no problems to contents with ASCII characters, but _still vulnerable to contents with multibyte characters_. (https://github.com/yhatt/jsx-slack/commit/36e4a10405e4c7745333e245fcc5029c02c7065d)
### References
- https://nvd.nist.gov/vuln/detail/CVE-2021-43838
- https://github.com/yhatt/jsx-slack/commit/36e4a10405e4c7745333e245fcc5029c02c7065d
### Credits
Thanks to @hieki for finding out this vulnerability. | {'CVE-2021-43838'} | 2022-01-04T19:52:06Z | 2021-12-17T19:59:02Z | LOW | null | {'CWE-400'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-43838', 'https://github.com/yhatt/jsx-slack/', 'https://github.com/yhatt/jsx-slack/commit/36e4a10405e4c7745333e245fcc5029c02c7065d', 'https://github.com/yhatt/jsx-slack/security/advisories/GHSA-55xv-f85c-248q'} | null | {'https://github.com/yhatt/jsx-slack/commit/36e4a10405e4c7745333e245fcc5029c02c7065d'} | {'https://github.com/yhatt/jsx-slack/commit/36e4a10405e4c7745333e245fcc5029c02c7065d'} |
npm | GHSA-59r9-6jp6-jcm7 | XSS vulnerability in GraphQL Playground from untrusted schemas | ## GraphQL Playground introspection schema template injection attack: Advisory Statement
This is a security advisory for an XSS vulnerability in `graphql-playground`.
A similar vulnerability affects `graphiql`, the package from which `graphql-playground` was forked. There is a corresponding `graphiql` [advisory](https://github.com/graphql/graphiql/security/advisories/GHSA-x4r7-m2q9-69c8).
- [1. Impact](#1-impact)
- [2. Scope](#2-scope)
- [3. Patches](#3-patches)
- [4. Reproducing the exploit](#4-reproducing-the-exploit)
- [5. Credit](#5-credit)
- [6. For more information](#6-for-more-information)
### 1. Impact
All versions of `graphql-playground-react` older than `graphql-playground-react@1.7.28` 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 malicious schema in `graphql-playground`. There are several ways this can occur, including by specifying the URL to a malicious schema in the `endpoint` query parameter. If a user clicks on a link to a GraphQL Playground installation that specifies a malicious server, arbitrary JavaScript can run in the user's browser, which can be used to exfiltrate user credentials or other harmful goals.
### 2. Scope
This advisory describes the impact on the `graphql-playground-react` package. The vulnerability also affects `graphiql`, the package from which `graphql-playground` was forked, with a less severe impact; see the [`graphiql` advisory](https://github.com/graphql/graphiql/security/advisories/GHSA-x4r7-m2q9-69c8) for details. It affects all versions of `graphql-playground-react` older than `v1.7.28`.
This vulnerability was introduced with the first public release of `graphql-playground`, so it impacts both the original legacy `graphql-playground` and the contemporary `graphql-playground-react` npm package. It is most easily exploited on `graphql-playground-react@1.7.0` and newer, as that release added functionality which made it possible to override the endpoint URL via query parameter even if it is explicitly specified in the code.
`graphql-playground-react` is commonly loaded via the `graphql-playground-html` package or a middleware package that wraps it (`graphql-playground-express`, `graphql-playground-middleware-koa`, `graphql-playground-middleware-hapi`, or `graphql-playground-middleware-lambda`). By default, these packages render an HTML page which loads the *latest* version of `graphql-playground-react` through a CDN. If you are using one of these packages to install GraphQL Playground on your domain *and you do not explicitly pass the `version` option to `renderPlaygroundPage` or the middleware function*, then you do not need to take any action to resolve this vulnerability, as the latest version of the React app will automatically be loaded.
`graphql-playground-react` is also commonly loaded via HTML served by Apollo Server. Apollo Server always pins a specific version of `graphql-playground-react`, so if you are using Apollo Server you do need to take action to resolve this vulnerability. See the [Apollo Server advisory](https://github.com/apollographql/apollo-server/security/advisories/GHSA-qm7x-rc44-rrqw) for details.
### 3. Patches
`graphql-playground-react@1.7.28` 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.
- **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. Prior to `graphql-playground-react@1.7.28`, GraphQL Playground used two separate libraries to render Markdown: `markdown-it` and `marked`. As part of the development of `graphql-playground-react@1.7.28`, 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.3` does update to the latest version of `markdown-it` (v12, from v10) so that any security fixes in v11 and v12 will take effect. On the other hand, [`marked`](https://github.com/markedjs/marked) recommends the use of a separate HTML sanitizer if its input is untrusted. In this release, we switch the one component which uses `marked` to use `markdown-it` like the rest of the app.
**If you are using `graphql-playground-react` directly in your client app**, upgrade to version 1.7.28 or later.
**If you are using `graphql-playground-html` or a package which starts with `graphql-playground-middleware-` in your server** and you are passing the `version` option to a function imported from that package, change that `version` option to be at least `"1.7.28"`.
**If you are using `graphql-playground-html` or a package which starts with `graphql-playground-middleware-` in your server** and you are **NOT** passing the `version` option to a function imported from that package, no action is necessary; your app automatically loads the latest version of `graphql-playground-react` from CDN.
### 4. Reproducing the exploit
We are hosting a "malicious" server at https://graphql-xss-schema.netlify.app/graphql . This server has a hard-coded introspection result that includes unsafe HTML in type names.
If you manually change a GraphQL Playground installation to use that endpoint, clear the operation pane, and type `{x` into the operation pane, an alert will pop up; this demonstrates execution of code provided by the malicious server.
An URL like https://YOUR-PLAYGROUND-SERVER/?endpoint=https%3A%2F%2Fgraphql-xss-schema.netlify.app%2Fgraphql&query=%7B will load already configured with the endpoint in question. (This URL-based exploit works on `graphql-playground-react@1.7.0` and newer; older versions may be protected from this particular URL-based exploit depending on their configuration.)
### 5. Credit
This vulnerability was discovered by [@Ry0taK](https://github.com/Ry0taK), thank you! :1st_place_medal:
Others who contributed:
- extensive help from [@glasser](https://github.com/glasser) at [Apollo](https://github.com/apollographql)
- [@acao](https://github.com/acao)
- [@imolorhe](https://github.com/imolorhe)
- [@divyenduz](https://github.com/divyenduz)
- [@dotansimha](https://github.com/dotansimha)
- [@timsuchanek](http://github.com/timsuchanek)
- [@benjie](https://github.com/Ry0taK) and many others who provided morale support
### 6. For more information
If you have any questions or comments about this advisory:
- The `graphiql` advisory document contains [more information](https://github.com/graphql/graphiql/blob/main/docs/security/2021-introspection-schema-xss.md#2-more-details-on-the-vulnerability) about how both the client-side and server-side vulnerabilities work
- Open an issue in the [graphql-playground repo](https://github.com/graphql/graphql-playground/new/issues)
| {'CVE-2021-41249'} | 2021-11-04T19:36:13Z | 2021-11-08T18:06:09Z | HIGH | null | {'CWE-79'} | {'https://github.com/graphql/graphiql/security/advisories/GHSA-x4r7-m2q9-69c8', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41249', 'https://github.com/graphql/graphiql/blob/main/docs/security/2021-introspection-schema-xss.md#2-more-details-on-the-vulnerability', 'https://github.com/graphql/graphql-playground', 'https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7', 'https://github.com/graphql/graphql-playground/commit/b8a956006835992f12c46b90384a79ab82bcadad'} | null | {'https://github.com/graphql/graphql-playground/commit/b8a956006835992f12c46b90384a79ab82bcadad'} | {'https://github.com/graphql/graphql-playground/commit/b8a956006835992f12c46b90384a79ab82bcadad'} |
npm | GHSA-j3f7-7rmc-6wqj | Improper certificate management in AWS IoT Device SDK v2 | The AWS IoT Device SDK v2 for Java, Python, C++ and Node.js appends a user supplied Certificate Authority (CA) to the root CAs instead of overriding it on macOS systems. Additionally, SNI validation is also not enabled when the CA has been “overridden”. TLS handshakes will thus succeed if the peer can be verified either from the user-supplied CA or the system’s default trust-store. Attackers with access to a host’s trust stores or are able to compromise a certificate authority already in the host's trust store (note: the attacker must also be able to spoof DNS in this case) may be able to use this issue to bypass CA pinning. An attacker could then spoof the MQTT broker, and either drop traffic and/or respond with the attacker's data, but they would not be able to forward this data on to the MQTT broker because the attacker would still need the user's private keys to authenticate against the MQTT broker. The 'aws_tls_ctx_options_override_default_trust_store_*' function within the aws-c-io submodule has been updated to address this behavior. This issue affects: Amazon Web Services AWS IoT Device SDK v2 for Java versions prior to 1.5.0 on macOS. Amazon Web Services AWS IoT Device SDK v2 for Python versions prior to 1.7.0 on macOS. Amazon Web Services AWS IoT Device SDK v2 for C++ versions prior to 1.14.0 on macOS. Amazon Web Services AWS IoT Device SDK v2 for Node.js versions prior to 1.6.0 on macOS. Amazon Web Services AWS-C-IO 0.10.7 on macOS. | {'CVE-2021-40831'} | 2022-03-03T05:14:12.538986Z | 2021-11-24T20:35:03Z | MODERATE | null | {'CWE-295'} | {'https://github.com/aws/aws-iot-device-sdk-python-v2/commit/5aef82573202309063eb540b72cee0e565f85a2d', 'https://github.com/aws/aws-iot-device-sdk-python-v2', 'https://github.com/awslabs/aws-c-io/', 'https://github.com/aws/aws-iot-device-sdk-cpp-v2', 'https://github.com/aws/aws-iot-device-sdk-js-v2', 'https://github.com/aws/aws-iot-device-sdk-js-v2/commit/22f1989f5bdb0bdd9c912a5a2d255ee6c0854f68', 'https://github.com/aws/aws-iot-device-sdk-java-v2', 'https://nvd.nist.gov/vuln/detail/CVE-2021-40831', 'https://github.com/aws/aws-iot-device-sdk-java-v2/commit/46375e9b1bfb34109b9ff3b1eff9c770f9daa186'} | null | {'https://github.com/aws/aws-iot-device-sdk-js-v2/commit/22f1989f5bdb0bdd9c912a5a2d255ee6c0854f68', 'https://github.com/aws/aws-iot-device-sdk-java-v2/commit/46375e9b1bfb34109b9ff3b1eff9c770f9daa186', 'https://github.com/aws/aws-iot-device-sdk-python-v2/commit/5aef82573202309063eb540b72cee0e565f85a2d'} | {'https://github.com/aws/aws-iot-device-sdk-js-v2/commit/22f1989f5bdb0bdd9c912a5a2d255ee6c0854f68', 'https://github.com/aws/aws-iot-device-sdk-python-v2/commit/5aef82573202309063eb540b72cee0e565f85a2d', 'https://github.com/aws/aws-iot-device-sdk-java-v2/commit/46375e9b1bfb34109b9ff3b1eff9c770f9daa186'} |
npm | GHSA-j6px-jwvv-vpwq | Angular Expressions - Remote Code Execution | ### Impact
The vulnerability, reported by GoSecure Inc, allows Remote Code Execution, if you call `expressions.compile(userControlledInput)` where `userControlledInput` is text that comes from user input.
This time, the security of the package could be bypassed by using a more complex payload, using a `.constructor.constructor` technique.
* If running angular-expressions in the browser, an attacker could run any browser script when the application code calls expressions.compile(userControlledInput).
* If running angular-expressions on the server, an attacker could run any Javascript expression, thus gaining Remote Code Execution.
### Patches
Users should upgrade to version 1.1.2 of angular-expressions
### Workarounds
A temporary workaround might be either to :
* disable user-controlled input that will be fed into angular-expressions in your application
OR
* allow only following characters in the userControlledInput :
```js
if (/^[|a-zA-Z.0-9 :"'+-?]+$/.test(userControlledInput)) {
var result = expressions.compile(userControlledInput);
}
else {
result = undefined;
}
```
### References
[Removal of angular-expression sandbox](http://blog.angularjs.org/2016/09/angular-16-expression-sandbox-removal.html)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [angular-expressions](https://github.com/peerigon/angular-expressions/issues)
* [Email us](mailto:contact@javascript-ninja.fr)
### Credits
The issue was reported by Maxime Nadeau from GoSecure, Inc. | {'CVE-2021-21277'} | 2021-02-01T15:00:53Z | 2021-02-01T15:01:26Z | LOW | null | {'CWE-74'} | {'https://github.com/peerigon/angular-expressions/commit/07edb62902b1f6127b3dcc013da61c6316dd0bf1', 'http://blog.angularjs.org/2016/09/angular-16-expression-sandbox-removal.html', 'https://www.npmjs.com/package/angular-expressions', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21277', 'https://github.com/peerigon/angular-expressions/security/advisories/GHSA-j6px-jwvv-vpwq'} | null | {'https://github.com/peerigon/angular-expressions/commit/07edb62902b1f6127b3dcc013da61c6316dd0bf1'} | {'https://github.com/peerigon/angular-expressions/commit/07edb62902b1f6127b3dcc013da61c6316dd0bf1'} |
npm | GHSA-9w6v-m7wp-jwg4 | Http request which redirect to another hostname do not strip authorization header in @actions/http-client | ### Impact
If consumers of the http-client:
1. make an http request with an authorization header
2. that request leads to a redirect (302) and
3. the redirect url redirects to another domain or hostname
The authorization header will get passed to the other domain.
Note that since this library is for actions, the GITHUB_TOKEN that is available in actions is generated and scoped per job with [these permissions](https://help.github.com/en/actions/configuring-and-managing-workflows/authenticating-with-the-github_token#permissions-for-the-github_token).
### Patches
The problem is fixed in 1.0.8 at [npm here](https://www.npmjs.com/package/@actions/http-client). In 1.0.8, the authorization header is stripped before making the redirected request if the hostname is different.
### Workarounds
None.
### References
https://github.com/actions/http-client/pull/27
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/actions/http-client/issues | {'CVE-2020-11021'} | 2021-08-25T21:03:11Z | 2020-04-29T17:58:53Z | MODERATE | null | {'CWE-200'} | {'https://github.com/actions/http-client/', 'https://github.com/actions/http-client/security/advisories/GHSA-9w6v-m7wp-jwg4', 'https://github.com/actions/http-client/pull/27', 'https://github.com/actions/http-client/commit/f6aae3dda4f4c9dc0b49737b36007330f78fd53a', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11021'} | null | {'https://github.com/actions/http-client/commit/f6aae3dda4f4c9dc0b49737b36007330f78fd53a'} | {'https://github.com/actions/http-client/commit/f6aae3dda4f4c9dc0b49737b36007330f78fd53a'} |
npm | GHSA-77xq-cpvg-7xm2 | Prototype pollution in @tsed/core | "This affects the package @tsed/core before 5.65.7. This vulnerability relates to the deepExtend function which is used as part of the utils directory. Depending on if user input is provided, an attacker can overwrite and pollute the object prototype of a program." | {'CVE-2020-7748'} | 2021-04-20T17:41:36Z | 2021-05-10T19:07:56Z | MODERATE | null | {'CWE-915'} | {'https://github.com/TypedProject/tsed/blob/production/packages/core/src/utils/deepExtends.ts%23L36', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7748', 'https://github.com/TypedProject/tsed/commit/1395773ddac35926cf058fc6da9fb8e82266761b', 'https://snyk.io/vuln/SNYK-JS-TSEDCORE-1019382'} | null | {'https://github.com/TypedProject/tsed/commit/1395773ddac35926cf058fc6da9fb8e82266761b'} | {'https://github.com/TypedProject/tsed/commit/1395773ddac35926cf058fc6da9fb8e82266761b'} |
npm | GHSA-x55w-vjjp-222r | Inefficient Regular Expression in inflect | inflect is customizable inflections for nodejs. inflect is vulnerable to Inefficient Regular Expression Complexity | {'CVE-2021-3820'} | 2022-05-04T03:41:09Z | 2021-09-29T17:12:19Z | MODERATE | null | {'CWE-400', 'CWE-697', 'CWE-1333'} | {'https://huntr.dev/bounties/4612b31a-072b-4f61-a916-c7e4cbc2042a', 'https://github.com/pksunkara/inflect', 'https://github.com/pksunkara/inflect/commit/a9a0a8e9561c3487854c7cae42565d9652ec858b', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3820'} | null | {'https://github.com/pksunkara/inflect/commit/a9a0a8e9561c3487854c7cae42565d9652ec858b'} | {'https://github.com/pksunkara/inflect/commit/a9a0a8e9561c3487854c7cae42565d9652ec858b'} |
npm | GHSA-g694-m8vq-gv9h | URL Confusion When Scheme Not Supplied in medialize/uri.js | Medialize is a Javascript URL mutation library. When parsing a URL without a scheme and with excessive slashes, like ///www.example.com, URI.js will parse the hostname as null and the path as /www.example.com. Such behaviour is different from that exhibited by browsers, which will parse ///www.example.com as http://www.example.com instead. For example, the following will cause a redirect to http://www.example.com: A fix was released in version 1.19.11. | {'CVE-2022-1233'} | 2022-04-15T02:53:33Z | 2022-04-05T00:00:17Z | MODERATE | null | {'CWE-115', 'CWE-601'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-1233', 'https://github.com/medialize/uri.js/commit/88805fd3da03bd7a5e60947adb49d182011f1277', 'https://github.com/medialize/uri.js', 'https://huntr.dev/bounties/228d5548-1109-49f8-8aee-91038e88371c'} | null | {'https://github.com/medialize/uri.js/commit/88805fd3da03bd7a5e60947adb49d182011f1277'} | {'https://github.com/medialize/uri.js/commit/88805fd3da03bd7a5e60947adb49d182011f1277'} |
npm | GHSA-hj48-42vr-x3v9 | Regular Expression Denial of Service in path-parse | Affected versions of npm package `path-parse` are vulnerable to Regular Expression Denial of Service (ReDoS) via splitDeviceRe, splitTailRe, and splitPathRe regular expressions. ReDoS exhibits polynomial worst-case time complexity. | {'CVE-2021-23343'} | 2021-08-10T15:34:57Z | 2021-08-10T15:33:47Z | MODERATE | null | {'CWE-400'} | {'https://github.com/jbgutierrez/path-parse/commit/eca63a7b9a473bf6978a2f5b7b3343662d1506f7', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23343', 'https://github.com/jbgutierrez/path-parse', 'https://github.com/jbgutierrez/path-parse/pull/10', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1279028', 'https://lists.apache.org/thread.html/r6a32cb3eda3b19096ad48ef1e7aa8f26e005f2f63765abb69ce08b85@%3Cdev.myfaces.apache.org%3E', 'https://github.com/jbgutierrez/path-parse/issues/8', 'https://snyk.io/vuln/SNYK-JS-PATHPARSE-1077067'} | null | {'https://github.com/jbgutierrez/path-parse/commit/eca63a7b9a473bf6978a2f5b7b3343662d1506f7'} | {'https://github.com/jbgutierrez/path-parse/commit/eca63a7b9a473bf6978a2f5b7b3343662d1506f7'} |
npm | GHSA-h5q8-5697-9p9h | Cross-Site Request Forgery in express-cart | The express-cart package through 1.1.10 for Node.js allows CSRF. | {'CVE-2020-22403'} | 2021-08-30T17:02:20Z | 2021-08-30T17:22:15Z | HIGH | null | {'CWE-352'} | {'https://security.netapp.com/advisory/ntap-20210909-0004/', 'https://hackerone.com/reports/395944', 'https://www.npmjs.com/package/express-cart', 'https://github.com/mrvautin/expressCart/commit/cd3ba1bc609c2f2946bfbc7ee2fccf3483eb71fb', 'https://github.com/mrvautin/expressCart', 'https://nvd.nist.gov/vuln/detail/CVE-2020-22403'} | null | {'https://github.com/mrvautin/expressCart/commit/cd3ba1bc609c2f2946bfbc7ee2fccf3483eb71fb'} | {'https://github.com/mrvautin/expressCart/commit/cd3ba1bc609c2f2946bfbc7ee2fccf3483eb71fb'} |
npm | GHSA-w973-2qcc-p78x | User Impersonation in converse.js | Versions of `converse.js` prior to 1.0.7 for 1.x or 2.0.5 for 2.x are vulnerable to User Impersonation. The package provides an incorrect implementation of [XEP-0280: Message Carbons](https://xmpp.org/extensions/xep-0280.html) that allows a remote attacker to impersonate any user, including contacts, in the vulnerable application's display. This allows for various kinds of social engineering attacks.
## Recommendation
If you're using `converse.js` 1.x, upgrade to 1.0.7 or later.
If you're using `converse.js` 2.x, upgrade to 2.0.5 or later. | {'CVE-2017-5858'} | 2021-09-28T16:56:35Z | 2020-09-11T21:19:09Z | MODERATE | null | {'CWE-20', 'CWE-346'} | {'https://github.com/jcbrand/converse.js/commit/42f249cabbbf5c026398e6d3b350f6f9536ea572', 'https://www.openwall.com/lists/oss-security/2017/02/09/29', 'https://nvd.nist.gov/vuln/detail/CVE-2017-5858', 'https://rt-solutions.de/wp-content/uploads/2017/02/CVE-2017-5589_xmpp_carbons.pdf', 'http://openwall.com/lists/oss-security/2017/02/09/29', 'https://www.npmjs.com/advisories/974', 'http://www.securityfocus.com/bid/96183', 'https://rt-solutions.de/en/2017/02/CVE-2017-5589_xmpp_carbons/', 'https://github.com/jcbrand/converse.js', 'https://snyk.io/vuln/SNYK-JS-CONVERSEJS-449664'} | null | {'https://github.com/jcbrand/converse.js/commit/42f249cabbbf5c026398e6d3b350f6f9536ea572'} | {'https://github.com/jcbrand/converse.js/commit/42f249cabbbf5c026398e6d3b350f6f9536ea572'} |
npm | GHSA-hxmg-hm46-cf62 | Remote code execution in mongo-express | mongo-express before 1.0.0 offers support for certain advanced syntax but implements this in an unsafe way. NOTE: this may overlap CVE-2019-10769. | {'CVE-2020-24391'} | 2021-03-31T20:14:37Z | 2021-04-13T15:41:01Z | HIGH | null | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-24391', 'https://github.com/mongo-express/mongo-express/commit/3a26b079e7821e0e209c3ee0cc2ae15ad467b91a', 'https://github.com/mongodb-js/query-parser/issues/16'} | null | {'https://github.com/mongo-express/mongo-express/commit/3a26b079e7821e0e209c3ee0cc2ae15ad467b91a'} | {'https://github.com/mongo-express/mongo-express/commit/3a26b079e7821e0e209c3ee0cc2ae15ad467b91a'} |
npm | GHSA-4449-hg37-77v8 | Command injection in total.js | There is a command injection vulnerability that affects the package total.js before version 3.4.7. The issue occurs in the image.pipe and image.stream functions. The type parameter is used to build the command that is then executed using child_process.spawn. The issue occurs because child_process.spawn is called with the option shell set to true and because the type parameter is not properly sanitized. | {'CVE-2020-28494'} | 2021-07-28T18:57:23Z | 2021-02-05T20:43:27Z | HIGH | null | {'CWE-78'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-28494', 'https://github.com/totaljs/framework/commit/6192491ab2631e7c1d317c221f18ea613e2c18a5', 'https://snyk.io/vuln/SNYK-JS-TOTALJS-1046672', 'https://www.npmjs.com/package/total.js'} | null | {'https://github.com/totaljs/framework/commit/6192491ab2631e7c1d317c221f18ea613e2c18a5'} | {'https://github.com/totaljs/framework/commit/6192491ab2631e7c1d317c221f18ea613e2c18a5'} |
npm | GHSA-qffw-8wg7-h665 | Command injection in git-interface | A command injection vulnerability exists in git-interface in the GitHub repository yarkeev/git-interface prior to 2.1.2. If both the git remote and destination directory are provided by user input, then the use of an `--upload-pack` command-line argument feature of git is also supported for `git clone`, which would then allow for any operating system command to be spawned by the attacker. | {'CVE-2022-1440'} | 2022-04-29T17:22:43Z | 2022-04-23T00:03:01Z | CRITICAL | null | {'CWE-78'} | {'https://huntr.dev/bounties/cdc25408-d3c1-4a9d-bb45-33b12a715ca1', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1440', 'https://github.com/yarkeev/git-interface/commit/f828aa790016fee3aa667f7b44cf94bf0aa8c60d', 'https://github.com/yarkeev/git-interface'} | null | {'https://github.com/yarkeev/git-interface/commit/f828aa790016fee3aa667f7b44cf94bf0aa8c60d'} | {'https://github.com/yarkeev/git-interface/commit/f828aa790016fee3aa667f7b44cf94bf0aa8c60d'} |
npm | GHSA-h3rx-g5c9-8q4x | Prototype Pollution in bmoor | The package bmoor before 0.8.12 are vulnerable to Prototype Pollution via the set function. | {'CVE-2020-7736'} | 2021-04-22T22:35:49Z | 2021-05-10T18:37:26Z | HIGH | null | {'CWE-1321'} | {'https://github.com/b-heilman/bmoor/commit/7d4a086a1dc3ef11ed0b323824d02348734b7da5', 'https://www.npmjs.com/package/bmoor', 'https://snyk.io/vuln/SNYK-JS-BMOOR-598664', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7736'} | null | {'https://github.com/b-heilman/bmoor/commit/7d4a086a1dc3ef11ed0b323824d02348734b7da5'} | {'https://github.com/b-heilman/bmoor/commit/7d4a086a1dc3ef11ed0b323824d02348734b7da5'} |
npm | GHSA-qwqc-28w3-fww6 | Message Signature Bypass in openpgp | Versions of `openpgp` prior to 4.2.0 are vulnerable to Message Signature Bypass. The package fails to verify that a message signature is of type `text`. This allows an attacker to to construct a message with a signature type that only verifies subpackets without additional input (such as `standalone` or `timestamp`). For example, an attacker that captures a `standalone` signature packet from a victim can construct arbitrary signed messages that would be verified correctly.
## Recommendation
Upgrade to version 4.2.0 or later.
If you are upgrading from a version <4.0.0 it is highly recommended to read the `High-Level API Changes` section of the `openpgp` 4.0.0 release: https://github.com/openpgpjs/openpgpjs/releases/tag/v4.0.0 | {'CVE-2019-9153'} | 2021-08-17T22:06:12Z | 2019-08-23T21:42:20Z | HIGH | null | {'CWE-347'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-9153', 'https://www.npmjs.com/advisories/1160', 'https://github.com/openpgpjs/openpgpjs/pull/797/commits/327d3e5392a6f59a4270569d200c7f7a2bfc4cbc', 'http://packetstormsecurity.com/files/154191/OpenPGP.js-4.2.0-Signature-Bypass-Invalid-Curve-Attack.html', 'https://sec-consult.com/en/blog/advisories/multiple-vulnerabilities-in-openpgp-js/', 'https://snyk.io/vuln/SNYK-JS-OPENPGP-460248', 'https://github.com/openpgpjs/openpgpjs/releases/tag/v4.2.0', 'https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/Studies/Mailvelope_Extensions/Mailvelope_Extensions_pdf.html#download=1', 'https://github.com/openpgpjs/openpgpjs/pull/816'} | null | {'https://github.com/openpgpjs/openpgpjs/pull/797/commits/327d3e5392a6f59a4270569d200c7f7a2bfc4cbc'} | {'https://github.com/openpgpjs/openpgpjs/pull/797/commits/327d3e5392a6f59a4270569d200c7f7a2bfc4cbc'} |
npm | GHSA-84fq-6626-w5fg | CORS Token Disclosure in crumb | When CORS is enabled on a hapi route handler, it is possible to set a crumb token for a different domain. An attacker would need to have an application consumer visit a site they control, request a route supporting CORS, and then retrieve the token. With this token, they could possibly make requests to non CORS routes as this user.
A configuration and scenario where this would occur is unlikely, as most configurations will set CORS globally (where crumb is not used), or not at all.
## Recommendation
Update to version 3.0.0 or greater. | {'CVE-2014-7193'} | 2020-08-31T18:07:28Z | 2017-10-24T18:33:36Z | MODERATE | null | {'CWE-284'} | {'https://nvd.nist.gov/vuln/detail/CVE-2014-7193', 'https://nodesecurity.io/advisories/crumb_cors_token_disclosure', 'https://github.com/advisories/GHSA-84fq-6626-w5fg', 'https://github.com/spumko/crumb/commit/5e6d4f5c81677fe9e362837ffd4a02394303db3c', 'https://github.com/hapijs/crumb/commit/5e6d4f5c81677fe9e362837ffd4a02394303db3c', 'https://www.npmjs.com/advisories/4'} | null | {'https://github.com/hapijs/crumb/commit/5e6d4f5c81677fe9e362837ffd4a02394303db3c', 'https://github.com/spumko/crumb/commit/5e6d4f5c81677fe9e362837ffd4a02394303db3c'} | {'https://github.com/hapijs/crumb/commit/5e6d4f5c81677fe9e362837ffd4a02394303db3c', 'https://github.com/spumko/crumb/commit/5e6d4f5c81677fe9e362837ffd4a02394303db3c'} |
npm | GHSA-xcvv-84j5-jw9h | Prototype Pollution in assign-deep | Versions of `assign-deep` before 0.4.7 are vulnerable to prototype pollution via merging functions.
## Recommendation
Update to version 0.4.7 or later. | {'CVE-2018-3720'} | 2020-08-31T18:28:34Z | 2018-07-26T15:12:31Z | LOW | null | {'CWE-471'} | {'https://github.com/jonschlinkert/assign-deep/commit/19953a8c089b0328c470acaaaf6accdfcb34da11', 'https://github.com/advisories/GHSA-xcvv-84j5-jw9h', 'https://hackerone.com/reports/310707', 'https://www.npmjs.com/advisories/579', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3720'} | null | {'https://github.com/jonschlinkert/assign-deep/commit/19953a8c089b0328c470acaaaf6accdfcb34da11'} | {'https://github.com/jonschlinkert/assign-deep/commit/19953a8c089b0328c470acaaaf6accdfcb34da11'} |
npm | GHSA-c7pp-g2v2-2766 | DOM-based XSS in gmail-js | Affected versions of `gmail-js` are vulnerable to cross-site scripting in the `tools.parse_response`, `helper.get.visible_emails_post`, and `helper.get.email_data_post` functions, which pass user input directly into the Function constructor.
## Recommendation
Update to version 0.6.5 or later. | {'CVE-2016-1000228'} | 2021-09-23T21:31:53Z | 2020-09-01T15:32:04Z | HIGH | null | {'CWE-79'} | {'https://www.npmjs.com/advisories/125', 'https://github.com/KartikTalwar/gmail.js/issues/281', 'https://github.com/KartikTalwar/gmail.js', 'https://nvd.nist.gov/vuln/detail/CVE-2016-1000228', 'https://github.com/KartikTalwar/gmail.js/commit/a83436f499f9c01b04280af945a5a81137b6baf1'} | null | {'https://github.com/KartikTalwar/gmail.js/commit/a83436f499f9c01b04280af945a5a81137b6baf1'} | {'https://github.com/KartikTalwar/gmail.js/commit/a83436f499f9c01b04280af945a5a81137b6baf1'} |
npm | GHSA-4cpg-3vgw-4877 | Prototype pollution in Plist | Prototype pollution vulnerability via `.parse()` in Plist allows attackers to cause a Denial of Service (DoS) and may lead to remote code execution. | {'CVE-2022-22912'} | 2022-03-23T15:06:35Z | 2022-02-18T00:00:33Z | CRITICAL | null | {'CWE-1321'} | {'https://github.com/TooTallNate/plist.js', 'https://nvd.nist.gov/vuln/detail/CVE-2022-22912', 'https://github.com/TooTallNate/plist.js/pull/118', 'https://github.com/TooTallNate/plist.js/commit/96e2303d059e6be0c9e0c4773226d14b4758de52', 'https://github.com/TooTallNate/plist.js/issues/114'} | null | {'https://github.com/TooTallNate/plist.js/commit/96e2303d059e6be0c9e0c4773226d14b4758de52'} | {'https://github.com/TooTallNate/plist.js/commit/96e2303d059e6be0c9e0c4773226d14b4758de52'} |
npm | GHSA-c9g6-9335-x697 | Improper Input Validation in SocksJS-Node | Incorrect handling of Upgrade header with the value websocket leads in crashing of containers hosting sockjs apps. This affects the package sockjs before 0.3.20. | {'CVE-2020-7693'} | 2021-04-06T21:47:25Z | 2021-04-13T15:27:51Z | MODERATE | null | {'CWE-20'} | {'https://github.com/sockjs/sockjs-node/commit/dd7e642cd69ee74385825816d30642c43e051d16', 'https://www.npmjs.com/package/sockjs', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7693', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-575448', 'https://github.com/andsnw/sockjs-dos-py', 'https://github.com/sockjs/sockjs-node/pull/265', 'https://github.com/sockjs/sockjs-node/issues/252', 'https://snyk.io/vuln/SNYK-JS-SOCKJS-575261'} | null | {'https://github.com/sockjs/sockjs-node/commit/dd7e642cd69ee74385825816d30642c43e051d16'} | {'https://github.com/sockjs/sockjs-node/commit/dd7e642cd69ee74385825816d30642c43e051d16'} |
npm | GHSA-pwhf-39xg-4rxw | Script injection | ### Impact
A malicious internal actor is able to upload documentation content with malicious scripts. These scripts would normally be sanitized by the TechDocs frontend, but by tricking a user to visit the content via the TechDocs API, the content sanitazion will be bypassed. If the TechDocs API is hosted on the same origin as the Backstage app or other backend plugins, this may give access to sensitive data.
The ability to upload malicious content may be limited by internal code review processes, unless the chosen TechDocs deployment method is to use an object store and the actor has access to upload files directly to that store.
### Patches
The vulnerability is patched in the `0.6.4` release of `@backstage/techdocs-common`.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [Backstage repository](https://github.com/backstage/backstage)
* Visit our chat, linked to in [Backstage README](https://github.com/backstage/backstage) | {'CVE-2021-32660'} | 2021-06-04T19:23:33Z | 2021-06-04T19:09:35Z | MODERATE | null | {'CWE-77', 'CWE-434'} | {'https://github.com/backstage/backstage/commit/aad98c544e59369901fe9e0a85f6357644dceb5c', 'https://github.com/backstage/backstage/releases/tag/release-2021-06-03', 'https://github.com/backstage/backstage/security/advisories/GHSA-pwhf-39xg-4rxw', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32660'} | null | {'https://github.com/backstage/backstage/commit/aad98c544e59369901fe9e0a85f6357644dceb5c'} | {'https://github.com/backstage/backstage/commit/aad98c544e59369901fe9e0a85f6357644dceb5c'} |
npm | GHSA-rj44-gpjc-29r7 | [thi.ng/egf] Potential arbitrary code execution of `#gpg`-tagged property values | ### Impact
Potential for arbitrary code execution in `#gpg`-tagged property values (only if `decrypt: true` option is enabled)
### Patches
[A fix](https://github.com/thi-ng/umbrella/commit/3e14765d6bfd8006742c9e7860bc7d58ae94dfa5) has already been released as v0.4.0
### Workarounds
By default, EGF parse functions do NOT attempt to decrypt values (since GPG is only available in non-browser env).
However, if GPG encrypted values are used/required:
1. Perform a regex search for `#gpg`-tagged values in the EGF source file/string and check for backtick (\`) chars in the encrypted value string
2. Replace/remove them or skip parsing if present...
### References
https://github.com/thi-ng/umbrella/security/advisories/GHSA-rj44-gpjc-29r7#advisory-comment-65261
### For more information
If you have any questions or comments about this advisory, please open an issue in the [thi.ng/umbrella repo](https://github.com/thi-ng/umbrella/issues), of which this package is part of. | {'CVE-2021-21412'} | 2021-03-30T20:20:04Z | 2021-04-06T17:22:41Z | MODERATE | null | {'CWE-78'} | {'https://www.npmjs.com/package/@thi.ng/egf', 'https://github.com/thi-ng/umbrella/blob/develop/packages/egf/CHANGELOG.md#040-2021-03-27', 'https://github.com/thi-ng/umbrella/security/advisories/GHSA-rj44-gpjc-29r7', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21412', 'https://github.com/thi-ng/umbrella/commit/88f61656e5f5cfba960013b8133186389efaf243'} | null | {'https://github.com/thi-ng/umbrella/commit/88f61656e5f5cfba960013b8133186389efaf243'} | {'https://github.com/thi-ng/umbrella/commit/88f61656e5f5cfba960013b8133186389efaf243'} |
npm | GHSA-p4pj-mg4r-x6v4 | Denial of Service in uap-core | ## 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 >= v0.11.0
Downstream packages such as uap-python, uap-ruby etc which depend upon uap-core follow different version schemes. | {'CVE-2021-21317'} | 2021-02-16T17:45:27Z | 2021-02-02T15:46:38Z | HIGH | null | {'CWE-400'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-21317', 'https://www.npmjs.com/package/uap-core', 'https://github.com/ua-parser/uap-core/commit/dc9925d458214cfe87b93e35346980612f6ae96c', 'https://github.com/ua-parser/uap-core/security/advisories/GHSA-p4pj-mg4r-x6v4'} | null | {'https://github.com/ua-parser/uap-core/commit/dc9925d458214cfe87b93e35346980612f6ae96c'} | {'https://github.com/ua-parser/uap-core/commit/dc9925d458214cfe87b93e35346980612f6ae96c'} |
npm | GHSA-pfj7-2qfw-vwgm | Path traversal in translator module in NodeBB | ### Impact
Prior to v1.18.5, a path traversal vulnerability was present that allowed users to access JSON files outside of the expected `languages/` directory.
### Patches
The vulnerability has been patched as of v1.18.5.
### Workarounds
Cherry-pick commit hash `c8b2fc46dc698db687379106b3f01c71b80f495f` to receive this patch in lieu of a full upgrade.
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@nodebb.org](mailto:security@nodebb.org)
| {'CVE-2021-43788'} | 2021-11-30T14:35:14Z | 2021-11-30T22:20:43Z | MODERATE | null | {'CWE-22'} | {'https://github.com/NodeBB/NodeBB/security/advisories/GHSA-pfj7-2qfw-vwgm', 'https://github.com/NodeBB/NodeBB/commit/c8b2fc46dc698db687379106b3f01c71b80f495f', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43788', 'https://github.com/NodeBB/NodeBB/releases/tag/v1.18.5', 'https://github.com/NodeBB/NodeBB'} | null | {'https://github.com/NodeBB/NodeBB/commit/c8b2fc46dc698db687379106b3f01c71b80f495f'} | {'https://github.com/NodeBB/NodeBB/commit/c8b2fc46dc698db687379106b3f01c71b80f495f'} |
npm | GHSA-rc8h-3fv6-pxv8 | Denial of Service in hapi | Versions of `hapi` prior to 11.1.3 are affected by a denial of service vulnerability.
The vulnerability is triggered when certain input is passed into the If-Modified-Since or Last-Modified headers.
This causes an 'illegal access' exception to be raised, and instead of sending a HTTP 500 error back to the sender, hapi will continue to hold the socket open until timed out (default node timeout is 2 minutes).
## Recommendation
Update to v11.1.3 or later | {'CVE-2015-9241'} | 2020-08-31T18:09:46Z | 2018-06-07T19:43:15Z | HIGH | null | {'CWE-400'} | {'https://nodesecurity.io/advisories/63', 'https://github.com/jfhbrook/node-ecstatic/pull/179', 'https://github.com/advisories/GHSA-rc8h-3fv6-pxv8', 'https://nodesecurity.io/advisories/64', 'https://nvd.nist.gov/vuln/detail/CVE-2015-9241', 'https://github.com/hapijs/hapi/commit/aab2496e930dce5ee1ab28eecec94e0e45f03580', 'https://www.npmjs.com/advisories/63'} | null | {'https://github.com/hapijs/hapi/commit/aab2496e930dce5ee1ab28eecec94e0e45f03580'} | {'https://github.com/hapijs/hapi/commit/aab2496e930dce5ee1ab28eecec94e0e45f03580'} |
npm | GHSA-fxwf-45c7-4ppr | Prototype pollution in object-hierarchy-access | Overview:Prototype pollution vulnerability in ‘object-hierarchy-access’ versions 0.2.0 through 0.32.0 allows attacker to cause a denial of service and may lead to remote code execution. | {'CVE-2020-28270'} | 2022-01-07T16:07:29Z | 2021-10-12T16:40:58Z | CRITICAL | null | {'CWE-915', 'CWE-1321'} | {'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2020-28270', 'https://github.com/mjpclab/object-hierarchy-access', 'https://github.com/mjpclab/object-hierarchy-access/commit/7b1aa134a8bc4a376296bcfac5c3463aef2b7572', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28270', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2020-28270,'} | null | {'https://github.com/mjpclab/object-hierarchy-access/commit/7b1aa134a8bc4a376296bcfac5c3463aef2b7572'} | {'https://github.com/mjpclab/object-hierarchy-access/commit/7b1aa134a8bc4a376296bcfac5c3463aef2b7572'} |
npm | GHSA-wxj7-97fp-j53j | Exposure of Resource to Wrong Sphere in Zip-Local | The package zip-local before 0.3.5 are vulnerable to Arbitrary File Write via Archive Extraction (Zip Slip) which can lead to an extraction of a crafted file outside the intended extraction directory. | {'CVE-2021-23484'} | 2022-02-07T21:20:28Z | 2022-02-01T00:46:01Z | CRITICAL | null | {'CWE-668', 'CWE-29'} | {'https://snyk.io/vuln/SNYK-JS-ZIPLOCAL-2327477', 'https://github.com/Mostafa-Samir/zip-local/blob/master/main.js%23L365', 'https://github.com/Mostafa-Samir/zip-local', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23484', 'https://github.com/Mostafa-Samir/zip-local/commit/949446a95a660c0752b1db0c654f0fd619ae6085'} | null | {'https://github.com/Mostafa-Samir/zip-local/commit/949446a95a660c0752b1db0c654f0fd619ae6085'} | {'https://github.com/Mostafa-Samir/zip-local/commit/949446a95a660c0752b1db0c654f0fd619ae6085'} |
npm | GHSA-3hjg-vc7r-rcrw | Denial of Service vulnerability in @podium/layout and @podium/proxy | ### Impact
An attacker using the `Trailer` header as part of the request against proxy endpoints has the ability to take down the server.
All Podium layouts that include podlets with proxy endpoints are affected.
### Patches
`@podium/layout` which is the main way developers/users are vulnerable to this exploit, has been patched in version `4.6.110`. All earlier versions are vulnerable.
`@podium/proxy` which is the source of the vulnerability and is used by `@podium/layout` has been patched in version `4.2.74`. All earlier versions are vulnerable.
### Workarounds
It is not easily possible to work around this issue without upgrading. We recommend upgrading `@podium/layout` and/or `@podium/proxy` as soon as possible.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [podium-lib/issues](https://github.com/podium-lib/issues)
### Credits
The vulnerability was reported by [krynos](https://hackerone.com/krynos) from [Ercoli Consulting](https://www.ercoliconsulting.eu/) via FINN.no's private bug bounty program
| {'CVE-2022-24822'} | 2022-04-07T15:20:23Z | 2022-04-07T15:20:23Z | HIGH | null | {'CWE-248'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-24822', 'https://github.com/podium-lib/proxy/commit/9698a40df081217ce142d4de71f929baaa339cdf', 'https://github.com/podium-lib/layout/releases/tag/v4.6.110', 'https://github.com/podium-lib/proxy/security/advisories/GHSA-3hjg-vc7r-rcrw', 'https://github.com/podium-lib/proxy/releases/tag/v4.2.74', 'https://github.com/podium-lib/layout/commit/fe43e655432b0a5f07b6475f67babcc2588fb039'} | null | {'https://github.com/podium-lib/proxy/commit/9698a40df081217ce142d4de71f929baaa339cdf', 'https://github.com/podium-lib/layout/commit/fe43e655432b0a5f07b6475f67babcc2588fb039'} | {'https://github.com/podium-lib/layout/commit/fe43e655432b0a5f07b6475f67babcc2588fb039', 'https://github.com/podium-lib/proxy/commit/9698a40df081217ce142d4de71f929baaa339cdf'} |
npm | GHSA-934w-hvj4-7fr6 | Path Traversal in jsreport-chrome-pdf | This affects the package jsreport-chrome-pdf before 1.10.0. | {'CVE-2020-7762'} | 2021-08-02T15:38:02Z | 2021-04-13T15:25:15Z | MODERATE | null | {'CWE-22'} | {'https://snyk.io/vuln/SNYK-JS-JSREPORTCHROMEPDF-1037310', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7762', 'https://github.com/jsreport/jsreport-chrome-pdf/commit/6750b2f77d05cb843aefc1c4a98097a3bd33a6a2'} | null | {'https://github.com/jsreport/jsreport-chrome-pdf/commit/6750b2f77d05cb843aefc1c4a98097a3bd33a6a2'} | {'https://github.com/jsreport/jsreport-chrome-pdf/commit/6750b2f77d05cb843aefc1c4a98097a3bd33a6a2'} |
npm | GHSA-4vvg-x86p-mvqc | Leaking of user information on Cross-Domain communication in sysend | ### Impact
Users that use Cross-Origin communication and send sensitive information make it possible for this data to be intercepted.
This is not a big impact because it happens only on the same browser.
### Patches
It has been patched in version 1.10.0
### Workarounds
The only workaround is to not send sensitive information with sysend messages.
| {'CVE-2022-24762'} | 2022-03-28T17:26:41Z | 2022-03-14T22:43:23Z | MODERATE | null | {'CWE-200'} | {'https://github.com/jcubic/sysend.js/security/advisories/GHSA-4vvg-x86p-mvqc', 'https://github.com/jcubic/sysend.js/issues/33', 'https://github.com/jcubic/sysend.js/commit/a24f4b776fb18191ae0f7e3d90c2c7bec459431a', 'https://github.com/jcubic/sysend.js/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24762', 'https://github.com/jcubic/sysend.js/releases/tag/1.10.0'} | null | {'https://github.com/jcubic/sysend.js/commit/a24f4b776fb18191ae0f7e3d90c2c7bec459431a'} | {'https://github.com/jcubic/sysend.js/commit/a24f4b776fb18191ae0f7e3d90c2c7bec459431a'} |
npm | GHSA-9gj3-hwp5-pmwc | XSS in the `altField` option of the Datepicker widget in jquery-ui | ### Impact
Accepting the value of the `altField` option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:
```js
$( "#datepicker" ).datepicker( {
altField: "<img onerror='doEvilThing()' src='/404' />",
} );
```
will call the `doEvilThing` function.
### Patches
The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `altField` option is now treated as a CSS selector.
### Workarounds
A workaround is to not accept the value of the `altField` option from untrusted sources.
### For more information
If you have any questions or comments about this advisory, search for a relevant issue in [the jQuery UI repo](https://github.com/jquery/jquery-ui/issues). If you don't find an answer, open a new issue. | {'CVE-2021-41182'} | 2021-10-27T17:00:10Z | 2021-10-26T14:55:02Z | MODERATE | null | {'CWE-79'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NXIUUBRVLA4E7G7MMIKCEN75YN7UFERW/', 'https://github.com/jquery/jquery-ui', 'https://security.netapp.com/advisory/ntap-20211118-0004/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41182', 'https://blog.jqueryui.com/2021/10/jquery-ui-1-13-0-released/', 'https://github.com/jquery/jquery-ui/pull/1954/commits/6809ce843e5ac4128108ea4c15cbc100653c2b63', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://www.drupal.org/sa-contrib-2022-004', 'https://lists.debian.org/debian-lts-announce/2022/01/msg00014.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/O74SXYY7RGXREQDQUDQD4BPJ4QQTD2XQ/', 'https://github.com/jquery/jquery-ui/security/advisories/GHSA-9gj3-hwp5-pmwc', 'https://www.drupal.org/sa-core-2022-002', 'https://www.tenable.com/security/tns-2022-09', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SNXA7XRKGINWSUIPIZ6ZBCTV6N3KSHES/'} | null | {'https://github.com/jquery/jquery-ui/pull/1954/commits/6809ce843e5ac4128108ea4c15cbc100653c2b63'} | {'https://github.com/jquery/jquery-ui/pull/1954/commits/6809ce843e5ac4128108ea4c15cbc100653c2b63'} |
npm | GHSA-cc2p-4jhr-xhhx | False-positive validity for NFT1 genesis transactions in SLPJS | ### Impact
In the npm package named "slpjs", versions prior to 0.27.4 are vulnerable to false-positive validation outcomes for the NFT1 Child Genesis transaction type. A poorly implemented SLP wallet or opportunistic attacker could create a seemingly valid NFT1 child token without burning any of the NFT1 Group token type as is required by the NFT1 specification.
### Patches
npm package "slpjs" has been patched and is published and tagged as version 0.27.4.
### Workarounds
Upgrade to slpjs 0.27.4.
### References
* Package location: https://www.npmjs.com/package/slpjs
* SLP NFT1 spec: https://slp.dev/specs/slp-nft-1/#nft1-protocol-requirements
* Git commit hash fixing this issue: https://github.com/simpleledger/slpjs/commit/290c20e8bff13ac81459d43e54cac232b5e3456c
* Unit tests have been added to assist validator implementations in avoiding this bug: https://github.com/simpleledger/slp-unit-test-data/commit/8c942eacfae12686dcf1f3366321445a4fba73e7
### For more information
If you have any questions or comments about this advisory please open an issue in the [slp-validate](https://github.com/simpleledger/slpjs/issues) repository. | {'CVE-2020-15130'} | 2021-01-07T23:43:05Z | 2020-07-30T14:58:42Z | CRITICAL | null | {'CWE-697'} | {'https://github.com/simpleledger/slpjs/security/advisories/GHSA-cc2p-4jhr-xhhx', 'https://github.com/simpleledger/slpjs/commit/290c20e8bff13ac81459d43e54cac232b5e3456c', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15130'} | null | {'https://github.com/simpleledger/slpjs/commit/290c20e8bff13ac81459d43e54cac232b5e3456c'} | {'https://github.com/simpleledger/slpjs/commit/290c20e8bff13ac81459d43e54cac232b5e3456c'} |
npm | GHSA-7r2x-3qcm-8vfw | Downloads Resources over HTTP in herbivore | Affected versions of `herbivore` 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 `herbivore`.
## Recommendation
The module author has rewritten much of the package, and in that process, patched the vulnerability, but has not published any of the new code to npm.
In order to get an updated version, it is necessary to install the package from github. This can be done using the following command:
```
npm i samatt/herbivore
``` | {'CVE-2016-10665'} | 2021-01-08T19:14:20Z | 2019-02-18T23:44:36Z | HIGH | null | {'CWE-311'} | {'https://github.com/samatt/herbivore', 'https://nodesecurity.io/advisories/258', 'https://www.npmjs.com/advisories/258', 'https://github.com/advisories/GHSA-7r2x-3qcm-8vfw', 'https://github.com/samatt/Herbivore/commit/0a041defc3463e99948e5d2064aef54b2128c5a3', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10665'} | null | {'https://github.com/samatt/Herbivore/commit/0a041defc3463e99948e5d2064aef54b2128c5a3'} | {'https://github.com/samatt/Herbivore/commit/0a041defc3463e99948e5d2064aef54b2128c5a3'} |
npm | GHSA-cph5-m8f7-6c5x | Incorrect Comparison in axios | axios is vulnerable to Inefficient Regular Expression Complexity | {'CVE-2021-3749'} | 2021-09-09T13:39:38Z | 2021-09-01T18:23:02Z | HIGH | null | {'CWE-400', 'CWE-697'} | {'https://www.npmjs.com/package/axios', 'https://github.com/axios/axios', 'https://lists.apache.org/thread.html/r216f0fd0a3833856d6a6a1fada488cadba45f447d87010024328ccf2@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/r3ae6d2654f92c5851bdb73b35e96b0e4e3da39f28ac7a1b15ae3aab8@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/rfa094029c959da0f7c8cd7dc9c4e59d21b03457bf0cedf6c93e1bb0a@%3Cdev.druid.apache.org%3E', 'https://lists.apache.org/thread.html/r4bf1b32983f50be00f9752214c1b53738b621be1c2b0dbd68c7f2391@%3Ccommits.druid.apache.org%3E', 'https://huntr.dev/bounties/1e8f07fc-c384-4ff9-8498-0690de2e8c31', 'https://lists.apache.org/thread.html/r075d464dce95cd13c03ff9384658edcccd5ab2983b82bfc72b62bb10@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/ra15d63c54dc6474b29f72ae4324bcb03038758545b3ab800845de7a1@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/r7324ecc35b8027a51cb6ed629490fcd3b2d7cf01c424746ed5744bf1@%3Ccommits.druid.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3749', 'https://lists.apache.org/thread.html/r74d0b359408fff31f87445261f0ee13bdfcac7d66f6b8e846face321@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/rfc5c478053ff808671aef170f3d9fc9d05cc1fab8fb64431edc66103@%3Ccommits.druid.apache.org%3E', 'https://github.com/axios/axios/commit/5b457116e31db0e88fede6c428e969e87f290929', 'https://lists.apache.org/thread.html/rc263bfc5b53afcb7e849605478d73f5556eb0c00d1f912084e407289@%3Ccommits.druid.apache.org%3E'} | null | {'https://github.com/axios/axios/commit/5b457116e31db0e88fede6c428e969e87f290929'} | {'https://github.com/axios/axios/commit/5b457116e31db0e88fede6c428e969e87f290929'} |
npm | GHSA-fx7m-j728-mjw3 | Moderate severity vulnerability that affects uap-core | An issue was discovered in regex.yaml (aka regexes.yaml) in UA-Parser UAP-Core before 0.6.0. A Regular Expression Denial of Service (ReDoS) issue allows remote attackers to overload a server by setting the User-Agent header in an HTTP(S) request to a value containing a long digit string. (The UAP-Core project contains the vulnerability, propagating to all implementations.) | {'CVE-2018-20164'} | 2021-09-10T20:12:01Z | 2019-03-06T17:35:47Z | MODERATE | null | {'CWE-185'} | {'https://github.com/advisories/GHSA-fx7m-j728-mjw3', 'https://nvd.nist.gov/vuln/detail/CVE-2018-20164', 'https://github.com/ua-parser/uap-core/commit/010ccdc7303546cd22b9da687c29f4a996990014', 'https://www.x41-dsec.de/lab/advisories/x41-2018-009-uaparser/', 'https://github.com/ua-parser/uap-core/issues/332', 'https://github.com/ua-parser/uap-core', 'https://github.com/ua-parser/uap-core/commit/156f7e12b215bddbaf3df4514c399d683e6cdadc'} | null | {'https://github.com/ua-parser/uap-core/commit/010ccdc7303546cd22b9da687c29f4a996990014', 'https://github.com/ua-parser/uap-core/commit/156f7e12b215bddbaf3df4514c399d683e6cdadc'} | {'https://github.com/ua-parser/uap-core/commit/156f7e12b215bddbaf3df4514c399d683e6cdadc', 'https://github.com/ua-parser/uap-core/commit/010ccdc7303546cd22b9da687c29f4a996990014'} |
npm | GHSA-cv3v-7846-6pxm | Unauthorized File Access in node-git-server | Versions of `node-git-server` prior to 0.6.1 are vulnerable to Unauthorized File Access. It is possible to access any git repository by using absolute paths, which may allow attackers to access private repositories.
## Recommendation
Upgrade to version 0.6.1 or later. | null | 2021-09-29T19:59:01Z | 2020-09-03T21:15:19Z | HIGH | null | {'CWE-552'} | {'https://snyk.io/vuln/SNYK-JS-NODEGITSERVER-474343', 'https://github.com/gabrielcsapo/node-git-server/commit/ac26650f69bc445d71e4f2c55328676d10a4be43', 'https://github.com/gabrielcsapo/node-git-server/pull/62', 'https://www.npmjs.com/advisories/1214', 'https://github.com/gabrielcsapo/node-git-server'} | null | {'https://github.com/gabrielcsapo/node-git-server/commit/ac26650f69bc445d71e4f2c55328676d10a4be43'} | {'https://github.com/gabrielcsapo/node-git-server/commit/ac26650f69bc445d71e4f2c55328676d10a4be43'} |
npm | GHSA-j636-crp3-m584 | Cross-site Scripting in tableexport.jquery.plugin | There is a cross-site scripting vulnerability with default `onCellHtmlData` function in GitHub repository hhurz/tableexport.jquery.plugin prior to 1.25.0. This can result in transmitting cookies to third-party servers and/or sending data from secure sessions to third-party servers. | {'CVE-2022-1291'} | 2022-04-22T20:17:22Z | 2022-04-11T00:00:22Z | MODERATE | null | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-1291', 'https://github.com/hhurz/tableexport.jquery.plugin', 'https://github.com/hhurz/tableexport.jquery.plugin/commit/dcbaee23cf98328397a153e71556f75202988ec9', 'https://huntr.dev/bounties/49a14371-6058-47dd-9801-ec38a7459fc5'} | null | {'https://github.com/hhurz/tableexport.jquery.plugin/commit/dcbaee23cf98328397a153e71556f75202988ec9'} | {'https://github.com/hhurz/tableexport.jquery.plugin/commit/dcbaee23cf98328397a153e71556f75202988ec9'} |
npm | GHSA-h4hr-7fg3-h35w | Denial of service in prismjs | The package prismjs before 1.23.0 are vulnerable to Regular Expression Denial of Service (ReDoS) via the prism-asciidoc, prism-rest, prism-tap and prism-eiffel components. | {'CVE-2021-23341'} | 2021-02-24T07:34:23Z | 2021-03-01T19:52:33Z | HIGH | null | {'CWE-400'} | {'https://github.com/PrismJS/prism/commit/c2f6a64426f44497a675cb32dccb079b3eff1609', 'https://github.com/PrismJS/prism/pull/2584', 'https://snyk.io/vuln/SNYK-JS-PRISMJS-1076581', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23341', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARS-1076583', 'https://github.com/PrismJS/prism/issues/2583', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1076582', 'https://www.npmjs.com/package/prismjs'} | null | {'https://github.com/PrismJS/prism/commit/c2f6a64426f44497a675cb32dccb079b3eff1609'} | {'https://github.com/PrismJS/prism/commit/c2f6a64426f44497a675cb32dccb079b3eff1609'} |
npm | GHSA-p3hc-fv2j-rp68 | Prototype Pollution in swiper | Versions of the package swiper before 6.5.1 are susceptible to prototype pollution. | {'CVE-2021-23370'} | 2021-05-07T17:34:38Z | 2021-05-10T15:36:30Z | CRITICAL | null | {'CWE-1321'} | {'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1244696', 'https://snyk.io/vuln/SNYK-JS-SWIPER-1088062', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23370', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARS-1244698', 'https://github.com/nolimits4web/swiper/commit/9dad2739b7474f383474773d5ab898a0c29ac178', 'https://github.com/nolimits4web/Swiper/commit/ec358deab79a8cd2529465f07a0ead5dbcc264ad', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBNOLIMITS4WEB-1244697', 'https://github.com/nolimits4web/swiper/blob/master/CHANGELOG.md#651-2021-03-29', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-1244699'} | null | {'https://github.com/nolimits4web/Swiper/commit/ec358deab79a8cd2529465f07a0ead5dbcc264ad', 'https://github.com/nolimits4web/swiper/commit/9dad2739b7474f383474773d5ab898a0c29ac178'} | {'https://github.com/nolimits4web/swiper/commit/9dad2739b7474f383474773d5ab898a0c29ac178', 'https://github.com/nolimits4web/Swiper/commit/ec358deab79a8cd2529465f07a0ead5dbcc264ad'} |
npm | GHSA-r5fx-8r73-v86c | Cross-Site Scripting in angular | Versions of `angular` prior to 1.5.0-beta.1 are vulnerable to Cross-Site Scripting. The package fails to sanitize `xlink:href` attributes, which may allow attackers to execute arbitrary JavaScript in a victim's browser if the value is user-controlled.
## Recommendation
Upgrade to version 1.5.0-beta.1 or later. | {'CVE-2019-14863'} | 2021-08-19T17:14:00Z | 2020-02-14T23:08:49Z | MODERATE | null | {'CWE-79'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-14863', 'https://github.com/angular/angular.js/pull/12524', 'https://github.com/angular/angular.js/commit/f33ce173c90736e349cf594df717ae3ee41e0f7a', 'https://github.com/angular/angular.js/commit/35a21532b73d5bd84b4325211c563e6a3e2dde82', 'https://nvd.nist.gov/vuln/detail/CVE-2019-14863', 'https://www.npmjs.com/advisories/1453', 'https://snyk.io/vuln/npm:angular:20150807'} | null | {'https://github.com/angular/angular.js/commit/f33ce173c90736e349cf594df717ae3ee41e0f7a', 'https://github.com/angular/angular.js/commit/35a21532b73d5bd84b4325211c563e6a3e2dde82'} | {'https://github.com/angular/angular.js/commit/35a21532b73d5bd84b4325211c563e6a3e2dde82', 'https://github.com/angular/angular.js/commit/f33ce173c90736e349cf594df717ae3ee41e0f7a'} |
npm | GHSA-468q-v4jj-485h | Inefficient Regular Expression Complexity in taro | taro is vulnerable to Inefficient Regular Expression Complexity | {'CVE-2021-3804'} | 2021-09-20T20:00:02Z | 2021-09-20T20:09:59Z | HIGH | null | {'CWE-1333'} | {'https://github.com/nervjs/taro', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3804', 'https://github.com/nervjs/taro/commit/acadb6c826ba57f2030a626f1de4f7b4608fcdb5', 'https://huntr.dev/bounties/0ebe85e6-cc85-42b8-957e-18d8df277414'} | null | {'https://github.com/nervjs/taro/commit/acadb6c826ba57f2030a626f1de4f7b4608fcdb5'} | {'https://github.com/nervjs/taro/commit/acadb6c826ba57f2030a626f1de4f7b4608fcdb5'} |
npm | GHSA-rjmf-p882-645m | Improper Certificate Validation | A specific version of the Node.js mongodb-client-encryption module does not perform correct validation of the KMS server’s certificate. This vulnerability in combination with a privileged network position active MITM attack could result in interception of traffic between the Node.js driver and the KMS service rendering client-side field level encryption (CSFLE) ineffective. This issue was discovered during internal testing and affects mongodb-client-encryption module version 1.2.0, which was available from 2021-Jan-29 and deprecated in the NPM Registry on 2021-Feb-04. This vulnerability does not impact driver traffic payloads with CSFLE-supported key services from applications residing inside the AWS, GCP, and Azure nework fabrics due to compensating controls in these environments. This issue does not impact driver workloads that don’t use Field Level Encryption. | {'CVE-2021-20327'} | 2021-04-12T18:51:10Z | 2021-04-12T18:51:17Z | MODERATE | null | {'CWE-295'} | {'https://jira.mongodb.org/browse/NODE-3125', 'https://github.com/mongodb/libmongocrypt/commit/76365515ff8754b9f705e56428dd0d7efa7f541b', 'https://www.npmjs.com/advisories/1660', 'https://nvd.nist.gov/vuln/detail/CVE-2021-20327'} | null | {'https://github.com/mongodb/libmongocrypt/commit/76365515ff8754b9f705e56428dd0d7efa7f541b'} | {'https://github.com/mongodb/libmongocrypt/commit/76365515ff8754b9f705e56428dd0d7efa7f541b'} |
npm | GHSA-2q4g-w47c-4674 | Unpreventable top-level navigation | ### Impact
The `will-navigate` event that apps use to prevent navigations to unexpected destinations [as per our security recommendations](https://www.electronjs.org/docs/tutorial/security) can be bypassed when a sub-frame performs a top-frame navigation across sites.
### Patches
* `11.0.0-beta.1`
* `10.0.1`
* `9.3.0`
* `8.5.1`
### Workarounds
Sandbox all your iframes using the [`sandbox` attribute](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe#attr-sandbox). This will prevent them creating top-frame navigations and is good practice anyway.
### For more information
If you have any questions or comments about this advisory:
* Email us at security@electronjs.org | {'CVE-2020-15174'} | 2021-11-19T14:44:04Z | 2020-10-06T14:24:04Z | HIGH | null | {'CWE-20', 'CWE-693'} | {'https://github.com/electron/electron', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15174', 'https://github.com/electron/electron/commit/18613925610ba319da7f497b6deed85ad712c59b', 'https://github.com/electron/electron/security/advisories/GHSA-2q4g-w47c-4674'} | null | {'https://github.com/electron/electron/commit/18613925610ba319da7f497b6deed85ad712c59b'} | {'https://github.com/electron/electron/commit/18613925610ba319da7f497b6deed85ad712c59b'} |
npm | GHSA-3cqr-58rm-57f8 | Arbitrary Code Execution in Handlebars | Handlebars before 3.0.8 and 4.x before 4.5.3 is vulnerable to Arbitrary Code Execution. The lookup helper fails to properly validate templates, allowing attackers to submit templates that execute arbitrary JavaScript. This can be used to run arbitrary code on a server processing Handlebars templates or in a victim's browser (effectively serving as XSS). | {'CVE-2019-20920'} | 2021-04-22T23:38:32Z | 2022-02-10T20:38:19Z | HIGH | null | {'CWE-94'} | {'https://www.npmjs.com/advisories/1316', 'https://www.npmjs.com/advisories/1324', 'https://github.com/handlebars-lang/handlebars.js/commit/d54137810a49939fd2ad01a91a34e182ece4528e', 'https://snyk.io/vuln/SNYK-JS-HANDLEBARS-534478', 'https://nvd.nist.gov/vuln/detail/CVE-2019-20920', 'https://www.npmjs.com/package/handlebars'} | null | {'https://github.com/handlebars-lang/handlebars.js/commit/d54137810a49939fd2ad01a91a34e182ece4528e'} | {'https://github.com/handlebars-lang/handlebars.js/commit/d54137810a49939fd2ad01a91a34e182ece4528e'} |
npm | GHSA-2xm2-xj2q-qgpj | receiving subscription objects with deleted session | Original Message:
Hi,
I create objects with one client with an ACL of all users with a specific column value. Thats working so far.
Then I deleted the session object from one user to look if he can receive subscription objects and he can receive them.
The client with the deleted session cant create new objects, which Parse restricts right.
The LiveQueryServer doesnt detect deleted sessions after the websocket connection was established.
There should be a mechanism that checks in an specific interval if the session exists.
I dont know if its true with expired sessions.
Any solutions?
Parse version: 4.3.0
Parse js SDK version: 2.17
Solution:
Hi guys.
I've found and fixed the problem. It happens because there are two caches in place for the session token:
- at Parse Server level, which, according with the docs, should be changed via cacheTTL option and defaults to 5 seconds;
- at Parse Live Query level, which, according with the docs, should be changed via liveQueryServerOptions.cacheTimeout and defaults to 30 days.
But there are three problems:
- cacheTTL has currently no effect over Live Query Server;
- cacheTimeout also has currently no effect over Live Query Server;
- cacheTimeout actually defaults to 1h.
So, currently, if you wait 1 hour after the session token was invalidated, the clients using the old session token are not able to receive the events.
What I did:
- Added a test case for the problem;
- Fixed cacheTTL for Live Query Server;
- Fixed cacheTimeout for Live Query Server;
- Changed the cacheTimeout to default 5s;
- Changed the docs to reflect the actual 5s default for cacheTimeout.
| {'CVE-2020-15270'} | 2021-10-06T22:02:05Z | 2020-10-27T19:15:19Z | MODERATE | null | {'CWE-672'} | {'https://github.com/parse-community/parse-server', 'https://github.com/parse-community/parse-server/security/advisories/GHSA-2xm2-xj2q-qgpj', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15270', 'https://github.com/parse-community/parse-server/commit/78b59fb26b1c36e3cdbd42ba9fec025003267f58'} | null | {'https://github.com/parse-community/parse-server/commit/78b59fb26b1c36e3cdbd42ba9fec025003267f58'} | {'https://github.com/parse-community/parse-server/commit/78b59fb26b1c36e3cdbd42ba9fec025003267f58'} |
npm | GHSA-6jqp-j69q-pm62 | AWS Lambda parser is vulnerable to Regular Expression Denial of Service | index.js in the aws-lambda-multipart-parser NPM package before 0.1.2 has a Regular Expression Denial of Service (ReDoS) issue via a crafted multipart/form-data boundary string. | {'CVE-2018-7560'} | 2022-04-25T22:28:16Z | 2018-03-05T19:16:56Z | HIGH | null | {'CWE-20'} | {'https://github.com/myshenin/aws-lambda-multipart-parser', 'https://github.com/myshenin/aws-lambda-multipart-parser/commit/56ccb03af4dddebc2b2defb348b6558783d5757e', 'https://nvd.nist.gov/vuln/detail/CVE-2018-7560', 'https://github.com/advisories/GHSA-6jqp-j69q-pm62'} | null | {'https://github.com/myshenin/aws-lambda-multipart-parser/commit/56ccb03af4dddebc2b2defb348b6558783d5757e'} | {'https://github.com/myshenin/aws-lambda-multipart-parser/commit/56ccb03af4dddebc2b2defb348b6558783d5757e'} |
npm | GHSA-g8m7-qhv7-9h5x | Path Traversal in serve-here.js | Versions of `serve-here.js` prior to 1.2.0 are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the served folder using relative paths.
## Recommendation
Upgrade to version 1.2.0 or later. | null | 2021-09-22T18:35:22Z | 2019-07-05T21:07:14Z | HIGH | null | {'CWE-22'} | {'https://hackerone.com/reports/569966', 'https://www.npmjs.com/advisories/554', 'https://github.com/vivaxy/here/commit/298dbab41344dfb7f95f66b1fa7b5cfb436bd4a2', 'https://nodesecurity.io/advisories/554', 'https://hackerone.com/reports/296254', 'https://github.com/vivaxy/here/pull/17'} | null | {'https://github.com/vivaxy/here/commit/298dbab41344dfb7f95f66b1fa7b5cfb436bd4a2'} | {'https://github.com/vivaxy/here/commit/298dbab41344dfb7f95f66b1fa7b5cfb436bd4a2'} |
npm | GHSA-j977-g5vj-j27g | Cross-Site Scripting in scratch-svg-renderer | This affects the package scratch-svg-renderer before 0.2.0-prerelease.20201019174008. The loadString function does not escape SVG properly, which can be used to inject arbitrary elements into the DOM via the _transformMeasurements function. | {'CVE-2020-7750'} | 2021-01-07T22:49:01Z | 2020-11-09T14:21:17Z | HIGH | null | {'CWE-79'} | {'https://github.com/LLK/scratch-svg-renderer/commit/9ebf57588aa596c4fa3bb64209e10ade395aee90', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7750', 'https://snyk.io/vuln/SNYK-JS-SCRATCHSVGRENDERER-1020497'} | null | {'https://github.com/LLK/scratch-svg-renderer/commit/9ebf57588aa596c4fa3bb64209e10ade395aee90'} | {'https://github.com/LLK/scratch-svg-renderer/commit/9ebf57588aa596c4fa3bb64209e10ade395aee90'} |
npm | GHSA-pm9p-9926-w68m | Denial of Service in ecstatic | `ecstatic`, a simple static file server middleware, is vulnerable to denial of service. If a payload with a large number of null bytes (`%00`) is provided by an attacker it can crash ecstatic by running it out of memory.
[Results from the original advisory](https://www.checkmarx.com/advisories/denial-of-service-dos-vulnerability-in-ecstatic-npm-package/)
```
A payload of 22kB caused a lag of 1 second,
A payload of 35kB caused a lag of 3 seconds,
A payload of 86kB caused the server to crash
```
## Recommendation
Update to version 2.0.0 or later. | {'CVE-2016-10703'} | 2021-09-16T18:15:09Z | 2017-12-28T22:52:47Z | HIGH | null | {'CWE-20'} | {'https://www.checkmarx.com/advisories/denial-of-service-dos-vulnerability-in-ecstatic-npm-package/', 'https://advisory.checkmarx.net/advisory/CX-2016-4450', 'https://github.com/advisories/GHSA-pm9p-9926-w68m', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10703', 'https://www.npmjs.com/advisories/553', 'https://github.com/jfhbrook/node-ecstatic/commit/71ce93988ead4b561a8592168c72143907189f01#diff-b2b5a88fb51675f1aa1065c093dce1ee', 'https://github.com/jfhbrook/node-ecstatic', 'https://github.com/jfhbrook/node-ecstatic/commit/71ce93988ead4b561a8592168c72143907189f01'} | null | {'https://github.com/jfhbrook/node-ecstatic/commit/71ce93988ead4b561a8592168c72143907189f01#diff-b2b5a88fb51675f1aa1065c093dce1ee', 'https://github.com/jfhbrook/node-ecstatic/commit/71ce93988ead4b561a8592168c72143907189f01'} | {'https://github.com/jfhbrook/node-ecstatic/commit/71ce93988ead4b561a8592168c72143907189f01#diff-b2b5a88fb51675f1aa1065c093dce1ee', 'https://github.com/jfhbrook/node-ecstatic/commit/71ce93988ead4b561a8592168c72143907189f01'} |
npm | GHSA-jxwx-85vp-gvwm | Regular Expression Denial of Service in jquery-validation | The GitHub Security Lab team has identified potential security vulnerabilities in jquery.validation.
The project contains one or more regular expressions that are vulnerable to ReDoS (Regular Expression Denial of Service)
This issue was discovered and reported by GitHub team member @erik-krogh (Erik Krogh Kristensen). | {'CVE-2021-21252'} | 2021-01-13T18:21:42Z | 2021-01-13T18:21:54Z | MODERATE | null | {'CWE-400'} | {'https://github.com/jquery-validation/jquery-validation/pull/2371', 'https://github.com/jquery-validation/jquery-validation/security/advisories/GHSA-jxwx-85vp-gvwm', 'https://security.netapp.com/advisory/ntap-20210219-0005/', 'https://github.com/jquery-validation/jquery-validation/commit/5d8f29eef363d043a8fec4eb86d42cadb5fa5f7d', 'https://www.npmjs.com/package/jquery-validation', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21252'} | null | {'https://github.com/jquery-validation/jquery-validation/commit/5d8f29eef363d043a8fec4eb86d42cadb5fa5f7d'} | {'https://github.com/jquery-validation/jquery-validation/commit/5d8f29eef363d043a8fec4eb86d42cadb5fa5f7d'} |
npm | GHSA-w2pf-g6r8-pg22 | Placeholder property does not indicate HTML capable, could lead to inadvertent abuse | ## Overview
Auth0 Lock version 11.20.4 and earlier did not properly sanitize the generated HTML code. Customers using the `additionalSignUpFields` customization option to add a checkbox to the sign-up dialog that are passing a `placeholder` property obtained from an untrusted source (e.g. a query parameter) could allow cross-site scripting (XSS) on their signup pages.
## Am I affected?
You are affected by this vulnerability if all of the following conditions apply:
- You are using Auth0 Lock version 11.20.4 or earlier.
- You pass `additionalSignUpFields` as options when initializing Lock which includes a field of type `checkbox` whose `placeholder` value is obtained from an untrusted source.
An example of a vulnerable snippet is the following where the `placeholder` value is partially user-controlled by the `name` query parameter:
```javascript
<script>
var params = new URLSearchParams(window.location.search);
var options = {
auth: {
redirectUrl: 'http://localhost:12345/callback',
responseType: 'code',
params: {
scope: 'openid email',
},
},
additionalSignUpFields: [{
name: 'agree',
type: 'checkbox',
placeholder: "I agree to Terms and Conditions for " + params.get('name'),
}],
};
var lock = new Auth0Lock('<CLIENT_ID>', '<TENANT_NAME>.auth0.com', options);
lock.show({
allowShowPassword: true,
initialScreen: 'signUp',
});
</script>
```
## How to fix that?
Developers using Auth0’s signin solution Lock need to upgrade to version 11.21.0 or later. Version 11.21.0 introduces two changes:
1. The existing `placeholder` property is now treated as plain text to mitigate the problem.
2. A new `placeholderHTML` property is introduced that indicates the level of control it provides and that it should be only supplied from trusted sources.
## Will this update impact my users?
This fix patches the Auth0 Lock widget and may require changes in application code, but it will not impact your users, their current state, or any existing sessions.
Developers using the `placeholder` property with HTML content from a trusted source should start using the `placeholderHTML` property to continue providing the same user experience. | {'CVE-2019-20174'} | 2021-08-19T16:48:59Z | 2020-01-31T17:59:51Z | MODERATE | null | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-20174', 'https://auth0.com/docs/security/bulletins/cve-2019-20174', 'https://github.com/auth0/lock/releases/tag/v11.21.0', 'https://github.com/auth0/lock/commit/6c15e5659c21cd814ea119af5c51b61399598dd5', 'https://github.com/auth0/lock/security/advisories/GHSA-w2pf-g6r8-pg22'} | null | {'https://github.com/auth0/lock/commit/6c15e5659c21cd814ea119af5c51b61399598dd5'} | {'https://github.com/auth0/lock/commit/6c15e5659c21cd814ea119af5c51b61399598dd5'} |
npm | GHSA-p72p-rjr2-r439 | Server-Side Request Forgery in terriajs-server | Versions of `terriajs-server`prior to 2.7.4 are vulnerable to Server-Side Request Forgery (SSRF). If an attacker has access to a server whitelisted by the terriajs-server proxy or if the attacker is able to modify the DNS records of a domain whitelisted by the terriajs-server proxy, the attacker can use the terriajs-server proxy to access any HTTP-accessible resources that are accessible to the server, including private resources in the hosting environment.
## Recommendation
Upgrade to version 2.7.4 or later. | null | 2020-08-31T18:35:03Z | 2019-05-29T20:24:02Z | HIGH | null | {'CWE-918'} | {'https://medium.com/terria/security-vulnerability-in-terriajs-server-82c8bf4da0a5', 'https://www.npmjs.com/advisories/768', 'https://github.com/TerriaJS/terriajs-server/commit/3cbc48475f50a53962f605491d0e60648a29bdf0'} | null | {'https://github.com/TerriaJS/terriajs-server/commit/3cbc48475f50a53962f605491d0e60648a29bdf0'} | {'https://github.com/TerriaJS/terriajs-server/commit/3cbc48475f50a53962f605491d0e60648a29bdf0'} |
npm | GHSA-hwqf-gcqm-7353 | Header injection in nodemailer | The package nodemailer before 6.6.1 are vulnerable to HTTP Header Injection if unsanitized user input that may contain newlines and carriage returns is passed into an address object. | {'CVE-2021-23400'} | 2021-06-30T17:38:02Z | 2021-12-10T18:56:57Z | MODERATE | null | {'CWE-74'} | {'https://github.com/nodemailer/nodemailer/issues/1289', 'https://github.com/nodemailer/nodemailer/commit/7e02648cc8cd863f5085bad3cd09087bccf84b9f', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1314737', 'https://snyk.io/vuln/SNYK-JS-NODEMAILER-1296415', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23400'} | null | {'https://github.com/nodemailer/nodemailer/commit/7e02648cc8cd863f5085bad3cd09087bccf84b9f'} | {'https://github.com/nodemailer/nodemailer/commit/7e02648cc8cd863f5085bad3cd09087bccf84b9f'} |
npm | GHSA-r3j7-x2g5-9gx6 | Command injection in samba-client | The samba-client package before 4.0.0 for Node.js allows command injection because of the use of process.exec. | {'CVE-2021-27185'} | 2022-05-03T03:44:37Z | 2021-02-11T20:47:27Z | CRITICAL | null | {'CWE-74', 'CWE-77', 'CWE-78'} | {'https://advisory.checkmarx.net/advisory/CX-2021-4302', 'https://github.com/eflexsystems/node-samba-client/releases/tag/4.0.0', 'https://security.netapp.com/advisory/ntap-20210319-0002/', 'https://github.com/eflexsystems/node-samba-client', 'https://github.com/eflexsystems/node-samba-client/commit/5bc3bbad9b8d02243bc861a11ec73f788fbb1235', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27185', 'https://www.npmjs.com/package/samba-client'} | null | {'https://github.com/eflexsystems/node-samba-client/commit/5bc3bbad9b8d02243bc861a11ec73f788fbb1235'} | {'https://github.com/eflexsystems/node-samba-client/commit/5bc3bbad9b8d02243bc861a11ec73f788fbb1235'} |
npm | GHSA-3hw5-q855-g6cw | Prototype Pollution in Dojox | The Dojox jQuery wrapper `jqMix` mixin method is vulnerable to Prototype Pollution.
Affected Area:
```
//https://github.com/dojo/dojox/blob/master/jq.js#L442
var tobj = {};
for(var x in props){
// the "tobj" condition avoid copying properties in "props"
// inherited from Object.prototype. For example, if obj has a custom
// toString() method, don't overwrite it with the toString() method
// that props inherited from Object.prototype
if((tobj[x] === undefined || tobj[x] != props[x]) && props[x] !== undefined && obj != props[x]){
if(dojo.isObject(obj[x]) && dojo.isObject(props[x])){
if(dojo.isArray(props[x])){
obj[x] = props[x];
}else{
obj[x] = jqMix(obj[x], props[x]);
}
}else{
obj[x] = props[x];
}
``` | {'CVE-2020-5259'} | 2021-02-18T19:45:35Z | 2020-03-10T18:03:32Z | LOW | null | {'CWE-94'} | {'https://github.com/dojo/dojox/security/advisories/GHSA-3hw5-q855-g6cw', 'https://github.com/dojo/dojox/commit/47d1b302b5b23d94e875b77b9b9a8c4f5622c9da', 'https://lists.debian.org/debian-lts-announce/2020/03/msg00012.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5259'} | null | {'https://github.com/dojo/dojox/commit/47d1b302b5b23d94e875b77b9b9a8c4f5622c9da'} | {'https://github.com/dojo/dojox/commit/47d1b302b5b23d94e875b77b9b9a8c4f5622c9da'} |
npm | GHSA-4hpf-3wq7-5rpr | Regular expression deinal of service (ReDoS) in is-my-json-valid | It was discovered that the is-my-json-valid JavaScript library used an inefficient regular expression to validate JSON fields defined to have email format. A specially crafted JSON file could cause it to consume an excessive amount of CPU time when validated. | {'CVE-2018-1107'} | 2021-04-23T20:09:28Z | 2022-01-06T20:44:07Z | MODERATE | null | {'CWE-400'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=1546357', 'https://github.com/mafintosh/is-my-json-valid/commit/b3051b277f7caa08cd2edc6f74f50aeda65d2976', 'https://nvd.nist.gov/vuln/detail/CVE-2018-1107', 'https://github.com/mafintosh/is-my-json-valid/pull/159', 'https://snyk.io/vuln/npm:is-my-json-valid:20180214'} | null | {'https://github.com/mafintosh/is-my-json-valid/commit/b3051b277f7caa08cd2edc6f74f50aeda65d2976'} | {'https://github.com/mafintosh/is-my-json-valid/commit/b3051b277f7caa08cd2edc6f74f50aeda65d2976'} |
npm | GHSA-8c8c-4vfj-rrpc | Reflected Cross-Site Scripting in redis-commander | Affected versions of `redis-commander` contain a cross-site scripting vulnerability in the `highlighterId` paramter of the clipboard.swf component on hosts serving Redis Commander.
Mitigating factors:
Flash must be installed / enabled for this to work. The below proof of concept was verified to work using Firefox 57.0 on Windows 10 by manually installing the [Flash NPAPI Windows plugin](https://get.adobe.com/flashplayer/otherversions/)
## Proof of concept
```
http://instance/jstree/_docs/syntax/clipboard.swf?highlighterId=\%22))}%20catch(e)%20{alert(document.domain);}//
```
## Recommendation
No direct patch for this vulnerability is currently available.
At this time, the best mitigation is to use an alternative, functionally equivalent package, or to use extreme caution when using redis-commander, ensuring that redis-commmander is the only web page you have open, and avoiding clicking on any links. | null | 2022-03-04T22:02:50Z | 2020-09-01T19:05:11Z | LOW | null | {'CWE-79'} | {'https://www.npmjs.com/advisories/562', 'https://github.com/joeferner/redis-commander/commit/1a483ebb3a706cf199dd283cf0aead96606adb14', 'https://hackerone.com/reports/296377', 'https://github.com/joeferner/redis-commander', 'https://github.com/joeferner/redis-commander/releases/tag/v0.5.0'} | null | {'https://github.com/joeferner/redis-commander/commit/1a483ebb3a706cf199dd283cf0aead96606adb14'} | {'https://github.com/joeferner/redis-commander/commit/1a483ebb3a706cf199dd283cf0aead96606adb14'} |
npm | GHSA-35g4-qx3c-vjhx | Automatic room upgrade handling can be used maliciously to bridge a room non-consentually | ### Impact
If a bridge has room upgrade handling turned on in the configuration (the `roomUpgradeOpts` key when instantiating a new `Bridge` instance.), any `m.room.tombstone` event it encounters will be used to unbridge the current room and bridge into the target room. However, the target room `m.room.create` event is not checked to verify if the `predecessor` field contains the previous room. This means that any mailcious admin of a bridged room can repoint the traffic to a different room without the new room being aware.
### Patches
Versions 2.6.1 and greater are patched.
### Workarounds
Disabling the automatic room upgrade handling can be done by removing the `roomUpgradeOpts` key from the `Bridge` class options.
### References
The issue is patched by https://github.com/matrix-org/matrix-appservice-bridge/pull/330
### For more information]
If you have any questions or comments about this advisory, email us at security@matrix.org. | {'CVE-2021-32659'} | 2021-06-16T20:08:37Z | 2021-06-21T17:09:22Z | MODERATE | null | {'CWE-306'} | {'https://github.com/matrix-org/matrix-appservice-bridge/releases/tag/2.6.1', 'https://github.com/matrix-org/matrix-appservice-bridge/commit/b69e745584a34fcfd858df33e4631e420da07b9f', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32659', 'https://github.com/matrix-org/matrix-appservice-bridge/pull/330', 'https://github.com/matrix-org/matrix-appservice-bridge/security/advisories/GHSA-35g4-qx3c-vjhx'} | null | {'https://github.com/matrix-org/matrix-appservice-bridge/commit/b69e745584a34fcfd858df33e4631e420da07b9f'} | {'https://github.com/matrix-org/matrix-appservice-bridge/commit/b69e745584a34fcfd858df33e4631e420da07b9f'} |
npm | GHSA-6vfc-qv3f-vr6c | Uncontrolled Resource Consumption in markdown-it | ### Impact
Special patterns with length > 50K chars can slow down parser significantly.
```js
const md = require('markdown-it')();
md.render(`x ${' '.repeat(150000)} x \nx`);
```
### Patches
Upgrade to v12.3.2+
### Workarounds
No.
### References
Fix + test sample: https://github.com/markdown-it/markdown-it/commit/ffc49ab46b5b751cd2be0aabb146f2ef84986101
| {'CVE-2022-21670'} | 2022-01-19T18:25:52Z | 2022-01-12T22:20:22Z | MODERATE | null | {'CWE-400'} | {'https://github.com/markdown-it/markdown-it/commit/ffc49ab46b5b751cd2be0aabb146f2ef84986101', 'https://github.com/markdown-it/markdown-it', 'https://github.com/markdown-it/markdown-it/security/advisories/GHSA-6vfc-qv3f-vr6c', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21670'} | null | {'https://github.com/markdown-it/markdown-it/commit/ffc49ab46b5b751cd2be0aabb146f2ef84986101'} | {'https://github.com/markdown-it/markdown-it/commit/ffc49ab46b5b751cd2be0aabb146f2ef84986101'} |
npm | GHSA-j9xp-92vc-559j | SQL Injection in sequelize | Affected versions of `sequelize` are vulnerable to SQL Injection. The package fails to sanitize JSON path keys in the MariaDB and MySQL dialects, which may allow attackers to inject SQL statements and execute arbitrary SQL queries.
## Recommendation
If you are using `sequelize` 5.x, upgrade to version 5.8.11 or later.
If you are using `sequelize` 4.x, upgrade to version 4.44.3 or later.
If you are using `sequelize` 3.x, upgrade to version 3.35.1 or later. | {'CVE-2019-10748'} | 2021-08-18T22:09:33Z | 2019-11-06T17:11:10Z | CRITICAL | null | {'CWE-89'} | {'https://github.com/sequelize/sequelize/commit/a72a3f5,', 'https://www.npmjs.com/advisories/1018', 'https://snyk.io/vuln/SNYK-JS-SEQUELIZE-450221', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10748', 'https://github.com/sequelize/sequelize/pull/11089,'} | null | {'https://github.com/sequelize/sequelize/commit/a72a3f5,'} | {'https://github.com/sequelize/sequelize/commit/a72a3f5,'} |
npm | GHSA-49r3-3h96-rwj6 | Cross-Site Scripting in ids-enterprise | Versions of `ids-enterprise` prior to 4.18.2 are vulnerable to Cross-Site Scripting (XSS). The `soho-dropdown` component does not properly encode its output and may allow attackers to execute arbitrary JavaScript.
## Recommendation
Upgrade to version 4.18.2 or later | null | 2020-08-31T18:41:54Z | 2019-06-13T19:09:31Z | HIGH | null | {'CWE-79'} | {'https://www.npmjs.com/advisories/956', 'https://github.com/infor-design/enterprise-ng/issues/503', 'https://github.com/infor-design/enterprise/commit/6bd74d8f38c268b22f31e8169316e065e0093362'} | null | {'https://github.com/infor-design/enterprise/commit/6bd74d8f38c268b22f31e8169316e065e0093362'} | {'https://github.com/infor-design/enterprise/commit/6bd74d8f38c268b22f31e8169316e065e0093362'} |
npm | GHSA-q8pj-2vqx-8ggc | Denial of service in css-what | The css-what package 4.0.0 through 5.0.0 for Node.js does not ensure that attribute parsing has Linear Time Complexity relative to the size of the input. | {'CVE-2021-33587'} | 2021-12-02T17:48:49Z | 2021-06-07T22:11:39Z | HIGH | null | {'CWE-400'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-33587', 'https://github.com/fb55/css-what', 'https://github.com/fb55/css-what/commit/4cdaacfd0d4b6fd00614be030da0dea6c2994655', 'https://github.com/fb55/css-what/releases/tag/v5.0.1', 'https://security.netapp.com/advisory/ntap-20210706-0007/'} | null | {'https://github.com/fb55/css-what/commit/4cdaacfd0d4b6fd00614be030da0dea6c2994655'} | {'https://github.com/fb55/css-what/commit/4cdaacfd0d4b6fd00614be030da0dea6c2994655'} |
npm | GHSA-7pr3-p5fm-8r9x | LiveQuery publishes user session tokens in parse-server | ### Impact
For regular (non-LiveQuery) queries, the session token is removed from the response, but for LiveQuery payloads it is currently not. If a user has a LiveQuery subscription on the `Parse.User` class, all session tokens created during user sign-ups will be broadcast as part of the LiveQuery payload.
### Patches
Remove session token from LiveQuery payload.
### Workaround
Set `user.acl(new Parse.ACL())` in a beforeSave trigger to make the user private already on sign-up. | {'CVE-2021-41109'} | 2021-09-30T16:43:12Z | 2021-09-30T17:09:47Z | HIGH | null | {'CWE-200'} | {'https://github.com/parse-community/parse-server/commit/4ac4b7f71002ed4fbedbb901db1f6ed1e9ac5559', 'https://github.com/parse-community/parse-server/releases/tag/4.10.4', 'https://github.com/parse-community/parse-server', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41109', 'https://github.com/parse-community/parse-server/security/advisories/GHSA-7pr3-p5fm-8r9x'} | null | {'https://github.com/parse-community/parse-server/commit/4ac4b7f71002ed4fbedbb901db1f6ed1e9ac5559'} | {'https://github.com/parse-community/parse-server/commit/4ac4b7f71002ed4fbedbb901db1f6ed1e9ac5559'} |
npm | GHSA-g74r-ffvr-5q9f | Memory Exposure in concat-stream | Versions of `concat-stream` before 1.5.2 are vulnerable to memory exposure if userp provided input is passed into `write()`
Versions <1.3.0 are not affected due to not using unguarded Buffer constructor.
## Recommendation
Update to version 1.5.2, 1.4.11, 1.3.2 or later.
If you are unable to update make sure user provided input into the `write()` function is not a number. | null | 2020-08-31T18:29:17Z | 2019-06-03T17:26:44Z | MODERATE | null | {'CWE-200'} | {'https://github.com/maxogden/concat-stream/pull/47', 'https://nodesecurity.io/advisories/597', 'https://gist.github.com/ChALkeR/c2d2fd3f1d72d51ad883df195be03a85', 'https://github.com/maxogden/concat-stream/pull/47/commits/3e285ba5e5b10b7c98552217f5c1023829efe69e', 'https://www.npmjs.com/advisories/597'} | null | {'https://github.com/maxogden/concat-stream/pull/47/commits/3e285ba5e5b10b7c98552217f5c1023829efe69e'} | {'https://github.com/maxogden/concat-stream/pull/47/commits/3e285ba5e5b10b7c98552217f5c1023829efe69e'} |
npm | GHSA-5fg8-2547-mr8q | Misinterpretation of malicious XML input | ### Impact
xmldom versions 0.6.0 and older do not correctly escape special characters when serializing elements removed from their ancestor. This may lead to unexpected syntactic changes during XML processing in some downstream applications.
### Patches
Update to one of the fixed versions of `@xmldom/xmldom` (`>=0.7.0`)
See issue #271 for the status of publishing `xmldom` to npm or join #270 for Q&A/discussion until it's resolved.
### Workarounds
Downstream applications can validate the input and reject the maliciously crafted documents.
### References
Similar to this one reported on the Go standard library:
- https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/
- https://mattermost.com/blog/securing-xml-implementations-across-the-web/
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [`xmldom/xmldom`](https://github.com/xmldom/xmldom)
* Email us: send an email to **all** addresses that are shown by `npm owner ls @xmldom/xmldom`
| {'CVE-2021-32796'} | 2022-01-04T19:36:30Z | 2021-08-03T16:57:05Z | MODERATE | null | {'CWE-116'} | {'https://www.npmjs.com/package/@xmldom/xmldom', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32796', 'https://github.com/xmldom/xmldom/commit/7b4b743917a892d407356e055b296dcd6d107e8b', 'https://github.com/xmldom/xmldom', 'https://github.com/xmldom/xmldom/security/advisories/GHSA-5fg8-2547-mr8q', 'https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/', 'https://mattermost.com/blog/securing-xml-implementations-across-the-web/'} | null | {'https://github.com/xmldom/xmldom/commit/7b4b743917a892d407356e055b296dcd6d107e8b'} | {'https://github.com/xmldom/xmldom/commit/7b4b743917a892d407356e055b296dcd6d107e8b'} |
npm | GHSA-fq6p-x6j3-cmmq | Denial of service in three | This affects the package three before 0.125.0. This can happen when handling rgb or hsl colors. PoC: var three = require('three') function build_blank (n) { var ret = "rgb(" for (var i = 0; i < n; i++) { ret += " " } return ret + ""; } var Color = three.Color var time = Date.now(); new Color(build_blank(50000)) var time_cost = Date.now() - time; console.log(time_cost+" ms") | {'CVE-2020-28496'} | 2021-02-24T07:40:52Z | 2021-03-01T19:57:16Z | HIGH | null | {'CWE-400'} | {'https://github.com/mrdoob/three.js/pull/21143/commits/4a582355216b620176a291ff319d740e619d583e', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28496', 'https://github.com/mrdoob/three.js/issues/21132', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1065972', 'https://snyk.io/vuln/SNYK-JS-THREE-1064931'} | null | {'https://github.com/mrdoob/three.js/pull/21143/commits/4a582355216b620176a291ff319d740e619d583e'} | {'https://github.com/mrdoob/three.js/pull/21143/commits/4a582355216b620176a291ff319d740e619d583e'} |
npm | GHSA-8948-ffc6-jg52 | Insecure Default Configuration in redbird | Versions of `redbird` prior to 0.9.1 have a vulnerable default configuration of allowing TLS 1.0 connections on `lib/proxy.js`. The package does not provide an option to disable TLS 1.0 which is deprecated and vulnerable.
## Recommendation
Upgrade to version 0.9.1 or later. | null | 2021-08-04T20:58:53Z | 2019-06-06T15:32:21Z | MODERATE | null | {'CWE-20'} | {'https://www.npmjs.com/advisories/828', 'https://github.com/OptimalBits/redbird/pull/207', 'https://github.com/OptimalBits/redbird/commit/39c7a2da84a2ddddfe046ea80e98800518920516', 'https://snyk.io/vuln/SNYK-JS-REDBIRD-174455'} | null | {'https://github.com/OptimalBits/redbird/commit/39c7a2da84a2ddddfe046ea80e98800518920516'} | {'https://github.com/OptimalBits/redbird/commit/39c7a2da84a2ddddfe046ea80e98800518920516'} |
npm | GHSA-mpgr-2cx9-327h | Information disclosure in SSB-DB | ### Impact
_What kind of vulnerability is it? Who is impacted?_
Servers running SSB-DB 20.0.0 (which is packaged with SSB-Server 16.0.0) must upgrade immediately.
**There is no evidence that other SSB apps are vulnerable or that this problem has been exploited in the wild.**
The `get()` method is supposed to only decrypt messages when you explicitly ask it to, but there's a bug where it's decrypting any message that it can. This means that it's returning the decrypted content of private messages, which a malicious peer could use to get access to private data. This only affects peers running SSB-DB@20.0.0 who also have private messages, and is only known to be exploitable if you're also running SSB-OOO (default in SSB-Server), which exposes a thin wrapper around `get()` to anonymous peers.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
Yes, please upgrade to SSB-DB 20.0.1 (or SSB-Server 16.0.1) immediately.
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
You may be able to disable the most obvious attack vector, SSB-OOO, by disabling the plugin, but you should upgrade immediately anyway.
### For more information
If you have any questions or comments about this advisory, open an issue in [SSB-DB](https://github.com/ssbc/ssb-db/) | {'CVE-2020-4045'} | 2021-01-08T20:12:11Z | 2020-06-11T21:09:04Z | HIGH | null | {'CWE-200'} | {'https://github.com/ssbc/ssb-db/security/advisories/GHSA-mpgr-2cx9-327h', 'https://nvd.nist.gov/vuln/detail/CVE-2020-4045', 'https://github.com/ssbc/ssb-db/commit/43334d0871c9cc6220e0f6d6338499060f7761d4'} | null | {'https://github.com/ssbc/ssb-db/commit/43334d0871c9cc6220e0f6d6338499060f7761d4'} | {'https://github.com/ssbc/ssb-db/commit/43334d0871c9cc6220e0f6d6338499060f7761d4'} |
npm | GHSA-2598-2f59-rmhq | SQL Injection in sequelize | Versions of `sequelize` prior to 3.35.1 are vulnerable to SQL Injection. The package fails to sanitize JSON path keys in the Postgres dialect, which may allow attackers to inject SQL statements and execute arbitrary SQL queries.
## Recommendation
Upgrade to version 3.35.1 or later. | {'CVE-2019-10749'} | 2021-08-18T22:10:20Z | 2019-11-08T17:05:17Z | CRITICAL | null | {'CWE-89'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-10749', 'https://www.npmjs.com/advisories/1017', 'https://snyk.io/vuln/SNYK-JS-SEQUELIZE-450222', 'https://github.com/sequelize/sequelize/commit/ee4017379db0059566ecb5424274ad4e2d66bc68'} | null | {'https://github.com/sequelize/sequelize/commit/ee4017379db0059566ecb5424274ad4e2d66bc68'} | {'https://github.com/sequelize/sequelize/commit/ee4017379db0059566ecb5424274ad4e2d66bc68'} |
npm | GHSA-cf4h-3jhx-xvhq | Arbitrary Code Execution in underscore | The package `underscore` from 1.13.0-0 and before 1.13.0-2, from 1.3.2 and before 1.12.1 are vulnerable to Arbitrary Code Execution via the template function, particularly when a variable property is passed as an argument as it is not sanitized. | {'CVE-2021-23358'} | 2021-08-25T17:37:24Z | 2021-05-06T16:09:43Z | HIGH | null | {'CWE-94'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-23358', 'https://github.com/jashkenas/underscore/blob/master/modules/template.js%23L71', 'https://github.com/jashkenas/underscore', 'https://www.tenable.com/security/tns-2021-14', 'https://www.debian.org/security/2021/dsa-4883', 'https://github.com/jashkenas/underscore/pull/2917', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBJASHKENAS-1081505', 'https://snyk.io/vuln/SNYK-JS-UNDERSCORE-1080984', 'https://lists.apache.org/thread.html/r770f910653772317b117ab4472b0a32c266ee4abbafda28b8a6f9306@%3Cissues.cordova.apache.org%3E', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1081503', 'https://github.com/jashkenas/underscore/releases/tag/1.12.1', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EOKATXXETD2PF3OR36Q5PD2VSVAR6J5Z/', 'https://lists.apache.org/thread.html/re69ee408b3983b43e9c4a82a9a17cbbf8681bb91a4b61b46f365aeaf@%3Cissues.cordova.apache.org%3E', 'https://github.com/jashkenas/underscore/commit/4c73526d43838ad6ab43a6134728776632adeb66', 'https://lists.debian.org/debian-lts-announce/2021/03/msg00038.html', 'https://lists.apache.org/thread.html/r5df90c46f7000c4aab246e947f62361ecfb849c5a553dcdb0ef545e1@%3Cissues.cordova.apache.org%3E', 'https://lists.apache.org/thread.html/rbc84926bacd377503a3f5c37b923c1931f9d343754488d94e6f08039@%3Cissues.cordova.apache.org%3E', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FGEE7U4Z655A2MK5EW4UQQZ7B64XJWBV/', 'https://lists.apache.org/thread.html/raae088abdfa4fbd84e1d19d7a7ffe52bf8e426b83e6599ea9a734dba@%3Cissues.cordova.apache.org%3E', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-1081504', 'https://www.npmjs.com/package/underscore'} | null | {'https://github.com/jashkenas/underscore/commit/4c73526d43838ad6ab43a6134728776632adeb66'} | {'https://github.com/jashkenas/underscore/commit/4c73526d43838ad6ab43a6134728776632adeb66'} |
npm | GHSA-4g77-cvgw-grvw | Prototype Pollution in putil-merge | This affects the package putil-merge before 3.8.0. The merge() function does not check the values passed into the argument. An attacker can supply a malicious value by adjusting the value to include the constructor property. Note: This vulnerability derives from an incomplete fix in https://security.snyk.io/vuln/SNYK-JS-PUTILMERGE-1317077 | {'CVE-2021-23470'} | 2022-02-11T16:15:46Z | 2022-02-05T00:00:31Z | HIGH | null | {'CWE-1321'} | {'https://snyk.io/vuln/SNYK-JS-PUTILMERGE-2391487', 'https://github.com/panates/putil-merge/commit/476d00078dfb2827d7c9ee0f2392c81b864f7bc5', 'https://github.com/panates/putil-merge/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23470'} | null | {'https://github.com/panates/putil-merge/commit/476d00078dfb2827d7c9ee0f2392c81b864f7bc5'} | {'https://github.com/panates/putil-merge/commit/476d00078dfb2827d7c9ee0f2392c81b864f7bc5'} |
npm | GHSA-cq8r-fc3q-6hg2 | Denial of Service (DoS) via the unsetByPath function in jsjoints | The package jointjs before 3.3.0 are vulnerable to Denial of Service (DoS) via the unsetByPath function. | {'CVE-2020-28479'} | 2021-04-06T20:51:59Z | 2021-04-13T15:29:40Z | HIGH | null | {'CWE-400'} | {'https://github.com/clientIO/joint/commit/ec7ab01b512a3c06a9944a25d50f255bf07c3499', 'https://snyk.io/vuln/SNYK-JS-JOINTJS-1062038', 'https://github.com/clientIO/joint/releases/tag/v3.3.0', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-1062040', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28479', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1062039'} | null | {'https://github.com/clientIO/joint/commit/ec7ab01b512a3c06a9944a25d50f255bf07c3499'} | {'https://github.com/clientIO/joint/commit/ec7ab01b512a3c06a9944a25d50f255bf07c3499'} |
npm | GHSA-qc22-qwm9-j8rx | Remote Code Execution in npm-groovy-lint | Versions of npm-groovy-lint prior to 9.1.0 bundle vulnerable versions of the Log4j library which are subject to remote code execution via jndi rendering. As a result npm-groovy-lint prior to 9.1.0 is also vulnerable. | null | 2021-12-20T16:57:06Z | 2021-12-20T16:59:31Z | CRITICAL | null | {'CWE-20'} | {'https://github.com/nvuillam/npm-groovy-lint', 'https://github.com/nvuillam/npm-groovy-lint/pull/195', 'https://github.com/advisories/GHSA-jfh8-c2jp-5v3q', 'https://github.com/nvuillam/npm-groovy-lint/commit/0b664519019442052e0190170c2b1c5aff7d72e7', 'https://github.com/nvuillam/npm-groovy-lint/issues/194'} | null | {'https://github.com/nvuillam/npm-groovy-lint/commit/0b664519019442052e0190170c2b1c5aff7d72e7'} | {'https://github.com/nvuillam/npm-groovy-lint/commit/0b664519019442052e0190170c2b1c5aff7d72e7'} |
npm | GHSA-p6jh-p7q8-pcrg | Prototype Pollution in nodee-utils | All versions of package nodee-utils below version 1.2.3 are vulnerable to Prototype Pollution via the deepSet function. | {'CVE-2020-7722'} | 2021-05-05T17:59:12Z | 2021-05-06T18:26:21Z | CRITICAL | null | {'CWE-1321'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-7722', 'https://github.com/nodee-apps/utils/commit/52460d936c52f03c9907bc99ac5e890970cef83c', 'https://snyk.io/vuln/SNYK-JS-NODEEUTILS-598679'} | null | {'https://github.com/nodee-apps/utils/commit/52460d936c52f03c9907bc99ac5e890970cef83c'} | {'https://github.com/nodee-apps/utils/commit/52460d936c52f03c9907bc99ac5e890970cef83c'} |
npm | GHSA-566m-qj78-rww5 | Regular Expression Denial of Service in postcss | The package postcss versions before 7.0.36 or between 8.0.0 and 8.2.13 are vulnerable to Regular Expression Denial of Service (ReDoS) via getAnnotationURL() and loadAnnotation() in lib/previous-map.js. The vulnerable regexes are caused mainly by the sub-pattern \/\*\s* sourceMappingURL=(.*). | {'CVE-2021-23382'} | 2022-02-23T20:31:15Z | 2022-01-07T00:21:36Z | MODERATE | null | {'CWE-400'} | {'https://github.com/postcss/postcss/commit/2b1d04c867995e55124e0a165b7c6622c1735956', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1255641', 'https://github.com/postcss/postcss/releases/tag/7.0.36', 'https://snyk.io/vuln/SNYK-JS-POSTCSS-1255640', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23382'} | null | {'https://github.com/postcss/postcss/commit/2b1d04c867995e55124e0a165b7c6622c1735956'} | {'https://github.com/postcss/postcss/commit/2b1d04c867995e55124e0a165b7c6622c1735956'} |
npm | GHSA-cqqh-49mx-fq63 | Prototype Pollution in merge | merge is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') | {'CVE-2021-3645'} | 2021-09-13T19:14:06Z | 2021-09-13T20:16:54Z | MODERATE | null | {'CWE-915', 'CWE-1321'} | {'https://github.com/viking04/merge', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3645', 'https://github.com/viking04/merge/commit/baba40332080b38b33840d2614df6d4142dedaf6', 'https://huntr.dev/bounties/ef387a9e-ca3c-4c21-80e3-d34a6a896262'} | null | {'https://github.com/viking04/merge/commit/baba40332080b38b33840d2614df6d4142dedaf6'} | {'https://github.com/viking04/merge/commit/baba40332080b38b33840d2614df6d4142dedaf6'} |
npm | GHSA-265q-28rp-chq5 | Insecure Entropy Source - Math.random() in node-uuid | Affected versions of `node-uuid` consistently fall back to using `Math.random` as an entropy source instead of `crypto`, which may result in guessable UUID's.
## Recommendation
Update to version 1.4.4 or later. | {'CVE-2015-8851'} | 2021-08-23T15:25:55Z | 2020-04-16T03:14:50Z | HIGH | null | {'CWE-331'} | {'https://github.com/broofa/node-uuid/commit/672f3834ed02c798aa021c618d0a5666c8da000d', 'https://github.com/broofa/node-uuid/issues/122', 'https://nodesecurity.io/advisories/93', 'https://nvd.nist.gov/vuln/detail/CVE-2015-8851', 'https://bugzilla.redhat.com/show_bug.cgi?id=1327056', 'https://www.npmjs.com/advisories/93', 'https://github.com/broofa/node-uuid/issues/108', 'http://www.openwall.com/lists/oss-security/2016/04/13/8'} | null | {'https://github.com/broofa/node-uuid/commit/672f3834ed02c798aa021c618d0a5666c8da000d'} | {'https://github.com/broofa/node-uuid/commit/672f3834ed02c798aa021c618d0a5666c8da000d'} |
npm | GHSA-3xph-cp8f-2229 | Prototype Pollution in @fabiocaccamo/utils.js | utils.js is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution'). | {'CVE-2021-3815'} | 2021-12-13T13:10:41Z | 2021-12-10T20:31:32Z | HIGH | null | {'CWE-1321'} | {'https://huntr.dev/bounties/20f48c63-f078-4173-bcac-a9f34885f2c0', 'https://github.com/fabiocaccamo/utils.js/commit/102efafb291ce1916985514440d3bf8a6826890a', 'https://github.com/fabiocaccamo/utils.js', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3815'} | null | {'https://github.com/fabiocaccamo/utils.js/commit/102efafb291ce1916985514440d3bf8a6826890a'} | {'https://github.com/fabiocaccamo/utils.js/commit/102efafb291ce1916985514440d3bf8a6826890a'} |
npm | GHSA-xrjf-phvv-r4vr | Command injection in strapi | When creating a strapi app using npxcreate-strapi-app, we can inject arbitrary commands through the template cli argument as per the code in this particular [link](https://github.com/strapi/strapi/blob/master/packages/generators/app/lib/utils/fetch-npm-template.js#L13), this happens due to improper sanitization of user input. | {'CVE-2022-0764'} | 2022-03-09T20:26:21Z | 2022-02-27T00:00:15Z | MODERATE | null | {'CWE-77', 'CWE-78'} | {'https://huntr.dev/bounties/001d1c29-805a-4035-93bb-71a0e81da3e5', 'https://www.github.com/strapi/strapi/commit/2a3f5e988be6a2c7dae5ac22b9e86d579b462f4c', 'https://github.com/strapi/strapi/blob/master/packages/generators/app/lib/utils/fetch-npm-template.js#L13', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0764', 'https://github.com/strapi/strapi', 'https://github.com/strapi/strapi/commit/2a3f5e988be6a2c7dae5ac22b9e86d579b462f4c'} | null | {'https://github.com/strapi/strapi/commit/2a3f5e988be6a2c7dae5ac22b9e86d579b462f4c', 'https://www.github.com/strapi/strapi/commit/2a3f5e988be6a2c7dae5ac22b9e86d579b462f4c'} | {'https://www.github.com/strapi/strapi/commit/2a3f5e988be6a2c7dae5ac22b9e86d579b462f4c', 'https://github.com/strapi/strapi/commit/2a3f5e988be6a2c7dae5ac22b9e86d579b462f4c'} |
npm | GHSA-wvh7-5p38-2qfc | Storing Password in Local Storage | The `setPassword` method (http://parseplatform.org/Parse-SDK-JS/api/2.9.1/Parse.User.html#setPassword) stores the user's password in localStorage as raw text making it vulnerable to anyone with access to your localStorage. We believe this is the only time that password is stored at all. In the documentation under Users > Signing Up, it clearly states, "We never store passwords in plaintext, nor will we ever transmit passwords back to the client in plaintext."
Example Code:
```js
async () => {
const user = Parse.User.current()
if (user) {
user.setPassword('newpass')
await user.save()
}
}
```
After running the above code, the new password will be stored in localStorage as a property named "password".
Proposed Solution:
Before saving anything to localStorage, Parse should strip out any properties named "password" that are attempting to be stored with a Parse.User type object.
Configuration:
Parse SDK: 2.9.1
Parse Server: 3.9.0 | null | 2021-09-22T21:05:43Z | 2020-07-23T18:20:10Z | MODERATE | null | {'CWE-256'} | {'https://github.com/parse-community/Parse-SDK-JS/security/advisories/GHSA-wvh7-5p38-2qfc', 'https://github.com/parse-community/Parse-SDK-JS', 'https://github.com/parse-community/Parse-SDK-JS/commit/d1106174571b699f972929dd7cbb8e45b5283cbb'} | null | {'https://github.com/parse-community/Parse-SDK-JS/commit/d1106174571b699f972929dd7cbb8e45b5283cbb'} | {'https://github.com/parse-community/Parse-SDK-JS/commit/d1106174571b699f972929dd7cbb8e45b5283cbb'} |
npm | GHSA-6m8p-4fxj-pgc2 | OS Command Injection in mversion | The issue occurs because tagName user input is formatted inside the exec function is executed without any checks. | {'CVE-2020-7688'} | 2021-05-11T19:56:27Z | 2021-05-17T21:01:08Z | MODERATE | null | {'CWE-78'} | {'https://github.com/mikaelbr/mversion/commit/b7a8b32600e60759a7ad3921ec4a2750bf173482', 'https://github.com/418sec/huntr/pull/102', 'https://snyk.io/vuln/SNYK-JS-MVERSION-573174', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7688'} | null | {'https://github.com/mikaelbr/mversion/commit/b7a8b32600e60759a7ad3921ec4a2750bf173482'} | {'https://github.com/mikaelbr/mversion/commit/b7a8b32600e60759a7ad3921ec4a2750bf173482'} |
npm | GHSA-68hw-vfh7-xvg8 | Forced Logout in keycloak-connect | Versions of `keycloak-connect` prior to 4.4.0 are vulnerable to Forced Logout. The package fails to validate JWT signatures on the `/k_logout` route, allowing attackers to logout users and craft malicious JWTs with NBF values that prevent user access indefinitely.
## Recommendation
Upgrade to version 4.4.0 or later. | {'CVE-2019-10157'} | 2021-08-16T15:25:07Z | 2019-06-13T20:38:09Z | MODERATE | null | {'CWE-287', 'CWE-345'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10157', 'http://www.securityfocus.com/bid/108734', 'https://snyk.io/vuln/SNYK-JS-KEYCLOAKNODEJSCONNECT-449920', 'https://www.npmjs.com/advisories/978', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10157', 'https://github.com/keycloak/keycloak-nodejs-connect/commit/55e54b55d05ba636bc125a8f3d39f0052d13f8f6'} | null | {'https://github.com/keycloak/keycloak-nodejs-connect/commit/55e54b55d05ba636bc125a8f3d39f0052d13f8f6'} | {'https://github.com/keycloak/keycloak-nodejs-connect/commit/55e54b55d05ba636bc125a8f3d39f0052d13f8f6'} |
npm | GHSA-p6rw-44q7-3fw4 | Stored XSS in Jupyter nbdime | ### Impact
Improper handling of user controlled input caused a stored cross-site scripting (XSS) vulnerability. All previous versions of nbdime are affected.
### Patches
Security patches will be released for each of the major versions of the nbdime packages since version 1.x of the nbdime python package.
#### Python
- nbdime 1.x: Patched in v. 1.1.1
- nbdime 2.x: Patched in v. 2.1.1
- nbdime 3.x: Patched in v. 3.1.1
#### npm
- nbdime 6.x version: Patched in 6.1.2
- nbdime 5.x version: Patched in 5.0.2
- nbdime-jupyterlab 1.x version: Patched in 1.0.1
- nbdime-jupyterlab 2.x version: Patched in 2.1.1
### For more information
If you have any questions or comments about this advisory email us at [security@ipython.org](mailto:security@ipython.org).
| {'CVE-2021-41134'} | 2022-03-03T05:14:20.151154Z | 2021-11-08T18:09:27Z | HIGH | null | {'CWE-79'} | {'https://github.com/jupyter/nbdime/security/advisories/GHSA-p6rw-44q7-3fw4', 'https://github.com/jupyter/nbdime/commit/e44a5cc7677f24b45ebafc756db49058c2f750ea', 'https://github.com/jupyter/nbdime', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41134'} | null | {'https://github.com/jupyter/nbdime/commit/e44a5cc7677f24b45ebafc756db49058c2f750ea'} | {'https://github.com/jupyter/nbdime/commit/e44a5cc7677f24b45ebafc756db49058c2f750ea'} |
npm | GHSA-5rwj-j5m3-3chj | Missing Release of Memory after Effective Lifetime in detect-character-encoding | ### Impact
In detect-character-encoding v0.3.0 and earlier, allocated memory is not released.
### Patches
The problem has been patched in [detect-character-encoding v0.3.1](https://github.com/sonicdoe/detect-character-encoding/releases/tag/v0.3.1).
### CVSS score
[CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/RL:O/RC:C](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/RL:O/RC:C)
Base Score: 7.5 (High)
Temporal Score: 7.2 (High)
Since detect-character-encoding is a library, the scoring is based on the “[reasonable worst-case implementation scenario](https://www.first.org/cvss/v3.1/user-guide#3-7-Scoring-Vulnerabilities-in-Software-Libraries-and-Similar)”, namely, using detect-character-encoding in a program accessible over the internet which becomes unavailable when running out of memory. Depending on your specific implementation, the vulnerability’s severity in your program may be different.
### Proof of concept
```js
const express = require("express");
const detectCharacterEncoding = require("detect-character-encoding");
const app = express();
app.get("/", (req, res) => {
detectCharacterEncoding(Buffer.from("foo"));
res.end();
});
app.listen(3000);
```
`hey -n 1000000 http://localhost:3000` ([`hey`](https://github.com/rakyll/hey)) causes the Node.js process to consume more and more memory.
### References
- https://github.com/sonicdoe/detect-character-encoding/commit/d44356927b92e3b13e178071bf6d7c671766f588
- https://github.com/sonicdoe/detect-character-encoding/pull/6 | {'CVE-2021-39176'} | 2021-10-21T14:28:07Z | 2021-09-01T18:25:16Z | HIGH | null | {'CWE-401'} | {'https://github.com/sonicdoe/detect-character-encoding/releases/tag/v0.3.1', 'https://github.com/sonicdoe/detect-character-encoding/commit/d44356927b92e3b13e178071bf6d7c671766f588', 'https://github.com/sonicdoe/detect-character-encoding/pull/6', 'https://github.com/sonicdoe/detect-character-encoding', 'https://github.com/sonicdoe/detect-character-encoding/security/advisories/GHSA-5rwj-j5m3-3chj', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39176'} | null | {'https://github.com/sonicdoe/detect-character-encoding/commit/d44356927b92e3b13e178071bf6d7c671766f588'} | {'https://github.com/sonicdoe/detect-character-encoding/commit/d44356927b92e3b13e178071bf6d7c671766f588'} |
npm | GHSA-jf5r-8hm2-f872 | Incorrect hostname / protocol due to unstripped leading control characters. | Leading control characters in a URL are not stripped when passed into url-parse. This can cause input URLs to be mistakenly be interpreted as a relative URL without a hostname and protocol, while the WHATWG URL parser will trim control characters and treat it as an absolute URL.
If url-parse is used in security decisions involving the hostname / protocol, and the input URL is used in a client which uses the WHATWG URL parser, the decision may be incorrect.
This can also lead to a cross-site scripting (XSS) vulnerability if url-parse is used to check for the javascript: protocol in URLs. See following example:
`````
const parse = require('url-parse')
const express = require('express')
const app = express()
const port = 3000
url = parse(\"\\bjavascript:alert(1)\")
console.log(url)
app.get('/', (req, res) => {
if (url.protocol !== \"javascript:\") {res.send(\"<a href=\\'\" + url.href + \"\\'>CLICK ME!</a>\")}
})
app.listen(port, () => {
console.log(`Example app listening on port ${port}`)
})
````` | {'CVE-2022-0691'} | 2022-03-11T22:47:09Z | 2022-02-22T00:00:30Z | MODERATE | null | {'CWE-639'} | {'https://github.com/unshiftio/url-parse', 'https://github.com/unshiftio/url-parse/commit/0e3fb542d60ddbf6933f22eb9b1e06e25eaa5b63', 'https://huntr.dev/bounties/57124ed5-4b68-4934-8325-2c546257f2e4', 'https://security.netapp.com/advisory/ntap-20220325-0006/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0691'} | null | {'https://github.com/unshiftio/url-parse/commit/0e3fb542d60ddbf6933f22eb9b1e06e25eaa5b63'} | {'https://github.com/unshiftio/url-parse/commit/0e3fb542d60ddbf6933f22eb9b1e06e25eaa5b63'} |
npm | GHSA-897m-rjf5-jp39 | Prototype Pollution in copy-props | The package copy-props before 2.0.5 are vulnerable to Prototype Pollution via the main functionality. | {'CVE-2020-28503'} | 2021-03-24T23:59:08Z | 2022-01-06T20:35:05Z | HIGH | null | {'CWE-1321'} | {'https://github.com/gulpjs/copy-props/pull/7', 'https://github.com/gulpjs/copy-props/commit/2c738f5c52cfb384b43d977a56a3ab7ce465df9b', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28503', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1088047', 'https://snyk.io/vuln/SNYK-JS-COPYPROPS-1082870'} | null | {'https://github.com/gulpjs/copy-props/commit/2c738f5c52cfb384b43d977a56a3ab7ce465df9b'} | {'https://github.com/gulpjs/copy-props/commit/2c738f5c52cfb384b43d977a56a3ab7ce465df9b'} |
npm | GHSA-9qmh-276g-x5pj | Prototype Pollution in immer | ## Overview
Affected versions of immer are vulnerable to Prototype Pollution.
## Proof of exploit
```
const {applyPatches, enablePatches} = require("immer");
enablePatches();
let obj = {};
console.log("Before : " + obj.polluted);
applyPatches({}, [ { op: 'add', path: [ "__proto__", "polluted" ], value: "yes" } ]);
// applyPatches({}, [ { op: 'replace', path: [ "__proto__", "polluted" ], value: "yes" } ]);
console.log("After : " + obj.polluted);
```
## Remediation
Version 8.0.1 contains a [fix](https://github.com/immerjs/immer/commit/da2bd4fa0edc9335543089fe7d290d6a346c40c5) for this vulnerability, updating is recommended. | {'CVE-2020-28477'} | 2021-01-20T21:27:33Z | 2021-01-20T21:27:56Z | HIGH | null | {'CWE-471'} | {'https://github.com/immerjs/immer/issues/738', 'https://www.npmjs.com/package/immer', 'https://github.com/immerjs/immer/blob/master/src/plugins/patches.ts%23L213', 'https://github.com/immerjs/immer/commit/da2bd4fa0edc9335543089fe7d290d6a346c40c5', 'https://snyk.io/vuln/SNYK-JS-IMMER-1019369', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28477', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1061986'} | null | {'https://github.com/immerjs/immer/commit/da2bd4fa0edc9335543089fe7d290d6a346c40c5'} | {'https://github.com/immerjs/immer/commit/da2bd4fa0edc9335543089fe7d290d6a346c40c5'} |
npm | GHSA-35jh-r3h4-6jhm | Command Injection in lodash | `lodash` versions prior to 4.17.21 are vulnerable to Command Injection via the template function. | {'CVE-2021-23337'} | 2022-02-08T21:35:09Z | 2021-05-06T16:05:51Z | HIGH | null | {'CWE-77'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-23337', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARS-1074930', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1074929', 'https://github.com/lodash/lodash', 'https://security.netapp.com/advisory/ntap-20210312-0006/', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-1074928', 'https://snyk.io/vuln/SNYK-JS-LODASH-1040724', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBLODASH-1074931', 'https://github.com/lodash/lodash/blob/ddfd9b11a0126db2302cb70ec9973b66baec0975/lodash.js#L14851', 'https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c', 'https://snyk.io/vuln/SNYK-JAVA-ORGFUJIONWEBJARS-1074932', 'https://github.com/lodash/lodash/blob/ddfd9b11a0126db2302cb70ec9973b66baec0975/lodash.js%23L14851', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c'} | {'https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c'} |
npm | GHSA-9vxc-g2jx-qj3p | API Admin Auth Weakness in tomato | Versions of `tomato` prior to 0.0.6 are affected by a somewhat complex authentication bypass vulnerability in the admin service when only a single access key is configured on the server. The vulnerability allows an attacker to guess the password for the admin service, no matter how complex that password is, in less than 200 requests.
## Details
The tomato API has an admin service that is enabled by setting up an `access_key` in the config options. This `access_key` is intended to protect the API admin from unauthorized access.
Tomato verifies the `access_key` by checking to see if the server `access_key` incorporates the user provided value at any location. This allows an attacker to provide a single character as an `access_key`, and so long as the server key contains at least one instance of that character it will be considered a valid key.
## Proof of Concept
This is the snippet of code that does the comparison to authorize requests.
```
if (access_key && config.master.api.access_key.indexOf(access_key) !== -1) {
```
For an access_key that is set to anything that includes the letter 'a' the following request would be authorized.
```
$ curl -X POST "http://localhost:8081/api/exec" -H "Content-Type: application/json" -d @test -H "access-key: a"
{
"cmd": "ls",
"path": ".",
"stdout": "app.js\nconfig.js\nlog\nnode_modules\nserver.js\n",
"stderr": ""
}
```
## Recommendation
Update to version 0.0.6 or later. | {'CVE-2013-7379'} | 2021-09-23T21:00:28Z | 2020-08-31T22:59:07Z | CRITICAL | null | {'CWE-287'} | {'https://github.com/leizongmin/tomato/commit/9e427d524e04a905312a3294c85e939ed7d57b8c', 'https://github.com/leizongmin/tomato', 'https://www.npmjs.com/advisories/38', 'https://nvd.nist.gov/vuln/detail/CVE-2013-7379', 'https://nodesecurity.io/advisories/Tomato_API_Admin_Auth_Weakness', 'http://www.openwall.com/lists/oss-security/2014/05/15/2', 'http://www.openwall.com/lists/oss-security/2014/05/13/1'} | null | {'https://github.com/leizongmin/tomato/commit/9e427d524e04a905312a3294c85e939ed7d57b8c'} | {'https://github.com/leizongmin/tomato/commit/9e427d524e04a905312a3294c85e939ed7d57b8c'} |
npm | GHSA-qmw8-3v4g-gwj4 | 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
A patch have been submitted by Corey Farrell git@cfware.com, the reporter.
All releases after v4.0.2 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-21321'} | 2021-03-02T03:32:13Z | 2021-03-03T01:52:05Z | CRITICAL | null | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-21321', 'https://www.npmjs.com/package/fastify-reply-from', 'https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-qmw8-3v4g-gwj4', 'https://github.com/fastify/fastify-reply-from/commit/dea227dda606900cc01870d08541b4dcc69d3889'} | null | {'https://github.com/fastify/fastify-reply-from/commit/dea227dda606900cc01870d08541b4dcc69d3889'} | {'https://github.com/fastify/fastify-reply-from/commit/dea227dda606900cc01870d08541b4dcc69d3889'} |
npm | GHSA-h9mj-fghc-664w | Denial of Service in mqtt | Affected versions of `mqtt` do not properly handle PUBLISH packets returning from the server, leading to a Denial of Service condition.
The vulnerability is completely mitigated if the only connected servers are trusted, guaranteed not to be under the control of a malicious actor.
## Proof of Concept
The following is a demonstration of how to generate the malicious packet sequence, but does not include information on handling the initial network connections and MQTT overhead.
```
var mqttp = require('mqtt-packet');
var packets = [];
for(var i=0; i<=1000;i++){
packets.push(
mqttp.generate({
cmd:'publish',
topic:Buffer.from('hello'),
payload:Buffer.from('world'),
retain: false,
dup: false,
messageId: ++i,
qos: 1
})
)
}
```
## Recommendation
Update to version 2.15.0 or later. | {'CVE-2017-10910'} | 2021-09-14T17:16:40Z | 2017-12-28T22:51:58Z | MODERATE | null | {'CWE-674'} | {'https://github.com/mqttjs/MQTT.js', 'https://jvn.jp/en/jp/JVN45494523/index.html', 'https://github.com/advisories/GHSA-h9mj-fghc-664w', 'https://github.com/nodejs/security-wg/blob/master/vuln/npm/357.json', 'https://nvd.nist.gov/vuln/detail/CVE-2017-10910', 'https://www.npmjs.com/advisories/555', 'https://github.com/mqttjs/MQTT.js/releases/tag/v2.15.0', 'https://github.com/mqttjs/MQTT.js/commit/403ba53b838f2d319a0c0505a045fe00239e9923'} | null | {'https://github.com/mqttjs/MQTT.js/commit/403ba53b838f2d319a0c0505a045fe00239e9923'} | {'https://github.com/mqttjs/MQTT.js/commit/403ba53b838f2d319a0c0505a045fe00239e9923'} |
npm | GHSA-5w9c-rv96-fr7g | Removal of functional code in faker.js | Faker.js helps users create large amounts of data for testing and development. The maintainer deliberately removed the functional code from this package. This appears to be a purposeful and successful attempt to make the package unusable. This is related to the colors.js [CVE-2021-23567](https://github.com/advisories/GHSA-gh88-3pxp-6fm8).
The functional code for this package was forked and can be found [here](https://github.com/faker-js/faker). | null | 2022-03-22T20:33:40Z | 2022-03-22T19:28:24Z | HIGH | null | null | {'https://nvd.nist.gov/vuln/detail/CVE-2021-23567', 'https://github.com/advisories/GHSA-gh88-3pxp-6fm8', 'https://www.npmjs.com/package/faker', 'https://www.npmjs.com/package/@faker-js/faker', 'https://github.com/Marak/Faker.js', 'https://github.com/Marak/colors.js/issues/285', 'https://github.com/Marak/colors.js/issues/285%23issuecomment-1008212640', 'https://github.com/Marak/colors.js/commit/074a0f8ed0c31c35d13d28632bd8a049ff136fb6#diff-92bbac9a308cd5fcf9db165841f2d90ce981baddcb2b1e26cfff170929af3bd1R18', 'https://snyk.io/vuln/SNYK-JS-COLORS-2331906'} | null | {'https://github.com/Marak/colors.js/commit/074a0f8ed0c31c35d13d28632bd8a049ff136fb6#diff-92bbac9a308cd5fcf9db165841f2d90ce981baddcb2b1e26cfff170929af3bd1R18'} | {'https://github.com/Marak/colors.js/commit/074a0f8ed0c31c35d13d28632bd8a049ff136fb6#diff-92bbac9a308cd5fcf9db165841f2d90ce981baddcb2b1e26cfff170929af3bd1R18'} |
npm | GHSA-mmj4-777p-fpq9 | Validation bypass in frourio-express | ## 日本語
### 影響
v0.26.0以前のfrourioを使用している、かつvalidators/を利用している場合、ネストされたバリデータがリクエストのボディーとクエリに対して正しく働かないケースがあります。また、リクエストに対してバリデーションが効かなくなる入力があります。
### パッチ
frourioをv0.26.0かそれ以降のバージョンにアップデートをお願いします。frourio を使用したプロジェクトには `class-transformer` と `reflect-metadata` の依存への追加も必要となります。
### ワークアラウンド
controller側で自分でclass-transformerを使用してチェックする、vaildatorを使わない、など。
### さらなる情報
このセキュリティ勧告に関する質問やコメントについては、以下の方法でお問い合わせいただけます。
* [frourio](https://github.com/frouriojs/frourio)にIssueを開く。
## English
### Impact
Frourio users who uses frourio version prior to v0.26.0 and integration with class-validator through `validators/` folder. Validators does not work properly for request bodies and queries in specific situations. Addtionally, some kind of input is not validated. (false positives)
### Patches
Please update your frourio to v0.26.0 or later. You also need to install `class-transformer` and `reflect-metadata` to your project.
### Workarounds
Validate objects from request with class-transformer in controllers by yourself, or prevent using validators.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [frourio](https://github.com/frouriojs/frourio)
| {'CVE-2022-23624'} | 2022-02-14T22:32:36Z | 2022-02-07T22:38:37Z | HIGH | null | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-23624', 'https://github.com/frouriojs/frourio-express', 'https://github.com/frouriojs/frourio-express/security/advisories/GHSA-mmj4-777p-fpq9', 'https://github.com/frouriojs/frourio-express/commit/73ded5c6f9f1c126c0cb2d05c0505e9e4db142d2'} | null | {'https://github.com/frouriojs/frourio-express/commit/73ded5c6f9f1c126c0cb2d05c0505e9e4db142d2'} | {'https://github.com/frouriojs/frourio-express/commit/73ded5c6f9f1c126c0cb2d05c0505e9e4db142d2'} |
npm | GHSA-4vmm-mhcq-4x9j | Sandbox Bypass Leading to Arbitrary Code Execution in constantinople | Versions of `constantinople` prior to 3.1.1 are vulnerable to a sandbox bypass which can lead to arbitrary code execution.
## Recommendation
Update to version 3.1.1 or later. | null | 2021-08-16T16:06:38Z | 2019-06-14T16:15:14Z | CRITICAL | null | null | {'https://github.com/pugjs/constantinople/commit/01d409c0d081dfd65223e6b7767c244156d35f7f', 'https://snyk.io/vuln/npm:constantinople:20180421', 'https://www.npmjs.com/advisories/568', 'https://nodesecurity.io/advisories/568', 'https://bugzilla.redhat.com/show_bug.cgi?id=1577703'} | null | {'https://github.com/pugjs/constantinople/commit/01d409c0d081dfd65223e6b7767c244156d35f7f'} | {'https://github.com/pugjs/constantinople/commit/01d409c0d081dfd65223e6b7767c244156d35f7f'} |
npm | GHSA-gpfj-4j6g-c4w9 | Clipboard-based DOM-XSS | ### Impact
A self Cross-Site Scripting vulnerability exists in the @github/paste-markdown library. If the clipboard data contains the string `<table>`, a **div** is dynamically created, and the clipboard content is copied into its **innerHTML** property without any sanitization, resulting in improper execution of JavaScript in the browser of the victim (the user who pasted the code). Users directed to copy text from a malicious website and paste it into pages that utilize this library are affected.
The following @github/paste-markdown code snippet is triggered when the user pastes something and the browser's clipboard data contains an entry whose content-type is **text/HTML**.
```typescript
function generateText(transfer: DataTransfer): string | undefined {
if (Array.from(transfer.types).indexOf('text/html') === -1) return
let html = transfer.getData('text/html')
if (!/<table/i.test(html)) return
html = html.replace(/<meta.*?>/, '')
const el = document.createElement('div')
el.innerHTML = html
const tables = el.querySelectorAll('table')
for (const table of tables) {
if (table.closest('[data-paste-markdown-skip]')) {
table.replaceWith(new Text(table.textContent || ''))
}
const formattedTable = tableMarkdown(table)
table.replaceWith(new Text(formattedTable))
}
return el.innerHTML
}
```
### Patches
A security patch was released in [version 0.3.4](https://github.com/github/paste-markdown/releases/tag/v0.3.4).
### Workarounds
A Content Security Policy that prevents `unsafe-inline` helps reduce the likelihood of this vulnerability being exploited in modern browsers.
<!--
### References
_Are there any links users can visit to find out more?_
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [example link to repo](http://example.com)
* Email us at [example email address](mailto:example@example.com)
*
-->
| {'CVE-2021-37700'} | 2021-08-30T23:16:08Z | 2021-08-12T20:42:17Z | MODERATE | null | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-37700', 'https://github.com/github/paste-markdown/commit/32b7ea3f29ae8f256f9d19768387be42678ddf30', 'https://github.com/github/paste-markdown', 'https://github.com/github/paste-markdown/releases/tag/v0.3.4', 'https://github.com/github/paste-markdown/security/advisories/GHSA-gpfj-4j6g-c4w9', 'https://www.npmjs.com/package/@github/paste-markdown'} | null | {'https://github.com/github/paste-markdown/commit/32b7ea3f29ae8f256f9d19768387be42678ddf30'} | {'https://github.com/github/paste-markdown/commit/32b7ea3f29ae8f256f9d19768387be42678ddf30'} |
npm | GHSA-pxcf-v868-m492 | Injection and Cross-site Scripting in osm-static-maps | This affects all versions of package osm-static-maps under 3.9.0. User input given to the package is passed directly to a template without escaping ({{{ ... }}}). As such, it is possible for an attacker to inject arbitrary HTML/JS code and depending on the context. It will be outputted as an HTML on the page which gives opportunity for XSS or rendered on the server (puppeteer) which also gives opportunity for SSRF and Local File Read. | {'CVE-2020-7749'} | 2021-08-02T15:31:49Z | 2021-05-10T18:43:45Z | HIGH | null | {'CWE-74', 'CWE-79'} | {'https://github.com/jperelli/osm-static-maps/commit/97355d29e08753d1cfe99b1281dbaa06f4e651b0', 'https://snyk.io/vuln/SNYK-JS-OSMSTATICMAPS-609637', 'https://github.com/jperelli/osm-static-maps/pull/24', 'https://github.com/jperelli/osm-static-maps/blob/master/src/template.html%23L142', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7749'} | null | {'https://github.com/jperelli/osm-static-maps/commit/97355d29e08753d1cfe99b1281dbaa06f4e651b0'} | {'https://github.com/jperelli/osm-static-maps/commit/97355d29e08753d1cfe99b1281dbaa06f4e651b0'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.