Datasets:

aswin1906

/

github-advisory-2020.csv

like 0

1.4.0

GHSA-xq5j-gw7f-jgj8

2023-08-08T15:14:47Z

2020-07-07T16:34:10Z

['CVE-2020-8167']

CSRF Vulnerability in rails-ujs

There is a vulnerability in rails-ujs that allows attackers to send CSRF tokens to wrong domains. Versions Affected: rails <= 6.0.3 Not affected: Applications which don't use rails-ujs. Fixed Versions: rails >= 5.2.4.3, rails >= 6.0.3.1 Impact ------ This is a regression of CVE-2015-1840. In the scenario where an attacker might be able to control the href attribute of an anchor tag or the action attribute of a form tag that will trigger a POST action, the attacker can set the href or action to a cross-origin URL, and the CSRF token will be sent. Workarounds ----------- To work around this problem, change code that allows users to control the href attribute of an anchor tag or the action attribute of a form tag to filter the user parameters. For example, code like this: link_to params to code like this: link_to filtered_params def filtered_params # Filter just the parameters that you trust end

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N'}]

[{'package': {'ecosystem': 'RubyGems', 'name': 'actionview'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '5.0.0'}, {'fixed': '5.2.4.3'}]}], 'database_specific': {'last_known_affected_version_range': '<= 5.2.4.2'}}, {'package': {'ecosystem': 'RubyGems', 'name': 'actionview'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '6.0.0'}, {'fixed': '6.0.3.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.0.3'}}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-8167'}, {'type': 'WEB', 'url': 'https://hackerone.com/reports/189878'}, {'type': 'WEB', 'url': 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/actionview/CVE-2020-8167.yml'}, {'type': 'WEB', 'url': 'https://groups.google.com/forum/#!topic/rubyonrails-security/x9DixQDG9a0'}, {'type': 'WEB', 'url': 'https://groups.google.com/g/rubyonrails-security/c/x9DixQDG9a0'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2020/dsa-4766'}]

{'cwe_ids': ['CWE-352'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-07T15:51:37Z', 'nvd_published_at': '2020-06-19T18:15:00Z'}

1.4.0

GHSA-ff7x-qrg7-qggm

2022-08-11T14:58:19Z

2020-07-29T20:56:59Z

['CVE-2020-8116']

dot-prop Prototype Pollution vulnerability

Prototype pollution vulnerability in dot-prop npm package versions before 4.2.1 and versions 5.x before 5.1.1 allows an attacker to add arbitrary properties to JavaScript language constructs such as objects.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L'}]

[{'package': {'ecosystem': 'npm', 'name': 'dot-prop'}, 'ecosystem_specific': {'affected_functions': ['dot-prop.set']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.2.1'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'dot-prop'}, 'ecosystem_specific': {'affected_functions': ['dot-prop.set']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '5.0.0'}, {'fixed': '5.1.1'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-8116'}, {'type': 'WEB', 'url': 'https://github.com/sindresorhus/dot-prop/issues/63'}, {'type': 'WEB', 'url': 'https://github.com/sindresorhus/dot-prop/commit/3039c8c07f6fdaa8b595ec869ae0895686a7a0f2'}, {'type': 'WEB', 'url': 'https://github.com/sindresorhus/dot-prop/commit/c914124f418f55edea27928e89c94d931babe587'}, {'type': 'WEB', 'url': 'https://hackerone.com/reports/719856'}, {'type': 'ADVISORY', 'url': 'https://github.com/advisories/GHSA-ff7x-qrg7-qggm'}, {'type': 'PACKAGE', 'url': 'https://github.com/sindresorhus/dot-prop'}, {'type': 'WEB', 'url': 'https://github.com/sindresorhus/dot-prop/tree/v4'}]

{'cwe_ids': ['CWE-1321', 'CWE-425', 'CWE-471'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-29T20:51:37Z', 'nvd_published_at': '2020-02-04T20:15:00Z'}

1.4.0

GHSA-976r-qfjj-c24w

2021-09-22T21:16:56Z

2020-07-27T16:57:33Z

['CVE-2020-11981']

Command injection via Celery broker in Apache Airflow

An issue was found in Apache Airflow versions 1.10.10 and below. When using CeleryExecutor, if an attacker can connect to the broker (Redis, RabbitMQ) directly, it is possible to inject commands, resulting in the celery worker running arbitrary commands.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'PyPI', 'name': 'apache-airflow'}, 'ecosystem_specific': {'affected_functions': ['airflow.www_rbac.views.Airflow.index']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.10.11'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-11981'}, {'type': 'WEB', 'url': 'https://github.com/apache/airflow/commit/afa4b11fddfdbadb048f742cf66d5c21c675a5c8'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r7255cf0be3566f23a768e2a04b40fb09e52fcd1872695428ba9afe91%40%3Cusers.airflow.apache.org%3E'}, {'type': 'WEB', 'url': 'https://web.archive.org/web/20220427031325/https://issues.apache.org/jira/browse/AIRFLOW-6351'}]

{'cwe_ids': ['CWE-78'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2020-07-27T16:55:01Z', 'nvd_published_at': None}

1.4.0

GHSA-34gh-3cwv-wvp2

2021-09-23T17:29:15Z

2020-07-29T18:07:11Z

['CVE-2020-7683']

Directory traversal in rollup-plugin-server

This affects all versions of package rollup-plugin-server. There is no path sanitization in readFile operation performed inside the readFileFromContentBase function.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}]

[{'package': {'ecosystem': 'npm', 'name': 'rollup-plugin-server'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.7.0'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-7683'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JS-ROLLUPPLUGINSERVER-590123'}]

{'cwe_ids': ['CWE-22'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-29T17:45:50Z', 'nvd_published_at': None}

1.4.0

GHSA-fpqv-x9hm-35j9

2021-09-23T18:13:50Z

2020-07-31T17:39:22Z

['CVE-2020-16095']

Potential XSS vulnerability in Kitodo.Presentation

### Impact Kitodo.Presentation fails to properly encode URL parameters for output in HTML making it vulnerable to Cross Site Scripting (XSS). Only sites using the `ListView`, `Navigation` or `PageView` plugins are affected. It also includes jQuery 3.4.1 which is known to be vulnerable against Cross Site Scripting, although there is currently no known way to exploit this in Kitodo.Presentation. ### Patches An updated version of Kitodo.Presentation is available on [GitHub](https://github.com/kitodo/kitodo-presentation/releases/tag/v3.1.2), [Packagist](https://packagist.org/packages/kitodo/presentation#v3.1.2) and in the [TYPO3 Extension Repository](https://extensions.typo3.org/extension/dlf/). Users are advised to update as soon as possible. The issue was also fixed in release 2.3.1 of the 2.x branch, although it is generally not recommended to run this branch since it depends on an outdated TYPO3 version. ### References TYPO3 Security Advisory [TYPO3-EXT-SA-2020-015](https://typo3.org/security/advisory/typo3-ext-sa-2020-015) jQuery Security Advisory [GHSA-gxr4-xjj5-5px2](https://github.com/jquery/jquery/security/advisories/GHSA-gxr4-xjj5-5px2) Open Bug Bounty Report [OBB-1219978](https://www.openbugbounty.org/reports/1219978/) ### Contact If you have any questions or comments about this advisory: * [Open an issue](https://github.com/kitodo/kitodo-presentation/issues/new/choose) * Email us at [security@kitodo.org](mailto:security@kitodo.org)

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N'}]

[{'package': {'ecosystem': 'Packagist', 'name': 'kitodo/presentation'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.1.2'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/kitodo/kitodo-presentation/security/advisories/GHSA-fpqv-x9hm-35j9'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-16095'}, {'type': 'WEB', 'url': 'https://github.com/kitodo/kitodo-presentation/commit/6a67256388350cc69efa7f36bbaee50c919ca23c'}, {'type': 'PACKAGE', 'url': 'https://github.com/kitodo/kitodo-presentation'}, {'type': 'WEB', 'url': 'https://typo3.org/help/security-advisories'}, {'type': 'WEB', 'url': 'https://typo3.org/security/advisory/typo3-ext-sa-2020-015'}]

{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-30T15:07:04Z', 'nvd_published_at': None}

1.4.0

GHSA-xp63-6vf5-xf3v

2021-01-07T23:47:13Z

2020-07-20T17:20:20Z

['CVE-2020-15123']

Command injection in codecov (npm package)

### Impact The `upload` method has a command injection vulnerability. Clients of the `codecov-node` library are unlikely to be aware of this, so they might unwittingly write code that contains a vulnerability. A similar CVE was issued: [CVE-2020-7597](https://github.com/advisories/GHSA-5q88-cjfq-g2mh), but the fix was incomplete. It only blocked `&`, and command injection is still possible using backticks instead to bypass the sanitizer. We have written a [CodeQL](https://codeql.com) query, which automatically detects this vulnerability. You can see the results of the query on the `codecov-node` project [here](https://lgtm.com/query/7714424068617023832/). ### Patches This has been patched in version 3.7.1 ### Workarounds None, however, the attack surface is low in this case. Particularly in the standard use of codecov, where the module is used directly in a build pipeline, not built against as a library in another application that may supply malicious input and perform command injection. ### References * [CVE-2020-7597](https://github.com/advisories/GHSA-5q88-cjfq-g2mh) ### For more information If you have any questions or comments about this advisory: * Contact us via our [Security Email](mailto:security@codecov.io)

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N'}]

[{'package': {'ecosystem': 'npm', 'name': 'codecov'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.7.1'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/codecov/codecov-node/security/advisories/GHSA-xp63-6vf5-xf3v'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15123'}, {'type': 'WEB', 'url': 'https://github.com/codecov/codecov-node/pull/180'}, {'type': 'WEB', 'url': 'https://github.com/codecov/codecov-node/commit/c0711c656686e902af2cd92d6aecc8074de4d83d'}, {'type': 'ADVISORY', 'url': 'https://github.com/advisories/GHSA-5q88-cjfq-g2mh'}, {'type': 'WEB', 'url': 'https://lgtm.com/query/7714424068617023832'}]

{'cwe_ids': ['CWE-78'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-20T17:19:56Z', 'nvd_published_at': None}

1.4.0

GHSA-gprm-xqrc-c2j3

2021-09-22T21:56:35Z

2020-07-27T22:51:44Z

['CVE-2020-1956']

Command Injection in Kylin

Kylin has some restful apis which will concatenate os command with the user input string, a user is likely to be able to execute any os command without any protection or validation.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'Maven', 'name': 'org.apache.kylin:kylin-core-common'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.6.6'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.apache.kylin:kylin-core-common'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.0.0'}, {'fixed': '3.0.2'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-1956'}, {'type': 'WEB', 'url': 'https://github.com/apache/kylin/commit/58fad56ac6aaa43c6bd8f962d7f2d84438664092'}, {'type': 'WEB', 'url': 'https://community.sonarsource.com/t/apache-kylin-3-0-1-command-injection-vulnerability/25706'}, {'type': 'PACKAGE', 'url': 'https://github.com/apache/kylin'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r021baf9d8d4ae41e8c8332c167c4fa96c91b5086563d9be55d2d7acf@%3Ccommits.kylin.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r1332ef34cf8e2c0589cf44ad269fb1fb4c06addec6297f0320f5111d%40%3Cuser.kylin.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r250a867961cfd6e0506240a9c7eaee782d84c6ab0091c7c4bc45f3eb@%3Cannounce.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r250a867961cfd6e0506240a9c7eaee782d84c6ab0091c7c4bc45f3eb@%3Cdev.kylin.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r250a867961cfd6e0506240a9c7eaee782d84c6ab0091c7c4bc45f3eb@%3Cuser.kylin.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r61666760d8a4e8764b2d5fe158d8a48b569414480fbfadede574cdc0@%3Ccommits.kylin.apache.org%3E'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEKYLIN-570207'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2020/07/14/1'}]

{'cwe_ids': ['CWE-78'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-27T22:50:23Z', 'nvd_published_at': None}

1.4.0

GHSA-9h4g-27m8-qjrg

2021-09-22T20:28:29Z

2020-07-07T19:24:47Z

['CVE-2020-15779']

Path Traversal in socket.io-file

All versions of `socket.io-file` are vulnerable to Path Traversal. The package fails to sanitize user input and uses it to generate the file upload paths. The `socket.io-file::createFile` message contains a `name` option that is passed directly to `path.join()`. It is possible to upload files to arbitrary folders on the server by sending relative paths on the `name` value, such as `../../test.js`. The `uploadDir` and `rename` options can be used to define the file upload path.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}]

[{'package': {'ecosystem': 'npm', 'name': 'socket.io-file'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '2.0.31'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15779'}, {'type': 'ADVISORY', 'url': 'https://github.com/advisories/GHSA-9h4g-27m8-qjrg'}, {'type': 'PACKAGE', 'url': 'https://github.com/rico345100/socket.io-file'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/advisories/1519'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/package/socket.io-file'}]

{'cwe_ids': ['CWE-22'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-07T19:23:52Z', 'nvd_published_at': None}

1.4.0

GHSA-jcq3-cprp-m333

2021-09-22T18:47:45Z

2020-07-01T17:12:20Z

['CVE-2019-2692']

Privilege escalation in mysql-connector-jav

Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 8.0.15 and prior. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Connectors executes to compromise MySQL Connectors. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.0 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).

[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'Maven', 'name': 'mysql:mysql-connector-java'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '8.0.16'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-2692'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20190423-0002/'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JAVA-MYSQL-174574'}, {'type': 'WEB', 'url': 'http://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html'}, {'type': 'WEB', 'url': 'http://www.securityfocus.com/bid/107925'}]

{'cwe_ids': ['CWE-843'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-01T17:11:19Z', 'nvd_published_at': None}

1.4.0

GHSA-3q49-h8f9-9fr9

2023-05-16T16:03:45Z

2020-07-31T17:39:42Z

['CVE-2020-15134']

Missing TLS certificate verification

Faye uses [em-http-request][6] and [faye-websocket][10] in the Ruby version of its client. Those libraries both use the [`EM::Connection#start_tls`][1] method in [EventMachine][2] to implement the TLS handshake whenever a `wss:` URL is used for the connection. This method does not implement certificate verification by default, meaning that it does not check that the server presents a valid and trusted TLS certificate for the expected hostname. That means that any `https:` or `wss:` connection made using these libraries is vulnerable to a man-in-the-middle attack, since it does not confirm the identity of the server it is connected to. The first request a Faye client makes is always sent via normal HTTP, but later messages may be sent via WebSocket. Therefore it is vulnerable to the same problem that these underlying libraries are, and we needed both libraries to support TLS verification before Faye could claim to do the same. Your client would still be insecure if its initial HTTPS request was verified, but later WebSocket connections were not. This has been a requested feature in EventMachine for many years now; see for example [#275][3], [#378][4], and [#814][5]. In June 2020, em-http-request published an [advisory][7] related to this problem and fixed it by [implementing TLS verification][8] in their own codebase; although EventMachine does not implement certificate verification itself, it provides an extension point for the caller to implement it, called [`ssl_verify_peer`][9]. Based on this implementation, we have incorporated similar functionality into faye-websocket. After implementing verification in v1.1.6, em-http-request has elected to leave the `:verify_peer` option switched off by default. We have decided to _enable_ this option by default in Faye, but are publishing a minor release with added functionality for configuring it. We are mindful of the fact that this may break existing programs, but we consider it much more important that all clients have TLS verification turned on by default. A client that is not carrying out verification is either: - talking to the expected server, and will not break under this change - being attacked, and would benefit from being alerted to this fact - deliberately talking to a server that would be rejected by verification The latter case includes situations like talking to a non-public server using a self-signed certificate. We consider this use case to be "working by accident", rather than functionality that was actively supported, and it should be properly and explicitly supported instead. We are releasing Faye v1.4.0, which enables verification by default and provides a way to opt out of it: ```rb client = Faye::Client.new('https://example.com/', tls: { verify_peer: false }) ``` Unfortunately we can't offer an equivalent of the `:root_cert_file` option that has been added to faye-websocket, because em-http-request does not support it. If you need to talk to servers whose certificates are not recognised by your default root certificates, then you need to add its certificate (or another one that can verify it) to your system's root set. The same functionality is now supported in the Node.js version, with a `tls` option whose values will be passed to the `https` and `tls` modules as appropriate when making connections. For example, you can provide your own CA certificate: ```js var client = new faye.Client('https://example.com/', { tls: { ca: fs.readFileSync('path/to/certificate.pem') } }); ``` For further background information on this issue, please see [faye#524][12] and [faye-websocket#129][13]. We would like to thank [Tero Marttila][14] and [Daniel Morsing][15] for providing invaluable assistance and feedback on this issue. [1]: https://www.rubydoc.info/github/eventmachine/eventmachine/EventMachine/Connection:start_tls [2]: https://rubygems.org/gems/eventmachine [3]: https://github.com/eventmachine/eventmachine/issues/275 [4]: https://github.com/eventmachine/eventmachine/pull/378 [5]: https://github.com/eventmachine/eventmachine/issues/814 [6]: https://rubygems.org/gems/em-http-request [7]: https://securitylab.github.com/advisories/GHSL-2020-094-igrigorik-em-http-request [8]: https://github.com/igrigorik/em-http-request/pull/340 [9]: https://www.rubydoc.info/github/eventmachine/eventmachine/EventMachine/Connection:ssl_verify_peer [10]: https://rubygems.org/gems/faye-websocket [11]: https://faye.jcoglan.com/ [12]: https://github.com/faye/faye/issues/524 [13]: https://github.com/faye/faye-websocket-ruby/pull/129 [14]: https://github.com/SpComb [15]: https://github.com/DanielMorsing

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N'}]

[{'package': {'ecosystem': 'RubyGems', 'name': 'faye'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.4.0'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/faye/faye/security/advisories/GHSA-3q49-h8f9-9fr9'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15134'}, {'type': 'WEB', 'url': 'https://github.com/eventmachine/eventmachine/issues/275'}, {'type': 'WEB', 'url': 'https://github.com/eventmachine/eventmachine/issues/814'}, {'type': 'WEB', 'url': 'https://github.com/faye/faye/issues/524'}, {'type': 'WEB', 'url': 'https://github.com/eventmachine/eventmachine/pull/378'}, {'type': 'WEB', 'url': 'https://github.com/faye/faye-websocket-ruby/pull/129'}, {'type': 'WEB', 'url': 'https://github.com/igrigorik/em-http-request/pull/340'}, {'type': 'WEB', 'url': 'https://blog.jcoglan.com/2020/07/31/missing-tls-verification-in-faye/'}, {'type': 'PACKAGE', 'url': 'https://github.com/faye/faye'}, {'type': 'WEB', 'url': 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/faye/CVE-2020-15134.yml'}, {'type': 'ADVISORY', 'url': 'https://securitylab.github.com/advisories/GHSL-2020-094-igrigorik-em-http-request'}, {'type': 'WEB', 'url': 'https://www.rubydoc.info/github/eventmachine/eventmachine/EventMachine/Connection:ssl_verify_peer'}, {'type': 'WEB', 'url': 'https://www.rubydoc.info/github/eventmachine/eventmachine/EventMachine/Connection:start_tls'}]

{'cwe_ids': ['CWE-295'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-31T17:38:46Z', 'nvd_published_at': None}

1.4.0

GHSA-2jpm-827p-j44g

2021-01-07T23:47:19Z

2020-07-09T18:28:07Z

['CVE-2020-15092']

Stored XSS in TimelineJS3

### Impact TimelineJS renders some user data as HTML. An attacker could implement an XSS exploit with maliciously crafted content in a number of data fields. This risk is present whether the source data for the timeline is stored on Google Sheets or in a JSON configuration file. Most TimelineJS users configure their timeline with a Google Sheets document. Those users are exposed to this vulnerability if they grant write access to the document to a malicious inside attacker, if the access of a trusted user is compromised, or if they grant public write access to the document. Some TimelineJS users configure their timeline with a JSON document. Those users are exposed to this vulnerability if they grant write access to the document to a malicious inside attacker, if the access of a trusted user is compromised, or if write access to the system hosting that document is otherwise compromised. Although the vulnerability has a [CVSS v3.1 base score of 7.2](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), this vulnerability has a severity of Moderate due to the likeliness of exploitation. ### Patches Version 3.7.0 of TimelineJS addresses this in two ways. 1. For content which is intended to support limited HTML markup for styling and linking, that content is "sanitized" before being added to the DOM. 1. For content intended for simple text display, all markup is stripped. Very few users of TimelineJS actually install the TimelineJS code on their server. Most users publish a timeline using a URL hosted on systems we control. The fix for this issue is published to our system such that **those users will automatically begin using the new code**. The only exception would be users who have deliberately edited the embed URL to "pin" their timeline to an earlier version of the code. Some users of TimelineJS use it as a part of a [wordpress plugin](https://wordpress.org/plugins/knight-lab-timelinejs/). Version 3.7.0.0 of that plugin and newer integrate the updated code. Users are encouraged to update the plugin rather than manually update the embedded version of TimelineJS. ### Workarounds To exploit this vulnerability, the attacker must have write access to the data source for the Timeline or the server which embeds the timeline. Thus, the only workaround is appropriate attention to securing write access to the Google Sheet or JSON file which serves as the data source. ### References For more about the release of TimelineJS which addresses this vulnerability, see the [Knight Lab website](https://knightlab.northwestern.edu/2020/07/09/timelinejs-update/index.html). A technical write-up of this vulnerability is available [here](https://zanderwork.com/blog/cve-2020-15092/). ### Acknowledgements This vulnerability was discovered by Zander Work ([@captainGeech42](https://twitter.com/captainGeech42)) of Oregon State University. ### For more information If you have any questions or comments about this advisory: * Open an issue in [GitHub](https://github.com/NUKnightLab/TimelineJS3/issues) * File a support request in our [helpdesk system](https://knightlab.zendesk.com/hc/en-us/requests/new)

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'npm', 'name': '@knight-lab/timelinejs'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.7.0'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/NUKnightLab/TimelineJS3/security/advisories/GHSA-2jpm-827p-j44g'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15092'}, {'type': 'WEB', 'url': 'https://knightlab.northwestern.edu/2020/07/09/timelinejs-update/index.html'}, {'type': 'WEB', 'url': 'https://knightlab.northwestern.edu/posts/'}]

{'cwe_ids': ['CWE-79'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-09T18:27:39Z', 'nvd_published_at': None}

1.4.0

GHSA-mm44-wc5p-wqhq

2022-01-18T23:05:18Z

2020-07-07T16:45:24Z

[]

Denial of service due to reference expansion in versions earlier than 4.0

### Impact The CBOR library supports optional tags that enable CBOR objects to contain references to objects within them. Versions earlier than 4.0 resolved those references automatically. While this by itself doesn't cause much of a security problem, a denial of service can happen if those references are deeply nested and used multiple times (so that the same reference to the same object occurs multiple times), and if the decoded CBOR object is sent to a serialization method such as EncodeToBytes, ToString, or ToJSONString, since the objects referred to are expanded in the process and take up orders of magnitude more memory than if the references weren't resolved. The impact of this problem on any particular system varies. In general, the risk is higher if the system allows users to send arbitrary CBOR objects without authentication, or exposes a remote endpoint in which arbitrary CBOR objects can be sent without authentication. ### Patches This problem is addressed in version 4.0 by disabling reference resolution by default. Users should use the latest version of this library. ### Workarounds Since version 3.6, an encoding option (`resolvereferences=true` or `resolvereferences=false`) in CBOREncodeOptions sets whether the CBOR processor will resolve these kinds of references when decoding a CBOR object. Set `resolvereferences=false` to disable reference resolution. In version 3.6, if the method used CBORObject.Read() or CBORObject.DecodeFromBytes() to decode a serialized CBOR object, call the overload that takes CBOREncodeOptions as follows: CBORObject.DecodeFromBytes(bytes, new CBOREncodeOptions("resolvereferences=false")); In versions 3.5 and earlier, this issue is present only if the CBOR object is an array or a map. If the application does not expect a decoded CBOR object to be an array or a map, it should check the CBOR object's type before encoding that object, as follows: if (cbor.Type != CBORType.Array && cbor.Type != CBORType.Map) { cbor.EncodeToBytes(); } Alternatively, for such versions, the application can use WriteTo to decode the CBOR object to a so-called "limited memory stream", that is, a Stream that throws an exception if too many bytes would be written. How to write such a limited-memory stream is nontrivial and beyond the scope of this advisory. LimitedMemoryStream stream = new LimitedMemoryStream(100000); // Limit to 100000 bytes cbor.WriteTo(stream); return stream.ToBytes(); To check whether a byte array representing a CBOR object might exhibit this problem, check whether the array contains the byte 0xd8 followed immediately by either 0x19 or 0x1d. This check catches all affected CBOR objects but may catch some non-affected CBOR objects (notably integers and byte strings). ### References See the Wikipedia article [Billion laughs attack](https://en.wikipedia.org/wiki/Billion_laughs_attack) and the related issue in [Kubernetes](https://github.com/kubernetes/kubernetes/issues/83253). ### For more information If you have any questions or comments about this advisory, open an issue in [the CBOR repository](https://github.com/peteroupc/cbor-java).

[]

[{'package': {'ecosystem': 'Maven', 'name': 'com.upokecenter:cbor'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.0.0'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/peteroupc/CBOR-Java/security/advisories/GHSA-mm44-wc5p-wqhq'}, {'type': 'PACKAGE', 'url': 'https://github.com/peteroupc/CBOR-Java'}]

{'cwe_ids': [], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-07T16:45:07Z', 'nvd_published_at': None}

1.4.0

GHSA-q4p3-qw5c-mhpc

2021-09-22T21:22:13Z

2020-07-27T16:57:25Z

['CVE-2020-11983']

Multiple stored XSS in RBAC Admin screens in Apache Airflow

An issue was found in Apache Airflow versions 1.10.10 and below. It was discovered that many of the admin management screens in the new/RBAC UI handled escaping incorrectly, allowing authenticated users with appropriate permissions to create stored XSS attacks.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N'}]

[{'package': {'ecosystem': 'PyPI', 'name': 'apache-airflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.10.11'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-11983'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r7255cf0be3566f23a768e2a04b40fb09e52fcd1872695428ba9afe91%40%3Cusers.airflow.apache.org%3E'}]

{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-27T16:55:16Z', 'nvd_published_at': None}

1.4.0

GHSA-4h44-w6fm-548g

2021-11-19T15:44:20Z

2020-07-29T16:15:12Z

['CVE-2020-15086']

Potential Remote Code Execution in TYPO3 with mediace extension

> ### Meta > * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (9.1) > * CWE-325, CWE-20, CWE-200, CWE-502 ### Problem It has been discovered that an internal verification mechanism can be used to generate arbitrary checksums. This allows to inject arbitrary data having a valid cryptographic message authentication code (HMAC-SHA1) and can lead to various attack chains as described below. * [TYPO3-CORE-SA-2020-007](https://typo3.org/security/advisory/typo3-core-sa-2020-007), [CVE-2020-15099](https://nvd.nist.gov/vuln/detail/CVE-2020-15099): Potential Privilege Escalation + the database server used for a TYPO3 installation must be accessible for an attacker (either via internet or shared hosting network) + `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (7.5, high) * [TYPO3-CORE-SA-2016-013](https://typo3.org/security/advisory/typo3-core-sa-2016-013), [CVE-2016-5091](https://nvd.nist.gov/vuln/detail/CVE-2016-5091): Insecure Deserialization & Remote Code Execution + an attacker must have access to at least one Extbase plugin or module action in a TYPO3 installation + `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (9.1, critical) The overall severity of this vulnerability is critical (9.1) based on mentioned attack chains and the fact it does not require any privileges. ### Solution In case the extension is not used and required at all, it is suggested to uninstall and remove it from the system completely. Otherwise, an updated version 7.6.5 is available from the TYPO3 extension manager, Packagist and the TYPO3 extension repository: * https://extensions.typo3.org/extension/download/mediace/7.6.5/zip/ * https://packagist.org/packages/friendsoftypo3/mediace#7.6.5 As a precautionary measure it is advised to change `encryptionKey` and database credentials in `typo3conf/LocalConfiguration.php`. ### Credits Thanks to TYPO3 security team member Oliver Hader who reported and fixed the issue. ### References * [TYPO3-EXT-SA-2020-014](https://typo3.org/security/advisory/typo3-ext-sa-2020-014)

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'Packagist', 'name': 'friendsoftypo3/mediace'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '7.6.2'}, {'fixed': '7.6.5'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/FriendsOfTYPO3/mediace/security/advisories/GHSA-4h44-w6fm-548g'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15086'}, {'type': 'WEB', 'url': 'https://github.com/FriendsOfTYPO3/mediace/pull/31'}, {'type': 'WEB', 'url': 'https://github.com/FriendsOfTYPO3/mediace/commit/fa29ffd3e8b275782a8600d2406e1b1e5e16ae75'}, {'type': 'PACKAGE', 'url': 'https://github.com/FriendsOfTYPO3/mediace'}]

{'cwe_ids': ['CWE-20', 'CWE-200', 'CWE-325', 'CWE-502'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-29T16:09:56Z', 'nvd_published_at': '2020-07-29T17:15:00Z'}

1.4.0

GHSA-93f3-23rq-pjfp

2022-08-10T23:59:40Z

2020-07-07T18:56:16Z

['CVE-2020-15095']

npm CLI exposing sensitive information through logs

Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N'}]

[{'package': {'ecosystem': 'npm', 'name': 'npm'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.14.6'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/npm/cli/security/advisories/GHSA-93f3-23rq-pjfp'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15095'}, {'type': 'WEB', 'url': 'https://github.com/npm/cli/commit/a9857b8f6869451ff058789c4631fadfde5bbcbc'}, {'type': 'WEB', 'url': 'https://github.com/npm/cli/blob/66aab417f836a901f8afb265251f761bb0422463/CHANGELOG.md#6146-2020-07-07'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4OOYAMJVLLCLXDTHW3V5UXNULZBBK4O6/'}, {'type': 'WEB', 'url': 'https://security.gentoo.org/glsa/202101-07'}, {'type': 'WEB', 'url': 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00011.html'}, {'type': 'WEB', 'url': 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00015.html'}, {'type': 'WEB', 'url': 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00023.html'}]

{'cwe_ids': ['CWE-532'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-07T18:30:59Z', 'nvd_published_at': '2020-07-07T19:15:00Z'}

1.4.0

GHSA-m93v-9qjc-3g79

2021-01-07T23:48:11Z

2020-07-07T00:01:07Z

['CVE-2020-4076']

Context isolation bypass via leaked cross-context objects in Electron

### Impact Apps using `contextIsolation` are affected. This is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions. ### Workarounds There are no app-side workarounds, you must update your Electron version to be protected. ### Fixed Versions * `9.0.0-beta.21` * `8.2.4` * `7.2.4` ### Non-Impacted Versions * `9.0.0-beta.*` ### For more information If you have any questions or comments about this advisory: * Email us at [security@electronjs.org](mailto:security@electronjs.org)

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N'}]

[{'package': {'ecosystem': 'npm', 'name': 'electron'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '7.2.4'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'electron'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '8.0.0'}, {'fixed': '8.2.4'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/electron/electron/security/advisories/GHSA-m93v-9qjc-3g79'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-4076'}, {'type': 'WEB', 'url': 'https://www.electronjs.org/releases/stable?page=3#release-notes-for-v824'}]

{'cwe_ids': ['CWE-501'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-06T23:55:29Z', 'nvd_published_at': None}

1.4.0

GHSA-43fq-w8qq-v88h

2023-02-28T15:12:44Z

2020-07-27T21:52:36Z

['CVE-2020-11538']

Out-of-bounds read in Pillow

In libImaging/SgiRleDecode.c in Pillow through 7.0.0, a number of out-of-bounds reads exist in the parsing of SGI image files, a different issue than CVE-2020-5311.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'PyPI', 'name': 'Pillow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '7.1.0'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-11538'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/pull/4504'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/pull/4538'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/commit/2ef59fdbaeb756bc512ab3f2ad15ac45665b303d'}, {'type': 'PACKAGE', 'url': 'https://github.com/python-pillow/Pillow'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/blob/master/docs/releasenotes/7.1.0.rst#security'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BEBCPE4F2VHTIT6EZA2YZQZLPVDEBJGD/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HOKHNWV2VS5GESY7IBD237E7C6T3I427/'}, {'type': 'WEB', 'url': 'https://pillow.readthedocs.io/en/stable/releasenotes/7.1.0.html'}, {'type': 'WEB', 'url': 'https://pillow.readthedocs.io/en/stable/releasenotes/index.html'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-PYTHON-PILLOW-574574'}, {'type': 'WEB', 'url': 'https://usn.ubuntu.com/4430-1/'}, {'type': 'WEB', 'url': 'https://usn.ubuntu.com/4430-2/'}]

{'cwe_ids': ['CWE-125'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-27T21:35:11Z', 'nvd_published_at': '2020-06-25T19:15:00Z'}

1.4.0

GHSA-w534-q4xf-h5v2

2021-01-07T23:47:26Z

2020-07-07T16:32:49Z

['CVE-2020-15231']

XSS in Mapfish Print relating to JSONP support

### Impact A user can use the JSONP support to do a Cross-site scripting. ### Patches Use version >= 3.24 ### Workarounds No ### References * https://github.com/mapfish/mapfish-print/pull/1397/commits/89155f2506b9cee822e15ce60ccae390a1419d5e * https://cwe.mitre.org/data/definitions/79.html ### For more information If you have any questions or comments about this advisory Comment the pull request: https://github.com/mapfish/mapfish-print/pull/1397

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N'}]

[{'package': {'ecosystem': 'Maven', 'name': 'org.mapfish.print:print-lib'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.24'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.mapfish.print:print-servlet'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.24'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.mapfish.print:print-standalone'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.24'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/mapfish/mapfish-print/security/advisories/GHSA-w534-q4xf-h5v2'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15231'}, {'type': 'WEB', 'url': 'https://github.com/mapfish/mapfish-print/pull/1397/commits/89155f2506b9cee822e15ce60ccae390a1419d5e'}]

{'cwe_ids': ['CWE-79'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2020-07-07T16:31:25Z', 'nvd_published_at': None}

1.4.0

GHSA-43jj-2rwc-2m3f

2021-09-22T21:03:46Z

2020-07-15T17:38:04Z

['CVE-2019-14273']

Broken access control on files

In SilverStripe assets 4.0, there is broken access control on files.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N'}]

[{'package': {'ecosystem': 'Packagist', 'name': 'silverstripe/framework'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.0.0'}, {'fixed': '4.3.5'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'silverstripe/framework'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.4.0'}, {'fixed': '4.4.4'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-14273'}, {'type': 'WEB', 'url': 'https://forum.silverstripe.org/c/releases'}, {'type': 'PACKAGE', 'url': 'https://github.com/FriendsOfPHP/security-advisories'}, {'type': 'WEB', 'url': 'https://github.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/CVE-2019-14273.yaml'}, {'type': 'WEB', 'url': 'https://www.silverstripe.org/blog/tag/release'}, {'type': 'WEB', 'url': 'https://www.silverstripe.org/download/security-releases/'}, {'type': 'WEB', 'url': 'https://www.silverstripe.org/download/security-releases/CVE-2019-14273'}]

{'cwe_ids': ['CWE-552'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-15T17:33:55Z', 'nvd_published_at': None}

1.4.0

GHSA-jphg-qwrw-7w9g

2023-01-25T22:49:03Z

2020-07-27T18:08:21Z

['CVE-2020-10663']

Unsafe object creation in json RubyGem

The JSON gem through 2.2.0 for Ruby, as used in Ruby 2.4 through 2.4.9, 2.5 through 2.5.7, and 2.6 through 2.6.5, has an Unsafe Object Creation Vulnerability. This is quite similar to CVE-2013-0269/GHSA-x457-cw4h-hq5f, but does not rely on poor garbage-collection behavior within Ruby. Specifically, use of JSON parsing methods can lead to creation of a malicious object within the interpreter, with adverse effects that are application-dependent.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}]

[{'package': {'ecosystem': 'RubyGems', 'name': 'json'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.0'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-10663'}, {'type': 'PACKAGE', 'url': 'https://github.com/flori/json'}, {'type': 'WEB', 'url': 'https://github.com/flori/json/blob/master/CHANGES.md#2019-12-11-230'}, {'type': 'WEB', 'url': 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/json/CVE-2020-10663.yml'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r37c0e1807da7ff2bdd028bbe296465a6bbb99e2320dbe661d5d8b33b@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r3b04f4e99a19613f88ae088aa18cd271231a3c79dfff8f5efa8cda61@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r5f17bfca1d6e7f4b33ae978725b2fd62a9f1b3111696eafa9add802d@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r8d2e174230f6d26e16c007546e804c343f1f68956f526daaafa4aaae@%3Cdev.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rb023d54a46da1ac0d8969097f5fecc79636b07d3b80db7b818a5c55c@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rb2b981912446a74e14fe6076c4b7c7d8502727ea0718e6a65a9b1be5@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rd9b9cc843f5cf5b532bdad9e87a817967efcf52b917e8c43b6df4cc7@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rec8bb4d637b04575da41cfae49118e108e95d43bfac39b7b698ee4db@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/ree3abcd33c06ee95ab59faa1751198a1186d8941ddc2c2562c12966c@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2020/04/msg00030.html'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7QL6MJD2BO4IRJ5CJFNMCDYMQQFT24BJ/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/F4TNVTT66VPRMX5UZYSDGSVRXKKDDDU5/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NK2PBXWMFRUD7U7Q7LHV4KYLYID77RI4/'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20210129-0003/'}, {'type': 'WEB', 'url': 'https://support.apple.com/kb/HT211931'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2020/dsa-4721'}, {'type': 'WEB', 'url': 'https://www.ruby-lang.org/en/news/2020/03/19/json-dos-cve-2020-10663/'}, {'type': 'WEB', 'url': 'http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00004.html'}, {'type': 'WEB', 'url': 'http://seclists.org/fulldisclosure/2020/Dec/32'}]

{'cwe_ids': ['CWE-20'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-27T18:07:46Z', 'nvd_published_at': '2020-04-28T21:15:00Z'}

1.4.0

GHSA-7xcx-6wjh-7xp2

2021-09-22T21:03:04Z

2020-07-13T21:34:59Z

[]

Command Injection in standard-version

# GitHub Security Lab (GHSL) Vulnerability Report: `GHSL-2020-111` The [GitHub Security Lab](https://securitylab.github.com) team has identified a potential security vulnerability in [standard-version](https://github.com/conventional-changelog/standard-version). ## Summary The `standardVersion` function has a command injection vulnerability. Clients of the `standard-version` library are unlikely to be aware of this, so they might unwittingly write code that contains a vulnerability. ## Product Standard Version ## Tested Version Commit [2f04ac8](https://github.com/conventional-changelog/standard-version/tree/2f04ac8fc1c134a1981c23a093d4eece77d0bbb9/) ## Details ### Issue 1: Command injection in `standardVersion` The following proof-of-concept illustrates the vulnerability. First install Standard Version and create an empty git repo to run the PoC in: ``` npm install standard-version git init echo "foo" > foo.txt # the git repo has to be non-empty git add foo.txt git commit -am "initial commit" ``` Now create a file with the following contents: ``` var fs = require("fs"); // setting up a bit of environment fs.writeFileSync("package.json", '{"name": "foo", "version": "1.0.0"}'); const standardVersion = require('standard-version') standardVersion({ noVerify: true, infile: 'foo.txt', releaseCommitMessageFormat: "bla `touch exploit`" }) ``` and run it: ``` node test.js ``` Notice that a file named `exploit` has been created. This vulnerability is similar to command injection vulnerabilities that have been found in other Javascript libraries. Here are some examples: [CVE-2020-7646](https://github.com/advisories/GHSA-m8xj-5v73-3hh8), [CVE-2020-7614](https://github.com/advisories/GHSA-426h-24vj-qwxf), [CVE-2020-7597](https://github.com/advisories/GHSA-5q88-cjfq-g2mh), [CVE-2019-10778](https://github.com/advisories/GHSA-4gp3-p7ph-x2jr), [CVE-2019-10776](https://github.com/advisories/GHSA-84cm-v6jp-gjmr), [CVE-2018-16462](https://github.com/advisories/GHSA-9jm3-5835-537m), [CVE-2018-16461](https://github.com/advisories/GHSA-7g2w-6r25-2j7p), [CVE-2018-16460](https://github.com/advisories/GHSA-cfhg-9x44-78h2), [CVE-2018-13797](https://github.com/advisories/GHSA-pp57-mqmh-44h7), [CVE-2018-3786](https://github.com/advisories/GHSA-c9j3-wqph-5xx9), [CVE-2018-3772](https://github.com/advisories/GHSA-wjr4-2jgw-hmv8), [CVE-2018-3746](https://github.com/advisories/GHSA-3pxp-6963-46r9), [CVE-2017-16100](https://github.com/advisories/GHSA-jcw8-r9xm-32c6), [CVE-2017-16042](https://github.com/advisories/GHSA-qh2h-chj9-jffq). We have written a [CodeQL](https://codeql.com) query, which automatically detects this vulnerability. You can see the results of the query on the `standard-version` project [here](https://lgtm.com/query/237522640229151035/). #### Impact This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input. #### Remediation We recommend not using an API that can interpret a string as a shell command. For example, use [`child_process.execFile`](https://nodejs.org/api/child_process.html#child_process_child_process_execfile_file_args_options_callback) instead of [`child_process.exec`](https://nodejs.org/api/child_process.html#child_process_child_process_exec_command_options_callback). ## Credit This issue was discovered and reported by GitHub Engineer [@erik-krogh (Erik Krogh Kristensen)](https://github.com/erik-krogh). ## Contact You can contact the GHSL team at `securitylab@github.com`, please include `GHSL-2020-111` in any communication regarding this issue. ## Disclosure Policy This report is subject to our [coordinated disclosure policy](https://securitylab.github.com/disclosures#policy).

[]

[{'package': {'ecosystem': 'npm', 'name': 'standard-version'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '8.0.1'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/conventional-changelog/standard-version/security/advisories/GHSA-7xcx-6wjh-7xp2'}, {'type': 'PACKAGE', 'url': 'https://github.com/conventional-changelog/standard-version'}, {'type': 'WEB', 'url': 'https://github.com/conventional-changelog/standard-version/tree/2f04ac8fc1c134a1981c23a093d4eece77d0bbb9'}]

{'cwe_ids': ['CWE-77'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-13T21:33:29Z', 'nvd_published_at': None}

1.4.0

GHSA-8m73-w2r2-6xxj

2023-03-03T00:01:57Z

2020-07-29T17:29:51Z

['CVE-2020-7685']

Insecure defaults in UmbracoForms

This affects all versions of package UmbracoForms. When using the default configuration for upload forms, it is possible to upload arbitrary file types. The package offers a way for users to mitigate the issue. The users of this package can create a custom workflow and frontend validation that blocks certain file types, depending on their security needs and policies.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}]

[{'package': {'ecosystem': 'NuGet', 'name': 'UmbracoForms'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '8.4.1'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-7685'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-DOTNET-UMBRACOFORMS-595765'}]

{'cwe_ids': ['CWE-1188'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-29T17:28:16Z', 'nvd_published_at': '2020-07-28T17:15:00Z'}

1.4.0

GHSA-v7m9-9497-p9gr

2021-11-19T15:44:01Z

2020-07-22T23:07:16Z

['CVE-2020-15110']

Possible pod name collisions in jupyterhub-kubespawner

### Impact _What kind of vulnerability is it? Who is impacted?_ JupyterHub deployments using: - KubeSpawner <= 0.11.1 (e.g. zero-to-jupyterhub 0.9.0) and - enabled named_servers (not default), and - an Authenticator that allows: - usernames with hyphens or other characters that require escape (e.g. `user-hyphen` or `user@email`), and - usernames which may match other usernames up to but not including the escaped character (e.g. `user` in the above cases) In this circumstance, certain usernames will be able to craft particular server names which will grant them access to the default server of other users who have matching usernames. ### Patches _Has the problem been patched? What versions should users upgrade to?_ Patch will be released in kubespawner 0.12 and zero-to-jupyterhub 0.9.1 ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ #### KubeSpawner Specify configuration: for KubeSpawner ```python from traitlets import default from kubespawner import KubeSpawner class PatchedKubeSpawner(KubeSpawner): @default("pod_name_template") def _default_pod_name_template(self): if self.name: return "jupyter-{username}-{servername}" else: return "jupyter-{username}" @default("pvc_name_template") def _default_pvc_name_template(self): if self.name: return "claim-{username}-{servername}" else: return "claim-{username}" c.JupyterHub.spawner_class = PatchedKubeSpawner ``` **Note for KubeSpawner:** this configuration will behave differently before and after the upgrade, so will need to be removed when upgrading. Only apply this configuration while still using KubeSpawner ≤ 0.11.1 and remove it after upgrade to ensure consistent pod and pvc naming. Changing the name template means pvcs for named servers will have different names. This will result in orphaned PVCs for named servers across Hub upgrade! This may appear as data loss for users, depending on configuration, but the orphaned PVCs will still be around and data can be migrated manually (or new PVCs created manually to reference existing PVs) before deleting the old PVCs and/or PVs. ### 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 [kubespawner](https://github.com/jupyterhub/kubespawner) * Email us at [security@ipython.org](mailto:security@ipython.org) Credit: Jining Huang

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N'}]

[{'package': {'ecosystem': 'PyPI', 'name': 'jupyterhub-kubespawner'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.12'}]}], 'database_specific': {'last_known_affected_version_range': '<= 0.11.1'}}]

[{'type': 'WEB', 'url': 'https://github.com/jupyterhub/kubespawner/security/advisories/GHSA-v7m9-9497-p9gr'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15110'}, {'type': 'WEB', 'url': 'https://github.com/jupyterhub/kubespawner/commit/3dfe870a7f5e98e2e398b01996ca6b8eff4bb1d0'}, {'type': 'PACKAGE', 'url': 'https://github.com/jupyterhub/kubespawner'}]

{'cwe_ids': ['CWE-863'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-17T20:49:37Z', 'nvd_published_at': '2020-07-17T21:15:00Z'}

1.4.0

GHSA-7hmh-8gwv-mfvq

2021-09-22T21:57:07Z

2020-07-27T22:51:47Z

['CVE-2020-1937']

SQL Injection in Kylin

Kylin has some restful apis which will concatenate SQLs with the user input string, a user is likely to be able to run malicious database queries.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N'}]

[{'package': {'ecosystem': 'Maven', 'name': 'org.apache.kylin:kylin-server-base'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.6.5'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.apache.kylin:kylin-server-base'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.0.0'}, {'fixed': '3.0.1'}]}], 'versions': ['3.0.0']}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-1937'}, {'type': 'WEB', 'url': 'https://github.com/apache/kylin/commit/e373c64c96a54a7abfe4bccb82e8feb60db04749'}, {'type': 'PACKAGE', 'url': 'https://github.com/apache/kylin'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r021baf9d8d4ae41e8c8332c167c4fa96c91b5086563d9be55d2d7acf@%3Ccommits.kylin.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r61666760d8a4e8764b2d5fe158d8a48b569414480fbfadede574cdc0@%3Ccommits.kylin.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rc574fef23740522f62ab3bbda4f6171be98aa7a25f3f54be143a80a8%40%3Cuser.kylin.apache.org%3E'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEKYLIN-552148'}]

{'cwe_ids': ['CWE-89'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-27T22:50:42Z', 'nvd_published_at': '2020-02-24T21:15:00Z'}

1.4.0

GHSA-3pc2-fm7p-q2vg

2021-03-04T18:26:09Z

2020-07-02T16:55:11Z

['CVE-2020-4061']

Cross-site Scripting in October

### Impact Pasting content copied from malicious websites into the Froala richeditor could result in a successful self-XSS attack. ### Patches Issue has been patched in Build 467 (v1.0.467). ### Workarounds Apply https://github.com/octobercms/october/commit/b384954a29b89117e1c0d6035b3ede4f46df67c5 to your installation manually if unable to upgrade to Build 467. ### References - https://research.securitum.com/the-curious-case-of-copy-paste/ ### For more information If you have any questions or comments about this advisory: * Email us at [hello@octobercms.com](mailto:hello@octobercms.com) ### Threat Assessment Assessed as Low given that by the nature of the attack it can only impact users that do it to themselves by copying and pasting from malicious websites. ### Acknowledgements Thanks to [Michał Bentkowski of Securitum](https://research.securitum.com/authors/michal-bentkowski/) for finding the original issue in Froala and @tomaszstrojny for reporting the issue to the October CMS team.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N'}]

[{'package': {'ecosystem': 'Packagist', 'name': 'october/backend'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.0.319'}, {'fixed': '1.0.467'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/octobercms/october/security/advisories/GHSA-3pc2-fm7p-q2vg'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-4061'}, {'type': 'WEB', 'url': 'https://github.com/octobercms/october/commit/b384954a29b89117e1c0d6035b3ede4f46df67c5'}, {'type': 'WEB', 'url': 'https://research.securitum.com/the-curious-case-of-copy-paste/'}]

{'cwe_ids': ['CWE-79'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2020-07-02T16:54:50Z', 'nvd_published_at': None}

1.4.0

GHSA-3x94-fv5h-5q2c

2021-10-08T20:36:13Z

2020-07-29T16:15:32Z

['CVE-2020-15099']

Exposure of Sensitive Information to an Unauthorized Actor in TYPO3 CMS

> ### Meta > * CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (7.5) > * CWE-20, CWE-200 ### Problem In case an attacker manages to generate a valid cryptographic message authentication code (HMAC-SHA1) - either by using a different existing vulnerability or in case the internal _encryptionKey_ was exposed - it is possible to retrieve arbitrary files of a TYPO3 installation. This includes the possibility to fetch _typo3conf/LocalConfiguration.php_ which again contains the _encryptionKey_ as well as credentials of the database management system being used. In case a database server is directly accessible either via internet or in a shared hosting network, this allows to completely retrieve, manipulate or delete database contents. This includes creating an administration user account - which can be used to trigger remote code execution by injecting custom extensions. ### Solution Update to TYPO3 versions 9.5.20 or 10.4.6 that fix the problem described. ### Credits Thanks to TYPO3 security team member Oliver Hader who reported and fixed the issue. ### References * [TYPO3-CORE-SA-2020-007](https://typo3.org/security/advisory/typo3-core-sa-2020-007)

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'Packagist', 'name': 'typo3/cms-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '9.0.0'}, {'fixed': '9.5.20'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'typo3/cms-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '10.0.0'}, {'fixed': '10.4.6'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-3x94-fv5h-5q2c'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15099'}, {'type': 'PACKAGE', 'url': 'https://github.com/TYPO3/TYPO3.CMS'}, {'type': 'WEB', 'url': 'https://typo3.org/security/advisory/typo3-core-sa-2020-007'}]

{'cwe_ids': ['CWE-20', 'CWE-200'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-29T16:14:57Z', 'nvd_published_at': '2020-07-29T17:15:00Z'}

1.4.0

GHSA-rvmq-4x66-q7j3

2023-09-01T10:09:33Z

2020-07-27T16:57:33Z

['CVE-2020-11978']

Remote code execution in Apache Airflow

An issue was found in Apache Airflow versions 1.10.10 and below. A remote code/command injection vulnerability was discovered in one of the example DAGs shipped with Airflow which would allow any authenticated user to run arbitrary commands as the user running airflow worker/scheduler (depending on the executor in use). If you already have examples disabled by setting load_examples=False in the config then you are not vulnerable.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'PyPI', 'name': 'apache-airflow'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.10.11'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-11978'}, {'type': 'PACKAGE', 'url': 'https://github.com/apache/airflow'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r7255cf0be3566f23a768e2a04b40fb09e52fcd1872695428ba9afe91%40%3Cusers.airflow.apache.org%3E'}, {'type': 'WEB', 'url': 'http://packetstormsecurity.com/files/162908/Apache-Airflow-1.10.10-Remote-Code-Execution.html'}]

{'cwe_ids': ['CWE-77', 'CWE-78'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-27T16:54:51Z', 'nvd_published_at': '2020-07-17T00:15:00Z'}

1.4.0

GHSA-f97h-2pfx-f59f

2023-02-01T09:16:37Z

2020-07-29T18:07:20Z

['CVE-2020-7695']

HTTP response splitting in uvicorn

Uvicorn before 0.11.7 is vulnerable to HTTP response splitting. CRLF sequences are not escaped in the value of HTTP headers. Attackers can exploit exploit this to add arbitrary headers to HTTP responses, or even return an arbitrary response body, whenever crafted input is used to construct HTTP headers.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}]

[{'package': {'ecosystem': 'PyPI', 'name': 'uvicorn'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.11.7'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-7695'}, {'type': 'PACKAGE', 'url': 'https://github.com/encode/uvicorn'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-PYTHON-UVICORN-570471'}]

{'cwe_ids': ['CWE-74'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-29T17:37:41Z', 'nvd_published_at': '2020-07-27T12:15:00Z'}

1.4.0

GHSA-5jpf-pj32-xx53

2021-01-07T23:44:25Z

2020-07-29T16:26:22Z

['CVE-2020-15125']

Authorization header is not sanitized in an error object in auth0

### Overview Versions before and including `2.27.0` use a block list of specific keys that should be sanitized from the request object contained in the error object. When a request to Auth0 management API fails, the key for `Authorization` header is not sanitized and the `Authorization` header value can be logged exposing a bearer token. ### Am I affected? You are affected by this vulnerability if all of the following conditions apply: - You are using `auth0` npm package - You are using a Machine to Machine application authorized to use Auth0's management API https://auth0.com/docs/flows/concepts/client-credentials ### How to fix that? Upgrade to version `2.27.1` ### Will this update impact my users? The fix provided in patch will not affect your users. ### Credit http://github.com/osdiab

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N'}]

[{'package': {'ecosystem': 'npm', 'name': 'auth0'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.27.1'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/auth0/node-auth0/security/advisories/GHSA-5jpf-pj32-xx53'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15125'}, {'type': 'WEB', 'url': 'https://github.com/auth0/node-auth0/pull/507'}, {'type': 'WEB', 'url': 'https://github.com/auth0/node-auth0/pull/507/commits/62ca61b3348ec8e74d7d00358661af1a8bc98a3c'}, {'type': 'WEB', 'url': 'https://github.com/auth0/node-auth0/tree/v2.27.1'}]

{'cwe_ids': ['CWE-209'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-29T16:25:59Z', 'nvd_published_at': None}

1.4.0

GHSA-236h-rqv8-8q73

2021-01-07T23:46:50Z

2020-07-22T23:06:47Z

['CVE-2020-15126']

GraphQL: Security breach on Viewer query

### Impact An authenticated user using the viewer GraphQL query can bypass all read security on his User object and can also bypass all objects linked via relation or Pointer on his User object. ### Patches This vulnerability has been patched in Parse Server 4.3.0. ### Workarounds No ### References See [commit 78239ac](https://github.com/parse-community/parse-server/commit/78239ac9071167fdf243c55ae4bc9a2c0b0d89aa) for details.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}]

[{'package': {'ecosystem': 'npm', 'name': 'parse-server'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.5.0'}, {'fixed': '4.3.0'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/parse-community/parse-server/security/advisories/GHSA-236h-rqv8-8q73'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15126'}, {'type': 'WEB', 'url': 'https://github.com/parse-community/parse-server/commit/78239ac9071167fdf243c55ae4bc9a2c0b0d89aa'}, {'type': 'WEB', 'url': 'https://github.com/parse-community/parse-server/blob/master/CHANGELOG.md#430'}]

{'cwe_ids': ['CWE-863'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-22T23:06:30Z', 'nvd_published_at': None}

1.4.0

GHSA-vr98-27qj-3c8q

2023-09-05T23:31:52Z

2020-07-29T18:07:35Z

['CVE-2020-7686']

Directory traversal in rollup-plugin-server

This affects all versions of package rollup-plugin-dev-server. There is no path sanitization in `readFile` operation inside the `readFileFromContentBase` function.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}]

[{'package': {'ecosystem': 'npm', 'name': 'rollup-plugin-server'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.7.0'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-7686'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JS-ROLLUPPLUGINDEVSERVER-590124'}]

{'cwe_ids': ['CWE-22'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-29T17:46:03Z', 'nvd_published_at': None}

1.4.0

GHSA-5x3v-2gxr-59m2

2021-04-07T19:55:55Z

2020-07-01T17:26:15Z

['CVE-2019-17572']

Directory traversal in Apache RocketMQ

In Apache RocketMQ 4.2.0 to 4.6.0, when the automatic topic creation in the broker is turned on by default, an evil topic like “../../../../topic2020” is sent from rocketmq-client to the broker, a topic folder will be created in the parent directory in brokers, which leads to a directory traversal vulnerability. Users of the affected versions should apply one of the following: Upgrade to Apache RocketMQ 4.6.1 or later.

[]

[{'package': {'ecosystem': 'Maven', 'name': 'org.apache.rocketmq:rocketmq-broker'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.2.0'}, {'fixed': '4.6.1'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-17572'}, {'type': 'WEB', 'url': 'https://github.com/apache/rocketmq/issues/1637'}, {'type': 'WEB', 'url': 'https://github.com/apache/rocketmq/commit/f8f6fbe4aa7f5dee937e688322628c366b12a552'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/fdea1c5407da47a17d5522fa149a097cacded1916c1c1534d46edc6d%40%3Cprivate.rocketmq.apache.org%3E'}, {'type': 'WEB', 'url': 'https://seclists.org/oss-sec/2020/q2/112'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEROCKETMQ-569108'}]

{'cwe_ids': ['CWE-22'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-01T17:26:05Z', 'nvd_published_at': None}

1.4.0

GHSA-gm9x-q798-hmr4

2021-09-23T17:26:33Z

2020-07-29T14:53:40Z

[]

Command Injection in git-tags-remote

All versions of `git-tags-remote ` are vulnerable to Command Injection. The package fails to sanitize the repository input and passes it directly to an `exec` call on the `get` function . This may allow attackers to execute arbitrary code in the system if the `repo` value passed to the function is user-controlled. The following proof-of-concept creates a file in `/tmp`: ``` const gitTagsRemote = require('git-tags-remote'); gitTagsRemote.get('https://github.com/sh0ji/git-tags-remote.git; echo "Injection Success" > /tmp/command-injection.test') .then(tags => console.log(tags)); ```

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'npm', 'name': 'git-tags-remote'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.0.4'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/sh0ji/git-tags-remote/issues/58'}, {'type': 'WEB', 'url': 'https://github.com/sh0ji/git-tags-remote/commit/a20488960cbd2c98455386108253094897ebfc1c'}, {'type': 'PACKAGE', 'url': 'https://github.com/sh0ji/git-tags-remote'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/advisories/1517'}]

{'cwe_ids': ['CWE-78'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-29T14:52:24Z', 'nvd_published_at': None}

1.4.0

GHSA-h9jc-284h-533g

2021-01-07T23:48:28Z

2020-07-07T00:01:10Z

['CVE-2020-4077']

Context isolation bypass via contextBridge in Electron

### Impact Apps using both `contextIsolation` and `contextBridge` are affected. This is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions. ### Workarounds There are no app-side workarounds, you must update your Electron version to be protected. ### Fixed Versions * `9.0.0-beta.21` * `8.2.4` * `7.2.4` ### For more information If you have any questions or comments about this advisory: * Email us at [security@electronjs.org](mailto:security@electronjs.org)

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N'}]

[{'package': {'ecosystem': 'npm', 'name': 'electron'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '7.2.4'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'electron'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '8.0.0'}, {'fixed': '8.2.4'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/electron/electron/security/advisories/GHSA-h9jc-284h-533g'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-4077'}, {'type': 'WEB', 'url': 'https://github.com/electron/electron/commit/b8e347709245d2dc5640fbb3044d9b21b4eaa6b0'}, {'type': 'WEB', 'url': 'https://www.electronjs.org/releases/stable?page=3#release-notes-for-v824'}]

{'cwe_ids': ['CWE-501'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-06T23:55:23Z', 'nvd_published_at': None}

1.4.0

GHSA-f9mq-jph6-9mhm

2021-01-07T23:48:36Z

2020-07-07T00:01:13Z

['CVE-2020-4075']

Arbitrary file read via window-open IPC in Electron

### Impact The vulnerability allows arbitrary local file read by defining unsafe window options on a child window opened via window.open. ### Workarounds Ensure you are calling `event.preventDefault()` on all [`new-window`](https://electronjs.org/docs/api/web-contents#event-new-window) events where the `url` or `options` is not something you expect. ### Fixed Versions * `9.0.0-beta.21` * `8.2.4` * `7.2.4` ### For more information If you have any questions or comments about this advisory: * Email us at [security@electronjs.org](mailto:security@electronjs.org)

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N'}]

[{'package': {'ecosystem': 'npm', 'name': 'electron'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '7.2.4'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'electron'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '8.0.0'}, {'fixed': '8.2.4'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/electron/electron/security/advisories/GHSA-f9mq-jph6-9mhm'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-4075'}, {'type': 'WEB', 'url': 'https://www.electronjs.org/releases/stable?page=3#release-notes-for-v824'}]

{'cwe_ids': ['CWE-552'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-06T23:54:56Z', 'nvd_published_at': None}

1.4.0

GHSA-vj42-xq3r-hr3r

2023-09-05T09:11:44Z

2020-07-27T21:52:39Z

['CVE-2020-10994']

Out-of-bounds reads in Pillow

In `libImaging/Jpeg2KDecode.c` in Pillow before 7.1.0, there are multiple out-of-bounds reads via a crafted JP2 file.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H'}]

[{'package': {'ecosystem': 'PyPI', 'name': 'Pillow'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '7.1.0'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-10994'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/pull/4505'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/pull/4538'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/commit/ff60894d697d1992147b791101ad53a8bf1352e4'}, {'type': 'PACKAGE', 'url': 'https://github.com/python-pillow/Pillow'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/blob/master/docs/releasenotes/7.1.0.rst#security'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/commits/master/src/libImaging/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BEBCPE4F2VHTIT6EZA2YZQZLPVDEBJGD/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HOKHNWV2VS5GESY7IBD237E7C6T3I427/'}, {'type': 'WEB', 'url': 'https://pillow.readthedocs.io/en/stable/releasenotes/'}, {'type': 'WEB', 'url': 'https://pillow.readthedocs.io/en/stable/releasenotes/7.1.0.html'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-PYTHON-PILLOW-574575'}, {'type': 'WEB', 'url': 'https://usn.ubuntu.com/4430-1/'}, {'type': 'WEB', 'url': 'https://usn.ubuntu.com/4430-2/'}]

{'cwe_ids': ['CWE-125'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-27T21:51:26Z', 'nvd_published_at': '2020-06-25T19:15:00Z'}

1.4.0

GHSA-vh7m-p724-62c2

2021-09-23T17:39:58Z

2020-07-29T20:40:35Z

['CVE-2020-13822']

Signature Malleabillity in elliptic

The Elliptic package before version 6.5.3 for Node.js allows ECDSA signature malleability via variations in encoding, leading '\0' bytes, or integer overflows. This could conceivably have a security-relevant impact if an application relied on a single canonical signature.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L'}]

[{'package': {'ecosystem': 'npm', 'name': 'elliptic'}, 'ecosystem_specific': {'affected_functions': ['elliptic.ec']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.5.3'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-13822'}, {'type': 'WEB', 'url': 'https://github.com/indutny/elliptic/issues/226'}, {'type': 'WEB', 'url': 'https://github.com/indutny/elliptic/commit/856fe4d99fe7b6200556e6400b3bf585b1721bec'}, {'type': 'PACKAGE', 'url': 'https://github.com/indutny/elliptic'}, {'type': 'WEB', 'url': 'https://medium.com/@herman_10687/malleability-attack-why-it-matters-7b5f59fb99a4'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/package/elliptic'}, {'type': 'WEB', 'url': 'https://yondon.blog/2019/01/01/how-not-to-use-ecdsa/'}]

{'cwe_ids': ['CWE-190'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-29T20:39:31Z', 'nvd_published_at': None}

1.4.0

GHSA-f7f4-hqp2-7prc

2021-09-22T21:11:20Z

2020-07-24T20:10:21Z

['CVE-2018-21036']

Improper Input Validation in sails-hook-sockets

Sails.js before v1.0.0-46 allows attackers to cause a denial of service with a single request because there is no error handler in sails-hook-sockets to handle an empty pathname in a WebSocket request.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}]

[{'package': {'ecosystem': 'npm', 'name': 'sails-hook-sockets'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.5.5'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2018-21036'}, {'type': 'WEB', 'url': 'https://github.com/balderdashy/sails-hook-sockets/commit/0533a4864b1920fd8fbb5287bc0889193c5faf44'}, {'type': 'WEB', 'url': 'https://github.com/balderdashy/sails-hook-sockets/commit/ff02114eaec090ee51db48435cc32d451662606e'}, {'type': 'PACKAGE', 'url': 'https://github.com/balderdashy/sails-hook-sockets'}, {'type': 'WEB', 'url': 'https://github.com/balderdashy/sails/blob/56f8276f6501a144a03d1f0f28df4ccdb4ad82e2/CHANGELOG.md'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2020/07/19/1'}]

{'cwe_ids': ['CWE-20'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-24T17:27:33Z', 'nvd_published_at': '2020-07-21T14:15:00Z'}

1.4.0

GHSA-7phr-5m9x-rw9q

2021-09-22T21:15:28Z

2020-07-27T16:02:57Z

['CVE-2020-7687']

Directory traversal in fast-http

This affects all versions of package fast-http. There is no path sanitization in the path provided at fs.readFile in index.js.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}]

[{'package': {'ecosystem': 'npm', 'name': 'fast-http'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.1.3'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-7687'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JS-FASTHTTP-572892'}]

{'cwe_ids': ['CWE-22'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-27T16:00:48Z', 'nvd_published_at': None}

1.4.0

GHSA-cc2p-4jhr-xhhx

2021-01-07T23:43:05Z

2020-07-30T14:58:42Z

['CVE-2020-15130']

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.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}]

[{'package': {'ecosystem': 'npm', 'name': 'slpjs'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.27.4'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/simpleledger/slpjs/security/advisories/GHSA-cc2p-4jhr-xhhx'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15130'}, {'type': 'WEB', 'url': 'https://github.com/simpleledger/slpjs/commit/290c20e8bff13ac81459d43e54cac232b5e3456c'}]

{'cwe_ids': ['CWE-697'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2020-07-30T14:44:06Z', 'nvd_published_at': None}

1.4.0

GHSA-w7q9-p3jq-fmhm

2023-09-08T22:35:55Z

2020-07-27T15:46:57Z

['CVE-2020-8175']

Uncontrolled resource consumption in jpeg-js

Uncontrolled resource consumption in `jpeg-js` before 0.4.0 may allow attacker to launch denial of service attacks using specially a crafted JPEG image.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H'}]

[{'package': {'ecosystem': 'npm', 'name': 'jpeg-js'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.0'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-8175'}, {'type': 'WEB', 'url': 'https://github.com/eugeneware/jpeg-js/commit/135705b1510afb6cb4275a4655d92c58f6843e79'}, {'type': 'WEB', 'url': 'https://hackerone.com/reports/842462'}]

{'cwe_ids': ['CWE-400'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-27T15:46:02Z', 'nvd_published_at': None}

1.4.0

GHSA-jmqm-f2gx-4fjv

2021-09-22T19:00:07Z

2020-07-07T18:59:10Z

[]

Sensitive information exposure through logs in npm-registry-fetch

Affected versions of `npm-registry-fetch` are vulnerable to an information exposure vulnerability through log files. The cli supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N'}]

[{'package': {'ecosystem': 'npm', 'name': 'npm-registry-fetch'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.0.5'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'npm-registry-fetch'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '5.0.0'}, {'fixed': '8.1.1'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/npm/npm-registry-fetch/security/advisories/GHSA-jmqm-f2gx-4fjv'}, {'type': 'WEB', 'url': 'https://github.com/npm/npm-registry-fetch/pull/29'}, {'type': 'WEB', 'url': 'https://github.com/npm/npm-registry-fetch/commit/18bf9b97fb1deecdba01ffb05580370846255c88'}, {'type': 'PACKAGE', 'url': 'https://github.com/npm/npm-registry-fetch'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JS-NPMREGISTRYFETCH-575432'}]

{'cwe_ids': ['CWE-352'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-07T18:26:15Z', 'nvd_published_at': None}

1.4.0

GHSA-vhr6-pvjm-9qwf

2021-01-07T23:48:04Z

2020-07-10T20:55:00Z

['CVE-2020-15105']

User passwords are stored in clear text in the Django session

### Impact django-two-factor-auth versions 1.11 and before store the user's password in clear text in the user session (base64-encoded). The password is stored in the session when the user submits their username and password, and is removed once they complete authentication by entering a two-factor authentication code. This means that the password is stored in clear text in the session for an arbitrary amount of time, and potentially forever if the user begins the login process by entering their username and password, and then leaves before entering their two-factor authentication code. The severity of this issue depends on which type of session storage you have configured: in the worst case, if you're using Django's default database session storage, then users' password are stored in clear text in your database. In the best case, if you're using Django's signed cookie session, then users' passwords are only stored in clear text within their browser's cookie store. In the common case of using Django's cache session store, the users' password are stored in clear text in whatever cache storage you have configured (typically Memcached or Redis). ### Patches Upgrade to version 1.12 to resolve this issue. After upgrading, users should be sure to delete any clear text passwords that have been stored. For example, if you're using the database session backend, you'll likely want to delete any session record from the database and purge that data from any database backups or replicas. In addition, affected organizations who have suffered a database breach while using an affected version should inform their users that their clear text passwords have been compromised. All organizations should encourage users whose passwords were insecurely stored to change these passwords on any sites where they were used. ### Workarounds Switching Django's session storage to use signed cookies instead of the database or cache lessens the impact of this issue, but should not be done without a thorough understanding of the security tradeoffs of using signed cookies rather than a server-side session storage. There is no way to fully mitigate the issue without upgrading. ### References For an explanation of why storing cleartext password is a substantial vulnerability: [Hashing Passwords: One-Way Road to Security](https://auth0.com/blog/hashing-passwords-one-way-road-to-security/). For documentation on configuring the Django session storage engine: [Django session documentation](https://docs.djangoproject.com/en/3.0/topics/http/sessions/). ### For more information If you have any questions or comments about this advisory: * Open an issue in [the repo](https://github.com/Bouke/django-two-factor-auth)

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N'}]

[{'package': {'ecosystem': 'PyPI', 'name': 'django-two-factor-auth'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.12.0'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/Bouke/django-two-factor-auth/security/advisories/GHSA-vhr6-pvjm-9qwf'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15105'}, {'type': 'WEB', 'url': 'https://github.com/Bouke/django-two-factor-auth/commit/454fd9842fa6e8bb772dbf0943976bc8e3335359'}, {'type': 'WEB', 'url': 'https://github.com/Bouke/django-two-factor-auth/blob/master/CHANGELOG.md#112---2020-07-08'}]

{'cwe_ids': ['CWE-312'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-10T20:52:31Z', 'nvd_published_at': None}

1.4.0

GHSA-67j9-c52g-w2q9

2021-01-07T23:46:05Z

2020-07-27T17:47:52Z

['CVE-2020-15120']

Authorization Bypass in I hate money

### Impact An authenticated member of one project can modify and delete members of another project, without knowledge of this other project's private code. This can be further exploited to access all bills of another project without knowledge of this other project's private code. With the default configuration, anybody is allowed to create a new project. An attacker can create a new project and then use it to become authenticated and exploit this flaw. As such, the exposure is similar to an unauthenticated attack, because it is trivial to become authenticated. ### Patches ```diff ihatemoney/models.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ihatemoney/models.py b/ihatemoney/models.py index fe7b519..5691c75 100644 --- a/ihatemoney/models.py +++ b/ihatemoney/models.py @@ -380,7 +380,7 @@ class Person(db.Model): def get_by_name(self, name, project): return ( Person.query.filter(Person.name == name) - .filter(Project.id == project.id) + .filter(Person.project_id == project.id) .one() ) @@ -389,7 +389,7 @@ class Person(db.Model): project = g.project return ( Person.query.filter(Person.id == id) - .filter(Project.id == project.id) + .filter(Person.project_id == project.id) .one() ) ``` ### Workarounds To limit the impact, it is possible to disable public project creation by setting `ALLOW_PUBLIC_PROJECT_CREATION = False` in the configuration (see [documentation](https://ihatemoney.readthedocs.io/en/latest/configuration.html)). Existing users will still be able to exploit the flaw, but this will prevent an external attacker from creating a new project. ### For more information `Person.query.get()` and `Person.query.get_by_name()` were mistakenly running a database join on the Project table without constraining the result. As a result, `Person.query.get(42, "projectfoo")` would return the Person with id=42, even if it is not associated to the project "projectfoo". The only condition is that "projectfoo" must exist. This flaw can be exploited in several places: 1) API: PUT requests to `/api/projects/<project>/members/<personID>` will succeed even though `<personID>` is not a member of `<project>`. This allows an authenticated attacker to alter the state of a member (name, weight, activated) in any project. In addition, the altered member will no longer be associated with its original project but will be associated to the attacker project instead, breaking many features of IHateMoney. For instance, bills referencing the altered member will no longer be visible in the original project. This causes an additional information disclosure and loss of integrity on bills: the attacker will now be able to see, edit and delete bills belonging to the altered member, because IHateMoney now believes that these bills are associated to the attacker project through the altered member. For instance, assume that `Person(id=42)` is a member of project "targetProject", and that the attacker has access to another project "attackerProject" with the private code "attackerPassword". The attacker can modify `Person(id=42)` with this command: $ curl -X PUT -d "name=Pwn3d&activated=1" --basic -u attackerProject:attackerPassword http://$SERVER/api/projects/attackerProject/members/42 The attacker can now see, edit and delete bills paid by `Person(id=42)` by simply browsing to http://$SERVER/attackerProject/ 2) Editing a member through the web interface at `/<project>/members/<personID>/edit` will succeed even though `<personID>` is not a member of `<project>`. This is very similar to the PUT exploit. Reusing the same example, the attacker needs to login to its "attackerProject" project with the private code "attackerPassword". It can then alter the state of `Person(id=42)` by accessing the edit form at the following URL: http://$SERVER/attackerProject/members/42/edit Again, as a result of the alteration, the altered member will become associated to the project "attackerProject", resulting in the same information disclosure and loss of integrity on bills. 3) API: DELETE requests to `/api/projects/<project>/members/<personID>` will similarly allow to delete the member `<personID>` even if it belongs to a different project than `<project>`. $ curl -X DELETE --basic -u attackerProject:attackerPassword http://$SERVER/api/projects/attackerProject/members/42 The impact is less serious than with PUT, because DELETE only deactivates a member (it does not really delete it). All these exploits require authentication: an attacker needs to know a valid project name and its associated "private code". Once this requirement is fullfilled, the attacker can exploit this flaw to alter the state of members in any other project, without needing to know the target project name or its private code. `Person.query.get_by_name()` suffers from the same issue as `Person.query.get()`. It has an additional issue: if multiple Person objects with the same name exist (this is possible if they are associated to different projects), `get_by_name()` will crash with `MultipleResultsFound` because of the call to `one()`. However, since `Person.query.get_by_name()` is currently not used anywhere in IHateMoney, the bug affecting this function has no impact and is not exploitable.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N'}]

[{'package': {'ecosystem': 'PyPI', 'name': 'ihatemoney'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.1.5'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/spiral-project/ihatemoney/security/advisories/GHSA-67j9-c52g-w2q9'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15120'}, {'type': 'WEB', 'url': 'https://github.com/spiral-project/ihatemoney/commit/8d77cf5d5646e1d2d8ded13f0660638f57e98471'}]

{'cwe_ids': ['CWE-863'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-27T17:47:33Z', 'nvd_published_at': None}

1.4.0

GHSA-m5vr-3m74-jwxp

2021-11-19T15:43:34Z

2020-07-29T16:15:19Z

['CVE-2020-15098']

Missing Required Cryptographic Step Leading to Sensitive Information Disclosure in TYPO3 CMS

> ### Meta > * CVSS: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (8.2) > * CWE-325, CWE-20, CWE-200, CWE-502 ### Problem It has been discovered that an internal verification mechanism can be used to generate arbitrary checksums. This allows to inject arbitrary data having a valid cryptographic message authentication code (HMAC-SHA1) and can lead to various attack chains as described below. * [TYPO3-CORE-SA-2020-007](https://typo3.org/security/advisory/typo3-core-sa-2020-007), [CVE-2020-15099](https://nvd.nist.gov/vuln/detail/CVE-2020-15099): Potential Privilege Escalation + the database server used for a TYPO3 installation must be accessible for an attacker (either via internet or shared hosting network) + `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (7.5, high) * [TYPO3-CORE-SA-2016-013](https://typo3.org/security/advisory/typo3-core-sa-2016-013), [CVE-2016-5091](https://nvd.nist.gov/vuln/detail/CVE-2016-5091): Insecure Deserialization & Remote Code Execution + an attacker must have access to at least one Extbase plugin or module action in a TYPO3 installation + `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (9.1, critical) The overall severity of this vulnerability is **high (8.2)** based on mentioned attack chains and the requirement of having a valid backend user session (authenticated). ### Solution Update to TYPO3 versions 9.5.20 or 10.4.6 that fix the problem described. ### Credits Thanks to TYPO3 security team member Oliver Hader who reported and fixed the issue. ### References * [TYPO3-CORE-SA-2020-008](https://typo3.org/security/advisory/typo3-core-sa-2020-008)

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'Packagist', 'name': 'typo3/cms-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '9.0.0'}, {'fixed': '9.5.20'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'typo3/cms-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '10.0.0'}, {'fixed': '10.4.6'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-m5vr-3m74-jwxp'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2016-5091'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15098'}, {'type': 'WEB', 'url': 'https://github.com/TYPO3/TYPO3.CMS/commit/85d3e70dff35a99ef53f4b561114acfa9e5c47e1'}, {'type': 'PACKAGE', 'url': 'https://github.com/TYPO3/TYPO3.CMS'}, {'type': 'WEB', 'url': 'https://typo3.org/security/advisory/typo3-core-sa-2016-013'}, {'type': 'WEB', 'url': 'https://typo3.org/security/advisory/typo3-core-sa-2020-008'}]

{'cwe_ids': ['CWE-20', 'CWE-200', 'CWE-325', 'CWE-327', 'CWE-502'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-29T16:14:21Z', 'nvd_published_at': '2020-07-29T17:15:00Z'}

1.4.0

GHSA-9qcf-c26r-x5rf

2021-10-21T21:18:39Z

2020-07-01T17:55:03Z

['CVE-2019-13990']

XML external entity injection in Terracotta Quartz Scheduler

initDocumentParser in xml/XMLSchedulingDataProcessor.java in Terracotta Quartz Scheduler through 2.3.0 allows XXE attacks via a job description.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'Maven', 'name': 'org.quartz-scheduler:quartz'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.2'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-13990'}, {'type': 'WEB', 'url': 'https://github.com/quartz-scheduler/quartz/issues/467'}, {'type': 'WEB', 'url': 'https://github.com/quartz-scheduler/quartz/pull/501'}, {'type': 'WEB', 'url': 'https://github.com/quartz-scheduler/quartz/commit/13c1d45aa1db15d0fa0e4997139c99ba219be551'}, {'type': 'PACKAGE', 'url': 'https://github.com/quartz-scheduler/quartz'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/172d405e556e2f1204be126bb3eb28c5115af91bcc1651b4e870bb82@%3Cdev.tomee.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/1870324fea41ea68cff2fd1bf6ee2747432dc1d9d22a22cc681e0ec3@%3Cdev.tomee.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/6b6e3480b19856365fb5eef03aa0915a4679de4b019a1e975502d949@%3Cdev.tomee.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/e493e718a50f21201e05e82d42a8796b4046e83f0d286b90e58e0629@%3Cdev.tomee.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/f74b170d3d58d7a24db1afd3908bb0ab58a3900e16e73275674cdfaf@%3Ccommits.tomee.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r21df13c8bd2c2eae4b9661aae814c4a2a814d1f7875c765b8b115c9a@%3Ccommits.tomee.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r3a6884e8d819f32cde8c07b98934de3e80467859880f784950bf44cf@%3Ccommits.tomee.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/re9b56ac1934d7bf16afc83eac1c39c98c1b20b4b15891dce923bf8aa@%3Ccommits.tomee.apache.org%3E'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20221028-0002/'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JAVA-ORGQUARTZSCHEDULER-461170'}, {'type': 'WEB', 'url': 'https://www.oracle.com//security-alerts/cpujul2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuapr2020.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujan2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujul2020.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2020.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2021.html'}]

{'cwe_ids': ['CWE-611'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2020-07-01T17:54:54Z', 'nvd_published_at': '2019-07-26T19:15:00Z'}

1.4.0

GHSA-57gr-jvqr-3hwm

2021-09-23T17:35:16Z

2020-07-29T18:07:38Z

['CVE-2020-15513']

Incorrect access control in typo3_forum

The typo3_forum extension before 1.2.1 for TYPO3 has Incorrect Access Control.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}]

[{'package': {'ecosystem': 'Packagist', 'name': 'mittwald/typo3_forum'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.2.1'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15513'}, {'type': 'WEB', 'url': 'https://typo3.org/help/security-advisories'}, {'type': 'WEB', 'url': 'https://typo3.org/security/advisory/typo3-ext-sa-2020-010'}]

{'cwe_ids': ['CWE-863'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-29T17:53:59Z', 'nvd_published_at': None}

1.4.0

GHSA-9vfj-5g7h-4p24

2021-06-15T18:10:24Z

2020-07-29T18:08:48Z

['CVE-2020-11994']

Server side template injection in Apache Camel

Server-Side Template Injection and arbitrary file disclosure on Camel templating components

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}]

[{'package': {'ecosystem': 'Maven', 'name': 'org.apache.camel:camel-robotframework'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.4.0'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-11994'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/d0e00f2e147a9e9b13a6829133092f349b2882bf6860397368a52600@%3Cannounce.tomcat.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r0a406dc5a158fe6fab6ee85f6e082a8473c0c346b37db8cc7a4619e6%40%3Cdev.camel.apache.org%3E'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JAVA-ORGAPACHECAMEL-575542'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuApr2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujan2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2021.html'}]

{'cwe_ids': ['CWE-74'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-29T18:06:56Z', 'nvd_published_at': '2020-07-08T16:15:00Z'}

1.4.0

GHSA-8843-m7mw-mxqm

2023-09-05T09:17:03Z

2020-07-27T21:52:41Z

['CVE-2020-10379']

Buffer overflow in Pillow

In Pillow before 7.1.0, there are two Buffer Overflows in `libImaging/TiffDecode.c`.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'PyPI', 'name': 'Pillow'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '7.1.0'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-10379'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/issues/4750'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/pull/4538'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/commit/46f4a349b88915787fea3fb91348bb1665831bbb#diff-9478f2787e3ae9668a15123b165c23ac'}, {'type': 'PACKAGE', 'url': 'https://github.com/python-pillow/Pillow'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/commits/master/src/libImaging'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BEBCPE4F2VHTIT6EZA2YZQZLPVDEBJGD/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HOKHNWV2VS5GESY7IBD237E7C6T3I427/'}, {'type': 'WEB', 'url': 'https://pillow.readthedocs.io/en/stable/releasenotes/6.2.3.html'}, {'type': 'WEB', 'url': 'https://pillow.readthedocs.io/en/stable/releasenotes/7.1.0.html'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-PYTHON-PILLOW-574577'}, {'type': 'WEB', 'url': 'https://usn.ubuntu.com/4430-2/'}]

{'cwe_ids': ['CWE-120'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-27T21:51:48Z', 'nvd_published_at': '2020-06-25T19:15:00Z'}

1.4.0

GHSA-cqhg-xjhh-p8hf

2023-09-05T09:19:22Z

2020-07-27T21:52:43Z

['CVE-2020-10177']

Out-of-bounds reads in Pillow

Pillow before 7.1.0 has multiple out-of-bounds reads in `libImaging/FliDecode.c`.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N'}]

[{'package': {'ecosystem': 'PyPI', 'name': 'Pillow'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '7.1.0'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-10177'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/issues/4750'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/pull/4503'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/pull/4538'}, {'type': 'PACKAGE', 'url': 'https://github.com/python-pillow/Pillow'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/commits/master/src/libImaging'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2020/08/msg00012.html'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BEBCPE4F2VHTIT6EZA2YZQZLPVDEBJGD/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HOKHNWV2VS5GESY7IBD237E7C6T3I427/'}, {'type': 'WEB', 'url': 'https://pillow.readthedocs.io/en/stable/releasenotes/6.2.3.html'}, {'type': 'WEB', 'url': 'https://pillow.readthedocs.io/en/stable/releasenotes/7.1.0.html'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-PYTHON-PILLOW-574573'}, {'type': 'WEB', 'url': 'https://usn.ubuntu.com/4430-1/'}, {'type': 'WEB', 'url': 'https://usn.ubuntu.com/4430-2/'}]

{'cwe_ids': ['CWE-125'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-27T21:52:00Z', 'nvd_published_at': '2020-06-25T19:15:00Z'}

1.4.0

GHSA-5f9h-9pjv-v6j7

2022-05-26T20:45:56Z

2020-07-06T21:31:02Z

['CVE-2020-8161']

Directory traversal in Rack::Directory app bundled with Rack

A directory traversal vulnerability exists in rack < 2.2.0 that allows an attacker perform directory traversal vulnerability in the Rack::Directory app that is bundled with Rack which could result in information disclosure.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N'}]

[{'package': {'ecosystem': 'RubyGems', 'name': 'rack'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.1.3'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-8161'}, {'type': 'WEB', 'url': 'https://github.com/rack/rack/commit/dddb7ad18ed79ca6ab06ccc417a169fde451246e'}, {'type': 'PACKAGE', 'url': 'https://github.com/rack/rack'}, {'type': 'WEB', 'url': 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/rack/CVE-2020-8161.yml'}, {'type': 'WEB', 'url': 'https://groups.google.com/forum/#!topic/ruby-security-ann/T4ZIsfRf2eA'}, {'type': 'WEB', 'url': 'https://groups.google.com/g/rubyonrails-security/c/IOO1vNZTzPA'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2020/07/msg00006.html'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2023/01/msg00038.html'}, {'type': 'WEB', 'url': 'https://usn.ubuntu.com/4561-1/'}]

{'cwe_ids': ['CWE-22', 'CWE-548'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-06T21:30:32Z', 'nvd_published_at': '2020-07-02T19:15:00Z'}

1.4.0

GHSA-vc9j-fhvv-8vrf

2023-09-12T18:20:33Z

2020-07-27T19:55:52Z

['CVE-2020-14000']

Remote Code Execution in scratch-vm

MIT Lifelong Kindergarten Scratch scratch-vm before `0.2.0-prerelease.20200714185213` loads extension URLs from untrusted project.json files with certain `_` characters, resulting in remote code execution because the URL's content is treated as a script and is executed as a worker. The responsible code is `getExtensionIdForOpcode` in serialization/sb3.js. The use of `_` is incompatible with a protection mechanism in older versions, in which URLs were split and consequently deserialization attacks were prevented. **NOTE**: the scratch.mit.edu hosted service is not affected because of the lack of worker scripts.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'npm', 'name': 'scratch-vm'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.2.0-prerelease.20200714185213'}]}], 'database_specific': {'last_known_affected_version_range': '<= 0.2.0-prerelease.20200709173451'}}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-14000'}, {'type': 'WEB', 'url': 'https://github.com/LLK/scratch-vm/pull/2476'}, {'type': 'WEB', 'url': 'https://github.com/LLK/scratch-vm/pull/2476/commits/90b9da45f4084958535338d1c4d71a22d6136aab'}, {'type': 'PACKAGE', 'url': 'https://github.com/LLK/scratch-vm'}, {'type': 'WEB', 'url': 'https://scratch.mit.edu/discuss/topic/422904/?page=1#post-4223443'}]

{'cwe_ids': ['CWE-502'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2020-07-27T19:53:24Z', 'nvd_published_at': None}

1.4.0

GHSA-qwfw-gxx2-mmv2

2021-09-22T21:50:54Z

2020-07-27T22:51:37Z

['CVE-2020-13925']

Command Injection in Kylin

Similar to CVE-2020-1956, Kylin has one more restful API which concatenates the API inputs into OS commands and then executes them on the server; while the reported API misses necessary input validation, which causes the hackers to have the possibility to execute OS command remotely. Users of all previous versions after 2.3 should upgrade to 3.1.0.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'Maven', 'name': 'org.apache.kylin:kylin-server-base'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.1.0'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-13925'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r021baf9d8d4ae41e8c8332c167c4fa96c91b5086563d9be55d2d7acf@%3Ccommits.kylin.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r250a867961cfd6e0506240a9c7eaee782d84c6ab0091c7c4bc45f3eb%40%3Cuser.kylin.apache.org%3E'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEKYLIN-584373'}]

{'cwe_ids': ['CWE-78'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2020-07-27T22:49:53Z', 'nvd_published_at': None}

1.4.0

GHSA-q7j5-9j77-g4gq

2021-07-29T20:50:40Z

2020-07-29T18:07:41Z

['CVE-2020-15515']

Remote code execution in turn extension for TYPO3

The turn extension through 0.3.2 for TYPO3 allows Remote Code Execution.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'Packagist', 'name': 'marcwillmann/turn'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.3.3'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15515'}, {'type': 'WEB', 'url': 'https://typo3.org/help/security-advisories'}, {'type': 'WEB', 'url': 'https://typo3.org/security/advisory/typo3-ext-sa-2020-011'}]

{'cwe_ids': ['CWE-74'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-29T18:00:39Z', 'nvd_published_at': '2020-07-07T16:15:00Z'}

1.4.0

GHSA-vjv6-gq77-3mjw

2023-06-27T20:27:43Z

2020-07-07T16:32:45Z

['CVE-2020-15232']

XXE attack in Mapfish Print

### Impact A user can do to an XML External Entity (XXE) attack with the provided SDL style. ### Patches Use version >= 3.24 ### Workarounds No ### References * https://cwe.mitre.org/data/definitions/611.html * https://github.com/mapfish/mapfish-print/pull/1397/commits/e1d0527d13db06b2b62ca7d6afb9e97dacd67a0e ### For more information If you have any questions or comments about this advisory Comment the pull request: https://github.com/mapfish/mapfish-print/pull/1397

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N'}]

[{'package': {'ecosystem': 'Maven', 'name': 'org.mapfish.print:print-lib'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.0'}, {'fixed': '3.24'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.mapfish.print:print-servlet'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.0'}, {'fixed': '3.24'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.mapfish.print:print-standalone'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.0'}, {'fixed': '3.24'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/mapfish/mapfish-print/security/advisories/GHSA-vjv6-gq77-3mjw'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15232'}, {'type': 'WEB', 'url': 'https://github.com/mapfish/mapfish-print/pull/1397'}, {'type': 'WEB', 'url': 'https://github.com/mapfish/mapfish-print/pull/1397/commits/e1d0527d13db06b2b62ca7d6afb9e97dacd67a0e'}, {'type': 'PACKAGE', 'url': 'https://github.com/mapfish/mapfish-print'}]

{'cwe_ids': ['CWE-611'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2020-07-07T16:32:20Z', 'nvd_published_at': None}

1.4.0

GHSA-hg7c-66ff-9q8g

2020-07-31T16:18:53Z

2020-07-31T16:18:53Z

[]

Sandbox bypass in constantinople

constantinople before 3.1.1 affected by a sandbox bypass.

[]

[{'package': {'ecosystem': 'npm', 'name': 'constantinople'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.1.1'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/pugjs/constantinople/commit/01d409c0d081dfd65223e6b7767c244156d35f7f'}, {'type': 'WEB', 'url': 'https://bugzilla.redhat.com/show_bug.cgi?id=1577703'}, {'type': 'ADVISORY', 'url': 'https://github.com/advisories/GHSA-hg7c-66ff-9q8g'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/advisories/568'}]

{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-04-16T03:01:22Z', 'nvd_published_at': None}

1.4.0

GHSA-wvh7-5p38-2qfc

2021-09-22T21:05:43Z

2020-07-23T18:20:10Z

[]

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

[]

[{'package': {'ecosystem': 'npm', 'name': 'parse'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.10.0'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/parse-community/Parse-SDK-JS/security/advisories/GHSA-wvh7-5p38-2qfc'}, {'type': 'WEB', 'url': 'https://github.com/parse-community/Parse-SDK-JS/commit/d1106174571b699f972929dd7cbb8e45b5283cbb'}, {'type': 'PACKAGE', 'url': 'https://github.com/parse-community/Parse-SDK-JS'}]

{'cwe_ids': ['CWE-256'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-23T18:18:24Z', 'nvd_published_at': None}

1.4.0

GHSA-j38c-25fj-mr84

2021-09-22T21:23:36Z

2020-07-27T16:57:34Z

['CVE-2020-9485']

Stored XSS in Apache Airflow

An issue was found in Apache Airflow versions 1.10.10 and below. A stored XSS vulnerability was discovered in the Chart pages of the the "classic" UI.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N'}]

[{'package': {'ecosystem': 'PyPI', 'name': 'apache-airflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.10.11'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-9485'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r7255cf0be3566f23a768e2a04b40fb09e52fcd1872695428ba9afe91%40%3Cusers.airflow.apache.org%3E'}]

{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-27T16:57:02Z', 'nvd_published_at': None}

1.4.0

GHSA-2473-9hgq-j7xw

2021-01-07T23:47:06Z

2020-07-20T17:50:30Z

['CVE-2020-15118']

Cross-Site Scripting in Wagtail

### Impact When a form page type is made available to Wagtail editors through the `wagtail.contrib.forms` app, and the page template is built using Django's standard form rendering helpers such as `form.as_p` ([as directed in the documentation](https://docs.wagtail.io/en/stable/reference/contrib/forms/index.html#usage)), any HTML tags used within a form field's help text will be rendered unescaped in the page. Allowing HTML within help text is [an intentional design decision](https://docs.djangoproject.com/en/3.0/ref/models/fields/#django.db.models.Field.help_text) by Django; however, as a matter of policy Wagtail does not allow editors to insert arbitrary HTML by default, as this could potentially be used to carry out cross-site scripting attacks, including privilege escalation. This functionality should therefore not have been made available to editor-level users. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin. ### Patches Patched versions have been released as Wagtail 2.7.4 (for the LTS 2.7 branch) and Wagtail 2.9.3 (for the current 2.9 branch). In these versions, help text will be escaped to prevent the inclusion of HTML tags. Site owners who wish to re-enable the use of HTML within help text (and are willing to accept the risk of this being exploited by editors) may set `WAGTAILFORMS_HELP_TEXT_ALLOW_HTML = True` in their configuration settings. ### Workarounds Site owners who are unable to upgrade to the new versions can secure their form page templates by [rendering forms field-by-field as per Django's documentation](https://docs.djangoproject.com/en/3.0/topics/forms/#looping-over-the-form-s-fields), but omitting the `|safe` filter when outputting the help text. ### Acknowledgements Many thanks to Timothy Bautista for reporting this issue. ### For more information If you have any questions or comments about this advisory: * Visit Wagtail's [support channels](https://docs.wagtail.io/en/stable/support.html) * Email us at [security@wagtail.io](mailto:security@wagtail.io) (if you wish to send encrypted email, the public key ID is `0x6ba1e1a86e0f8ce8`)

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N'}]

[{'package': {'ecosystem': 'PyPI', 'name': 'wagtail'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.8.0'}, {'fixed': '2.9.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'wagtail'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.7.4'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/wagtail/wagtail/security/advisories/GHSA-2473-9hgq-j7xw'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15118'}, {'type': 'WEB', 'url': 'https://github.com/wagtail/wagtail/commit/d9a41e7f24d08c024acc9a3094940199df94db34'}, {'type': 'WEB', 'url': 'https://docs.djangoproject.com/en/3.0/ref/models/fields/#django.db.models.Field.help_text'}, {'type': 'WEB', 'url': 'https://docs.wagtail.io/en/stable/reference/contrib/forms/index.html#usage'}, {'type': 'WEB', 'url': 'https://github.com/wagtail/wagtail/blob/master/docs/releases/2.9.3.rst'}]

{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-20T17:47:32Z', 'nvd_published_at': None}

1.4.0

GHSA-wwgf-3xp7-cxj4

2021-09-22T20:22:02Z

2020-07-07T16:33:45Z

[]

Potentially sensitive data exposure in Symfony Web Socket Bundle

### Impact Inside `Gos\Bundle\WebSocketBundle\Server\App\Dispatcher\TopicDispatcher::onPublish()`, messages are arbitrarily broadcasted to the related Topic if `Gos\Bundle\WebSocketBundle\Server\App\Dispatcher\TopicDispatcher::dispatch()` does not succeed. The `dispatch()` method can be considered to not succeed if (depending on the version of the bundle) the callback defined on a topic route is misconfigured, a `Gos\Bundle\WebSocketBundle\Topic\TopicInterface` implementation is not found for the callback, a topic which also implements `Gos\Bundle\WebSocketBundle\Topic\SecuredTopicInterface` rejects the connection, or an Exception is unhandled. This can result in an unintended broadcast to the websocket server potentially with data that should be considered sensitive. ### Patches In 1.10.4, 2.6.1, and 3.3.0, `Gos\Bundle\WebSocketBundle\Server\App\Dispatcher\TopicDispatcher::onPublish()` has been changed to no longer broadcast an event's data if `Gos\Bundle\WebSocketBundle\Server\App\Dispatcher\TopicDispatcher::dispatch()` fails. ### Workarounds Upgrade to 1.10.4, 2.6.1, and 3.3.0 Note, the 1.x branch is considered end of support as of July 1, 2020. ### For more information If you have any questions or comments about this advisory: * Open an issue in [this repository](https://github.com/GeniusesOfSymfony/WebSocketBundle)

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'}]

[{'package': {'ecosystem': 'Packagist', 'name': 'gos/web-socket-bundle'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.10.4'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'gos/web-socket-bundle'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.0.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'gos/web-socket-bundle'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.0.0'}, {'fixed': '3.3.0'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/GeniusesOfSymfony/WebSocketBundle/security/advisories/GHSA-wwgf-3xp7-cxj4'}, {'type': 'WEB', 'url': 'https://github.com/FriendsOfPHP/security-advisories/commit/942fd37245cb724ba8cc8d6f11f075a1bd53b338'}, {'type': 'PACKAGE', 'url': 'https://github.com/GeniusesOfSymfony/WebSocketBundle'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-PHP-GOSWEBSOCKETBUNDLE-575401'}]

{'cwe_ids': ['CWE-200'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-07-07T16:21:44Z', 'nvd_published_at': None}

1.4.0

GHSA-6jmr-jfh7-xg3h

2021-01-08T21:00:17Z

2020-07-30T14:58:53Z

['CVE-2020-15131']

False-positive validity for NFT1 genesis transactions

### Impact In the npm package named "slp-validate", versions prior to 1.2.2 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 "slp-validate" has been patched and is published and tagged as version 1.2.2. ### Workarounds Upgrade to slp-validate 1.2.2. ### References * Package location: https://www.npmjs.com/package/slp-validate * SLP NFT1 spec: https://slp.dev/specs/slp-nft-1/#nft1-protocol-requirements * Git commit hash fixing this issue: https://github.com/simpleledger/slp-validate.js/commit/3963cf914afae69084059b82483da916d97af65c * 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/slp-validate.js/issues) repository.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}]

[{'package': {'ecosystem': 'npm', 'name': 'slp-validate'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.2.2'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/simpleledger/slp-validate.js/security/advisories/GHSA-6jmr-jfh7-xg3h'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15131'}, {'type': 'WEB', 'url': 'https://github.com/simpleledger/slp-validate.js/commit/3963cf914afae69084059b82483da916d97af65c'}]

{'cwe_ids': ['CWE-697'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2020-07-30T14:54:40Z', 'nvd_published_at': None}

1.4.0

GHSA-9g2w-5f3v-mfmm

2021-09-22T21:19:02Z

2020-07-27T16:57:33Z

['CVE-2020-11982']

Insecure default config of Celery worker in Apache Airflow

An issue was found in Apache Airflow versions 1.10.10 and below. When using CeleryExecutor, if an attack can connect to the broker (Redis, RabbitMQ) directly, it was possible to insert a malicious payload directly to the broker which could lead to a deserialization attack (and thus remote code execution) on the Worker.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'PyPI', 'name': 'apache-airflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.10.11'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-11982'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r7255cf0be3566f23a768e2a04b40fb09e52fcd1872695428ba9afe91%40%3Cusers.airflow.apache.org%3E'}]

{'cwe_ids': ['CWE-502'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2020-07-27T16:55:08Z', 'nvd_published_at': None}

1.4.0

GHSA-6vrv-94jv-crrg

2021-01-07T23:48:19Z

2020-07-07T00:01:05Z

['CVE-2020-15096']

Context isolation bypass via Promise in Electron

### Impact Apps using `contextIsolation` are affected. This is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions. ### Workarounds There are no app-side workarounds, you must update your Electron version to be protected. ### Fixed Versions * `9.0.0-beta.21` * `8.2.4` * `7.2.4` * `6.1.11` ### For more information If you have any questions or comments about this advisory: * Email us at [security@electronjs.org](mailto:security@electronjs.org)

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:N'}]

[{'package': {'ecosystem': 'npm', 'name': 'electron'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.1.11'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'electron'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '7.0.0'}, {'fixed': '7.2.4'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'electron'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '8.0.0'}, {'fixed': '8.2.4'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/electron/electron/security/advisories/GHSA-6vrv-94jv-crrg'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15096'}, {'type': 'WEB', 'url': 'https://www.electronjs.org/releases/stable?page=3#release-notes-for-v824'}]

{'cwe_ids': ['CWE-501'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2020-07-06T23:55:38Z', 'nvd_published_at': None}

1.4.0

GHSA-p6mc-m468-83gw

2022-02-08T22:04:28Z

2020-07-15T19:15:48Z

['CVE-2020-8203']

Prototype Pollution in lodash

Versions of lodash prior to 4.17.19 are vulnerable to Prototype Pollution. The function zipObjectDeep allows a malicious user to modify the prototype of Object if the property identifiers are user-supplied. Being affected by this issue requires zipping objects based on user-provided property arrays. This vulnerability causes the addition or modification of an existing property that will exist on all objects and may lead to Denial of Service or Code Execution under specific circumstances.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H'}]

[{'package': {'ecosystem': 'npm', 'name': 'lodash'}, 'ecosystem_specific': {'affected_functions': ['lodash.baseSet']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.17.20'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'lodash-es'}, 'ecosystem_specific': {'affected_functions': ['lodash.baseSet']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.17.20'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-8203'}, {'type': 'WEB', 'url': 'https://github.com/lodash/lodash/issues/4744'}, {'type': 'WEB', 'url': 'https://github.com/lodash/lodash/issues/4874'}, {'type': 'WEB', 'url': 'https://github.com/lodash/lodash/commit/c84fe82760fb2d3e03a63379b297a1cc1a2fce12'}, {'type': 'WEB', 'url': 'https://hackerone.com/reports/712065'}, {'type': 'PACKAGE', 'url': 'https://github.com/lodash/lodash'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20200724-0006/'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/advisories/1523'}, {'type': 'WEB', 'url': 'https://www.oracle.com//security-alerts/cpujul2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuApr2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuapr2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujan2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2021.html'}]

{'cwe_ids': ['CWE-1321', 'CWE-770'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-15T19:14:58Z', 'nvd_published_at': '2020-07-15T17:15:00Z'}

1.4.0

GHSA-2v5c-755p-p4gv

2023-05-16T16:01:20Z

2020-07-31T17:40:04Z

['CVE-2020-15133']

Missing TLS certificate verification in faye-websocket

The `Faye::WebSocket::Client` class uses the [`EM::Connection#start_tls`][1] method in [EventMachine][2] to implement the TLS handshake whenever a `wss:` URL is used for the connection. This method does not implement certificate verification by default, meaning that it does not check that the server presents a valid and trusted TLS certificate for the expected hostname. That means that any `wss:` connection made using this library is vulnerable to a man-in-the-middle attack, since it does not confirm the identity of the server it is connected to. This has been a requested feature in EventMachine for many years now; see for example [#275][3], [#378][4], and [#814][5]. In June 2020, [em-http-request][6] published an [advisory][7] related to this problem and fixed it by [implementing TLS verification][8] in their own codebase; although EventMachine does not implement certificate verification itself, it provides an extension point for the caller to implement it, called [`ssl_verify_peer`][9]. Based on this implementation, we have incorporated similar functionality into [faye-websocket for Ruby][10], such that we use the `OpenSSL` module to perform two checks: - The chain of certificates presented by the server is valid and ultimately trusted by your root certificate set -- either your system default root certificates, or a set provided at runtime - The final certificate presented by the server is valid for the hostname used in the request URI; if the connection is made via a proxy we use the hostname from the request, not the proxy's hostname After implementing verification in v1.1.6, em-http-request has elected to leave the `:verify_peer` option switched off by default. We have decided to _enable_ this option by default in faye-websocket, but are publishing a minor release with added functionality for configuring it. We are mindful of the fact that this may break existing programs, but we consider it much more important that all clients have TLS verification turned on by default. A client that is not carrying out verification is either: - talking to the expected server, and will not break under this change - being attacked, and would benefit from being alerted to this fact - deliberately talking to a server that would be rejected by verification The latter case includes situations like talking to a non-public server using a self-signed certificate. We consider this use case to be "working by accident", rather than functionality that was actively supported, and it should be properly and explicitly supported instead. To that end, we have added two new options to the `Faye::WebSocket::Client` constructor: `tls.root_cert_file`, and `tls.verify_peer`. The `:root_cert_file` option lets you provide a different set of root certificates in situations where you don't want to use your system's default root certificates to verify the remote host. It should be a path or an array of paths identifying the certificates to use instead of the defaults. ```rb client = Faye::WebSocket::Client.new('wss://example.com/', [], tls: { root_cert_file: 'path/to/certificate.pem' }) ``` The `:verify_peer` option lets you turn verification off entirely. This should be a last resort and we recommend using the `:root_cert_file` option if possible. ```rb client = Faye::WebSocket::Client.new('wss://example.com/', [], tls: { verify_peer: false }) ``` To get the new behaviour, please upgrade to v0.11.0 of the [Rubygems package][10]. There are, unfortunately, no workarounds for this issue, as you cannot enable `:verify_peer` in EventMachine unless the calling library contains an implementation of `ssl_verify_peer` that actually checks the server's certificates. For further background information on this issue, please see [faye#524][12] and [faye-websocket#129][13]. We would like to thank [Tero Marttila][14] and [Daniel Morsing][15] for providing invaluable assistance and feedback on this issue. [1]: https://www.rubydoc.info/github/eventmachine/eventmachine/EventMachine/Connection:start_tls [2]: https://rubygems.org/gems/eventmachine [3]: https://github.com/eventmachine/eventmachine/issues/275 [4]: https://github.com/eventmachine/eventmachine/pull/378 [5]: https://github.com/eventmachine/eventmachine/issues/814 [6]: https://rubygems.org/gems/em-http-request [7]: https://securitylab.github.com/advisories/GHSL-2020-094-igrigorik-em-http-request [8]: https://github.com/igrigorik/em-http-request/pull/340 [9]: https://www.rubydoc.info/github/eventmachine/eventmachine/EventMachine/Connection:ssl_verify_peer [10]: https://rubygems.org/gems/faye-websocket [12]: https://github.com/faye/faye/issues/524 [13]: https://github.com/faye/faye-websocket-ruby/pull/129 [14]: https://github.com/SpComb [15]: https://github.com/DanielMorsing

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N'}]

[{'package': {'ecosystem': 'RubyGems', 'name': 'faye-websocket'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.11.0'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/faye/faye-websocket-ruby/security/advisories/GHSA-2v5c-755p-p4gv'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15133'}, {'type': 'WEB', 'url': 'https://github.com/eventmachine/eventmachine/issues/275'}, {'type': 'WEB', 'url': 'https://github.com/eventmachine/eventmachine/issues/814'}, {'type': 'WEB', 'url': 'https://github.com/faye/faye/issues/524'}, {'type': 'WEB', 'url': 'https://github.com/eventmachine/eventmachine/pull/378'}, {'type': 'WEB', 'url': 'https://github.com/faye/faye-websocket-ruby/pull/129'}, {'type': 'WEB', 'url': 'https://github.com/igrigorik/em-http-request/pull/340'}, {'type': 'WEB', 'url': 'https://blog.jcoglan.com/2020/07/31/missing-tls-verification-in-faye/'}, {'type': 'PACKAGE', 'url': 'https://github.com/faye/faye-websocket-ruby'}, {'type': 'WEB', 'url': 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/faye-websocket/CVE-2020-15133.yml'}, {'type': 'ADVISORY', 'url': 'https://securitylab.github.com/advisories/GHSL-2020-094-igrigorik-em-http-request'}, {'type': 'WEB', 'url': 'https://www.rubydoc.info/github/eventmachine/eventmachine/EventMachine/Connection:ssl_verify_peer'}, {'type': 'WEB', 'url': 'https://www.rubydoc.info/github/eventmachine/eventmachine/EventMachine/Connection:start_tls'}]

{'cwe_ids': ['CWE-295'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-31T17:39:00Z', 'nvd_published_at': '2020-07-31T18:15:00Z'}

1.4.0

GHSA-hx5g-8hq2-8x4w

2021-09-22T21:51:23Z

2020-07-27T22:51:40Z

['CVE-2020-13926']

SQL Injection in Kylin

Kylin concatenates and executes a Hive SQL in Hive CLI or beeline when building a new segment; some part of the HQL is from system configurations, while the configuration can be overwritten by certain rest api, which makes SQL injection attack is possible. Users of all previous versions after 2.0 should upgrade to 3.1.0.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'Maven', 'name': 'org.apache.kylin:kylin-server-base'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.1.0'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-13926'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r021baf9d8d4ae41e8c8332c167c4fa96c91b5086563d9be55d2d7acf@%3Ccommits.kylin.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r63d5663169e866d44ff9250796193337cff7d9cf61cc3839e86163fd%40%3Cuser.kylin.apache.org%3E'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEKYLIN-584374'}]

{'cwe_ids': ['CWE-89'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2020-07-27T22:50:07Z', 'nvd_published_at': None}

1.4.0

GHSA-33c7-2mpw-hg34

2021-07-29T21:17:18Z

2020-07-29T18:07:16Z

['CVE-2020-7694']

Log injection in uvicorn

This affects all versions of package uvicorn. The request logger provided by the package is vulnerable to ASNI escape sequence injection. Whenever any HTTP request is received, the default behaviour of uvicorn is to log its details to either the console or a log file. When attackers request crafted URLs with percent-encoded escape sequences, the logging component will log the URL after it's been processed with urllib.parse.unquote, therefore converting any percent-encoded characters into their single-character equivalent, which can have special meaning in terminal emulators. By requesting URLs with crafted paths, attackers can: * Pollute uvicorn's access logs, therefore jeopardising the integrity of such files. * Use ANSI sequence codes to attempt to interact with the terminal emulator that's displaying the logs (either in real time or from a file).

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}]

[{'package': {'ecosystem': 'PyPI', 'name': 'uvicorn'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.11.7'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-7694'}, {'type': 'WEB', 'url': 'https://github.com/encode/uvicorn'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-PYTHON-UVICORN-575560'}]

{'cwe_ids': ['CWE-116', 'CWE-94'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-29T17:37:27Z', 'nvd_published_at': '2020-07-27T12:15:00Z'}

1.4.0

GHSA-cr3x-7m39-c6jq

2023-07-05T20:22:39Z

2020-07-07T16:34:27Z

['CVE-2020-8163']

Remote code execution via user-provided local names in ActionView

The is a code injection vulnerability in versions of Rails prior to 5.0.1 that would allow an attacker who controlled the `locals` argument of a `render` call to perform a RCE.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'RubyGems', 'name': 'actionview'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.2.11.3'}]}], 'database_specific': {'last_known_affected_version_range': '<= 4.2.11.1'}}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-8163'}, {'type': 'WEB', 'url': 'https://hackerone.com/reports/304805'}, {'type': 'WEB', 'url': 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/actionview/CVE-2020-8163.yml'}, {'type': 'WEB', 'url': 'https://groups.google.com/forum/#!topic/rubyonrails-security/hWuKcHyoKh0'}, {'type': 'WEB', 'url': 'https://groups.google.com/g/rubyonrails-security/c/hWuKcHyoKh0'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2020/07/msg00013.html'}, {'type': 'WEB', 'url': 'http://packetstormsecurity.com/files/158604/Ruby-On-Rails-5.0.1-Remote-Code-Execution.html'}]

{'cwe_ids': ['CWE-94'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-07-07T15:44:56Z', 'nvd_published_at': '2020-07-02T19:15:00Z'}

1.4.0

GHSA-v2wc-pfq2-5cm6

2021-01-08T20:22:25Z

2020-04-14T23:09:29Z

['CVE-2020-11001']

Possible XSS attack in Wagtail

### Impact A cross-site scripting (XSS) vulnerability exists on the page revision comparison view within the Wagtail admin interface. A user with a limited-permission editor account for the Wagtail admin could potentially craft a page revision history that, when viewed by a user with higher privileges, could perform actions with that user's credentials. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin. ### Patches Patched versions have been released as Wagtail 2.7.2 (for the LTS 2.7 branch) and Wagtail 2.8.1 (for the current 2.8 branch). ### Workarounds Site owners who are unable to upgrade to the new versions can disable the revision comparison view by adding the following URL route to the top of their project's `urls.py` configuration: from django.views.generic.base import RedirectView urlpatterns = [ url(r'^admin/pages/(\d+)/revisions/compare/', RedirectView.as_view(url='/admin/')), # ... ] ### Acknowledgements Many thanks to Vlad Gerasimenko for reporting this issue. ### For more information If you have any questions or comments about this advisory: * Visit Wagtail's [support channels](https://docs.wagtail.io/en/stable/support.html) * Email us at [security@wagtail.io](mailto:security@wagtail.io) (if you wish to send encrypted email, the public key ID is `0x6ba1e1a86e0f8ce8`)

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N'}]

[{'package': {'ecosystem': 'PyPI', 'name': 'wagtail'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.9.0'}, {'fixed': '2.7.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'wagtail'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.8.0'}, {'fixed': '2.8.1'}]}], 'versions': ['2.8.0']}]

[{'type': 'WEB', 'url': 'https://github.com/wagtail/wagtail/security/advisories/GHSA-v2wc-pfq2-5cm6'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-11001'}, {'type': 'WEB', 'url': 'https://github.com/wagtail/wagtail/commit/61045ceefea114c40ac4b680af58990dbe732389'}, {'type': 'WEB', 'url': 'https://github.com/wagtail/wagtail/releases/tag/v2.8.1'}]

{'cwe_ids': ['CWE-80'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-04-14T23:02:21Z', 'nvd_published_at': None}

1.4.0

GHSA-q8xg-8xwf-m598

2021-09-16T20:39:54Z

2020-04-16T03:14:59Z

['CVE-2020-10800']

Machine-In-The-Middle in lix

All versions of `lix` are vulnerable to Machine-In-The-Middle. The package accepts downloads with `http` and follows `location` header redirects for package downloads. This allows for an attacker in a privileged network position to intercept a lix package installation and redirect the download to a malicious source. ## Recommendation No fix is currently available. Consider using an alternative package until a fix is made available.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'npm', 'name': 'lix'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '15.11.4'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-10800'}, {'type': 'PACKAGE', 'url': 'https://github.com/lix-pm/lix.client'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/advisories/1306'}]

{'cwe_ids': ['CWE-544', 'CWE-639'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-04-16T03:10:39Z', 'nvd_published_at': '2020-03-21T15:15:00Z'}

1.4.0

GHSA-prfq-f66g-43mp

2021-01-08T20:23:16Z

2020-04-10T18:19:10Z

['CVE-2020-5263']

Information disclosure through error object in auth0.js

## Overview Between versions 8.0.0 and 9.13.1(inclusive), in the case of an (authentication) error, the error object returned by the library contains the original request of the user, which may include the plaintext password the user entered. If the error object is exposed or logged without modification, the application risks password exposure. ## Am I affected? You are affected by this vulnerability if all of the following conditions apply: - You are using Auth0.js version between 8.0.0 and 9.13.1(inclusive). - You store or display error objects without filtering. ## How to fix that? Developers should upgrade auth0.js to version 9.13.2 or later where user inputted passwords are masked in errors. If upgrading is not possible, a temporary fix may include not storing the error object or displaying it publicly without modification. ## Will this update impact my users? This fix patches the Auth0.js and may require changes in application code due to password no longer available in error object, but it will not impact your users, their current state, or any existing sessions.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N'}]

[{'package': {'ecosystem': 'npm', 'name': 'auth0-js'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '8.0.0'}, {'fixed': '9.13.2'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/auth0/auth0.js/security/advisories/GHSA-prfq-f66g-43mp'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-5263'}, {'type': 'WEB', 'url': 'https://github.com/auth0/auth0.js/commit/355ca749b229fb93142f0b3978399b248d710828'}]

{'cwe_ids': ['CWE-522'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-04-09T15:53:16Z', 'nvd_published_at': None}

1.4.0

GHSA-jpcq-cgw6-v4j6

2022-02-08T22:06:24Z

2020-04-29T22:19:14Z

['CVE-2020-11023']

Potential XSS vulnerability in jQuery

### Impact Passing HTML containing `<option>` elements from untrusted sources - even after sanitizing them - to one of jQuery's DOM manipulation methods (i.e. `.html()`, `.append()`, and others) may execute untrusted code. ### Patches This problem is patched in jQuery 3.5.0. ### Workarounds To workaround this issue without upgrading, use [DOMPurify](https://github.com/cure53/DOMPurify) with its `SAFE_FOR_JQUERY` option to sanitize the HTML string before passing it to a jQuery method. ### References https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/ ### For more information If you have any questions or comments about this advisory, search for a relevant issue in [the jQuery repo](https://github.com/jquery/jquery/issues). If you don't find an answer, open a new issue.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N'}]

[{'package': {'ecosystem': 'npm', 'name': 'jquery'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.0.3'}, {'fixed': '3.5.0'}]}]}, {'package': {'ecosystem': 'RubyGems', 'name': 'jquery-rails'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.4.0'}]}]}, {'package': {'ecosystem': 'NuGet', 'name': 'jQuery'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.0.3'}, {'fixed': '3.5.0'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.webjars.npm:jquery'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.0.3'}, {'fixed': '3.5.0'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/jquery/jquery/security/advisories/GHSA-jpcq-cgw6-v4j6'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-11023'}, {'type': 'WEB', 'url': 'https://blog.jquery.com/2020/04/10/jquery-3-5-0-released'}, {'type': 'PACKAGE', 'url': 'https://github.com/jquery/jquery'}, {'type': 'WEB', 'url': 'https://github.com/jquery/jquery/releases/tag/3.5.0'}, {'type': 'WEB', 'url': 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/jquery-rails/CVE-2020-11023.yml'}, {'type': 'WEB', 'url': 'https://jquery.com/upgrade-guide/3.5/'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r0483ba0072783c2e1bfea613984bfb3c86e73ba8879d780dc1cc7d36@%3Cissues.flink.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r0593393ca1e97b1e7e098fe69d414d6bd0a467148e9138d07e86ebbb@%3Cissues.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r07ab379471fb15644bf7a92e4a98cbc7df3cf4e736abae0cc7625fe6@%3Cdev.felix.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r094f435595582f6b5b24b66fedf80543aa8b1d57a3688fbcc21f06ec@%3Cissues.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r1fed19c860a0d470f2a3eded12795772c8651ff583ef951ddac4918c@%3Cgitbox.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r2c85121a47442036c7f8353a3724aa04f8ecdfda1819d311ba4f5330@%3Cdev.felix.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r3702ede0ff83a29ba3eb418f6f11c473d6e3736baba981a8dbd9c9ef@%3Cdev.felix.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r49ce4243b4738dd763caeb27fa8ad6afb426ae3e8c011ff00b8b1f48@%3Cissues.flink.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r4aadb98086ca72ed75391f54167522d91489a0d0ae25b12baa8fc7c5@%3Cissues.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r4dba67be3239b34861f1b9cfdf9dfb3a90272585dcce374112ed6e16@%3Cdev.felix.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r54565a8f025c7c4f305355fdfd75b68eca442eebdb5f31c2e7d977ae@%3Cissues.flink.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r55f5e066cc7301e3630ce90bbbf8d28c82212ae1f2d4871012141494@%3Cdev.felix.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r564585d97bc069137e64f521e68ba490c7c9c5b342df5d73c49a0760@%3Cissues.flink.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r6c4df3b33e625a44471009a172dabe6865faec8d8f21cac2303463b1@%3Cissues.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r6e97b37963926f6059ecc1e417721608723a807a76af41d4e9dbed49@%3Cissues.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r706cfbc098420f7113968cc377247ec3d1439bce42e679c11c609e2d@%3Cissues.flink.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r8f70b0f65d6bedf316ecd899371fd89e65333bc988f6326d2956735c@%3Cissues.flink.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r9006ad2abf81d02a0ef2126bab5177987e59095b7194a487c4ea247c@%3Ccommits.felix.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r9c5fda81e4bca8daee305b4c03283dddb383ab8428a151d4cb0b3b15@%3Cissues.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r9e0bd31b7da9e7403478d22652b8760c946861f8ebd7bd750844898e@%3Cdev.felix.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/ra32c7103ded9041c7c1cb8c12c8d125a6b2f3f3270e2937ef8417fac@%3Cgitbox.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/ra374bb0299b4aa3e04edde01ebc03ed6f90cf614dad40dd428ce8f72@%3Cgitbox.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/ra3c9219fcb0b289e18e9ec5a5ebeaa5c17d6b79a201667675af6721c@%3Cgitbox.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/ra406b3adfcffcb5ce8707013bdb7c35e3ffc2776a8a99022f15274c6@%3Cissues.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rab82dd040f302018c85bd07d33f5604113573514895ada523c3401d9@%3Ccommits.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/radcb2aa874a79647789f3563fcbbceaf1045a029ee8806b59812a8ea@%3Cissues.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rb25c3bc7418ae75cba07988dafe1b6912f76a9dd7d94757878320d61@%3Cgitbox.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rb69b7d8217c1a6a2100247a5d06ce610836b31e3f5d73fc113ded8e7@%3Cissues.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rbb448222ba62c430e21e13f940be4cb5cfc373cd3bce56b48c0ffa67@%3Cdev.flink.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rd38b4185a797b324c8dd940d9213cf99fcdc2dbf1fc5a63ba7dee8c9@%3Cissues.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rda99599896c3667f2cc9e9d34c7b6ef5d2bbed1f4801e1d75a2b0679@%3Ccommits.nifi.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/re4ae96fa5c1a2fe71ccbb7b7ac1538bd0cb677be270a2bf6e2f8d108@%3Cissues.flink.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rede9cfaa756e050a3d83045008f84a62802fc68c17f2b4eabeaae5e4@%3Cissues.flink.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/ree3bd8ddb23df5fa4e372d11c226830ea3650056b1059f3965b3fce2@%3Cissues.flink.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rf0f8939596081d84be1ae6a91d6248b96a02d8388898c372ac807817@%3Cdev.felix.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rf1ba79e564fe7efc56aef7c986106f1cf67a3427d08e997e088e7a93@%3Cgitbox.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rf661a90a15da8da5922ba6127b3f5f8194d4ebec8855d60a0dd13248@%3Cdev.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2021/03/msg00033.html'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2023/08/msg00040.html'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AVKYXLWCLZBV2N7M46KYK4LVA5OXWPBY/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QPN2L2XVQGUA2V5HNQJWHK3APSK3VN7K/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SAPQVX3XDNPGFT26QAQ6AJIXZZBZ4CD4/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SFP4UK4EGP4AFH2MWYJ5A5Z4I7XVFQ6B/'}, {'type': 'WEB', 'url': 'https://security.gentoo.org/glsa/202007-03'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20200511-0006/'}, {'type': 'WEB', 'url': 'https://security.snyk.io/vuln/SNYK-DOTNET-JQUERY-565440'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2020/dsa-4693'}, {'type': 'WEB', 'url': 'https://www.drupal.org/sa-core-2020-002'}, {'type': 'WEB', 'url': 'https://www.oracle.com//security-alerts/cpujul2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuApr2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuapr2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujan2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujan2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujul2020.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujul2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2020.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2021.html'}, {'type': 'WEB', 'url': 'https://www.tenable.com/security/tns-2021-02'}, {'type': 'WEB', 'url': 'https://www.tenable.com/security/tns-2021-10'}, {'type': 'WEB', 'url': 'http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00067.html'}, {'type': 'WEB', 'url': 'http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00085.html'}, {'type': 'WEB', 'url': 'http://lists.opensuse.org/opensuse-security-announce/2020-11/msg00039.html'}, {'type': 'WEB', 'url': 'http://packetstormsecurity.com/files/162160/jQuery-1.0.3-Cross-Site-Scripting.html'}]

{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-04-29T21:04:50Z', 'nvd_published_at': '2020-04-29T21:15:00Z'}

1.4.0

GHSA-5p34-5m6p-p58g

2021-08-25T20:57:31Z

2020-04-23T21:08:40Z

['CVE-2020-9546']

jackson-databind mishandles the interaction between serialization gadgets and typing

FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.hadoop.shaded.com.zaxxer.hikari.HikariConfig (aka shaded hikari-config).

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'Maven', 'name': 'com.fasterxml.jackson.core:jackson-databind'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.9.0'}, {'fixed': '2.9.10.4'}]}], 'database_specific': {'last_known_affected_version_range': '<= 2.9.10.3'}}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-9546'}, {'type': 'WEB', 'url': 'https://github.com/FasterXML/jackson-databind/issues/2631'}, {'type': 'PACKAGE', 'url': 'https://github.com/FasterXML/jackson-databind'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r35d30db00440ef63b791c4b7f7acb036e14d4a23afa2a249cb66c0fd@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r893a0104e50c1c2559eb9a5812add28ae8c3e5f43712947a9847ec18@%3Cnotifications.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r9464a40d25c3ba1a55622db72f113eb494a889656962d098c70c5bb1@%3Cdev.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r98c9b6e4c9e17792e2cd1ec3e4aa20b61a791939046d3f10888176bb@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rb6fecb5e96a6d61e175ff49f33f2713798dd05cf03067c169d195596@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rd5a4457be4623038c3989294429bc063eec433a2e55995d81591e2ca@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rdd49ab9565bec436a896bc00c4b9fc9dce1598e106c318524fbdfec6@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rdd4df698d5d8e635144d2994922bf0842e933809eae259521f3b5097@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rf1bbc0ea4a9f014cf94df9a12a6477d24a27f52741dbc87f2fd52ff2@%3Cissues.geode.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2020/03/msg00008.html'}, {'type': 'WEB', 'url': 'https://medium.com/@cowtowncoder/on-jackson-cves-dont-panic-here-is-what-you-need-to-know-54cd0d6e8062'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20200904-0006/'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujan2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujul2020.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2020.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2021.html'}]

{'cwe_ids': ['CWE-502'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2020-04-23T19:26:40Z', 'nvd_published_at': '2020-03-02T04:15:00Z'}

1.4.0

GHSA-fv3h-8x5j-pvgq

2023-09-01T10:18:10Z

2020-04-22T20:59:50Z

['CVE-2020-11888']

XSS in python-markdown2

python-markdown2 through 2.3.8 allows XSS because element names are mishandled unless a \w+ match succeeds. For example, an attack might use elementname@ or elementname- with an onclick attribute.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N'}]

[{'package': {'ecosystem': 'PyPI', 'name': 'markdown2'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.9'}]}], 'database_specific': {'last_known_affected_version_range': '<= 2.3.8'}}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-11888'}, {'type': 'WEB', 'url': 'https://github.com/trentm/python-markdown2/issues/348'}, {'type': 'PACKAGE', 'url': 'https://github.com/trentm/python-markdown2'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6XOAIRJJCZNJUALXDHSIGH5PS2H63A3J/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AQLRBGRVRRZK7P5SFL2MNGXFX37YHJAV/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PN6QSHRFZXRQAYZJQ4MOW5MKIXBYOMED/'}, {'type': 'WEB', 'url': 'http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00031.html'}, {'type': 'WEB', 'url': 'http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00035.html'}]

{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-04-22T19:19:38Z', 'nvd_published_at': None}

1.4.0

GHSA-5gm3-px64-rw72

2023-02-02T10:30:38Z

2020-04-01T16:36:44Z

['CVE-2019-19911']

Uncontrolled Resource Consumption in Pillow

There is a DoS vulnerability in Pillow before 6.2.2 caused by FpxImagePlugin.py calling the range function on an unvalidated 32-bit integer if the number of bands is large. On Windows running 32-bit Python, this results in an OverflowError or MemoryError due to the 2 GB limit. However, on Linux running 64-bit Python this results in the process being terminated by the OOM killer.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}]

[{'package': {'ecosystem': 'PyPI', 'name': 'Pillow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.2.2'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-19911'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/commit/774e53bb132461d8d5ebefec1162e29ec0ebc63d'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/blob/master/CHANGES.rst#622-2020-01-02'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3DUMIBUYGJRAVJCTFUWBRLVQKOUTVX5P/'}, {'type': 'WEB', 'url': 'https://pillow.readthedocs.io/en/stable/releasenotes/6.2.2.html'}, {'type': 'WEB', 'url': 'https://usn.ubuntu.com/4272-1/'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2020/dsa-4631'}]

{'cwe_ids': ['CWE-190'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-04-01T16:30:58Z', 'nvd_published_at': '2020-01-05T22:15:00Z'}

1.4.0

GHSA-9q64-mpxx-87fg

2020-12-15T16:51:18Z

2020-04-01T16:35:08Z

[]

Open Redirect in ecstatic

Versions of `ecstatic` prior to 4.1.2, 3.3.2 or 2.2.2 are vulnerable to Open Redirect. The package fails to validate redirects, allowing attackers to craft requests that result in an `HTTP 301` redirect to any other domains. ## Recommendation If using `ecstatic` 4.x, upgrade to 4.1.2 or later. If using `ecstatic` 3.x, upgrade to 3.3.2 or later. If using `ecstatic` 2.x, upgrade to 2.2.2 or later.

[]

[{'package': {'ecosystem': 'npm', 'name': 'ecstatic'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.2.2'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'ecstatic'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.0.0'}, {'fixed': '3.3.2'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'ecstatic'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.0.0'}, {'fixed': '4.1.2'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-10775'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/advisories/830'}]

{'cwe_ids': ['CWE-601'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-04-01T15:37:18Z', 'nvd_published_at': None}

1.4.0

GHSA-h4rc-386g-6m85

2021-08-23T15:31:59Z

2020-04-23T20:19:02Z

['CVE-2020-11620']

jackson-databind mishandles the interaction between serialization gadgets and typing

FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.jelly.impl.Embedded (aka commons-jelly).

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'Maven', 'name': 'com.fasterxml.jackson.core:jackson-databind'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.9.0'}, {'fixed': '2.9.10.4'}]}], 'database_specific': {'last_known_affected_version_range': '<= 2.9.10.3'}}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-11620'}, {'type': 'WEB', 'url': 'https://github.com/FasterXML/jackson-databind/issues/2682'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rf1bbc0ea4a9f014cf94df9a12a6477d24a27f52741dbc87f2fd52ff2@%3Cissues.geode.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2020/04/msg00012.html'}, {'type': 'WEB', 'url': 'https://medium.com/@cowtowncoder/on-jackson-cves-dont-panic-here-is-what-you-need-to-know-54cd0d6e8062'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20200511-0004/'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujan2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujul2020.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2020.html'}]

{'cwe_ids': ['CWE-502'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-04-22T21:17:03Z', 'nvd_published_at': '2020-04-07T23:15:00Z'}

1.4.0

GHSA-9475-xg6m-j7pw

2021-01-08T20:21:35Z

2020-04-22T20:59:37Z

['CVE-2020-5268']

Subject Confirmation Method not validated in Saml2 Authentication Services for ASP.NET

### Impact Saml2 tokens are usually used as bearer tokens - a caller that presents a token is assumed to be the subject of the token. There is also support in the Saml2 protocol for issuing tokens that is tied to a subject through other means, e.g. holder-of-key where possession of a private key must be proved. The Sustainsys.Saml2 library incorrectly treats all incoming tokens as bearer tokens, even though they have another subject confirmation method specified. This could be used by an attacker that could get access to Saml2 tokens with another subject confirmation method than bearer. The attacker could then use such a tocken to create a log in session. ### Patches Version 1.0.2 and 2.7.0 are patched. ### Workarounds Ensure that any IdentityProvider trusted by the Sustainsys.Saml2 SP only issues bearer tokens if the audience matches the Sustainsys.Saml2 SP. ### For more information If you have any questions or comments about this advisory: * Comment on #103 * Email us at security@sustainsys.com if you think that there are further security issues.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:L/A:N'}]

[{'package': {'ecosystem': 'NuGet', 'name': 'Sustainsys.Saml2'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.0.2'}]}]}, {'package': {'ecosystem': 'NuGet', 'name': 'Sustainsys.Saml2'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.0.0'}, {'fixed': '2.7.0'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/Sustainsys/Saml2/security/advisories/GHSA-9475-xg6m-j7pw'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-5268'}, {'type': 'WEB', 'url': 'https://github.com/Sustainsys/Saml2/issues/712'}, {'type': 'WEB', 'url': 'https://github.com/Sustainsys/Saml2/commit/e58e0a1aff2b1ead6aca080b7cdced55ee6d5241'}, {'type': 'WEB', 'url': 'https://www.nuget.org/packages/Sustainsys.Saml2/'}]

{'cwe_ids': ['CWE-303'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2020-04-21T18:41:43Z', 'nvd_published_at': None}

1.4.0

GHSA-qpg4-4w7w-2mq5

2023-05-16T15:51:44Z

2020-04-29T17:41:15Z

['CVE-2020-11020']

Authentication and extension bypass in Faye

On 20 April 2020 it was reported to me that the potential for authentication bypass exists in [Faye][1]'s extension system. This vulnerability has existed in the Node.js and Ruby versions of the server since version 0.5.0, when extensions were first introduced, in July 2010. It is patched in versions 1.0.4, 1.1.3 and 1.2.5, which we are releasing today. The vulnerability allows any client to bypass checks put in place by server-side extensions, by appending extra segments to the message channel. For example, the Faye [extension docs][2] suggest that users implement access control for subscriptions by checking incoming messages for the `/meta/subscribe` channel, for example: ```js server.addExtension({ incoming: function(message, callback) { if (message.channel === '/meta/subscribe') { if (message.ext.authToken !== 'my super secret password') { message.error = 'Invalid auth token'; } } callback(message); } }); ``` A bug in the server's code for recognising the special `/meta/*` channels, which trigger connection and subscription events, means that a client can bypass this check by sending a message to `/meta/subscribe/x` rather than `/meta/subscribe`: ```json { "channel": "/meta/subscribe/x", "clientId": "3jrc6602npj4gyp6bn5ap2wqzjtb2q3", "subscription": "/foo" } ``` This message will not be checked by the above extension, as it checks the message's channel is exactly equal to `/meta/subscribe`. But it will still be processed as a subscription request by the server, so the client becomes subscribed to the channel `/foo` without supplying the necessary credentials. The vulnerability is caused by the way the Faye server recognises meta channels. It will treat a message to any channel that's a prefix-match for one of the special channels `/meta/handshake`, `/meta/connect`, `/meta/subscribe`, `/meta/unsubscribe` or `/meta/disconnect`, as though it were an exact match for that channel. So, a message to `/meta/subscribe/x` is still processed as a subscription request, for example. An authentication bypass for subscription requests is the most serious effect of this but all other meta channels are susceptible to similar manipulation. This parsing bug in the server is fixed in versions 1.0.4, 1.1.3 and 1.2.5. These should be drop-in replacements for prior versions and you should upgrade immediately if you are running any prior version. If you are unable to install one of these versions, you can make your extensions catch all messages the server would process by checking the channel _begins_ with the expected channel name, for example: ```js server.addExtension({ incoming: function(message, callback) { if (message.channel.startsWith('/meta/subscribe')) { // authentication logic } callback(message); } }); ``` [1]: https://faye.jcoglan.com/ [2]: https://faye.jcoglan.com/node/extensions.html

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N'}]

[{'package': {'ecosystem': 'RubyGems', 'name': 'faye'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.5.0'}, {'fixed': '1.0.4'}]}]}, {'package': {'ecosystem': 'RubyGems', 'name': 'faye'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.1.0'}, {'fixed': '1.1.3'}]}]}, {'package': {'ecosystem': 'RubyGems', 'name': 'faye'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.2.0'}, {'fixed': '1.2.5'}]}]}]

[{'type': 'WEB', 'url': 'https://github.com/faye/faye/security/advisories/GHSA-qpg4-4w7w-2mq5'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-11020'}, {'type': 'WEB', 'url': 'https://github.com/faye/faye/commit/65d297d341b607f3cb0b5fa6021a625a991cc30e'}, {'type': 'PACKAGE', 'url': 'https://github.com/faye/faye'}, {'type': 'WEB', 'url': 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/faye/CVE-2020-11020.yml'}]

{'cwe_ids': ['CWE-287'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-04-29T17:40:59Z', 'nvd_published_at': None}

1.4.0

GHSA-758m-v56v-grj4

2021-08-25T20:58:08Z

2020-04-23T21:36:03Z

['CVE-2020-10969']

jackson-databind mishandles the interaction between serialization gadgets and typing

FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to javax.swing.JEditorPane.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'Maven', 'name': 'com.fasterxml.jackson.core:jackson-databind'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.9.0'}, {'fixed': '2.9.10.4'}]}], 'database_specific': {'last_known_affected_version_range': '<= 2.9.10.3'}}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-10969'}, {'type': 'WEB', 'url': 'https://github.com/FasterXML/jackson-databind/issues/2642'}, {'type': 'PACKAGE', 'url': 'https://github.com/FasterXML/jackson-databind'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2020/04/msg00012.html'}, {'type': 'WEB', 'url': 'https://medium.com/@cowtowncoder/on-jackson-cves-dont-panic-here-is-what-you-need-to-know-54cd0d6e8062'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20200403-0002/'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujan2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujul2020.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2020.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2021.html'}]

{'cwe_ids': ['CWE-502'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-04-23T19:28:10Z', 'nvd_published_at': '2020-03-26T13:15:00Z'}

1.4.0

GHSA-4g46-5grc-wq49

2020-08-31T18:59:46Z

2020-04-01T16:36:31Z

['CVE-2019-15603']

Cross-Site Scripting in seeftl

All versions of `seeftl` are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code. ## Recommendation No fix is currently available. Consider using an alternative package until a fix is made available.

[]

[{'package': {'ecosystem': 'npm', 'name': 'seeftl'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.1.1'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-15603'}, {'type': 'WEB', 'url': 'https://hackerone.com/reports/665302'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/advisories/1451'}]

{'cwe_ids': ['CWE-79'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2020-04-01T16:26:05Z', 'nvd_published_at': None}

1.4.0

GHSA-426h-24vj-qwxf

2021-07-29T15:52:29Z

2020-04-23T20:09:09Z

['CVE-2020-7614']

Command Injection in npm-programmatic

All versions of `npm-programmatic ` are vulnerable to Command Injection. The package fails to sanitize input rules and passes it directly to an `exec` call on the `install`, `uninstall` and `list` functions . This may allow attackers to execute arbitrary code in the system if the package name passed to the function is user-controlled. ## Recommendation No fix is currently available. Consider using an alternative package until a fix is made available.

[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]

[{'package': {'ecosystem': 'npm', 'name': 'npm-programmatic'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.0.12'}]}]}]

[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-7614'}, {'type': 'WEB', 'url': 'https://github.com/Manak/npm-programmatic/blob/master/index.js#L18'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JS-NPMPROGRAMMATIC-564115'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/advisories/1507'}]

{'cwe_ids': ['CWE-20', 'CWE-78'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2020-04-23T20:02:33Z', 'nvd_published_at': '2020-04-07T14:15:00Z'}