ecosystem stringclasses 11
values | vuln_id stringlengths 10 19 | summary stringlengths 4 220 ⌀ | details stringlengths 34 13.5k | aliases stringlengths 17 87 ⌀ | modified_date stringdate 2019-03-26 14:13:00 2022-05-10 08:46:52 | published_date stringdate 2012-06-17 03:41:00 2022-05-10 08:46:50 | severity stringclasses 5
values | score float64 0 10 ⌀ | cwe_id stringclasses 581
values | refs stringlengths 82 11.6k | introduced stringclasses 843
values | code_refs stringlengths 46 940 | commits stringlengths 46 940 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
GHSA | GHSA-7r2x-3qcm-8vfw | Downloads Resources over HTTP in herbivore | Affected versions of `herbivore` insecurely download an executable over an unencrypted HTTP connection.
In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running `herbivore`.
## Recommendation
The module author has rewritten much of the package, and in that process, patched the vulnerability, but has not published any of the new code to npm.
In order to get an updated version, it is necessary to install the package from github. This can be done using the following command:
```
npm i samatt/herbivore
``` | {'CVE-2016-10665'} | 2021-01-08T19:14:21Z | 2019-02-18T23:44:36Z | HIGH | 0 | {'CWE-311'} | {'https://github.com/samatt/herbivore', 'https://nodesecurity.io/advisories/258', 'https://www.npmjs.com/advisories/258', 'https://github.com/samatt/Herbivore/commit/0a041defc3463e99948e5d2064aef54b2128c5a3', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10665', 'https://github.com/advisories/GHSA-7r2x-3qcm-8vfw'} | null | {'https://github.com/samatt/Herbivore/commit/0a041defc3463e99948e5d2064aef54b2128c5a3'} | {'https://github.com/samatt/Herbivore/commit/0a041defc3463e99948e5d2064aef54b2128c5a3'} |
GHSA | GHSA-cph5-m8f7-6c5x | Incorrect Comparison in axios | axios is vulnerable to Inefficient Regular Expression Complexity | {'CVE-2021-3749'} | 2022-05-05T13:51:38Z | 2021-09-01T18:23:02Z | HIGH | 7.5 | {'CWE-400', 'CWE-697'} | {'https://www.npmjs.com/package/axios', 'https://lists.apache.org/thread.html/rc263bfc5b53afcb7e849605478d73f5556eb0c00d1f912084e407289@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/r216f0fd0a3833856d6a6a1fada488cadba45f447d87010024328ccf2@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/r3ae6d2654f92c5851bdb73b35e96b0e4e3da39f28ac7a1b15ae3aab8@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/rfa094029c959da0f7c8cd7dc9c4e59d21b03457bf0cedf6c93e1bb0a@%3Cdev.druid.apache.org%3E', 'https://lists.apache.org/thread.html/r4bf1b32983f50be00f9752214c1b53738b621be1c2b0dbd68c7f2391@%3Ccommits.druid.apache.org%3E', 'https://huntr.dev/bounties/1e8f07fc-c384-4ff9-8498-0690de2e8c31', 'https://lists.apache.org/thread.html/r075d464dce95cd13c03ff9384658edcccd5ab2983b82bfc72b62bb10@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/ra15d63c54dc6474b29f72ae4324bcb03038758545b3ab800845de7a1@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/r7324ecc35b8027a51cb6ed629490fcd3b2d7cf01c424746ed5744bf1@%3Ccommits.druid.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3749', 'https://lists.apache.org/thread.html/r74d0b359408fff31f87445261f0ee13bdfcac7d66f6b8e846face321@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/rfc5c478053ff808671aef170f3d9fc9d05cc1fab8fb64431edc66103@%3Ccommits.druid.apache.org%3E', 'https://github.com/axios/axios/commit/5b457116e31db0e88fede6c428e969e87f290929', 'https://github.com/advisories/GHSA-cph5-m8f7-6c5x'} | null | {'https://github.com/axios/axios/commit/5b457116e31db0e88fede6c428e969e87f290929'} | {'https://github.com/axios/axios/commit/5b457116e31db0e88fede6c428e969e87f290929'} |
GHSA | GHSA-6jv7-28mv-qp9c | Missing permission check in Jenkins autonomiq Plugin | A missing permission check in Jenkins autonomiq Plugin 1.15 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials. | {'CVE-2022-25195'} | 2022-05-04T20:59:05Z | 2022-02-16T00:01:23Z | MODERATE | 4.3 | {'CWE-862'} | {'https://www.jenkins.io/security/advisory/2022-02-15/#SECURITY-2545', 'https://github.com/advisories/GHSA-6jv7-28mv-qp9c', 'https://github.com/jenkinsci/autonomiq-plugin/commit/e06b1ff67664a90819c9561bbc12f4c6e593d1dc', 'https://nvd.nist.gov/vuln/detail/CVE-2022-25195'} | null | {'https://github.com/jenkinsci/autonomiq-plugin/commit/e06b1ff67664a90819c9561bbc12f4c6e593d1dc'} | {'https://github.com/jenkinsci/autonomiq-plugin/commit/e06b1ff67664a90819c9561bbc12f4c6e593d1dc'} |
GHSA | GHSA-fr28-569j-53c4 | Incorrect Default Permissions | An issue was discovered in Django 2.2 before 2.2.16, 3.0 before 3.0.10, and 3.1 before 3.1.1 (when Python 3.7+ is used). The intermediate-level directories of the filesystem cache had the system's standard umask rather than 0o077. | {'CVE-2020-24584'} | 2021-03-18T20:30:01Z | 2021-03-18T20:30:01Z | HIGH | 7.5 | {'CWE-276'} | {'https://usn.ubuntu.com/4479-1/', 'https://github.com/django/django/commit/1853724acaf17ed7414d54c7d2b5563a25025a71', 'https://www.openwall.com/lists/oss-security/2020/09/01/2', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OLGFFLMF3X6USMJD7V5F5P4K2WVUTO3T/', 'https://www.djangoproject.com/weblog/2020/sep/01/security-releases/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-24584', 'https://docs.djangoproject.com/en/dev/releases/security/', 'https://groups.google.com/forum/#!topic/django-announce/Gdqn58RqIDM', 'https://groups.google.com/forum/#!topic/django-announce/zFCMdgUnutU', 'https://github.com/advisories/GHSA-fr28-569j-53c4', 'https://security.netapp.com/advisory/ntap-20200918-0004/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/F2ZHO3GZCJMP3DDTXCNVFV6ED3W64NAU/', 'https://www.oracle.com/security-alerts/cpujan2021.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZCRPQCBTV3RZHKVZ6K6QOAANPRZQD3GI/'} | null | {'https://github.com/django/django/commit/1853724acaf17ed7414d54c7d2b5563a25025a71'} | {'https://github.com/django/django/commit/1853724acaf17ed7414d54c7d2b5563a25025a71'} |
GHSA | GHSA-fx7m-j728-mjw3 | Moderate severity vulnerability that affects uap-core | An issue was discovered in regex.yaml (aka regexes.yaml) in UA-Parser UAP-Core before 0.6.0. A Regular Expression Denial of Service (ReDoS) issue allows remote attackers to overload a server by setting the User-Agent header in an HTTP(S) request to a value containing a long digit string. (The UAP-Core project contains the vulnerability, propagating to all implementations.) | {'CVE-2018-20164'} | 2021-09-10T20:12:02Z | 2019-03-06T17:35:47Z | MODERATE | 5.3 | {'CWE-185'} | {'https://github.com/advisories/GHSA-fx7m-j728-mjw3', 'https://nvd.nist.gov/vuln/detail/CVE-2018-20164', 'https://github.com/ua-parser/uap-core/commit/010ccdc7303546cd22b9da687c29f4a996990014', 'https://www.x41-dsec.de/lab/advisories/x41-2018-009-uaparser/', 'https://github.com/ua-parser/uap-core/issues/332', 'https://github.com/ua-parser/uap-core/commit/156f7e12b215bddbaf3df4514c399d683e6cdadc'} | null | {'https://github.com/ua-parser/uap-core/commit/010ccdc7303546cd22b9da687c29f4a996990014', 'https://github.com/ua-parser/uap-core/commit/156f7e12b215bddbaf3df4514c399d683e6cdadc'} | {'https://github.com/ua-parser/uap-core/commit/156f7e12b215bddbaf3df4514c399d683e6cdadc', 'https://github.com/ua-parser/uap-core/commit/010ccdc7303546cd22b9da687c29f4a996990014'} |
GHSA | GHSA-cv3v-7846-6pxm | Unauthorized File Access in node-git-server | Versions of `node-git-server` prior to 0.6.1 are vulnerable to Unauthorized File Access. It is possible to access any git repository by using absolute paths, which may allow attackers to access private repositories.
## Recommendation
Upgrade to version 0.6.1 or later. | null | 2021-09-29T19:59:02Z | 2020-09-03T21:15:19Z | HIGH | 7.5 | {'CWE-552'} | {'https://snyk.io/vuln/SNYK-JS-NODEGITSERVER-474343', 'https://github.com/gabrielcsapo/node-git-server/commit/ac26650f69bc445d71e4f2c55328676d10a4be43', 'https://github.com/gabrielcsapo/node-git-server/pull/62', 'https://www.npmjs.com/advisories/1214', 'https://github.com/advisories/GHSA-cv3v-7846-6pxm'} | null | {'https://github.com/gabrielcsapo/node-git-server/commit/ac26650f69bc445d71e4f2c55328676d10a4be43'} | {'https://github.com/gabrielcsapo/node-git-server/commit/ac26650f69bc445d71e4f2c55328676d10a4be43'} |
GHSA | GHSA-j636-crp3-m584 | Cross-site Scripting in tableexport.jquery.plugin | There is a cross-site scripting vulnerability with default `onCellHtmlData` function in GitHub repository hhurz/tableexport.jquery.plugin prior to 1.25.0. This can result in transmitting cookies to third-party servers and/or sending data from secure sessions to third-party servers. | {'CVE-2022-1291'} | 2022-04-22T20:17:23Z | 2022-04-11T00:00:22Z | MODERATE | 5.4 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-1291', 'https://github.com/advisories/GHSA-j636-crp3-m584', 'https://github.com/hhurz/tableexport.jquery.plugin/commit/dcbaee23cf98328397a153e71556f75202988ec9', 'https://huntr.dev/bounties/49a14371-6058-47dd-9801-ec38a7459fc5'} | null | {'https://github.com/hhurz/tableexport.jquery.plugin/commit/dcbaee23cf98328397a153e71556f75202988ec9'} | {'https://github.com/hhurz/tableexport.jquery.plugin/commit/dcbaee23cf98328397a153e71556f75202988ec9'} |
GHSA | GHSA-m6wg-2mwg-4rfq | Use After Free | The proglottis Go wrapper before 0.1.1 for the GPGME library has a use-after-free, as demonstrated by use for container image pulls by Docker or CRI-O. This leads to a crash or potential code execution during GPG signature verification. | {'CVE-2020-8945'} | 2021-05-18T15:29:42Z | 2021-05-18T15:29:42Z | HIGH | 7.5 | {'CWE-416'} | {'https://github.com/advisories/GHSA-m6wg-2mwg-4rfq', 'https://access.redhat.com/errata/RHSA-2020:0689', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WXV7NZELYWRRCXATXU3FYD3G3WJT3WYM/', 'https://github.com/proglottis/gpgme/commit/92153bcb59bd2f511e502262c46c7bd660e21733', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8945', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3SOCLOPTSYABTE4CLTSPDIFE6ZZZR4LX/', 'https://github.com/containers/image/commit/4c7a23f82ef09127b0ff28366d1cf31316dd6cc1', 'https://access.redhat.com/errata/RHSA-2020:0679', 'https://access.redhat.com/errata/RHSA-2020:0697', 'https://bugzilla.redhat.com/show_bug.cgi?id=1795838', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KDBT77KV3U7BESJX3P4S4MPVDGRTAQA2/', 'https://github.com/proglottis/gpgme/pull/23', 'https://github.com/proglottis/gpgme/compare/v0.1.0...v0.1.1', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/H6P6SSNKN4H6GSEVROHBDXA64PX7EOED/'} | null | {'https://github.com/proglottis/gpgme/commit/92153bcb59bd2f511e502262c46c7bd660e21733', 'https://github.com/containers/image/commit/4c7a23f82ef09127b0ff28366d1cf31316dd6cc1'} | {'https://github.com/containers/image/commit/4c7a23f82ef09127b0ff28366d1cf31316dd6cc1', 'https://github.com/proglottis/gpgme/commit/92153bcb59bd2f511e502262c46c7bd660e21733'} |
GHSA | GHSA-9c4x-5hgq-q3wh | Instance config inline secret exposure in Grafana | ### Impact
Some inline secrets are exposed in plaintext over the Grafana Agent HTTP server:
* Inline secrets for metrics instance configs in the base YAML file are exposed at `/-/config`
* Inline secrets for integrations are exposed at `/-/config`
* Inline secrets for Consul ACL tokens and ETCD basic auth when configured for the scraping service at `/-/config`.
* Inline secrets for the Kafka receiver for OpenTelemetry-Collector tracing at `/-/config`.
* Inline secrets for metrics instance configs loaded from the scraping service are exposed at `/agent/api/v1/configs/{name}`.
Inline secrets will be exposed to anyone being able to reach these endpoints.
Secrets found in these sections are used for:
* Delivering metrics to a Prometheus Remote Write system
* Authenticating against a system for discovering Prometheus targets
* Authenticating against a system for collecting metrics (scrape_configs and integrations)
* Authenticating against a Consul or ETCD for storing configurations to distribute in scraping service mode
* Authenticating against Kafka for receiving traces
Non-inlined secrets, such as `*_file`-based secrets, are not impacted by this vulnerability.
### Patches
Download [v0.20.1](https://github.com/grafana/agent/releases/tag/v0.20.1) or any version past [v0.21.2](https://github.com/grafana/agent/releases/tag/v0.21.2) to patch Grafana Agent. These patches obfuscate the listed impacted secrets from the vulnerable endpoints.
The patches also disable the endpoints by default. Pass the command-line flag `--config.enable-read-api` to opt-in and re-enable the endpoints.
### Workarounds
If for some reason you cannot upgrade, use non-inline secrets where possible. Not all configuration options may have a non-inline equivalent.
You also may desire to restrict API access to Grafana Agent, with some combination of:
* Restrict network interfaces Grafana Agent listens on through `http_listen_address` in the `server` block. `127.0.0.1` is the most restrictive, `0.0.0.0` is the default.
* Configure Grafana Agent to use HTTPS with client authentication.
* Use firewall rules to restrict external access to Grafana Agent's API. | {'CVE-2021-41090'} | 2022-04-01T20:13:45Z | 2021-12-08T19:52:40Z | MODERATE | 6.5 | {'CWE-200', 'CWE-312'} | {'https://github.com/advisories/GHSA-9c4x-5hgq-q3wh', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41090', 'https://github.com/grafana/agent/releases/tag/v0.21.2', 'https://github.com/grafana/agent/commit/af7fb01e31fe2d389e5f1c36b399ddc46b412b21', 'https://github.com/grafana/agent/pull/1152', 'https://security.netapp.com/advisory/ntap-20211229-0004/', 'https://github.com/grafana/agent/releases/tag/v0.20.1', 'https://github.com/grafana/agent/security/advisories/GHSA-9c4x-5hgq-q3wh', 'https://github.com/grafana/agent/commit/a5479755e946e5c7cddb793ee9adda8f5692ba11'} | null | {'https://github.com/grafana/agent/commit/af7fb01e31fe2d389e5f1c36b399ddc46b412b21', 'https://github.com/grafana/agent/commit/a5479755e946e5c7cddb793ee9adda8f5692ba11'} | {'https://github.com/grafana/agent/commit/af7fb01e31fe2d389e5f1c36b399ddc46b412b21', 'https://github.com/grafana/agent/commit/a5479755e946e5c7cddb793ee9adda8f5692ba11'} |
GHSA | GHSA-h4hr-7fg3-h35w | Denial of service in prismjs | The package prismjs before 1.23.0 are vulnerable to Regular Expression Denial of Service (ReDoS) via the prism-asciidoc, prism-rest, prism-tap and prism-eiffel components. | {'CVE-2021-23341'} | 2021-03-01T19:52:33Z | 2021-03-01T19:52:33Z | HIGH | 0 | {'CWE-400'} | {'https://github.com/advisories/GHSA-h4hr-7fg3-h35w', 'https://github.com/PrismJS/prism/commit/c2f6a64426f44497a675cb32dccb079b3eff1609', 'https://github.com/PrismJS/prism/pull/2584', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARS-1076583', 'https://www.npmjs.com/package/prismjs', 'https://snyk.io/vuln/SNYK-JS-PRISMJS-1076581', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23341', 'https://github.com/PrismJS/prism/issues/2583', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1076582'} | null | {'https://github.com/PrismJS/prism/commit/c2f6a64426f44497a675cb32dccb079b3eff1609'} | {'https://github.com/PrismJS/prism/commit/c2f6a64426f44497a675cb32dccb079b3eff1609'} |
GHSA | GHSA-xxq4-3742-3h28 | Generation of Error Message Containing Sensitive Information in microweber | microweber version 1.2.10 and prior may generate an error message containing sensitive information. | {'CVE-2022-0504'} | 2022-02-10T22:12:48Z | 2022-02-09T00:00:31Z | MODERATE | 6.5 | {'CWE-209'} | {'https://huntr.dev/bounties/285ff8a0-a273-4d62-ba01-3e4b4e18467b', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0504', 'https://github.com/microweber/microweber/commit/e607e5f745cd99d5c06a7fce16b3577fab8e1250', 'https://github.com/advisories/GHSA-xxq4-3742-3h28'} | null | {'https://github.com/microweber/microweber/commit/e607e5f745cd99d5c06a7fce16b3577fab8e1250'} | {'https://github.com/microweber/microweber/commit/e607e5f745cd99d5c06a7fce16b3577fab8e1250'} |
GHSA | GHSA-p3hc-fv2j-rp68 | Prototype Pollution in swiper | Versions of the package swiper before 6.5.1 are susceptible to prototype pollution. | {'CVE-2021-23370'} | 2021-05-10T15:36:30Z | 2021-05-10T15:36:30Z | CRITICAL | 9.8 | {'CWE-1321'} | {'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1244696', 'https://snyk.io/vuln/SNYK-JS-SWIPER-1088062', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23370', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARS-1244698', 'https://github.com/nolimits4web/swiper/commit/9dad2739b7474f383474773d5ab898a0c29ac178', 'https://github.com/nolimits4web/Swiper/commit/ec358deab79a8cd2529465f07a0ead5dbcc264ad', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBNOLIMITS4WEB-1244697', 'https://github.com/advisories/GHSA-p3hc-fv2j-rp68', 'https://github.com/nolimits4web/swiper/blob/master/CHANGELOG.md#651-2021-03-29', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-1244699'} | null | {'https://github.com/nolimits4web/Swiper/commit/ec358deab79a8cd2529465f07a0ead5dbcc264ad', 'https://github.com/nolimits4web/swiper/commit/9dad2739b7474f383474773d5ab898a0c29ac178'} | {'https://github.com/nolimits4web/swiper/commit/9dad2739b7474f383474773d5ab898a0c29ac178', 'https://github.com/nolimits4web/Swiper/commit/ec358deab79a8cd2529465f07a0ead5dbcc264ad'} |
GHSA | GHSA-mr7p-25v2-35wr | Path Traversal in nltk | NLTK Downloader before 3.4.5 is vulnerable to a directory traversal, allowing attackers to write arbitrary files via a ../ (dot dot slash) in an NLTK package (ZIP archive) that is mishandled during extraction. | {'CVE-2019-14751'} | 2021-08-17T22:10:30Z | 2019-08-23T21:53:51Z | HIGH | 7.5 | {'CWE-22'} | {'http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00001.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QI4IJGLZQ5S7C5LNRNROHAO2P526XE3D/', 'https://github.com/mssalvatore/CVE-2019-14751_PoC', 'https://github.com/nltk/nltk/blob/3.4.5/ChangeLog', 'https://github.com/advisories/GHSA-mr7p-25v2-35wr', 'https://github.com/nltk/nltk/commit/f59d7ed8df2e0e957f7f247fe218032abdbe9a10', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZGZSSEJH7RHH3RBUEVWWYT75QU67J7SE/', 'http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00054.html', 'https://salvatoresecurity.com/zip-slip-in-nltk-cve-2019-14751/', 'https://nvd.nist.gov/vuln/detail/CVE-2019-14751'} | null | {'https://github.com/nltk/nltk/commit/f59d7ed8df2e0e957f7f247fe218032abdbe9a10'} | {'https://github.com/nltk/nltk/commit/f59d7ed8df2e0e957f7f247fe218032abdbe9a10'} |
GHSA | GHSA-r5fx-8r73-v86c | Cross-Site Scripting in angular | Versions of `angular` prior to 1.5.0-beta.1 are vulnerable to Cross-Site Scripting. The package fails to sanitize `xlink:href` attributes, which may allow attackers to execute arbitrary JavaScript in a victim's browser if the value is user-controlled.
## Recommendation
Upgrade to version 1.5.0-beta.1 or later. | {'CVE-2019-14863'} | 2021-08-19T17:14:00Z | 2020-02-14T23:08:49Z | MODERATE | 6.1 | {'CWE-79'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-14863', 'https://github.com/angular/angular.js/pull/12524', 'https://github.com/angular/angular.js/commit/f33ce173c90736e349cf594df717ae3ee41e0f7a', 'https://github.com/angular/angular.js/commit/35a21532b73d5bd84b4325211c563e6a3e2dde82', 'https://nvd.nist.gov/vuln/detail/CVE-2019-14863', 'https://www.npmjs.com/advisories/1453', 'https://snyk.io/vuln/npm:angular:20150807', 'https://github.com/advisories/GHSA-r5fx-8r73-v86c'} | null | {'https://github.com/angular/angular.js/commit/f33ce173c90736e349cf594df717ae3ee41e0f7a', 'https://github.com/angular/angular.js/commit/35a21532b73d5bd84b4325211c563e6a3e2dde82'} | {'https://github.com/angular/angular.js/commit/35a21532b73d5bd84b4325211c563e6a3e2dde82', 'https://github.com/angular/angular.js/commit/f33ce173c90736e349cf594df717ae3ee41e0f7a'} |
GHSA | GHSA-7mqr-2v3q-v2wm | Ignored errors on token revokation in github.com/ory/fosite | ### Impact
The `TokenRevocationHandler` ignores errors coming from the storage. This can lead to unexpected 200 status codes indicating successful revocation while the token is still valid. Whether an attacker can use this for her advantage depends on the ability to trigger errors in the store.
### References
[RFC 7009](https://tools.ietf.org/html/rfc7009#section-2.2.1) states that a 503 HTTP code must be returned when the server has a problem. | {'CVE-2020-15223'} | 2022-04-19T19:02:34Z | 2021-05-24T16:57:39Z | HIGH | 8 | {'CWE-755'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15223', 'https://github.com/ory/fosite/security/advisories/GHSA-7mqr-2v3q-v2wm', 'https://tools.ietf.org/html/rfc7009#section-2.2.1', 'https://github.com/ory/fosite/commit/03dd55813f5521985f7dd64277b7ba0cf1441319', 'https://github.com/advisories/GHSA-7mqr-2v3q-v2wm'} | null | {'https://github.com/ory/fosite/commit/03dd55813f5521985f7dd64277b7ba0cf1441319'} | {'https://github.com/ory/fosite/commit/03dd55813f5521985f7dd64277b7ba0cf1441319'} |
GHSA | GHSA-468q-v4jj-485h | Inefficient Regular Expression Complexity in taro | taro is vulnerable to Inefficient Regular Expression Complexity | {'CVE-2021-3804'} | 2021-09-20T20:09:59Z | 2021-09-20T20:09:59Z | HIGH | 7.5 | {'CWE-1333'} | {'https://github.com/advisories/GHSA-468q-v4jj-485h', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3804', 'https://github.com/nervjs/taro/commit/acadb6c826ba57f2030a626f1de4f7b4608fcdb5', 'https://huntr.dev/bounties/0ebe85e6-cc85-42b8-957e-18d8df277414'} | null | {'https://github.com/nervjs/taro/commit/acadb6c826ba57f2030a626f1de4f7b4608fcdb5'} | {'https://github.com/nervjs/taro/commit/acadb6c826ba57f2030a626f1de4f7b4608fcdb5'} |
GHSA | GHSA-rjmf-p882-645m | Improper Certificate Validation | A specific version of the Node.js mongodb-client-encryption module does not perform correct validation of the KMS server’s certificate. This vulnerability in combination with a privileged network position active MITM attack could result in interception of traffic between the Node.js driver and the KMS service rendering client-side field level encryption (CSFLE) ineffective. This issue was discovered during internal testing and affects mongodb-client-encryption module version 1.2.0, which was available from 2021-Jan-29 and deprecated in the NPM Registry on 2021-Feb-04. This vulnerability does not impact driver traffic payloads with CSFLE-supported key services from applications residing inside the AWS, GCP, and Azure nework fabrics due to compensating controls in these environments. This issue does not impact driver workloads that don’t use Field Level Encryption. | {'CVE-2021-20327'} | 2021-04-12T18:51:17Z | 2021-04-12T18:51:17Z | MODERATE | 6.8 | {'CWE-295'} | {'https://jira.mongodb.org/browse/NODE-3125', 'https://nvd.nist.gov/vuln/detail/CVE-2021-20327', 'https://github.com/advisories/GHSA-rjmf-p882-645m', 'https://github.com/mongodb/libmongocrypt/commit/76365515ff8754b9f705e56428dd0d7efa7f541b', 'https://www.npmjs.com/advisories/1660'} | null | {'https://github.com/mongodb/libmongocrypt/commit/76365515ff8754b9f705e56428dd0d7efa7f541b'} | {'https://github.com/mongodb/libmongocrypt/commit/76365515ff8754b9f705e56428dd0d7efa7f541b'} |
GHSA | GHSA-862g-9h5m-m3qv | coreos-installer < 0.10.0 writes world-readable Ignition config to installed system | ### Impact
On systems installed with coreos-installer before 0.10.0, the user-provided Ignition config was written to `/boot/ignition/config.ign` with world-readable permissions, granting unprivileged users access to any secrets included in the config.
Default configurations of Fedora CoreOS and RHEL CoreOS do not include any unprivileged user accounts. In addition, instances launched from a cloud image, and systems provisioned with the `ignition.config.url` kernel argument, do not use the `config.ign` file and are unaffected.
### Patches
coreos-installer 0.10.0 and later [writes](https://github.com/coreos/coreos-installer/pull/571) the Ignition config with restricted permissions.
### Workarounds
On Fedora CoreOS systems installed from version 34.20210711.3.0 (stable), 34.20210711.2.0 (testing), 34.20210711.1.1 (next) and later, the `/boot/ignition` directory and its contents are removed after provisioning is complete. All Fedora CoreOS systems that have updated to these versions or later have automatically removed the `/boot/ignition` directory and no action is required.
On other systems, `/boot/ignition/config.ign` can be removed manually, as it is not used after provisioning is complete:
```
sudo mount -o remount,rw /boot
sudo rm -rf /boot/ignition
```
### References
For more information, see https://github.com/coreos/fedora-coreos-tracker/issues/889.
### For more information
If you have any questions or comments about this advisory, [open an issue in coreos-installer](https://github.com/coreos/coreos-installer/issues/new/choose) or email the CoreOS [development mailing list](https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org/). | {'CVE-2021-3917'} | 2022-04-19T19:03:13Z | 2021-11-08T18:01:13Z | LOW | 0 | null | {'https://github.com/coreos/coreos-installer/releases/tag/v0.10.0', 'https://github.com/advisories/GHSA-862g-9h5m-m3qv', 'https://github.com/coreos/coreos-installer/security/advisories/GHSA-862g-9h5m-m3qv', 'https://github.com/coreos/coreos-installer/commit/2a36405339c87b16ed6c76e91ad5b76638fbdb0c'} | null | {'https://github.com/coreos/coreos-installer/commit/2a36405339c87b16ed6c76e91ad5b76638fbdb0c'} | {'https://github.com/coreos/coreos-installer/commit/2a36405339c87b16ed6c76e91ad5b76638fbdb0c'} |
GHSA | GHSA-g8j6-m4p7-5rfq | High severity vulnerability that affects DotNetNuke.Core | DNN (aka DotNetNuke) before 9.2.0 suffers from a Server-Side Request Forgery (SSRF) vulnerability in the DnnImageHandler class. Attackers may be able to access information about internal network resources. | {'CVE-2017-0929'} | 2021-09-10T20:29:40Z | 2018-10-16T17:18:12Z | HIGH | 7.5 | {'CWE-918'} | {'https://github.com/dnnsoftware/Dnn.Platform/commit/d3953db85fee77bb5e6383747692c507ef8b94c3', 'https://github.com/advisories/GHSA-g8j6-m4p7-5rfq', 'https://nvd.nist.gov/vuln/detail/CVE-2017-0929'} | null | {'https://github.com/dnnsoftware/Dnn.Platform/commit/d3953db85fee77bb5e6383747692c507ef8b94c3'} | {'https://github.com/dnnsoftware/Dnn.Platform/commit/d3953db85fee77bb5e6383747692c507ef8b94c3'} |
GHSA | GHSA-3rhm-67j6-42jq | Moderate severity vulnerability that affects com.jason-goodwin:authentikat-jwt_2.12 | A time-sensitive equality check on the JWT signature in the JsonWebToken.validate method in main/scala/authentikat/jwt/JsonWebToken.scala in authentikat-jwt (aka com.jason-goodwin/authentikat-jwt) version 0.4.5 and earlier allows the supplier of a JWT token to guess bit after bit of the signature by repeating validation requests. | {'CVE-2017-18239'} | 2021-08-31T21:23:38Z | 2018-11-09T17:50:40Z | CRITICAL | 9.8 | null | {'https://github.com/jasongoodwin/authentikat-jwt/commit/2d2fa0d40ac8f2f7aa7e9b070fa1a25eee082cb0', 'https://github.com/jasongoodwin/authentikat-jwt/issues/12', 'https://github.com/jasongoodwin/authentikat-jwt/pull/36', 'https://nvd.nist.gov/vuln/detail/CVE-2017-18239', 'https://github.com/advisories/GHSA-3rhm-67j6-42jq'} | null | {'https://github.com/jasongoodwin/authentikat-jwt/commit/2d2fa0d40ac8f2f7aa7e9b070fa1a25eee082cb0'} | {'https://github.com/jasongoodwin/authentikat-jwt/commit/2d2fa0d40ac8f2f7aa7e9b070fa1a25eee082cb0'} |
GHSA | GHSA-rh4p-g7x6-8pqg | Out-of-bounds write | A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1092, CVE-2019-1103, CVE-2019-1106, CVE-2019-1107. | {'CVE-2019-1062'} | 2021-03-29T20:59:09Z | 2021-03-29T20:59:09Z | HIGH | 7.5 | {'CWE-787'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-1062', 'https://github.com/chakra-core/ChakraCore/commit/7f0d390ad77d838cbb81d4586c83ec822f384ce8', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1062', 'https://github.com/chakra-core/ChakraCore/commit/75162b7f2d8ac2b37d17564e9c979ba1bae707e8', 'https://github.com/advisories/GHSA-rh4p-g7x6-8pqg'} | null | {'https://github.com/chakra-core/ChakraCore/commit/75162b7f2d8ac2b37d17564e9c979ba1bae707e8', 'https://github.com/chakra-core/ChakraCore/commit/7f0d390ad77d838cbb81d4586c83ec822f384ce8'} | {'https://github.com/chakra-core/ChakraCore/commit/75162b7f2d8ac2b37d17564e9c979ba1bae707e8', 'https://github.com/chakra-core/ChakraCore/commit/7f0d390ad77d838cbb81d4586c83ec822f384ce8'} |
GHSA | GHSA-wpfr-6297-9v57 | User object created with invalid provider data in GoTrue | ### Impact
_What kind of vulnerability is it? Who is impacted?_
Under certain circumstances a valid user object would have been created with invalid provider metadata.
This vulnerability affects everyone running an instance of GoTrue as a service. We advise you to update especially if you are using the provider metadata from the user object to secure other resources.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
A patch is available with the release of version [1.0.1 on Github](https://github.com/netlify/gotrue/releases/tag/v1.0.1).
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
If you don't rely on the provider metadata in the user object, you might not be affected. We still strongly recommend upgrading.
### References
_Are there any links users can visit to find out more?_
This problem was initially found and reported by the team at Supabase: https://github.com/supabase/gotrue/security/advisories/GHSA-5hvv-9cqv-894r. We want to thank them for the cooperation around this report.
In contrast to their advisory, we decided to set the severity to "Moderate" since the provider metadata is not an inherent security feature of this GoTrue codebase or the Netlify ecosystem.
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@netlify.com](mailto:security@netlify.com)
| null | 2022-02-11T21:52:12Z | 2022-02-09T22:29:01Z | MODERATE | 0 | null | {'https://github.com/netlify/gotrue/releases/tag/v1.0.1', 'https://github.com/netlify/gotrue/commit/4d8a3b39fe485a5f83c70617d594be01130c5b83', 'https://github.com/netlify/gotrue/pull/313', 'https://github.com/advisories/GHSA-wpfr-6297-9v57', 'https://github.com/netlify/gotrue/security/advisories/GHSA-wpfr-6297-9v57'} | null | {'https://github.com/netlify/gotrue/commit/4d8a3b39fe485a5f83c70617d594be01130c5b83'} | {'https://github.com/netlify/gotrue/commit/4d8a3b39fe485a5f83c70617d594be01130c5b83'} |
GHSA | GHSA-3c33-3465-fhx2 | Exposure of Resource to Wrong Sphere in LibreNMS | An issue was discovered in LibreNMS before 1.65.1. It has insufficient access control for normal users because of "'guard' => 'admin'" instead of "'middleware' => ['can:admin']" in routes/web.php. | {'CVE-2020-15877'} | 2021-09-08T17:27:17Z | 2021-09-08T17:27:16Z | HIGH | 8.8 | {'CWE-668'} | {'https://github.com/advisories/GHSA-3c33-3465-fhx2', 'https://github.com/librenms/librenms/commit/e5bb6d80bc308fc56b9a01ffb76c34159995353c', 'https://github.com/librenms/librenms/releases/tag/1.65.1', 'https://github.com/librenms/librenms/compare/1.65...1.65.1', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15877', 'https://github.com/librenms/librenms/pull/11915', 'https://community.librenms.org/c/announcements', 'https://shielder.it/blog'} | null | {'https://github.com/librenms/librenms/commit/e5bb6d80bc308fc56b9a01ffb76c34159995353c'} | {'https://github.com/librenms/librenms/commit/e5bb6d80bc308fc56b9a01ffb76c34159995353c'} |
GHSA | GHSA-xmq7-7fxm-rr79 | Denial of Service in Tensorflow | ### Impact
By controlling the `fill` argument of [`tf.strings.as_string`](https://www.tensorflow.org/api_docs/python/tf/strings/as_string), a malicious attacker is able to trigger a format string vulnerability due to the way the internal format use in a `printf` call is constructed: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/as_string_op.cc#L68-L74
This can result in unexpected output:
```python
In [1]: tf.strings.as_string(input=[1234], width=6, fill='-')
Out[1]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['1234 '], dtype=object)>
In [2]: tf.strings.as_string(input=[1234], width=6, fill='+')
Out[2]: <tf.Tensor: shape=(1,), dtype=string, numpy=array([' +1234'], dtype=object)>
In [3]: tf.strings.as_string(input=[1234], width=6, fill="h")
Out[3]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['%6d'], dtype=object)>
In [4]: tf.strings.as_string(input=[1234], width=6, fill="d")
Out[4]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['12346d'], dtype=object)>
In [5]: tf.strings.as_string(input=[1234], width=6, fill="o")
Out[5]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['23226d'], dtype=object)>
In [6]: tf.strings.as_string(input=[1234], width=6, fill="x")
Out[6]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['4d26d'], dtype=object)>
In [7]: tf.strings.as_string(input=[1234], width=6, fill="g")
Out[7]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['8.67458e-3116d'], dtype=object)>
In [8]: tf.strings.as_string(input=[1234], width=6, fill="a")
Out[8]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['0x0.00ff7eebb4d4p-10226d'], dtype=object)>
In [9]: tf.strings.as_string(input=[1234], width=6, fill="c")
Out[9]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['\xd26d'], dtype=object)>
In [10]: tf.strings.as_string(input=[1234], width=6, fill="p")
Out[10]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['0x4d26d'], dtype=object)>
In [11]: tf.strings.as_string(input=[1234], width=6, fill='m')
Out[11]: <tf.Tensor: shape=(1,), dtype=string, numpy=array(['Success6d'], dtype=object)>
```
However, passing in `n` or `s` results in segmentation fault.
### Patches
We have patched the issue in 33be22c65d86256e6826666662e40dbdfe70ee83 and will release patch releases for all versions between 1.15 and 2.3.
We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2020-15203'} | 2021-11-19T15:18:24Z | 2020-09-25T18:28:37Z | HIGH | 7.5 | {'CWE-20', 'CWE-134'} | {'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html', 'https://github.com/tensorflow/tensorflow/commit/33be22c65d86256e6826666662e40dbdfe70ee83', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15203', 'https://github.com/advisories/GHSA-xmq7-7fxm-rr79', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-xmq7-7fxm-rr79', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1'} | null | {'https://github.com/tensorflow/tensorflow/commit/33be22c65d86256e6826666662e40dbdfe70ee83'} | {'https://github.com/tensorflow/tensorflow/commit/33be22c65d86256e6826666662e40dbdfe70ee83'} |
GHSA | GHSA-455w-gv5p-wgg3 | Cross-site Scripting in pimcore | pimcore is vulnerable to Stored XSS at Name field in the setting tab of the Global Targeting Rules. | {'CVE-2022-0260'} | 2022-01-26T22:10:48Z | 2022-01-26T22:10:48Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/pimcore/pimcore/pull/11205', 'https://github.com/pimcore/pimcore/commit/665976327ad3c2c87efa2a5a64d696032c0a8109', 'https://huntr.dev/bounties/89e4ab60-21ec-4396-92ad-5b78d4c2897e', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0260', 'https://github.com/advisories/GHSA-455w-gv5p-wgg3'} | null | {'https://github.com/pimcore/pimcore/commit/665976327ad3c2c87efa2a5a64d696032c0a8109'} | {'https://github.com/pimcore/pimcore/commit/665976327ad3c2c87efa2a5a64d696032c0a8109'} |
GHSA | GHSA-4574-qv3w-fcmg | Deserialization of Untrusted Data in codeception/codeception | This affects the package codeception/codeception from 4.0.0 before 4.1.22 and before 3.1.3. The RunProcess class can be leveraged as a gadget to run arbitrary commands on a system that is deserializing user input without validation. | {'CVE-2021-23420'} | 2021-09-01T18:36:15Z | 2021-09-01T18:36:15Z | CRITICAL | 9.8 | {'CWE-502'} | {'https://github.com/Codeception/Codeception/commit/802a108057d250ee563120eaa5365a519afc0a71', 'https://github.com/Codeception/Codeception/commit/cbce9ea7f4664052fa1ac6b36f5b5a6dbd864d71', 'https://github.com/Codeception/Codeception/blob/4.1/ext/RunProcess.php#L52', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23420', 'https://github.com/Codeception/Codeception/blob/4.1/CHANGELOG-4.x.md#4122', 'https://snyk.io/vuln/SNYK-PHP-CODECEPTIONCODECEPTION-1324585', 'https://github.com/JinYiTong/poc', 'https://github.com/Codeception/Codeception/pull/6241', 'https://github.com/advisories/GHSA-4574-qv3w-fcmg'} | null | {'https://github.com/Codeception/Codeception/commit/802a108057d250ee563120eaa5365a519afc0a71', 'https://github.com/Codeception/Codeception/commit/cbce9ea7f4664052fa1ac6b36f5b5a6dbd864d71'} | {'https://github.com/Codeception/Codeception/commit/cbce9ea7f4664052fa1ac6b36f5b5a6dbd864d71', 'https://github.com/Codeception/Codeception/commit/802a108057d250ee563120eaa5365a519afc0a71'} |
GHSA | GHSA-hh7m-rx4f-4vpv | CSRF can expose users authentication token | ### Issue
The /login and /change endpoints can return the authenticated user's authentication token in response to a GET request. Since GET requests aren't protected with a CSRF token, this could lead to a malicious 3rd party site acquiring the authentication token.
### Patches
Version 3.4.5 and soon to be released 4.0.0 are patched.
### Workarounds
If you aren't using authentication tokens - you can set the SECURITY_TOKEN_MAX_AGE to "0" (seconds) which should make the token unusable.
### References
None | {'CVE-2021-21241'} | 2021-01-13T19:29:09Z | 2021-01-11T20:38:28Z | HIGH | 0 | {'CWE-352'} | {'https://github.com/Flask-Middleware/flask-security/security/advisories/GHSA-hh7m-rx4f-4vpv', 'https://github.com/Flask-Middleware/flask-security/commit/6d50ee9169acf813257c37b75babe9c28e83542a', 'https://github.com/Flask-Middleware/flask-security/releases/tag/3.4.5', 'https://github.com/Flask-Middleware/flask-security/commit/61d313150b5f620d0b800896c4f2199005e84b1f', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21241', 'https://github.com/advisories/GHSA-hh7m-rx4f-4vpv', 'https://github.com/Flask-Middleware/flask-security/pull/422', 'https://pypi.org/project/Flask-Security-Too'} | null | {'https://github.com/Flask-Middleware/flask-security/commit/61d313150b5f620d0b800896c4f2199005e84b1f', 'https://github.com/Flask-Middleware/flask-security/commit/6d50ee9169acf813257c37b75babe9c28e83542a'} | {'https://github.com/Flask-Middleware/flask-security/commit/61d313150b5f620d0b800896c4f2199005e84b1f', 'https://github.com/Flask-Middleware/flask-security/commit/6d50ee9169acf813257c37b75babe9c28e83542a'} |
GHSA | GHSA-v5jg-558j-q67c | Moderate severity vulnerability that affects actionpack | Cross-site scripting (XSS) vulnerability in the strip_tags helper in actionpack/lib/action_controller/vendor/html-scanner/html/node.rb in Ruby on Rails before 2.3.13, 3.0.x before 3.0.10, and 3.1.x before 3.1.0.rc5 allows remote attackers to inject arbitrary web script or HTML via a tag with an invalid name. | {'CVE-2011-2931'} | 2021-09-20T15:11:54Z | 2017-10-24T18:33:38Z | MODERATE | 0 | {'CWE-79'} | {'http://www.openwall.com/lists/oss-security/2011/08/19/11', 'http://lists.fedoraproject.org/pipermail/package-announce/2011-September/065137.html', 'https://nvd.nist.gov/vuln/detail/CVE-2011-2931', 'http://www.debian.org/security/2011/dsa-2301', 'http://www.openwall.com/lists/oss-security/2011/08/22/5', 'https://github.com/rails/rails/commit/586a944ddd4d03e66dea1093306147594748037a', 'https://github.com/advisories/GHSA-v5jg-558j-q67c', 'http://lists.fedoraproject.org/pipermail/package-announce/2011-September/065212.html', 'http://secunia.com/advisories/45921', 'http://www.openwall.com/lists/oss-security/2011/08/20/1', 'http://lists.fedoraproject.org/pipermail/package-announce/2011-September/065109.html', 'http://weblog.rubyonrails.org/2011/8/16/ann-rails-3-1-0-rc6', 'http://www.openwall.com/lists/oss-security/2011/08/22/13', 'http://www.openwall.com/lists/oss-security/2011/08/22/14', 'http://groups.google.com/group/rubyonrails-security/msg/fd41ab62966e0fd1?dmode=source&output=gplain', 'https://bugzilla.redhat.com/show_bug.cgi?id=731436', 'http://www.openwall.com/lists/oss-security/2011/08/17/1'} | null | {'https://github.com/rails/rails/commit/586a944ddd4d03e66dea1093306147594748037a'} | {'https://github.com/rails/rails/commit/586a944ddd4d03e66dea1093306147594748037a'} |
GHSA | GHSA-jmgf-p46x-982h | Moderate severity vulnerability that affects rails | CRLF injection vulnerability in Ruby on Rails before 2.0.5 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via a crafted URL to the redirect_to function. | {'CVE-2008-5189'} | 2021-09-14T19:47:41Z | 2017-10-24T18:33:38Z | MODERATE | 0 | {'CWE-352'} | {'http://github.com/rails/rails/commit/7282ed863ca7e6f928bae9162c9a63a98775a19d', 'http://weblog.rubyonrails.org/2008/10/19/rails-2-0-5-redirect_to-and-offset-limit-sanitizing', 'https://github.com/advisories/GHSA-jmgf-p46x-982h', 'https://nvd.nist.gov/vuln/detail/CVE-2008-5189', 'http://lists.opensuse.org/opensuse-security-announce/2008-12/msg00002.html', 'http://www.securityfocus.com/bid/32359', 'http://weblog.rubyonrails.org/2008/10/19/response-splitting-risk'} | null | {'http://github.com/rails/rails/commit/7282ed863ca7e6f928bae9162c9a63a98775a19d'} | {'http://github.com/rails/rails/commit/7282ed863ca7e6f928bae9162c9a63a98775a19d'} |
GHSA | GHSA-9fh3-vh3h-q4g3 | Moderate severity vulnerability that affects activesupport | Cross-site scripting (XSS) vulnerability in activesupport/lib/active_support/core_ext/string/output_safety.rb in Ruby on Rails 2.x before 2.3.13, 3.0.x before 3.0.10, and 3.1.x before 3.1.0.rc5 allows remote attackers to inject arbitrary web script or HTML via a malformed Unicode string, related to a "UTF-8 escaping vulnerability." | {'CVE-2011-2932'} | 2021-09-07T21:32:10Z | 2017-10-24T18:33:38Z | MODERATE | 0 | {'CWE-79'} | {'https://github.com/rails/rails/commit/bfc432574d0b141fd7fe759edfe9b6771dd306bd', 'http://www.openwall.com/lists/oss-security/2011/08/19/11', 'https://bugzilla.redhat.com/show_bug.cgi?id=731435', 'http://lists.fedoraproject.org/pipermail/package-announce/2011-September/065212.html', 'http://www.openwall.com/lists/oss-security/2011/08/17/1', 'http://www.openwall.com/lists/oss-security/2011/08/20/1', 'http://groups.google.com/group/rubyonrails-security/msg/f1d2749773db9f21?dmode=source&output=gplain', 'https://github.com/advisories/GHSA-9fh3-vh3h-q4g3', 'http://weblog.rubyonrails.org/2011/8/16/ann-rails-3-1-0-rc6', 'http://lists.fedoraproject.org/pipermail/package-announce/2011-September/065189.html', 'http://www.openwall.com/lists/oss-security/2011/08/22/5', 'http://www.openwall.com/lists/oss-security/2011/08/22/13', 'http://lists.fedoraproject.org/pipermail/package-announce/2011-September/065114.html', 'http://www.openwall.com/lists/oss-security/2011/08/22/14', 'https://nvd.nist.gov/vuln/detail/CVE-2011-2932', 'http://secunia.com/advisories/45917'} | null | {'https://github.com/rails/rails/commit/bfc432574d0b141fd7fe759edfe9b6771dd306bd'} | {'https://github.com/rails/rails/commit/bfc432574d0b141fd7fe759edfe9b6771dd306bd'} |
GHSA | GHSA-27qf-jwm8-g7f3 | FPE in LSH in TFLite | ### Impact
An attacker can craft a TFLite model that would trigger a division by zero error in LSH [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/lsh_projection.cc#L118).
```cc
int RunningSignBit(const TfLiteTensor* input, const TfLiteTensor* weight,
float seed) {
int input_item_bytes = input->bytes / SizeOfDimension(input, 0);
// ...
}
```
There is no check that the first dimension of the input is non zero.
### Patches
We have patched the issue in GitHub commit [0575b640091680cfb70f4dd93e70658de43b94f9](https://github.com/tensorflow/tensorflow/commit/0575b640091680cfb70f4dd93e70658de43b94f9).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick thiscommit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Yakun Zhang of Baidu Security. | {'CVE-2021-37691'} | 2021-08-25T14:39:17Z | 2021-08-25T14:39:17Z | MODERATE | 5.5 | {'CWE-369'} | {'https://github.com/tensorflow/tensorflow/commit/0575b640091680cfb70f4dd93e70658de43b94f9', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-27qf-jwm8-g7f3', 'https://github.com/advisories/GHSA-27qf-jwm8-g7f3', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37691'} | null | {'https://github.com/tensorflow/tensorflow/commit/0575b640091680cfb70f4dd93e70658de43b94f9'} | {'https://github.com/tensorflow/tensorflow/commit/0575b640091680cfb70f4dd93e70658de43b94f9'} |
GHSA | GHSA-2q4g-w47c-4674 | Unpreventable top-level navigation | ### Impact
The `will-navigate` event that apps use to prevent navigations to unexpected destinations [as per our security recommendations](https://www.electronjs.org/docs/tutorial/security) can be bypassed when a sub-frame performs a top-frame navigation across sites.
### Patches
* `11.0.0-beta.1`
* `10.0.1`
* `9.3.0`
* `8.5.1`
### Workarounds
Sandbox all your iframes using the [`sandbox` attribute](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe#attr-sandbox). This will prevent them creating top-frame navigations and is good practice anyway.
### For more information
If you have any questions or comments about this advisory:
* Email us at security@electronjs.org | {'CVE-2020-15174'} | 2022-04-19T19:02:34Z | 2020-10-06T14:24:04Z | HIGH | 7.5 | {'CWE-20', 'CWE-693'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15174', 'https://github.com/advisories/GHSA-2q4g-w47c-4674', 'https://github.com/electron/electron/commit/18613925610ba319da7f497b6deed85ad712c59b', 'https://github.com/electron/electron/security/advisories/GHSA-2q4g-w47c-4674'} | null | {'https://github.com/electron/electron/commit/18613925610ba319da7f497b6deed85ad712c59b'} | {'https://github.com/electron/electron/commit/18613925610ba319da7f497b6deed85ad712c59b'} |
GHSA | GHSA-wxc4-f4m6-wwqv | Excessive Platform Resource Consumption within a Loop in Kubernetes | The Kubernetes API Server component in versions 1.1-1.14, and versions prior to 1.15.10, 1.16.7 and 1.17.3 allows an authorized user who sends malicious YAML payloads to cause the kube-apiserver to consume excessive CPU cycles while parsing YAML. | {'CVE-2019-11254'} | 2021-12-20T16:55:06Z | 2021-12-20T16:55:06Z | MODERATE | 6.5 | {'CWE-1050'} | {'https://security.netapp.com/advisory/ntap-20200413-0003/', 'https://github.com/kubernetes/kubernetes/issues/89535', 'https://github.com/go-yaml/yaml/commit/53403b58ad1b561927d19068c655246f2db79d48', 'https://nvd.nist.gov/vuln/detail/CVE-2019-11254', 'https://groups.google.com/d/msg/kubernetes-announce/ALL9s73E5ck/4yHe8J-PBAAJ', 'https://github.com/advisories/GHSA-wxc4-f4m6-wwqv', 'https://github.com/kubernetes/kubernetes/pull/87467/commits/b86df2bec4f377afc0ca03482ffad2f0a49a83b8'} | null | {'https://github.com/kubernetes/kubernetes/pull/87467/commits/b86df2bec4f377afc0ca03482ffad2f0a49a83b8', 'https://github.com/go-yaml/yaml/commit/53403b58ad1b561927d19068c655246f2db79d48'} | {'https://github.com/kubernetes/kubernetes/pull/87467/commits/b86df2bec4f377afc0ca03482ffad2f0a49a83b8', 'https://github.com/go-yaml/yaml/commit/53403b58ad1b561927d19068c655246f2db79d48'} |
GHSA | GHSA-x7rp-74x2-mjf3 | Segfault in Tensorflow | ### Impact
The `RaggedCountSparseOutput` implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the `splits` tensor generate a valid partitioning of the `values` tensor. Thus, the [following code](https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L248-L265
) sets up conditions to cause a heap buffer overflow:
```cc
auto per_batch_counts = BatchedMap<W>(num_batches);
int batch_idx = 0;
for (int idx = 0; idx < num_values; ++idx) {
while (idx >= splits_values(batch_idx)) {
batch_idx++;
}
const auto& value = values_values(idx);
if (value >= 0 && (maxlength_ <= 0 || value < maxlength_)) {
per_batch_counts[batch_idx - 1][value] = 1;
}
}
```
A `BatchedMap` is equivalent to a vector where each element is a hashmap. However, if the first element of `splits_values` is not 0, `batch_idx` will never be 1, hence there will be no hashmap at index 0 in `per_batch_counts`. Trying to access that in the user code results in a segmentation fault.
### Patches
We have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release.
We recommend users to upgrade to TensorFlow 2.3.1.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability is a variant of [GHSA-p5f8-gfw5-33w4](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4) | {'CVE-2020-15200'} | 2021-11-19T15:19:14Z | 2020-09-25T18:28:32Z | MODERATE | 5.9 | {'CWE-20', 'CWE-787', 'CWE-122'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15200', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-x7rp-74x2-mjf3', 'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02', 'https://github.com/advisories/GHSA-x7rp-74x2-mjf3', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1'} | null | {'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02'} | {'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02'} |
GHSA | GHSA-3cqr-58rm-57f8 | Arbitrary Code Execution in Handlebars | Handlebars before 3.0.8 and 4.x before 4.5.3 is vulnerable to Arbitrary Code Execution. The lookup helper fails to properly validate templates, allowing attackers to submit templates that execute arbitrary JavaScript. This can be used to run arbitrary code on a server processing Handlebars templates or in a victim's browser (effectively serving as XSS). | {'CVE-2019-20920'} | 2022-02-10T20:38:19Z | 2022-02-10T20:38:19Z | HIGH | 8.1 | {'CWE-94'} | {'https://www.npmjs.com/advisories/1316', 'https://github.com/advisories/GHSA-3cqr-58rm-57f8', 'https://www.npmjs.com/advisories/1324', 'https://github.com/handlebars-lang/handlebars.js/commit/d54137810a49939fd2ad01a91a34e182ece4528e', 'https://snyk.io/vuln/SNYK-JS-HANDLEBARS-534478', 'https://nvd.nist.gov/vuln/detail/CVE-2019-20920', 'https://www.npmjs.com/package/handlebars'} | null | {'https://github.com/handlebars-lang/handlebars.js/commit/d54137810a49939fd2ad01a91a34e182ece4528e'} | {'https://github.com/handlebars-lang/handlebars.js/commit/d54137810a49939fd2ad01a91a34e182ece4528e'} |
GHSA | GHSA-9qw8-ccq9-ffj9 | Out-of-bounds write | A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1131, CVE-2019-1140, CVE-2019-1141, CVE-2019-1195, CVE-2019-1196, CVE-2019-1197. | {'CVE-2019-1139'} | 2021-03-29T20:57:53Z | 2021-03-29T20:57:53Z | HIGH | 7.5 | {'CWE-787'} | {'https://github.com/chakra-core/ChakraCore/commit/ae8a8d9644e677a9878e5dd7824d4b876454e799', 'https://github.com/chakra-core/ChakraCore/commit/6b1250b6ffea7006226dd937e52cf5b353fcfc15', 'https://nvd.nist.gov/vuln/detail/CVE-2019-1139', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1139', 'https://github.com/advisories/GHSA-9qw8-ccq9-ffj9'} | null | {'https://github.com/chakra-core/ChakraCore/commit/ae8a8d9644e677a9878e5dd7824d4b876454e799', 'https://github.com/chakra-core/ChakraCore/commit/6b1250b6ffea7006226dd937e52cf5b353fcfc15'} | {'https://github.com/chakra-core/ChakraCore/commit/ae8a8d9644e677a9878e5dd7824d4b876454e799', 'https://github.com/chakra-core/ChakraCore/commit/6b1250b6ffea7006226dd937e52cf5b353fcfc15'} |
GHSA | GHSA-hggx-3h72-49ww | Moderate severity vulnerability that affects Pillow | Buffer overflow in the ImagingLibTiffDecode function in libImaging/TiffDecode.c in Pillow before 3.1.1 allows remote attackers to overwrite memory via a crafted TIFF file. | {'CVE-2016-0740'} | 2021-09-14T17:17:46Z | 2018-07-24T20:03:51Z | MODERATE | 6.5 | {'CWE-119'} | {'https://nvd.nist.gov/vuln/detail/CVE-2016-0740', 'https://security.gentoo.org/glsa/201612-52', 'https://github.com/advisories/GHSA-hggx-3h72-49ww', 'https://github.com/python-pillow/Pillow/commit/6dcbf5bd96b717c58d7b642949da8d323099928e', 'https://github.com/python-pillow/Pillow/blob/c3cb690fed5d4bf0c45576759de55d054916c165/CHANGES.rst', 'http://www.debian.org/security/2016/dsa-3499'} | null | {'https://github.com/python-pillow/Pillow/commit/6dcbf5bd96b717c58d7b642949da8d323099928e'} | {'https://github.com/python-pillow/Pillow/commit/6dcbf5bd96b717c58d7b642949da8d323099928e'} |
GHSA | GHSA-hx2x-85gr-wrpq | Out of bounds access in tensorflow-lite | ### Impact
In TensorFlow Lite models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/internal/reference/reference_ops.h#L2625-L2631
Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `output_data` buffer.
This might result in a segmentation fault but it can also be used to further corrupt the memory and can be chained with other vulnerabilities to create more advanced exploits.
### Patches
We have patched the issue in 204945b and will release patch releases for all affected versions.
We recommend users to upgrade to TensorFlow 2.2.1, or 2.3.1.
### Workarounds
A potential workaround would be to add a custom `Verifier` to the model loading code to ensure that the segment ids are all positive, although this only handles the case when the segment ids are stored statically in the model.
A similar validation could be done if the segment ids are generated at runtime between inference steps.
If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been discovered from a variant analysis of [GHSA-p2cq-cprg-frvm](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p2cq-cprg-frvm). | {'CVE-2020-15212'} | 2021-08-26T15:20:18Z | 2020-09-25T18:29:00Z | HIGH | 8.1 | {'CWE-787'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15212', 'https://github.com/tensorflow/tensorflow/commit/204945b19e44b57906c9344c0d00120eeeae178a', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hx2x-85gr-wrpq', 'https://github.com/advisories/GHSA-hx2x-85gr-wrpq', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1'} | null | {'https://github.com/tensorflow/tensorflow/commit/204945b19e44b57906c9344c0d00120eeeae178a'} | {'https://github.com/tensorflow/tensorflow/commit/204945b19e44b57906c9344c0d00120eeeae178a'} |
GHSA | GHSA-xr2c-5w89-63pv | Untrusted Search Path in Poetry | Poetry prior to v1.1.9 was discovered to contain an untrusted search path which causes the application to behave in unexpected ways when users execute Poetry commands in a directory containing malicious content. This vulnerability occurs when the application is ran on Windows OS. | {'CVE-2022-26184'} | 2022-03-30T21:05:22Z | 2022-03-23T00:00:24Z | CRITICAL | 9.8 | {'CWE-426'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-26184', 'https://github.com/advisories/GHSA-xr2c-5w89-63pv', 'https://github.com/python-poetry/poetry/releases/tag/1.1.9', 'https://github.com/python-poetry/poetry-core/pull/205/commits/fa9cb6f358ae840885c700f954317f34838caba7'} | null | {'https://github.com/python-poetry/poetry-core/pull/205/commits/fa9cb6f358ae840885c700f954317f34838caba7'} | {'https://github.com/python-poetry/poetry-core/pull/205/commits/fa9cb6f358ae840885c700f954317f34838caba7'} |
GHSA | GHSA-2xm2-xj2q-qgpj | receiving subscription objects with deleted session | Original Message:
Hi,
I create objects with one client with an ACL of all users with a specific column value. Thats working so far.
Then I deleted the session object from one user to look if he can receive subscription objects and he can receive them.
The client with the deleted session cant create new objects, which Parse restricts right.
The LiveQueryServer doesnt detect deleted sessions after the websocket connection was established.
There should be a mechanism that checks in an specific interval if the session exists.
I dont know if its true with expired sessions.
Any solutions?
Parse version: 4.3.0
Parse js SDK version: 2.17
Solution:
Hi guys.
I've found and fixed the problem. It happens because there are two caches in place for the session token:
- at Parse Server level, which, according with the docs, should be changed via cacheTTL option and defaults to 5 seconds;
- at Parse Live Query level, which, according with the docs, should be changed via liveQueryServerOptions.cacheTimeout and defaults to 30 days.
But there are three problems:
- cacheTTL has currently no effect over Live Query Server;
- cacheTimeout also has currently no effect over Live Query Server;
- cacheTimeout actually defaults to 1h.
So, currently, if you wait 1 hour after the session token was invalidated, the clients using the old session token are not able to receive the events.
What I did:
- Added a test case for the problem;
- Fixed cacheTTL for Live Query Server;
- Fixed cacheTimeout for Live Query Server;
- Changed the cacheTimeout to default 5s;
- Changed the docs to reflect the actual 5s default for cacheTimeout.
| {'CVE-2020-15270'} | 2022-04-19T19:02:40Z | 2020-10-27T19:15:19Z | MODERATE | 4.3 | {'CWE-672'} | {'https://github.com/advisories/GHSA-2xm2-xj2q-qgpj', 'https://github.com/parse-community/parse-server/security/advisories/GHSA-2xm2-xj2q-qgpj', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15270', 'https://github.com/parse-community/parse-server/commit/78b59fb26b1c36e3cdbd42ba9fec025003267f58'} | null | {'https://github.com/parse-community/parse-server/commit/78b59fb26b1c36e3cdbd42ba9fec025003267f58'} | {'https://github.com/parse-community/parse-server/commit/78b59fb26b1c36e3cdbd42ba9fec025003267f58'} |
GHSA | GHSA-43fq-w8qq-v88h | 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. | {'CVE-2020-11538'} | 2021-09-22T21:32:48Z | 2020-07-27T21:52:36Z | HIGH | 8.1 | {'CWE-125'} | {'https://github.com/advisories/GHSA-43fq-w8qq-v88h', 'https://github.com/python-pillow/Pillow/pull/4504', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11538', 'https://github.com/python-pillow/Pillow/commit/2ef59fdbaeb756bc512ab3f2ad15ac45665b303d', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HOKHNWV2VS5GESY7IBD237E7C6T3I427/', 'https://pillow.readthedocs.io/en/stable/releasenotes/index.html', 'https://snyk.io/vuln/SNYK-PYTHON-PILLOW-574574', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BEBCPE4F2VHTIT6EZA2YZQZLPVDEBJGD/', 'https://usn.ubuntu.com/4430-2/', 'https://github.com/python-pillow/Pillow/blob/master/docs/releasenotes/7.1.0.rst#security', 'https://pillow.readthedocs.io/en/stable/releasenotes/7.1.0.html', 'https://usn.ubuntu.com/4430-1/', 'https://github.com/python-pillow/Pillow/pull/4538'} | null | {'https://github.com/python-pillow/Pillow/commit/2ef59fdbaeb756bc512ab3f2ad15ac45665b303d'} | {'https://github.com/python-pillow/Pillow/commit/2ef59fdbaeb756bc512ab3f2ad15ac45665b303d'} |
GHSA | GHSA-mcgw-5fhw-3fq8 | Incorrect Authorization in saleor | Incorrect Authorization in saleor prior to 3.1.2. | {'CVE-2022-0932'} | 2022-03-29T21:09:08Z | 2022-03-12T00:00:34Z | MODERATE | 6.5 | {'CWE-863'} | {'https://github.com/advisories/GHSA-mcgw-5fhw-3fq8', 'https://huntr.dev/bounties/88ae4cbc-c697-401b-8b04-7dc4e03ad8eb', 'https://github.com/saleor/saleor/commit/521dfd6394f3926a77c60d8633c058e16d0f916d', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0932'} | null | {'https://github.com/saleor/saleor/commit/521dfd6394f3926a77c60d8633c058e16d0f916d'} | {'https://github.com/saleor/saleor/commit/521dfd6394f3926a77c60d8633c058e16d0f916d'} |
GHSA | GHSA-6jqp-j69q-pm62 | AWS Lambda parser is vulnerable to Regular Expression Denial of Service | index.js in the aws-lambda-multipart-parser NPM package before 0.1.2 has a Regular Expression Denial of Service (ReDoS) issue via a crafted multipart/form-data boundary string. | {'CVE-2018-7560'} | 2022-04-25T22:28:18Z | 2018-03-05T19:16:56Z | HIGH | 7.5 | {'CWE-20'} | {'https://github.com/myshenin/aws-lambda-multipart-parser/commit/56ccb03af4dddebc2b2defb348b6558783d5757e', 'https://nvd.nist.gov/vuln/detail/CVE-2018-7560', 'https://github.com/advisories/GHSA-6jqp-j69q-pm62'} | null | {'https://github.com/myshenin/aws-lambda-multipart-parser/commit/56ccb03af4dddebc2b2defb348b6558783d5757e'} | {'https://github.com/myshenin/aws-lambda-multipart-parser/commit/56ccb03af4dddebc2b2defb348b6558783d5757e'} |
GHSA | GHSA-hj5v-574p-mj7c | Regular expression denial of service in py | A denial of service via regular expression in the py.path.svnwc component of py (aka python-py) through 1.9.0 could be used by attackers to cause a compute-time denial of service attack by supplying malicious input to the blame functionality. | {'CVE-2020-29651'} | 2021-04-21T20:27:10Z | 2021-04-20T16:39:57Z | HIGH | 7.5 | {'CWE-400'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-29651', 'https://github.com/pytest-dev/py/issues/256', 'https://github.com/pytest-dev/py/pull/257', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AYWNYEV3FGDHPIHX4DDUDMFZ6NLCQRC4/', 'https://github.com/advisories/GHSA-hj5v-574p-mj7c', 'https://github.com/pytest-dev/py/pull/257/commits/4a9017dc6199d2a564b6e4b0aa39d6d8870e4144', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CHDTINIBJZ67T3W74QTBIY5LPKAXEOGR/'} | null | {'https://github.com/pytest-dev/py/pull/257/commits/4a9017dc6199d2a564b6e4b0aa39d6d8870e4144'} | {'https://github.com/pytest-dev/py/pull/257/commits/4a9017dc6199d2a564b6e4b0aa39d6d8870e4144'} |
GHSA | GHSA-g8m7-qhv7-9h5x | Path Traversal in serve-here.js | Versions of `serve-here.js` prior to 1.2.0 are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the served folder using relative paths.
## Recommendation
Upgrade to version 1.2.0 or later. | null | 2021-09-22T18:35:24Z | 2019-07-05T21:07:14Z | HIGH | 0 | {'CWE-22'} | {'https://github.com/advisories/GHSA-g8m7-qhv7-9h5x', 'https://nodesecurity.io/advisories/554', 'https://hackerone.com/reports/569966', 'https://www.npmjs.com/advisories/554', 'https://github.com/vivaxy/here/commit/298dbab41344dfb7f95f66b1fa7b5cfb436bd4a2', 'https://hackerone.com/reports/296254', 'https://github.com/vivaxy/here/pull/17'} | null | {'https://github.com/vivaxy/here/commit/298dbab41344dfb7f95f66b1fa7b5cfb436bd4a2'} | {'https://github.com/vivaxy/here/commit/298dbab41344dfb7f95f66b1fa7b5cfb436bd4a2'} |
GHSA | GHSA-6c7m-qwxj-mvhp | Broken encryption in EdgeX Foundry | ### Summary
Broken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors.
### Detailed Description
The app-functions-sdk exports an “aes” transform that user scripts can optionally call to encrypt data in the processing pipeline. No decrypt function is provided. Encryption is not enabled by default, but if used, the level of protection may be less than the user may expects due to a broken implementation in https://github.com/edgexfoundry/app-functions-sdk-go/blob/v1.0.0/pkg/transforms/encryption.go
Version v2.1.0 (EdgeX Foundry Jakarta release and later) of app-functions-sdk-go/v2 deprecates the “aes” transform and provides an improved “aes256” transform in its place. The broken implementation will remain in a deprecated state until it is removed in the next EdgeX major release to avoid breakage of existing software that depends on the broken implementation.
### Impact
As the broken transform is a library function that is not invoked by default, users who do not use the AES transform in their processing pipelines are unaffected. Those that are affected are urged to upgrade to the Jakarta EdgeX release and modify processing pipelines to use the new "aes256" transform.
#### Vulnerable go modules
- github.com/edgexfoundry/app-functions-sdk-go < v2.1.0
- github.com/edgexfoundry/app-functions-sdk-go/v2 < v2.1.0
- github.com/edgexfoundry/app-service-configurable < v2.1.0
#### Vulnerable containers
- https://hub.docker.com/r/edgexfoundry/app-service-configurable >= 2.0.0 < v2.1.0
- https://hub.docker.com/r/edgexfoundry/app-service-configurable-arm64 >= 2.0.0 < 2.1.0
- https://hub.docker.com/r/edgexfoundry/docker-app-service-configurable < 2.0.0
- https://hub.docker.com/r/edgexfoundry/docker-app-service-configurable-arm64 < 2.0.0
#### Vulnerable Snaps
- https://snapcraft.io/edgex-app-service-configurable >= 2.0.0 < 2.1.0
### Patches
Upgrade to 2.1.0 version of app-functions-sdk-go/v2, app-service-configurable, and related docker containers shown below and modify user scripts to use the new "aes256" transform in place of the existing "aes" transform.
#### Patched go modules
- github.com/edgexfoundry/app-functions-sdk-go/v2 v2.1.0
- github.com/edgexfoundry/app-service-configurable v2.1.0
Modification of user scripts is necessary for full remediation.
#### Patched containers
- https://hub.docker.com/r/edgexfoundry/app-service-configurable:>=2.1.0
- https://hub.docker.com/r/edgexfoundry/app-service-configurable-arm64:>=2.1.0
Modification of user scripts is necessary for full remediation.
#### Patched Snaps
- https://snapcraft.io/edgex-app-service-configurable >= 2.1.0
Modification of user scripts is necessary for full remediation.
### Workarounds
If unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption.
### References
* [2.0 documentation](https://docs.edgexfoundry.org/2.0/microservices/application/BuiltIn/#aes)
* [2.1 documentation](https://docs.edgexfoundry.org/2.1/microservices/application/BuiltIn/#encryption-deprecated)
* [GitHub issue](https://github.com/edgexfoundry/app-functions-sdk-go/issues/968)
### For more information
If you have any questions or comments about this advisory:
* Contact us in the [Slack #security channel](https://slack.edgexfoundry.org/)
* Open an issue in [edgex-go](https://github.com/edgexfoundry/edgex-go)
* Email us at [EdgeX-TSC-Security@lists.edgexfoundry.org](mailto:EdgeX-TSC-Security@lists.edgexfoundry.org) | {'CVE-2021-41278'} | 2022-04-19T19:03:14Z | 2021-11-19T20:55:16Z | MODERATE | 5.4 | {'CWE-327'} | {'https://github.com/edgexfoundry/app-functions-sdk-go/commit/8fa13c6388ce76a6b878b54490eac61aa7d81165', 'https://github.com/edgexfoundry/app-functions-sdk-go/security/advisories/GHSA-6c7m-qwxj-mvhp', 'https://github.com/advisories/GHSA-6c7m-qwxj-mvhp', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41278'} | null | {'https://github.com/edgexfoundry/app-functions-sdk-go/commit/8fa13c6388ce76a6b878b54490eac61aa7d81165'} | {'https://github.com/edgexfoundry/app-functions-sdk-go/commit/8fa13c6388ce76a6b878b54490eac61aa7d81165'} |
GHSA | GHSA-2gfx-95x2-5v3x | Heap buffer overflow in `QuantizedReshape` | ### Impact
An attacker can cause a heap buffer overflow in `QuantizedReshape` by passing in invalid thresholds for the quantization:
```python
import tensorflow as tf
tensor = tf.constant([], dtype=tf.qint32)
shape = tf.constant([], dtype=tf.int32)
input_min = tf.constant([], dtype=tf.float32)
input_max = tf.constant([], dtype=tf.float32)
tf.raw_ops.QuantizedReshape(tensor=tensor, shape=shape, input_min=input_min, input_max=input_max)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/a324ac84e573fba362a5e53d4e74d5de6729933e/tensorflow/core/kernels/quantized_reshape_op.cc#L38-L55) assumes that the 2 arguments are always valid scalars and tries to access the numeric value directly:
```cc
const auto& input_min_float_tensor = ctx->input(2);
...
const float input_min_float = input_min_float_tensor.flat<float>()(0);
const auto& input_max_float_tensor = ctx->input(3);
...
const float input_max_float = input_max_float_tensor.flat<float>()(0);
```
However, if any of these tensors is empty, then `.flat<T>()` is an empty buffer and accessing the element at position 0 results in overflow.
### Patches
We have patched the issue in GitHub commit [a324ac84e573fba362a5e53d4e74d5de6729933e](https://github.com/tensorflow/tensorflow/commit/a324ac84e573fba362a5e53d4e74d5de6729933e).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team. | {'CVE-2021-29536'} | 2021-05-21T14:22:32Z | 2021-05-21T14:22:32Z | LOW | 2.5 | {'CWE-787'} | {'https://github.com/advisories/GHSA-2gfx-95x2-5v3x', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29536', 'https://github.com/tensorflow/tensorflow/commit/a324ac84e573fba362a5e53d4e74d5de6729933e', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-2gfx-95x2-5v3x'} | null | {'https://github.com/tensorflow/tensorflow/commit/a324ac84e573fba362a5e53d4e74d5de6729933e'} | {'https://github.com/tensorflow/tensorflow/commit/a324ac84e573fba362a5e53d4e74d5de6729933e'} |
GHSA | GHSA-338v-3958-8v8r | Information disclosure in JBoss Weld | Race condition in JBoss Weld before 2.2.8 and 3.x before 3.0.0 Alpha3 allows remote attackers to obtain information from a previous conversation via vectors related to a stale thread state. | {'CVE-2014-8122'} | 2021-08-30T13:39:37Z | 2020-06-10T20:54:15Z | MODERATE | 0 | {'CWE-362'} | {'https://nvd.nist.gov/vuln/detail/CVE-2014-8122', 'http://rhn.redhat.com/errata/RHSA-2015-0773.html', 'http://rhn.redhat.com/errata/RHSA-2015-0920.html', 'http://rhn.redhat.com/errata/RHSA-2015-0218.html', 'https://github.com/weld/core/commit/8e413202fa1af08c09c580f444e4fd16874f9c65', 'http://rhn.redhat.com/errata/RHSA-2015-0850.html', 'https://github.com/weld/core/commit/29fd1107fd30579ad9bb23fae4dc3ba464205745', 'http://www.securitytracker.com/id/1031741', 'http://rhn.redhat.com/errata/RHSA-2015-0851.html', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/100892', 'https://github.com/weld/core/commit/6808b11cd6d97c71a2eed754ed4f955acd789086', 'https://github.com/victims/victims-cve-db/blob/master/database/java/2014/8122.yaml', 'https://github.com/advisories/GHSA-338v-3958-8v8r', 'http://rhn.redhat.com/errata/RHSA-2015-0675.html', 'http://rhn.redhat.com/errata/RHSA-2015-0217.html', 'http://rhn.redhat.com/errata/RHSA-2015-0215.html', 'http://www.securityfocus.com/bid/74252', 'http://rhn.redhat.com/errata/RHSA-2015-0216.html'} | null | {'https://github.com/weld/core/commit/6808b11cd6d97c71a2eed754ed4f955acd789086', 'https://github.com/weld/core/commit/29fd1107fd30579ad9bb23fae4dc3ba464205745', 'https://github.com/weld/core/commit/8e413202fa1af08c09c580f444e4fd16874f9c65'} | {'https://github.com/weld/core/commit/8e413202fa1af08c09c580f444e4fd16874f9c65', 'https://github.com/weld/core/commit/29fd1107fd30579ad9bb23fae4dc3ba464205745', 'https://github.com/weld/core/commit/6808b11cd6d97c71a2eed754ed4f955acd789086'} |
GHSA | GHSA-pc22-3g76-gm6j | Generator Web Application: Local Privilege Escalation Vulnerability via System Temp Directory | ### Impact
On Unix like systems, the system's temporary directory is shared between all users on that system. A collocated user can observe the process of creating a temporary sub directory in the shared temporary directory and race to complete the creation of the temporary subdirectory.
This vulnerability is local privilege escalation because the contents of the `outputFolder` can be appended to by an attacker. As such, code written to this directory, when executed can be attacker controlled.
#### Java Code
The method `File.createTempFile` from the JDK is vulnerable to this local information disclosure vulnerability.
https://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-generator/src/main/java/io/swagger/generator/online/Generator.java#L174-L185
### Patches
Fix has been applied to the master branch with:
* https://github.com/swagger-api/swagger-codegen/commit/987ea7a30b463cc239580d6ad166c707ae942a89
included in release: 2.4.19
### References
* [CWE-378: Creation of Temporary File With Insecure Permissions](https://cwe.mitre.org/data/definitions/378.html)
* [CWE-379: Creation of Temporary File in Directory with Insecure Permissions](https://cwe.mitre.org/data/definitions/379.html)
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@swagger.io](mailto:security@swagger.io)
#### Original vulnerability report
> I'm performing OSS security research under the GitHub Security Lab Bug Bounty program.
> I've been using a custom CodeQL query to find local temporary directory vulnerabilities in OSS with three custom CodeQL queries.
>
> - https://github.com/github/codeql/pull/4388/files#diff-71d36c0f2bd0b08e32866f873f1c906cdc17277e0ad327c0c6cd2c882f30de4f
> - https://github.com/github/codeql/pull/4388/files#diff-1893a18a8bf43c011d61a7889d0139b998a5a78701a30fe7722eddd4c506aaac
> - https://github.com/github/codeql/pull/4473
>
> The code generated by the Swagger Generator contains a local information disclosure vulnerability. The system temporary directory, on unix-like systems is shared between multiple users. Information written to this directory, or directories created under this directory that do not correctly set the posix standard permissions can have these directories read/modified by other users.
>
> ---
>
> This vulnerability exists in the maven plugin.
>
> This vulnerability is distinctly different. This vulnerability is most likely a local privilege escalation vulnerability.
>
> https://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-generator/src/main/java/io/swagger/generator/online/Generator.java#L174-L185
>
> This vulnerability is very similar to this similar vulnerability I disclosed in the Eclipse Jetty project.
>
> https://github.com/eclipse/jetty.project/security/advisories/GHSA-g3wg-6mcf-8jj6
>
> This is due to a race condition between the call to `delete` and the call to `mkdirs`.
>
> ```java
> // ensure file will always be unique by appending random digits
> File outputFolder = File.createTempFile("codegen-", "-tmp"); // Attacker knows the full path of the file that will be generated
> // delete the file that was created
> outputFolder.delete(); // Attacker sees file is deleted and begins a race to create their own directory before Swagger Code Generator.
> // and make a directory of the same name
> // SECURITY VULNERABILITY: Race Condition! - Attacker beats Swagger Code Generator and now owns this directory
> outputFolder.mkdirs();
> ```
>
> This vulnerability is local privilege escalation because the contents of the `outputFolder` can be appended to by an attacker. As such, code written to this directory, when executed can be attacker controlled.
>
> The fix here is to switch to the `Files` API for creating temporary directories. Which does not contain this race condition, and appropriately sets the correct file permissions.
> | {'CVE-2021-21363'} | 2022-04-19T19:02:48Z | 2021-03-11T03:09:16Z | LOW | 9.3 | {'CWE-379', 'CWE-378'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-21363', 'https://github.com/swagger-api/swagger-codegen/security/advisories/GHSA-pc22-3g76-gm6j', 'https://github.com/advisories/GHSA-pc22-3g76-gm6j', 'https://github.com/swagger-api/swagger-codegen/commit/987ea7a30b463cc239580d6ad166c707ae942a89'} | null | {'https://github.com/swagger-api/swagger-codegen/commit/987ea7a30b463cc239580d6ad166c707ae942a89'} | {'https://github.com/swagger-api/swagger-codegen/commit/987ea7a30b463cc239580d6ad166c707ae942a89'} |
GHSA | GHSA-j977-g5vj-j27g | Cross-Site Scripting in scratch-svg-renderer | This affects the package scratch-svg-renderer before 0.2.0-prerelease.20201019174008. The loadString function does not escape SVG properly, which can be used to inject arbitrary elements into the DOM via the _transformMeasurements function. | {'CVE-2020-7750'} | 2021-01-07T22:49:02Z | 2020-11-09T14:21:17Z | HIGH | 9.6 | {'CWE-79'} | {'https://github.com/LLK/scratch-svg-renderer/commit/9ebf57588aa596c4fa3bb64209e10ade395aee90', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7750', 'https://snyk.io/vuln/SNYK-JS-SCRATCHSVGRENDERER-1020497', 'https://github.com/advisories/GHSA-j977-g5vj-j27g'} | null | {'https://github.com/LLK/scratch-svg-renderer/commit/9ebf57588aa596c4fa3bb64209e10ade395aee90'} | {'https://github.com/LLK/scratch-svg-renderer/commit/9ebf57588aa596c4fa3bb64209e10ade395aee90'} |
GHSA | GHSA-pm9p-9926-w68m | Denial of Service in ecstatic | `ecstatic`, a simple static file server middleware, is vulnerable to denial of service. If a payload with a large number of null bytes (`%00`) is provided by an attacker it can crash ecstatic by running it out of memory.
[Results from the original advisory](https://www.checkmarx.com/advisories/denial-of-service-dos-vulnerability-in-ecstatic-npm-package/)
```
A payload of 22kB caused a lag of 1 second,
A payload of 35kB caused a lag of 3 seconds,
A payload of 86kB caused the server to crash
```
## Recommendation
Update to version 2.0.0 or later. | {'CVE-2016-10703'} | 2021-09-16T18:15:10Z | 2017-12-28T22:52:47Z | HIGH | 7.5 | {'CWE-20'} | {'https://advisory.checkmarx.net/advisory/CX-2016-4450', 'https://github.com/advisories/GHSA-pm9p-9926-w68m', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10703', 'https://www.npmjs.com/advisories/553', 'https://github.com/jfhbrook/node-ecstatic/commit/71ce93988ead4b561a8592168c72143907189f01#diff-b2b5a88fb51675f1aa1065c093dce1ee', 'https://www.checkmarx.com/advisories/denial-of-service-dos-vulnerability-in-ecstatic-npm-package/', 'https://github.com/jfhbrook/node-ecstatic/commit/71ce93988ead4b561a8592168c72143907189f01'} | null | {'https://github.com/jfhbrook/node-ecstatic/commit/71ce93988ead4b561a8592168c72143907189f01#diff-b2b5a88fb51675f1aa1065c093dce1ee', 'https://github.com/jfhbrook/node-ecstatic/commit/71ce93988ead4b561a8592168c72143907189f01'} | {'https://github.com/jfhbrook/node-ecstatic/commit/71ce93988ead4b561a8592168c72143907189f01#diff-b2b5a88fb51675f1aa1065c093dce1ee', 'https://github.com/jfhbrook/node-ecstatic/commit/71ce93988ead4b561a8592168c72143907189f01'} |
GHSA | GHSA-jppv-gw3r-w3q8 | OS Command Injection in Rake | There is an OS command injection vulnerability in Ruby Rake before 12.3.3 in Rake::FileList when supplying a filename that begins with the pipe character `|`. | {'CVE-2020-8130'} | 2021-01-08T20:28:46Z | 2020-02-28T16:54:36Z | MODERATE | 0 | {'CWE-78'} | {'http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00041.html', 'https://hackerone.com/reports/651518', 'https://github.com/advisories/GHSA-jppv-gw3r-w3q8', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/523CLQ62VRN3VVC52KMPTROCCKY4Z36B/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8130', 'https://usn.ubuntu.com/4295-1/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VXMX4ARNX2JLRJMSH4N3J3UBMUT5CI44/', 'https://github.com/ruby/rake/commit/5b8f8fc41a5d7d7d6a5d767e48464c60884d3aee', 'https://lists.debian.org/debian-lts-announce/2020/02/msg00026.html'} | null | {'https://github.com/ruby/rake/commit/5b8f8fc41a5d7d7d6a5d767e48464c60884d3aee'} | {'https://github.com/ruby/rake/commit/5b8f8fc41a5d7d7d6a5d767e48464c60884d3aee'} |
GHSA | GHSA-mgx3-27hr-mfgp | High severity vulnerability that affects httparty | The httparty gem 0.9.0 and earlier for Ruby does not properly restrict casts of string values, which might allow remote attackers to conduct object-injection attacks and execute arbitrary code, or cause a denial of service (memory and CPU consumption) by leveraging Action Pack support for YAML type conversion, a similar vulnerability to CVE-2013-0156. | {'CVE-2013-1801'} | 2021-09-15T19:00:25Z | 2017-10-24T18:33:37Z | HIGH | 0 | null | {'https://bugzilla.redhat.com/show_bug.cgi?id=917229', 'https://support.cloud.engineyard.com/entries/22915701-january-14-2013-security-vulnerabilities-httparty-extlib-crack-nori-update-these-gems-immediately', 'https://nvd.nist.gov/vuln/detail/CVE-2013-1801', 'https://github.com/advisories/GHSA-mgx3-27hr-mfgp', 'http://www.securityfocus.com/bid/58260', 'https://github.com/jnunemaker/httparty/commit/53a812426dd32108d6cba4272b493aa03bc8c031'} | null | {'https://github.com/jnunemaker/httparty/commit/53a812426dd32108d6cba4272b493aa03bc8c031'} | {'https://github.com/jnunemaker/httparty/commit/53a812426dd32108d6cba4272b493aa03bc8c031'} |
GHSA | GHSA-6r86-2jm9-9mh4 | File upload restriction bypass in Zenario CMS | Zenario CMS 9.2 allows an authenticated admin user to bypass the file upload restriction by creating a new 'File/MIME Types' using the '.phar' extension. Then an attacker can upload a malicious file, intercept the request and change the extension to '.phar' in order to run commands on the server. | {'CVE-2022-23043'} | 2022-03-04T21:39:12Z | 2022-02-25T00:01:07Z | HIGH | 7.2 | {'CWE-434'} | {'https://fluidattacks.com/advisories/simone/', 'https://github.com/advisories/GHSA-6r86-2jm9-9mh4', 'https://github.com/TribalSystems/Zenario/releases/tag/9.2.55826', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23043', 'https://github.com/TribalSystems/Zenario/commit/f0682d22688d9921dc0dfd6e858900ebf2706f19'} | null | {'https://github.com/TribalSystems/Zenario/commit/f0682d22688d9921dc0dfd6e858900ebf2706f19'} | {'https://github.com/TribalSystems/Zenario/commit/f0682d22688d9921dc0dfd6e858900ebf2706f19'} |
GHSA | GHSA-pc32-x737-74cv | Cross-site Scripting in Pimcore | Pimcore 10.3.3 and prior is vulnerable to stored cross-site scripting. A patch is available on the 10.x branch and will likely be part of version 10.4.0. | {'CVE-2022-0704'} | 2022-03-29T21:32:26Z | 2022-03-17T00:00:48Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/advisories/GHSA-pc32-x737-74cv', 'https://github.com/pimcore/pimcore/pull/11447', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0704', 'https://github.com/pimcore/pimcore/commit/6e0922c5b2959ac1b48500ac508d8fc5a97286f9', 'https://huntr.dev/bounties/4142a8b4-b439-4328-aaa3-52f6fedfd0a6'} | null | {'https://github.com/pimcore/pimcore/commit/6e0922c5b2959ac1b48500ac508d8fc5a97286f9'} | {'https://github.com/pimcore/pimcore/commit/6e0922c5b2959ac1b48500ac508d8fc5a97286f9'} |
GHSA | GHSA-crch-j389-5f84 | Heap OOB write in TFLite | ### Impact
A specially crafted TFLite model could trigger an OOB write on heap in the TFLite implementation of [`ArgMin`/`ArgMax`](https://github.com/tensorflow/tensorflow/blob/102b211d892f3abc14f845a72047809b39cc65ab/tensorflow/lite/kernels/arg_min_max.cc#L52-L59):
```cc
TfLiteIntArray* output_dims = TfLiteIntArrayCreate(NumDimensions(input) - 1);
int j = 0;
for (int i = 0; i < NumDimensions(input); ++i) {
if (i != axis_value) {
output_dims->data[j] = SizeOfDimension(input, i);
++j;
}
}
```
If `axis_value` is not a value between 0 and `NumDimensions(input)`, then the condition in the `if` is never true, so code writes past the last valid element of `output_dims->data`.
### Patches
We have patched the issue in GitHub commit [c59c37e7b2d563967da813fa50fe20b21f4da683](https://github.com/tensorflow/tensorflow/commit/c59c37e7b2d563967da813fa50fe20b21f4da683).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-29603'} | 2021-05-21T14:28:15Z | 2021-05-21T14:28:15Z | LOW | 2.5 | {'CWE-787'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29603', 'https://github.com/advisories/GHSA-crch-j389-5f84', 'https://github.com/tensorflow/tensorflow/commit/c59c37e7b2d563967da813fa50fe20b21f4da683', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-crch-j389-5f84'} | null | {'https://github.com/tensorflow/tensorflow/commit/c59c37e7b2d563967da813fa50fe20b21f4da683'} | {'https://github.com/tensorflow/tensorflow/commit/c59c37e7b2d563967da813fa50fe20b21f4da683'} |
GHSA | GHSA-jxwx-85vp-gvwm | Regular Expression Denial of Service in jquery-validation | The GitHub Security Lab team has identified potential security vulnerabilities in jquery.validation.
The project contains one or more regular expressions that are vulnerable to ReDoS (Regular Expression Denial of Service)
This issue was discovered and reported by GitHub team member @erik-krogh (Erik Krogh Kristensen). | {'CVE-2021-21252'} | 2022-04-19T19:02:41Z | 2021-01-13T18:21:54Z | MODERATE | 0 | {'CWE-400'} | {'https://github.com/jquery-validation/jquery-validation/pull/2371', 'https://github.com/jquery-validation/jquery-validation/security/advisories/GHSA-jxwx-85vp-gvwm', 'https://security.netapp.com/advisory/ntap-20210219-0005/', 'https://github.com/jquery-validation/jquery-validation/commit/5d8f29eef363d043a8fec4eb86d42cadb5fa5f7d', 'https://www.npmjs.com/package/jquery-validation', 'https://github.com/advisories/GHSA-jxwx-85vp-gvwm', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21252'} | null | {'https://github.com/jquery-validation/jquery-validation/commit/5d8f29eef363d043a8fec4eb86d42cadb5fa5f7d'} | {'https://github.com/jquery-validation/jquery-validation/commit/5d8f29eef363d043a8fec4eb86d42cadb5fa5f7d'} |
GHSA | GHSA-246w-56m2-5899 | Cross-site scripting (XSS) vulnerability in the password reset endpoint | ### Impact
The password reset endpoint served via Synapse was vulnerable to cross-site scripting (XSS) attacks. The impact depends on the configuration of the domain that Synapse is deployed on, but may allow access to cookies and other browser data, CSRF vulnerabilities, and access to other resources served on the same domain or parent domains.
### Patches
This is fixed in #9200.
### Workarounds
Depending on the needs and configuration of the homeserver a few options are available:
1. Password resets can be disabled by delegating email to a third-party service (via the `account_threepid_delegates.email` setting) or disabling email (by not configuring the `email` setting).
2. If the homeserver is not configured to use passwords (via the `password_config.enabled` setting) then the affected endpoint can be blocked at a reverse proxy:
* `/_synapse/client/password_reset/email/submit_token`
3. The `password_reset_confirmation.html` template can be overridden with a custom template that manually escapes the variables using [JInja2's `escape` filter](https://jinja.palletsprojects.com/en/2.11.x/templates/#escape). See the `email.template_dir` setting. | {'CVE-2021-21332'} | 2021-08-31T21:07:24Z | 2021-03-26T19:52:54Z | MODERATE | 6.9 | {'CWE-79'} | {'https://github.com/matrix-org/synapse/commit/e54746bdf7d5c831eabe4dcea76a7626f1de73df', 'https://github.com/matrix-org/synapse/releases/tag/v1.27.0', 'https://github.com/advisories/GHSA-246w-56m2-5899', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21332', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TNNAJOZNMVMXM6AS7RFFKB4QLUJ4IFEY/', 'https://github.com/matrix-org/synapse/pull/9200', 'https://github.com/matrix-org/synapse/security/advisories/GHSA-246w-56m2-5899'} | null | {'https://github.com/matrix-org/synapse/commit/e54746bdf7d5c831eabe4dcea76a7626f1de73df'} | {'https://github.com/matrix-org/synapse/commit/e54746bdf7d5c831eabe4dcea76a7626f1de73df'} |
GHSA | GHSA-qf7v-8hj3-4xw7 | Improper Verification of Cryptographic Signature in PySAML2 | PySAML2 before 5.0.0 does not check that the signature in a SAML document is enveloped and thus signature wrapping is effective, i.e., it is affected by XML Signature Wrapping (XSW). The signature information and the node/object that is signed can be in different places and thus the signature verification will succeed, but the wrong data will be used. This specifically affects the verification of assertion that have been signed. | {'CVE-2020-5390'} | 2021-08-25T21:05:17Z | 2020-05-06T19:41:29Z | HIGH | 7.5 | {'CWE-347'} | {'https://github.com/IdentityPython/pysaml2/commit/f27c7e7a7010f83380566a219fd6a290a00f2b6e', 'https://usn.ubuntu.com/4245-1/', 'https://lists.debian.org/debian-lts-announce/2020/02/msg00025.html', 'https://github.com/IdentityPython/pysaml2/releases/tag/v5.0.0', 'https://pypi.org/project/pysaml2/5.0.0/', 'https://github.com/IdentityPython/pysaml2/releases', 'https://github.com/IdentityPython/pysaml2/blob/master/CHANGELOG.md#500-2020-01-13', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5390', 'https://github.com/IdentityPython/pysaml2/commit/5e9d5acbcd8ae45c4e736ac521fd2df5b1c62e25', 'https://www.debian.org/security/2020/dsa-4630', 'https://github.com/advisories/GHSA-qf7v-8hj3-4xw7'} | null | {'https://github.com/IdentityPython/pysaml2/commit/f27c7e7a7010f83380566a219fd6a290a00f2b6e', 'https://github.com/IdentityPython/pysaml2/commit/5e9d5acbcd8ae45c4e736ac521fd2df5b1c62e25'} | {'https://github.com/IdentityPython/pysaml2/commit/5e9d5acbcd8ae45c4e736ac521fd2df5b1c62e25', 'https://github.com/IdentityPython/pysaml2/commit/f27c7e7a7010f83380566a219fd6a290a00f2b6e'} |
GHSA | GHSA-r8j4-96mx-rjcc | Improper Restriction of XML External Entity Reference in skylot/jadx | skylot/jadx prior to 1.3.2 is vulnerable to Improper Restriction of XML External Entities when a user is tricked into exporting a malicious APK file (via the -e option) containing a crafted AndroidManifest.xml / strings.xml to gradle, leading to possible local file disclosure. | {'CVE-2022-0219'} | 2022-04-19T19:03:24Z | 2022-01-21T18:13:42Z | MODERATE | 5.5 | {'CWE-611'} | {'https://github.com/skylot/jadx/commit/d22db30166e7cb369d72be41382bb63ac8b81c52', 'https://github.com/advisories/GHSA-r8j4-96mx-rjcc', 'https://huntr.dev/bounties/0d093863-29e8-4dd7-a885-64f76d50bf5e', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0219'} | null | {'https://github.com/skylot/jadx/commit/d22db30166e7cb369d72be41382bb63ac8b81c52'} | {'https://github.com/skylot/jadx/commit/d22db30166e7cb369d72be41382bb63ac8b81c52'} |
GHSA | GHSA-w2pf-g6r8-pg22 | Placeholder property does not indicate HTML capable, could lead to inadvertent abuse | ## Overview
Auth0 Lock version 11.20.4 and earlier did not properly sanitize the generated HTML code. Customers using the `additionalSignUpFields` customization option to add a checkbox to the sign-up dialog that are passing a `placeholder` property obtained from an untrusted source (e.g. a query parameter) could allow cross-site scripting (XSS) on their signup pages.
## Am I affected?
You are affected by this vulnerability if all of the following conditions apply:
- You are using Auth0 Lock version 11.20.4 or earlier.
- You pass `additionalSignUpFields` as options when initializing Lock which includes a field of type `checkbox` whose `placeholder` value is obtained from an untrusted source.
An example of a vulnerable snippet is the following where the `placeholder` value is partially user-controlled by the `name` query parameter:
```javascript
<script>
var params = new URLSearchParams(window.location.search);
var options = {
auth: {
redirectUrl: 'http://localhost:12345/callback',
responseType: 'code',
params: {
scope: 'openid email',
},
},
additionalSignUpFields: [{
name: 'agree',
type: 'checkbox',
placeholder: "I agree to Terms and Conditions for " + params.get('name'),
}],
};
var lock = new Auth0Lock('<CLIENT_ID>', '<TENANT_NAME>.auth0.com', options);
lock.show({
allowShowPassword: true,
initialScreen: 'signUp',
});
</script>
```
## How to fix that?
Developers using Auth0’s signin solution Lock need to upgrade to version 11.21.0 or later. Version 11.21.0 introduces two changes:
1. The existing `placeholder` property is now treated as plain text to mitigate the problem.
2. A new `placeholderHTML` property is introduced that indicates the level of control it provides and that it should be only supplied from trusted sources.
## Will this update impact my users?
This fix patches the Auth0 Lock widget and may require changes in application code, but it will not impact your users, their current state, or any existing sessions.
Developers using the `placeholder` property with HTML content from a trusted source should start using the `placeholderHTML` property to continue providing the same user experience. | {'CVE-2019-20174'} | 2021-08-19T16:48:59Z | 2020-01-31T17:59:51Z | MODERATE | 6.1 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-20174', 'https://auth0.com/docs/security/bulletins/cve-2019-20174', 'https://github.com/advisories/GHSA-w2pf-g6r8-pg22', 'https://github.com/auth0/lock/releases/tag/v11.21.0', 'https://github.com/auth0/lock/commit/6c15e5659c21cd814ea119af5c51b61399598dd5', 'https://github.com/auth0/lock/security/advisories/GHSA-w2pf-g6r8-pg22'} | null | {'https://github.com/auth0/lock/commit/6c15e5659c21cd814ea119af5c51b61399598dd5'} | {'https://github.com/auth0/lock/commit/6c15e5659c21cd814ea119af5c51b61399598dd5'} |
GHSA | GHSA-p72p-rjr2-r439 | Server-Side Request Forgery in terriajs-server | Versions of `terriajs-server`prior to 2.7.4 are vulnerable to Server-Side Request Forgery (SSRF). If an attacker has access to a server whitelisted by the terriajs-server proxy or if the attacker is able to modify the DNS records of a domain whitelisted by the terriajs-server proxy, the attacker can use the terriajs-server proxy to access any HTTP-accessible resources that are accessible to the server, including private resources in the hosting environment.
## Recommendation
Upgrade to version 2.7.4 or later. | null | 2021-08-04T20:07:20Z | 2019-05-29T20:24:02Z | HIGH | 0 | {'CWE-918'} | {'https://github.com/advisories/GHSA-p72p-rjr2-r439', 'https://medium.com/terria/security-vulnerability-in-terriajs-server-82c8bf4da0a5', 'https://www.npmjs.com/advisories/768', 'https://github.com/TerriaJS/terriajs-server/commit/3cbc48475f50a53962f605491d0e60648a29bdf0'} | null | {'https://github.com/TerriaJS/terriajs-server/commit/3cbc48475f50a53962f605491d0e60648a29bdf0'} | {'https://github.com/TerriaJS/terriajs-server/commit/3cbc48475f50a53962f605491d0e60648a29bdf0'} |
GHSA | GHSA-hwqf-gcqm-7353 | Header injection in nodemailer | The package nodemailer before 6.6.1 are vulnerable to HTTP Header Injection if unsanitized user input that may contain newlines and carriage returns is passed into an address object. | {'CVE-2021-23400'} | 2021-12-10T18:56:57Z | 2021-12-10T18:56:57Z | MODERATE | 6.3 | {'CWE-74'} | {'https://github.com/advisories/GHSA-hwqf-gcqm-7353', 'https://github.com/nodemailer/nodemailer/issues/1289', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1314737', 'https://snyk.io/vuln/SNYK-JS-NODEMAILER-1296415', 'https://github.com/nodemailer/nodemailer/commit/7e02648cc8cd863f5085bad3cd09087bccf84b9f', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23400'} | null | {'https://github.com/nodemailer/nodemailer/commit/7e02648cc8cd863f5085bad3cd09087bccf84b9f'} | {'https://github.com/nodemailer/nodemailer/commit/7e02648cc8cd863f5085bad3cd09087bccf84b9f'} |
GHSA | GHSA-v6rh-hp5x-86rv | Potential bypass of an upstream access control based on URL paths in Django | In Django 2.2 before 2.2.25, 3.1 before 3.1.14, and 3.2 before 3.2.10, HTTP requests for URLs with trailing newlines could bypass upstream access control based on URL paths. This issue has low severity, according to the Django security policy. | {'CVE-2021-44420'} | 2022-02-14T22:20:29Z | 2021-12-09T19:09:37Z | HIGH | 7.3 | {'CWE-287'} | {'https://security.netapp.com/advisory/ntap-20211229-0006/', 'https://www.djangoproject.com/weblog/2021/dec/07/security-releases/', 'https://github.com/django/django/commit/d4dcd5b9dd9e462fec8220e33e3e6c822b7e88a6', 'https://groups.google.com/forum/#!forum/django-announce', 'https://www.openwall.com/lists/oss-security/2021/12/07/1', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/B4SQG2EAF4WCI2SLRL6XRDJ3RPK3ZRDV/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-44420', 'https://docs.djangoproject.com/en/3.2/releases/security/', 'https://github.com/advisories/GHSA-v6rh-hp5x-86rv'} | null | {'https://github.com/django/django/commit/d4dcd5b9dd9e462fec8220e33e3e6c822b7e88a6'} | {'https://github.com/django/django/commit/d4dcd5b9dd9e462fec8220e33e3e6c822b7e88a6'} |
GHSA | GHSA-f884-gm86-cg3q | PrestaShop module ps_facetedsearch might be vulnerable from CVE-2017-9841 | ### Impact
We have identified that some ps_facetedsearch module ZIP archives have been built with phpunit dev dependencies. PHPUnit contains a php script that would allow, on a webserver, an attacker to perform a RCE.
This vulnerability impacts
- phpunit before 4.8.28 and 5.x before 5.6.3 as reported in [CVE-2017-9841](https://nvd.nist.gov/vuln/detail/CVE-2017-9841)
- phpunit >= 5.63 before 7.5.19 and 8.5.1 (this is a newly found vulnerability that is currently being submitted as a CVE after disclosure was provided to phpunit maintainers)
### Patches
In the [security patch](https://github.com/PrestaShop/ps_facetedsearch/releases/tag/v3.4.1), we look for the unwanted vendor/phpunit folder and remove it if we find it. This allows users to fix the security issue when upgrading.
### Workarounds
Users can also simply remove the unwanted vendor/phpunit folder.
### References
https://nvd.nist.gov/vuln/detail/CVE-2017-9841
### For more information
If you have any questions or comments about this advisory, email us at security@prestashop.com | null | 2020-01-07T17:20:47Z | 2020-01-07T17:20:47Z | HIGH | 0 | null | {'https://github.com/PrestaShop/ps_facetedsearch/commit/47c4785a21ee3b1734b2d46f044f9659a151feca', 'https://github.com/PrestaShop/ps_facetedsearch/security/advisories/GHSA-f884-gm86-cg3q', 'https://github.com/advisories/GHSA-f884-gm86-cg3q'} | null | {'https://github.com/PrestaShop/ps_facetedsearch/commit/47c4785a21ee3b1734b2d46f044f9659a151feca'} | {'https://github.com/PrestaShop/ps_facetedsearch/commit/47c4785a21ee3b1734b2d46f044f9659a151feca'} |
GHSA | GHSA-7r79-mrp6-8mhq | Rate limit missing in microweber | Microweber prior to version 1.3 does not rate limit password reset emails. | {'CVE-2022-0777'} | 2022-03-10T16:00:57Z | 2022-03-02T00:00:19Z | HIGH | 7.5 | {'CWE-640'} | {'https://github.com/microweber/microweber/commit/a3944cf9d1d8c41a48297ddc98302934e2511b0f', 'https://huntr.dev/bounties/b36be8cd-544f-42bd-990d-aa1a46df44d7', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0777', 'https://github.com/advisories/GHSA-7r79-mrp6-8mhq'} | null | {'https://github.com/microweber/microweber/commit/a3944cf9d1d8c41a48297ddc98302934e2511b0f'} | {'https://github.com/microweber/microweber/commit/a3944cf9d1d8c41a48297ddc98302934e2511b0f'} |
GHSA | GHSA-r3j7-x2g5-9gx6 | Command injection in samba-client | The samba-client package before 4.0.0 for Node.js allows command injection because of the use of process.exec. | {'CVE-2021-27185'} | 2022-05-03T03:44:39Z | 2021-02-11T20:47:27Z | CRITICAL | 9.8 | {'CWE-74', 'CWE-78', 'CWE-77'} | {'https://advisory.checkmarx.net/advisory/CX-2021-4302', 'https://github.com/eflexsystems/node-samba-client/releases/tag/4.0.0', 'https://security.netapp.com/advisory/ntap-20210319-0002/', 'https://github.com/eflexsystems/node-samba-client/commit/5bc3bbad9b8d02243bc861a11ec73f788fbb1235', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27185', 'https://www.npmjs.com/package/samba-client', 'https://github.com/advisories/GHSA-r3j7-x2g5-9gx6'} | null | {'https://github.com/eflexsystems/node-samba-client/commit/5bc3bbad9b8d02243bc861a11ec73f788fbb1235'} | {'https://github.com/eflexsystems/node-samba-client/commit/5bc3bbad9b8d02243bc861a11ec73f788fbb1235'} |
GHSA | GHSA-xcr3-4qvr-54rh | Cross-site Scripting in Pimcore | Pimcore prior to version 10.4 is vulnerable to stored cross-site scripting in Tooltip. | {'CVE-2022-1351'} | 2022-04-22T20:46:45Z | 2022-04-15T00:00:45Z | MODERATE | 6.8 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-1351', 'https://github.com/pimcore/pimcore/commit/8c39a8b8f14dce078b31f61c4da599ca6f8fc7ac', 'https://github.com/advisories/GHSA-xcr3-4qvr-54rh', 'https://huntr.dev/bounties/c23ae6c2-2e53-4bf5-85b0-e90418476615'} | null | {'https://github.com/pimcore/pimcore/commit/8c39a8b8f14dce078b31f61c4da599ca6f8fc7ac'} | {'https://github.com/pimcore/pimcore/commit/8c39a8b8f14dce078b31f61c4da599ca6f8fc7ac'} |
GHSA | GHSA-3hw5-q855-g6cw | Prototype Pollution in Dojox | The Dojox jQuery wrapper `jqMix` mixin method is vulnerable to Prototype Pollution.
Affected Area:
```
//https://github.com/dojo/dojox/blob/master/jq.js#L442
var tobj = {};
for(var x in props){
// the "tobj" condition avoid copying properties in "props"
// inherited from Object.prototype. For example, if obj has a custom
// toString() method, don't overwrite it with the toString() method
// that props inherited from Object.prototype
if((tobj[x] === undefined || tobj[x] != props[x]) && props[x] !== undefined && obj != props[x]){
if(dojo.isObject(obj[x]) && dojo.isObject(props[x])){
if(dojo.isArray(props[x])){
obj[x] = props[x];
}else{
obj[x] = jqMix(obj[x], props[x]);
}
}else{
obj[x] = props[x];
}
``` | {'CVE-2020-5259'} | 2021-02-18T19:45:36Z | 2020-03-10T18:03:32Z | LOW | 7.7 | {'CWE-94'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-5259', 'https://github.com/advisories/GHSA-3hw5-q855-g6cw', 'https://github.com/dojo/dojox/security/advisories/GHSA-3hw5-q855-g6cw', 'https://github.com/dojo/dojox/commit/47d1b302b5b23d94e875b77b9b9a8c4f5622c9da', 'https://lists.debian.org/debian-lts-announce/2020/03/msg00012.html'} | null | {'https://github.com/dojo/dojox/commit/47d1b302b5b23d94e875b77b9b9a8c4f5622c9da'} | {'https://github.com/dojo/dojox/commit/47d1b302b5b23d94e875b77b9b9a8c4f5622c9da'} |
GHSA | GHSA-4hpf-3wq7-5rpr | Regular expression deinal of service (ReDoS) in is-my-json-valid | It was discovered that the is-my-json-valid JavaScript library used an inefficient regular expression to validate JSON fields defined to have email format. A specially crafted JSON file could cause it to consume an excessive amount of CPU time when validated. | {'CVE-2018-1107'} | 2022-01-06T20:44:07Z | 2022-01-06T20:44:07Z | MODERATE | 5.3 | {'CWE-400'} | {'https://github.com/advisories/GHSA-4hpf-3wq7-5rpr', 'https://bugzilla.redhat.com/show_bug.cgi?id=1546357', 'https://github.com/mafintosh/is-my-json-valid/commit/b3051b277f7caa08cd2edc6f74f50aeda65d2976', 'https://nvd.nist.gov/vuln/detail/CVE-2018-1107', 'https://github.com/mafintosh/is-my-json-valid/pull/159', 'https://snyk.io/vuln/npm:is-my-json-valid:20180214'} | null | {'https://github.com/mafintosh/is-my-json-valid/commit/b3051b277f7caa08cd2edc6f74f50aeda65d2976'} | {'https://github.com/mafintosh/is-my-json-valid/commit/b3051b277f7caa08cd2edc6f74f50aeda65d2976'} |
GHSA | GHSA-x8wj-6m73-gfqp | Relative Path Traversal (CWE-23) in chunked uploads in oneup/uploader-bundle | ### Impact
The vulnerability was identified in the web service for a chunked file
upload. While the names of the POST parameters vary with the used
frontend, their values are always used in the same way to build a path
where the chunks are stored and assembled temporarily. By not validating
these parameters properly, OneupUploaderBundle is susceptible to a path
traversal vulnerability which can be exploited to upload files to
arbitrary folders on the filesystem. The assembly process can further be
misused with some restrictions to delete and copy files to other
locations.
The vulnerability can be exploited by any users that have legitimate
access to the upload functionality and can lead to arbitrary code
execution, denial of service and disclosure of confidential information.
### Patches
Yes, see version 1.9.3 and 2.1.5.
### References
https://owasp.org/www-community/attacks/Path_Traversal
### Credits:
This security vulnerability was found by Thibaud Kehler of SySS GmbH.
E-Mail: thibaud.kehler@syss.de | {'CVE-2020-5237'} | 2022-01-04T19:45:22Z | 2020-02-18T18:59:24Z | HIGH | 8.8 | {'CWE-23', 'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-5237', 'https://github.com/1up-lab/OneupUploaderBundle/commit/a6011449b716f163fe1ae323053077e59212350c', 'https://github.com/1up-lab/OneupUploaderBundle/security/advisories/GHSA-x8wj-6m73-gfqp', 'https://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2020-003.txt', 'https://github.com/advisories/GHSA-x8wj-6m73-gfqp'} | null | {'https://github.com/1up-lab/OneupUploaderBundle/commit/a6011449b716f163fe1ae323053077e59212350c'} | {'https://github.com/1up-lab/OneupUploaderBundle/commit/a6011449b716f163fe1ae323053077e59212350c'} |
GHSA | GHSA-jcxc-rh6w-wf49 | Link Following in Iris | This affects all versions of package github.com/kataras/iris; all versions of package github.com/kataras/iris/v12. The unsafe handling of file names during upload using UploadFormFiles method may enable attackers to write to arbitrary locations outside the designated target folder. | {'CVE-2021-23772'} | 2022-04-01T21:02:48Z | 2022-01-06T21:36:19Z | HIGH | 7.5 | {'CWE-59'} | {'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMKATARASIRIS-2325169', 'https://github.com/kataras/iris/commit/e213dba0d32ff66653e0ef124bc5088817264b08', 'https://github.com/advisories/GHSA-jcxc-rh6w-wf49', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMKATARASIRISV12-2325170', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23772'} | null | {'https://github.com/kataras/iris/commit/e213dba0d32ff66653e0ef124bc5088817264b08'} | {'https://github.com/kataras/iris/commit/e213dba0d32ff66653e0ef124bc5088817264b08'} |
GHSA | GHSA-xh99-hw7h-wf63 | Unchecked validity of Facing values in PlayerActionPacket | ### Impact
A remote attacker may crash a server by sending `PlayerActionPacket` with invalid facing values (e.g. negative), specifically with `START_BREAK` or `CRACK_BLOCK` actions, or with a `UseItemTransactionData` (typically in `InventoryTransactionPacket`).
### Patches
f126479c37ff00a717a828f5271cf8e821d12d6c
### Workarounds
Using a plugin, cancel `DataPacketReceiveEvent` if the packet is `PlayerActionPacket` and the facing is outside the range 0-5 when receiving START_BREAK or CRACK_BLOCK actions, or UseItemTransactionData. However, beware that negative values may be legitimate in some cases.
### For more information
If you have any questions or comments about this advisory:
* Email us at [team@pmmp.io](mailto:team@pmmp.io)
| null | 2022-01-13T22:25:44Z | 2022-01-13T22:25:44Z | HIGH | 7.5 | null | {'https://github.com/advisories/GHSA-xh99-hw7h-wf63', 'https://github.com/pmmp/PocketMine-MP/security/advisories/GHSA-xh99-hw7h-wf63', 'https://github.com/pmmp/PocketMine-MP/commit/f126479c37ff00a717a828f5271cf8e821d12d6c'} | null | {'https://github.com/pmmp/PocketMine-MP/commit/f126479c37ff00a717a828f5271cf8e821d12d6c'} | {'https://github.com/pmmp/PocketMine-MP/commit/f126479c37ff00a717a828f5271cf8e821d12d6c'} |
GHSA | GHSA-qw36-p97w-vcqr | Cookie persistence after password changes in symfony/security-bundle | Description
-----------
Since the rework of the Remember me cookie in Symfony 5.3, the cookie is not invalidated anymore when the user changes its password.
Attackers can therefore maintain their access to the account even if the password is changed as long as they have had the chance to login once and get a valid remember me cookie.
Resolution
----------
Symfony now makes the password part of the signature by default. In that way, when the password changes then the cookie is not valid anymore.
The patch for this issue is available [here](https://github.com/symfony/symfony/commit/36a808b857cd3240244f4b224452fb1e70dc6dfc) for branch 5.3.
Credits
-------
We would like to thank Thibaut Decherit for reporting the issue and Wouter J for fixing the issue.
| {'CVE-2021-41268'} | 2022-04-19T19:03:15Z | 2021-11-24T20:05:22Z | MODERATE | 6.5 | {'CWE-384'} | {'https://github.com/symfony/symfony/pull/44243', 'https://github.com/advisories/GHSA-qw36-p97w-vcqr', 'https://github.com/symfony/symfony/security/advisories/GHSA-qw36-p97w-vcqr', 'https://github.com/symfony/symfony/releases/tag/v5.3.12', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41268', 'https://github.com/symfony/symfony/commit/36a808b857cd3240244f4b224452fb1e70dc6dfc'} | null | {'https://github.com/symfony/symfony/commit/36a808b857cd3240244f4b224452fb1e70dc6dfc'} | {'https://github.com/symfony/symfony/commit/36a808b857cd3240244f4b224452fb1e70dc6dfc'} |
GHSA | GHSA-jh5x-hfhg-78jq | Deserialization of Untrusted Data in Archive_Tar | Archive_Tar through 1.4.10 allows an unserialization attack because phar: is blocked but PHAR: is not blocked. See: https://github.com/pear/Archive_Tar/issues/33 | {'CVE-2020-28948'} | 2022-04-01T18:11:12Z | 2021-04-22T16:20:50Z | HIGH | 7.8 | {'CWE-502'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VJQQYDAOWHD6RDITDRPHFW7WY6BS3V5N/', 'https://github.com/pear/Archive_Tar/issues/33', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28948', 'https://www.drupal.org/sa-core-2020-013', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/42GPGVVFTLJYAKRI75IVB5R45NYQGEUR/', 'https://github.com/advisories/GHSA-jh5x-hfhg-78jq', 'https://github.com/pear/Archive_Tar/commit/0670a05fdab997036a3fc3ef113b8f5922e574da', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NBYZSHYTIOBK6V7C4N7TP6KIKCRKLVWP/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5KSFM672XW3X6BR7TVKRD63SLZGKK437/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4V35LBRM6HBCXBVCITKQ4UEBTXO2EG7B/', 'https://www.debian.org/security/2020/dsa-4817', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KWM4CTMEGAC4I2CHYNJVSROY4CVXVEUT/', 'https://lists.debian.org/debian-lts-announce/2020/11/msg00045.html', 'https://security.gentoo.org/glsa/202101-23'} | null | {'https://github.com/pear/Archive_Tar/commit/0670a05fdab997036a3fc3ef113b8f5922e574da'} | {'https://github.com/pear/Archive_Tar/commit/0670a05fdab997036a3fc3ef113b8f5922e574da'} |
GHSA | GHSA-5p3x-r448-pc62 | Improper Verification of Cryptographic Signature in PySAML2 | ### Impact
All users of pysaml2 that use the default `CryptoBackendXmlSec1` backend and need to verify signed SAML documents are impacted. `pysaml2 <= 6.4.1` does not ensure that a signed SAML document is correctly signed. The default `CryptoBackendXmlSec1` backend is using the `xmlsec1` binary to verify the signature of signed SAML documents, but by default, `xmlsec1` accepts any type of key found within the given document. `xmlsec1` needs to be configured explicitly to only use only _x509 certificates_ for the verification process of the SAML document signature.
### Patches
Users should upgrade to pysaml2 `v6.5.0`.
### Workarounds
No workaround provided at this point.
### References
This issue has been reported in the past at the xmlsec1 mailing list:
https://www.aleksey.com/pipermail/xmlsec/2013/009717.html
### Credits
- Brian Wolff
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [pysaml2](https://github.com/IdentityPython/pysaml2)
* Email us at [the incident-response address](mailto:incident-response@idpy.org) | {'CVE-2021-21239'} | 2021-03-01T18:55:05Z | 2021-01-21T14:12:18Z | LOW | 6.5 | {'CWE-347'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-21239', 'https://github.com/IdentityPython/pysaml2/commit/46578df0695269a16f1c94171f1429873f90ed99', 'https://github.com/IdentityPython/pysaml2/security/advisories/GHSA-5p3x-r448-pc62', 'https://pypi.org/project/pysaml2', 'https://www.aleksey.com/pipermail/xmlsec/2013/009717.html', 'https://github.com/IdentityPython/pysaml2/releases/tag/v6.5.0', 'https://github.com/advisories/GHSA-5p3x-r448-pc62', 'https://lists.debian.org/debian-lts-announce/2021/02/msg00038.html'} | null | {'https://github.com/IdentityPython/pysaml2/commit/46578df0695269a16f1c94171f1429873f90ed99'} | {'https://github.com/IdentityPython/pysaml2/commit/46578df0695269a16f1c94171f1429873f90ed99'} |
GHSA | GHSA-8wcc-f2vq-h4gx | Cross-site Scripting in livehelperchat | Stored XSS is found in Settings>Live help configuration>Personal Theme>static content. Under the NAME field put a payload {{constructor.constructor('alert(1)')()}} while creating content, and you will see that the input gets stored, and every time the user visits, the payload gets executed. | {'CVE-2022-0370'} | 2022-02-03T20:34:04Z | 2022-01-28T23:06:22Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/advisories/GHSA-8wcc-f2vq-h4gx', 'https://github.com/livehelperchat/livehelperchat/commit/9f5bc33c943349bd765b991db0b7f6b6ef05cfdb', 'https://huntr.dev/bounties/fbe4b376-57ce-42cd-a9a9-049c4099b3ca', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0370'} | null | {'https://github.com/livehelperchat/livehelperchat/commit/9f5bc33c943349bd765b991db0b7f6b6ef05cfdb'} | {'https://github.com/livehelperchat/livehelperchat/commit/9f5bc33c943349bd765b991db0b7f6b6ef05cfdb'} |
GHSA | GHSA-x3rh-m7vp-35f2 | Operation on a Resource after Expiration or Release in Jetty Server | In Eclipse Jetty, versions 9.4.27.v20200227 to 9.4.29.v20200521, in case of too large response headers, Jetty throws an exception to produce an HTTP 431 error. When this happens, the ByteBuffer containing the HTTP response headers is released back to the ByteBufferPool twice. Because of this double release, two threads can acquire the same ByteBuffer from the pool and while thread1 is about to use the ByteBuffer to write response1 data, thread2 fills the ByteBuffer with response2 data. Thread1 then proceeds to write the buffer that now contains response2 data. This results in client1, which issued request1 and expects responses, to see response2 which could contain sensitive data belonging to client2 (HTTP session ids, authentication credentials, etc.). | {'CVE-2019-17638'} | 2021-06-15T18:11:20Z | 2020-08-05T14:52:59Z | CRITICAL | 9.4 | {'CWE-675', 'CWE-672'} | {'https://github.com/advisories/GHSA-x3rh-m7vp-35f2', 'https://lists.apache.org/thread.html/r521168299e023fb075b57afe33d17ff1d09e8a10e0fd8c775ea0e028@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/r9a2cfa56d30782a0c17a5deb951a622d1f5c8de48e1c3b578ffc2a84@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/r29073905dc9139d0d7a146595694bf57bb9e35e5ec6aa73eb9c8443a@%3Ccommits.pulsar.apache.org%3E', 'https://bugs.eclipse.org/bugs/show_bug.cgi?id=564984', 'https://lists.apache.org/thread.html/r378e4cdec15e132575aa1dcb6296ffeff2a896745a8991522e266ad4@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/ra8661fc8c69c647cb06153c1485d48484a833d873f75dfe45937e9de@%3Ccommits.pulsar.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://nvd.nist.gov/vuln/detail/CVE-2019-17638', 'https://github.com/eclipse/jetty.project/issues/4936', 'https://snyk.io/vuln/SNYK-JAVA-ORGECLIPSEJETTY-575561', 'https://lists.apache.org/thread.html/r4bdd3f7bb6820a79f9416b6667d718a06d269018619a75ce4b759318@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/r7fc5f2ed49641ea91c433e3cd0fc3d31c0278c87b82b15c33b881415@%3Ccommits.pulsar.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://lists.apache.org/thread.html/rbe1f230e87ea947593145d0072d0097ddb0af10fee1161db8ca1546c@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/r9584c4304c888f651d214341a939bd264ed30c9e3d0d30fe85097ecf@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/rd98cfd012490cb02caa1a11aaa0cc38bff2d43bcce9b20c2f01063dd@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/rd0e44e8ef71eeaaa3cf3d1b8b41eb25894372e2995ec908ce7624d26@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/r81f58591fb4716fb867b36956f30c7c8ad4ab3f23abc952d9d86a2a0@%3Ccommits.pulsar.apache.org%3E', 'http://www.openwall.com/lists/oss-security/2020/08/17/1', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XE6US6VPZHOWFMUSFGDS5V2DNQPY5MKB/', 'https://github.com/eclipse/jetty.project/commit/ff8ae56fa939c3477a0cdd1ff56ce3d902f08fba'} | null | {'https://github.com/eclipse/jetty.project/commit/ff8ae56fa939c3477a0cdd1ff56ce3d902f08fba'} | {'https://github.com/eclipse/jetty.project/commit/ff8ae56fa939c3477a0cdd1ff56ce3d902f08fba'} |
GHSA | GHSA-pg59-2f92-5cph | Heap buffer overflow in Tensorflow | ### Impact
The `SparseCountSparseOutput` and `RaggedCountSparseOutput` implementations don't validate that the `weights` tensor has the same shape as the data. The check exists for `DenseCountSparseOutput`, where both tensors are fully specified:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L110-L117
In the sparse and ragged count weights are still accessed in parallel with the data:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L199-L201
But, since there is no validation, a user passing fewer weights than the values for the tensors can generate a read from outside the bounds of the heap buffer allocated for the weights.
### Patches
We have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release.
We recommend users to upgrade to TensorFlow 2.3.1.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability is a variant of [GHSA-p5f8-gfw5-33w4](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4) | {'CVE-2020-15196'} | 2021-11-19T15:20:13Z | 2020-09-25T18:28:21Z | HIGH | 8.5 | {'CWE-119', 'CWE-122', 'CWE-125'} | {'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15196', 'https://github.com/advisories/GHSA-pg59-2f92-5cph', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-pg59-2f92-5cph', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1'} | null | {'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02'} | {'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02'} |
GHSA | GHSA-5p9j-w2wx-qx4c | Open Redirect in django-spirit | django-spirit prior to version 0.12.3 is vulnerable to open redirect. In the /user/login endpoint, it doesn't check the value of the next parameter when the user is logged in and passes it directly to redirect which result to open redirect. This also affects /user/logout, /user/register, /user/login, /user/resend-activation. | {'CVE-2022-0869'} | 2022-03-14T21:19:29Z | 2022-03-07T00:00:40Z | MODERATE | 6.1 | {'CWE-601'} | {'https://github.com/advisories/GHSA-5p9j-w2wx-qx4c', 'https://huntr.dev/bounties/ed335a88-f68c-4e4d-ac85-f29a51b03342', 'https://github.com/nitely/spirit/commit/8f32f89654d6c30d56e0dd167059d32146fb32ef', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0869'} | null | {'https://github.com/nitely/spirit/commit/8f32f89654d6c30d56e0dd167059d32146fb32ef'} | {'https://github.com/nitely/spirit/commit/8f32f89654d6c30d56e0dd167059d32146fb32ef'} |
GHSA | GHSA-6h7w-fc84-x7p6 | StaticFile.fromUrl can leak presence of a directory | ### Impact
`StaticFile.fromUrl` can leak the presence of a directory on a server when the `URL` scheme is not `file://`, and the URL points to a fetchable resource under its scheme and authority. The function returns `F[None]`, indicating no resource, if `url.getFile` is a directory, without first checking the scheme or authority of the URL. If a URL connection to the scheme and URL would return a stream, and the path in the URL exists as a directory on the server, the presence of the directory on the server could be inferred from the 404 response. The contents and other metadata about the directory are not exposed.
This affects http4s versions:
* 0.21.7 through 0.21.23
* 0.22.0-M1 through 0.22.0-M8
* 0.23.0-M1
* 1.0.0-M1 through 1.0.0-M22
### Patches
The [patch](https://github.com/http4s/http4s/commit/52e1890665410b4385e37b96bc49c5e3c708e4e9) is available in the following versions:
* v0.21.24
* v0.22.0-RC1
* v0.23.0-RC1
* v1.0.0-M23
Note: a previous version of this advisory incorrectly referred to 0.22.0-M9 and 0.23.0-M2.
### Workarounds
Don't call `StaticFile.fromUrl` with non-file URLs.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the http4s repository](https://github.com/http4s/http4s)
* Disclose further vulnerabilities according to the [http4s security policy](https://github.com/http4s/http4s/blob/main/SECURITY.md)
| {'CVE-2021-32643'} | 2021-05-28T15:54:39Z | 2021-05-28T15:54:39Z | MODERATE | 5.8 | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-32643', 'https://mvnrepository.com/artifact/org.http4s/http4s-core', 'https://github.com/http4s/http4s/commit/52e1890665410b4385e37b96bc49c5e3c708e4e9', 'https://github.com/advisories/GHSA-6h7w-fc84-x7p6', 'https://github.com/http4s/http4s/security/advisories/GHSA-6h7w-fc84-x7p6'} | null | {'https://github.com/http4s/http4s/commit/52e1890665410b4385e37b96bc49c5e3c708e4e9'} | {'https://github.com/http4s/http4s/commit/52e1890665410b4385e37b96bc49c5e3c708e4e9'} |
GHSA | GHSA-8c8c-4vfj-rrpc | Reflected Cross-Site Scripting in redis-commander | Affected versions of `redis-commander` contain a cross-site scripting vulnerability in the `highlighterId` paramter of the clipboard.swf component on hosts serving Redis Commander.
Mitigating factors:
Flash must be installed / enabled for this to work. The below proof of concept was verified to work using Firefox 57.0 on Windows 10 by manually installing the [Flash NPAPI Windows plugin](https://get.adobe.com/flashplayer/otherversions/)
## Proof of concept
```
http://instance/jstree/_docs/syntax/clipboard.swf?highlighterId=\%22))}%20catch(e)%20{alert(document.domain);}//
```
## Recommendation
No direct patch for this vulnerability is currently available.
At this time, the best mitigation is to use an alternative, functionally equivalent package, or to use extreme caution when using redis-commander, ensuring that redis-commmander is the only web page you have open, and avoiding clicking on any links. | null | 2022-04-19T19:03:26Z | 2020-09-01T19:05:11Z | LOW | 0 | {'CWE-79'} | {'https://www.npmjs.com/advisories/562', 'https://github.com/joeferner/redis-commander/commit/1a483ebb3a706cf199dd283cf0aead96606adb14', 'https://github.com/advisories/GHSA-8c8c-4vfj-rrpc', 'https://hackerone.com/reports/296377', 'https://github.com/joeferner/redis-commander/releases/tag/v0.5.0'} | null | {'https://github.com/joeferner/redis-commander/commit/1a483ebb3a706cf199dd283cf0aead96606adb14'} | {'https://github.com/joeferner/redis-commander/commit/1a483ebb3a706cf199dd283cf0aead96606adb14'} |
GHSA | GHSA-c697-r227-pq6h | Unrestricted Upload of File with Dangerous Type in pimcore | Unrestricted Upload of File with Dangerous Type in Packagist pimcore/pimcore | {'CVE-2022-0263'} | 2022-01-25T20:47:42Z | 2022-01-21T23:33:58Z | HIGH | 7.8 | {'CWE-434'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0263', 'https://github.com/advisories/GHSA-c697-r227-pq6h', 'https://huntr.dev/bounties/96506857-06bc-4c84-88b7-4f397715bcf6', 'https://github.com/pimcore/pimcore/commit/35d1853baf64d6a1d90fd8803e52439da53a3911'} | null | {'https://github.com/pimcore/pimcore/commit/35d1853baf64d6a1d90fd8803e52439da53a3911'} | {'https://github.com/pimcore/pimcore/commit/35d1853baf64d6a1d90fd8803e52439da53a3911'} |
GHSA | GHSA-4fx9-vc88-q2xc | Infinite loop in Pillow | JpegImagePlugin may append an EOF marker to the end of a truncated file, so that the last segment of the data will still be processed by the decoder.
If the EOF marker is not detected as such however, this could lead to an infinite loop where JpegImagePlugin keeps trying to end the file. | null | 2022-03-11T23:39:41Z | 2022-03-11T23:39:27Z | LOW | 0 | {'CWE-400'} | {'https://github.com/python-pillow/Pillow/commit/baae9ec4b67c68e3adaf1208cf54e8de5e38a6fd', 'https://pillow.readthedocs.io/en/stable/releasenotes/9.0.0.html#ensure-jpegimageplugin-stops-at-the-end-of-a-truncated-file', 'https://github.com/advisories/GHSA-4fx9-vc88-q2xc'} | null | {'https://github.com/python-pillow/Pillow/commit/baae9ec4b67c68e3adaf1208cf54e8de5e38a6fd'} | {'https://github.com/python-pillow/Pillow/commit/baae9ec4b67c68e3adaf1208cf54e8de5e38a6fd'} |
GHSA | GHSA-cff7-6h4q-q5pj | Lacked element count during splitting of JWE string | The json-jwt gem before 1.11.0 for Ruby lacks an element count during the splitting of a JWE string. | {'CVE-2019-18848'} | 2022-05-04T01:52:59Z | 2019-11-14T15:25:51Z | HIGH | 7.5 | {'CWE-287', 'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-18848', 'https://lists.debian.org/debian-lts-announce/2020/10/msg00001.html', 'https://github.com/nov/json-jwt/compare/v1.10.2...v1.11.0', 'https://github.com/nov/json-jwt/commit/ada16e772906efdd035e3df49cb2ae372f0f948a', 'https://github.com/advisories/GHSA-cff7-6h4q-q5pj'} | null | {'https://github.com/nov/json-jwt/commit/ada16e772906efdd035e3df49cb2ae372f0f948a'} | {'https://github.com/nov/json-jwt/commit/ada16e772906efdd035e3df49cb2ae372f0f948a'} |
GHSA | GHSA-35g4-qx3c-vjhx | Automatic room upgrade handling can be used maliciously to bridge a room non-consentually | ### Impact
If a bridge has room upgrade handling turned on in the configuration (the `roomUpgradeOpts` key when instantiating a new `Bridge` instance.), any `m.room.tombstone` event it encounters will be used to unbridge the current room and bridge into the target room. However, the target room `m.room.create` event is not checked to verify if the `predecessor` field contains the previous room. This means that any mailcious admin of a bridged room can repoint the traffic to a different room without the new room being aware.
### Patches
Versions 2.6.1 and greater are patched.
### Workarounds
Disabling the automatic room upgrade handling can be done by removing the `roomUpgradeOpts` key from the `Bridge` class options.
### References
The issue is patched by https://github.com/matrix-org/matrix-appservice-bridge/pull/330
### For more information]
If you have any questions or comments about this advisory, email us at security@matrix.org. | {'CVE-2021-32659'} | 2021-06-21T17:09:22Z | 2021-06-21T17:09:22Z | MODERATE | 6.5 | {'CWE-306'} | {'https://github.com/matrix-org/matrix-appservice-bridge/releases/tag/2.6.1', 'https://github.com/advisories/GHSA-35g4-qx3c-vjhx', 'https://github.com/matrix-org/matrix-appservice-bridge/commit/b69e745584a34fcfd858df33e4631e420da07b9f', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32659', 'https://github.com/matrix-org/matrix-appservice-bridge/pull/330', 'https://github.com/matrix-org/matrix-appservice-bridge/security/advisories/GHSA-35g4-qx3c-vjhx'} | null | {'https://github.com/matrix-org/matrix-appservice-bridge/commit/b69e745584a34fcfd858df33e4631e420da07b9f'} | {'https://github.com/matrix-org/matrix-appservice-bridge/commit/b69e745584a34fcfd858df33e4631e420da07b9f'} |
GHSA | GHSA-6vfc-qv3f-vr6c | Uncontrolled Resource Consumption in markdown-it | ### Impact
Special patterns with length > 50K chars can slow down parser significantly.
```js
const md = require('markdown-it')();
md.render(`x ${' '.repeat(150000)} x \nx`);
```
### Patches
Upgrade to v12.3.2+
### Workarounds
No.
### References
Fix + test sample: https://github.com/markdown-it/markdown-it/commit/ffc49ab46b5b751cd2be0aabb146f2ef84986101
| {'CVE-2022-21670'} | 2022-04-19T19:03:19Z | 2022-01-12T22:20:22Z | MODERATE | 5.3 | {'CWE-400'} | {'https://github.com/markdown-it/markdown-it/commit/ffc49ab46b5b751cd2be0aabb146f2ef84986101', 'https://github.com/advisories/GHSA-6vfc-qv3f-vr6c', 'https://github.com/markdown-it/markdown-it/security/advisories/GHSA-6vfc-qv3f-vr6c', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21670'} | null | {'https://github.com/markdown-it/markdown-it/commit/ffc49ab46b5b751cd2be0aabb146f2ef84986101'} | {'https://github.com/markdown-it/markdown-it/commit/ffc49ab46b5b751cd2be0aabb146f2ef84986101'} |
GHSA | GHSA-j9xp-92vc-559j | SQL Injection in sequelize | Affected versions of `sequelize` are vulnerable to SQL Injection. The package fails to sanitize JSON path keys in the MariaDB and MySQL dialects, which may allow attackers to inject SQL statements and execute arbitrary SQL queries.
## Recommendation
If you are using `sequelize` 5.x, upgrade to version 5.8.11 or later.
If you are using `sequelize` 4.x, upgrade to version 4.44.3 or later.
If you are using `sequelize` 3.x, upgrade to version 3.35.1 or later. | {'CVE-2019-10748'} | 2021-08-18T22:09:34Z | 2019-11-06T17:11:10Z | CRITICAL | 9.8 | {'CWE-89'} | {'https://github.com/advisories/GHSA-j9xp-92vc-559j', 'https://github.com/sequelize/sequelize/pull/11089,', 'https://www.npmjs.com/advisories/1018', 'https://snyk.io/vuln/SNYK-JS-SEQUELIZE-450221', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10748', 'https://github.com/sequelize/sequelize/commit/a72a3f5,'} | null | {'https://github.com/sequelize/sequelize/commit/a72a3f5,'} | {'https://github.com/sequelize/sequelize/commit/a72a3f5,'} |
GHSA | GHSA-7v5r-r995-q2x2 | SSRF in repository migration | Gogs is a self-hosted Git service. The malicious user is able to discover services in the internal network through repository migration functionality. All installations accepting public traffic are affected. Internal network CIDRs are prohibited to be used as repository migration targets. Users should upgrade to 0.12.5 or the latest 0.13.0+dev. Gogs should be ran in its own private network until users can update. | {'CVE-2022-0870'} | 2022-03-24T23:23:22Z | 2022-03-12T00:00:34Z | MODERATE | 5 | {'CWE-918'} | {'https://huntr.dev/bounties/327797d7-ae41-498f-9bff-cc0bf98cf531', 'https://github.com/gogs/gogs/commit/91f2cde5e95f146bfe4765e837e7282df6c7cabb', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0870', 'https://github.com/advisories/GHSA-7v5r-r995-q2x2'} | null | {'https://github.com/gogs/gogs/commit/91f2cde5e95f146bfe4765e837e7282df6c7cabb'} | {'https://github.com/gogs/gogs/commit/91f2cde5e95f146bfe4765e837e7282df6c7cabb'} |
GHSA | GHSA-49r3-3h96-rwj6 | Cross-Site Scripting in ids-enterprise | Versions of `ids-enterprise` prior to 4.18.2 are vulnerable to Cross-Site Scripting (XSS). The `soho-dropdown` component does not properly encode its output and may allow attackers to execute arbitrary JavaScript.
## Recommendation
Upgrade to version 4.18.2 or later | null | 2021-08-16T15:19:11Z | 2019-06-13T19:09:31Z | HIGH | 0 | {'CWE-79'} | {'https://www.npmjs.com/advisories/956', 'https://github.com/infor-design/enterprise-ng/issues/503', 'https://github.com/advisories/GHSA-49r3-3h96-rwj6', 'https://github.com/infor-design/enterprise/commit/6bd74d8f38c268b22f31e8169316e065e0093362'} | null | {'https://github.com/infor-design/enterprise/commit/6bd74d8f38c268b22f31e8169316e065e0093362'} | {'https://github.com/infor-design/enterprise/commit/6bd74d8f38c268b22f31e8169316e065e0093362'} |
GHSA | GHSA-673j-qm5f-xpv8 | Arbitrary File Write Vulnerability | ### Overview
The connection properties for configuring a pgjdbc connection are not meant to be exposed to an unauthenticated attacker. While allowing an attacker to specify arbitrary connection properties could lead to a compromise of a system, that's a defect of an application that allows unauthenticated attackers that level of control.
It's not the job of the pgjdbc driver to decide whether a given log file location is acceptable. End user applications that use the pgjdbc driver must ensure that filenames are valid and restrict unauthenticated attackers from being able to supply arbitrary values. That's not specific to the pgjdbc driver either, it would be true for any library that can write to the application's local file system.
While we do not consider this a security issue with the driver, we have decided to remove the loggerFile and loggerLevel connection properties in the next release of the driver. Removal of those properties does not make exposing the JDBC URL or connection properties to an attacker safe and we continue to suggest that applications do not allow untrusted users to specify arbitrary connection properties. We are removing them to prevent misuse and their functionality can be delegated to java.util.logging.
If you identify an application that allows remote users to specify a complete JDBC URL or properties without validating it's contents, we encourage you to notify the application owner as that may be a security defect in that specific application.
### Impact
It is possible to specify an arbitrary filename in the loggerFileName connection parameter
"jdbc:postgresql://localhost:5432/test?user=test&password=test&loggerLevel=DEBUG&loggerFile=./blah.jsp&<%Runtime.getRuntime().exec(request.getParameter(\"i\"));%>"
This creates a valid JSP file which could lead to a Remote Code Execution
### Patches
Problem has been resolved in version 42.3.3
### Workarounds
sanitize the inputs to the driver
| null | 2022-02-16T00:32:02Z | 2022-02-16T00:08:18Z | MODERATE | 0 | null | {'https://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-673j-qm5f-xpv8', 'https://github.com/pgjdbc/pgjdbc/commit/f6d47034a4ce292e1a659fa00963f6f713117064', 'https://github.com/advisories/GHSA-673j-qm5f-xpv8'} | null | {'https://github.com/pgjdbc/pgjdbc/commit/f6d47034a4ce292e1a659fa00963f6f713117064'} | {'https://github.com/pgjdbc/pgjdbc/commit/f6d47034a4ce292e1a659fa00963f6f713117064'} |
GHSA | GHSA-jq7p-26h5-w78r | Out-of-bounds read in Apache Thrift | In Apache Thrift 0.9.3 to 0.12.0, a server implemented in Go using TJSONProtocol or TSimpleJSONProtocol may panic when feed with invalid input data. | {'CVE-2019-0210'} | 2021-07-27T22:20:55Z | 2021-05-18T15:32:04Z | HIGH | 7.5 | {'CWE-125'} | {'https://lists.apache.org/thread.html/r2832722c31d78bef7526e2c701ba4b046736e4c851473194a247392f@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/rab740e5c70424ef79fd095a4b076e752109aeee41c4256c2e5e5e142@%3Ccommits.pulsar.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2020:0806', 'https://security.gentoo.org/glsa/202107-32', 'https://github.com/apache/thrift/blob/master/CHANGES.md#0130', 'https://lists.apache.org/thread.html/r36581cc7047f007dd6aadbdd34e18545ec2c1eb7ccdae6dd47a877a9@%3Ccommits.pulsar.apache.org%3E', 'https://github.com/apache/thrift/commit/264a3f318ed3e9e51573f67f963c8509786bcec2', 'https://access.redhat.com/errata/RHSA-2020:0804', 'https://access.redhat.com/errata/RHSA-2020:0811', 'http://mail-archives.apache.org/mod_mbox/thrift-dev/201910.mbox/%3C277A46CA87494176B1BBCF5D72624A2A%40HAGGIS%3E', 'https://github.com/advisories/GHSA-jq7p-26h5-w78r', 'https://nvd.nist.gov/vuln/detail/CVE-2019-0210', 'https://access.redhat.com/errata/RHSA-2020:0805', 'https://lists.apache.org/thread.html/r55609613abab203a1f2c1f3de050b63ae8f5c4a024df0d848d6915ff@%3Ccommits.pulsar.apache.org%3E'} | null | {'https://github.com/apache/thrift/commit/264a3f318ed3e9e51573f67f963c8509786bcec2'} | {'https://github.com/apache/thrift/commit/264a3f318ed3e9e51573f67f963c8509786bcec2'} |
GHSA | GHSA-q8pj-2vqx-8ggc | Denial of service in css-what | The css-what package 4.0.0 through 5.0.0 for Node.js does not ensure that attribute parsing has Linear Time Complexity relative to the size of the input. | {'CVE-2021-33587'} | 2021-12-02T17:48:50Z | 2021-06-07T22:11:39Z | HIGH | 7.5 | {'CWE-400'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-33587', 'https://github.com/advisories/GHSA-q8pj-2vqx-8ggc', 'https://github.com/fb55/css-what/releases/tag/v5.0.1', 'https://github.com/fb55/css-what/commit/4cdaacfd0d4b6fd00614be030da0dea6c2994655', 'https://security.netapp.com/advisory/ntap-20210706-0007/'} | null | {'https://github.com/fb55/css-what/commit/4cdaacfd0d4b6fd00614be030da0dea6c2994655'} | {'https://github.com/fb55/css-what/commit/4cdaacfd0d4b6fd00614be030da0dea6c2994655'} |
GHSA | GHSA-85r7-w5mv-c849 | Moderate severity vulnerability that affects rack | rack/file.rb (Rack::File) in Rack 1.5.x before 1.5.2 and 1.4.x before 1.4.5 allows attackers to access arbitrary files outside the intended root directory via a crafted PATH_INFO environment variable, probably a directory traversal vulnerability that is remotely exploitable, aka "symlink path traversals." | {'CVE-2013-0262'} | 2021-09-03T22:59:00Z | 2017-10-24T18:33:37Z | MODERATE | 0 | {'CWE-22'} | {'http://secunia.com/advisories/52033', 'https://gist.github.com/rentzsch/4736940', 'https://github.com/advisories/GHSA-85r7-w5mv-c849', 'https://nvd.nist.gov/vuln/detail/CVE-2013-0262', 'https://bugzilla.redhat.com/show_bug.cgi?id=909071', 'http://rack.github.com/', 'https://groups.google.com/forum/#!msg/rack-devel/bf937jPZxJM/1s6x95vIhmAJ', 'https://bugzilla.redhat.com/show_bug.cgi?id=909072', 'https://github.com/rack/rack/blob/master/lib/rack/file.rb#L56', 'http://lists.opensuse.org/opensuse-updates/2013-03/msg00048.html', 'https://groups.google.com/forum/#!msg/rack-devel/mZsuRonD7G8/DpZIOmMLbOgJ', 'https://github.com/rack/rack/commit/6f237e4c9fab649d3750482514f0fde76c56ab30'} | null | {'https://github.com/rack/rack/commit/6f237e4c9fab649d3750482514f0fde76c56ab30'} | {'https://github.com/rack/rack/commit/6f237e4c9fab649d3750482514f0fde76c56ab30'} |
GHSA | GHSA-gp6w-ccqv-p7qr | firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF) | firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF) | {'CVE-2021-3729'} | 2021-08-25T14:49:58Z | 2021-08-25T14:49:58Z | MODERATE | 4.3 | {'CWE-352'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-3729', 'https://huntr.dev/bounties/d32f3d5a-0738-41ba-89de-34f2a772de76', 'https://github.com/firefly-iii/firefly-iii/commit/06d319cd71b7787aa919b3ba1ccf51e4ade67712', 'https://github.com/advisories/GHSA-gp6w-ccqv-p7qr'} | null | {'https://github.com/firefly-iii/firefly-iii/commit/06d319cd71b7787aa919b3ba1ccf51e4ade67712'} | {'https://github.com/firefly-iii/firefly-iii/commit/06d319cd71b7787aa919b3ba1ccf51e4ade67712'} |
GHSA | GHSA-7pr3-p5fm-8r9x | LiveQuery publishes user session tokens in parse-server | ### Impact
For regular (non-LiveQuery) queries, the session token is removed from the response, but for LiveQuery payloads it is currently not. If a user has a LiveQuery subscription on the `Parse.User` class, all session tokens created during user sign-ups will be broadcast as part of the LiveQuery payload.
### Patches
Remove session token from LiveQuery payload.
### Workaround
Set `user.acl(new Parse.ACL())` in a beforeSave trigger to make the user private already on sign-up. | {'CVE-2021-41109'} | 2022-04-19T19:03:10Z | 2021-09-30T17:09:47Z | HIGH | 7.5 | {'CWE-200'} | {'https://github.com/parse-community/parse-server/commit/4ac4b7f71002ed4fbedbb901db1f6ed1e9ac5559', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41109', 'https://github.com/parse-community/parse-server/releases/tag/4.10.4', 'https://github.com/parse-community/parse-server/security/advisories/GHSA-7pr3-p5fm-8r9x', 'https://github.com/advisories/GHSA-7pr3-p5fm-8r9x'} | null | {'https://github.com/parse-community/parse-server/commit/4ac4b7f71002ed4fbedbb901db1f6ed1e9ac5559'} | {'https://github.com/parse-community/parse-server/commit/4ac4b7f71002ed4fbedbb901db1f6ed1e9ac5559'} |
GHSA | GHSA-wcp5-m52f-mhh5 | Improper Restriction of XML External Entity Reference in MPXJ | "MPXJ through 8.1.3 allows XXE attacks. This affects the GanttProjectReader and PhoenixReader components." | {'CVE-2020-25020'} | 2021-05-07T15:54:36Z | 2021-05-07T15:54:36Z | CRITICAL | 9.8 | {'CWE-611'} | {'https://github.com/advisories/GHSA-wcp5-m52f-mhh5', 'https://nvd.nist.gov/vuln/detail/CVE-2020-25020', 'https://github.com/joniles/mpxj/releases/tag/v8.1.4', 'https://github.com/joniles/mpxj/pull/178/commits/c3e457f7a16facfe563eade82b0fa8736a8c96f9', 'https://www.oracle.com/security-alerts/cpujan2021.html'} | null | {'https://github.com/joniles/mpxj/pull/178/commits/c3e457f7a16facfe563eade82b0fa8736a8c96f9'} | {'https://github.com/joniles/mpxj/pull/178/commits/c3e457f7a16facfe563eade82b0fa8736a8c96f9'} |
GHSA | GHSA-wh98-p28r-vrc9 | Exposure of information in Action Pack | ### Impact
Under certain circumstances response bodies will not be closed, for example a [bug in a webserver](https://github.com/puma/puma/pull/2812) or a bug in a Rack middleware. In the event a response is *not* notified of a `close`, `ActionDispatch::Executor` will not know to reset thread local state for the next request. This can lead to data being leaked to subsequent requests, especially when interacting with `ActiveSupport::CurrentAttributes`.
Upgrading to the FIXED versions of Rails will ensure mitigation of this issue even in the context of a buggy webserver or middleware implementation.
### Patches
This has been fixed in Rails 7.0.2.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.
### Workarounds
Upgrading is highly recommended, but to work around this problem the following middleware can be used:
```ruby
class GuardedExecutor < ActionDispatch::Executor
def call(env)
ensure_completed!
super
end
private
def ensure_completed!
@executor.new.complete! if @executor.active?
end
end
# Ensure the guard is inserted before ActionDispatch::Executor
Rails.application.configure do
config.middleware.swap ActionDispatch::Executor, GuardedExecutor, executor
end
``` | {'CVE-2022-23633'} | 2022-04-19T19:03:23Z | 2022-02-11T20:49:14Z | HIGH | 7.4 | {'CWE-200'} | {'http://www.openwall.com/lists/oss-security/2022/02/11/5', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23633', 'https://discuss.rubyonrails.org/t/cve-2022-23633-possible-exposure-of-information-vulnerability-in-action-pack/80016', 'https://github.com/rails/rails/security/advisories/GHSA-wh98-p28r-vrc9', 'https://github.com/advisories/GHSA-wh98-p28r-vrc9', 'https://github.com/rails/rails/commit/f9a2ad03943d5c2ba54e1d45f155442b519c75da', 'https://rubyonrails.org/2022/2/11/Rails-7-0-2-2-6-1-4-6-6-0-4-6-and-5-2-6-2-have-been-released'} | null | {'https://github.com/rails/rails/commit/f9a2ad03943d5c2ba54e1d45f155442b519c75da'} | {'https://github.com/rails/rails/commit/f9a2ad03943d5c2ba54e1d45f155442b519c75da'} |
GHSA | GHSA-hx6g-q9v2-xh7v | Information exposure in elgg | elgg is vulnerable to Exposure of Private Personal Information to an Unauthorized Actor. Forms in the view namespace 'forms/admin' were not protected by an AdminGatekeeper in case of AJAX requests to 'ajax/form/admin/'. | {'CVE-2021-3980'} | 2021-12-16T15:30:48Z | 2021-12-16T15:30:48Z | HIGH | 7.5 | {'CWE-359'} | {'https://github.com/advisories/GHSA-hx6g-q9v2-xh7v', 'https://github.com/elgg/elgg/commit/572d210e2392f1fdf47ff2f38665372a6535c126', 'https://huntr.dev/bounties/1f43f11e-4bd8-451f-a244-dc9541cdc0ac', 'https://github.com/Elgg/Elgg/pull/13791', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3980'} | null | {'https://github.com/elgg/elgg/commit/572d210e2392f1fdf47ff2f38665372a6535c126'} | {'https://github.com/elgg/elgg/commit/572d210e2392f1fdf47ff2f38665372a6535c126'} |
GHSA | GHSA-mv2w-4jqc-6fg4 | Command injection in libvcs and vcspull | The package libvcs before 0.11.1 are vulnerable to Command Injection via argument injection. When calling the update_repo function (when using hg), the url parameter is passed to the hg clone command. By injecting some hg options it was possible to get arbitrary command execution. | {'CVE-2022-21187'} | 2022-04-04T21:38:53Z | 2022-03-15T00:00:53Z | HIGH | 8.1 | {'CWE-74', 'CWE-77'} | {'https://github.com/vcs-python/libvcs/blob/v0.11.1/CHANGES%23libvcs-0111-2022-03-12', 'https://github.com/vcs-python/vcspull/commit/e1b77128a1fa0754625b5f43d8bc47956f21f33e', 'https://github.com/advisories/GHSA-mv2w-4jqc-6fg4', 'https://github.com/vcs-python/libvcs/blob/master/CHANGES#libvcs-0111-2022-03-12', 'https://github.com/vcs-python/libvcs/pull/306', 'https://github.com/vcs-python/vcspull/blob/master/CHANGES#vcspull-1111-2022-03-12', 'https://snyk.io/vuln/SNYK-PYTHON-LIBVCS-2421204', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21187'} | null | {'https://github.com/vcs-python/vcspull/commit/e1b77128a1fa0754625b5f43d8bc47956f21f33e'} | {'https://github.com/vcs-python/vcspull/commit/e1b77128a1fa0754625b5f43d8bc47956f21f33e'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.