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-rf3w-29h3-r636 | Arbitrary Code Execution in feehi/cms | An arbitrary file upload vulnerability in Feehi CMS v2.0.8 and below allows attackers to execute arbitrary code via a crafted PHP file. | {'CVE-2020-21322'} | 2021-09-29T18:02:51Z | 2021-09-20T20:45:35Z | HIGH | 0 | {'CWE-434'} | {'https://github.com/advisories/GHSA-rf3w-29h3-r636', 'https://nvd.nist.gov/vuln/detail/CVE-2020-21322', 'https://github.com/liufee/cms/commit/ecbfb0ca77874ead5b6e79b96a5e1f94e67475a9', 'https://github.com/liufee/cms/issues/44'} | null | {'https://github.com/liufee/cms/commit/ecbfb0ca77874ead5b6e79b96a5e1f94e67475a9'} | {'https://github.com/liufee/cms/commit/ecbfb0ca77874ead5b6e79b96a5e1f94e67475a9'} |
GHSA | GHSA-8v5f-hp78-jgxq | Signature Verification Bypass in jwt-simple | Versions of `jwt-simple` prior to 0.5.3 are vulnerable to Signature Verification Bypass. If no algorithm is specified in the `decode()` function, the packages uses the algorithm in the JWT to decode tokens. This allows an attacker to create a HS256 (symmetric algorithm) JWT with the server's public key as secret, and the package will verify it as HS256 instead of RS256 (asymmetric algorithm).
## Recommendation
Upgrade to version 0.5.3 or later. | null | 2021-08-04T20:57:39Z | 2019-06-06T15:30:33Z | HIGH | 0 | {'CWE-347'} | {'https://github.com/hokaccha/node-jwt-simple/commit/ead36e1d687645da9c3be8befdaaef622ea33106', 'https://www.npmjs.com/advisories/831', 'https://github.com/advisories/GHSA-8v5f-hp78-jgxq'} | null | {'https://github.com/hokaccha/node-jwt-simple/commit/ead36e1d687645da9c3be8befdaaef622ea33106'} | {'https://github.com/hokaccha/node-jwt-simple/commit/ead36e1d687645da9c3be8befdaaef622ea33106'} |
GHSA | GHSA-hhx9-p69v-cx2j | Authentication bypass in Apache Airflow | "The previous default setting for Airflow's Experimental API was to allow all API requests without authentication, but this poses security risks to users who miss this fact. From Airflow 1.10.11 the default has been changed to deny all requests by default and is documented at https://airflow.apache.org/docs/1.10.11/security.html#api-authentication. Note this change fixes it for new installs but existing users need to change their config to default `[api]auth_backend = airflow.api.auth.backend.deny_all` as mentioned in the Updating Guide: https://github.com/apache/airflow/blob/1.10.11/UPDATING.md#experimental-api-will-deny-all-request-by-default" | {'CVE-2020-13927'} | 2021-06-03T15:21:59Z | 2021-04-30T17:34:13Z | CRITICAL | 9.8 | {'CWE-287'} | {'https://github.com/advisories/GHSA-hhx9-p69v-cx2j', 'https://airflow.apache.org/docs/apache-airflow/1.10.11/security.html#api-authentication', 'http://packetstormsecurity.com/files/162908/Apache-Airflow-1.10.10-Remote-Code-Execution.html', 'https://github.com/apache/airflow/pull/9611/commits/c8053e166d45ad519c0a1cd4480e025a759c176e', 'https://nvd.nist.gov/vuln/detail/CVE-2020-13927', 'https://lists.apache.org/thread.html/r23a81b247aa346ff193670be565b2b8ea4b17ddbc7a35fc099c1aadd%40%3Cdev.airflow.apache.org%3E', 'https://github.com/apache/airflow/releases/tag/1.10.11'} | null | {'https://github.com/apache/airflow/pull/9611/commits/c8053e166d45ad519c0a1cd4480e025a759c176e'} | {'https://github.com/apache/airflow/pull/9611/commits/c8053e166d45ad519c0a1cd4480e025a759c176e'} |
GHSA | GHSA-58v3-j75h-xr49 | Improper Input Validation in libseccomp-golang | libseccomp-golang 0.9.0 and earlier incorrectly generates BPFs that OR multiple arguments rather than ANDing them. A process running under a restrictive seccomp filter that specified multiple syscall arguments could bypass intended access restrictions by specifying a single matching argument. | {'CVE-2017-18367'} | 2021-05-18T15:44:30Z | 2021-05-18T15:44:30Z | HIGH | 4.8 | {'CWE-284'} | {'https://lists.debian.org/debian-lts-announce/2020/08/msg00016.html', 'http://www.openwall.com/lists/oss-security/2019/04/25/6', 'https://access.redhat.com/errata/RHSA-2019:4090', 'https://usn.ubuntu.com/4574-1/', 'https://github.com/seccomp/libseccomp-golang/commit/06e7a29f36a34b8cf419aeb87b979ee508e58f9e', 'https://github.com/seccomp/libseccomp-golang/issues/22', 'https://github.com/advisories/GHSA-58v3-j75h-xr49', 'https://access.redhat.com/errata/RHSA-2019:4087', 'https://nvd.nist.gov/vuln/detail/CVE-2017-18367'} | null | {'https://github.com/seccomp/libseccomp-golang/commit/06e7a29f36a34b8cf419aeb87b979ee508e58f9e'} | {'https://github.com/seccomp/libseccomp-golang/commit/06e7a29f36a34b8cf419aeb87b979ee508e58f9e'} |
GHSA | GHSA-w6cx-qg2q-rvq8 | Path Traversal in @finastra/ssr-pages | A path traversal issue can occur when providing untrusted input to the `svg` property as an argument to the `build(MessagePageOptions)` function.
### References
- https://github.com/Finastra/ssr-pages/pull/1
- https://github.com/Finastra/ssr-pages/pull/1/commits/c3e4c563384ae3ba3892f37dd190218577620780
| {'CVE-2022-24718'} | 2022-04-19T19:03:25Z | 2022-03-01T22:09:18Z | HIGH | 7.6 | {'CWE-22'} | {'https://github.com/Finastra/ssr-pages/pull/1', 'https://github.com/Finastra/ssr-pages/pull/1/commits/c3e4c563384ae3ba3892f37dd190218577620780', 'https://github.com/advisories/GHSA-w6cx-qg2q-rvq8', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24718', 'https://github.com/Finastra/ssr-pages/security/advisories/GHSA-w6cx-qg2q-rvq8'} | null | {'https://github.com/Finastra/ssr-pages/pull/1/commits/c3e4c563384ae3ba3892f37dd190218577620780'} | {'https://github.com/Finastra/ssr-pages/pull/1/commits/c3e4c563384ae3ba3892f37dd190218577620780'} |
GHSA | GHSA-5r2v-6gm6-vpvh | Insecure Permissions in Gogs | routes/api/v1/api.go in Gogs 0.11.86 lacks permission checks for routes: deploy keys, collaborators, and hooks. | {'CVE-2019-14544'} | 2021-05-18T17:33:58Z | 2021-05-18T17:33:58Z | CRITICAL | 9.8 | {'CWE-200'} | {'https://github.com/advisories/GHSA-5r2v-6gm6-vpvh', 'https://github.com/gogs/gogs/issues/5764', 'https://github.com/gogs/gogs/commit/c3af3ff1d0484de3bd789ee6c6e47f35d590e945', 'https://nvd.nist.gov/vuln/detail/CVE-2019-14544'} | null | {'https://github.com/gogs/gogs/commit/c3af3ff1d0484de3bd789ee6c6e47f35d590e945'} | {'https://github.com/gogs/gogs/commit/c3af3ff1d0484de3bd789ee6c6e47f35d590e945'} |
GHSA | GHSA-mg98-x2cm-4cpf | Out-of-bounds write | A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1062, CVE-2019-1092, CVE-2019-1103, CVE-2019-1107. | {'CVE-2019-1106'} | 2021-03-29T20:59:15Z | 2021-03-29T20:59:15Z | HIGH | 7.5 | {'CWE-787'} | {'https://github.com/chakra-core/ChakraCore/commit/75162b7f2d8ac2b37d17564e9c979ba1bae707e8', 'https://github.com/advisories/GHSA-mg98-x2cm-4cpf', 'https://github.com/chakra-core/ChakraCore/commit/362e96537af207be3ecf7fa32f338229ee1dcc46', 'https://nvd.nist.gov/vuln/detail/CVE-2019-1106', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1106'} | null | {'https://github.com/chakra-core/ChakraCore/commit/75162b7f2d8ac2b37d17564e9c979ba1bae707e8', 'https://github.com/chakra-core/ChakraCore/commit/362e96537af207be3ecf7fa32f338229ee1dcc46'} | {'https://github.com/chakra-core/ChakraCore/commit/362e96537af207be3ecf7fa32f338229ee1dcc46', 'https://github.com/chakra-core/ChakraCore/commit/75162b7f2d8ac2b37d17564e9c979ba1bae707e8'} |
GHSA | GHSA-pccm-j6vj-jwwf | Cross-site Scripting in ShowDoc | ShowDoc prior to 2.10.4 is vulnerable to stored cross-site scripting via `.webma` file upload. | {'CVE-2022-0962'} | 2022-03-29T21:17:44Z | 2022-03-15T00:00:54Z | MODERATE | 5.4 | {'CWE-79'} | {'https://huntr.dev/bounties/7ebe3e5f-2c86-44de-b83e-2ddb6bbda908', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0962', 'https://github.com/advisories/GHSA-pccm-j6vj-jwwf', 'https://github.com/star7th/showdoc/commit/3caa32334db0c277b84e993eaca2036f5d1dbef8'} | null | {'https://github.com/star7th/showdoc/commit/3caa32334db0c277b84e993eaca2036f5d1dbef8'} | {'https://github.com/star7th/showdoc/commit/3caa32334db0c277b84e993eaca2036f5d1dbef8'} |
GHSA | GHSA-pq2f-3fg3-rw99 | SQL Injection in WordPress Zero Spam WordPress plugin | The WordPress Zero Spam WordPress plugin before 5.2.13 does not properly sanitise and escape the order and orderby parameters before using them in a SQL statement in the admin dashboard, leading to a SQL injection | {'CVE-2022-0254'} | 2022-03-29T21:17:17Z | 2022-03-15T00:00:57Z | CRITICAL | 9.8 | {'CWE-89'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0254', 'https://plugins.trac.wordpress.org/changeset/2680906', 'https://plugins.trac.wordpress.org/changeset/2660225', 'https://github.com/Highfivery/zero-spam-for-wordpress/commit/49723f696f1e2f2a76ac89375910bb036a4895f3', 'https://github.com/advisories/GHSA-pq2f-3fg3-rw99', 'https://wpscan.com/vulnerability/ae54681f-7b89-408c-b0ee-ba4a520db997'} | null | {'https://github.com/Highfivery/zero-spam-for-wordpress/commit/49723f696f1e2f2a76ac89375910bb036a4895f3'} | {'https://github.com/Highfivery/zero-spam-for-wordpress/commit/49723f696f1e2f2a76ac89375910bb036a4895f3'} |
GHSA | GHSA-4p4p-www8-8fv9 | Reference binding to null in `ParameterizedTruncatedNormal` | ### Impact
An attacker can trigger undefined behavior by binding to null pointer in `tf.raw_ops.ParameterizedTruncatedNormal`:
```python
import tensorflow as tf
shape = tf.constant([], shape=[0], dtype=tf.int32)
means = tf.constant((1), dtype=tf.float32)
stdevs = tf.constant((1), dtype=tf.float32)
minvals = tf.constant((1), dtype=tf.float32)
maxvals = tf.constant((1), dtype=tf.float32)
tf.raw_ops.ParameterizedTruncatedNormal(
shape=shape, means=means, stdevs=stdevs, minvals=minvals, maxvals=maxvals)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/3f6fe4dfef6f57e768260b48166c27d148f3015f/tensorflow/core/kernels/parameterized_truncated_normal_op.cc#L630) does not validate input arguments before accessing the first element of `shape`:
```cc
int32 num_batches = shape_tensor.flat<int32>()(0);
```
If `shape` argument is empty, then `shape_tensor.flat<T>()` is an empty array.
### Patches
We have patched the issue in GitHub commit [5e52ef5a461570cfb68f3bdbbebfe972cb4e0fd8](https://github.com/tensorflow/tensorflow/commit/5e52ef5a461570cfb68f3bdbbebfe972cb4e0fd8).
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-29568'} | 2021-05-21T14:25:19Z | 2021-05-21T14:25:19Z | LOW | 2.5 | {'CWE-824'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29568', 'https://github.com/tensorflow/tensorflow/commit/5e52ef5a461570cfb68f3bdbbebfe972cb4e0fd8', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-4p4p-www8-8fv9', 'https://github.com/advisories/GHSA-4p4p-www8-8fv9'} | null | {'https://github.com/tensorflow/tensorflow/commit/5e52ef5a461570cfb68f3bdbbebfe972cb4e0fd8'} | {'https://github.com/tensorflow/tensorflow/commit/5e52ef5a461570cfb68f3bdbbebfe972cb4e0fd8'} |
GHSA | GHSA-86mr-6m89-vgj3 | Buffer Overflow in node-weakauras-parser | Affected versions of `node-weakauras-parser` are vulnerable to a Buffer Overflow. The `encode_weakaura` function fails to properly validate the input size. A buffer of 13835058055282163711 bytes causes an overflow on 64-bit systems.
## Recommendation
Upgrade to versions 1.0.5, 2.0.2, 3.0.1 or later. | null | 2021-10-04T21:10:10Z | 2020-09-03T15:51:38Z | MODERATE | 0 | {'CWE-120'} | {'https://github.com/Zireael-N/node-weakauras-parser/commit/bc146da09db689e554d28e948f1cf1c138f09f69#diff-023afe6291ac9ada88788108cb3367b3R38-R43', 'https://www.npmjs.com/advisories/1504', 'https://github.com/advisories/GHSA-86mr-6m89-vgj3'} | null | {'https://github.com/Zireael-N/node-weakauras-parser/commit/bc146da09db689e554d28e948f1cf1c138f09f69#diff-023afe6291ac9ada88788108cb3367b3R38-R43'} | {'https://github.com/Zireael-N/node-weakauras-parser/commit/bc146da09db689e554d28e948f1cf1c138f09f69#diff-023afe6291ac9ada88788108cb3367b3R38-R43'} |
GHSA | GHSA-v4cr-m5f8-gxw8 | yetiforcecrm is vulnerable to Cross-Site Request Forgery (CSRF) | yetiforcecrm is vulnerable to Cross-Site Request Forgery (CSRF). | {'CVE-2021-4092'} | 2021-12-16T14:14:56Z | 2021-12-16T14:14:56Z | MODERATE | 4.3 | {'CWE-352'} | {'https://github.com/advisories/GHSA-v4cr-m5f8-gxw8', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4092', 'https://github.com/yetiforcecompany/yetiforcecrm/commit/585da04bb72d36a894f6ea5939ab909e53fd8c23', 'https://huntr.dev/bounties/7b58c160-bb62-45fe-ad1f-38354378b89e'} | null | {'https://github.com/yetiforcecompany/yetiforcecrm/commit/585da04bb72d36a894f6ea5939ab909e53fd8c23'} | {'https://github.com/yetiforcecompany/yetiforcecrm/commit/585da04bb72d36a894f6ea5939ab909e53fd8c23'} |
GHSA | GHSA-2jhm-qp48-hv5j | Missing authorization in xwiki-platform | ### Impact
Any user with SCRIPT right (EDIT right before XWiki 7.4) can read any file located in the XWiki WAR (for example xwiki.cfg and xwiki.properties) through XWiki#invokeServletAndReturnAsString:
```
$xwiki.invokeServletAndReturnAsString("/WEB-INF/xwiki.cfg")
```
### Patches
It has been patched in XWiki versions 12.10.9, 13.4.3 and 13.7-rc-1.
### Workarounds
The only workaround is to give SCRIPT right only to trusted users.
### References
https://jira.xwiki.org/browse/XWIKI-18870
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Jira XWiki](https://jira.xwiki.org)
* Email us at [our security mailing list](mailto:security@xwiki.org) | {'CVE-2022-23621'} | 2022-02-11T15:00:23Z | 2022-02-09T21:56:05Z | MODERATE | 5.5 | {'CWE-862'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-23621', 'https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-2jhm-qp48-hv5j', 'https://jira.xwiki.org/browse/XWIKI-18870', 'https://github.com/advisories/GHSA-2jhm-qp48-hv5j', 'https://github.com/xwiki/xwiki-platform/commit/df8bd49b5a4d87a427002c6535fb5b1746ff117a'} | null | {'https://github.com/xwiki/xwiki-platform/commit/df8bd49b5a4d87a427002c6535fb5b1746ff117a'} | {'https://github.com/xwiki/xwiki-platform/commit/df8bd49b5a4d87a427002c6535fb5b1746ff117a'} |
GHSA | GHSA-2ww3-fxvq-293j | Inefficient Regular Expression in nltk | nltk is contains an Inefficient Regular Expression and is vulnerable to regular expression denial of service attacks. | {'CVE-2021-3828'} | 2022-04-26T18:03:42Z | 2021-09-29T17:14:53Z | HIGH | 7.5 | {'CWE-697', 'CWE-1333'} | {'https://github.com/nltk/nltk/pull/2816', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3828', 'https://huntr.dev/bounties/d19aed43-75bc-4a03-91a0-4d0bb516bc32', 'https://github.com/nltk/nltk/commit/277711ab1dec729e626b27aab6fa35ea5efbd7e6', 'https://github.com/advisories/GHSA-2ww3-fxvq-293j'} | null | {'https://github.com/nltk/nltk/commit/277711ab1dec729e626b27aab6fa35ea5efbd7e6'} | {'https://github.com/nltk/nltk/commit/277711ab1dec729e626b27aab6fa35ea5efbd7e6'} |
GHSA | GHSA-m8rp-q82r-c5mf | Cross-site Scripting in microweber | Cross-site Scripting (XSS) - Stored in Packagist microweber/microweber prior to 1.2.11. | {'CVE-2022-0278'} | 2022-01-27T18:31:49Z | 2022-01-21T18:06:49Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/advisories/GHSA-m8rp-q82r-c5mf', 'https://huntr.dev/bounties/64495d0f-d5ec-4542-9693-32372c18d030', 'https://github.com/microweber/microweber/commit/b64ef574b82dbf89a908e1569d790c7012d1ccd7', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0278'} | null | {'https://github.com/microweber/microweber/commit/b64ef574b82dbf89a908e1569d790c7012d1ccd7'} | {'https://github.com/microweber/microweber/commit/b64ef574b82dbf89a908e1569d790c7012d1ccd7'} |
GHSA | GHSA-282f-qqgm-c34q | Prototype Pollution in node-jsonpointer | This affects the package `jsonpointer` before `5.0.0`. A type confusion vulnerability can lead to a bypass of a previous Prototype Pollution fix when the pointer components are arrays. | {'CVE-2021-23807'} | 2021-11-08T17:44:45Z | 2021-11-08T17:44:45Z | MODERATE | 5.6 | {'CWE-843', 'CWE-1321'} | {'https://github.com/advisories/GHSA-282f-qqgm-c34q', 'https://snyk.io/vuln/SNYK-JS-JSONPOINTER-1577288', 'https://github.com/janl/node-jsonpointer/commit/a0345f3550cd9c4d89f33b126390202b89510ad4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23807', 'https://github.com/janl/node-jsonpointer/pull/51'} | null | {'https://github.com/janl/node-jsonpointer/commit/a0345f3550cd9c4d89f33b126390202b89510ad4'} | {'https://github.com/janl/node-jsonpointer/commit/a0345f3550cd9c4d89f33b126390202b89510ad4'} |
GHSA | GHSA-m34j-p8rj-wjxq | Division by 0 in `QuantizedBiasAdd` | ### Impact
An attacker can trigger an integer division by zero undefined behavior in `tf.raw_ops.QuantizedBiasAdd`:
```python
import tensorflow as tf
input_tensor = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.quint8)
bias = tf.constant([], shape=[0], dtype=tf.quint8)
min_input = tf.constant(-10.0, dtype=tf.float32)
max_input = tf.constant(-10.0, dtype=tf.float32)
min_bias = tf.constant(-10.0, dtype=tf.float32)
max_bias = tf.constant(-10.0, dtype=tf.float32)
tf.raw_ops.QuantizedBiasAdd(input=input_tensor, bias=bias, min_input=min_input,
max_input=max_input, min_bias=min_bias,
max_bias=max_bias, out_type=tf.qint32)
```
This is because the [implementation of the Eigen kernel](https://github.com/tensorflow/tensorflow/blob/61bca8bd5ba8a68b2d97435ddfafcdf2b85672cd/tensorflow/core/kernels/quantization_utils.h#L812-L849) does a division by the number of elements of the smaller input (based on shape) without checking that this is not zero:
```cc
template <typename T1, typename T2, typename T3>
void QuantizedAddUsingEigen(const Eigen::ThreadPoolDevice& device,
const Tensor& input, float input_min,
float input_max, const Tensor& smaller_input,
float smaller_input_min, float smaller_input_max,
Tensor* output, float* output_min,
float* output_max) {
...
const int64 input_element_count = input.NumElements();
const int64 smaller_input_element_count = smaller_input.NumElements();
...
bcast[0] = input_element_count / smaller_input_element_count;
...
}
```
This integral division by 0 is undefined behavior.
### Patches
We have patched the issue in GitHub commit [67784700869470d65d5f2ef20aeb5e97c31673cb](https://github.com/tensorflow/tensorflow/commit/67784700869470d65d5f2ef20aeb5e97c31673cb).
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-29546'} | 2021-05-21T14:23:28Z | 2021-05-21T14:23:28Z | LOW | 2.5 | {'CWE-369'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29546', 'https://github.com/advisories/GHSA-m34j-p8rj-wjxq', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-m34j-p8rj-wjxq', 'https://github.com/tensorflow/tensorflow/commit/67784700869470d65d5f2ef20aeb5e97c31673cb'} | null | {'https://github.com/tensorflow/tensorflow/commit/67784700869470d65d5f2ef20aeb5e97c31673cb'} | {'https://github.com/tensorflow/tensorflow/commit/67784700869470d65d5f2ef20aeb5e97c31673cb'} |
GHSA | GHSA-x3g3-jh26-76cf | Cross-site Scripting in livehelperchat | LiveHelperChat is vulnerable to Stored XSS at the Name field in the Admin themes of System configuration. | {'CVE-2022-0375'} | 2022-02-02T16:05:34Z | 2022-01-28T23:06:00Z | MODERATE | 6.5 | {'CWE-79'} | {'https://github.com/advisories/GHSA-x3g3-jh26-76cf', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0375', 'https://github.com/livehelperchat/livehelperchat/commit/bbfaa26ce54a2a86ce1a42a16496038f5bdfc102', 'https://huntr.dev/bounties/28e1c356-6eaa-4d93-af56-938e3b4d40a7'} | null | {'https://github.com/livehelperchat/livehelperchat/commit/bbfaa26ce54a2a86ce1a42a16496038f5bdfc102'} | {'https://github.com/livehelperchat/livehelperchat/commit/bbfaa26ce54a2a86ce1a42a16496038f5bdfc102'} |
GHSA | GHSA-p3rp-vmj9-gv6v | Incorrect sanitisation function leads to `XSS` in mermaid | ### Impact
Malicious diagrams can contain javascript code that can be run at diagram readers machines.
### Patches
The users should upgrade to version 8.13.8
### Workarounds
You need to upgrade in order to avoid this issue.
| {'CVE-2021-43861'} | 2022-01-06T19:45:59Z | 2022-01-06T19:45:59Z | HIGH | 7.2 | {'CWE-20', 'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-43861', 'https://github.com/mermaid-js/mermaid/security/advisories/GHSA-p3rp-vmj9-gv6v', 'https://github.com/mermaid-js/mermaid/commit/066b7a0d0bda274d94a2f2d21e4323dab5776d83', 'https://github.com/advisories/GHSA-p3rp-vmj9-gv6v', 'https://github.com/mermaid-js/mermaid/releases/tag/8.13.8'} | null | {'https://github.com/mermaid-js/mermaid/commit/066b7a0d0bda274d94a2f2d21e4323dab5776d83'} | {'https://github.com/mermaid-js/mermaid/commit/066b7a0d0bda274d94a2f2d21e4323dab5776d83'} |
GHSA | GHSA-2j9c-9vmv-7m39 | Missing anchor in Rack-Cors allows malicious third party site to perform CORS request | Missing anchor in generated regex for rack-cors before 0.4.1 allows a malicious third-party site to perform CORS requests. If the configuration were intended to allow only the trusted example.com domain name and not the malicious example.net domain name, then example.com.example.net (as well as example.com-example.net) would be inadvertently allowed. | {'CVE-2017-11173'} | 2022-04-26T18:19:30Z | 2018-07-31T18:18:39Z | HIGH | 8.8 | null | {'https://github.com/cyu/rack-cors/commit/42ebe6caa8e85ffa9c8a171bda668ba1acc7a5e6', 'https://github.com/advisories/GHSA-2j9c-9vmv-7m39', 'http://seclists.org/fulldisclosure/2017/Jul/22', 'http://www.debian.org/security/2017/dsa-3931', 'https://packetstormsecurity.com/files/143345/rack-cors-Missing-Anchor.html', 'https://nvd.nist.gov/vuln/detail/CVE-2017-11173'} | null | {'https://github.com/cyu/rack-cors/commit/42ebe6caa8e85ffa9c8a171bda668ba1acc7a5e6'} | {'https://github.com/cyu/rack-cors/commit/42ebe6caa8e85ffa9c8a171bda668ba1acc7a5e6'} |
GHSA | GHSA-fh37-cx83-q542 | Improper Authentication in Apache Airflow | The lineage endpoint of the deprecated Experimental API was not protected by authentication in Airflow 2.0.0. This allowed unauthenticated users to hit that endpoint. This is low-severity issue as the attacker needs to be aware of certain parameters to pass to that endpoint and even after can just get some metadata about a DAG and a Task. This issue only affects Apache Airflow 2.0.0. | {'CVE-2021-26697'} | 2021-06-18T18:30:11Z | 2021-06-18T18:30:11Z | MODERATE | 5.3 | {'CWE-287', 'CWE-269'} | {'https://lists.apache.org/thread.html/re21fec81baea7a6d73b0b5d31efd07cc02c61f832e297f65bb19b519@%3Cdev.airflow.apache.org%3E', 'http://www.openwall.com/lists/oss-security/2021/02/17/2', 'https://lists.apache.org/thread.html/re21fec81baea7a6d73b0b5d31efd07cc02c61f832e297f65bb19b519@%3Cusers.airflow.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2021-26697', 'https://github.com/advisories/GHSA-fh37-cx83-q542', 'https://github.com/apache/airflow/commit/21cedff205e7d62675949fda2aa4616d77232b76', 'https://lists.apache.org/thread.html/re21fec81baea7a6d73b0b5d31efd07cc02c61f832e297f65bb19b519%40%3Cusers.airflow.apache.org%3E', 'https://lists.apache.org/thread.html/r36111262a59219a3e2704c71e97cf84937dae5ba7a1da99499e5d8f9@%3Cannounce.apache.org%3E'} | null | {'https://github.com/apache/airflow/commit/21cedff205e7d62675949fda2aa4616d77232b76'} | {'https://github.com/apache/airflow/commit/21cedff205e7d62675949fda2aa4616d77232b76'} |
GHSA | GHSA-m5pj-vjjf-4m3h | Arbitrary Code Execution in grunt | The package grunt before 1.3.0 are vulnerable to Arbitrary Code Execution due to the default usage of the function load() instead of its secure replacement safeLoad() of the package js-yaml inside grunt.file.readYAML. | {'CVE-2020-7729'} | 2021-05-06T18:27:18Z | 2021-05-06T18:27:18Z | HIGH | 7.1 | {'CWE-1188'} | {'https://snyk.io/vuln/SNYK-JS-GRUNT-597546', 'https://github.com/gruntjs/grunt/blob/master/lib/grunt/file.js%23L249', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-607922', 'https://github.com/advisories/GHSA-m5pj-vjjf-4m3h', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7729', 'https://github.com/gruntjs/grunt/commit/e350cea1724eb3476464561a380fb6a64e61e4e7', 'https://usn.ubuntu.com/4595-1/', 'https://lists.debian.org/debian-lts-announce/2020/09/msg00008.html'} | null | {'https://github.com/gruntjs/grunt/commit/e350cea1724eb3476464561a380fb6a64e61e4e7'} | {'https://github.com/gruntjs/grunt/commit/e350cea1724eb3476464561a380fb6a64e61e4e7'} |
GHSA | GHSA-686f-ch3r-xwmh | Data races in unicycle | Affected versions of this crate unconditionally implemented `Send` & `Sync` for types `PinSlab<T>` & `Unordered<T, S>`. This allows sending non-Send types to other threads and concurrently accessing non-Sync types from multiple threads.
This can result in a data race & memory corruption when types that provide internal mutability without synchronization are contained within `PinSlab<T>` or `Unordered<T, S>` and accessed concurrently from multiple threads.
The flaw was corrected in commits 92f40b4 & 6a6c367 by adding trait bound `T: Send` to `Send` impls for `PinSlab<T>` & `Unordered<T, S>` and adding `T: Sync` to `Sync` impls for `PinSlab<T>` & `Unordered<T, S>`. | {'CVE-2020-36436'} | 2021-08-25T20:58:17Z | 2021-08-25T20:58:17Z | HIGH | 8.1 | {'CWE-119', 'CWE-362'} | {'https://github.com/udoprog/unicycle/commit/6a6c367a0c25f86f998fa315ea90c328f685b194', 'https://github.com/udoprog/unicycle/commit/92f40b4a2c671553dfa96feacff0265206c44ce5', 'https://rustsec.org/advisories/RUSTSEC-2020-0116.html', 'https://github.com/udoprog/unicycle/issues/8', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36436', 'https://github.com/advisories/GHSA-686f-ch3r-xwmh'} | null | {'https://github.com/udoprog/unicycle/commit/6a6c367a0c25f86f998fa315ea90c328f685b194', 'https://github.com/udoprog/unicycle/commit/92f40b4a2c671553dfa96feacff0265206c44ce5'} | {'https://github.com/udoprog/unicycle/commit/6a6c367a0c25f86f998fa315ea90c328f685b194', 'https://github.com/udoprog/unicycle/commit/92f40b4a2c671553dfa96feacff0265206c44ce5'} |
GHSA | GHSA-x64g-4xx9-fh6x | Denial of Service in Cryptacular | CiphertextHeader.java in Cryptacular before 1.2.4, as used in Apereo CAS and other products, allows attackers to trigger excessive memory allocation during a decode operation, because the nonce array length associated with "new byte" may depend on untrusted input within the header of encoded data. | {'CVE-2020-7226'} | 2022-04-22T18:19:17Z | 2020-06-10T20:02:58Z | HIGH | 7.5 | {'CWE-770'} | {'https://lists.apache.org/thread.html/r380781f5b489cb3c818536cd3b3757e806bfe0bca188591e0051ac03@%3Ccommits.ws.apache.org%3E', 'https://lists.apache.org/thread.html/r0847c7eb78c8f9e87d5b841fbd5da52b2ad4b4345e04b51c30621d88@%3Ccommits.tomee.apache.org%3E', 'https://lists.apache.org/thread.html/re04e4f8f0d095387fb6b0ff9016a0af8c93f42e1de93b09298bfa547@%3Ccommits.ws.apache.org%3E', 'https://github.com/vt-middleware/cryptacular/issues/52', 'https://github.com/apereo/cas/commit/a042808d6adbbf44753d52c55cac5f533e24101f', 'https://lists.apache.org/thread.html/r2237a27040b57adc2fcc5570bd530ad2038e67fcb2a3ce65283d3143@%3Ccommits.tomee.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://github.com/advisories/GHSA-x64g-4xx9-fh6x', 'https://lists.apache.org/thread.html/r209de85beae4d257d27fc577e3a3e97039bdb4c2dc6f4a8e5a5a5811@%3Ccommits.tomee.apache.org%3E', 'https://lists.apache.org/thread.html/r77c48cd851f60833df9a9c9c31f12243508e15d1b2a0961066d44fc6@%3Ccommits.tomee.apache.org%3E', 'https://github.com/vt-middleware/cryptacular/blob/master/src/main/java/org/cryptacular/CiphertextHeader.java#L153', 'https://github.com/vt-middleware/cryptacular/commit/ec2fb65f2455c479376695e3d75d30c7f6884b3f', 'https://lists.apache.org/thread.html/rfa4647c58e375996e62a9094bffff6dc350ec311ba955b430e738945@%3Cdev.ws.apache.org%3E', 'https://github.com/apereo/cas/commit/8810f2b6c71d73341d4dde6b09a18eb46cfd6d45', 'https://github.com/vt-middleware/cryptacular/blob/fafccd07ab1214e3588a35afe3c361519129605f/src/main/java/org/cryptacular/CiphertextHeader.java#L153', 'https://lists.apache.org/thread.html/re7f46c4cc29a4616e0aa669c84a0eb34832e83a8eef05189e2e59b44@%3Cdev.ws.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7226', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://github.com/vt-middleware/cryptacular/commit/311baf12252abf21947afd07bf0a0291ec3ec796', 'https://lists.apache.org/thread.html/r4a62133ad01d5f963755021027a4cce23f76b8674a13860d2978c7c8@%3Ccommits.tomee.apache.org%3E', 'https://lists.apache.org/thread.html/rc36b75cabb4d700b48035d15ad8b8c2712bb32123572a1bdaec2510a@%3Cdev.ws.apache.org%3E', 'https://github.com/vt-middleware/cryptacular/pull/56', 'https://github.com/apereo/cas/commit/93b1c3e9d90e36a19d0fa0f6efb863c6f0235e75', 'https://github.com/apereo/cas/pull/4685'} | null | {'https://github.com/apereo/cas/commit/93b1c3e9d90e36a19d0fa0f6efb863c6f0235e75', 'https://github.com/apereo/cas/commit/a042808d6adbbf44753d52c55cac5f533e24101f', 'https://github.com/vt-middleware/cryptacular/commit/311baf12252abf21947afd07bf0a0291ec3ec796', 'https://github.com/apereo/cas/commit/8810f2b6c71d73341d4dde6b09a18eb46cfd6d45', 'https://github.com/vt-middleware/cryptacular/commit/ec2fb65f2455c479376695e3d75d30c7f6884b3f'} | {'https://github.com/apereo/cas/commit/a042808d6adbbf44753d52c55cac5f533e24101f', 'https://github.com/apereo/cas/commit/8810f2b6c71d73341d4dde6b09a18eb46cfd6d45', 'https://github.com/vt-middleware/cryptacular/commit/311baf12252abf21947afd07bf0a0291ec3ec796', 'https://github.com/apereo/cas/commit/93b1c3e9d90e36a19d0fa0f6efb863c6f0235e75', 'https://github.com/vt-middleware/cryptacular/commit/ec2fb65f2455c479376695e3d75d30c7f6884b3f'} |
GHSA | GHSA-xqfj-35wv-m3cr | Null pointer dereference in `StringNGrams` | ### Impact
An attacker can trigger a dereference of a null pointer in `tf.raw_ops.StringNGrams`:
```python
import tensorflow as tf
data=tf.constant([''] * 11, shape=[11], dtype=tf.string)
splits = [0]*115
splits.append(3)
data_splits=tf.constant(splits, shape=[116], dtype=tf.int64)
tf.raw_ops.StringNGrams(data=data, data_splits=data_splits, separator=b'Ss',
ngram_widths=[7,6,11],
left_pad='ABCDE', right_pad=b'ZYXWVU',
pad_width=50, preserve_short_sequences=True)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/1cdd4da14282210cc759e468d9781741ac7d01bf/tensorflow/core/kernels/string_ngrams_op.cc#L67-L74) does not fully validate the `data_splits` argument. This would result in [`ngrams_data`](https://github.com/tensorflow/tensorflow/blob/1cdd4da14282210cc759e468d9781741ac7d01bf/tensorflow/core/kernels/string_ngrams_op.cc#L106-L110) to be a null pointer when the output would be computed to have 0 or negative size.
Later writes to the output tensor would then cause a null pointer dereference.
### Patches
We have patched the issue in GitHub commit [ba424dd8f16f7110eea526a8086f1a155f14f22b](https://github.com/tensorflow/tensorflow/commit/ba424dd8f16f7110eea526a8086f1a155f14f22b).
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-29541'} | 2021-05-21T17:07:00Z | 2021-05-21T14:23:12Z | LOW | 2.5 | {'CWE-476'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-xqfj-35wv-m3cr', 'https://github.com/tensorflow/tensorflow/commit/ba424dd8f16f7110eea526a8086f1a155f14f22b', 'https://github.com/advisories/GHSA-xqfj-35wv-m3cr', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29541'} | null | {'https://github.com/tensorflow/tensorflow/commit/ba424dd8f16f7110eea526a8086f1a155f14f22b'} | {'https://github.com/tensorflow/tensorflow/commit/ba424dd8f16f7110eea526a8086f1a155f14f22b'} |
GHSA | GHSA-6vx5-cg2p-7g5v | Unrestricted Upload of File with Dangerous Type in microweber | Unrestricted Upload of File with Dangerous Type in GitHub repository microweber/microweber prior to 1.2.12. | {'CVE-2022-0912'} | 2022-03-22T21:37:49Z | 2022-03-12T00:00:35Z | MODERATE | 4.8 | {'CWE-434'} | {'https://github.com/microweber/microweber/commit/24245297231f5dc88bb3a2b20d0e4e25b0ebc789', 'https://huntr.dev/bounties/ae5bb359-7e53-498b-848e-540c05b44c54', 'https://github.com/advisories/GHSA-6vx5-cg2p-7g5v', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0912'} | null | {'https://github.com/microweber/microweber/commit/24245297231f5dc88bb3a2b20d0e4e25b0ebc789'} | {'https://github.com/microweber/microweber/commit/24245297231f5dc88bb3a2b20d0e4e25b0ebc789'} |
GHSA | GHSA-fjqr-fx3f-g4rv | Electron protocol handler browser vulnerable to Command Injection | Github Electron version Electron 1.8.2-beta.4 and earlier contains a Command Injection vulnerability in Protocol Handler that can result in command execute. This attack appear to be exploitable via the victim opening an electron protocol handler in their browser. This vulnerability appears to have been fixed in Electron 1.8.2-beta.5. This issue is due to an incomplete fix for CVE-2018-1000006, specifically the black list used was not case insensitive allowing an attacker to potentially bypass it. | {'CVE-2018-1000118'} | 2022-04-26T14:35:23Z | 2018-03-26T16:41:20Z | HIGH | 8.8 | {'CWE-78'} | {'https://github.com/electron/electron/commit/ce361a12e355f9e1e99c989f1ea056c9e502dbe7', 'https://electronjs.org/releases#1.8.2-beta.5', 'https://nvd.nist.gov/vuln/detail/CVE-2018-1000118', 'https://github.com/advisories/GHSA-fjqr-fx3f-g4rv'} | null | {'https://github.com/electron/electron/commit/ce361a12e355f9e1e99c989f1ea056c9e502dbe7'} | {'https://github.com/electron/electron/commit/ce361a12e355f9e1e99c989f1ea056c9e502dbe7'} |
GHSA | GHSA-rg32-m3hf-772v | Deserialization of Untrusted Data in Slanger | Slanger 0.6.0 is affected by Remote Code Execution (RCE). The impact is A remote attacker can execute arbitrary commands by sending a crafted request to the server. The component is Message handler & request validator. The attack vector is Remote unauthenticated. The fixed version is after commit 5267b455caeb2e055cccf0d2b6a22727c111f5c3. | {'CVE-2019-1010306'} | 2021-05-11T15:51:16Z | 2019-07-16T00:41:40Z | CRITICAL | 9.8 | {'CWE-502'} | {'https://github.com/stevegraham/slanger/pull/238/commits/5267b455caeb2e055cccf0d2b6a22727c111f5c3', 'https://nvd.nist.gov/vuln/detail/CVE-2019-1010306', 'https://github.com/advisories/GHSA-rg32-m3hf-772v'} | null | {'https://github.com/stevegraham/slanger/pull/238/commits/5267b455caeb2e055cccf0d2b6a22727c111f5c3'} | {'https://github.com/stevegraham/slanger/pull/238/commits/5267b455caeb2e055cccf0d2b6a22727c111f5c3'} |
GHSA | GHSA-fr6q-jv7j-35g3 | Path Traversal in w-zip | Path Traversal in NPM w-zip prior to 1.0.12. | {'CVE-2022-0401'} | 2022-02-10T23:41:29Z | 2022-02-02T00:01:46Z | CRITICAL | 9.8 | {'CWE-22'} | {'https://github.com/advisories/GHSA-fr6q-jv7j-35g3', 'https://github.com/yuda-lyu/w-zip/commit/d7039d034e02fa358e6656565157cedf5fa83288', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0401', 'https://huntr.dev/bounties/d93259aa-ad03-43d6-8846-a00b9f58876d'} | null | {'https://github.com/yuda-lyu/w-zip/commit/d7039d034e02fa358e6656565157cedf5fa83288'} | {'https://github.com/yuda-lyu/w-zip/commit/d7039d034e02fa358e6656565157cedf5fa83288'} |
GHSA | GHSA-374m-jm66-3vj8 | Heap OOB in `SparseBinCount` | ### Impact
The [implementation](https://github.com/tensorflow/tensorflow/blob/e71b86d47f8bc1816bf54d7bddc4170e47670b97/tensorflow/core/kernels/bincount_op.cc#L353-L417) of `SparseBinCount` is vulnerable to a heap OOB:
```python
import tensorflow as tf
tf.raw_ops.SparseBincount(
indices=[[0],[1],[2]]
values=[0,-10000000]
dense_shape=[1,1]
size=[1]
weights=[3,2,1]
binary_output=False)
```
This is because of missing validation between the elements of the `values` argument and the shape of the sparse output:
```cc
for (int64_t i = 0; i < indices_mat.dimension(0); ++i) {
const int64_t batch = indices_mat(i, 0);
const Tidx bin = values(i);
...
out(batch, bin) = ...;
}
```
### Patches
We have patched the issue in GitHub commit [f410212e373eb2aec4c9e60bf3702eba99a38aba](https://github.com/tensorflow/tensorflow/commit/f410212e373eb2aec4c9e60bf3702eba99a38aba).
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-41226'} | 2021-11-10T18:41:47Z | 2021-11-10T18:41:47Z | HIGH | 7.1 | {'CWE-125'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-41226', 'https://github.com/advisories/GHSA-374m-jm66-3vj8', 'https://github.com/tensorflow/tensorflow/commit/f410212e373eb2aec4c9e60bf3702eba99a38aba', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-374m-jm66-3vj8'} | null | {'https://github.com/tensorflow/tensorflow/commit/f410212e373eb2aec4c9e60bf3702eba99a38aba'} | {'https://github.com/tensorflow/tensorflow/commit/f410212e373eb2aec4c9e60bf3702eba99a38aba'} |
GHSA | GHSA-gfp2-w5jm-955q | OMERO.web exposes some unnecessary session information in the page | ### Background
OMERO.web loads various information about the current user such as their id, name and the groups they are in, and these are available on the main webclient pages. Some additional information being loaded is not used by the webclient and is being removed in this release.
### Impact
OMERO.web before 5.9.0
### Patches
5.9.0
### Workarounds
No workaround
### References
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [omero-web](https://github.com/ome/omero-web)
* Email us at [security](mailto:security@openmicroscopy.org.uk) | {'CVE-2021-21376'} | 2021-03-29T17:30:03Z | 2021-03-23T15:26:34Z | MODERATE | 0 | {'CWE-200'} | {'https://github.com/ome/omero-web/commit/952f8e5d28532fbb14fb665982211329d137908c', 'https://www.openmicroscopy.org/security/advisories/2021-SV1/', 'https://pypi.org/project/omero-web/', 'https://github.com/ome/omero-web/security/advisories/GHSA-gfp2-w5jm-955q', 'https://github.com/ome/omero-web/blob/master/CHANGELOG.md#590-march-2021', 'https://github.com/advisories/GHSA-gfp2-w5jm-955q', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21376'} | null | {'https://github.com/ome/omero-web/commit/952f8e5d28532fbb14fb665982211329d137908c'} | {'https://github.com/ome/omero-web/commit/952f8e5d28532fbb14fb665982211329d137908c'} |
GHSA | GHSA-8h2f-7jc4-7m3m | Open Redirect in urijs | urijs prior to version 1.19.10 is vulnerable to open redirect. This is the result of a bypass for the fix to CVE-2022-0613. | {'CVE-2022-0868'} | 2022-03-14T21:10:49Z | 2022-03-07T00:00:40Z | MODERATE | 6.1 | {'CWE-601'} | {'https://github.com/medialize/URI.js/releases/tag/v1.19.10', 'https://huntr.dev/bounties/5f4db013-64bd-4a6b-9dad-870c296b0b02', 'https://github.com/advisories/GHSA-8h2f-7jc4-7m3m', 'https://github.com/medialize/uri.js/commit/a8166fe02f3af6dc1b2b888dcbb807155aad9509', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0868'} | null | {'https://github.com/medialize/uri.js/commit/a8166fe02f3af6dc1b2b888dcbb807155aad9509'} | {'https://github.com/medialize/uri.js/commit/a8166fe02f3af6dc1b2b888dcbb807155aad9509'} |
GHSA | GHSA-qjhr-c23f-w76q | Inline JS XSS vulnerability in Mautic | ### Impact
Mautic version 2.1.0 - 2.11.0 is vulnerable to an inline JS XSS attack when using Mautic forms on a Mautic landing page using GET parameters to pre-populate the form.
### Patches
Upgrade to 2.12.0 or later.
### Workarounds
None
### References
https://github.com/mautic/mautic/releases/tag/2.12.0
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@mautic.org](mailto:security@mautic.org) | {'CVE-2017-1000488'} | 2022-04-19T19:02:44Z | 2021-01-19T21:16:24Z | MODERATE | 6.1 | {'CWE-79'} | {'https://github.com/mautic/mautic/releases/tag/2.12.0', 'https://github.com/advisories/GHSA-qjhr-c23f-w76q', 'https://github.com/mautic/mautic/security/advisories/GHSA-qjhr-c23f-w76q', 'https://github.com/mautic/mautic/commit/bda60c0eefbd19c759589e975e63ab1d201c1b8e', 'https://nvd.nist.gov/vuln/detail/CVE-2017-1000488'} | null | {'https://github.com/mautic/mautic/commit/bda60c0eefbd19c759589e975e63ab1d201c1b8e'} | {'https://github.com/mautic/mautic/commit/bda60c0eefbd19c759589e975e63ab1d201c1b8e'} |
GHSA | GHSA-9crf-c6qr-r273 | Integer division by 0 in `tf.raw_ops.AllToAll` | ### Impact
The [shape inference code for `AllToAll`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/tpu_cross_replica_ops.cc#L25-L74) can be made to execute a division by 0:
```python
import tensorflow as tf
@tf.function
def func():
return tf.raw_ops.AllToAll(
input=[0.0, 0.1652, 0.6543],
group_assignment=[1, -1],
concat_dimension=0,
split_dimension=0,
split_count=0)
func()
```
This occurs whenever the `split_count` argument is 0:
```cc
TF_RETURN_IF_ERROR(c->GetAttr("split_count", &split_count));
...
for (int32_t i = 0; i < rank; ++i) {
...
dims[i] = c->MakeDim(c->Value(dims[i]) / split_count);
...
}
```
### Patches
We have patched the issue in GitHub commit [a8ad3e5e79c75f36edb81e0ba3f3c0c5442aeddc](https://github.com/tensorflow/tensorflow/commit/a8ad3e5e79c75f36edb81e0ba3f3c0c5442aeddc).
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-41218'} | 2021-11-10T18:52:24Z | 2021-11-10T18:52:24Z | MODERATE | 5.5 | {'CWE-369'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-41218', 'https://github.com/advisories/GHSA-9crf-c6qr-r273', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9crf-c6qr-r273', 'https://github.com/tensorflow/tensorflow/commit/a8ad3e5e79c75f36edb81e0ba3f3c0c5442aeddc'} | null | {'https://github.com/tensorflow/tensorflow/commit/a8ad3e5e79c75f36edb81e0ba3f3c0c5442aeddc'} | {'https://github.com/tensorflow/tensorflow/commit/a8ad3e5e79c75f36edb81e0ba3f3c0c5442aeddc'} |
GHSA | GHSA-v542-8q9x-cffc | Exposure of Sensitive Information to an Unauthorized Actor | Django Channels 3.x before 3.0.3 allows remote attackers to obtain sensitive information from a different request scope. The legacy channels.http.AsgiHandler class, used for handling HTTP type requests in an ASGI environment prior to Django 3.0, did not correctly separate request scopes in Channels 3.0. In many cases this would result in a crash but, with correct timing, responses could be sent to the wrong client, resulting in potential leakage of session identifiers and other sensitive data. Note that this affects only the legacy Channels provided class, and not Django's similar ASGIHandler, available from Django 3.0. | {'CVE-2020-35681'} | 2021-03-19T21:29:02Z | 2021-03-19T21:29:02Z | HIGH | 7.4 | {'CWE-200'} | {'https://github.com/django/channels/releases', 'https://channels.readthedocs.io/en/stable/releases/index.html', 'https://github.com/advisories/GHSA-v542-8q9x-cffc', 'https://github.com/django/channels/commit/e85874d9630474986a6937430eac52db79a2a022', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35681', 'https://channels.readthedocs.io/en/stable/releases/3.0.3.html'} | null | {'https://github.com/django/channels/commit/e85874d9630474986a6937430eac52db79a2a022'} | {'https://github.com/django/channels/commit/e85874d9630474986a6937430eac52db79a2a022'} |
GHSA | GHSA-pf8f-w267-mq2h | The rack-cors rubygem may allow directory traveral | An issue was discovered in the rack-cors (aka Rack CORS Middleware) gem before 1.0.4 for Ruby. It allows ../ directory traversal to access private resources because resource matching does not ensure that pathnames are in a canonical format. | {'CVE-2019-18978'} | 2021-08-18T22:30:22Z | 2019-11-15T20:26:59Z | MODERATE | 5.3 | {'CWE-22'} | {'https://github.com/advisories/GHSA-pf8f-w267-mq2h', 'https://github.com/cyu/rack-cors/commit/e4d4fc362a4315808927011cbe5afcfe5486f17d', 'https://www.debian.org/security/2021/dsa-4918', 'https://lists.debian.org/debian-lts-announce/2020/02/msg00004.html', 'https://nvd.nist.gov/vuln/detail/CVE-2019-18978', 'https://lists.debian.org/debian-lts-announce/2020/10/msg00000.html', 'https://github.com/cyu/rack-cors/compare/v1.0.3...v1.0.4', 'https://usn.ubuntu.com/4571-1/'} | null | {'https://github.com/cyu/rack-cors/commit/e4d4fc362a4315808927011cbe5afcfe5486f17d'} | {'https://github.com/cyu/rack-cors/commit/e4d4fc362a4315808927011cbe5afcfe5486f17d'} |
GHSA | GHSA-9px9-73fg-3fqp | Null pointer dereference in Grappler's `IsConstant` | ### Impact
Under certain scenarios, Grappler component of TensorFlow can trigger a null pointer dereference. There are 2 places where this can occur, for the same malicious alteration of a `SavedModel` file (fixing the first one would trigger the same dereference in the second place):
First, during [constant folding](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/grappler/optimizers/constant_folding.cc#L3466-L3497), the `GraphDef` might not have the required nodes for the binary operation:
```cc
NodeDef* mul_left_child = node_map_->GetNode(node->input(0));
NodeDef* mul_right_child = node_map_->GetNode(node->input(1));
// One child must be constant, and the second must be Conv op.
const bool left_child_is_constant = IsReallyConstant(*mul_left_child);
const bool right_child_is_constant = IsReallyConstant(*mul_right_child);
```
If a node is missing, the correposning `mul_*child` would be null, and the dereference in the subsequent line would be incorrect.
We have a similar issue during [`IsIdentityConsumingSwitch`](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/grappler/mutable_graph_view.cc#L59-L74):
```cc
NodeDef* input_node = graph.GetNode(tensor_id.node());
return IsSwitch(*input_node);
```
### Patches
We have patched the issue in GitHub commits [0a365c029e437be0349c31f8d4c9926b69fa3fa1](https://github.com/tensorflow/tensorflow/commit/0a365c029e437be0349c31f8d4c9926b69fa3fa1) and [045deec1cbdebb27d817008ad5df94d96a08b1bf](https://github.com/tensorflow/tensorflow/commit/045deec1cbdebb27d817008ad5df94d96a08b1bf).
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. | {'CVE-2022-23589'} | 2022-02-11T20:00:55Z | 2022-02-09T23:29:14Z | MODERATE | 6.5 | {'CWE-476'} | {'https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/grappler/mutable_graph_view.cc#L59-L74', 'https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/grappler/optimizers/constant_folding.cc#L3466-L3497', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9px9-73fg-3fqp', 'https://github.com/tensorflow/tensorflow/commit/045deec1cbdebb27d817008ad5df94d96a08b1bf', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23589', 'https://github.com/advisories/GHSA-9px9-73fg-3fqp', 'https://github.com/tensorflow/tensorflow/commit/0a365c029e437be0349c31f8d4c9926b69fa3fa1'} | null | {'https://github.com/tensorflow/tensorflow/commit/045deec1cbdebb27d817008ad5df94d96a08b1bf', 'https://github.com/tensorflow/tensorflow/commit/0a365c029e437be0349c31f8d4c9926b69fa3fa1'} | {'https://github.com/tensorflow/tensorflow/commit/045deec1cbdebb27d817008ad5df94d96a08b1bf', 'https://github.com/tensorflow/tensorflow/commit/0a365c029e437be0349c31f8d4c9926b69fa3fa1'} |
GHSA | GHSA-4p8f-mmfj-r45g | Cross-site scripting in fat_free_crm | Fat Free CRM before 0.18.1 has XSS in the tags_helper in app/helpers/tags_helper.rb. | {'CVE-2018-20975'} | 2021-08-17T21:11:19Z | 2019-08-21T16:15:04Z | MODERATE | 6.1 | {'CWE-79'} | {'https://github.com/fatfreecrm/fat_free_crm/commit/6d60bc8ed010c4eda05d6645c64849f415f68d65', 'https://github.com/fatfreecrm/fat_free_crm/compare/v0.17.3...v0.18.1', 'https://github.com/advisories/GHSA-4p8f-mmfj-r45g', 'https://github.com/fatfreecrm/fat_free_crm/releases/tag/v0.18.1', 'https://nvd.nist.gov/vuln/detail/CVE-2018-20975'} | null | {'https://github.com/fatfreecrm/fat_free_crm/commit/6d60bc8ed010c4eda05d6645c64849f415f68d65'} | {'https://github.com/fatfreecrm/fat_free_crm/commit/6d60bc8ed010c4eda05d6645c64849f415f68d65'} |
GHSA | GHSA-qw5h-7f53-xrp6 | Stack overflow in `ParseAttrValue` with nested tensors | ### Impact
The implementation of [`ParseAttrValue`](https://github.com/tensorflow/tensorflow/blob/c22d88d6ff33031aa113e48aa3fc9aa74ed79595/tensorflow/core/framework/attr_value_util.cc#L397-L453) can be tricked into stack overflow due to recursion by giving in a specially crafted input.
### Patches
We have patched the issue in GitHub commit [e07e1c3d26492c06f078c7e5bf2d138043e199c1](https://github.com/tensorflow/tensorflow/commit/e07e1c3d26492c06f078c7e5bf2d138043e199c1).
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. | {'CVE-2021-29615'} | 2021-05-21T14:28:45Z | 2021-05-21T14:28:45Z | LOW | 2.5 | {'CWE-674'} | {'https://github.com/advisories/GHSA-qw5h-7f53-xrp6', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qw5h-7f53-xrp6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29615', 'https://github.com/tensorflow/tensorflow/commit/e07e1c3d26492c06f078c7e5bf2d138043e199c1'} | null | {'https://github.com/tensorflow/tensorflow/commit/e07e1c3d26492c06f078c7e5bf2d138043e199c1'} | {'https://github.com/tensorflow/tensorflow/commit/e07e1c3d26492c06f078c7e5bf2d138043e199c1'} |
GHSA | GHSA-86ch-6w7v-v6xf | Denial of Service in soketi | ### Impact
_What kind of vulnerability is it? Who is impacted?_
There was a wrong behavior when reading POST requests, making the server crash if it couldn't read the body. In case a POST request was sent to any endpoint of the server with an empty body, **even unauthenticated with the Pusher Protocol**, it would simply just crash the server for trying to send a response after the request closed.
All users that run the server are affected by it and it's highly recommended to upgrade to the latest patch.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
Updating to at least 0.24.1 or the latest version.
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
No. Upgrading is the only solution.
### References
_Are there any links users can visit to find out more?_
https://github.com/soketi/soketi/releases/tag/0.24.1
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the issues board](https://github.com/soketi/soketi/issues)
* Email us at [alex@renoki.org](mailto:alex@renoki.org)
| {'CVE-2022-21667'} | 2022-01-18T22:37:18Z | 2022-01-08T00:24:44Z | HIGH | 7.5 | {'CWE-755'} | {'https://github.com/advisories/GHSA-86ch-6w7v-v6xf', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21667', 'https://github.com/soketi/soketi/commit/4b12efef9c31117c36a0a0f1c3aa32114e86364b', 'https://github.com/soketi/soketi/security/advisories/GHSA-86ch-6w7v-v6xf', 'https://github.com/soketi/soketi/releases/tag/0.24.1'} | null | {'https://github.com/soketi/soketi/commit/4b12efef9c31117c36a0a0f1c3aa32114e86364b'} | {'https://github.com/soketi/soketi/commit/4b12efef9c31117c36a0a0f1c3aa32114e86364b'} |
GHSA | GHSA-48w2-rm65-62xx | Inconsistent Interpretation of HTTP Requests in puma | ### Impact
Prior to `puma` version 5.5.0, using `puma` with a proxy which forwards LF characters as line endings could allow HTTP request smuggling. A client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client.
This behavior (forwarding LF characters as line endings) is very uncommon amongst proxy servers, so we have graded the impact here as "low". Puma is only aware of a single proxy server which has this behavior.
If the proxy uses persistent connections and the client adds another request in via HTTP pipelining, the proxy may mistake it as the first request's body. Puma, however, would see it as two requests, and when processing the second request, send back a response that the proxy does not expect. If the proxy has reused the persistent connection to Puma to send another request for a different client, the second response from the first client will be sent to the second client.
### Patches
This vulnerability was patched in Puma 5.5.1 and 4.3.9.
### Workarounds
This vulnerability only affects Puma installations without any proxy in front.
Use a proxy which does not forward LF characters as line endings.
Proxies which do not forward LF characters as line endings:
* Nginx
* Apache (>2.4.25)
* Haproxy
* Caddy
* Traefik
### Possible Breakage
If you are [dealing with legacy clients that want to send `LF` as a line ending](https://stackoverflow.com/questions/43574428/have-apache-accept-lf-vs-crlf-in-request-headers) in an HTTP header, this will cause those clients to receive a `400` error.
### References
* [HTTP Request Smuggling](https://portswigger.net/web-security/request-smuggling)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Puma](https://github.com/puma/puma)
* See our [security policy](https://github.com/puma/puma/security/policy)
| {'CVE-2021-41136'} | 2022-04-19T19:03:12Z | 2021-10-12T17:53:00Z | LOW | 3.7 | {'CWE-444'} | {'https://github.com/puma/puma/releases/tag/v5.5.1', 'https://github.com/advisories/GHSA-48w2-rm65-62xx', 'https://github.com/puma/puma/releases/tag/v4.3.9', 'https://github.com/puma/puma/security/advisories/GHSA-48w2-rm65-62xx', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41136', 'https://github.com/puma/puma/commit/acdc3ae571dfae0e045cf09a295280127db65c7f'} | null | {'https://github.com/puma/puma/commit/acdc3ae571dfae0e045cf09a295280127db65c7f'} | {'https://github.com/puma/puma/commit/acdc3ae571dfae0e045cf09a295280127db65c7f'} |
GHSA | GHSA-8rc5-hx3v-2jg7 | Sanitizer bypass in svg-sanitizer | It is possible to bypass enshrined/svg-sanitize before 0.13.1 using the "xlink:href" attribute due to mishandling of the xlink namespace by the sanitizer. | {'CVE-2019-10772'} | 2021-08-19T19:25:07Z | 2020-02-27T20:36:29Z | MODERATE | 6.1 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-10772', 'https://snyk.io/vuln/SNYK-PHP-ENSHRINEDSVGSANITIZE-536969', 'https://github.com/advisories/GHSA-8rc5-hx3v-2jg7', 'https://github.com/darylldoyle/svg-sanitizer/commit/6add43e5c5649bc40e3afcb68c522720dcb336f9'} | null | {'https://github.com/darylldoyle/svg-sanitizer/commit/6add43e5c5649bc40e3afcb68c522720dcb336f9'} | {'https://github.com/darylldoyle/svg-sanitizer/commit/6add43e5c5649bc40e3afcb68c522720dcb336f9'} |
GHSA | GHSA-9qrh-qjmc-5w2p | Denial-of-Service when binding invalid parameters in sqlite3 | Affected versions of sqlite3 will experience a fatal error when supplying a specific object in the parameter array. This error causes the application to crash and could not be caught. Users of `sqlite3` v5.0.0, v5.0.1 and v5.0.2 are affected by this. This issue is fixed in v5.0.3. All users are recommended to upgrade to v5.0.3 or later. Ensure there is sufficient sanitization in the parent application to protect against invalid values being supplied to binding parameters as a workaround.
| {'CVE-2022-21227'} | 2022-05-03T02:24:26Z | 2022-04-28T20:25:23Z | HIGH | 7.5 | {'CWE-248'} | {'https://github.com/TryGhost/node-sqlite3/issues/1440', 'https://github.com/TryGhost/node-sqlite3/issues/1449', 'https://github.com/TryGhost/node-sqlite3/commit/593c9d498be2510d286349134537e3bf89401c4a', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-2805470', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21227', 'https://github.com/TryGhost/node-sqlite3/security/advisories/GHSA-9qrh-qjmc-5w2p', 'https://security.snyk.io/vuln/SNYK-JS-SQLITE3-2388645', 'https://github.com/advisories/GHSA-9qrh-qjmc-5w2p', 'https://snyk.io/vuln/SNYK-JS-SQLITE3-2388645'} | null | {'https://github.com/TryGhost/node-sqlite3/commit/593c9d498be2510d286349134537e3bf89401c4a'} | {'https://github.com/TryGhost/node-sqlite3/commit/593c9d498be2510d286349134537e3bf89401c4a'} |
GHSA | GHSA-7fm6-gxqg-2pwr | Code Injection in total.js | The package total.js before 3.4.9 are vulnerable to Arbitrary Code Execution via the U.set() and U.get() functions. | {'CVE-2021-23389'} | 2021-12-10T17:26:06Z | 2021-12-10T17:26:06Z | CRITICAL | 9.8 | {'CWE-94'} | {'https://snyk.io/vuln/SNYK-JS-TOTALJS-1088607', 'https://github.com/advisories/GHSA-7fm6-gxqg-2pwr', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23389', 'https://github.com/totaljs/framework/blob/master/utils.js%23L6606-L6631', 'https://github.com/totaljs/framework/commit/887b0fa9e162ef7a2dd9cec20a5ca122726373b3'} | null | {'https://github.com/totaljs/framework/commit/887b0fa9e162ef7a2dd9cec20a5ca122726373b3'} | {'https://github.com/totaljs/framework/commit/887b0fa9e162ef7a2dd9cec20a5ca122726373b3'} |
GHSA | GHSA-j7m2-58wv-9v79 | Vulnerability in Torpedo Query | Torpedo Query before 2.5.3 mishandles the LIKE operator in ConditionBuilder.java, LikeCondition.java, and NotLikeCondition.java. | {'CVE-2019-11343'} | 2022-02-10T20:47:29Z | 2022-02-10T20:47:29Z | CRITICAL | 9.8 | null | {'https://github.com/xjodoin/torpedoquery/compare/v2.5.2...v2.5.3', 'https://github.com/xjodoin/torpedoquery/commit/3c20b874fba9cc2a78b9ace10208de1602b56c3f', 'https://nvd.nist.gov/vuln/detail/CVE-2019-11343', 'https://github.com/advisories/GHSA-j7m2-58wv-9v79'} | null | {'https://github.com/xjodoin/torpedoquery/commit/3c20b874fba9cc2a78b9ace10208de1602b56c3f'} | {'https://github.com/xjodoin/torpedoquery/commit/3c20b874fba9cc2a78b9ace10208de1602b56c3f'} |
GHSA | GHSA-2hxv-mx8x-mcj9 | Spina vulnerable to a cross-site request forgery (CSRF) vulnerability | Cross-site request forgery (CSRF) vulnerability in Spina before commit bfe44f289e336f80b6593032679300c493735e75. | {'CVE-2015-4619'} | 2022-04-26T18:26:09Z | 2018-08-28T22:34:22Z | HIGH | 8.8 | {'CWE-352'} | {'http://www.securityfocus.com/bid/75216', 'https://github.com/advisories/GHSA-2hxv-mx8x-mcj9', 'http://www.openwall.com/lists/oss-security/2015/06/16/20', 'https://nvd.nist.gov/vuln/detail/CVE-2015-4619', 'https://github.com/denkGroot/Spina/commit/bfe44f289e336f80b6593032679300c493735e75'} | null | {'https://github.com/denkGroot/Spina/commit/bfe44f289e336f80b6593032679300c493735e75'} | {'https://github.com/denkGroot/Spina/commit/bfe44f289e336f80b6593032679300c493735e75'} |
GHSA | GHSA-c3m8-x3cg-qm2c | Configuration Override in helmet-csp | Versions of `helmet-csp` before to 2.9.1 are vulnerable to a Configuration Override affecting the application's Content Security Policy (CSP). The package's browser sniffing for Firefox deletes the `default-src` CSP policy, which is the fallback policy. This allows an attacker to remove an application's default CSP, possibly rendering the application vulnerable to Cross-Site Scripting.
## Recommendation
Upgrade to version 2.9.1 or later. Setting the `browserSniff` configuration to `false` in vulnerable versions also mitigates the issue. | null | 2021-09-29T18:45:07Z | 2020-09-03T20:39:53Z | MODERATE | 6.5 | null | {'https://snyk.io/vuln/SNYK-JS-HELMETCSP-469436', 'https://github.com/advisories/GHSA-c3m8-x3cg-qm2c', 'https://github.com/helmetjs/csp/commit/67a69baafa8198a154f0505a0cf0875f76f6186a', 'https://www.npmjs.com/advisories/1176'} | null | {'https://github.com/helmetjs/csp/commit/67a69baafa8198a154f0505a0cf0875f76f6186a'} | {'https://github.com/helmetjs/csp/commit/67a69baafa8198a154f0505a0cf0875f76f6186a'} |
GHSA | GHSA-m94c-37g6-cjhc | Fake objects feature vulnerability allowing to execute JavaScript code using malformed HTML. | ### Affected packages
The vulnerability has been discovered in [Fake Objects](https://ckeditor.com/cke4/addon/fakeobjects) plugin. All plugins with [Fake Objects](https://ckeditor.com/cke4/addon/fakeobjects) plugin dependency are affected:
* [Fake Objects](https://ckeditor.com/cke4/addon/fakeobjects)
* [Link](https://ckeditor.com/cke4/addon/link)
* [Flash](https://ckeditor.com/cke4/addon/flash)
* [Iframe](https://ckeditor.com/cke4/addon/iframe)
* [Forms](https://ckeditor.com/cke4/addon/forms)
* [Page Break](https://ckeditor.com/cke4/addon/pagebreak)
### Impact
A potential vulnerability has been discovered in CKEditor 4 [Fake Objects](https://ckeditor.com/cke4/addon/fakeobjects) package. The vulnerability allowed to inject malformed Fake Objects HTML, which could result in executing JavaScript code. It affects all users using the CKEditor 4 plugins listed above at version < 4.16.2.
### Patches
The problem has been recognized and patched. The fix will be available in version 4.16.2.
### For more information
Email us at security@cksource.com if you have any questions or comments about this advisory.
### Acknowledgements
The CKEditor 4 team would like to thank Mika Kulmala ([kulmik](https://github.com/kulmik)) for recognizing and reporting this vulnerability.
| {'CVE-2021-37695'} | 2022-02-08T21:01:40Z | 2021-08-23T19:42:15Z | HIGH | 7.3 | {'CWE-79'} | {'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://github.com/ckeditor/ckeditor4/security/advisories/GHSA-m94c-37g6-cjhc', 'https://github.com/ckeditor/ckeditor4/commit/de3c001540715f9c3801aaa38a1917de46cfcf58', 'https://lists.debian.org/debian-lts-announce/2021/11/msg00007.html', 'https://github.com/advisories/GHSA-m94c-37g6-cjhc', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37695', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NYA354LJP47KCVJMTUO77ZCX3ZK42G3T/', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WAGNWHFIQAVCP537KFFS2A2GDG66J7XD/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UVOYN2WKDPLKCNILIGEZM236ABQASLGW/'} | null | {'https://github.com/ckeditor/ckeditor4/commit/de3c001540715f9c3801aaa38a1917de46cfcf58'} | {'https://github.com/ckeditor/ckeditor4/commit/de3c001540715f9c3801aaa38a1917de46cfcf58'} |
GHSA | GHSA-7q8g-gpfp-v8gx | Insertion of Sensitive Information into Log File in Apache NiFi | In Apache NiFi 0.0.1 to 1.11.0, the flow fingerprint factory generated flow fingerprints which included sensitive property descriptor values. In the event a node attempted to join a cluster and the cluster flow was not inheritable, the flow fingerprint of both the cluster and local flow was printed, potentially containing sensitive values in plaintext. | {'CVE-2020-1942'} | 2022-01-06T20:40:58Z | 2022-01-06T20:40:58Z | HIGH | 7.5 | {'CWE-200', 'CWE-532'} | {'https://github.com/advisories/GHSA-7q8g-gpfp-v8gx', 'https://github.com/apache/nifi/commit/d7c29f46378379fb596e4d1e59d1a3c41063db5b', 'https://nvd.nist.gov/vuln/detail/CVE-2020-1942', 'https://nifi.apache.org/security.html#CVE-2020-1942', 'https://github.com/apache/nifi/commit/95746d346cddbd6134c4b28fdc39d5813a626f97'} | null | {'https://github.com/apache/nifi/commit/95746d346cddbd6134c4b28fdc39d5813a626f97', 'https://github.com/apache/nifi/commit/d7c29f46378379fb596e4d1e59d1a3c41063db5b'} | {'https://github.com/apache/nifi/commit/d7c29f46378379fb596e4d1e59d1a3c41063db5b', 'https://github.com/apache/nifi/commit/95746d346cddbd6134c4b28fdc39d5813a626f97'} |
GHSA | GHSA-46j2-xjgp-jrfm | Information disclosure issue in Active Resource | There is a possible information disclosure issue in Active Resource <v5.1.1 that could allow an attacker to create specially crafted requests to access data in an unexpected way and possibly leak information. | {'CVE-2020-8151'} | 2021-10-08T19:59:27Z | 2020-05-21T21:09:38Z | HIGH | 7.5 | {'CWE-200', 'CWE-863'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-8151', 'https://github.com/rails/activeresource/commit/0de18f7e96fa90bbf23b16ac11980bc2cb6a716e', 'https://groups.google.com/forum/#!topic/rubyonrails-security/pktoF4VmiM8', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/P7B7A4H22DZ522HLDS3JX3NX2CXIOZSR/', 'https://github.com/advisories/GHSA-46j2-xjgp-jrfm'} | null | {'https://github.com/rails/activeresource/commit/0de18f7e96fa90bbf23b16ac11980bc2cb6a716e'} | {'https://github.com/rails/activeresource/commit/0de18f7e96fa90bbf23b16ac11980bc2cb6a716e'} |
GHSA | GHSA-7f63-h6g3-7cwm | Cross Site Scripting (XSS) in @finastra/ssr-pages | A cross site scripting (XSS) issue can occur when providing untrusted input to the `redirect.link` property as an argument to the `build(MessagePageOptions)` function.
### References
- https://github.com/Finastra/ssr-pages/pull/2
- https://github.com/Finastra/ssr-pages/pull/2/commits/133606ffaec2edd9918d9fba5771ed21da7876a5
- https://github.com/Finastra/ssr-pages/commit/98abc59e28fec48246be0d59ac144675d6361073
| {'CVE-2022-24717'} | 2022-04-19T19:03:25Z | 2022-03-01T22:09:25Z | MODERATE | 6.1 | {'CWE-79'} | {'https://github.com/Finastra/ssr-pages/security/advisories/GHSA-7f63-h6g3-7cwm', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24717', 'https://github.com/Finastra/ssr-pages/commit/98abc59e28fec48246be0d59ac144675d6361073', 'https://github.com/Finastra/ssr-pages/pull/2', 'https://github.com/advisories/GHSA-7f63-h6g3-7cwm', 'https://github.com/Finastra/ssr-pages/pull/2/commits/133606ffaec2edd9918d9fba5771ed21da7876a5'} | null | {'https://github.com/Finastra/ssr-pages/commit/98abc59e28fec48246be0d59ac144675d6361073', 'https://github.com/Finastra/ssr-pages/pull/2/commits/133606ffaec2edd9918d9fba5771ed21da7876a5'} | {'https://github.com/Finastra/ssr-pages/pull/2/commits/133606ffaec2edd9918d9fba5771ed21da7876a5', 'https://github.com/Finastra/ssr-pages/commit/98abc59e28fec48246be0d59ac144675d6361073'} |
GHSA | GHSA-gf2j-f278-xh4v | Division by zero in TFLite | ### Impact
An attacker can craft a TFLite model that would trigger a division by zero in [`BiasAndClamp` implementation](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/lite/kernels/internal/common.h#L75):
```cc
inline void BiasAndClamp(float clamp_min, float clamp_max, int bias_size,
const float* bias_data, int array_size,
float* array_data) {
// ...
TFLITE_DCHECK_EQ((array_size % bias_size), 0);
// ...
}
```
There is no check that the `bias_size` is non zero.
### Patches
We have patched the issue in GitHub commit [8c6f391a2282684a25cbfec7687bd5d35261a209](https://github.com/tensorflow/tensorflow/commit/8c6f391a2282684a25cbfec7687bd5d35261a209).
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 Wang Xuan of Qihoo 360 AIVul Team. | {'CVE-2022-23557'} | 2022-02-11T16:11:40Z | 2022-02-09T23:47:57Z | MODERATE | 6.5 | {'CWE-369'} | {'https://github.com/tensorflow/tensorflow/commit/8c6f391a2282684a25cbfec7687bd5d35261a209', 'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/lite/kernels/internal/common.h#L75', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23557', 'https://github.com/advisories/GHSA-gf2j-f278-xh4v', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-gf2j-f278-xh4v'} | null | {'https://github.com/tensorflow/tensorflow/commit/8c6f391a2282684a25cbfec7687bd5d35261a209'} | {'https://github.com/tensorflow/tensorflow/commit/8c6f391a2282684a25cbfec7687bd5d35261a209'} |
GHSA | GHSA-m4fw-77v7-924m | Moderate severity vulnerability that affects qutebrowser | qutebrowser version introduced in v0.11.0 (1179ee7a937fb31414d77d9970bac21095358449) contains a Cross Site Scripting (XSS) vulnerability in history command, qute://history page that can result in Via injected JavaScript code, a website can steal the user's browsing history. This attack appear to be exploitable via the victim must open a page with a specially crafted <title> attribute, and then open the qute://history site via the :history command. This vulnerability appears to have been fixed in fixed in v1.3.3 (4c9360237f186681b1e3f2a0f30c45161cf405c7, to be released today) and v1.4.0 (5a7869f2feaa346853d2a85413d6527c87ef0d9f, released later this week). | {'CVE-2018-1000559'} | 2021-09-14T22:12:29Z | 2018-09-13T15:47:57Z | MODERATE | 6.1 | {'CWE-79'} | {'https://github.com/advisories/GHSA-m4fw-77v7-924m', 'https://github.com/qutebrowser/qutebrowser/commit/5a7869f2feaa346853d2a85413d6527c87ef0d9f', 'https://github.com/qutebrowser/qutebrowser/commit/4c9360237f186681b1e3f2a0f30c45161cf405c7', 'https://nvd.nist.gov/vuln/detail/CVE-2018-1000559', 'https://github.com/qutebrowser/qutebrowser/issues/4011'} | null | {'https://github.com/qutebrowser/qutebrowser/commit/4c9360237f186681b1e3f2a0f30c45161cf405c7', 'https://github.com/qutebrowser/qutebrowser/commit/5a7869f2feaa346853d2a85413d6527c87ef0d9f'} | {'https://github.com/qutebrowser/qutebrowser/commit/5a7869f2feaa346853d2a85413d6527c87ef0d9f', 'https://github.com/qutebrowser/qutebrowser/commit/4c9360237f186681b1e3f2a0f30c45161cf405c7'} |
GHSA | GHSA-w8rc-pgxq-x2cj | Negative charge in shopping cart in Shopizer | ### Impact
Using API or Controller based versions negative quantity is not adequately validated hence creating incorrect shopping cart and order total.
### Patches
Adding a back-end verification to check that quantity parameter isn't negative. If so, it is set to 1. Patched in 2.11.0
### Workarounds
Without uprading, it's possible to just apply the fixes in the same files it's done for the patch. Or you use javax constraint validation on the quantity parameter.
### References
[Input Validation](https://cheatsheetseries.owasp.org/cheatsheets/Input_Validation_Cheat_Sheet.html)
[Using bean validation constraint](https://javaee.github.io/tutorial/bean-validation002.html)
[Commits with fixes](https://github.com/shopizer-ecommerce/shopizer/commit/929ca0839a80c6f4dad087e0259089908787ad2a)
CVE Details below :
[Mitre](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11007)
[NVD](https://nvd.nist.gov/vuln/detail/CVE-2020-11007)
### Credits
Found and solved by Yannick Gosset from Aix-Marseille University cybersecurity
master program supervised by Yassine Ilmi | {'CVE-2020-11007'} | 2022-04-19T19:02:25Z | 2020-04-22T20:59:26Z | CRITICAL | 6.5 | {'CWE-20'} | {'https://github.com/shopizer-ecommerce/shopizer/commit/929ca0839a80c6f4dad087e0259089908787ad2a', 'https://github.com/shopizer-ecommerce/shopizer/security/advisories/GHSA-w8rc-pgxq-x2cj', 'https://github.com/advisories/GHSA-w8rc-pgxq-x2cj', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11007'} | null | {'https://github.com/shopizer-ecommerce/shopizer/commit/929ca0839a80c6f4dad087e0259089908787ad2a'} | {'https://github.com/shopizer-ecommerce/shopizer/commit/929ca0839a80c6f4dad087e0259089908787ad2a'} |
GHSA | GHSA-f256-j965-7f32 | Possible request smuggling in HTTP/2 due missing validation of content-length | ### Impact
The content-length header is not correctly validated if the request only use a single Http2HeaderFrame with the endStream set to to true. This could lead to request smuggling if the request is proxied to a remote peer and translated to HTTP/1.1
This is a followup of https://github.com/netty/netty/security/advisories/GHSA-wm47-8v5p-wjpj which did miss to fix this one case.
### Patches
This was fixed as part of 4.1.61.Final
### Workarounds
Validation can be done by the user before proxy the request by validating the header. | {'CVE-2021-21409'} | 2022-04-22T15:50:24Z | 2021-03-30T15:10:38Z | MODERATE | 5.9 | {'CWE-444'} | {'https://lists.apache.org/thread.html/r69efd8ef003f612c43e4154e788ca3b1f837feaacd16d97854402355@%3Ccommits.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/redef0fb5474fd686781007de9ddb852b24f1b04131a248d9a4789183@%3Cnotifications.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/r101f82d8f3b5af0bf79aecbd5b2dd3b404f6bb51d1a54c2c3d29bed9@%3Cnotifications.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/re4b0141939370304d676fe23774d0c6fbc584b648919825402d0cb39@%3Cnotifications.zookeeper.apache.org%3E', 'https://github.com/advisories/GHSA-f256-j965-7f32', 'https://lists.apache.org/thread.html/r2732aa3884cacfecac4c54cfaa77c279ba815cad44b464a567216f83@%3Cissues.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/r855b4b6814ac829ce2d48dd9d8138d07f33387e710de798ee92c011e@%3Cissues.flink.apache.org%3E', 'https://lists.apache.org/thread.html/r5f2f120b2b8d099226473db1832ffb4d7c1d6dc2d228a164bf293a8e@%3Cissues.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/rdd5715f3ee5e3216d5e0083a07994f67da6dbb9731ce9e7a6389b18e@%3Ccommits.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/r1b3cb056364794f919aaf26ceaf7423de64e7fdd05a914066e7d5219@%3Cissues.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/rf38e4dcdefc7c59f7ba0799a399d6d6e37b555d406a1dfc2fcbf0b35@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/rcae42fba06979934208bbd515584b241d3ad01d1bb8b063512644362@%3Cdev.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/r9ec78dc409f3f1edff88f21cab53737f36aad46f582a9825389092e0@%3Cissues.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/rbde2f13daf4911504f0eaea43eee4f42555241b5f6d9d71564b6c5fa@%3Cjira.kafka.apache.org%3E', 'https://lists.apache.org/thread.html/r7879ddcb990c835c6b246654770d836f9d031dee982be836744e50ed@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/r0ca82fec33334e571fe5b388272260778883e307e15415d7b1443de2@%3Cissues.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/r5cbea8614812289a9b98d0cfc54b47f54cef424ac98d5e315b791795@%3Cnotifications.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/rd4a6b7dec38ea6cd28b6f94bd4b312629a52b80be3786d5fb0e474bc@%3Cissues.kudu.apache.org%3E', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://lists.apache.org/thread.html/re9e6ed60941da831675de2f8f733c026757fb4fa28a7b6c9f3dfb575@%3Cdev.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/re1911e05c08f3ec2bab85744d788773519a0afb27272a31ac2a0b4e8@%3Cnotifications.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/r0b09f3e31e004fe583f677f7afa46bd30110904576c13c5ac818ac2c@%3Cissues.flink.apache.org%3E', 'https://lists.apache.org/thread.html/re39391adcb863f0e9f3f15e7986255948f263f02e4700b82453e7102@%3Cissues.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/ra64d56a8a331ffd7bdcd24a9aaaeeedeacd5d639f5a683389123f898@%3Cdev.flink.apache.org%3E', 'https://lists.apache.org/thread.html/r6dac9bd799ceac499c7a7e152a9b0dc7f2fe7f89ec5605d129bb047b@%3Cissues.zookeeper.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21409', 'https://lists.apache.org/thread.html/r823d4b27fcba8dad5fe945bdefce3ca5a0031187966eb6ef3cc22ba9@%3Cissues.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/rafc77f9f03031297394f3d372ccea751b23576f8a2ae9b6b053894c5@%3Cissues.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/r602e98daacc98934f097f07f2eed6eb07c18bfc1949c8489dc7bfcf5@%3Cissues.flink.apache.org%3E', 'https://lists.apache.org/thread.html/ra655e5cec74d1ddf62adacb71d398abd96f3ea2c588f6bbf048348eb@%3Cissues.kudu.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://lists.apache.org/thread.html/r4b8be87acf5b9c098a2ee350b5ca5716fe7afeaf0a21a4ee45a90687@%3Cissues.zookeeper.apache.org%3E', 'https://www.debian.org/security/2021/dsa-4885', 'https://lists.apache.org/thread.html/r70c3a7bfa904f06a1902f4df20ee26e4f09a46b8fd3eb304dc57a2de@%3Cdev.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/rf148b2bf6c2754153a8629bc7495e216bd0bd4c915695486542a10b4@%3Cnotifications.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/r5baac01f9e06c40ff7aab209d5751b3b58802c63734e33324b70a06a@%3Cissues.flink.apache.org%3E', 'https://lists.apache.org/thread.html/r31044fb995e894749cb821c6fe56f487c16a97028e6e360e59f09d58@%3Cissues.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/rba2a9ef1d0af882ab58fadb336a58818495245dda43d32a7d7837187@%3Cissues.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/rf521ff2be2e2dd38984174d3451e6ee935c845948845c8fccd86371d@%3Cissues.zookeeper.apache.org%3E', 'https://github.com/netty/netty/security/advisories/GHSA-f256-j965-7f32', 'https://lists.apache.org/thread.html/r4a98827bb4a7edbd69ef862f2351391845697c40711820d10df52ca5@%3Ccommits.zookeeper.apache.org%3E', 'https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-21295', 'https://lists.apache.org/thread.html/r584cf871f188c406d8bd447ff4e2fd9817fca862436c064d0951a071@%3Ccommits.pulsar.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://lists.apache.org/thread.html/rf934292a4a1c189827f625d567838d2c1001e4739b158638d844105b@%3Cissues.kudu.apache.org%3E', 'https://lists.apache.org/thread.html/r61564d86a75403b854cdafee67fc69c8b88c5f6802c2c838f4282cc8@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/r967002f0939e69bdec58f070735a19dd57c1f2b8f817949ca17cddae@%3Cissues.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/r4ea2f1a9d79d4fc1896e085f31fb60a21b1770d0a26a5250f849372d@%3Cissues.kudu.apache.org%3E', 'https://lists.apache.org/thread.html/rd8f72411fb75b98d366400ae789966373b5c3eb3f511e717caf3e49e@%3Cissues.flink.apache.org%3E', 'https://lists.apache.org/thread.html/ra66e93703e3f4bd31bdfd0b6fb0c32ae96b528259bb1aa2b6d38e401@%3Cissues.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/r7b54563abebe3dbbe421e1ba075c2030d8d460372f8c79b7789684b6@%3Cissues.zookeeper.apache.org%3E', 'https://security.netapp.com/advisory/ntap-20210604-0003/', 'https://lists.apache.org/thread.html/rac8cf45a1bab9ead5c9a860cbadd6faaeb7792203617b6ec3874736d@%3Cissues.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/r9fe840c36b74f92b8d4a089ada1f9fd1d6293742efa18b10e06b66d2@%3Ccommits.zookeeper.apache.org%3E', 'https://github.com/netty/netty/security/advisories/GHSA-wm47-8v5p-wjpj', 'https://lists.apache.org/thread.html/raa413040db6d2197593cc03edecfd168732e697119e6447b0a25d525@%3Cissues.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/rca0978b634a0c3ebee4126ec29c7f570b165fae3f8f3658754c1cbd3@%3Cissues.kudu.apache.org%3E', 'https://lists.apache.org/thread.html/rdd206d9dd7eb894cc089b37fe6edde2932de88d63a6d8368b44f5101@%3Ccommits.zookeeper.apache.org%3E', 'https://github.com/netty/netty/commit/b0fa4d5aab4215f3c22ce6123dd8dd5f38dc0432', 'https://lists.apache.org/thread.html/re7c69756a102bebce8b8681882844a53e2f23975a189363e68ad0324@%3Cissues.flink.apache.org%3E', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/netty/netty/commit/b0fa4d5aab4215f3c22ce6123dd8dd5f38dc0432'} | {'https://github.com/netty/netty/commit/b0fa4d5aab4215f3c22ce6123dd8dd5f38dc0432'} |
GHSA | GHSA-w4fj-ccr6-7pcp | Insertion of Sensitive Information into Log File in Apache NiFi | An information disclosure vulnerability was found in Apache NiFi 1.10.0. The sensitive parameter parser would log parsed values for debugging purposes. This would expose literal values entered in a sensitive property when no parameter was present. | {'CVE-2020-1928'} | 2022-01-06T20:40:56Z | 2022-01-06T20:40:56Z | MODERATE | 5.3 | {'CWE-200', 'CWE-532'} | {'https://lists.apache.org/thread.html/rd50baccd1bbb96c2327d5a8caa25a49692b3d68d96915bd1cfbb9f8b@%3Cusers.tomcat.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-1928', 'https://github.com/apache/nifi/commit/42cb6e84898e66672878f61f99543d6af3c0a567', 'https://nifi.apache.org/security.html#CVE-2020-1928', 'https://lists.apache.org/thread.html/r17aaa3a05b5b7fe9075613dd0c681efa60a4f8c8fbad152c61371b6e@%3Cusers.tomcat.apache.org%3E', 'https://lists.apache.org/thread.html/r38a5b7943b9a62ecb853acc22ef08ff586a7b3c66e08f949f0396ab1@%3Cusers.tomcat.apache.org%3E', 'https://github.com/advisories/GHSA-w4fj-ccr6-7pcp'} | null | {'https://github.com/apache/nifi/commit/42cb6e84898e66672878f61f99543d6af3c0a567'} | {'https://github.com/apache/nifi/commit/42cb6e84898e66672878f61f99543d6af3c0a567'} |
GHSA | GHSA-wjx2-7hqq-8h7m | rails_admin ruby gem XSS vulnerability | RailsAdmin (aka rails_admin) before 1.4.3 and 2.x before 2.0.2 allows XSS via nested forms. | {'CVE-2020-36190'} | 2021-01-19T18:16:40Z | 2021-01-14T19:17:16Z | MODERATE | 0 | {'CWE-79'} | {'https://github.com/sferik/rails_admin/commit/d72090ec6a07c3b9b7b48ab50f3d405f91ff4375', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/rails_admin/CVE-2020-36190.yml', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36190', 'https://github.com/sferik/rails_admin/blob/master/README.md', 'https://github.com/advisories/GHSA-wjx2-7hqq-8h7m', 'https://github.com/sferik/rails_admin/compare/v1.4.2...v1.4.3'} | null | {'https://github.com/sferik/rails_admin/commit/d72090ec6a07c3b9b7b48ab50f3d405f91ff4375'} | {'https://github.com/sferik/rails_admin/commit/d72090ec6a07c3b9b7b48ab50f3d405f91ff4375'} |
GHSA | GHSA-44r7-7p62-q3fr | Insecure generation of random numbers | The miekg Go DNS package before 1.1.25, as used in CoreDNS before 1.6.6 and other products, improperly generates random numbers because math/rand is used. The TXID becomes predictable, leading to response forgeries. | {'CVE-2019-19794'} | 2021-05-18T21:09:13Z | 2021-05-18T21:09:13Z | MODERATE | 5.9 | {'CWE-338', 'CWE-330'} | {'https://github.com/miekg/dns/compare/v1.1.24...v1.1.25', 'https://github.com/advisories/GHSA-44r7-7p62-q3fr', 'https://github.com/miekg/dns/issues/1043', 'https://github.com/miekg/dns/pull/1044', 'https://nvd.nist.gov/vuln/detail/CVE-2019-19794', 'https://github.com/miekg/dns/commit/8ebf2e419df7857ac8919baa05248789a8ffbf33', 'https://github.com/coredns/coredns/issues/3547', 'https://github.com/coredns/coredns/issues/3519'} | null | {'https://github.com/miekg/dns/commit/8ebf2e419df7857ac8919baa05248789a8ffbf33'} | {'https://github.com/miekg/dns/commit/8ebf2e419df7857ac8919baa05248789a8ffbf33'} |
GHSA | GHSA-57j2-w4cx-62h2 | Deeply nested json in jackson-databind | jackson-databind is a data-binding package for the Jackson Data Processor. jackson-databind allows a Java stack overflow exception and denial of service via a large depth of nested objects. | {'CVE-2020-36518'} | 2022-03-28T19:57:53Z | 2022-03-12T00:00:36Z | HIGH | 7.5 | {'CWE-787'} | {'https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.13', 'https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.12', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36518', 'https://github.com/advisories/GHSA-57j2-w4cx-62h2', 'https://github.com/FasterXML/jackson-databind/issues/2816', 'https://github.com/FasterXML/jackson-databind/commit/fcfc4998ec23f0b1f7f8a9521c2b317b6c25892b'} | null | {'https://github.com/FasterXML/jackson-databind/commit/fcfc4998ec23f0b1f7f8a9521c2b317b6c25892b'} | {'https://github.com/FasterXML/jackson-databind/commit/fcfc4998ec23f0b1f7f8a9521c2b317b6c25892b'} |
GHSA | GHSA-jc8m-cxhj-668x | Improper Restriction of Excessive Authentication Attempts in Sorcery | ### Impact
Brute force vulnerability when using password authentication via Sorcery. The brute force protection submodule will prevent a brute force attack for the defined lockout period, but once expired protection will not be re-enabled until a user or malicious actor logs in successfully. This does not affect users that do not use the built-in brute force protection submodule, nor users that use permanent account lockout.
### Patches
Patched as of version `0.15.0`.
### Workarounds
Currently no workarounds, other than monkey patching the authenticate method provided by Sorcery or upgrading to version `0.15.0`. | {'CVE-2020-11052'} | 2022-04-19T19:02:25Z | 2020-05-07T21:16:46Z | HIGH | 8.3 | {'CWE-307'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-11052', 'https://github.com/Sorcery/sorcery/issues/231', 'https://github.com/Sorcery/sorcery/pull/235', 'https://github.com/Sorcery/sorcery/commit/0f116d223826895a73b12492f17486e5d54ab7a7', 'https://github.com/advisories/GHSA-jc8m-cxhj-668x', 'https://github.com/Sorcery/sorcery/security/advisories/GHSA-jc8m-cxhj-668x'} | null | {'https://github.com/Sorcery/sorcery/commit/0f116d223826895a73b12492f17486e5d54ab7a7'} | {'https://github.com/Sorcery/sorcery/commit/0f116d223826895a73b12492f17486e5d54ab7a7'} |
GHSA | GHSA-m648-33qf-v3gp | CHECK-fail in LSTM with zero-length input in TensorFlow | ### Impact
Running an LSTM/GRU model where the LSTM/GRU layer receives an input with zero-length results in a `CHECK` failure when using the CUDA backend.
This can result in a query-of-death vulnerability, via denial of service, if users can control the input to the layer.
### Patches
We have patched the issue in GitHub commit [14755416e364f17fb1870882fa778c7fec7f16e3](https://github.com/tensorflow/tensorflow/commit/14755416e364f17fb1870882fa778c7fec7f16e3) and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.
Since this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive.
### 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. | {'CVE-2020-26270'} | 2021-01-07T22:35:25Z | 2020-12-10T19:07:31Z | LOW | 4.4 | {'CWE-20'} | {'https://github.com/advisories/GHSA-m648-33qf-v3gp', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-m648-33qf-v3gp', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26270', 'https://github.com/tensorflow/tensorflow/commit/14755416e364f17fb1870882fa778c7fec7f16e3'} | null | {'https://github.com/tensorflow/tensorflow/commit/14755416e364f17fb1870882fa778c7fec7f16e3'} | {'https://github.com/tensorflow/tensorflow/commit/14755416e364f17fb1870882fa778c7fec7f16e3'} |
GHSA | GHSA-gh6x-4whr-2qv4 | Null pointer dereference and heap OOB read in operations restoring tensors | ### Impact
When restoring tensors via raw APIs, if the tensor name is not provided, TensorFlow can be tricked into dereferencing a null pointer:
```python
import tensorflow as tf
tf.raw_ops.Restore(
file_pattern=['/tmp'],
tensor_name=[],
default_value=21,
dt=tf.int,
preferred_shard=1)
```
The same undefined behavior can be triggered by `tf.raw_ops.RestoreSlice`:
```python
import tensorflow as tf
tf.raw_ops.RestoreSlice(
file_pattern=['/tmp'],
tensor_name=[],
shape_and_slice='2',
dt=inp.array([tf.int]),
preferred_shard=1)
```
Alternatively, attackers can read memory outside the bounds of heap allocated data by providing some tensor names but not enough for a successful restoration:
```python
import tensorflow as tf
tf.raw_ops.Restore(
file_pattern=['/tmp'],
tensor_name=['x'],
default_value=21,
dt=tf.int,
preferred_shard=42)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/save_restore_tensor.cc#L158-L159) retrieves the tensor list corresponding to the `tensor_name` user controlled input and immediately retrieves the tensor at the restoration index (controlled via `preferred_shard` argument). This occurs without validating that the provided list has enough values.
If the list is empty this results in dereferencing a null pointer (undefined behavior). If, however, the list has some elements, if the restoration index is outside the bounds this results in heap OOB read.
### Patches
We have patched the issue in GitHub commit [9e82dce6e6bd1f36a57e08fa85af213e2b2f2622](https://github.com/tensorflow/tensorflow/commit/9e82dce6e6bd1f36a57e08fa85af213e2b2f2622).
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-37639'} | 2022-04-26T18:06:27Z | 2021-08-25T14:44:05Z | HIGH | 8.4 | {'CWE-476', 'CWE-125'} | {'https://github.com/advisories/GHSA-gh6x-4whr-2qv4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37639', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-gh6x-4whr-2qv4', 'https://github.com/tensorflow/tensorflow/commit/9e82dce6e6bd1f36a57e08fa85af213e2b2f2622'} | null | {'https://github.com/tensorflow/tensorflow/commit/9e82dce6e6bd1f36a57e08fa85af213e2b2f2622'} | {'https://github.com/tensorflow/tensorflow/commit/9e82dce6e6bd1f36a57e08fa85af213e2b2f2622'} |
GHSA | GHSA-vhfp-9wvj-gwvg | XML External Entity vulnerability in MODX CMS | A XML External Entity (XXE) vulnerability was discovered in the modRestServiceRequest component in MODX CMS 2.7.3 which can lead to an information disclosure or denial of service (DOS). | {'CVE-2020-25911'} | 2021-11-03T14:52:00Z | 2021-11-01T19:19:43Z | CRITICAL | 9.1 | {'CWE-611'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-25911', 'https://github.com/advisories/GHSA-vhfp-9wvj-gwvg', 'https://github.com/dahua966/Vul_disclose/blob/main/XXE_modxcms.md', 'https://github.com/modxcms/revolution/pull/15238/commits/1b7ffe02df30f05dbf67dd15e4d8101687c1585a', 'https://github.com/modxcms/revolution/issues/15237', 'https://github.com/modxcms/revolution/pull/15238'} | null | {'https://github.com/modxcms/revolution/pull/15238/commits/1b7ffe02df30f05dbf67dd15e4d8101687c1585a'} | {'https://github.com/modxcms/revolution/pull/15238/commits/1b7ffe02df30f05dbf67dd15e4d8101687c1585a'} |
GHSA | GHSA-r2j6-p67h-q639 | Secret disclosure when containing characters that become URI encoded | ### Impact
Secrets that would normally be masked by `semantic-release` can be accidentally disclosed if they contain characters that become encoded when included in a URL.
### Patches
Fixed in v17.2.3
### Workarounds
Secrets that do not contain characters that become encoded when included in a URL are already masked properly. | {'CVE-2020-26226'} | 2022-04-19T19:02:39Z | 2020-11-18T21:19:14Z | HIGH | 8.1 | {'CWE-116'} | {'https://github.com/advisories/GHSA-r2j6-p67h-q639', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26226', 'https://github.com/semantic-release/semantic-release/commit/ca90b34c4a9333438cc4d69faeb43362bb991e5a', 'https://github.com/semantic-release/semantic-release/security/advisories/GHSA-r2j6-p67h-q639'} | null | {'https://github.com/semantic-release/semantic-release/commit/ca90b34c4a9333438cc4d69faeb43362bb991e5a'} | {'https://github.com/semantic-release/semantic-release/commit/ca90b34c4a9333438cc4d69faeb43362bb991e5a'} |
GHSA | GHSA-4vf2-4xcg-65cx | Division by 0 in `Conv2D` | ### Impact
An attacker can trigger a division by 0 in `tf.raw_ops.Conv2D`:
```python
import tensorflow as tf
input = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)
filter = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)
strides = [1, 1, 1, 1]
padding = "SAME"
tf.raw_ops.Conv2D(input=input, filter=filter, strides=strides, padding=padding)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/988087bd83f144af14087fe4fecee2d250d93737/tensorflow/core/kernels/conv_ops.cc#L261-L263) does a division by a quantity that is controlled by the caller:
```cc
const int64 patch_depth = filter.dim_size(2);
if (in_depth % patch_depth != 0) { ... }
```
### Patches
We have patched the issue in GitHub commit [b12aa1d44352de21d1a6faaf04172d8c2508b42b](https://github.com/tensorflow/tensorflow/commit/b12aa1d44352de21d1a6faaf04172d8c2508b42b).
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-29526'} | 2021-05-21T14:21:55Z | 2021-05-21T14:21:55Z | LOW | 2.5 | {'CWE-369'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29526', 'https://github.com/tensorflow/tensorflow/commit/b12aa1d44352de21d1a6faaf04172d8c2508b42b', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-4vf2-4xcg-65cx', 'https://github.com/advisories/GHSA-4vf2-4xcg-65cx'} | null | {'https://github.com/tensorflow/tensorflow/commit/b12aa1d44352de21d1a6faaf04172d8c2508b42b'} | {'https://github.com/tensorflow/tensorflow/commit/b12aa1d44352de21d1a6faaf04172d8c2508b42b'} |
GHSA | GHSA-cxg7-84wp-8pcq | yetiforcecrm is vulnerable to Business Logic Errors | yetiforcecrm is vulnerable to Business Logic Errors. | {'CVE-2021-4117'} | 2022-01-03T15:47:43Z | 2021-12-16T21:01:07Z | HIGH | 7.7 | null | {'https://github.com/yetiforcecompany/yetiforcecrm/commit/8dccd93442725f245b4b71986bbe6f4f48639239', 'https://huntr.dev/bounties/0b81e572-bdc9-4caf-aa02-81f3c7ad7c0a', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4117', 'https://github.com/advisories/GHSA-cxg7-84wp-8pcq'} | null | {'https://github.com/yetiforcecompany/yetiforcecrm/commit/8dccd93442725f245b4b71986bbe6f4f48639239'} | {'https://github.com/yetiforcecompany/yetiforcecrm/commit/8dccd93442725f245b4b71986bbe6f4f48639239'} |
GHSA | GHSA-5rg2-6qr5-2xp8 | Cross-site Scripting in snipe-it | snipe-it is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') | {'CVE-2021-3863'} | 2021-10-25T20:08:18Z | 2021-10-21T17:49:18Z | MODERATE | 5.5 | {'CWE-79'} | {'https://github.com/snipe/snipe-it/releases/tag/v5.3.0', 'https://github.com/snipe/snipe-it/commit/fc5efd857f61f7e45c61db567bb66612bcb53128', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3863', 'https://github.com/advisories/GHSA-5rg2-6qr5-2xp8', 'https://huntr.dev/bounties/1dbc8d79-1b53-44a3-a576-faec78f29ba0'} | null | {'https://github.com/snipe/snipe-it/commit/fc5efd857f61f7e45c61db567bb66612bcb53128'} | {'https://github.com/snipe/snipe-it/commit/fc5efd857f61f7e45c61db567bb66612bcb53128'} |
GHSA | GHSA-8jpx-m2wh-2v34 | Remote Code Execution (RCE) vulnerability in dropwizard-validation | ### Summary
A server-side template injection was identified in the self-validating ([`@SelfValidating`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/SelfValidating.html)) feature of **dropwizard-validation** enabling attackers to inject arbitrary Java EL expressions, leading to Remote Code Execution (RCE) vulnerability.
If you're using a self-validating bean (via [`@SelfValidating`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/SelfValidating.html)), an upgrade to Dropwizard 1.3.21/2.0.3 or later is strongly recommended.
The changes introduced in Dropwizard 1.3.19 and 2.0.2 (see [GHSA-3mcp-9wr4-cjqf](https://github.com/dropwizard/dropwizard/security/advisories/GHSA-3mcp-9wr4-cjqf)/[CVE-2020-5245](https://github.com/advisories/GHSA-3mcp-9wr4-cjqf)) unfortunately didn't fix the underlying issue completely.
### Impact
This issue may allow Remote Code Execution (RCE), allowing to run arbitrary code on the host system (with the privileges of the Dropwizard service account privileges) by injecting arbitrary [Java Expression Language (EL)](https://docs.jboss.org/hibernate/validator/6.1/reference/en-US/html_single/#section-interpolation-with-message-expressions) expressions when using the self-validating feature ([`@SelfValidating`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/SelfValidating.html), [`@SelfValidation`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/SelfValidation.html)) in **dropwizard-validation**.
### Patches
The issue has been fixed in **dropwizard-validation** **1.3.21** and **2.0.3** or later. We strongly recommend upgrading to one of these versions.
The evaluation of EL expressions has been disabled by default now.
In order to use some interpolation in the violation messages added to [`ViolationCollector`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/ViolationCollector.html), it has to be explicitly allowed by setting [`SelfValidating#escapeExpressions()`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/SelfValidating.html#escapeExpressions--) to `false`.
It is also recommended to use the `addViolation` methods supporting message parameters instead of EL expressions introduced in Dropwizard 1.3.21 and 2.0.3:
* [`ViolationCollector#addViolation(String, Map<String, Object>`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/ViolationCollector.html#addViolation-java.lang.String-java.util.Map-)
* [`ViolationCollector#addViolation(String, String, Map<String, Object>`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/ViolationCollector.html#addViolation-java.lang.String-java.lang.String-java.util.Map-)
* [`ViolationCollector#addViolation(String, String, Integer, Map<String, Object>`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/ViolationCollector.html#addViolation-java.lang.String-java.lang.Integer-java.lang.String-java.util.Map-)
* [`ViolationCollector#addViolation(String, String, String, Map<String, Object>`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/ViolationCollector.html#addViolation-java.lang.String-java.lang.String-java.lang.String-java.util.Map-)
### Workarounds
If you are not able to upgrade to one of the aforementioned versions of **dropwizard-validation** but still want to use the [`@SelfValidating`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.2/io/dropwizard/validation/selfvalidating/SelfValidating.html) feature, make sure to properly sanitize any message you're adding to the [`ViolationCollector`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/ViolationCollector.html) in the method annotated with [`@SelfValidation`](https://javadoc.io/static/io.dropwizard/dropwizard-project/2.0.3/io/dropwizard/validation/selfvalidating/SelfValidation.html).
Example:
```java
@SelfValidation
public void validateFullName(ViolationCollector col) {
if (fullName.contains("_")) {
// Sanitize fullName variable by escaping relevant characters such as "$"
col.addViolation("Full name contains invalid characters: " + sanitizeJavaEl(fullName));
}
}
```
See also:
https://github.com/dropwizard/dropwizard/blob/v2.0.3/dropwizard-validation/src/main/java/io/dropwizard/validation/InterpolationHelper.java
### References
* https://github.com/dropwizard/dropwizard/security/advisories/GHSA-3mcp-9wr4-cjqf
* https://github.com/dropwizard/dropwizard/pull/3208
* https://github.com/dropwizard/dropwizard/pull/3209
* https://docs.jboss.org/hibernate/validator/6.1/reference/en-US/html_single/#section-hibernateconstraintvalidatorcontext
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [dropwizard/dropwizard](https://github.com/dropwizard/dropwizard/issues/new)
* Start a discussion on the [dropwizard-dev mailing list](https://groups.google.com/forum/#!forum/dropwizard-dev)
### Security contact
If you want to responsibly disclose a security issue in Dropwizard or one of its official modules, please contact us via the published channels in our [security policy](https://github.com/dropwizard/dropwizard/security/policy):
https://github.com/dropwizard/dropwizard/security/policy#reporting-a-vulnerability | {'CVE-2020-11002'} | 2022-04-19T19:02:55Z | 2020-04-10T18:42:20Z | HIGH | 8 | {'CWE-74'} | {'https://docs.jboss.org/hibernate/validator/6.1/reference/en-US/html_single/#section-hibernateconstraintvalidatorcontext', 'https://github.com/dropwizard/dropwizard/security/policy#reporting-a-vulnerability', 'https://github.com/dropwizard/dropwizard/pull/3209', 'https://github.com/dropwizard/dropwizard/pull/3208', 'https://github.com/advisories/GHSA-8jpx-m2wh-2v34', 'https://github.com/dropwizard/dropwizard/security/advisories/GHSA-8jpx-m2wh-2v34', 'https://github.com/dropwizard/dropwizard/security/advisories/GHSA-3mcp-9wr4-cjqf', 'https://github.com/dropwizard/dropwizard/commit/d5a512f7abf965275f2a6b913ac4fe778e424242', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11002'} | null | {'https://github.com/dropwizard/dropwizard/commit/d5a512f7abf965275f2a6b913ac4fe778e424242'} | {'https://github.com/dropwizard/dropwizard/commit/d5a512f7abf965275f2a6b913ac4fe778e424242'} |
GHSA | GHSA-6973-94v8-5mgw | Out-of-bounds write | A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0989, CVE-2019-0992, CVE-2019-0993, CVE-2019-1002, CVE-2019-1003, CVE-2019-1024, CVE-2019-1051, CVE-2019-1052. | {'CVE-2019-0991'} | 2021-03-29T20:57:42Z | 2021-03-29T20:57:42Z | HIGH | 7.5 | {'CWE-787'} | {'https://github.com/chakra-core/ChakraCore/commit/1caa4118796d33513bc40ce894c053a92de98abb', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0991', 'https://github.com/advisories/GHSA-6973-94v8-5mgw', 'https://github.com/chakra-core/ChakraCore/commit/3d6226cc2d1077537220361c82e34a362c6c76ee', 'https://nvd.nist.gov/vuln/detail/CVE-2019-0991'} | null | {'https://github.com/chakra-core/ChakraCore/commit/3d6226cc2d1077537220361c82e34a362c6c76ee', 'https://github.com/chakra-core/ChakraCore/commit/1caa4118796d33513bc40ce894c053a92de98abb'} | {'https://github.com/chakra-core/ChakraCore/commit/3d6226cc2d1077537220361c82e34a362c6c76ee', 'https://github.com/chakra-core/ChakraCore/commit/1caa4118796d33513bc40ce894c053a92de98abb'} |
GHSA | GHSA-q7q9-w24q-cpgh | Cross-site Scripting (XSS) in Apache Ambari Views | A cross-site scripting issue was found in Apache Ambari Views. This was addressed in Apache Ambari 2.7.4. | {'CVE-2020-1936'} | 2022-01-06T20:35:22Z | 2022-01-06T20:35:22Z | MODERATE | 6.1 | {'CWE-79'} | {'http://www.openwall.com/lists/oss-security/2021/03/02/1', 'https://github.com/advisories/GHSA-q7q9-w24q-cpgh', 'https://issues.apache.org/jira/browse/AMBARI-25329', 'https://github.com/apache/ambari/pull/3040', 'https://github.com/apache/ambari/pull/3040/commits/a9cfdb9dcce63a3494c07c81ebb2cf8da218a210', 'https://nvd.nist.gov/vuln/detail/CVE-2020-1936', 'https://lists.apache.org/thread.html/946a9d72e664ad8bc592168d9a2fed88100c6e9f1bdfea08e91a3184%40%3Cuser.ambari.apache.org%3E'} | null | {'https://github.com/apache/ambari/pull/3040/commits/a9cfdb9dcce63a3494c07c81ebb2cf8da218a210'} | {'https://github.com/apache/ambari/pull/3040/commits/a9cfdb9dcce63a3494c07c81ebb2cf8da218a210'} |
GHSA | GHSA-4rq4-32rv-6wp6 | Improper Privilege Management in shelljs | shelljs is vulnerable to Improper Privilege Management | {'CVE-2022-0144'} | 2022-01-21T23:37:28Z | 2022-01-21T23:37:28Z | HIGH | 7.1 | {'CWE-269'} | {'https://github.com/shelljs/shelljs/commit/d919d22dd6de385edaa9d90313075a77f74b338c', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0144', 'https://huntr.dev/bounties/50996581-c08e-4eed-a90e-c0bac082679c', 'https://github.com/advisories/GHSA-4rq4-32rv-6wp6'} | null | {'https://github.com/shelljs/shelljs/commit/d919d22dd6de385edaa9d90313075a77f74b338c'} | {'https://github.com/shelljs/shelljs/commit/d919d22dd6de385edaa9d90313075a77f74b338c'} |
GHSA | GHSA-wf43-55jj-vwq8 | DNS Rebinding in etcd | DNS rebinding vulnerability found in etcd 3.3.1 and earlier. An attacker can control his DNS records to direct to localhost, and trick the browser into sending requests to localhost (or any other address). | {'CVE-2018-1099'} | 2022-04-12T22:12:47Z | 2022-02-15T01:57:18Z | MODERATE | 5.5 | {'CWE-350', 'CWE-20'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JX7QTIT465BQGRGNCE74RATRQLKT2QE4/', 'https://bugzilla.redhat.com/show_bug.cgi?id=1552717', 'https://nvd.nist.gov/vuln/detail/CVE-2018-1099', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UPGYHMSKDPW5GAMI7BEP3XQRVRLLBJKS/', 'https://github.com/coreos/etcd/commit/a7e5790c82039945639798ae9a3289fe787f5e56', 'https://github.com/coreos/etcd/issues/9353', 'https://github.com/advisories/GHSA-wf43-55jj-vwq8'} | null | {'https://github.com/coreos/etcd/commit/a7e5790c82039945639798ae9a3289fe787f5e56'} | {'https://github.com/coreos/etcd/commit/a7e5790c82039945639798ae9a3289fe787f5e56'} |
GHSA | GHSA-3p3g-vpw6-4w66 | Authentication Bypass in hydra | ### Impact
"When using client authentication method "private_key_jwt" [1], OpenId specification says the following about assertion `jti`:"
> A unique identifier for the token, which can be used to prevent reuse of the token. These tokens MUST only be used once, unless conditions for reuse were negotiated between the parties
"Hydra does not seem to check the uniqueness of this `jti` value. Here is me sending the same token request twice, hence with the same `jti` assertion, and getting two access tokens:"
```
$ curl --insecure --location --request POST 'https://localhost/_/oauth2/token' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'grant_type=client_credentials' \
--data-urlencode 'client_id=c001d00d-5ecc-beef-ca4e-b00b1e54a111' \
--data-urlencode 'scope=application openid' \
--data-urlencode 'client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer' \
--data-urlencode 'client_assertion=eyJhb [...] jTw'
{"access_token":"zeG0NoqOtlACl8q5J6A-TIsNegQRRUzqLZaYrQtoBZQ.VR6iUcJQYp3u_j7pwvL7YtPqGhtyQe5OhnBE2KCp5pM","expires_in":3599,"scope":"application openid","token_type":"bearer"}⏎ ~$ curl --insecure --location --request POST 'https://localhost/_/oauth2/token' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'grant_type=client_credentials' \
--data-urlencode 'client_id=c001d00d-5ecc-beef-ca4e-b00b1e54a111' \
--data-urlencode 'scope=application openid' \
--data-urlencode 'client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer' \
--data-urlencode 'client_assertion=eyJhb [...] jTw'
{"access_token":"wOYtgCLxLXlELORrwZlmeiqqMQ4kRzV-STU2_Sollas.mwlQGCZWXN7G2IoegUe1P0Vw5iGoKrkOzOaplhMSjm4","expires_in":3599,"scope":"application openid","token_type":"bearer"}
```
### Severity
"We rate the severity as medium because the following reasons make it hard to replay tokens without the patch:"
- TLS protects against MITM which makes it difficult to intercept valid tokens for replay attacks
- The expiry time of the JWT gives only a short window of opportunity where it could be replayed
### Patches
This will be patched with v1.4.0+oryOS.17
### Workarounds
Two workarounds have been identified:
- Do not allow clients to use `private_key_jwt`
- Use short expiry times for the JWTs
### Upstream
This issue will be resolved in the upstream repository https://github.com/ory/fosite | {'CVE-2020-5300'} | 2021-05-27T18:43:22Z | 2021-05-27T18:43:22Z | MODERATE | 5.8 | {'CWE-294'} | {'https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication', 'https://github.com/ory/hydra/releases/tag/v1.4.0', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5300', 'https://github.com/advisories/GHSA-3p3g-vpw6-4w66', 'https://github.com/ory/hydra/commit/700d17d3b7d507de1b1d459a7261d6fb2571ebe3', 'https://github.com/ory/hydra/security/advisories/GHSA-3p3g-vpw6-4w66'} | null | {'https://github.com/ory/hydra/commit/700d17d3b7d507de1b1d459a7261d6fb2571ebe3'} | {'https://github.com/ory/hydra/commit/700d17d3b7d507de1b1d459a7261d6fb2571ebe3'} |
GHSA | GHSA-gcv9-6737-pjqw | SSRF vulnerability in jupyter-server-proxy | ### Impact
**What kind of vulnerability is it?** Server-Side Request Forgery ( SSRF )
**Who is impacted?** Any user deploying Jupyter Server or Notebook with jupyter-proxy-server extension enabled.
A lack of input validation allowed authenticated clients to proxy requests to other hosts, bypassing the `allowed_hosts` check. Because authentication is required, which already grants permissions to make the same requests via kernel or terminal execution, this is considered low to moderate severity.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
Upgrade to 3.2.1, or apply the patch https://github.com/jupyterhub/jupyter-server-proxy/compare/v3.2.0...v3.2.1.patch
### For more information
If you have any questions or comments about this advisory:
* Open a topic [on our forum](https://discourse.jupyter.org)
* Email the Jupyter security team at [security@ipython.org](mailto:security@ipython.org)
| {'CVE-2022-21697'} | 2022-04-19T19:03:20Z | 2022-01-27T16:24:26Z | MODERATE | 6.3 | {'CWE-918'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-21697', 'https://github.com/jupyterhub/jupyter-server-proxy/compare/v3.2.0...v3.2.1.patch', 'https://github.com/jupyterhub/jupyter-server-proxy/security/advisories/GHSA-gcv9-6737-pjqw', 'https://github.com/advisories/GHSA-gcv9-6737-pjqw', 'https://github.com/jupyterhub/jupyter-server-proxy/commit/fd31930bacd12188c448c886e0783529436b99eb'} | null | {'https://github.com/jupyterhub/jupyter-server-proxy/commit/fd31930bacd12188c448c886e0783529436b99eb'} | {'https://github.com/jupyterhub/jupyter-server-proxy/commit/fd31930bacd12188c448c886e0783529436b99eb'} |
GHSA | GHSA-9vh6-qfv6-vcqp | snipe-IT vulnerable to host header injection | Snipe-IT is a free, open-source IT asset/license management systemIn Snipe-IT, versions v3.0-alpha to v5.3.7 are vulnerable to Host Header Injection. By sending a specially crafted host header in the reset password request, it is possible to send password reset links to users which once clicked lead to an attacker controlled server and thus leading to password reset token leak. This can lead to account take over. | {'CVE-2022-23064'} | 2022-05-03T06:29:50Z | 2022-05-03T00:00:43Z | HIGH | 8.8 | {'CWE-74'} | {'https://github.com/snipe/snipe-it/commit/0c4768fd2a11ac26a61814cef23a71061bfd8bcc', 'https://github.com/advisories/GHSA-9vh6-qfv6-vcqp', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23064', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2022-23064'} | null | {'https://github.com/snipe/snipe-it/commit/0c4768fd2a11ac26a61814cef23a71061bfd8bcc'} | {'https://github.com/snipe/snipe-it/commit/0c4768fd2a11ac26a61814cef23a71061bfd8bcc'} |
GHSA | GHSA-gh8j-2pgf-x458 | Infinite Loop in rencode | The rencode package through 1.0.6 for Python allows an infinite loop in typecode decoding (such as via ;\x2f\x7f), enabling a remote attack that consumes CPU and memory. | {'CVE-2021-40839'} | 2022-02-16T22:03:02Z | 2021-09-13T20:05:51Z | HIGH | 7.5 | {'CWE-835'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-40839', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MCLETLGVM5DBX6QNHQFW6TWGO5T3DENY/', 'https://github.com/advisories/GHSA-gh8j-2pgf-x458', 'https://seclists.org/fulldisclosure/2021/Sep/16', 'https://pypi.org/project/rencode/#history', 'https://github.com/aresch/rencode/commit/572ff74586d9b1daab904c6f7f7009ce0143bb75', 'https://github.com/aresch/rencode/pull/29', 'https://security.netapp.com/advisory/ntap-20211008-0001/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BMVQRPDVSVZNGGX57CFKCYT3DEYO4QB6/'} | null | {'https://github.com/aresch/rencode/commit/572ff74586d9b1daab904c6f7f7009ce0143bb75'} | {'https://github.com/aresch/rencode/commit/572ff74586d9b1daab904c6f7f7009ce0143bb75'} |
GHSA | GHSA-c3xm-pvg7-gh7r | mount destinations can be swapped via symlink-exchange to cause mounts outside the rootfs | ### Summary
runc 1.0.0-rc94 and earlier are vulnerable to a symlink exchange attack whereby
an attacker can request a seemingly-innocuous container configuration that
actually results in the host filesystem being bind-mounted into the container
(allowing for a container escape). CVE-2021-30465 has been assigned for this
issue.
An attacker must have the ability to start containers using some kind of custom
volume configuration, and while recommended container hardening mechanisms such
as LSMs (AppArmor/SELinux) and user namespaces will restrict the amount of
damage an attacker could do, they do not block this attack outright. We have a
reproducer using Kubernetes (and the below description mentions
Kubernetes-specific paths), but this is not a Kubernetes-specific issue.
The now-released [runc v1.0.0-rc95][release] contains a fix for this issue, we
recommend users update as soon as possible.
[release]: https://github.com/opencontainers/runc/releases/tag/v1.0.0-rc95
### Details
In circumstances where a container is being started, and runc is mounting
inside a volume shared with another container (which is conducting a
symlink-exchange attack), runc can be tricked into mounting outside of the
container rootfs by swapping the target of a mount with a symlink due to a
time-of-check-to-time-of-use (TOCTTOU) flaw. This is fairly similar in style to
previous TOCTTOU attacks (and is a problem we are working on solving with
libpathrs).
However, this alone is not useful because this happens inside a mount namespace
with `MS_SLAVE` propagation applied to `/` (meaning that the mount doesn't
appear on the host -- it's only a "host-side mount" inside the container's
namespace). To exploit this, you must have additional mount entries in the
configuration that use some subpath of the mounted-over host path as a source
for a subsequent mount.
However, it turns out with some container orchestrators (such as Kubernetes --
though it is very likely that other downstream users of runc could have similar
behaviour be accessible to untrusted users), the existence of additional volume
management infrastructure allows this attack to be applied to gain access to
the host filesystem without requiring the attacker to have completely arbitrary
control over container configuration.
In the case of Kubernetes, this is exploitable by creating a symlink in a
volume to the top-level (well-known) directory where volumes are sourced from
(for instance,
`/var/lib/kubelet/pods/$MY_POD_UID/volumes/kubernetes.io~empty-dir`), and then
using that symlink as the target of a mount. The source of the mount is an
attacker controlled directory, and thus the source directory from which
subsequent mounts will occur is an attacker-controlled directory. Thus the
attacker can first place a symlink to `/` in their malicious source directory
with the name of a volume, and a subsequent mount in the container will
bind-mount `/` into the container.
Applying this attack requires the attacker to start containers with a slightly
peculiar volume configuration (though not explicitly malicious-looking such as
bind-mounting `/` into the container explicitly), and be able to run malicious
code in a container that shares volumes with said volume configuration. It
helps the attacker if the host paths used for volume management are well known,
though this is not a hard requirement.
### Patches
This has been patched in runc 1.0.0-rc95, and users should upgrade as soon as
possible. The patch itself can be found [here](https://github.com/opencontainers/runc/commit/0ca91f44f1664da834bc61115a849b56d22f595f).
### Workarounds
There are no known workarounds for this issue.
However, users who enforce running containers with more confined security
profiles (such as reduced capabilities, not running code as root in the
container, user namespaces, AppArmor/SELinux, and seccomp) will restrict what
an attacker can do in the case of a container breakout -- we recommend users
make use of strict security profiles if possible (most notably user namespaces
-- which can massively restrict the impact a container breakout can have on the
host system).
### References
* [commit](https://github.com/opencontainers/runc/commit/0ca91f44f1664da834bc61115a849b56d22f595f)
* [seclists public disclosure](https://www.openwall.com/lists/oss-security/2021/05/19/2)
### Credit
Thanks to Etienne Champetier for discovering and disclosing this vulnerability,
to Noah Meyerhans for writing the first draft of this patch, and to Samuel Karp
for testing it.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [our issue tracker](https://github.com/opencontainers/runc/issues).
* Email us at <security@opencontainers.org>. | {'CVE-2021-30465'} | 2022-04-19T19:02:53Z | 2021-05-25T18:44:42Z | HIGH | 7.6 | {'CWE-367', 'CWE-22'} | {'https://github.com/advisories/GHSA-c3xm-pvg7-gh7r', 'https://github.com/opencontainers/runc/security/advisories/GHSA-c3xm-pvg7-gh7r', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4HOARVIT47RULTTFWAU7XBG4WY6TDDHV/', 'https://github.com/opencontainers/runc/commit/0ca91f44f1664da834bc61115a849b56d22f595f', 'https://security.netapp.com/advisory/ntap-20210708-0003/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/35ZW6NBZSBH5PWIT7JU4HXOXGFVDCOHH/', 'https://github.com/opencontainers/runc/releases', 'https://nvd.nist.gov/vuln/detail/CVE-2021-30465', 'https://bugzilla.opensuse.org/show_bug.cgi?id=1185405', 'http://www.openwall.com/lists/oss-security/2021/05/19/2'} | null | {'https://github.com/opencontainers/runc/commit/0ca91f44f1664da834bc61115a849b56d22f595f'} | {'https://github.com/opencontainers/runc/commit/0ca91f44f1664da834bc61115a849b56d22f595f'} |
GHSA | GHSA-78cj-fxph-m83p | Regular Expression Denial of Service (ReDoS) in ua-parser-js | ua-parser-js >= 0.7.14, fixed in 0.7.24, uses a regular expression which is vulnerable to denial of service. If an attacker sends a malicious User-Agent header, ua-parser-js will get stuck processing it for an extended period of time. | {'CVE-2021-27292'} | 2021-05-06T16:11:13Z | 2021-05-06T16:11:13Z | HIGH | 7.5 | {'CWE-400'} | {'https://github.com/pygments/pygments/commit/2e7e8c4a7b318f4032493773732754e418279a14', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27292', 'https://gist.github.com/b-c-ds/6941d80d6b4e694df4bc269493b7be76', 'https://github.com/advisories/GHSA-78cj-fxph-m83p', 'https://github.com/faisalman/ua-parser-js/commit/809439e20e273ce0d25c1d04e111dcf6011eb566'} | null | {'https://github.com/pygments/pygments/commit/2e7e8c4a7b318f4032493773732754e418279a14', 'https://github.com/faisalman/ua-parser-js/commit/809439e20e273ce0d25c1d04e111dcf6011eb566'} | {'https://github.com/faisalman/ua-parser-js/commit/809439e20e273ce0d25c1d04e111dcf6011eb566', 'https://github.com/pygments/pygments/commit/2e7e8c4a7b318f4032493773732754e418279a14'} |
GHSA | GHSA-hxxp-6546-wv6r | Improper Restriction of XML External Entity Reference | Jenkins Selenium HTML report Plugin 1.0 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks. | {'CVE-2021-21672'} | 2022-04-19T18:25:32Z | 2021-07-02T18:36:13Z | MODERATE | 4.3 | {'CWE-611'} | {'https://github.com/advisories/GHSA-hxxp-6546-wv6r', 'https://www.jenkins.io/security/advisory/2021-06-30/#SECURITY-2329', 'http://www.openwall.com/lists/oss-security/2021/06/30/1', 'http://www.openwall.com/lists/oss-security/2022/04/14/2', 'https://github.com/jenkinsci/seleniumhtmlreport-plugin/commit/5ca59b8c7d23af4450dc7f19c1b4107d59063ae1', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21672'} | null | {'https://github.com/jenkinsci/seleniumhtmlreport-plugin/commit/5ca59b8c7d23af4450dc7f19c1b4107d59063ae1'} | {'https://github.com/jenkinsci/seleniumhtmlreport-plugin/commit/5ca59b8c7d23af4450dc7f19c1b4107d59063ae1'} |
GHSA | GHSA-p3w3-4ppm-c3f6 | Cross site scripting in FacturaScripts | FacturaScripts prior to version 2022.06 is vulnerable to stored cross-site scripting via upload plugin functionality in zip format. | {'CVE-2022-1514'} | 2022-04-29T21:02:50Z | 2022-04-29T00:00:23Z | CRITICAL | 9 | {'CWE-79'} | {'https://github.com/neorazorx/facturascripts/commit/aa9f28cb86467468f43486b77ddef7ff4d3c687e', 'https://huntr.dev/bounties/4ae2a917-843a-4ae4-8197-8425a596761c', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1514', 'https://github.com/advisories/GHSA-p3w3-4ppm-c3f6'} | null | {'https://github.com/neorazorx/facturascripts/commit/aa9f28cb86467468f43486b77ddef7ff4d3c687e'} | {'https://github.com/neorazorx/facturascripts/commit/aa9f28cb86467468f43486b77ddef7ff4d3c687e'} |
GHSA | GHSA-h56g-v4vp-q9q6 | Cross-site Scripting in calibreweb | calibreweb prior to version 0.6.16 contains a cross-site scripting vulnerability. | {'CVE-2022-0352'} | 2022-02-10T22:40:43Z | 2022-01-29T00:00:41Z | MODERATE | 6.1 | {'CWE-79'} | {'https://huntr.dev/bounties/a577ff17-2ded-4c41-84ae-6ac02440f717', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0352', 'https://github.com/advisories/GHSA-h56g-v4vp-q9q6', 'https://github.com/janeczku/calibre-web/commit/6bf07539788004513c3692c074ebc7ba4ce005e1'} | null | {'https://github.com/janeczku/calibre-web/commit/6bf07539788004513c3692c074ebc7ba4ce005e1'} | {'https://github.com/janeczku/calibre-web/commit/6bf07539788004513c3692c074ebc7ba4ce005e1'} |
GHSA | GHSA-qrpm-p2h7-hrv2 | Exposure of Sensitive Information to an Unauthorized Actor in nanoid | The package nanoid from 3.0.0, before 3.1.31, are vulnerable to Information Exposure via the valueOf() function which allows to reproduce the last id generated. | {'CVE-2021-23566'} | 2022-03-18T13:15:56Z | 2022-01-21T23:57:06Z | MODERATE | 5.5 | {'CWE-200'} | {'https://gist.github.com/artalar/bc6d1eb9a3477d15d2772e876169a444', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-2332550', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23566', 'https://github.com/advisories/GHSA-qrpm-p2h7-hrv2', 'https://github.com/ai/nanoid/pull/328', 'https://snyk.io/vuln/SNYK-JS-NANOID-2332193', 'https://github.com/ai/nanoid/commit/2b7bd9332bc49b6330c7ddb08e5c661833db2575'} | null | {'https://github.com/ai/nanoid/commit/2b7bd9332bc49b6330c7ddb08e5c661833db2575'} | {'https://github.com/ai/nanoid/commit/2b7bd9332bc49b6330c7ddb08e5c661833db2575'} |
GHSA | GHSA-44c6-4v22-4mhx | Regular Expression Denial of Service (ReDOS) | npm `semver-regex` is vulnerable to Inefficient Regular Expression Complexity | {'CVE-2021-3795'} | 2021-09-20T20:42:25Z | 2021-09-20T20:42:25Z | MODERATE | 7.5 | {'CWE-400'} | {'https://github.com/sindresorhus/semver-regex/commit/11c66245f4e1976dccc52977ed183696a21a3fd7', 'https://huntr.dev/bounties/006624e3-35ac-448f-aab9-7b5183f30e28', 'https://github.com/advisories/GHSA-44c6-4v22-4mhx', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3795'} | null | {'https://github.com/sindresorhus/semver-regex/commit/11c66245f4e1976dccc52977ed183696a21a3fd7'} | {'https://github.com/sindresorhus/semver-regex/commit/11c66245f4e1976dccc52977ed183696a21a3fd7'} |
GHSA | GHSA-2v7p-f4qm-r5pc | SQL Injection found in Pimcore | Pimcore is an open source data & experience management platform. A SQL injection was discovered in GridHelperService.php in GitHub repository pimcore/pimcore prior to 10.3.6. | {'CVE-2022-1429'} | 2022-05-03T21:01:42Z | 2022-04-23T00:03:03Z | HIGH | 7.5 | {'CWE-89'} | {'https://huntr.dev/bounties/cfba30b4-85fa-4499-9160-cd6e3119310e', 'https://github.com/pimcore/pimcore/commit/523a735ab94f004459b84ffdfd3db784586bbd82', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1429', 'https://github.com/advisories/GHSA-2v7p-f4qm-r5pc'} | null | {'https://github.com/pimcore/pimcore/commit/523a735ab94f004459b84ffdfd3db784586bbd82'} | {'https://github.com/pimcore/pimcore/commit/523a735ab94f004459b84ffdfd3db784586bbd82'} |
GHSA | GHSA-4c7m-vv47-7c69 | Insecure Permissions in Gogs | In Gogs 0.11.91, MakeEmailPrimary in models/user_mail.go lacks a "not the owner of the email" check. | {'CVE-2020-14958'} | 2021-05-18T20:33:05Z | 2021-05-18T20:33:05Z | MODERATE | 5.3 | {'CWE-281'} | {'https://github.com/advisories/GHSA-4c7m-vv47-7c69', 'https://github.com/gogs/gogs/commit/82ff0c5852f29daa5f95d965fd50665581e7ea3c', 'https://github.com/gogs/gogs/pull/5988', 'https://nvd.nist.gov/vuln/detail/CVE-2020-14958'} | null | {'https://github.com/gogs/gogs/commit/82ff0c5852f29daa5f95d965fd50665581e7ea3c'} | {'https://github.com/gogs/gogs/commit/82ff0c5852f29daa5f95d965fd50665581e7ea3c'} |
GHSA | GHSA-gp4j-w3vj-7299 | Information Exposure in RunC | RunC allowed additional container processes via 'runc exec' to be ptraced by the pid 1 of the container. This allows the main processes of the container, if running as root, to gain access to file-descriptors of these new processes during the initialization and can lead to container escapes or modification of runC state before the process is fully placed inside the container. | {'CVE-2016-9962'} | 2021-12-20T18:21:43Z | 2021-12-20T18:21:43Z | MODERATE | 6.4 | {'CWE-200'} | {'http://seclists.org/fulldisclosure/2017/Jan/29', 'http://seclists.org/fulldisclosure/2017/Jan/21', 'https://access.redhat.com/security/vulnerabilities/cve-2016-9962', 'https://security.gentoo.org/glsa/201701-34', 'https://github.com/opencontainers/runc/commit/50a19c6ff828c58e5dab13830bd3dacde268afe5', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FINGBFMIXBG6B6ZWYH3TMRP5V3PDBNXR/', 'http://www.securityfocus.com/bid/95361', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UVM7FCOQMPKOFLDTUYSS4ES76DDM56VP/', 'https://github.com/opencontainers/runc/commit/5d93fed3d27f1e2bab58bad13b180a7a81d0b378', 'http://rhn.redhat.com/errata/RHSA-2017-0127.html', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-9962', 'https://github.com/docker/docker/releases/tag/v1.12.6', 'https://nvd.nist.gov/vuln/detail/CVE-2016-9962', 'http://rhn.redhat.com/errata/RHSA-2017-0116.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WUQ3MQNEL5IBZZLMLR72Q4YDCL2SCKRK/', 'http://www.securityfocus.com/archive/1/540001/100/0/threaded', 'https://github.com/advisories/GHSA-gp4j-w3vj-7299', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BQAXJMMLRU7DD2IMG47SR2K4BOFFG7FZ/', 'https://bugzilla.suse.com/show_bug.cgi?id=1012568#c6', 'http://rhn.redhat.com/errata/RHSA-2017-0123.html'} | null | {'https://github.com/opencontainers/runc/commit/50a19c6ff828c58e5dab13830bd3dacde268afe5', 'https://github.com/opencontainers/runc/commit/5d93fed3d27f1e2bab58bad13b180a7a81d0b378'} | {'https://github.com/opencontainers/runc/commit/5d93fed3d27f1e2bab58bad13b180a7a81d0b378', 'https://github.com/opencontainers/runc/commit/50a19c6ff828c58e5dab13830bd3dacde268afe5'} |
GHSA | GHSA-jc87-6vpp-7ff3 | Heap buffer overflow in Tensorflow | ### Impact
The `SparseCountSparseOutput` implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the `indices` tensor has the same shape as the `values` one. The values in these tensors are always accessed in parallel:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L193-L195
Thus, a shape mismatch can result in accesses outside the bounds of heap allocated buffers.
### Patches
We have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release.
We recommend users to upgrade to TensorFlow 2.3.1.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability is a variant of [GHSA-p5f8-gfw5-33w4](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4) | {'CVE-2020-15198'} | 2021-08-26T15:11:47Z | 2020-09-25T18:28:22Z | MODERATE | 5.4 | {'CWE-119', 'CWE-122'} | {'https://github.com/advisories/GHSA-jc87-6vpp-7ff3', 'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15198', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-jc87-6vpp-7ff3', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1'} | null | {'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02'} | {'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02'} |
GHSA | GHSA-vjv6-gq77-3mjw | XXE attack in Mapfish Print | ### Impact
A user can do to an XML External Entity (XXE) attack with the provided SDL style.
### Patches
Use version >= 3.24
### Workarounds
No
### References
* https://cwe.mitre.org/data/definitions/611.html
* https://github.com/mapfish/mapfish-print/pull/1397/commits/e1d0527d13db06b2b62ca7d6afb9e97dacd67a0e
### For more information
If you have any questions or comments about this advisory Comment the pull request: https://github.com/mapfish/mapfish-print/pull/1397 | {'CVE-2020-15232'} | 2021-01-07T23:47:51Z | 2020-07-07T16:32:45Z | LOW | 9.3 | {'CWE-611'} | {'https://github.com/advisories/GHSA-vjv6-gq77-3mjw', 'https://github.com/mapfish/mapfish-print/security/advisories/GHSA-vjv6-gq77-3mjw', 'https://github.com/mapfish/mapfish-print/pull/1397/commits/e1d0527d13db06b2b62ca7d6afb9e97dacd67a0e', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15232', 'https://github.com/mapfish/mapfish-print/pull/1397'} | null | {'https://github.com/mapfish/mapfish-print/pull/1397/commits/e1d0527d13db06b2b62ca7d6afb9e97dacd67a0e'} | {'https://github.com/mapfish/mapfish-print/pull/1397/commits/e1d0527d13db06b2b62ca7d6afb9e97dacd67a0e'} |
GHSA | GHSA-x2p8-rgfm-qw3v | Access Control vulnerability within CoreNLP | An Incorrect Access Control vulnerability exists in CoreNLP 4.3.2 via the classifier in NERServlet.java (lines 158 and 159). | {'CVE-2021-44550'} | 2022-03-03T22:07:42Z | 2022-02-25T00:01:07Z | CRITICAL | 9.8 | {'CWE-863'} | {'https://github.com/stanfordnlp/CoreNLP/commit/5ee097dbede547023e88f60ed3f430ff09398b87', 'https://github.com/stanfordnlp/CoreNLP/issues/1222', 'https://github.com/advisories/GHSA-x2p8-rgfm-qw3v', 'https://nvd.nist.gov/vuln/detail/CVE-2021-44550'} | null | {'https://github.com/stanfordnlp/CoreNLP/commit/5ee097dbede547023e88f60ed3f430ff09398b87'} | {'https://github.com/stanfordnlp/CoreNLP/commit/5ee097dbede547023e88f60ed3f430ff09398b87'} |
GHSA | GHSA-f3pp-32qc-36w4 | Prototype Pollution in jointjs | This affects the package jointjs before 3.4.2. A type confusion vulnerability can lead to a bypass of CVE-2020-28480 when the user-provided keys used in the path parameter are arrays in the setByPath function. | {'CVE-2021-23444'} | 2021-10-04T14:21:41Z | 2021-09-22T20:36:34Z | MODERATE | 5.6 | {'CWE-843', 'CWE-1321'} | {'https://github.com/clientIO/joint/pull/1514', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-1655817', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1655816', 'https://snyk.io/vuln/SNYK-JS-JOINTJS-1579578', 'https://github.com/clientIO/joint/commit/e5bf89efef6d5ea572d66870ffd86560de7830a8', 'https://github.com/advisories/GHSA-f3pp-32qc-36w4', 'https://github.com/clientIO/joint/releases/tag/v3.4.2'} | null | {'https://github.com/clientIO/joint/commit/e5bf89efef6d5ea572d66870ffd86560de7830a8'} | {'https://github.com/clientIO/joint/commit/e5bf89efef6d5ea572d66870ffd86560de7830a8'} |
GHSA | GHSA-cq76-mxrc-vchh | Crash in `tf.math.segment_*` operations | ### Impact
The implementation of `tf.math.segment_*` operations results in a `CHECK`-fail related abort (and denial of service) if a segment id in `segment_ids` is large.
```python
import tensorflow as tf
tf.math.segment_max(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])
tf.math.segment_min(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])
tf.math.segment_mean(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])
tf.math.segment_sum(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])
tf.math.segment_prod(data=np.ones((1,10,1)), segment_ids=[1676240524292489355])
```
This is similar to [CVE-2021-29584](https://github.com/tensorflow/tensorflow/blob/3a74f0307236fe206b046689c4d76f57c9b74eee/tensorflow/security/advisory/tfsa-2021-071.md) (and similar other reported vulnerabilities in TensorFlow, localized to specific APIs): the [implementation](https://github.com/tensorflow/tensorflow/blob/dae66e518c88de9c11718cd0f8f40a0b666a90a0/tensorflow/core/kernels/segment_reduction_ops_impl.h) (both on CPU and GPU) computes the output shape using [`AddDim`](https://github.com/tensorflow/tensorflow/blob/0b6b491d21d6a4eb5fbab1cca565bc1e94ca9543/tensorflow/core/framework/tensor_shape.cc#L395-L408). However, if the number of elements in the tensor overflows an `int64_t` value, `AddDim` results in a `CHECK` failure which provokes a `std::abort`. Instead, code should use [`AddDimWithStatus`](https://github.com/tensorflow/tensorflow/blob/0b6b491d21d6a4eb5fbab1cca565bc1e94ca9543/tensorflow/core/framework/tensor_shape.cc#L410-L440).
### Patches
We have patched the issue in GitHub commit [e9c81c1e1a9cd8dd31f4e83676cab61b60658429](https://github.com/tensorflow/tensorflow/commit/e9c81c1e1a9cd8dd31f4e83676cab61b60658429) (merging [#51733](https://github.com/tensorflow/tensorflow/pull/51733)).
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 externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46888). | {'CVE-2021-41195'} | 2021-11-10T19:36:50Z | 2021-11-10T19:36:50Z | MODERATE | 5.5 | {'CWE-190'} | {'https://github.com/tensorflow/tensorflow/issues/46888', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cq76-mxrc-vchh', 'https://github.com/advisories/GHSA-cq76-mxrc-vchh', 'https://github.com/tensorflow/tensorflow/commit/e9c81c1e1a9cd8dd31f4e83676cab61b60658429', 'https://github.com/tensorflow/tensorflow/pull/51733', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41195'} | null | {'https://github.com/tensorflow/tensorflow/commit/e9c81c1e1a9cd8dd31f4e83676cab61b60658429'} | {'https://github.com/tensorflow/tensorflow/commit/e9c81c1e1a9cd8dd31f4e83676cab61b60658429'} |
GHSA | GHSA-j9cf-pr2x-5273 | Prototype Pollution in dot-object | dot-object before 2.1.3 is vulnerable to Prototype Pollution. The set function could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload. | {'CVE-2019-10793'} | 2022-04-19T19:03:24Z | 2022-02-09T22:33:31Z | MODERATE | 6.3 | {'CWE-74'} | {'https://github.com/advisories/GHSA-j9cf-pr2x-5273', 'https://github.com/rhalff/dot-object/commit/f76cff5fe6d01d30ce110d8f454db2e5bd28a7de', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10793', 'https://snyk.io/vuln/SNYK-JS-DOTOBJECT-548905'} | null | {'https://github.com/rhalff/dot-object/commit/f76cff5fe6d01d30ce110d8f454db2e5bd28a7de'} | {'https://github.com/rhalff/dot-object/commit/f76cff5fe6d01d30ce110d8f454db2e5bd28a7de'} |
GHSA | GHSA-hf79-8hjp-rrvq | Use After Free in lucet | ### Impact
There is a bug in the main branch of Lucet's `lucet-runtime` that allows a use-after-free in an `Instance` object that could result in memory corruption, data race, or other related issues. This bug was introduced early in the development of Lucet and is present in all releases. As a result of this bug, and dependent on the memory backing for the `Instance` objects, it is possible to trigger a use-after-free when the `Instance` is dropped.
### Patches
Users should upgrade to the `main` branch of the Lucet repository. Lucet does not provide versioned releases on crates.io.
### Workarounds
There is no way to remediate this vulnerability without upgrading.
### Description
Lucet uses a "pool" allocator for new WebAssembly instances that are created. This pool allocator manages everything from the linear memory of the wasm instance, the runtime stack for async switching, as well as the memory behind the Instance itself. `Instances` are referred to via an `InstanceHandle` type which will, on drop, release the memory backing the Instance back to the pool.
When an Instance is dropped, the fields of the `Instance` are destructed top-to-bottom, however when the `alloc: Alloc` field is destructed, the memory backing the `Instance` is released back to the pool before the destructors of the remaining fields are run. If another thread allocates the same memory from the pool while these destructors are still running, a race condition occurs that can lead to use-after-free errors.
The bug was corrected by changing how the `InstanceHandle` destructor operates to ensure that the memory backing an Instance is only returned to the pool once the `Instance` has been completely destroyed.
This security advisory has been assigned CVE-2021-43790.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [lucet repository](https://github.com/bytecodealliance/lucet)
* Email [the lucet team](mailto:lucet@fastly.com)
* See the [Bytecode Alliance security policy](https://bytecodealliance.org/security)
| {'CVE-2021-43790'} | 2022-04-19T19:03:16Z | 2021-11-30T22:20:36Z | HIGH | 8.5 | {'CWE-416'} | {'https://github.com/bytecodealliance/lucet/commit/7c7757c772fb709c61b1442bcc1e1fbee97bf4a8', 'https://crates.io/crates/lucet-runtime', 'https://github.com/bytecodealliance/lucet/security/advisories/GHSA-hf79-8hjp-rrvq', 'https://github.com/advisories/GHSA-hf79-8hjp-rrvq', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43790'} | null | {'https://github.com/bytecodealliance/lucet/commit/7c7757c772fb709c61b1442bcc1e1fbee97bf4a8'} | {'https://github.com/bytecodealliance/lucet/commit/7c7757c772fb709c61b1442bcc1e1fbee97bf4a8'} |
GHSA | GHSA-6gm7-j668-w6h9 | SQL Injection in Pimcore | Pimcore prior to version 10.3.5 is vulnerable SQL injection in RecyclebinController.php. This vulnerability affects data confidentiality. | {'CVE-2022-1219'} | 2022-04-22T20:42:11Z | 2022-04-09T00:00:30Z | HIGH | 7.5 | {'CWE-89'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-1219', 'https://github.com/advisories/GHSA-6gm7-j668-w6h9', 'https://huntr.dev/bounties/f700bd18-1fd3-4a05-867f-07176aebc7f6', 'https://github.com/pimcore/pimcore/commit/a697830359df06246acca502ee2455614de68017'} | null | {'https://github.com/pimcore/pimcore/commit/a697830359df06246acca502ee2455614de68017'} | {'https://github.com/pimcore/pimcore/commit/a697830359df06246acca502ee2455614de68017'} |
GHSA | GHSA-r8hp-5m7c-jhv4 | Cross-site Scripting OrchardCore.Application.Cms.Targets | Cross-site Scripting (XSS) - Stored in NuGet OrchardCore.Application.Cms.Targets prior to 1.2.2. | {'CVE-2022-0274'} | 2022-01-21T23:08:50Z | 2022-01-21T23:08:50Z | MODERATE | 6.8 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0274', 'https://github.com/advisories/GHSA-r8hp-5m7c-jhv4', 'https://huntr.dev/bounties/a82a714a-9b71-475e-bfc3-43326fcaf764', 'https://github.com/orchardcms/orchardcore/commit/218f25ddfadb66a54de7a82dffe3ab2e4ab7c4b4'} | null | {'https://github.com/orchardcms/orchardcore/commit/218f25ddfadb66a54de7a82dffe3ab2e4ab7c4b4'} | {'https://github.com/orchardcms/orchardcore/commit/218f25ddfadb66a54de7a82dffe3ab2e4ab7c4b4'} |
GHSA | GHSA-v24h-pjjv-mcp6 | Denial of service in Tendermint | ### Description
**Denial of Service 1**
Tendermint 0.33.2 and earlier does not limit the number of P2P connection requests. For each p2p connection, Tendermint allocates XXX bytes. Even though this memory is garbage collected once the connection is terminated (due to duplicate IP or reaching a maximum number of inbound peers), temporary memory spikes can lead to OOM (Out-Of-Memory) exceptions.
Tendermint 0.33.3 (and 0.32.10) limits the total number of P2P incoming connection requests to to `p2p.max_num_inbound_peers + len(p2p.unconditional_peer_ids)`.
Notes:
- Tendermint does not rate limit P2P connection requests per IP (an attacker can saturate all the inbound slots);
- Tendermint does not rate limit HTTP(S) requests. If you expose any RPC endpoints to the public, please make sure to put in place some protection (https://www.nginx.com/blog/rate-limiting-nginx/). We may implement this in the future (https://github.com/tendermint/tendermint/issues/1696).
**Denial of Service 2**
Tendermint 0.33.2 and earlier does not reclaim `activeID` of a peer after it's removed in `Mempool` reactor. This does not happen all the time. It only happens when a connection fails (for any reason) before the `Peer` is created and added to all reactors. `RemovePeer` is therefore called before `AddPeer`, which leads to always growing memory (`activeIDs` map). The `activeIDs` map has a maximum size of 65535 and the node will panic if this map reaches the maximum. An attacker can create a lot of connection attempts (exploiting Denial of Service 1), which ultimately will lead to the node panicking.
Tendermint 0.33.3 (and 0.32.10) claims `activeID` for a peer in `InitPeer`, which is executed before `MConnection` is started.
Notes:
- `InitPeer` function was added to all reactors to combat a similar issue - https://github.com/tendermint/tendermint/issues/3338;
- Denial of Service 2 is independent of Denial of Service 1 and can be executed without it.
### Impact
- All full nodes (except for validators who are behind closed networks)
- Node's memory usage increases, then it panics either in the mempool or due to OOM.
### Patches
- v0.33.3
- v0.32.10
- v0.31.12
### Workarounds
No workarounds.
### References
- https://hackerone.com/reports/820317 (not disclosed yet)
- https://github.com/tendermint/tendermint/issues/3338
- https://github.com/tendermint/tendermint/issues/1696
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [tendermint/tendermint](https://github.com/tendermint/tendermint)
* Email us at [security@tendermint.com](mailto:security@tendermint.com)
More information can be found [here](https://tendermint.com/security/).
### Credits
- [fudongbai](https://hackerone.com/fudongbai) for discovering and reporting Denial of Service 2
- Ethan Buchman (@ebuchman) for writing a test case for Denial of Service 2 and Tess Rinearson (@tessr) for fixing it
- Anton Kaliaev (@melekes) for fixing Denial of Service 1 | {'CVE-2020-5303'} | 2021-05-27T18:44:09Z | 2021-05-27T18:44:09Z | LOW | 3.1 | {'CWE-789', 'CWE-787'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-5303', 'https://github.com/tendermint/tendermint/blob/master/CHANGELOG.md#denial-of-service-1', 'https://github.com/tendermint/tendermint/commit/e2d6859afd7dba4cf97c7f7d412e7d8fc908d1cd', 'https://github.com/advisories/GHSA-v24h-pjjv-mcp6', 'https://github.com/tendermint/tendermint/issues/1696', 'https://hackerone.com/reports/820317', 'https://github.com/tendermint/tendermint/issues/3338', 'https://github.com/tendermint/tendermint/security/advisories/GHSA-v24h-pjjv-mcp6'} | null | {'https://github.com/tendermint/tendermint/commit/e2d6859afd7dba4cf97c7f7d412e7d8fc908d1cd'} | {'https://github.com/tendermint/tendermint/commit/e2d6859afd7dba4cf97c7f7d412e7d8fc908d1cd'} |
GHSA | GHSA-vc6r-4x6g-mmqc | Path Traversal in m-server | Versions of `m-server` before 1.4.2 are vulnerable to path traversal allowing a remote attacker to display content of arbitrary files from the server.
## Recommendation
Update to version 1.4.2 or later. | null | 2021-08-04T21:07:26Z | 2019-06-11T16:16:23Z | MODERATE | 0 | {'CWE-22'} | {'https://github.com/advisories/GHSA-vc6r-4x6g-mmqc', 'https://hackerone.com/reports/319795', 'https://github.com/nodejs/security-wg/blob/master/vuln/npm/468.json', 'https://github.com/nunnly/m-server/commit/01f13f040d1961ca3146dce7e2db990156e65e9a', 'https://www.npmjs.com/advisories/731'} | null | {'https://github.com/nunnly/m-server/commit/01f13f040d1961ca3146dce7e2db990156e65e9a'} | {'https://github.com/nunnly/m-server/commit/01f13f040d1961ca3146dce7e2db990156e65e9a'} |
GHSA | GHSA-m4hj-wg2r-qpcr | showdoc is vulnerable to Cross-Site Request Forgery (CSRF) | showdoc is vulnerable to Cross-Site Request Forgery (CSRF). | {'CVE-2021-3776'} | 2021-11-17T21:10:57Z | 2021-11-15T23:13:34Z | MODERATE | 4.3 | {'CWE-352'} | {'https://github.com/advisories/GHSA-m4hj-wg2r-qpcr', 'https://github.com/star7th/showdoc/commit/67093c879a6563aa6ee08003177777d1975e2351', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3776', 'https://huntr.dev/bounties/e0edf27d-437e-44fe-907a-df020f385304'} | null | {'https://github.com/star7th/showdoc/commit/67093c879a6563aa6ee08003177777d1975e2351'} | {'https://github.com/star7th/showdoc/commit/67093c879a6563aa6ee08003177777d1975e2351'} |
GHSA | GHSA-vfp9-gwrh-wq9g | Path Traversal in crud-file-server | Versions of `crud-file-server` prior to 0.9.0 are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the served folder using relative paths.
## Recommendation
Upgrade to version 0.9.0 or later. | {'CVE-2018-3733'} | 2021-01-08T01:57:29Z | 2018-07-18T21:20:19Z | HIGH | 0 | {'CWE-22'} | {'https://www.npmjs.com/advisories/1003', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3733', 'https://github.com/omphalos/crud-file-server/commit/4fc3b404f718abb789f4ce4272c39c7a138c7a82', 'https://hackerone.com/reports/310690', 'https://github.com/advisories/GHSA-vfp9-gwrh-wq9g'} | null | {'https://github.com/omphalos/crud-file-server/commit/4fc3b404f718abb789f4ce4272c39c7a138c7a82'} | {'https://github.com/omphalos/crud-file-server/commit/4fc3b404f718abb789f4ce4272c39c7a138c7a82'} |
GHSA | GHSA-w4xf-2pqw-5mq7 | Reference binding to nullptr in `RaggedTensorToVariant` | ### Impact
An attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.RaggedTensorToVariant`:
```python
import tensorflow as tf
tf.raw_ops.RaggedTensorToVariant(
rt_nested_splits=[],
rt_dense_values=[1,2,3],
batched_input=True)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_to_variant_op.cc#L129) has an incomplete validation of the splits values, missing the case when the argument would be empty.
### Patches
We have patched the issue in GitHub commit [be7a4de6adfbd303ce08be4332554dff70362612](https://github.com/tensorflow/tensorflow/commit/be7a4de6adfbd303ce08be4332554dff70362612).
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-37666'} | 2021-08-25T14:42:13Z | 2021-08-25T14:42:13Z | HIGH | 7.8 | {'CWE-824'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-37666', 'https://github.com/advisories/GHSA-w4xf-2pqw-5mq7', 'https://github.com/tensorflow/tensorflow/commit/be7a4de6adfbd303ce08be4332554dff70362612', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-w4xf-2pqw-5mq7'} | null | {'https://github.com/tensorflow/tensorflow/commit/be7a4de6adfbd303ce08be4332554dff70362612'} | {'https://github.com/tensorflow/tensorflow/commit/be7a4de6adfbd303ce08be4332554dff70362612'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.