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-4h44-w6fm-548g | Potential Remote Code Execution in TYPO3 with mediace extension | > ### Meta
> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (9.1)
> * CWE-325, CWE-20, CWE-200, CWE-502
### Problem
It has been discovered that an internal verification mechanism can be used to generate arbitrary checksums. This allows to inject arbitrary data having a valid cryptographic message authentication code (HMAC-SHA1) and can lead to various attack chains as described below.
* [TYPO3-CORE-SA-2020-007](https://typo3.org/security/advisory/typo3-core-sa-2020-007), [CVE-2020-15099](https://nvd.nist.gov/vuln/detail/CVE-2020-15099): Potential Privilege Escalation
+ the database server used for a TYPO3 installation must be accessible for an attacker (either via internet or shared hosting network)
+ `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (7.5, high)
* [TYPO3-CORE-SA-2016-013](https://typo3.org/security/advisory/typo3-core-sa-2016-013), [CVE-2016-5091](https://nvd.nist.gov/vuln/detail/CVE-2016-5091): Insecure Deserialization & Remote Code Execution
+ an attacker must have access to at least one Extbase plugin or module action in a TYPO3 installation
+ `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (9.1, critical)
The overall severity of this vulnerability is critical (9.1) based on mentioned attack chains and the fact it does not require any privileges.
### Solution
In case the extension is not used and required at all, it is suggested to uninstall and remove it from the system completely. Otherwise, an updated version 7.6.5 is available from the TYPO3 extension manager, Packagist and the TYPO3 extension repository:
* https://extensions.typo3.org/extension/download/mediace/7.6.5/zip/
* https://packagist.org/packages/friendsoftypo3/mediace#7.6.5
As a precautionary measure it is advised to change `encryptionKey` and database credentials in `typo3conf/LocalConfiguration.php`.
### Credits
Thanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.
### References
* [TYPO3-EXT-SA-2020-014](https://typo3.org/security/advisory/typo3-ext-sa-2020-014) | {'CVE-2020-15086'} | 2022-04-19T19:02:30Z | 2020-07-29T16:15:12Z | HIGH | 9.8 | {'CWE-200', 'CWE-325', 'CWE-20', 'CWE-502'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15086', 'https://github.com/FriendsOfTYPO3/mediace/pull/31', 'https://github.com/FriendsOfTYPO3/mediace/security/advisories/GHSA-4h44-w6fm-548g', 'https://github.com/FriendsOfTYPO3/mediace/commit/fa29ffd3e8b275782a8600d2406e1b1e5e16ae75', 'https://github.com/advisories/GHSA-4h44-w6fm-548g'} | null | {'https://github.com/FriendsOfTYPO3/mediace/commit/fa29ffd3e8b275782a8600d2406e1b1e5e16ae75'} | {'https://github.com/FriendsOfTYPO3/mediace/commit/fa29ffd3e8b275782a8600d2406e1b1e5e16ae75'} |
GHSA | GHSA-6g85-3hm8-83f9 | CHECK-fail in `QuantizeAndDequantizeV4Grad` | ### Impact
An attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.QuantizeAndDequantizeV4Grad`:
```python
import tensorflow as tf
gradient_tensor = tf.constant([0.0], shape=[1])
input_tensor = tf.constant([0.0], shape=[1])
input_min = tf.constant([[0.0]], shape=[1, 1])
input_max = tf.constant([[0.0]], shape=[1, 1])
tf.raw_ops.QuantizeAndDequantizeV4Grad(
gradients=gradient_tensor, input=input_tensor,
input_min=input_min, input_max=input_max, axis=0)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L162-L163) does not validate the rank of the `input_*` tensors. In turn, this results in the tensors being passes as they are to [`QuantizeAndDequantizePerChannelGradientImpl`](https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.h#L295-L306):
```cc
template <typename Device, typename T>
struct QuantizeAndDequantizePerChannelGradientImpl {
static void Compute(const Device& d,
typename TTypes<T, 3>::ConstTensor gradient,
typename TTypes<T, 3>::ConstTensor input,
const Tensor* input_min_tensor,
const Tensor* input_max_tensor,
typename TTypes<T, 3>::Tensor input_backprop,
typename TTypes<T>::Flat input_min_backprop,
typename TTypes<T>::Flat input_max_backprop) {
...
auto input_min = input_min_tensor->vec<T>();
auto input_max = input_max_tensor->vec<T>();
...
}
```
However, the `vec<T>` method, requires the rank to 1 and triggers a `CHECK` failure otherwise.
### Patches
We have patched the issue in GitHub commit [20431e9044cf2ad3c0323c34888b192f3289af6b](https://github.com/tensorflow/tensorflow/commit/20431e9044cf2ad3c0323c34888b192f3289af6b).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 as this is the only other affected version.
### 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 and Ying Wang of Baidu X-Team. | {'CVE-2021-29544'} | 2021-05-21T14:23:22Z | 2021-05-21T14:23:22Z | LOW | 2.5 | {'CWE-754'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-6g85-3hm8-83f9', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29544', 'https://github.com/tensorflow/tensorflow/commit/20431e9044cf2ad3c0323c34888b192f3289af6b', 'https://github.com/advisories/GHSA-6g85-3hm8-83f9'} | null | {'https://github.com/tensorflow/tensorflow/commit/20431e9044cf2ad3c0323c34888b192f3289af6b'} | {'https://github.com/tensorflow/tensorflow/commit/20431e9044cf2ad3c0323c34888b192f3289af6b'} |
GHSA | GHSA-2p89-ppc2-mrq4 | Cross site scripting in getgrav/grav | User input is not properly sanitized leading to cross site scrpting (xss) in grav. | {'CVE-2022-0743'} | 2022-03-18T20:45:47Z | 2022-03-02T00:00:22Z | MODERATE | 4.6 | {'CWE-79'} | {'https://github.com/getgrav/grav/commit/3dd0cabeac9835fe64dcb4b68c658b39f1f6be2f', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0743', 'https://github.com/advisories/GHSA-2p89-ppc2-mrq4', 'https://huntr.dev/bounties/32ea4ddb-5b41-4bf9-b5a1-ef455fe2d293'} | null | {'https://github.com/getgrav/grav/commit/3dd0cabeac9835fe64dcb4b68c658b39f1f6be2f'} | {'https://github.com/getgrav/grav/commit/3dd0cabeac9835fe64dcb4b68c658b39f1f6be2f'} |
GHSA | GHSA-rpx7-33j2-xx9x | Arbitrary file deletion in NeMo ASR webapp | ### Description
NVIDIA NeMo contains a vulnerability in ASR WebApp, where Relative Path Traversal (CWE-23) may lead to deletion of any directory through the "../" structure when admin privileges are available.
CVSS Score = 2.0
https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:N
### Impact
When the optional tool ASR Webapp (https://github.com/NVIDIA/NeMo/tree/main/tools/asr_webapp) is used prior to commit https://github.com/NVIDIA/NeMo/commit/f7e4ed7e4f7f2fa43765a38c2fafa1b6d1ebd7c0, some interfaces do not verify user input. Malicious attackers can construct malicious requests to delete any directory through the "../" structure.
The vulnerability affects only cases where this particular web app is started by a user with superuser permissions. The web application is *not* a part of the regular pip release or the corresponding container, and impacts only users that clone the repository in its entirety and execute the web app (while also possessing superuser permissions).
## Patches
This vulnerability has been patched via https://github.com/NVIDIA/NeMo/commit/f7e4ed7e4f7f2fa43765a38c2fafa1b6d1ebd7c0, which is effectively any clone of the repository post r1.5.1 branch. Since the web app is not distributed via pip release or container, users who clone the main branch post this commit will possess the patch.
### Workarounds
The changes in commit https://github.com/NVIDIA/NeMo/commit/f7e4ed7e4f7f2fa43765a38c2fafa1b6d1ebd7c0 can be applied to any version of the web app without any adverse effect.
### Additional Information
Exploit Found on: 2021.12.16
Exploit Found by: @haby0
| null | 2022-04-20T21:03:58Z | 2022-02-15T01:57:18Z | LOW | 2 | null | {'https://github.com/NVIDIA/NeMo/security/advisories/GHSA-rpx7-33j2-xx9x', 'https://github.com/NVIDIA/NeMo/commit/f7e4ed7e4f7f2fa43765a38c2fafa1b6d1ebd7c0', 'https://github.com/advisories/GHSA-rpx7-33j2-xx9x'} | null | {'https://github.com/NVIDIA/NeMo/commit/f7e4ed7e4f7f2fa43765a38c2fafa1b6d1ebd7c0'} | {'https://github.com/NVIDIA/NeMo/commit/f7e4ed7e4f7f2fa43765a38c2fafa1b6d1ebd7c0'} |
GHSA | GHSA-33f9-j839-rf8h | Prototype Pollution in immer | This affects the package immer before 9.0.6. A type confusion vulnerability can lead to a bypass of CVE-2020-28477 when the user-provided keys used in the path parameter are arrays. In particular, this bypass is possible because the condition (p === "__proto__" || p === "constructor") in applyPatches_ returns false if p is ['__proto__'] (or ['constructor']). The === operator (strict equality operator) returns false if the operands have different type. | {'CVE-2021-23436'} | 2021-09-13T20:27:53Z | 2021-09-02T17:17:37Z | CRITICAL | 9.8 | {'CWE-843', 'CWE-1321'} | {'https://github.com/advisories/GHSA-33f9-j839-rf8h', 'https://github.com/immerjs/immer/commit/fa671e55ee9bd42ae08cc239102b665a23958237', 'https://snyk.io/vuln/SNYK-JS-IMMER-1540542', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23436', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1579266'} | null | {'https://github.com/immerjs/immer/commit/fa671e55ee9bd42ae08cc239102b665a23958237'} | {'https://github.com/immerjs/immer/commit/fa671e55ee9bd42ae08cc239102b665a23958237'} |
GHSA | GHSA-pgh6-m65r-2rhq | DOS and Open Redirect with user input | ### Impact
A redirect vulnerability in the `fastify-static` module allows remote attackers to redirect Mozilla Firefox users to arbitrary websites via a double slash `//` followed by a domain: `http://localhost:3000//a//youtube.com/%2e%2e%2f%2e%2e`.
A DOS vulnerability is possible if the URL contains invalid characters `curl --path-as-is "http://localhost:3000//^/.."`
The issue shows up on all the `fastify-static` applications that set `redirect: true` option. By default, it is `false`.
### Patches
The issue has been patched in `fastify-static@4.4.1`
### Workarounds
If updating is not an option, you can sanitize the input URLs using the [`rewriteUrl`](https://www.fastify.io/docs/latest/Server/#rewriteurl) server option.
### References
+ Bug founder: drstrnegth
+ [hackerone Report](https://hackerone.com/reports/1361804)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [fastify-static](https://github.com/fastify/fastify-static)
* Contact the [security team](https://github.com/fastify/fastify/blob/main/SECURITY.md#the-fastify-security-team)
| {'CVE-2021-22964'} | 2021-10-21T14:57:14Z | 2021-10-12T16:04:17Z | HIGH | 8.8 | {'CWE-248', 'CWE-601'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-22964', 'https://hackerone.com/reports/1361804', 'https://github.com/fastify/fastify-static/security/advisories/GHSA-pgh6-m65r-2rhq', 'https://github.com/advisories/GHSA-pgh6-m65r-2rhq', 'https://github.com/fastify/fastify-static/commit/c31f17d107cb19a0e96733c80a9abf16c56166d4'} | null | {'https://github.com/fastify/fastify-static/commit/c31f17d107cb19a0e96733c80a9abf16c56166d4'} | {'https://github.com/fastify/fastify-static/commit/c31f17d107cb19a0e96733c80a9abf16c56166d4'} |
GHSA | GHSA-g7v2-2qxx-wjrw | Symlink Attack in Libcontainer and Docker Engine | Libcontainer and Docker Engine before 1.6.1 opens the file-descriptor passed to the pid-1 process before performing the chroot, which allows local users to gain privileges via a symlink attack in an image. | {'CVE-2015-3627'} | 2022-02-15T01:18:02Z | 2022-02-15T01:18:02Z | MODERATE | 0 | {'CWE-59'} | {'https://github.com/docker/docker/commit/d5ebb60bddbabea0439213501f4f6ed494b23cba', 'https://nvd.nist.gov/vuln/detail/CVE-2015-3627', 'https://packetstormsecurity.com/files/131835/Docker-Privilege-Escalation-Information-Disclosure.html', 'https://groups.google.com/forum/#%21searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ', 'https://seclists.org/fulldisclosure/2015/May/28', 'https://lists.opensuse.org/opensuse-updates/2015-05/msg00023.html', 'https://github.com/advisories/GHSA-g7v2-2qxx-wjrw', 'https://groups.google.com/forum/#!searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ'} | null | {'https://github.com/docker/docker/commit/d5ebb60bddbabea0439213501f4f6ed494b23cba'} | {'https://github.com/docker/docker/commit/d5ebb60bddbabea0439213501f4f6ed494b23cba'} |
GHSA | GHSA-4w8p-x6g8-fv64 | Server-Side Request Forgery in calibreweb | calibreweb prior to version 0.6.16 contains a Server-Side Request Forgery (SSRF) vulnerability. | {'CVE-2022-0339'} | 2022-04-04T21:38:26Z | 2022-02-01T00:48:54Z | MODERATE | 6.5 | {'CWE-918'} | {'https://github.com/janeczku/calibre-web/commit/35f6f4c727c887f8f3607fe3233dbc1980d15020', 'https://github.com/janeczku/calibre-web/commit/3b216bfa07ec7992eff03e55d61732af6df9bb92', 'https://github.com/advisories/GHSA-4w8p-x6g8-fv64', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0339', 'https://huntr.dev/bounties/499688c4-6ac4-4047-a868-7922c3eab369', 'https://github.com/janeczku/calibre-web/releases/tag/0.6.16'} | null | {'https://github.com/janeczku/calibre-web/commit/3b216bfa07ec7992eff03e55d61732af6df9bb92', 'https://github.com/janeczku/calibre-web/commit/35f6f4c727c887f8f3607fe3233dbc1980d15020'} | {'https://github.com/janeczku/calibre-web/commit/3b216bfa07ec7992eff03e55d61732af6df9bb92', 'https://github.com/janeczku/calibre-web/commit/35f6f4c727c887f8f3607fe3233dbc1980d15020'} |
GHSA | GHSA-qh7x-j4v8-qw5w | Clipboard-based XSS | ### Impact
XSS against the user.
### Details
jsuites is vulnerable to DOM based XSS if the user can be tricked into copying _anything_ from a malicious and pasting it into the html editor. This is because a part of the clipboard content is directly written to `innerHTML` causing XSS.
### References
The Curious Case of Copy & Paste – on risks of pasting arbitrary content in browsers: https://research.securitum.com/the-curious-case-of-copy-paste/
| {'CVE-2021-41086'} | 2022-04-19T19:03:11Z | 2021-09-22T20:39:26Z | HIGH | 8.7 | {'CWE-79'} | {'https://www.npmjs.com/package/jsuites', 'https://github.com/jsuites/jsuites/security/advisories/GHSA-qh7x-j4v8-qw5w', 'https://github.com/jsuites/jsuites/commit/d47a6f4e143188dde2742f4cffd313e1068ad3b3', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41086', 'https://github.com/advisories/GHSA-qh7x-j4v8-qw5w', 'https://github.com/jsuites/jsuites/commit/fe1d3cc5e339f2f4da8ed1f9f42271fdf9cbd8d2'} | null | {'https://github.com/jsuites/jsuites/commit/d47a6f4e143188dde2742f4cffd313e1068ad3b3', 'https://github.com/jsuites/jsuites/commit/fe1d3cc5e339f2f4da8ed1f9f42271fdf9cbd8d2'} | {'https://github.com/jsuites/jsuites/commit/d47a6f4e143188dde2742f4cffd313e1068ad3b3', 'https://github.com/jsuites/jsuites/commit/fe1d3cc5e339f2f4da8ed1f9f42271fdf9cbd8d2'} |
GHSA | GHSA-v9w2-v7j9-rjpr | Remote code execution in Eclipse Theia | In Eclipse Theia 0.3.9 to 1.8.1, the "mini-browser" extension allows a user to preview HTML files in an iframe inside the IDE. But with the way it is made it is possible for a previewed HTML file to trigger an RCE. This exploit only happens if a user previews a malicious file. | {'CVE-2021-34435'} | 2021-09-13T20:27:31Z | 2021-09-02T22:02:36Z | HIGH | 8.8 | {'CWE-668', 'CWE-942'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-34435', 'https://bugs.eclipse.org/bugs/show_bug.cgi?id=568018', 'https://github.com/eclipse-theia/theia/commit/0761dcf5fe3c14c27432683d42d2c526ad0cfbd5', 'https://github.com/advisories/GHSA-v9w2-v7j9-rjpr', 'https://github.com/eclipse-theia/theia/pull/8759'} | null | {'https://github.com/eclipse-theia/theia/commit/0761dcf5fe3c14c27432683d42d2c526ad0cfbd5'} | {'https://github.com/eclipse-theia/theia/commit/0761dcf5fe3c14c27432683d42d2c526ad0cfbd5'} |
GHSA | GHSA-mq47-6wwv-v79w | Path traversal in claircore | A directory traversal vulnerability was found in the ClairCore engine of Clair. An attacker can exploit this by supplying a crafted container image which, when scanned by Clair, allows for arbitrary file write on the filesystem, potentially allowing for remote code execution. | {'CVE-2021-3762'} | 2022-03-21T15:33:08Z | 2022-03-04T00:00:16Z | HIGH | 7.8 | {'CWE-22'} | {'https://github.com/quay/clair/pull/1379', 'https://github.com/quay/claircore/commit/dff671c665141f126c072de8a744855d4916c9c7', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3762', 'https://bugzilla.redhat.com/show_bug.cgi?id=2000795', 'https://github.com/advisories/GHSA-mq47-6wwv-v79w', 'https://github.com/quay/claircore/commit/691f2023a1720a0579e688b69a2f4bfe1f4b7821', 'https://vulmon.com/exploitdetails?qidtp=maillist_oss_security&qid=d19fce9ede06e13dfb5630ece7f14f83', 'https://github.com/quay/clair/pull/1380', 'https://github.com/quay/claircore/pull/478'} | null | {'https://github.com/quay/claircore/commit/dff671c665141f126c072de8a744855d4916c9c7', 'https://github.com/quay/claircore/commit/691f2023a1720a0579e688b69a2f4bfe1f4b7821'} | {'https://github.com/quay/claircore/commit/dff671c665141f126c072de8a744855d4916c9c7', 'https://github.com/quay/claircore/commit/691f2023a1720a0579e688b69a2f4bfe1f4b7821'} |
GHSA | GHSA-9xr8-8hmc-389f | Cross-Site Scripting in vant | Versions of `vant` prior to 2.1.8 are vulnerable to Cross-Site Scripting. The text value of the `Picker` component column is not sanitized, which may allow attackers to execute arbitrary JavaScript in a victim's browser.
## Recommendation
Upgrade to version 2.1.8 or later. | null | 2021-08-18T22:47:16Z | 2019-11-22T13:45:33Z | HIGH | 9.1 | {'CWE-79'} | {'https://github.com/youzan/vant/pull/4278/commits/d777b78c7dc2c904f474d057ea88449cfe2ca13a', 'https://snyk.io/vuln/SNYK-JS-VANT-460461', 'https://www.npmjs.com/advisories/1157', 'https://github.com/advisories/GHSA-9xr8-8hmc-389f', 'https://github.com/youzan/vant/issues/4270'} | null | {'https://github.com/youzan/vant/pull/4278/commits/d777b78c7dc2c904f474d057ea88449cfe2ca13a'} | {'https://github.com/youzan/vant/pull/4278/commits/d777b78c7dc2c904f474d057ea88449cfe2ca13a'} |
GHSA | GHSA-5rqg-jm4f-cqx7 | Infinite loop causing Denial of Service in colors | colors is a library for including colored text in node.js consoles. Between 07 and 09 January 2022, colors versions 1.4.1, 1.4.2, and 1.4.44-liberty-2 were published including malicious code that caused a Denial of Service due to an infinite loop. Software dependent on these versions experienced the printing of randomized characters to console and an infinite loop resulting in unbound system resource consumption.
Users of colors relying on these specific versions should downgrade to version 1.4.0.
| null | 2022-04-19T19:03:27Z | 2022-01-10T17:29:53Z | HIGH | 0 | {'CWE-835'} | {'https://github.com/Marak/colors.js/commit/6bc50e79eeaa1d87369bb3e7e608ebed18c5cf26', 'https://github.com/Marak/colors.js/commit/137c6dae3339e97f4bbc838c221803c363b0a9fd', 'https://github.com/Marak/colors.js/commit/5d2d242f656103ac38086d6b26433a09f1c38c75', 'https://github.com/advisories/GHSA-5rqg-jm4f-cqx7'} | null | {'https://github.com/Marak/colors.js/commit/5d2d242f656103ac38086d6b26433a09f1c38c75', 'https://github.com/Marak/colors.js/commit/6bc50e79eeaa1d87369bb3e7e608ebed18c5cf26', 'https://github.com/Marak/colors.js/commit/137c6dae3339e97f4bbc838c221803c363b0a9fd'} | {'https://github.com/Marak/colors.js/commit/5d2d242f656103ac38086d6b26433a09f1c38c75', 'https://github.com/Marak/colors.js/commit/6bc50e79eeaa1d87369bb3e7e608ebed18c5cf26', 'https://github.com/Marak/colors.js/commit/137c6dae3339e97f4bbc838c221803c363b0a9fd'} |
GHSA | GHSA-mmqv-m45h-q2hp | Sandbox Breakout / Arbitrary Code Execution in localeval | All versions of `localeval` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to restrict access to the main context through `constructor.constructor`. This may allow attackers to execute arbitrary code in the system. Evaluating the payload
```
constructor.constructor("return process.env")()
```
returns the contents of `process.env`.
## Recommendation
No fix is currently available. Consider using an alternative package until a fix is made available. | null | 2022-03-14T23:59:01Z | 2020-09-04T15:22:40Z | CRITICAL | 0 | null | {'https://github.com/espadrine/localeval/commit/823f112c793b8fae051eeddad61d4ed29804a56c', 'https://github.com/espadrine/localeval/issues/9', 'https://github.com/espadrine/localeval/commit/ce985eba77a5f89a7f718727cbaa7fb14da40335', 'https://github.com/advisories/GHSA-mmqv-m45h-q2hp'} | null | {'https://github.com/espadrine/localeval/commit/ce985eba77a5f89a7f718727cbaa7fb14da40335', 'https://github.com/espadrine/localeval/commit/823f112c793b8fae051eeddad61d4ed29804a56c'} | {'https://github.com/espadrine/localeval/commit/823f112c793b8fae051eeddad61d4ed29804a56c', 'https://github.com/espadrine/localeval/commit/ce985eba77a5f89a7f718727cbaa7fb14da40335'} |
GHSA | GHSA-hj56-84jw-67h6 | Potential Denial-of-Service in bindata | In the bindata RubyGem before version 2.4.10 there is a potential denial-of-service vulnerability. In affected versions it is very slow for certain classes in BinData to be created. For example BinData::Bit100000, BinData::Bit100001, BinData::Bit100002, BinData::Bit<N>. In combination with <user_input>.constantize there is a potential for a CPU-based DoS. In version 2.4.10 bindata improved the creation time of Bits and Integers.
| {'CVE-2021-32823'} | 2021-06-24T13:11:19Z | 2021-06-23T23:42:04Z | LOW | 3.7 | {'CWE-400'} | {'https://github.com/dmendel/bindata/blob/v2.4.10/ChangeLog.rdoc#version-2410-2021-05-18-', 'https://github.com/advisories/GHSA-hj56-84jw-67h6', 'https://github.com/dmendel/bindata/commit/d99f050b88337559be2cb35906c1f8da49531323', 'https://github.com/rubysec/ruby-advisory-db/issues/476', 'https://about.gitlab.com/releases/2021/06/01/security-release-gitlab-13-12-2-released/#update-bindata-dependency', 'https://rubygems.org/gems/bindata', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32823', 'https://github.com/dmendel/bindata/blob/master/ChangeLog.rdoc#version-2410-2021-05-18-'} | null | {'https://github.com/dmendel/bindata/commit/d99f050b88337559be2cb35906c1f8da49531323'} | {'https://github.com/dmendel/bindata/commit/d99f050b88337559be2cb35906c1f8da49531323'} |
GHSA | GHSA-37q6-576q-vgr7 | Missing Origin Validation in parcel-bundler | Versions of `parcel-bundler` before 1.10.0 are missing origin validation on the websocket server. This vulnerability allows a remote attacker to steal a developer's source code because the origin of requests to the websocket server that is used for Hot Module Replacement (HMR) are not validated.
## Recommendation
Update to version 1.10.0 or later. | {'CVE-2018-14731'} | 2021-08-31T20:51:50Z | 2018-10-30T20:36:53Z | HIGH | 7.5 | {'CWE-200'} | {'https://github.com/parcel-bundler/parcel/issues/1783', 'https://github.com/parcel-bundler/parcel/pull/1794', 'https://nvd.nist.gov/vuln/detail/CVE-2018-14731', 'https://www.npmjs.com/advisories/721', 'https://github.com/advisories/GHSA-37q6-576q-vgr7', 'https://github.com/parcel-bundler/parcel/commit/066e0bf6bd26b15c78bd47df023452e4b20073e4', 'https://blog.cal1.cn/post/Sniffing%20Codes%20in%20Hot%20Module%20Reloading%20Messages', 'https://blog.cal1.cn/post/Sniffing%20Codes%20in%20Hot%20Module%20Reloading%20Messages)'} | null | {'https://github.com/parcel-bundler/parcel/commit/066e0bf6bd26b15c78bd47df023452e4b20073e4'} | {'https://github.com/parcel-bundler/parcel/commit/066e0bf6bd26b15c78bd47df023452e4b20073e4'} |
GHSA | GHSA-6445-fm66-fvq2 | Integer overflows in Tensorflow | ### Impact
The [implementation of `AddManySparseToTensorsMap`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/sparse_tensors_map_ops.cc) is vulnerable to an integer overflow which results in a `CHECK`-fail when building new `TensorShape` objects (so, an assert failure based denial of service):
```python
import tensorflow as tf
import numpy as np
tf.raw_ops.AddManySparseToTensorsMap(
sparse_indices=[(0,0),(0,1),(0,2),(4,3),(5,0),(5,1)],
sparse_values=[1,1,1,1,1,1],
sparse_shape=[2**32,2**32],
container='',
shared_name='',
name=None)
```
We are missing some validation on the shapes of the input tensors as well as directly constructing a large `TensorShape` with user-provided dimensions. The latter is an instance of [TFSA-2021-198](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-198.md) (CVE-2021-41197) and is easily fixed by replacing a call to `TensorShape` constructor with a call to `BuildTensorShape` static helper factory.
### Patches
We have patched the issue in GitHub commits [b51b82fe65ebace4475e3c54eb089c18a4403f1c](https://github.com/tensorflow/tensorflow/commit/b51b82fe65ebace4475e3c54eb089c18a4403f1c) and [a68f68061e263a88321c104a6c911fe5598050a8](https://github.com/tensorflow/tensorflow/commit/a68f68061e263a88321c104a6c911fe5598050a8).
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, 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 Faysal Hossain Shezan from University of Virginia. | {'CVE-2022-23568'} | 2022-02-11T17:05:21Z | 2022-02-09T23:39:11Z | MODERATE | 6.5 | {'CWE-190'} | {'https://github.com/advisories/GHSA-6445-fm66-fvq2', 'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/sparse_tensors_map_ops.cc', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23568', 'https://github.com/tensorflow/tensorflow/commit/b51b82fe65ebace4475e3c54eb089c18a4403f1c', 'https://github.com/tensorflow/tensorflow/commit/a68f68061e263a88321c104a6c911fe5598050a8', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-6445-fm66-fvq2'} | null | {'https://github.com/tensorflow/tensorflow/commit/b51b82fe65ebace4475e3c54eb089c18a4403f1c', 'https://github.com/tensorflow/tensorflow/commit/a68f68061e263a88321c104a6c911fe5598050a8'} | {'https://github.com/tensorflow/tensorflow/commit/b51b82fe65ebace4475e3c54eb089c18a4403f1c', 'https://github.com/tensorflow/tensorflow/commit/a68f68061e263a88321c104a6c911fe5598050a8'} |
GHSA | GHSA-vxhx-gmhm-623c | Improper Access Control in moodle | Users' enrollment capabilities were not being sufficiently checked in Moodle when they are restored into an existing course. This could lead to them unenrolling users without having permission to do so. Versions affected: 3.5 to 3.5.14, 3.7 to 3.7.8, 3.8 to 3.8.5, 3.9 to 3.9.2 and earlier unsupported versions. Fixed in 3.9.3, 3.8.6, 3.7.9, 3.5.15, and 3.10. | {'CVE-2020-25698'} | 2021-03-29T20:42:46Z | 2021-03-29T20:42:46Z | HIGH | 7.5 | {'CWE-284'} | {'https://moodle.org/mod/forum/discuss.php?d=413935', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4NNFCHPPHRJNJROIX6SYMHOC6HMKP3GU/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-25698', 'https://bugzilla.redhat.com/show_bug.cgi?id=1895419', 'https://github.com/moodle/moodle/commit/c8ac07fb50fa92eee1d574823fbda09e1b309a63', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/B55KXBVAT45MDASJ3EK6VIGQOYGJ4NH6/', 'https://github.com/advisories/GHSA-vxhx-gmhm-623c'} | null | {'https://github.com/moodle/moodle/commit/c8ac07fb50fa92eee1d574823fbda09e1b309a63'} | {'https://github.com/moodle/moodle/commit/c8ac07fb50fa92eee1d574823fbda09e1b309a63'} |
GHSA | GHSA-75vw-3m5v-fprh | corenlp is vulnerable to Improper Restriction of XML External Entity Reference | corenlp is vulnerable to Improper Restriction of XML External Entity Reference | {'CVE-2022-0239'} | 2022-01-24T22:08:32Z | 2022-01-21T23:43:11Z | CRITICAL | 9.8 | {'CWE-611'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0239', 'https://github.com/advisories/GHSA-75vw-3m5v-fprh', 'https://github.com/stanfordnlp/corenlp/commit/1940ffb938dc4f3f5bc5f2a2fd8b35aabbbae3dd', 'https://huntr.dev/bounties/a717aec2-5646-4a5f-ade0-dadc25736ae3'} | null | {'https://github.com/stanfordnlp/corenlp/commit/1940ffb938dc4f3f5bc5f2a2fd8b35aabbbae3dd'} | {'https://github.com/stanfordnlp/corenlp/commit/1940ffb938dc4f3f5bc5f2a2fd8b35aabbbae3dd'} |
GHSA | GHSA-f854-hpxv-cw9r | Drainage of FeeCollector's Block Transaction Fees in cronos | ### Impact
In Cronos nodes running versions before v0.6.5, it is possible to take transaction fees from Cosmos SDK's FeeCollector for the current block by sending a custom crafted MsgEthereumTx.
User funds and balances are safe.
### Patches
This problem has been patched in Cronos v0.6.5 on the mempool level.
The next network upgrade with consensus-breaking changes will patch it on the consensus level.
### Workarounds
There are no tested workarounds. All validator node operators are recommended to upgrade to Cronos v0.6.5 at their earliest possible convenience.
### Credits
Thank you to @zb3 for reporting this issue on [Cronos Immunefi Bug Bounty Program](https://immunefi.com/bounty/cronos/), to @cyril-crypto for reproducing the issue and to @yihuang and @thomas-nguy for patching the issue on the CheckTx (mempool) and the DeliverTx (consensus) levels.
### For more information
If you have any questions or comments about this advisory:
* Open a discussion in [crypto-org-chain/cronos](https://github.com/crypto-org-chain/cronos/discussions/new)
* Email us at [chain@crypto.org](mailto:chain@crypto.org)
| {'CVE-2021-43839'} | 2022-04-19T19:03:18Z | 2022-01-06T18:30:54Z | HIGH | 7.5 | {'CWE-670'} | {'https://github.com/crypto-org-chain/cronos/commit/150ef237b37ac28c8136e1c0f494932860b9ebe8', 'https://github.com/crypto-org-chain/cronos/pull/270', 'https://github.com/advisories/GHSA-f854-hpxv-cw9r', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43839', 'https://github.com/crypto-org-chain/cronos/security/advisories/GHSA-f854-hpxv-cw9r'} | null | {'https://github.com/crypto-org-chain/cronos/commit/150ef237b37ac28c8136e1c0f494932860b9ebe8'} | {'https://github.com/crypto-org-chain/cronos/commit/150ef237b37ac28c8136e1c0f494932860b9ebe8'} |
GHSA | GHSA-rp34-85x3-3764 | Cross-site Scripting in librenms | Cross-site Scripting (XSS) - Generic in Packagist librenms/librenms prior to 22.1.0. | {'CVE-2022-0576'} | 2022-02-24T13:07:05Z | 2022-02-15T00:02:47Z | MODERATE | 6.1 | {'CWE-79'} | {'https://github.com/librenms/librenms/commit/135717a9a05c5bf8921f1389cbb469dcbf300bfd', 'https://notes.netbytesec.com/2022/02/multiple-vulnerabilities-in-librenms.html', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0576', 'https://huntr.dev/bounties/114ba055-a2f0-4db9-aafb-95df944ba177', 'https://github.com/advisories/GHSA-rp34-85x3-3764'} | null | {'https://github.com/librenms/librenms/commit/135717a9a05c5bf8921f1389cbb469dcbf300bfd'} | {'https://github.com/librenms/librenms/commit/135717a9a05c5bf8921f1389cbb469dcbf300bfd'} |
GHSA | GHSA-5hfj-r725-wpc4 | Arbitrary code execution in october/system | ### Impact
Assuming an attacker with access to the backend is able to execute PHP code by using the theme import feature. This will bypass the safe mode feature that prevents PHP execution in the CMS templates.
### Patches
Issue has been patched in Build 473 and v1.1.6
### Workarounds
Apply https://github.com/octobercms/october/commit/167b592eed291ae1563c8fcc5b9b34a03a300f26 to your installation manually if you are unable to upgrade.
### References
Credits to:
• Sushi Yushi
### For more information
If you have any questions or comments about this advisory:
* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)
| {'CVE-2021-32650'} | 2022-04-19T19:02:58Z | 2022-01-14T21:08:26Z | HIGH | 8.8 | {'CWE-74'} | {'https://github.com/octobercms/october/security/advisories/GHSA-5hfj-r725-wpc4', 'https://github.com/octobercms/october/commit/167b592eed291ae1563c8fcc5b9b34a03a300f26', 'https://github.com/advisories/GHSA-5hfj-r725-wpc4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32650'} | null | {'https://github.com/octobercms/october/commit/167b592eed291ae1563c8fcc5b9b34a03a300f26'} | {'https://github.com/octobercms/october/commit/167b592eed291ae1563c8fcc5b9b34a03a300f26'} |
GHSA | GHSA-gg96-f8wr-p89f | Script injection | ### Impact
A malicious internal actor can potentially upload documentation content with malicious scripts by embedding the script within an `object` element. This may give access to sensitive data when other users visit that same documentation page.
The ability to upload malicious content may be limited by internal code review processes, unless the chosen TechDocs deployment method is to use an object store and the actor has access to upload files directly to that store.
### Patches
The vulnerability is patched in the `0.9.5` release of `@backstage/plugin-techdocs`.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [Backstage repository](https://github.com/backstage/backstage)
* Visit our chat, linked to in [Backstage README](https://github.com/backstage/backstage)
| {'CVE-2021-32661'} | 2021-06-21T22:43:06Z | 2021-06-04T19:09:26Z | MODERATE | 6.8 | {'CWE-434', 'CWE-77'} | {'https://github.com/backstage/backstage/commit/aad98c544e59369901fe9e0a85f6357644dceb5c', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32661', 'https://github.com/backstage/backstage/security/advisories/GHSA-gg96-f8wr-p89f', 'https://github.com/backstage/backstage/releases/tag/release-2021-06-03', 'https://github.com/advisories/GHSA-gg96-f8wr-p89f'} | null | {'https://github.com/backstage/backstage/commit/aad98c544e59369901fe9e0a85f6357644dceb5c'} | {'https://github.com/backstage/backstage/commit/aad98c544e59369901fe9e0a85f6357644dceb5c'} |
GHSA | GHSA-2m39-62fm-q8r3 | Regular Expression Denial of Service in sshpk | Versions of `sshpk` before 1.13.2 or 1.14.1 are vulnerable to regular expression denial of service when parsing crafted invalid public keys.
## Recommendation
Update to version 1.13.2, 1.14.1 or later. | {'CVE-2018-3737'} | 2021-01-08T20:07:45Z | 2018-08-15T13:22:23Z | HIGH | 0 | {'CWE-770'} | {'https://www.npmjs.com/advisories/606', 'https://github.com/advisories/GHSA-2m39-62fm-q8r3', 'https://hackerone.com/reports/319593', 'https://github.com/joyent/node-sshpk/blob/v1.13.1/lib/formats/ssh.js#L17', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3737', 'https://github.com/joyent/node-sshpk/commit/46065d38a5e6d1bccf86d3efb2fb83c14e3f9957'} | null | {'https://github.com/joyent/node-sshpk/commit/46065d38a5e6d1bccf86d3efb2fb83c14e3f9957'} | {'https://github.com/joyent/node-sshpk/commit/46065d38a5e6d1bccf86d3efb2fb83c14e3f9957'} |
GHSA | GHSA-2xgj-xhgf-ggjv | Heap buffer overflow in `BandedTriangularSolve` | ### Impact
An attacker can trigger a heap buffer overflow in Eigen implementation of `tf.raw_ops.BandedTriangularSolve`:
```python
import tensorflow as tf
import numpy as np
matrix_array = np.array([])
matrix_tensor = tf.convert_to_tensor(np.reshape(matrix_array,(0,1)),dtype=tf.float32)
rhs_array = np.array([1,1])
rhs_tensor = tf.convert_to_tensor(np.reshape(rhs_array,(1,2)),dtype=tf.float32)
tf.raw_ops.BandedTriangularSolve(matrix=matrix_tensor,rhs=rhs_tensor)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/linalg/banded_triangular_solve_op.cc#L269-L278) calls `ValidateInputTensors` for input validation but fails to validate that the two tensors are not empty:
```cc
void ValidateInputTensors(OpKernelContext* ctx, const Tensor& in0, const Tensor& in1) {
OP_REQUIRES(
ctx, in0.dims() >= 2,
errors::InvalidArgument("In[0] ndims must be >= 2: ", in0.dims()));
OP_REQUIRES(
ctx, in1.dims() >= 2,
errors::InvalidArgument("In[1] ndims must be >= 2: ", in1.dims()));
}
```
Furthermore, since `OP_REQUIRES` macro only stops execution of current function after setting `ctx->status()` to a non-OK value, callers of helper functions that use `OP_REQUIRES` must check value of `ctx->status()` before continuing. This doesn't happen [in this op's implementation](https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/linalg/banded_triangular_solve_op.cc#L219), hence the validation that is present is also not effective.
### Patches
We have patched the issue in GitHub commit [ba6822bd7b7324ba201a28b2f278c29a98edbef2](https://github.com/tensorflow/tensorflow/commit/ba6822bd7b7324ba201a28b2f278c29a98edbef2) followed by GitHub commit [0ab290774f91a23bebe30a358fde4e53ab4876a0](https://github.com/tensorflow/tensorflow/commit/0ab290774f91a23bebe30a358fde4e53ab4876a0).
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 Ye Zhang and Yakun Zhang of Baidu X-Team. | {'CVE-2021-29612'} | 2021-05-21T14:28:37Z | 2021-05-21T14:28:37Z | LOW | 3.6 | {'CWE-120'} | {'https://github.com/advisories/GHSA-2xgj-xhgf-ggjv', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29612', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-2xgj-xhgf-ggjv', 'https://github.com/tensorflow/tensorflow/commit/ba6822bd7b7324ba201a28b2f278c29a98edbef2', 'https://github.com/tensorflow/tensorflow/commit/0ab290774f91a23bebe30a358fde4e53ab4876a0'} | null | {'https://github.com/tensorflow/tensorflow/commit/0ab290774f91a23bebe30a358fde4e53ab4876a0', 'https://github.com/tensorflow/tensorflow/commit/ba6822bd7b7324ba201a28b2f278c29a98edbef2'} | {'https://github.com/tensorflow/tensorflow/commit/ba6822bd7b7324ba201a28b2f278c29a98edbef2', 'https://github.com/tensorflow/tensorflow/commit/0ab290774f91a23bebe30a358fde4e53ab4876a0'} |
GHSA | GHSA-qpv2-jxc7-3638 | Exposure of Sensitive Information in snipe/snipe-it | Snipe-IT prior to v5.3.10 is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor. | {'CVE-2022-0569'} | 2022-02-24T13:13:02Z | 2022-02-15T00:02:47Z | MODERATE | 4.3 | {'CWE-200'} | {'https://huntr.dev/bounties/b41d5e63-bcd8-4864-8a2e-8ec74eec520b', 'https://github.com/advisories/GHSA-qpv2-jxc7-3638', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0569', 'https://github.com/snipe/snipe-it/commit/05c0819776b07425b2831cd31a8a0f4e7ac30c09'} | null | {'https://github.com/snipe/snipe-it/commit/05c0819776b07425b2831cd31a8a0f4e7ac30c09'} | {'https://github.com/snipe/snipe-it/commit/05c0819776b07425b2831cd31a8a0f4e7ac30c09'} |
GHSA | GHSA-c87f-fq5g-63r2 | Cross-site scripting in Unicorn framework | The Unicorn framework through 0.35.3 for Django allows XSS via component.name. | {'CVE-2021-42053'} | 2021-10-12T17:51:11Z | 2021-10-12T17:51:11Z | MODERATE | 0 | {'CWE-79'} | {'https://github.com/advisories/GHSA-c87f-fq5g-63r2', 'https://github.com/adamghill/django-unicorn/pull/288', 'https://nvd.nist.gov/vuln/detail/CVE-2021-42053', 'http://packetstormsecurity.com/files/164442/django-unicorn-0.35.3-Cross-Site-Scripting.html', 'https://github.com/adamghill/django-unicorn/compare/0.35.3...0.36.0', 'https://github.com/adamghill/django-unicorn/pull/288/commits/aa5b9835d946bd9893ef02e556859e3ea62cc5e2'} | null | {'https://github.com/adamghill/django-unicorn/pull/288/commits/aa5b9835d946bd9893ef02e556859e3ea62cc5e2'} | {'https://github.com/adamghill/django-unicorn/pull/288/commits/aa5b9835d946bd9893ef02e556859e3ea62cc5e2'} |
GHSA | GHSA-r992-xph6-h7x2 | Open redirect in microweber | microweber prior to 1.2.11 is vulnerable to open redirect. | {'CVE-2022-0560'} | 2022-02-23T21:57:39Z | 2022-02-12T00:00:48Z | MODERATE | 6.1 | {'CWE-601'} | {'https://github.com/microweber/microweber/commit/72d4b12cc487f56a859a8570ada4efb77b4b8c63', 'https://github.com/advisories/GHSA-r992-xph6-h7x2', 'https://huntr.dev/bounties/c9d586e7-0fa1-47ab-a2b3-b890e8dc9b25', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0560'} | null | {'https://github.com/microweber/microweber/commit/72d4b12cc487f56a859a8570ada4efb77b4b8c63'} | {'https://github.com/microweber/microweber/commit/72d4b12cc487f56a859a8570ada4efb77b4b8c63'} |
GHSA | GHSA-grg4-wf29-r9vv | Bzip2Decoder doesn't allow setting size restrictions for decompressed data | ### Impact
The Bzip2 decompression decoder function doesn't allow setting size restrictions on the decompressed output data (which affects the allocation size used during decompression).
All users of Bzip2Decoder are affected. The malicious input can trigger an OOME and so a DoS attack
### Workarounds
No workarounds other than not using the `Bzip2Decoder`
### References
Relevant code areas:
https://github.com/netty/netty/blob/netty-4.1.67.Final/codec/src/main/java/io/netty/handler/codec/compression/Bzip2Decoder.java#L80
https://github.com/netty/netty/blob/netty-4.1.67.Final/codec/src/main/java/io/netty/handler/codec/compression/Bzip2Decoder.java#L294
https://github.com/netty/netty/blob/netty-4.1.67.Final/codec/src/main/java/io/netty/handler/codec/compression/Bzip2Decoder.java#L305 | {'CVE-2021-37136'} | 2022-04-22T15:41:16Z | 2021-09-09T17:11:21Z | HIGH | 7.5 | {'CWE-400'} | {'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://github.com/netty/netty/commit/41d3d61a61608f2223bb364955ab2045dd5e4020', 'https://lists.apache.org/thread.html/rfb2bf8597e53364ccab212fbcbb2a4e9f0a9e1429b1dc08023c6868e@%3Cdev.tinkerpop.apache.org%3E', 'https://lists.apache.org/thread.html/r75490c61c2cb7b6ae2c81238fd52ae13636c60435abcd732d41531a0@%3Ccommits.druid.apache.org%3E', 'https://github.com/netty/netty/blob/4.1/codec/src/main/java/io/netty/handler/codec/compression/Bzip2Decoder.java#L294', 'https://github.com/advisories/GHSA-grg4-wf29-r9vv', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37136', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://github.com/netty/netty/blob/4.1/codec/src/main/java/io/netty/handler/codec/compression/Bzip2Decoder.java#L80', 'https://lists.apache.org/thread.html/rd262f59b1586a108e320e5c966feeafbb1b8cdc96965debc7cc10b16@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/r5e05eba32476c580412f9fbdfc9b8782d5b40558018ac4ac07192a04@%3Ccommits.druid.apache.org%3E', 'https://github.com/netty/netty/security/advisories/GHSA-grg4-wf29-r9vv', 'https://security.netapp.com/advisory/ntap-20220210-0012/', 'https://lists.apache.org/thread.html/r06a145c9bd41a7344da242cef07977b24abe3349161ede948e30913d@%3Ccommits.druid.apache.org%3E', 'https://github.com/netty/netty/blob/4.1/codec/src/main/java/io/netty/handler/codec/compression/Bzip2Decoder.java#L305', 'https://lists.apache.org/thread.html/r5406eaf3b07577d233b9f07cfc8f26e28369e6bab5edfcab41f28abb@%3Ccommits.druid.apache.org%3E'} | null | {'https://github.com/netty/netty/commit/41d3d61a61608f2223bb364955ab2045dd5e4020'} | {'https://github.com/netty/netty/commit/41d3d61a61608f2223bb364955ab2045dd5e4020'} |
GHSA | GHSA-9475-xg6m-j7pw | Subject Confirmation Method not validated in Saml2 Authentication Services for ASP.NET | ### Impact
Saml2 tokens are usually used as bearer tokens - a caller that presents a token is assumed to be the subject of the token. There is also support in the Saml2 protocol for issuing tokens that is tied to a subject through other means, e.g. holder-of-key where possession of a private key must be proved.
The Sustainsys.Saml2 library incorrectly treats all incoming tokens as bearer tokens, even though they have another subject confirmation method specified. This could be used by an attacker that could get access to Saml2 tokens with another subject confirmation method than bearer. The attacker could then use such a tocken to create a log in session.
### Patches
Version 1.0.2 and 2.7.0 are patched.
### Workarounds
Ensure that any IdentityProvider trusted by the Sustainsys.Saml2 SP only issues bearer tokens if the audience matches the Sustainsys.Saml2 SP.
### For more information
If you have any questions or comments about this advisory:
* Comment on #103
* Email us at security@sustainsys.com if you think that there are further security issues. | {'CVE-2020-5268'} | 2021-01-08T20:21:36Z | 2020-04-22T20:59:37Z | MODERATE | 6.5 | {'CWE-303'} | {'https://github.com/Sustainsys/Saml2/commit/e58e0a1aff2b1ead6aca080b7cdced55ee6d5241', 'https://github.com/advisories/GHSA-9475-xg6m-j7pw', 'https://github.com/Sustainsys/Saml2/issues/712', 'https://www.nuget.org/packages/Sustainsys.Saml2/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5268', 'https://github.com/Sustainsys/Saml2/security/advisories/GHSA-9475-xg6m-j7pw'} | null | {'https://github.com/Sustainsys/Saml2/commit/e58e0a1aff2b1ead6aca080b7cdced55ee6d5241'} | {'https://github.com/Sustainsys/Saml2/commit/e58e0a1aff2b1ead6aca080b7cdced55ee6d5241'} |
GHSA | GHSA-v92m-hhhw-vv9v | Code injection in codiad | Codiad Web IDE through 2.8.4 allows PHP Code injection. | {'CVE-2019-19208'} | 2022-01-31T22:01:57Z | 2021-09-01T18:27:12Z | CRITICAL | 9.8 | {'CWE-94'} | {'https://herolab.usd.de/security-advisories/usd-2019-0049/', 'https://github.com/Hacker5preme/Exploits/tree/main/CVE-2019-19208-Exploit', 'https://www.exploit-db.com/exploits/49902', 'https://nvd.nist.gov/vuln/detail/CVE-2019-19208', 'https://github.com/advisories/GHSA-v92m-hhhw-vv9v', 'https://herolab.usd.de/en/security-advisories/', 'https://github.com/Codiad/Codiad/commits/master', 'http://packetstormsecurity.com/files/162753/Codiad-2.8.4-Remote-Code-Execution.html'} | null | {'https://github.com/Codiad/Codiad/commits/master'} | {'https://github.com/Codiad/Codiad/commits/master'} |
GHSA | GHSA-864j-6qpp-cmrr | SQL Injection in Geocoder | sql.rb in Geocoder before 1.6.1 allows Boolean-based SQL injection when within_bounding_box is used in conjunction with untrusted sw_lat, sw_lng, ne_lat, or ne_lng data. | {'CVE-2020-7981'} | 2021-08-30T13:36:05Z | 2020-06-10T20:03:02Z | CRITICAL | 9.8 | {'CWE-89'} | {'https://github.com/alexreisner/geocoder/compare/v1.6.0...v1.6.1', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7981', 'https://github.com/alexreisner/geocoder/commit/dcdc3d8675411edce3965941a2ca7c441ca48613', 'https://github.com/advisories/GHSA-864j-6qpp-cmrr', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/geocoder/CVE-2020-7981.yml', 'https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7981'} | null | {'https://github.com/alexreisner/geocoder/commit/dcdc3d8675411edce3965941a2ca7c441ca48613'} | {'https://github.com/alexreisner/geocoder/commit/dcdc3d8675411edce3965941a2ca7c441ca48613'} |
GHSA | GHSA-2647-c639-qv2j | Server-Side Request Forgery in calibreweb | calibreweb prior to version 0.6.17 is vulnerable to server-side request forgery (SSRF). This is due to an incomplete fix for [CVE-2022-0339](https://github.com/advisories/GHSA-4w8p-x6g8-fv64). The blacklist does not check for `0.0.0.0`, which would result in a payload of `0.0.0.0` resolving to `localhost`. | {'CVE-2022-0766'} | 2022-03-18T21:20:46Z | 2022-03-08T00:00:31Z | CRITICAL | 9.8 | {'CWE-918'} | {'https://huntr.dev/bounties/7f2a5bb4-e6c7-4b6a-b8eb-face9e3add7b', 'https://github.com/janeczku/calibre-web/commit/965352c8d96c9eae7a6867ff76b0db137d04b0b8', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0766', 'https://github.com/advisories/GHSA-2647-c639-qv2j'} | null | {'https://github.com/janeczku/calibre-web/commit/965352c8d96c9eae7a6867ff76b0db137d04b0b8'} | {'https://github.com/janeczku/calibre-web/commit/965352c8d96c9eae7a6867ff76b0db137d04b0b8'} |
GHSA | GHSA-fmj2-7wx8-qj4v | Server-side request forgery (SSRF) in Apache XmlGraphics Commons | Apache XmlGraphics Commons 2.4 is vulnerable to server-side request forgery, caused by improper input validation by the XMPParser. By using a specially-crafted argument, an attacker could exploit this vulnerability to cause the underlying server to make arbitrary GET requests. | {'CVE-2020-11988'} | 2022-02-09T00:45:56Z | 2022-02-09T00:45:56Z | HIGH | 8.2 | {'CWE-20', 'CWE-918'} | {'https://github.com/apache/xmlgraphics-commons/commit/57393912eb87b994c7fed39ddf30fb778a275183', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/22HESSYU7T4D6GGENUVEX3X3H6FGBECH/', 'https://lists.apache.org/thread.html/r588d05a0790b40a0eb81088252e1e8c1efb99706631421f17038eb05@%3Cdev.poi.apache.org%3E', 'https://lists.apache.org/thread.html/ra8f4d6ae402ec020ee3e8c28632c91be131c4d8b4c9c6756a179b12b@%3Cdev.jmeter.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11988', 'https://xmlgraphics.apache.org/security.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JP4XA56DA3BFNRBBLBXM6ZAI5RUVFA33/', 'https://github.com/advisories/GHSA-fmj2-7wx8-qj4v', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://lists.apache.org/thread.html/r2877ae10e8be56a3c52d03e373512ddd32f16b863f24c2e22f5a5ba2@%3Cdev.poi.apache.org%3E', 'https://issues.apache.org/jira/browse/XGC-122', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/apache/xmlgraphics-commons/commit/57393912eb87b994c7fed39ddf30fb778a275183'} | {'https://github.com/apache/xmlgraphics-commons/commit/57393912eb87b994c7fed39ddf30fb778a275183'} |
GHSA | GHSA-r4c4-5fpq-56wg | Heap OOB in boosted trees | ### Impact
An attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to `BoostedTreesSparseCalculateBestFeatureSplit`:
```python
import tensorflow as tf
tf.raw_ops.BoostedTreesSparseCalculateBestFeatureSplit(
node_id_range=[0,10],
stats_summary_indices=[[1, 2, 3, 0x1000000]],
stats_summary_values=[1.0],
stats_summary_shape=[1,1,1,1],
l1=l2=[1.0],
tree_complexity=[0.5],
min_node_weight=[1.0],
logits_dimension=3,
split_type='inequality')
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) needs to validate that each value in `stats_summary_indices` is in range.
### Patches
We have patched the issue in GitHub commit [e84c975313e8e8e38bb2ea118196369c45c51378](https://github.com/tensorflow/tensorflow/commit/e84c975313e8e8e38bb2ea118196369c45c51378).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit 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 members of the Aivul Team from Qihoo 360. | {'CVE-2021-37664'} | 2021-08-25T14:42:20Z | 2021-08-25T14:42:20Z | HIGH | 7.3 | {'CWE-125'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-r4c4-5fpq-56wg', 'https://github.com/tensorflow/tensorflow/commit/e84c975313e8e8e38bb2ea118196369c45c51378', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37664', 'https://github.com/advisories/GHSA-r4c4-5fpq-56wg'} | null | {'https://github.com/tensorflow/tensorflow/commit/e84c975313e8e8e38bb2ea118196369c45c51378'} | {'https://github.com/tensorflow/tensorflow/commit/e84c975313e8e8e38bb2ea118196369c45c51378'} |
GHSA | GHSA-hc6c-75p4-hmq4 | Reference binding to null pointer in `MatrixDiag*` ops | ### Impact
The implementation of [`MatrixDiag*` operations](https://github.com/tensorflow/tensorflow/blob/4c4f420e68f1cfaf8f4b6e8e3eb857e9e4c3ff33/tensorflow/core/kernels/linalg/matrix_diag_op.cc#L195-L197) does not validate that the tensor arguments are non-empty:
```cc
num_rows = context->input(2).flat<int32>()(0);
num_cols = context->input(3).flat<int32>()(0);
padding_value = context->input(4).flat<T>()(0);
```
Thus, users can trigger null pointer dereferences if any of the above tensors are null:
```python
import tensorflow as tf
d = tf.convert_to_tensor([],dtype=tf.float32)
p = tf.convert_to_tensor([],dtype=tf.float32)
tf.raw_ops.MatrixDiagV2(diagonal=d, k=0, num_rows=0, num_cols=0, padding_value=p)
```
Changing from `tf.raw_ops.MatrixDiagV2` to `tf.raw_ops.MatrixDiagV3` still reproduces the issue.
### Patches
We have patched the issue in GitHub commit [a7116dd3913c4a4afd2a3a938573aa7c785fdfc6](https://github.com/tensorflow/tensorflow/commit/a7116dd3913c4a4afd2a3a938573aa7c785fdfc6).
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 Ye Zhang and Yakun Zhang of Baidu X-Team. | {'CVE-2021-29515'} | 2021-05-21T14:20:54Z | 2021-05-21T14:20:54Z | LOW | 2.5 | {'CWE-476'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hc6c-75p4-hmq4', 'https://github.com/advisories/GHSA-hc6c-75p4-hmq4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29515', 'https://github.com/tensorflow/tensorflow/commit/a7116dd3913c4a4afd2a3a938573aa7c785fdfc6'} | null | {'https://github.com/tensorflow/tensorflow/commit/a7116dd3913c4a4afd2a3a938573aa7c785fdfc6'} | {'https://github.com/tensorflow/tensorflow/commit/a7116dd3913c4a4afd2a3a938573aa7c785fdfc6'} |
GHSA | GHSA-v82p-hv3v-p6qp | Incomplete validation in MKL requantization | ### Impact
Due to incomplete validation in MKL implementation of requantization, an attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays:
```python
import tensorflow as tf
tf.raw_ops.RequantizationRangePerChannel(
input=[],
input_min=[0,0,0,0,0],
input_max=[1,1,1,1,1],
clip_value_max=1)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantization_range_per_channel_op.cc) does not validate the dimensions of the `input` tensor.
A similar issue occurs in `MklRequantizePerChannelOp`:
```python
import tensorflow as tf
from tensorflow.python.ops import gen_math_ops
gen_math_ops.requantize_per_channel(
input=[],
input_min=[-100,-100,-100,-100,-100],
input_max=[-100,-100,-100],
requested_output_min=[-100,-100,-100,-100,-100],
requested_output_max=[],
out_type=tf.int)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantize_per_channel_op.cc) does not perform full validation for all the input arguments.
### Patches
We have patched the issue in GitHub commit [9e62869465573cb2d9b5053f1fa02a81fce21d69](https://github.com/tensorflow/tensorflow/commit/9e62869465573cb2d9b5053f1fa02a81fce21d69) and in the Github commit [203214568f5bc237603dbab6e1fd389f1572f5c9](https://github.com/tensorflow/tensorflow/commit/203214568f5bc237603dbab6e1fd389f1572f5c9).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit 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 members of the Aivul Team from Qihoo 360. | {'CVE-2021-37665'} | 2021-08-25T14:42:16Z | 2021-08-25T14:42:16Z | HIGH | 7.8 | {'CWE-20'} | {'https://github.com/tensorflow/tensorflow/commit/9e62869465573cb2d9b5053f1fa02a81fce21d69', 'https://github.com/advisories/GHSA-v82p-hv3v-p6qp', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-v82p-hv3v-p6qp', 'https://github.com/tensorflow/tensorflow/commit/203214568f5bc237603dbab6e1fd389f1572f5c9', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37665'} | null | {'https://github.com/tensorflow/tensorflow/commit/9e62869465573cb2d9b5053f1fa02a81fce21d69', 'https://github.com/tensorflow/tensorflow/commit/203214568f5bc237603dbab6e1fd389f1572f5c9'} | {'https://github.com/tensorflow/tensorflow/commit/203214568f5bc237603dbab6e1fd389f1572f5c9', 'https://github.com/tensorflow/tensorflow/commit/9e62869465573cb2d9b5053f1fa02a81fce21d69'} |
GHSA | GHSA-hm45-mgqm-gjm4 | Remote Code Execution (RCE) Exploit on Cross Site Scripting (XSS) Vulnerability | ### Impact
A RCE exploit has been discovered in the Red Discord Bot - Dashboard Webserver: this exploit allows Discord users with specially crafted Server names and Usernames/Nicknames to inject code into the webserver front-end code. By abusing this exploit, it's possible to perform destructive actions and/or access sensitive information.
### Patches
This high severity exploit has been fixed on version `0.1.7a`.
### Workarounds
There are no workarounds, bot owners must upgrade their relevant packages (Dashboard module and Dashboard webserver) in order to patch this issue
### References
- 99d88b8
- a6b9785
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Cog-Creators/Red-Dashboard](https://github.com/Cog-Creators/Red-Dashboard/issues/new/choose)
* Over on the official [Red Server](https://discord.gg/red) or at the Third Party Server [Toxic Layer](https://discord.gg/vQZTdB9) | {'CVE-2020-26249'} | 2022-04-19T19:02:41Z | 2020-12-08T23:55:54Z | HIGH | 7.7 | {'CWE-79'} | {'https://github.com/Cog-Creators/Red-Dashboard/security/advisories/GHSA-hm45-mgqm-gjm4', 'https://github.com/Cog-Creators/Red-Dashboard/commit/a6b9785338003ec87fb75305e7d1cc2d40c7ab91', 'https://github.com/advisories/GHSA-hm45-mgqm-gjm4', 'https://pypi.org/project/Red-Dashboard', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26249', 'https://github.com/Cog-Creators/Red-Dashboard/commit/99d88b840674674166ce005b784ae8e31e955ab1'} | null | {'https://github.com/Cog-Creators/Red-Dashboard/commit/a6b9785338003ec87fb75305e7d1cc2d40c7ab91', 'https://github.com/Cog-Creators/Red-Dashboard/commit/99d88b840674674166ce005b784ae8e31e955ab1'} | {'https://github.com/Cog-Creators/Red-Dashboard/commit/99d88b840674674166ce005b784ae8e31e955ab1', 'https://github.com/Cog-Creators/Red-Dashboard/commit/a6b9785338003ec87fb75305e7d1cc2d40c7ab91'} |
GHSA | GHSA-cr6m-62pq-hmqh | OS Command injection in npm-lockfile | npm-lockfile safely generates an npm lockfile and output it to the filename of your choice. npm-lockfile before 2.0.4 does not santize unsafe external input and invoke sensitive command execution API with the input, causing command injection vulnerability. A fix was released in version 2.0.5. | {'CVE-2022-0841'} | 2022-04-04T21:37:39Z | 2022-03-04T00:00:18Z | CRITICAL | 9.8 | {'CWE-78'} | {'https://huntr.dev/bounties/4f806dc9-2ecd-4e79-997e-5292f1bea9f1', 'https://github.com/ljharb/npm-lockfile/commit/bfdb84813260f0edbf759f2fde1e8c816c1478b8', 'https://github.com/advisories/GHSA-cr6m-62pq-hmqh', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0841'} | null | {'https://github.com/ljharb/npm-lockfile/commit/bfdb84813260f0edbf759f2fde1e8c816c1478b8'} | {'https://github.com/ljharb/npm-lockfile/commit/bfdb84813260f0edbf759f2fde1e8c816c1478b8'} |
GHSA | GHSA-vm37-j55j-8655 | OS Command Injection in Microweber | Microweber is a content management system with drag and drop. Prior to version 1.2.11, Microweber is vulnerable to OS Command Injection. | {'CVE-2022-0557'} | 2022-03-28T15:23:38Z | 2022-02-12T00:00:49Z | HIGH | 7.8 | {'CWE-78'} | {'https://github.com/microweber/microweber/commit/0a7e5f1d81de884861ca677ee1aaac31f188d632', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0557', 'http://packetstormsecurity.com/files/166077/Microweber-1.2.11-Shell-Upload.html', 'https://www.exploit-db.com/exploits/50768', 'https://huntr.dev/bounties/660c89af-2de5-41bc-aada-9e4e78142db8', 'https://github.com/advisories/GHSA-vm37-j55j-8655'} | null | {'https://github.com/microweber/microweber/commit/0a7e5f1d81de884861ca677ee1aaac31f188d632'} | {'https://github.com/microweber/microweber/commit/0a7e5f1d81de884861ca677ee1aaac31f188d632'} |
GHSA | GHSA-rrvx-pwf8-p59p | In Bouncy Castle JCE Provider the DSA key pair generator generates a weak private key if used with default values | In the Bouncy Castle JCE Provider version 1.55 and earlier the DSA key pair generator generates a weak private key if used with default values. If the JCA key pair generator is not explicitly initialised with DSA parameters, 1.55 and earlier generates a private value assuming a 1024 bit key size. In earlier releases this can be dealt with by explicitly passing parameters to the key pair generator. | {'CVE-2016-1000343'} | 2022-04-27T13:29:12Z | 2018-10-17T16:24:22Z | HIGH | 7.5 | null | {'https://github.com/advisories/GHSA-rrvx-pwf8-p59p', 'https://lists.apache.org/thread.html/708d94141126eac03011144a971a6411fcac16d9c248d1d535a39451@%3Csolr-user.lucene.apache.org%3E', 'https://security.netapp.com/advisory/ntap-20181127-0004/', 'https://access.redhat.com/errata/RHSA-2018:2927', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://access.redhat.com/errata/RHSA-2018:2669', 'https://github.com/bcgit/bc-java/commit/50a53068c094d6cff37659da33c9b4505becd389#diff-5578e61500abb2b87b300d3114bdfd7d', 'https://usn.ubuntu.com/3727-1/', 'https://lists.debian.org/debian-lts-announce/2018/07/msg00009.html', 'https://nvd.nist.gov/vuln/detail/CVE-2016-1000343'} | null | {'https://github.com/bcgit/bc-java/commit/50a53068c094d6cff37659da33c9b4505becd389#diff-5578e61500abb2b87b300d3114bdfd7d'} | {'https://github.com/bcgit/bc-java/commit/50a53068c094d6cff37659da33c9b4505becd389#diff-5578e61500abb2b87b300d3114bdfd7d'} |
GHSA | GHSA-76qr-mmh8-cp8f | Moderate severity vulnerability that affects com.sparkjava:spark-core | In Spark before 2.7.2, a remote attacker can read unintended static files via various representations of absolute or relative pathnames, as demonstrated by file: URLs and directory traversal sequences. NOTE: this product is unrelated to Ignite Realtime Spark. | {'CVE-2018-9159'} | 2021-09-02T19:24:33Z | 2018-10-19T16:56:00Z | MODERATE | 5.3 | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-9159', 'https://access.redhat.com/errata/RHSA-2018:2405', 'https://github.com/advisories/GHSA-76qr-mmh8-cp8f', 'https://access.redhat.com/errata/RHSA-2018:2020', 'https://github.com/perwendel/spark/commit/a221a864db28eb736d36041df2fa6eb8839fc5cd', 'http://sparkjava.com/news#spark-272-released', 'https://github.com/perwendel/spark/commit/ce9e11517eca69e58ed4378d1e47a02bd06863cc', 'https://github.com/perwendel/spark/issues/981', 'https://github.com/perwendel/spark/commit/030e9d00125cbd1ad759668f85488aba1019c668'} | null | {'https://github.com/perwendel/spark/commit/a221a864db28eb736d36041df2fa6eb8839fc5cd', 'https://github.com/perwendel/spark/commit/030e9d00125cbd1ad759668f85488aba1019c668', 'https://github.com/perwendel/spark/commit/ce9e11517eca69e58ed4378d1e47a02bd06863cc'} | {'https://github.com/perwendel/spark/commit/a221a864db28eb736d36041df2fa6eb8839fc5cd', 'https://github.com/perwendel/spark/commit/ce9e11517eca69e58ed4378d1e47a02bd06863cc', 'https://github.com/perwendel/spark/commit/030e9d00125cbd1ad759668f85488aba1019c668'} |
GHSA | GHSA-qh2g-7h5p-mxf4 | Credentials bypass in Apache Druid | When LDAP authentication is enabled in Apache Druid 0.17.0, callers of Druid APIs with a valid set of LDAP credentials can bypass the credentialsValidator.userSearch filter barrier that determines if a valid LDAP user is allowed to authenticate with Druid. They are still subject to role-based authorization checks, if configured. Callers of Druid APIs can also retrieve any LDAP attribute values of users that exist on the LDAP server, so long as that information is visible to the Druid server. This information disclosure does not require the caller itself to be a valid LDAP user. | {'CVE-2020-1958'} | 2022-02-09T22:05:39Z | 2022-02-09T22:05:39Z | MODERATE | 6.5 | {'CWE-200', 'CWE-74'} | {'https://github.com/apache/druid/commit/dbaabdd24710fef726c5730c609937706f456a44#diff-fab6b7a8a160a405e787690201aade5462961550c97715ab18de6ad07a3edf7e', 'https://lists.apache.org/thread.html/rf70876ecafb45b314eff9d040c5281c4adb0cb7771eb029448cfb79b@%3Cannounce.apache.org%3E', 'https://lists.apache.org/thread.html/r1c32c95543d44559b8d7fd89b0a85f728c80e8b715685bbf788a15a4@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/r1526dbce98a138629a41daa06c13393146ddcaf8f9d273cc49d57681@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/r9d437371793b410f8a8e18f556d52d4bb68e18c537962f6a97f4945e%40%3Cdev.druid.apache.org%3E', 'https://lists.apache.org/thread.html/rffabc9e83cc2831bbee5db32b3965b84b09346a26ebc1012db63d28c@%3Ccommits.druid.apache.org%3E', 'https://github.com/advisories/GHSA-qh2g-7h5p-mxf4', 'https://nvd.nist.gov/vuln/detail/CVE-2020-1958', 'https://lists.apache.org/thread.html/r026540c617d334007810cd8f0068f617b5c78444be00a31fc1b03390@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/r47c90a378efdb3fd07ff7f74095b8eb63b3ca93b8ada5c2661c5e371@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/r75e74d39c41c1b95a658b6a9f75fc6fd02b1d1922566a0ee4ee2fdfc@%3Ccommits.druid.apache.org%3E', 'https://github.com/apache/druid/pull/9600#issuecomment-607497875'} | null | {'https://github.com/apache/druid/commit/dbaabdd24710fef726c5730c609937706f456a44#diff-fab6b7a8a160a405e787690201aade5462961550c97715ab18de6ad07a3edf7e'} | {'https://github.com/apache/druid/commit/dbaabdd24710fef726c5730c609937706f456a44#diff-fab6b7a8a160a405e787690201aade5462961550c97715ab18de6ad07a3edf7e'} |
GHSA | GHSA-qjw2-hr98-qgfh | Unsafe Deserialization in jackson-databind | FasterXML jackson-databind 2.x before 2.6.7.5 and from 2.7.x before 2.9.10.6 mishandles the interaction between serialization gadgets and typing, related to com.pastdev.httpcomponents.configuration.JndiConfiguration. | {'CVE-2020-24750'} | 2022-04-26T20:58:39Z | 2021-12-09T19:15:36Z | HIGH | 8.1 | {'CWE-502'} | {'https://lists.debian.org/debian-lts-announce/2021/04/msg00025.html', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://security.netapp.com/advisory/ntap-20201009-0003/', 'https://github.com/advisories/GHSA-qjw2-hr98-qgfh', 'https://nvd.nist.gov/vuln/detail/CVE-2020-24750', 'https://github.com/FasterXML/jackson-databind/issues/2798', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://github.com/FasterXML/jackson-databind/commit/ad5a630174f08d279504bc51ebba8772fd71b86b', 'https://github.com/FasterXML/jackson-databind/commit/2118e71325486c68f089a9761c9d8a11b4ddd1cb', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://www.oracle.com/security-alerts/cpujan2021.html', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/FasterXML/jackson-databind/commit/2118e71325486c68f089a9761c9d8a11b4ddd1cb', 'https://github.com/FasterXML/jackson-databind/commit/ad5a630174f08d279504bc51ebba8772fd71b86b'} | {'https://github.com/FasterXML/jackson-databind/commit/2118e71325486c68f089a9761c9d8a11b4ddd1cb', 'https://github.com/FasterXML/jackson-databind/commit/ad5a630174f08d279504bc51ebba8772fd71b86b'} |
GHSA | GHSA-hxmp-pqch-c8mm | Denial of service attack via incorrect parameters in Matrix Synapse | ### Impact
A malicious or poorly-implemented homeserver can inject malformed events into a room by specifying a different room id in the path of a `/send_join`, `/send_leave`, `/invite` or `/exchange_third_party_invite` request.
This can lead to a denial of service in which future events will not be correctly sent to other servers over federation.
This affects any server which accepts federation requests from untrusted servers.
### Patches
Issue is resolved by https://github.com/matrix-org/synapse/pull/8776.
### Workarounds
Homeserver administrators could limit access to the federation API to trusted servers (for example via `federation_domain_whitelist`). | {'CVE-2020-26257'} | 2021-01-07T22:37:52Z | 2020-12-09T18:21:29Z | LOW | 6.5 | {'CWE-74', 'CWE-79', 'CWE-400'} | {'https://github.com/matrix-org/synapse/pull/8776', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26257', 'https://github.com/matrix-org/synapse/security/advisories/GHSA-hxmp-pqch-c8mm', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QR4MMYZKX5N5GYGH4H5LBUUC5TLAFHI7/', 'https://github.com/matrix-org/synapse/blob/develop/CHANGES.md#synapse-1231-2020-12-09', 'https://github.com/advisories/GHSA-hxmp-pqch-c8mm', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DBTIU3ZNBFWZ56V4X7JIAD33V5H2GOMC/', 'https://github.com/matrix-org/synapse/commit/3ce2f303f15f6ac3dc352298972dc6e04d9b7a8b'} | null | {'https://github.com/matrix-org/synapse/commit/3ce2f303f15f6ac3dc352298972dc6e04d9b7a8b'} | {'https://github.com/matrix-org/synapse/commit/3ce2f303f15f6ac3dc352298972dc6e04d9b7a8b'} |
GHSA | GHSA-57q7-rxqq-7vgp | On Windows, `git-sizer` might run a `git` executable within the repository being analyzed | ### Impact
On Windows, if `git-sizer` is run against a non-bare repository, and that repository has an executable called `git.exe`, `git.bat`, etc., then that executable might be run by `git-sizer` rather than the system `git` executable. An attacker could try to use social engineering to get a victim to run `git-sizer` against a hostile repository and thereby get the victim to run arbitrary code.
On Linux or other Unix-derived platforms, a similar problem could occur if the user's `PATH` has the current directory before the path to the standard `git` executable, but this is would be a very unusual configuration that has been known for decades to lead to all kinds of security problems.
### Patches
Users should update to git-sizer v1.4.0
### Workarounds
If you are on Windows, then either
* Don't run `git-sizer` against a repository that might contain hostile code, or, if you must…
* Run `git-sizer` against a bare clone of the hostile repository, or, if that is not possible…
* Make sure that the hostile repository doesn't have an executable in its top-level directory before running `git-sizer`.
If you are on Linux or other Unix-based system, then (for myriad reasons!) don't add the current directory to your `PATH`.
### References
* [Command PATH security in Go](https://blog.golang.org/path-security)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the `git-sizer` project](https://github.com/github/git-sizer).
* Email us at [GitHub support](mailto:support@github.com). | null | 2022-04-12T22:48:44Z | 2022-02-15T01:57:18Z | MODERATE | 0 | null | {'https://github.com/github/git-sizer/security/advisories/GHSA-57q7-rxqq-7vgp', 'https://github.com/advisories/GHSA-57q7-rxqq-7vgp', 'https://github.com/github/git-sizer/commit/38400d6ddd79325e956b00ff584cfcc8dd96d536'} | null | {'https://github.com/github/git-sizer/commit/38400d6ddd79325e956b00ff584cfcc8dd96d536'} | {'https://github.com/github/git-sizer/commit/38400d6ddd79325e956b00ff584cfcc8dd96d536'} |
GHSA | GHSA-5f38-9jw2-6r6h | Cross-site Scripting in teddy | Teddy is a readable and easy to learn templating language. This affects the package teddy before 0.5.9. A type confusion vulnerability can be used to bypass input sanitization when the model content is an array (instead of a string). | {'CVE-2021-23447'} | 2022-05-05T13:48:52Z | 2021-10-12T16:22:04Z | MODERATE | 5.4 | {'CWE-79', 'CWE-843'} | {'https://github.com/rooseveltframework/teddy/commit/64c556717b4879bf8d4c30067cf6e70d899a3dc0', 'https://github.com/rooseveltframework/teddy/releases/tag/0.5.9', 'https://github.com/advisories/GHSA-5f38-9jw2-6r6h', 'https://github.com/rooseveltframework/teddy/pull/518', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23447', 'https://snyk.io/vuln/SNYK-JS-TEDDY-1579557'} | null | {'https://github.com/rooseveltframework/teddy/commit/64c556717b4879bf8d4c30067cf6e70d899a3dc0'} | {'https://github.com/rooseveltframework/teddy/commit/64c556717b4879bf8d4c30067cf6e70d899a3dc0'} |
GHSA | GHSA-78vq-9j56-wrfr | Cross-site Scripting in gon | An issue was discovered in the gon gem before gon-6.4.0 for Ruby. MultiJson does not honor the escape_mode parameter to escape fields as an XSS protection mechanism. To mitigate, json_dumper.rb in gon now does escaping for XSS by default without relying on MultiJson. | {'CVE-2020-25739'} | 2021-04-30T17:29:15Z | 2021-04-30T17:29:15Z | MODERATE | 6.1 | {'CWE-79'} | {'https://usn.ubuntu.com/4560-1/', 'https://github.com/advisories/GHSA-78vq-9j56-wrfr', 'https://lists.debian.org/debian-lts-announce/2020/09/msg00018.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-25739', 'https://github.com/gazay/gon/commit/fe3c7b2191a992386dc9edd37de5447a4e809bc7'} | null | {'https://github.com/gazay/gon/commit/fe3c7b2191a992386dc9edd37de5447a4e809bc7'} | {'https://github.com/gazay/gon/commit/fe3c7b2191a992386dc9edd37de5447a4e809bc7'} |
GHSA | GHSA-r4gv-vj59-cccm | Control character injection in console output in github.com/ipfs/go-ipfs | ### Impact
Control characters are not escaped from console output. This can result in hiding input from the user which could result in the user taking an unknown, malicious action.
### Patches
<!-- _Has the problem been patched? What versions should users upgrade to?_ -->
- Patched via https://github.com/ipfs/go-ipfs/pull/7831 in v0.8.0
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [go-ipfs](http://github.com/ipfs/go-ipfs)
* Email us at [security@ipfs.io](mailto:security@ipfs.io) | {'CVE-2020-26283'} | 2022-04-19T19:02:51Z | 2021-06-23T17:27:27Z | MODERATE | 6.8 | {'CWE-116', 'CWE-150'} | {'https://github.com/advisories/GHSA-r4gv-vj59-cccm', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26283', 'https://github.com/ipfs/go-ipfs/commit/fb0a9acd2d8288bd1028c3219a420de62a09683a', 'https://github.com/ipfs/go-ipfs/security/advisories/GHSA-r4gv-vj59-cccm', 'https://github.com/ipfs/go-ipfs/pull/7831'} | null | {'https://github.com/ipfs/go-ipfs/commit/fb0a9acd2d8288bd1028c3219a420de62a09683a'} | {'https://github.com/ipfs/go-ipfs/commit/fb0a9acd2d8288bd1028c3219a420de62a09683a'} |
GHSA | GHSA-4q69-q4q7-x82c | High severity vulnerability that affects rendertron | Rendertron 1.0.0 includes an _ah/stop route to shutdown the Chrome instance responsible for serving render requests to all users. Visiting this route with a GET request allows any unauthorized remote attacker to disable the core service of the application. | {'CVE-2017-18353'} | 2021-09-01T17:52:46Z | 2019-01-04T17:41:46Z | HIGH | 7.5 | null | {'https://github.com/GoogleChrome/rendertron/pull/88', 'https://github.com/GoogleChrome/rendertron/commit/8d70628c96ae72eff6eebb451d26fc9ed6b58b0e', 'https://github.com/advisories/GHSA-4q69-q4q7-x82c', 'https://nvd.nist.gov/vuln/detail/CVE-2017-18353', 'https://bugs.chromium.org/p/chromium/issues/detail?id=759111'} | null | {'https://github.com/GoogleChrome/rendertron/commit/8d70628c96ae72eff6eebb451d26fc9ed6b58b0e'} | {'https://github.com/GoogleChrome/rendertron/commit/8d70628c96ae72eff6eebb451d26fc9ed6b58b0e'} |
GHSA | GHSA-83rh-hx5x-q9p5 | Out-of-bounds Read in OpenCV | In OpenCV 3.3.1 (corresponding with OpenCV-Python 3.3.1.11), a heap-based buffer over-read exists in the function cv::HdrDecoder::checkSignature in modules/imgcodecs/src/grfmt_hdr.cpp. | {'CVE-2017-18009'} | 2021-10-12T22:03:23Z | 2021-10-12T22:03:23Z | HIGH | 7.5 | {'CWE-125'} | {'http://www.securityfocus.com/bid/106945', 'https://github.com/opencv/opencv/issues/10479', 'https://nvd.nist.gov/vuln/detail/CVE-2017-18009', 'https://github.com/opencv/opencv/pull/10480/commits/4ca89db22dea962690f31c1781bce5937ee91837', 'https://github.com/advisories/GHSA-83rh-hx5x-q9p5'} | null | {'https://github.com/opencv/opencv/pull/10480/commits/4ca89db22dea962690f31c1781bce5937ee91837'} | {'https://github.com/opencv/opencv/pull/10480/commits/4ca89db22dea962690f31c1781bce5937ee91837'} |
GHSA | GHSA-75f6-78jr-4656 | Null pointer dereference in `EditDistance` | ### Impact
An attacker can trigger a null pointer dereference in the implementation of `tf.raw_ops.EditDistance`:
```python
import tensorflow as tf
hypothesis_indices = tf.constant([247, 247, 247], shape=[1, 3], dtype=tf.int64)
hypothesis_values = tf.constant([-9.9999], shape=[1], dtype=tf.float32)
hypothesis_shape = tf.constant([0, 0, 0], shape=[3], dtype=tf.int64)
truth_indices = tf.constant([], shape=[0, 3], dtype=tf.int64)
truth_values = tf.constant([], shape=[0], dtype=tf.float32)
truth_shape = tf.constant([0, 0, 0], shape=[3], dtype=tf.int64)
tf.raw_ops.EditDistance(
hypothesis_indices=hypothesis_indices, hypothesis_values=hypothesis_values,
hypothesis_shape=hypothesis_shape, truth_indices=truth_indices,
truth_values=truth_values, truth_shape=truth_shape, normalize=True)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/79865b542f9ffdc9caeb255631f7c56f1d4b6517/tensorflow/core/kernels/edit_distance_op.cc#L103-L159) has incomplete validation of the input parameters.
In the above scenario, an attacker causes an allocation of an empty tensor for the output:
```cc
OP_REQUIRES_OK(ctx, ctx->allocate_output("output", output_shape, &output));
auto output_t = output->flat<float>();
output_t.setZero();
```
Because `output_shape` has 0 elements, the result of `output->flat<T>()` has an empty buffer, so calling `setZero` would result in a null dereference.
### Patches
We have patched the issue in GitHub commit [f4c364a5d6880557f6f5b6eb5cee2c407f0186b3](https://github.com/tensorflow/tensorflow/commit/f4c364a5d6880557f6f5b6eb5cee2c407f0186b3).
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 Yakun Zhang and Ying Wang of Baidu X-Team. | {'CVE-2021-29564'} | 2021-05-21T14:25:08Z | 2021-05-21T14:25:08Z | LOW | 2.5 | {'CWE-476'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-75f6-78jr-4656', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29564', 'https://github.com/advisories/GHSA-75f6-78jr-4656', 'https://github.com/tensorflow/tensorflow/commit/f4c364a5d6880557f6f5b6eb5cee2c407f0186b3'} | null | {'https://github.com/tensorflow/tensorflow/commit/f4c364a5d6880557f6f5b6eb5cee2c407f0186b3'} | {'https://github.com/tensorflow/tensorflow/commit/f4c364a5d6880557f6f5b6eb5cee2c407f0186b3'} |
GHSA | GHSA-c2w9-48qc-qpj4 | High severity vulnerability that affects ansible | An exploitable vulnerability exists in the yaml loading functionality of ansible-vault before 1.0.5. A specially crafted vault can execute arbitrary python commands resulting in command execution. An attacker can insert python into the vault to trigger this vulnerability. | {'CVE-2017-2809'} | 2021-09-08T21:28:07Z | 2018-07-13T15:16:54Z | HIGH | 7.8 | {'CWE-94'} | {'https://github.com/tomoh1r/ansible-vault/commit/3f8f659ef443ab870bb19f95d43543470168ae04', 'https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0305', 'https://github.com/advisories/GHSA-c2w9-48qc-qpj4', 'http://www.securityfocus.com/bid/100824', 'https://nvd.nist.gov/vuln/detail/CVE-2017-2809', 'https://github.com/tomoh1r/ansible-vault/blob/v1.0.5/CHANGES.txt', 'https://github.com/tomoh1r/ansible-vault/issues/4'} | null | {'https://github.com/tomoh1r/ansible-vault/commit/3f8f659ef443ab870bb19f95d43543470168ae04'} | {'https://github.com/tomoh1r/ansible-vault/commit/3f8f659ef443ab870bb19f95d43543470168ae04'} |
GHSA | GHSA-j5hj-fhc9-g24m | Moderate severity vulnerability that affects rack-mini-profiler | The rack-mini-profiler gem before 0.10.1 for Ruby allows remote attackers to obtain sensitive information about allocated strings and objects by leveraging incorrect ordering of security checks. | {'CVE-2016-4442'} | 2021-09-14T18:19:21Z | 2017-10-24T18:33:35Z | MODERATE | 5.3 | {'CWE-200'} | {'https://github.com/MiniProfiler/rack-mini-profiler/commit/4273771d65f1a7411e3ef5843329308d0e2d257c', 'https://github.com/advisories/GHSA-j5hj-fhc9-g24m', 'https://github.com/MiniProfiler/rack-mini-profiler/blob/v0.10.1/CHANGELOG.md', 'http://www.openwall.com/lists/oss-security/2016/06/10/2', 'https://nvd.nist.gov/vuln/detail/CVE-2016-4442'} | null | {'https://github.com/MiniProfiler/rack-mini-profiler/commit/4273771d65f1a7411e3ef5843329308d0e2d257c'} | {'https://github.com/MiniProfiler/rack-mini-profiler/commit/4273771d65f1a7411e3ef5843329308d0e2d257c'} |
GHSA | GHSA-83vp-6jqg-6cmr | Incorrect Authentication in shopware | ### Impact
Modify Customers, create Orders without App Permission
## Patches
We recommend updating to the current version 6.4.8.2. You can get the update to 6.4.8.2 regularly via the Auto-Updater or directly via the download overview.
https://www.shopware.com/en/download/#shopware-6
## Workarounds
For older versions of 6.1, 6.2, and 6.3, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version. | {'CVE-2022-24748'} | 2022-03-18T20:15:33Z | 2022-03-10T18:02:14Z | MODERATE | 6.8 | {'CWE-287'} | {'https://github.com/advisories/GHSA-83vp-6jqg-6cmr', 'https://github.com/shopware/platform/security/advisories/GHSA-83vp-6jqg-6cmr', 'https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-03-2022?_ga=2.27683580.172848620.1646933022-368790926.1646933022', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24748', 'https://github.com/shopware/core/commit/329e4d7e028dd8081496cf8bd3acc822000b0ec0'} | null | {'https://github.com/shopware/core/commit/329e4d7e028dd8081496cf8bd3acc822000b0ec0'} | {'https://github.com/shopware/core/commit/329e4d7e028dd8081496cf8bd3acc822000b0ec0'} |
GHSA | GHSA-32wr-8wxm-852c | Deserialization of Untrusted Data in NukeViet | includes/core/is_user.php in NukeViet before 4.3.04 deserializes the untrusted nvloginhash cookie (i.e., the code relies on PHP's serialization format when JSON can be used to eliminate the risk). | {'CVE-2019-7725'} | 2021-06-22T15:24:59Z | 2021-06-22T15:24:59Z | CRITICAL | 9.8 | {'CWE-502'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-7725', 'https://github.com/nukeviet/nukeviet/blob/4.3.04/CHANGELOG.txt', 'https://github.com/nukeviet/nukeviet/blob/nukeviet4.3/CHANGELOG.txt', 'https://github.com/nukeviet/nukeviet/compare/4.3.03...4.3.04', 'https://github.com/advisories/GHSA-32wr-8wxm-852c', 'https://github.com/nukeviet/nukeviet/pull/2740/commits/05dfb9b4531f12944fe39556f58449b9a56241be'} | null | {'https://github.com/nukeviet/nukeviet/pull/2740/commits/05dfb9b4531f12944fe39556f58449b9a56241be'} | {'https://github.com/nukeviet/nukeviet/pull/2740/commits/05dfb9b4531f12944fe39556f58449b9a56241be'} |
GHSA | GHSA-qx4v-6gc5-f2vv | Regular Expression Denial of Service | A Regular Expression Denial of Service vulnerability was discovered in esm before 3.1.0. The issue is that esm's find-indexes is using the unescaped identifiers in a regex, which, in this case, causes an infinite loop. | null | 2021-02-25T17:21:01Z | 2019-06-20T14:32:56Z | MODERATE | 0 | {'CWE-400'} | {'https://github.com/standard-things/esm/issues/694', 'https://github.com/advisories/GHSA-qx4v-6gc5-f2vv', 'https://github.com/standard-things/esm/commit/c41e001d81a5a52b0d2d1722b1c2af04d997c05b'} | null | {'https://github.com/standard-things/esm/commit/c41e001d81a5a52b0d2d1722b1c2af04d997c05b'} | {'https://github.com/standard-things/esm/commit/c41e001d81a5a52b0d2d1722b1c2af04d997c05b'} |
GHSA | GHSA-5crj-c72x-m7gq | Null pointer exception when `Exit` node is not preceded by `Enter` op | ### Impact
The [process of building the control flow graph](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/common_runtime/immutable_executor_state.cc#L284-L346) for a TensorFlow model is vulnerable to a null pointer exception when nodes that should be paired are not:
```python
import tensorflow as tf
@tf.function
def func():
return tf.raw_ops.Exit(data=[False,False])
func()
```
This occurs because the code assumes that the first node in the pairing (e.g., an `Enter` node) always exists when encountering the second node (e.g., an `Exit` node):
```cc
...
} else if (IsExit(curr_node)) {
// Exit to the parent frame.
parent = parent_nodes[curr_id];
frame_name = cf_info->frame_names[parent->id()];
...
```
When this is not the case, `parent` is `nullptr` so dereferencing it causes a crash.
### Patches
We have patched the issue in GitHub commit [05cbebd3c6bb8f517a158b0155debb8df79017ff](https://github.com/tensorflow/tensorflow/commit/05cbebd3c6bb8f517a158b0155debb8df79017ff).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.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-41217'} | 2021-11-10T18:55:11Z | 2021-11-10T18:55:11Z | MODERATE | 5.5 | {'CWE-476'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-41217', 'https://github.com/tensorflow/tensorflow/commit/05cbebd3c6bb8f517a158b0155debb8df79017ff', 'https://github.com/advisories/GHSA-5crj-c72x-m7gq', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-5crj-c72x-m7gq'} | null | {'https://github.com/tensorflow/tensorflow/commit/05cbebd3c6bb8f517a158b0155debb8df79017ff'} | {'https://github.com/tensorflow/tensorflow/commit/05cbebd3c6bb8f517a158b0155debb8df79017ff'} |
GHSA | GHSA-pgf8-28gg-vpr6 | Path traversal | ### Impact
A malicious actor could read sensitive files from the environment where TechDocs documentation is built and published by setting a particular path for `docs_dir` in `mkdocs.yml`. These files would then be available over the TechDocs backend API.
This vulnerability is mitigated by the fact that an attacker would need access to modify the `mkdocs.yml` in the documentation source code, and would also need access to the TechDocs backend API.
### Patches
The vulnerability is patched in the `0.6.3` release of `@backstage/techdocs-common`.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [Backstage repository](https://github.com/backstage/backstage)
* Visit our chat, linked to in [Backstage README](https://github.com/backstage/backstage) | {'CVE-2021-32662'} | 2021-06-07T18:55:30Z | 2021-06-04T19:09:20Z | MODERATE | 6.5 | {'CWE-22'} | {'https://github.com/backstage/backstage/commit/8cefadca04cbf01d0394b0cb1983247e5f1d6208', 'https://github.com/advisories/GHSA-pgf8-28gg-vpr6', 'https://github.com/backstage/backstage/releases/tag/release-2021-05-27', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32662', 'https://github.com/backstage/backstage/security/advisories/GHSA-pgf8-28gg-vpr6'} | null | {'https://github.com/backstage/backstage/commit/8cefadca04cbf01d0394b0cb1983247e5f1d6208'} | {'https://github.com/backstage/backstage/commit/8cefadca04cbf01d0394b0cb1983247e5f1d6208'} |
GHSA | GHSA-rgp5-m2pq-3fmg | Cross-site Scripting in microweber | microweber prior to version 1.2.11 is vulnerable to cross-site scripting. | {'CVE-2022-0690'} | 2022-02-26T01:15:28Z | 2022-02-20T00:00:31Z | HIGH | 8.8 | {'CWE-79'} | {'https://huntr.dev/bounties/4999a0f4-6efb-4681-b4ba-b36babc366f9', 'https://github.com/advisories/GHSA-rgp5-m2pq-3fmg', 'https://github.com/microweber/microweber/commit/f7f5d41ba1a08ceed37c00d5f70a3f48b272e9f2', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0690'} | null | {'https://github.com/microweber/microweber/commit/f7f5d41ba1a08ceed37c00d5f70a3f48b272e9f2'} | {'https://github.com/microweber/microweber/commit/f7f5d41ba1a08ceed37c00d5f70a3f48b272e9f2'} |
GHSA | GHSA-cqv6-3phm-hcwx | Access to invalid memory during shape inference in `Cudnn*` ops | ### Impact
The [shape inference code](https://github.com/tensorflow/tensorflow/blob/9ff27787893f76d6971dcd1552eb5270d254f31b/tensorflow/core/ops/cudnn_rnn_ops.cc) for the `Cudnn*` operations in TensorFlow can be tricked into accessing invalid memory, via a heap buffer overflow:
```python
import tensorflow as tf
@tf.function
def func():
return tf.raw_ops.CudnnRNNV3(
input=[0.1, 0.1],
input_h=[0.5],
input_c=[0.1, 0.1, 0.1],
params=[0.5, 0.5],
sequence_lengths=[-1, 0, 1])
func()
```
This occurs because the ranks of the `input`, `input_h` and `input_c` parameters are not validated, but code assumes they have certain values:
```cc
auto input_shape = c->input(0);
auto input_h_shape = c->input(1);
auto seq_length = c->Dim(input_shape, 0);
auto batch_size = c->Dim(input_shape, 1); // assumes rank >= 2
auto num_units = c->Dim(input_h_shape, 2); // assumes rank >= 3
```
### Patches
We have patched the issue in GitHub commit [af5fcebb37c8b5d71c237f4e59c6477015c78ce6](https://github.com/tensorflow/tensorflow/commit/af5fcebb37c8b5d71c237f4e59c6477015c78ce6).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.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-41221'} | 2021-11-10T18:50:17Z | 2021-11-10T18:50:17Z | HIGH | 7.8 | {'CWE-787', 'CWE-120'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cqv6-3phm-hcwx', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41221', 'https://github.com/advisories/GHSA-cqv6-3phm-hcwx', 'https://github.com/tensorflow/tensorflow/commit/af5fcebb37c8b5d71c237f4e59c6477015c78ce6'} | null | {'https://github.com/tensorflow/tensorflow/commit/af5fcebb37c8b5d71c237f4e59c6477015c78ce6'} | {'https://github.com/tensorflow/tensorflow/commit/af5fcebb37c8b5d71c237f4e59c6477015c78ce6'} |
GHSA | GHSA-gq67-pp9w-43gp | Cryptographically weak CSRF tokens in Apache MyFaces | In the default configuration, Apache MyFaces Core versions 2.2.0 to 2.2.13, 2.3.0 to 2.3.7, 2.3-next-M1 to 2.3-next-M4, and 3.0.0-RC1 use cryptographically weak implicit and explicit cross-site request forgery (CSRF) tokens. Due to that limitation, it is possible (although difficult) for an attacker to calculate a future CSRF token value and to use that value to trick a user into executing unwanted actions on an application.
Mitigation:
Existing web.xml configuration parameters can be used to direct
MyFaces to use SecureRandom for CSRF token generation:
org.apache.myfaces.RANDOM_KEY_IN_VIEW_STATE_SESSION_TOKEN=secureRandom
org.apache.myfaces.RANDOM_KEY_IN_CSRF_SESSION_TOKEN=secureRandom
org.apache.myfaces.RANDOM_KEY_IN_WEBSOCKET_SESSION_TOKEN=secureRandom | {'CVE-2021-26296'} | 2021-06-16T17:31:39Z | 2021-06-16T17:31:39Z | HIGH | 0 | {'CWE-352', 'CWE-330'} | {'https://security.netapp.com/advisory/ntap-20210528-0007/', 'https://lists.apache.org/thread.html/r2b73e2356c6155e9ec78fdd8f72a4fac12f3e588014f5f535106ed9b%40%3Cannounce.apache.org%3E', 'https://github.com/apache/myfaces/commit/cc6e1cc7b9aa17e52452f7f2657b3af9c421b2b2', 'https://issues.apache.org/jira/browse/MYFACES-4373', 'https://github.com/advisories/GHSA-gq67-pp9w-43gp', 'http://seclists.org/fulldisclosure/2021/Feb/66', 'http://packetstormsecurity.com/files/161484/Apache-MyFaces-2.x-Cross-Site-Request-Forgery.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-26296'} | null | {'https://github.com/apache/myfaces/commit/cc6e1cc7b9aa17e52452f7f2657b3af9c421b2b2'} | {'https://github.com/apache/myfaces/commit/cc6e1cc7b9aa17e52452f7f2657b3af9c421b2b2'} |
GHSA | GHSA-46hv-7769-j7rx | Unauthorized File Access in harp | Affected versions of `harp` are vulnerable to Unauthorized File Access. The package states that it ignores files and directories with names that start with an underscore, such as `_secret-folder`. If the underscore character is URL encoded the server delivers the file.
## Recommendation
Upgrade to version `0.40.2` or later. | {'CVE-2019-5437'} | 2021-06-03T17:09:41Z | 2019-06-13T16:12:22Z | MODERATE | 0 | {'CWE-548'} | {'https://github.com/sintaxi/harp/commit/1ec790baeeb2bfdb4584f1998af3d10a8fa31210', 'https://www.npmjs.com/advisories/807', 'https://github.com/advisories/GHSA-46hv-7769-j7rx', 'https://nvd.nist.gov/vuln/detail/CVE-2019-5437', 'https://hackerone.com/reports/453820'} | null | {'https://github.com/sintaxi/harp/commit/1ec790baeeb2bfdb4584f1998af3d10a8fa31210'} | {'https://github.com/sintaxi/harp/commit/1ec790baeeb2bfdb4584f1998af3d10a8fa31210'} |
GHSA | GHSA-f4g9-h89h-jgv9 | SAML XML Signature wrapping 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 validate the SAML document against an XML schema. This allows invalid XML documents to trick the verification process, by presenting elements with a valid signature inside elements whose content has been malformed. The verification is offloaded to `xmlsec1` and `xmlsec1` will not validate every signature in the given document, but only the first it finds in the given scope.
### Patches
Users should upgrade to pysaml2 `v6.5.0`.
### Workarounds
No workaround provided at this point.
### References
No references provided at this point.
### Credits
- Victor Schönfelder Garcia (isits AG International School of IT Security)
- Juraj Somorovsky (Paderborn University)
- Vladislav Mladenov (Ruhr University Bochum)
### 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-21238'} | 2022-04-19T19:02:44Z | 2021-01-21T14:12:16Z | LOW | 6.5 | {'CWE-347'} | {'https://github.com/IdentityPython/pysaml2/releases/tag/v6.5.0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21238', 'https://pypi.org/project/pysaml2', 'https://github.com/advisories/GHSA-f4g9-h89h-jgv9', 'https://github.com/IdentityPython/pysaml2/security/advisories/GHSA-f4g9-h89h-jgv9', 'https://github.com/IdentityPython/pysaml2/commit/1d8fd268f5bf887480a403a7a5ef8f048157cc14'} | null | {'https://github.com/IdentityPython/pysaml2/commit/1d8fd268f5bf887480a403a7a5ef8f048157cc14'} | {'https://github.com/IdentityPython/pysaml2/commit/1d8fd268f5bf887480a403a7a5ef8f048157cc14'} |
GHSA | GHSA-g44j-7vp3-68cv | Arbitrary File Write in Libcontainer | Libcontainer 1.6.0, as used in Docker Engine, allows local users to escape containerization ("mount namespace breakout") and write to arbitrary file on the host system via a symlink attack in an image when respawning a container. | {'CVE-2015-3629'} | 2022-04-12T22:13:08Z | 2022-02-15T01:57:18Z | HIGH | 8.4 | {'CWE-59'} | {'https://groups.google.com/forum/#%21searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ', 'http://seclists.org/fulldisclosure/2015/May/28', 'http://lists.opensuse.org/opensuse-updates/2015-05/msg00023.html', 'https://groups.google.com/forum/#!searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ', 'http://www.securityfocus.com/bid/74558', 'http://packetstormsecurity.com/files/131835/Docker-Privilege-Escalation-Information-Disclosure.html', 'https://github.com/docker/docker/commit/d5ebb60bddbabea0439213501f4f6ed494b23cba', 'https://github.com/advisories/GHSA-g44j-7vp3-68cv', 'https://nvd.nist.gov/vuln/detail/CVE-2015-3629', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-3629'} | null | {'https://github.com/docker/docker/commit/d5ebb60bddbabea0439213501f4f6ed494b23cba'} | {'https://github.com/docker/docker/commit/d5ebb60bddbabea0439213501f4f6ed494b23cba'} |
GHSA | GHSA-q9p4-qfc8-fvpp | SQL Injection in medoo | columnQuote in medoo before 1.7.5 allows remote attackers to perform a SQL Injection due to improper escaping. | {'CVE-2019-10762'} | 2021-10-12T16:32:38Z | 2021-10-12T16:32:38Z | CRITICAL | 9.8 | {'CWE-89'} | {'https://snyk.io/vuln/SNYK-PHP-CATFANMEDOO-474562', 'https://github.com/catfan/Medoo/commit/659864b393961bf224bba1efc03b7dcbed7de533', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10762', 'https://github.com/advisories/GHSA-q9p4-qfc8-fvpp'} | null | {'https://github.com/catfan/Medoo/commit/659864b393961bf224bba1efc03b7dcbed7de533'} | {'https://github.com/catfan/Medoo/commit/659864b393961bf224bba1efc03b7dcbed7de533'} |
GHSA | GHSA-w457-6q6x-cgp9 | Prototype Pollution in handlebars | Versions of `handlebars` prior to 3.0.8 or 4.3.0 are vulnerable to Prototype Pollution leading to Remote Code Execution. Templates may alter an Objects' `__proto__` and `__defineGetter__` properties, which may allow an attacker to execute arbitrary code through crafted payloads.
## Recommendation
Upgrade to version 3.0.8, 4.3.0 or later. | {'CVE-2019-19919'} | 2021-07-26T21:51:07Z | 2019-12-26T17:58:13Z | CRITICAL | 9.8 | {'CWE-74'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-19919', 'https://github.com/wycats/handlebars.js/issues/1558', 'https://www.npmjs.com/advisories/1164', 'https://github.com/advisories/GHSA-w457-6q6x-cgp9', 'https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19919', 'https://github.com/wycats/handlebars.js/commit/2078c727c627f25d4a149962f05c1e069beb18bc'} | null | {'https://github.com/wycats/handlebars.js/commit/2078c727c627f25d4a149962f05c1e069beb18bc'} | {'https://github.com/wycats/handlebars.js/commit/2078c727c627f25d4a149962f05c1e069beb18bc'} |
GHSA | GHSA-vj9x-w7ch-f46p | pimcore is vulnerable to SQL Injection | pimcore is vulnerable to Improper Neutralization of Special Elements used in an SQL Command | {'CVE-2022-0258'} | 2022-01-21T23:50:08Z | 2022-01-21T23:50:08Z | HIGH | 8.3 | {'CWE-89'} | {'https://github.com/pimcore/pimcore/commit/66281c12479dc01a06258d8533eaddfb1770d5bd', 'https://github.com/advisories/GHSA-vj9x-w7ch-f46p', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0258', 'https://huntr.dev/bounties/0df891e4-6412-4d9a-a9b7-d9df50311802'} | null | {'https://github.com/pimcore/pimcore/commit/66281c12479dc01a06258d8533eaddfb1770d5bd'} | {'https://github.com/pimcore/pimcore/commit/66281c12479dc01a06258d8533eaddfb1770d5bd'} |
GHSA | GHSA-xjp4-6w75-qrj7 | Remote CLI Command Execution Vulnerability in CodeIgniter4 | ### Impact
This vulnerability allows attackers to execute CLI routes via HTTP request.
### Patches
Upgrade to v4.1.9 or later.
### Workarounds
None.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [codeigniter4/CodeIgniter4](https://github.com/codeigniter4/CodeIgniter4/issues)
* Email us at [SECURITY.md](https://github.com/codeigniter4/CodeIgniter4/blob/develop/SECURITY.md)
| {'CVE-2022-24711'} | 2022-04-19T19:03:22Z | 2022-03-01T21:44:13Z | CRITICAL | 9.4 | {'CWE-94', 'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-24711', 'https://github.com/advisories/GHSA-xjp4-6w75-qrj7', 'https://github.com/codeigniter4/CodeIgniter4/security/advisories/GHSA-xjp4-6w75-qrj7', 'https://github.com/codeigniter4/CodeIgniter4/commit/202f41ad522ba1d414b9d9c35aba1cb0c156b781'} | null | {'https://github.com/codeigniter4/CodeIgniter4/commit/202f41ad522ba1d414b9d9c35aba1cb0c156b781'} | {'https://github.com/codeigniter4/CodeIgniter4/commit/202f41ad522ba1d414b9d9c35aba1cb0c156b781'} |
GHSA | GHSA-6jmr-jfh7-xg3h | False-positive validity for NFT1 genesis transactions | ### Impact
In the npm package named "slp-validate", versions prior to 1.2.2 are vulnerable to false-positive validation outcomes for the NFT1 Child Genesis transaction type. A poorly implemented SLP wallet or opportunistic attacker could create a seemingly valid NFT1 child token without burning any of the NFT1 Group token type as is required by the NFT1 specification.
### Patches
npm package "slp-validate" has been patched and is published and tagged as version 1.2.2.
### Workarounds
Upgrade to slp-validate 1.2.2.
### References
* Package location: https://www.npmjs.com/package/slp-validate
* SLP NFT1 spec: https://slp.dev/specs/slp-nft-1/#nft1-protocol-requirements
* Git commit hash fixing this issue: https://github.com/simpleledger/slp-validate.js/commit/3963cf914afae69084059b82483da916d97af65c
* Unit tests have been added to assist validator implementations in avoiding this bug: https://github.com/simpleledger/slp-unit-test-data/commit/8c942eacfae12686dcf1f3366321445a4fba73e7
### For more information
If you have any questions or comments about this advisory please open an issue in the [slp-validate](https://github.com/simpleledger/slp-validate.js/issues) repository. | {'CVE-2020-15131'} | 2021-01-08T21:00:18Z | 2020-07-30T14:58:53Z | CRITICAL | 7.5 | {'CWE-697'} | {'https://github.com/simpleledger/slp-validate.js/commit/3963cf914afae69084059b82483da916d97af65c', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15131', 'https://github.com/advisories/GHSA-6jmr-jfh7-xg3h', 'https://github.com/simpleledger/slp-validate.js/security/advisories/GHSA-6jmr-jfh7-xg3h'} | null | {'https://github.com/simpleledger/slp-validate.js/commit/3963cf914afae69084059b82483da916d97af65c'} | {'https://github.com/simpleledger/slp-validate.js/commit/3963cf914afae69084059b82483da916d97af65c'} |
GHSA | GHSA-j59f-6m4q-62h6 | Improper Key Verification in ipns | Versions 0.1.1 or 0.1.2 of `ipns` are vulnerable to improper key validation. This is due to the public key verification was not being performed properly, resulting in any key being valid.
## Recommendation
Update to version 0.1.3 or later. | null | 2021-08-04T21:17:51Z | 2019-05-30T17:28:48Z | HIGH | 7.5 | {'CWE-287'} | {'https://github.com/advisories/GHSA-j59f-6m4q-62h6', 'https://github.com/ipfs/js-ipns/commit/33684e356f1f2fdcd99b2fb85fcc5d52223769a0', 'https://www.npmjs.com/advisories/693'} | null | {'https://github.com/ipfs/js-ipns/commit/33684e356f1f2fdcd99b2fb85fcc5d52223769a0'} | {'https://github.com/ipfs/js-ipns/commit/33684e356f1f2fdcd99b2fb85fcc5d52223769a0'} |
GHSA | GHSA-c3xq-cj8f-7829 | Inadequate Encryption Strength in python-keystoneclient | python-keystoneclient version 0.2.3 to 0.2.5 has middleware memcache encryption bypass | {'CVE-2013-2166'} | 2022-03-23T19:45:18Z | 2021-10-12T16:31:43Z | CRITICAL | 9.8 | {'CWE-326'} | {'http://www.openwall.com/lists/oss-security/2013/06/19/5', 'http://www.securityfocus.com/bid/60684', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-2166', 'http://lists.fedoraproject.org/pipermail/package-announce/2013-August/113944.html', 'https://nvd.nist.gov/vuln/detail/CVE-2013-2166', 'https://github.com/openstack/python-keystoneclient/commit/eeefb784f24c37d5f56a421e1ccc911cace9385e', 'http://rhn.redhat.com/errata/RHSA-2013-0992.html', 'https://bugzilla.suse.com/show_bug.cgi?id=CVE-2013-2166', 'https://access.redhat.com/security/cve/cve-2013-2166', 'https://github.com/advisories/GHSA-c3xq-cj8f-7829', 'https://security-tracker.debian.org/tracker/CVE-2013-2166'} | null | {'https://github.com/openstack/python-keystoneclient/commit/eeefb784f24c37d5f56a421e1ccc911cace9385e'} | {'https://github.com/openstack/python-keystoneclient/commit/eeefb784f24c37d5f56a421e1ccc911cace9385e'} |
GHSA | GHSA-55r9-7mf8-m382 | Cross-site Scripting in edge.js | Edge is a logical and batteries included template engine for Node.js. This affects the package edge.js before 5.3.2. A type confusion vulnerability can be used to bypass input sanitization when the input to be rendered is an array (instead of a string or a SafeValue), even if {{ }} are used. | {'CVE-2021-23443'} | 2022-05-05T13:50:00Z | 2021-09-22T20:36:46Z | MODERATE | 5.4 | {'CWE-79', 'CWE-843'} | {'https://github.com/advisories/GHSA-55r9-7mf8-m382', 'https://snyk.io/vuln/SNYK-JS-EDGEJS-1579556', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23443', 'https://github.com/edge-js/edge/commit/fa2c7fde86327aeae232752e89a6e37e2e469e21'} | null | {'https://github.com/edge-js/edge/commit/fa2c7fde86327aeae232752e89a6e37e2e469e21'} | {'https://github.com/edge-js/edge/commit/fa2c7fde86327aeae232752e89a6e37e2e469e21'} |
GHSA | GHSA-8w94-cf6g-c8mg | Man-in-the-Middle (MitM) | Docker before 1.3.1 and docker-py before 0.5.3 fall back to HTTP when the HTTPS connection to the registry fails, which allows man-in-the-middle attackers to conduct downgrade attacks and obtain authentication and image data by leveraging a network position between the client and the registry to block HTTPS traffic. | {'CVE-2014-5277'} | 2022-04-12T22:53:42Z | 2022-02-15T01:57:18Z | MODERATE | 5.3 | null | {'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-5277', 'https://github.com/advisories/GHSA-8w94-cf6g-c8mg', 'https://github.com/docker/docker/commit/8caacb18f8019dfda30d79c327397e5f5783c068', 'https://groups.google.com/forum/#!topic/docker-user/oYm0i3xShJU', 'https://nvd.nist.gov/vuln/detail/CVE-2014-5277', 'http://lists.opensuse.org/opensuse-updates/2014-11/msg00048.html', 'https://groups.google.com/forum/#%21topic/docker-user/oYm0i3xShJU'} | null | {'https://github.com/docker/docker/commit/8caacb18f8019dfda30d79c327397e5f5783c068'} | {'https://github.com/docker/docker/commit/8caacb18f8019dfda30d79c327397e5f5783c068'} |
GHSA | GHSA-rv6r-3f5q-9rgx | Twisted SSH client and server deny of service during SSH handshake. | ### Impact
The Twisted SSH client and server implementation naively accepted an infinite amount of data for the peer's SSH version identifier.
A malicious peer can trivially craft a request that uses all available memory and crash the server, resulting in denial of service. The attack is as simple as `nc -rv localhost 22 < /dev/zero`.
### Patches
The issue was fix in GitHub commit https://github.com/twisted/twisted/commit/98387b39e9f0b21462f6abc7a1325dc370fcdeb1
A fix is available in Twisted 22.2.0.
### Workarounds
* Limit access to the SSH server only to trusted source IP addresses.
* Connect over SSH only to trusted destination IP addresses.
### References
Reported at https://twistedmatrix.com/trac/ticket/10284
Discussions at https://github.com/twisted/twisted/security/advisories/GHSA-rv6r-3f5q-9rgx
### For more information
Found by vin01 | {'CVE-2022-21716'} | 2022-04-22T15:33:58Z | 2022-03-03T19:02:08Z | HIGH | 7.5 | {'CWE-120'} | {'https://github.com/twisted/twisted/commit/98387b39e9f0b21462f6abc7a1325dc370fcdeb1', 'https://github.com/twisted/twisted/releases/tag/twisted-22.2.0', 'https://github.com/twisted/twisted/security/advisories/GHSA-rv6r-3f5q-9rgx', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21716', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://lists.debian.org/debian-lts-announce/2022/03/msg00009.html', 'https://github.com/advisories/GHSA-rv6r-3f5q-9rgx', 'https://github.com/twisted/twisted/commit/89c395ee794e85a9657b112c4351417850330ef9', 'https://twistedmatrix.com/trac/ticket/10284'} | null | {'https://github.com/twisted/twisted/commit/89c395ee794e85a9657b112c4351417850330ef9', 'https://github.com/twisted/twisted/commit/98387b39e9f0b21462f6abc7a1325dc370fcdeb1'} | {'https://github.com/twisted/twisted/commit/98387b39e9f0b21462f6abc7a1325dc370fcdeb1', 'https://github.com/twisted/twisted/commit/89c395ee794e85a9657b112c4351417850330ef9'} |
GHSA | GHSA-g8rg-7rpr-cwr2 | Information Disclosure in TYPO3 extension sf_event_mgt | A missing access check in the backend module allows an authenticated backend user to export participant data for events which the user does not have access to, resulting in Information Disclosure.
Another missing access check in the backend module allows an authenticated backend user to send emails to event participants for events which the user does not have access to, resulting in Broken Access Control.
External reference: [https://typo3.org/security/advisory/typo3-ext-sa-2020-017](https://typo3.org/security/advisory/typo3-ext-sa-2020-017) | {'CVE-2020-25026'} | 2022-04-19T19:02:33Z | 2020-09-02T18:03:26Z | MODERATE | 4.3 | {'CWE-863'} | {'https://github.com/advisories/GHSA-g8rg-7rpr-cwr2', 'https://github.com/derhansen/sf_event_mgt/security/advisories/GHSA-g8rg-7rpr-cwr2', 'https://packagist.org/packages/derhansen/sf_event_mgt', 'https://nvd.nist.gov/vuln/detail/CVE-2020-25026', 'https://github.com/derhansen/sf_event_mgt/commit/17edcbf608b252cc1123e1279f0735f6aa28fef4', 'https://typo3.org/help/security-advisories', 'https://typo3.org/security/advisory/typo3-ext-sa-2020-017'} | null | {'https://github.com/derhansen/sf_event_mgt/commit/17edcbf608b252cc1123e1279f0735f6aa28fef4'} | {'https://github.com/derhansen/sf_event_mgt/commit/17edcbf608b252cc1123e1279f0735f6aa28fef4'} |
GHSA | GHSA-9vpm-rcf4-9wqw | Division by 0 in `MaxPoolGradWithArgmax` | ### Impact
The implementation of `tf.raw_ops.MaxPoolGradWithArgmax` is vulnerable to a division by 0:
```python
import tensorflow as tf
input = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)
grad = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)
argmax = tf.constant([], shape=[0], dtype=tf.int64)
ksize = [1, 1, 1, 1]
strides = [1, 1, 1, 1]
tf.raw_ops.MaxPoolGradWithArgmax(
input=input, grad=grad, argmax=argmax, ksize=ksize, strides=strides,
padding='SAME', include_batch_in_index=False)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/279bab6efa22752a2827621b7edb56a730233bd8/tensorflow/core/kernels/maxpooling_op.cc#L1033-L1034) fails to validate that the batch dimension of the tensor is non-zero, before dividing by this quantity.
### Patches
We have patched the issue in GitHub commit [376c352a37ce5a68b721406dc7e77ac4b6cf483d](https://github.com/tensorflow/tensorflow/commit/376c352a37ce5a68b721406dc7e77ac4b6cf483d).
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-29573'} | 2021-05-21T14:26:07Z | 2021-05-21T14:26:07Z | LOW | 2.5 | {'CWE-369'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9vpm-rcf4-9wqw', 'https://github.com/advisories/GHSA-9vpm-rcf4-9wqw', 'https://github.com/tensorflow/tensorflow/commit/376c352a37ce5a68b721406dc7e77ac4b6cf483d', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29573'} | null | {'https://github.com/tensorflow/tensorflow/commit/376c352a37ce5a68b721406dc7e77ac4b6cf483d'} | {'https://github.com/tensorflow/tensorflow/commit/376c352a37ce5a68b721406dc7e77ac4b6cf483d'} |
GHSA | GHSA-8jxj-9r5f-w3m2 | Low severity vulnerability that affects puppet | lib/puppet/defaults.rb in Puppet 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, uses 0644 permissions for last_run_report.yaml, which allows local users to obtain sensitive configuration information by leveraging access to the puppet master server to read this file. | {'CVE-2012-3866'} | 2021-09-07T19:48:46Z | 2017-10-24T18:33:37Z | LOW | 0 | null | {'http://www.debian.org/security/2012/dsa-2511', 'https://nvd.nist.gov/vuln/detail/CVE-2012-3866', 'http://www.ubuntu.com/usn/USN-1506-1', 'https://github.com/advisories/GHSA-8jxj-9r5f-w3m2', 'https://bugzilla.redhat.com/show_bug.cgi?id=839135', 'https://github.com/puppetlabs/puppet/commit/fd44bf5e6d0d360f6a493d663b653c121fa83c3f', 'http://secunia.com/advisories/50014', 'http://lists.opensuse.org/opensuse-updates/2012-07/msg00036.html', 'http://puppetlabs.com/security/cve/cve-2012-3866/'} | null | {'https://github.com/puppetlabs/puppet/commit/fd44bf5e6d0d360f6a493d663b653c121fa83c3f'} | {'https://github.com/puppetlabs/puppet/commit/fd44bf5e6d0d360f6a493d663b653c121fa83c3f'} |
GHSA | GHSA-874w-m2v2-mj64 | Double Free in Adplug | AdPlug 2.3.1 has a double free in the Cu6mPlayer class in u6m.h. | {'CVE-2019-15151'} | 2021-03-29T20:48:45Z | 2021-03-29T20:48:45Z | CRITICAL | 9.8 | {'CWE-415'} | {'https://github.com/miller-alex/adplug/commit/8abb9328bf27dcbdafc67ade3e75af0ffd8f7633', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/U3PW6PLDTPSQQRHKTU2FB72SUB4Q66NE/', 'https://github.com/adplug/adplug/commit/1a282a486a8e33fef3e15998bf6408d3515dc07e', 'https://github.com/adplug/adplug/issues/91', 'https://github.com/advisories/GHSA-874w-m2v2-mj64', 'https://nvd.nist.gov/vuln/detail/CVE-2019-15151', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Q32A64R2APAC5PXIMSYIEFDQX5AD4GAS/'} | null | {'https://github.com/miller-alex/adplug/commit/8abb9328bf27dcbdafc67ade3e75af0ffd8f7633', 'https://github.com/adplug/adplug/commit/1a282a486a8e33fef3e15998bf6408d3515dc07e'} | {'https://github.com/miller-alex/adplug/commit/8abb9328bf27dcbdafc67ade3e75af0ffd8f7633', 'https://github.com/adplug/adplug/commit/1a282a486a8e33fef3e15998bf6408d3515dc07e'} |
GHSA | GHSA-5mj6-3cmq-fh34 | showdoc is vulnerable to Generation of Error Message Containing Sensitive Information | showdoc is vulnerable to Generation of Error Message Containing Sensitive Information | {'CVE-2022-0079'} | 2022-01-06T22:22:46Z | 2022-01-06T22:22:46Z | MODERATE | 5.3 | {'CWE-209'} | {'https://github.com/advisories/GHSA-5mj6-3cmq-fh34', 'https://huntr.dev/bounties/b37f0e26-355a-4d50-8495-a567c10828ee', 'https://github.com/star7th/showdoc/commit/e43df0a190f68aefa272507d3bd54475f566c1db', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0079'} | null | {'https://github.com/star7th/showdoc/commit/e43df0a190f68aefa272507d3bd54475f566c1db'} | {'https://github.com/star7th/showdoc/commit/e43df0a190f68aefa272507d3bd54475f566c1db'} |
GHSA | GHSA-v84g-cf5j-xjqx | Path Traversal in Apache James Server | Apache James Server prior to version 3.6.2 contains a path traversal vulnerability. The fix for CVE-2021-40525 does not prepend delimiters upon valid directory validations. Affected implementations include: - maildir mailbox store - Sieve file repository This enables a user to access other users data stores (limited to user names being prefixed by the value of the username being used). | {'CVE-2022-22931'} | 2022-02-10T22:46:45Z | 2022-02-08T00:00:34Z | MODERATE | 0 | {'CWE-22'} | {'https://github.com/advisories/GHSA-v84g-cf5j-xjqx', 'https://github.com/apache/james-project/pull/877/commits/b1e891a9e5eeadfa1d779ae50f21c73efe4d2fc7', 'https://lists.apache.org/thread/bp8yql4wws56jlh0vxoowj7foothsmpr', 'https://nvd.nist.gov/vuln/detail/CVE-2022-22931', 'https://github.com/apache/james-project/pull/877', 'https://www.openwall.com/lists/oss-security/2022/02/07/1'} | null | {'https://github.com/apache/james-project/pull/877/commits/b1e891a9e5eeadfa1d779ae50f21c73efe4d2fc7'} | {'https://github.com/apache/james-project/pull/877/commits/b1e891a9e5eeadfa1d779ae50f21c73efe4d2fc7'} |
GHSA | GHSA-g5rr-p69h-7v3g | Insufficient type validation in pocketmine/pocketmine-mp | When an inventory interaction is performed (e.g. moving an item around an inventory), the client sends a serialized version of the itemstack to the server, which the server then deserializes and compares against its own copy. If the copies don't match, the transaction is invalid. This involves deserializing item NBT from the client, which allows for bogus data to be provided. Usually, this is harmless, but in this particular case, it could result in crashes on certain types of bad data (e.g. incorrect ListTag type provided for the `CanDestroy` tag). This is fixed in 4.2.9 by commit 5a98b08ee8dc8ff14862cd83d2e4af9d212fefc2. It's non-trivial to workaround this, but can be done by handling `InventoryTransactionPacket` and `PlayerAuthInputPacket` to scrub inbound transaction data of bogus NBT that would cause these crashes.
| null | 2022-04-26T20:57:10Z | 2022-04-22T20:57:12Z | HIGH | 7.5 | {'CWE-20', 'CWE-1287'} | {'https://github.com/pmmp/PocketMine-MP/commit/5a98b08ee8dc8ff14862cd83d2e4af9d212fefc2', 'https://github.com/pmmp/PocketMine-MP/security/advisories/GHSA-g5rr-p69h-7v3g', 'https://github.com/pmmp/PocketMine-MP/releases/tag/4.2.9', 'https://github.com/pmmp/PocketMine-MP/blob/4.2.9/changelogs/4.2.md#429', 'https://github.com/advisories/GHSA-g5rr-p69h-7v3g'} | null | {'https://github.com/pmmp/PocketMine-MP/commit/5a98b08ee8dc8ff14862cd83d2e4af9d212fefc2'} | {'https://github.com/pmmp/PocketMine-MP/commit/5a98b08ee8dc8ff14862cd83d2e4af9d212fefc2'} |
GHSA | GHSA-f2c5-997w-7f5c | Cross-site Scripting in peertube | peertube is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). It was found that one could upload a SVG image and then send the url of that to other users and when they open the link we can get their complete session keys as the session keys stored in local storage and with Javascript easily can be stolen by attackers. | {'CVE-2021-3780'} | 2021-09-24T13:07:20Z | 2021-09-20T20:42:41Z | MODERATE | 6.1 | {'CWE-79'} | {'https://huntr.dev/bounties/282807a8-4bf5-4fe2-af62-e05f945b3d65', 'https://github.com/advisories/GHSA-f2c5-997w-7f5c', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3780', 'https://github.com/chocobozzz/peertube/commit/0ea2f79d45b301fcd660efc894469a99b2239bf6'} | null | {'https://github.com/chocobozzz/peertube/commit/0ea2f79d45b301fcd660efc894469a99b2239bf6'} | {'https://github.com/chocobozzz/peertube/commit/0ea2f79d45b301fcd660efc894469a99b2239bf6'} |
GHSA | GHSA-h6xx-pmxh-3wgp | Improper Authentication in etcd | etcd versions 3.2.x before 3.2.26 and 3.3.x before 3.3.11 are vulnerable to an improper authentication issue when role-based access control (RBAC) is used and client-cert-auth is enabled. If an etcd client server TLS certificate contains a Common Name (CN) which matches a valid RBAC username, a remote attacker may authenticate as that user with any valid (trusted) client certificate in a REST API request to the gRPC-gateway. | {'CVE-2018-16886'} | 2022-04-12T22:41:39Z | 2022-02-15T01:57:18Z | HIGH | 8.1 | {'CWE-287', 'CWE-285'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JX7QTIT465BQGRGNCE74RATRQLKT2QE4/', 'https://github.com/etcd-io/etcd/commit/0191509637546621d6f2e18e074e955ab8ef374d', 'https://nvd.nist.gov/vuln/detail/CVE-2018-16886', 'https://github.com/etcd-io/etcd/pull/10366', 'http://www.securityfocus.com/bid/106540', 'https://github.com/advisories/GHSA-h6xx-pmxh-3wgp', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16886', 'https://github.com/etcd-io/etcd/blob/1eee465a43720d713bb69f7b7f5e120135fdb1ac/CHANGELOG-3.3.md#security-authentication', 'https://github.com/etcd-io/etcd/blob/1eee465a43720d713bb69f7b7f5e120135fdb1ac/CHANGELOG-3.2.md#security-authentication', 'https://access.redhat.com/errata/RHSA-2019:0237', 'https://github.com/etcd-io/etcd/commit/bf9d0d8291dc71ecbfb2690612954e1a298154b2', 'https://access.redhat.com/errata/RHSA-2019:1352', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UPGYHMSKDPW5GAMI7BEP3XQRVRLLBJKS/'} | null | {'https://github.com/etcd-io/etcd/commit/0191509637546621d6f2e18e074e955ab8ef374d', 'https://github.com/etcd-io/etcd/commit/bf9d0d8291dc71ecbfb2690612954e1a298154b2'} | {'https://github.com/etcd-io/etcd/commit/0191509637546621d6f2e18e074e955ab8ef374d', 'https://github.com/etcd-io/etcd/commit/bf9d0d8291dc71ecbfb2690612954e1a298154b2'} |
GHSA | GHSA-h9q8-5gv2-v6mg | Potential Session Hijacking | ### Impact
Potential session hijacking of store customers.
### Patches
We recommend to update to the current version 6.3.5.2. You can get the update to 6.3.5.2 regularly via the Auto-Updater or directly via the download overview.
https://www.shopware.com/en/download/#shopware-6
### Workarounds
For older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.
https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659
### For more information
https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-03-2021 | null | 2021-03-12T23:09:08Z | 2021-03-12T23:09:08Z | LOW | 0 | {'CWE-613'} | {'https://github.com/shopware/platform/security/advisories/GHSA-h9q8-5gv2-v6mg', 'https://github.com/advisories/GHSA-h9q8-5gv2-v6mg', 'https://github.com/shopware/platform/commit/010c0154bea57c1fca73277c7431d029db7a972e', 'https://packagist.org/packages/shopware/platform'} | null | {'https://github.com/shopware/platform/commit/010c0154bea57c1fca73277c7431d029db7a972e'} | {'https://github.com/shopware/platform/commit/010c0154bea57c1fca73277c7431d029db7a972e'} |
GHSA | GHSA-m22m-h4rf-pwq3 | Path Traversal in SharpZipLib | SharpZipLib (or #ziplib) is a Zip, GZip, Tar and BZip2 library. Prior to version 1.3.3, a TAR file entry `../evil.txt` may be extracted in the parent directory of `destFolder`. This leads to arbitrary file write that may lead to code execution. The vulnerability was patched in version 1.3.3. | {'CVE-2021-32840'} | 2022-02-08T19:45:31Z | 2022-02-01T16:22:50Z | HIGH | 7.3 | {'CWE-22'} | {'https://securitylab.github.com/advisories/GHSL-2021-125-sharpziplib/', 'https://github.com/icsharpcode/SharpZipLib/releases/tag/v1.3.3', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32840', 'https://github.com/advisories/GHSA-m22m-h4rf-pwq3', 'https://github.com/icsharpcode/SharpZipLib/commit/a0e96de70b5264f4c919b09253b1522bc7a221cc'} | null | {'https://github.com/icsharpcode/SharpZipLib/commit/a0e96de70b5264f4c919b09253b1522bc7a221cc'} | {'https://github.com/icsharpcode/SharpZipLib/commit/a0e96de70b5264f4c919b09253b1522bc7a221cc'} |
GHSA | GHSA-4gp3-p7ph-x2jr | OS Command Injection in devcert-sanscache | devcert-sanscache before 0.4.7 allows remote attackers to execute arbitrary code or cause a Command Injection via the exec function. The variable `commonName` controlled by user input is used as part of the `exec` function without any sanitization. | {'CVE-2019-10778'} | 2021-08-23T15:12:52Z | 2020-04-14T23:09:00Z | CRITICAL | 9.8 | {'CWE-78'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-10778', 'https://github.com/guybedford/devcert/commit/571f4e6d077f7f21c6aed655ae380d85a7a5d3b8', 'https://snyk.io/vuln/SNYK-JS-DEVCERTSANSCACHE-540926', 'https://github.com/advisories/GHSA-4gp3-p7ph-x2jr'} | null | {'https://github.com/guybedford/devcert/commit/571f4e6d077f7f21c6aed655ae380d85a7a5d3b8'} | {'https://github.com/guybedford/devcert/commit/571f4e6d077f7f21c6aed655ae380d85a7a5d3b8'} |
GHSA | GHSA-33wf-4crm-2322 | Improper Access Control in librenms | Improper Access Control in Packagist librenms/librenms prior to 22.2.0. | {'CVE-2022-0580'} | 2022-02-24T12:12:44Z | 2022-02-16T00:01:58Z | HIGH | 7.1 | {'CWE-284'} | {'https://github.com/advisories/GHSA-33wf-4crm-2322', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0580', 'https://github.com/librenms/librenms/commit/95970af78e4c899744a715766d744deef8c505f7', 'https://notes.netbytesec.com/2022/02/multiple-vulnerabilities-in-librenms.html', 'https://huntr.dev/bounties/2494106c-7703-4558-bb1f-1eae59d264e3'} | null | {'https://github.com/librenms/librenms/commit/95970af78e4c899744a715766d744deef8c505f7'} | {'https://github.com/librenms/librenms/commit/95970af78e4c899744a715766d744deef8c505f7'} |
GHSA | GHSA-3mpr-hq3p-49h9 | Prototype Pollution in mixin-deep | Versions of `mixin-deep` before 1.3.1 are vulnerable to prototype pollution via merging functions.
## Recommendation
Update to version 1.3.1 or later. | {'CVE-2018-3719'} | 2021-01-08T20:00:26Z | 2018-07-26T15:10:54Z | LOW | 0 | {'CWE-471'} | {'https://hackerone.com/reports/311236', 'https://www.npmjs.com/advisories/578', 'https://github.com/jonschlinkert/mixin-deep/commit/578b0bc5e74e14de9ef4975f504dc698796bdf9c', 'https://github.com/advisories/GHSA-3mpr-hq3p-49h9', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3719'} | null | {'https://github.com/jonschlinkert/mixin-deep/commit/578b0bc5e74e14de9ef4975f504dc698796bdf9c'} | {'https://github.com/jonschlinkert/mixin-deep/commit/578b0bc5e74e14de9ef4975f504dc698796bdf9c'} |
GHSA | GHSA-wph3-44rj-92pr | Multiple vulnerabilities leading to RCE | ### Impact
We recently fixed several vulnerabilities affect elFinder 2.1.58. These vulnerabilities can allow an attacker to execute arbitrary code and commands on the server hosting the elFinder PHP connector, even with the minimal configuration.
### Patches
The issues were addressed in our last release, 2.1.59.
### Workarounds
If you can't update to 2.1.59, make sure your connector is not exposed without authentication.
### Reference
Further technical details will be disclosed on https://blog.sonarsource.com/tag/security after some time.
### For more information
If you have any questions or comments about this advisory, you can contact:
- The original reporters, by sending an email to vulnerability.research@sonarsource.com;
- The maintainers, by opening an issue on this repository. | {'CVE-2021-32682'} | 2022-04-19T19:02:59Z | 2021-06-16T17:04:29Z | CRITICAL | 9.8 | {'CWE-918', 'CWE-22', 'CWE-78'} | {'https://github.com/advisories/GHSA-wph3-44rj-92pr', 'https://github.com/Studio-42/elFinder/security/advisories/GHSA-wph3-44rj-92pr', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32682', 'http://packetstormsecurity.com/files/164173/elFinder-Archive-Command-Injection.html', 'https://github.com/Studio-42/elFinder/security/advisories/GHSA-qm58-cvvm-c5qr', 'https://github.com/Studio-42/elFinder/commit/a106c350b7dfe666a81d6b576816db9fe0899b17'} | null | {'https://github.com/Studio-42/elFinder/commit/a106c350b7dfe666a81d6b576816db9fe0899b17'} | {'https://github.com/Studio-42/elFinder/commit/a106c350b7dfe666a81d6b576816db9fe0899b17'} |
GHSA | GHSA-636j-7x7r-gvw2 | Old sessions not blocked by login enable function in Snipe-IT | Snipe-IT is a FOSS project for asset management in IT Operations. In Snipe-IT versions 5.4.1 and 6.0.0-RC-5 and prior, active sessions are not revoked when a user account is disabled, allowing that user to still access information that they should no longer be able to. Workarounds include using the KillAllSessions console command, clearing the contents of the storage/framework/sessions directory, or changing the cookie name, but all of those options logout ALL users, which could be kind of annoying. This issue is fixed in versions 6.0.0-RC-6 and 5.4.2. | {'CVE-2022-1155'} | 2022-04-13T13:28:22Z | 2022-03-31T00:00:22Z | HIGH | 7.4 | {'CWE-613'} | {'https://github.com/snipe/snipe-it/releases/tag/v5.4.2', 'https://github.com/snipe/snipe-it/pull/10876', 'https://huntr.dev/bounties/ebc26354-2414-4f72-88aa-f044aec2b2e1', 'https://github.com/snipe/snipe-it/releases/tag/v6.0.0-RC-6', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1155', 'https://github.com/advisories/GHSA-636j-7x7r-gvw2', 'https://github.com/snipe/snipe-it/commit/bdabbbd4e98e88ee01e728ceb4fd512661fbd38d'} | null | {'https://github.com/snipe/snipe-it/commit/bdabbbd4e98e88ee01e728ceb4fd512661fbd38d'} | {'https://github.com/snipe/snipe-it/commit/bdabbbd4e98e88ee01e728ceb4fd512661fbd38d'} |
GHSA | GHSA-5pv8-ppvj-4h68 | Prevent user enumeration using Guard or the new Authenticator-based Security | Description
-----------
The ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.
Resolution
----------
We now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.
The patch for this issue is available [here](https://github.com/symfony/symfony/commit/2a581d22cc621b33d5464ed65c4bc2057f72f011) for branch 3.4.
Credits
-------
I would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue. | {'CVE-2021-21424'} | 2022-04-19T19:02:57Z | 2021-05-13T20:23:02Z | MODERATE | 5.3 | {'CWE-200'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VRUS2H2SSOQWNLBD35SKIWIDQEMV2PD3/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KENRNLB3FYXYGDWRBH2PDBOZZKOD7VY4/', 'https://github.com/advisories/GHSA-5pv8-ppvj-4h68', 'https://github.com/symfony/symfony/commit/2a581d22cc621b33d5464ed65c4bc2057f72f011', 'https://github.com/symfony/symfony/security/advisories/GHSA-5pv8-ppvj-4h68', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21424', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RH7TMM5CHQYBFFGXWRPJDPB3SKCZXI2M/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UC7BND775DVZDQT3RMGD2HVB2PKLJDJW/'} | null | {'https://github.com/symfony/symfony/commit/2a581d22cc621b33d5464ed65c4bc2057f72f011'} | {'https://github.com/symfony/symfony/commit/2a581d22cc621b33d5464ed65c4bc2057f72f011'} |
GHSA | GHSA-83rx-c8cr-6j8q | Insecure Default Configuration in tesseract.js | Versions of `tesseract.js` prior to 1.0.19 default to using a third-party proxy. Requests may be proxied through `crossorigin.me` which clearly states is not suitable for production use. This may lead to instability and privacy violations.
## Recommendation
Upgrade to version 1.0.19 or later. | null | 2021-08-04T21:33:59Z | 2019-06-05T20:48:55Z | MODERATE | 5.9 | {'CWE-829'} | {'https://github.com/naptha/tesseract.js/pull/267', 'https://www.npmjs.com/advisories/792', 'https://github.com/advisories/GHSA-83rx-c8cr-6j8q', 'https://snyk.io/vuln/SNYK-JS-TESSERACTJS-174085', 'https://github.com/naptha/tesseract.js/commit/679eba055f2a4271558e86beec3d1b70cae3fb28'} | null | {'https://github.com/naptha/tesseract.js/commit/679eba055f2a4271558e86beec3d1b70cae3fb28'} | {'https://github.com/naptha/tesseract.js/commit/679eba055f2a4271558e86beec3d1b70cae3fb28'} |
GHSA | GHSA-27j5-4p9v-pp67 | `std::abort` raised from `TensorListReserve` | ### Impact
Providing a negative element to `num_elements` list argument of `tf.raw_ops.TensorListReserve` causes the runtime to abort the process due to reallocating a `std::vector` to have a negative number of elements:
```python
import tensorflow as tf
tf.raw_ops.TensorListReserve(
element_shape = tf.constant([1]),
num_elements=tf.constant([-1]),
element_dtype = tf.int32)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/list_kernels.cc#L312) calls `std::vector.resize()` with the new size controlled by input given by the user, without checking that this input is valid.
### Patches
We have patched the issue in GitHub commit [8a6e874437670045e6c7dc6154c7412b4a2135e2](https://github.com/tensorflow/tensorflow/commit/8a6e874437670045e6c7dc6154c7412b4a2135e2).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit 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 members of the Aivul Team from Qihoo 360. | {'CVE-2021-37644'} | 2021-08-25T14:43:40Z | 2021-08-25T14:43:40Z | MODERATE | 5.5 | {'CWE-617'} | {'https://github.com/tensorflow/tensorflow/commit/8a6e874437670045e6c7dc6154c7412b4a2135e2', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-27j5-4p9v-pp67', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37644', 'https://github.com/advisories/GHSA-27j5-4p9v-pp67'} | null | {'https://github.com/tensorflow/tensorflow/commit/8a6e874437670045e6c7dc6154c7412b4a2135e2'} | {'https://github.com/tensorflow/tensorflow/commit/8a6e874437670045e6c7dc6154c7412b4a2135e2'} |
GHSA | GHSA-37cf-r3w2-gjfw | django-nopassword stores secrets in cleartext | django-nopassword before 5.0.0 stores cleartext secrets in the database. | {'CVE-2019-10682'} | 2021-07-28T21:27:01Z | 2020-06-05T16:09:19Z | HIGH | 7.5 | {'CWE-312', 'CWE-522'} | {'https://github.com/relekang/django-nopassword/commit/d8b4615f5fbfe3997d96cf4cb3e342406396193c', 'https://github.com/advisories/GHSA-37cf-r3w2-gjfw', 'https://github.com/relekang/django-nopassword/compare/v4.0.1...v5.0.0', 'https://github.com/relekang/django-nopassword/blob/8e8cfc765ee00adfed120c2c79bf71ef856e9022/nopassword/models.py#L14', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10682'} | null | {'https://github.com/relekang/django-nopassword/commit/d8b4615f5fbfe3997d96cf4cb3e342406396193c'} | {'https://github.com/relekang/django-nopassword/commit/d8b4615f5fbfe3997d96cf4cb3e342406396193c'} |
GHSA | GHSA-pfj7-w373-gqch | Cross-Site Request Forgery in firefly-iii | firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF). | {'CVE-2021-3900'} | 2021-10-29T13:49:08Z | 2021-10-28T23:14:21Z | MODERATE | 6.5 | {'CWE-352'} | {'https://huntr.dev/bounties/909e55b6-ef02-4143-92e4-bc3e8397db76', 'https://github.com/advisories/GHSA-pfj7-w373-gqch', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3900', 'https://github.com/firefly-iii/firefly-iii/commit/c2c8c42ef3194d1aeba8c48240fe2e9063f77635'} | null | {'https://github.com/firefly-iii/firefly-iii/commit/c2c8c42ef3194d1aeba8c48240fe2e9063f77635'} | {'https://github.com/firefly-iii/firefly-iii/commit/c2c8c42ef3194d1aeba8c48240fe2e9063f77635'} |
GHSA | GHSA-c27r-x354-4m68 | HMAC-SHA1 signatures can bypass validation via key confusion | ### Impact
An attacker can inject an HMAC-SHA1 signature that is valid using only knowledge of the RSA public key. This allows bypassing signature validation.
### Patches
Version 2.0.0 has the fix.
### Workarounds
The recommendation is to upgrade. In case that is not possible remove the 'http://www.w3.org/2000/09/xmldsig#hmac-sha1' entry from SignedXml.SignatureAlgorithms. | null | 2022-04-19T19:02:39Z | 2020-10-27T20:39:46Z | HIGH | 0 | {'CWE-287'} | {'https://www.npmjs.com/package/xml-crypto', 'https://github.com/yaronn/xml-crypto/security/advisories/GHSA-c27r-x354-4m68', 'https://github.com/yaronn/xml-crypto/commit/3d9db712e6232c765cd2ad6bd2902b88a0d22100', 'https://github.com/advisories/GHSA-c27r-x354-4m68'} | null | {'https://github.com/yaronn/xml-crypto/commit/3d9db712e6232c765cd2ad6bd2902b88a0d22100'} | {'https://github.com/yaronn/xml-crypto/commit/3d9db712e6232c765cd2ad6bd2902b88a0d22100'} |
GHSA | GHSA-x92h-wmg2-6hp7 | Invalid HTTP method overrides allow possible XSS or other attacks in Symfony | In Symfony before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, HTTP Methods provided as verbs or using the override header may be treated as trusted input, but they are not validated, possibly causing SQL injection or XSS. This is related to symfony/http-foundation. | {'CVE-2019-10913'} | 2021-08-19T15:18:28Z | 2019-12-02T18:10:24Z | CRITICAL | 9.8 | {'CWE-89', 'CWE-79'} | {'https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/http-foundation/CVE-2019-10913.yaml', 'https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2019-10913.yaml', 'https://symfony.com/blog/cve-2019-10913-reject-invalid-http-method-overrides', 'https://symfony.com/cve-2019-10913', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10913', 'https://github.com/symfony/symfony/commit/944e60f083c3bffbc6a0b5112db127a10a66a8ec', 'https://github.com/advisories/GHSA-x92h-wmg2-6hp7'} | null | {'https://github.com/symfony/symfony/commit/944e60f083c3bffbc6a0b5112db127a10a66a8ec'} | {'https://github.com/symfony/symfony/commit/944e60f083c3bffbc6a0b5112db127a10a66a8ec'} |
GHSA | GHSA-2f5v-8r3f-8pww | Improper access control allows admin privilege escalation in Argo CD | ### Impact
#### Impacts for versions starting with v1.0.0
All unpatched versions of Argo CD starting with v1.0.0 are vulnerable to an improper access control bug, allowing a malicious user to potentially escalate their privileges to admin-level.
To perform the following exploits, an authorized Argo CD user must have push access to an Application's source git or Helm repository or `sync` _and_ `override` access to an Application. Once a user has that access, different exploitation levels are possible depending on their other RBAC privileges:
1. If that user has `update` access to the Application, they can modify any resource on the Application's destination cluster. If the destination cluster is or can be made to be the same as the cluster hosting Argo CD, the user can escalate their Argo CD permissions to admin-level.
2. If the user has `delete` access to the Application, they can delete any resource on the Application's destination cluster. (This exploit is possible starting with v0.8.0.)
3. If the user has `get` access to the Application, they can view any resource on the Application's destination cluster (except for the contents of Secrets) and list [actions](https://argo-cd.readthedocs.io/en/stable/operator-manual/resource_actions/) available for that resource.
4. If the user has `get` access to the Application, they can view the logs of any Pods on the Application's destination cluster.
5. If the user has `action/{some action or *}` access on the Application, they can run an action for any resource (which supports the allowed action(s)) on the Application's destination cluster. (Some actions are available in Argo CD by default, and others may be configured by an Argo CD admin.)
See the [Argo CD RBAC documentation](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#rbac-resources-and-actions) for an explanation of the privileges available in Argo CD.
##### Events exploit
A related exploit is possible for a user with `get` access to an Application **even if they do not have access to the Application's source git or Helm repository or `sync` and `override` access to the Application**. The user can access any Event in the Application's destination cluster if they know the involved object's name, UID, and namespace.
#### Impacts for versions starting with v0.8.0
The same bug exists starting with v0.8.0, but only the following exploits were possible before v1.0.0:
* The `delete` exploit (#⁠2 above).
* The logs exploit (#⁠4 above).
* The Events exploit described above.
#### Impacts for versions starting with v0.5.0
The same bug exists starting with v0.5.0 (when RBAC was implemented), but only the Events exploit described above was possible before v0.8.0.
### Patches
A patch for this vulnerability has been released in the following Argo CD versions:
* v2.3.2
* v2.2.8
* v2.1.14
**Versions 2.0.x and earlier users:** See the [changelog](https://github.com/argoproj/argo-cd/blob/master/CHANGELOG.md) for links to upgrade instructions for your version. It is imperative to upgrade quickly, but some limited mitigations are described in the next section.
**argo-helm chart users:** Argo CD users deploying v2.3.x with [argo-helm](https://github.com/argoproj/argo-helm) can upgrade the chart to version 4.2.2. Argo CD 2.2 and 2.1 users can set the `global.image.tag` value to the latest in your current release series (`v2.2.8`, or `v2.1.14`). Since charts for the 2.2 and 2.1 series are no longer maintained, you will need to either leave the value override in place or upgrade to the 4.x chart series (and therefore to Argo CD 2.3).
### Workarounds
The only certain way to avoid the vulnerability is to upgrade.
#### Mitigations
* To avoid privilege escalation:
* Limit who has push access to Application source repositories or `sync` + `override` access to Applications.
* Limit which repositories are available in [projects](https://argo-cd.readthedocs.io/en/stable/user-guide/projects/) where users have `update` access to Applications.
* To avoid unauthorized resource inspection/tampering:
* Limit who has `delete`, `get`, or `action` access to Applications.
These mitigations can help limit potential damage, but they are _not_ a substitute for upgrading. It is necessary to upgrade immediately.
### References
* [Argo CD RBAC configuration documentation](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#)
### For more information
Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions)
Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel #argo-cd
| {'CVE-2022-24768'} | 2022-04-04T20:40:45Z | 2022-03-24T00:18:54Z | CRITICAL | 9.9 | {'CWE-200', 'CWE-269'} | {'https://github.com/argoproj/argo-cd/security/advisories/GHSA-2f5v-8r3f-8pww', 'https://github.com/argoproj/argo-cd/commit/af03b291d4b7e9d3ce9a6580ae9c8141af0e05cf', 'https://github.com/advisories/GHSA-2f5v-8r3f-8pww', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24768', 'https://github.com/argoproj/argo-cd/releases/tag/v2.3.2', 'https://github.com/argoproj/argo-cd/releases/tag/v2.1.14', 'https://github.com/argoproj/argo-cd/releases/tag/v2.2.8'} | null | {'https://github.com/argoproj/argo-cd/commit/af03b291d4b7e9d3ce9a6580ae9c8141af0e05cf'} | {'https://github.com/argoproj/argo-cd/commit/af03b291d4b7e9d3ce9a6580ae9c8141af0e05cf'} |
GHSA | GHSA-27rq-4943-qcwp | Insertion of Sensitive Information into Log File in Hashicorp go-getter | The Hashicorp go-getter library before 1.5.11 could write SSH credentials into its logfile, exposing sensitive credentials to local users able to read the logfile. | {'CVE-2022-29810'} | 2022-05-03T20:19:27Z | 2022-04-28T00:00:35Z | MODERATE | 0 | {'CWE-532'} | {'https://github.com/hashicorp/go-getter/pull/348', 'https://nvd.nist.gov/vuln/detail/CVE-2022-29810', 'https://github.com/advisories/GHSA-27rq-4943-qcwp', 'https://github.com/hashicorp/go-getter/releases/tag/v1.5.11', 'https://github.com/hashicorp/go-getter/commit/36b68b2f68a3ed10ee7ecbb0cb9f6b1dc5da49cc'} | null | {'https://github.com/hashicorp/go-getter/commit/36b68b2f68a3ed10ee7ecbb0cb9f6b1dc5da49cc'} | {'https://github.com/hashicorp/go-getter/commit/36b68b2f68a3ed10ee7ecbb0cb9f6b1dc5da49cc'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.