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-6p56-wp2h-9hxr | Buffer Overflow in NumPy | A Buffer Overflow vulnerability exists in NumPy 1.9.x in the PyArray_NewFromDescr_int function of ctors.c when specifying arrays of large dimensions (over 32) from Python code, which could let a malicious user cause a Denial of Service. | {'CVE-2021-33430'} | 2022-02-08T20:09:25Z | 2022-01-07T00:09:39Z | MODERATE | 5.3 | {'CWE-120'} | {'https://github.com/advisories/GHSA-6p56-wp2h-9hxr', 'https://github.com/numpy/numpy/issues/18939', 'https://nvd.nist.gov/vuln/detail/CVE-2021-33430', 'https://github.com/numpy/numpy/commit/ae317fd9ff3e79c0eac357d723bfc29cbd625f2e'} | null | {'https://github.com/numpy/numpy/commit/ae317fd9ff3e79c0eac357d723bfc29cbd625f2e'} | {'https://github.com/numpy/numpy/commit/ae317fd9ff3e79c0eac357d723bfc29cbd625f2e'} |
GHSA | GHSA-vgrx-w6rg-8fqf | Forgeable Public/Private Tokens in jwt-simple | Affected versions of the `jwt-simple` package allow users to select what algorithm the server will use to verify a provided JWT. A malicious actor can use this behaviour to arbitrarily modify the contents of a JWT while still passing verification. For the common use case of the JWT, the end result is a complete authentication bypass with minimal effort.
## Recommendation
Update to version 0.3.1 or later.
Additionally, be sure to always specify an algorithm in calls to `.decode()`. | {'CVE-2016-10555'} | 2021-01-08T01:57:18Z | 2018-11-06T23:12:07Z | CRITICAL | 0 | {'CWE-20'} | {'https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/', 'https://github.com/hokaccha/node-jwt-simple/commit/957957cfa44474049b4603b293569588ee9ffd97', 'https://github.com/advisories/GHSA-vgrx-w6rg-8fqf', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10555', 'https://www.npmjs.com/advisories/87', 'https://github.com/hokaccha/node-jwt-simple/pull/16', 'https://github.com/hokaccha/node-jwt-simple/pull/14', 'https://nodesecurity.io/advisories/87'} | null | {'https://github.com/hokaccha/node-jwt-simple/commit/957957cfa44474049b4603b293569588ee9ffd97'} | {'https://github.com/hokaccha/node-jwt-simple/commit/957957cfa44474049b4603b293569588ee9ffd97'} |
GHSA | GHSA-fx5c-h9f6-rv7c | `CHECK`-fails due to attempting to build a reference tensor | ### Impact
A malicious user can cause a denial of service by altering a `SavedModel` such that [Grappler optimizer would attempt to build a tensor using a reference `dtype`](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/grappler/optimizers/constant_folding.cc#L1328-L1402). This would result in a crash due to a `CHECK`-fail [in the `Tensor` constructor](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/framework/tensor.cc#L733-L781) as reference types are not allowed.
### Patches
We have patched the issue in GitHub commit [6b5adc0877de832b2a7c189532dbbbc64622eeb6](https://github.com/tensorflow/tensorflow/commit/6b5adc0877de832b2a7c189532dbbbc64622eeb6).
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-23588'} | 2022-02-11T20:01:09Z | 2022-02-09T23:28:07Z | MODERATE | 6.5 | {'CWE-617'} | {'https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/grappler/optimizers/constant_folding.cc#L1328-L1402', 'https://github.com/advisories/GHSA-fx5c-h9f6-rv7c', 'https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/framework/tensor.cc#L733-L781', 'https://github.com/tensorflow/tensorflow/commit/6b5adc0877de832b2a7c189532dbbbc64622eeb6', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23588', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-fx5c-h9f6-rv7c'} | null | {'https://github.com/tensorflow/tensorflow/commit/6b5adc0877de832b2a7c189532dbbbc64622eeb6'} | {'https://github.com/tensorflow/tensorflow/commit/6b5adc0877de832b2a7c189532dbbbc64622eeb6'} |
GHSA | GHSA-7x7c-qm48-pq9c | Cross-site Scripting in karma | karma prior to version 6.3.14 contains a cross-site scripting vulnerability. | {'CVE-2022-0437'} | 2022-02-11T19:59:48Z | 2022-02-06T00:00:54Z | MODERATE | 6.1 | {'CWE-79'} | {'https://github.com/karma-runner/karma/releases/tag/v6.3.14', 'https://huntr.dev/bounties/64b67ea1-5487-4382-a5f6-e8a95f798885', 'https://github.com/karma-runner/karma/commit/839578c45a8ac42fbc1d72105f97eab77dd3eb8a', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0437', 'https://github.com/advisories/GHSA-7x7c-qm48-pq9c'} | null | {'https://github.com/karma-runner/karma/commit/839578c45a8ac42fbc1d72105f97eab77dd3eb8a'} | {'https://github.com/karma-runner/karma/commit/839578c45a8ac42fbc1d72105f97eab77dd3eb8a'} |
GHSA | GHSA-gf88-j2mg-cc82 | Crash caused by integer conversion to unsigned | ### Impact
An attacker can cause a denial of service in `boosted_trees_create_quantile_stream_resource` by using negative arguments:
```python
import tensorflow as tf
from tensorflow.python.ops import gen_boosted_trees_ops
import numpy as np
v= tf.Variable([0.0, 0.0, 0.0, 0.0, 0.0])
gen_boosted_trees_ops.boosted_trees_create_quantile_stream_resource(
quantile_stream_resource_handle = v.handle,
epsilon = [74.82224],
num_streams = [-49],
max_elements = np.int32(586))
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantile_ops.cc#L96) does not validate that `num_streams` only contains non-negative numbers. In turn, [this results in using this value to allocate memory](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantiles/quantile_stream_resource.h#L31-L40):
```cc
class BoostedTreesQuantileStreamResource : public ResourceBase {
public:
BoostedTreesQuantileStreamResource(const float epsilon,
const int64 max_elements,
const int64 num_streams)
: are_buckets_ready_(false),
epsilon_(epsilon),
num_streams_(num_streams),
max_elements_(max_elements) {
streams_.reserve(num_streams_);
...
}
}
```
However, `reserve` receives an unsigned integer so there is an implicit conversion from a negative value to a large positive unsigned. This results in a crash from the standard library.
### Patches
We have patched the issue in GitHub commit [8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992](https://github.com/tensorflow/tensorflow/commit/8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992).
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-37661'} | 2021-08-25T14:42:28Z | 2021-08-25T14:42:28Z | MODERATE | 5.5 | {'CWE-681'} | {'https://github.com/tensorflow/tensorflow/commit/8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37661', 'https://github.com/advisories/GHSA-gf88-j2mg-cc82', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-gf88-j2mg-cc82'} | null | {'https://github.com/tensorflow/tensorflow/commit/8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992'} | {'https://github.com/tensorflow/tensorflow/commit/8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992'} |
GHSA | GHSA-r56q-vv3c-6g9c | Improper sanitization of delegated role names | ### Impact
The tough library, prior to 0.12.0, does not properly sanitize delegated role names when caching a repository, or when loading a repository from the filesystem. When the repository is cached or loaded, files ending with the .json extension could be overwritten with role metadata anywhere on the system.
AWS would like to thank https://github.com/jku for reporting this issue.
### Patches
A fix is available in version 0.12.0.
### Workarounds
No workarounds to this issue are known.
### References
https://github.com/theupdateframework/python-tuf/security/advisories/GHSA-wjw6-2cqr-j4qr
| {'CVE-2021-41150'} | 2021-10-20T15:38:21Z | 2021-10-19T20:16:26Z | HIGH | 8.2 | {'CWE-22'} | {'https://github.com/advisories/GHSA-r56q-vv3c-6g9c', 'https://github.com/theupdateframework/python-tuf/security/advisories/GHSA-wjw6-2cqr-j4qr', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41150', 'https://github.com/awslabs/tough/commit/1809b9bd1106d78a51fbea3071aa97a3530bac9a', 'https://github.com/awslabs/tough/security/advisories/GHSA-r56q-vv3c-6g9c'} | null | {'https://github.com/awslabs/tough/commit/1809b9bd1106d78a51fbea3071aa97a3530bac9a'} | {'https://github.com/awslabs/tough/commit/1809b9bd1106d78a51fbea3071aa97a3530bac9a'} |
GHSA | GHSA-pfjj-m3jj-9jc9 | Undefined behavior in `SparseTensorSliceDataset` | ### Impact
The [implementation of `SparseTensorSliceDataset`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L227-L292) has an undefined behavior: under certain condition it can be made to dereference a `nullptr` value:
```python
import tensorflow as tf
import numpy as np
tf.raw_ops.SparseTensorSliceDataset(
indices=[[]],
values=[],
dense_shape=[1,1])
```
The 3 input arguments represent a sparse tensor. However, there are some preconditions that these arguments must satisfy but these are not validated in the implementation.
### Patches
We have patched the issue in GitHub commit [965b97e4a9650495cda5a8c210ef6684b4b9eceb](https://github.com/tensorflow/tensorflow/commit/965b97e4a9650495cda5a8c210ef6684b4b9eceb).
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Faysal Hossain Shezan from University of Virginia. | {'CVE-2022-21736'} | 2022-02-11T16:24:04Z | 2022-02-09T23:43:27Z | HIGH | 7.6 | {'CWE-476'} | {'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L227-L292', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-pfjj-m3jj-9jc9', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21736', 'https://github.com/tensorflow/tensorflow/commit/965b97e4a9650495cda5a8c210ef6684b4b9eceb', 'https://github.com/advisories/GHSA-pfjj-m3jj-9jc9'} | null | {'https://github.com/tensorflow/tensorflow/commit/965b97e4a9650495cda5a8c210ef6684b4b9eceb'} | {'https://github.com/tensorflow/tensorflow/commit/965b97e4a9650495cda5a8c210ef6684b4b9eceb'} |
GHSA | GHSA-93p5-8fqw-wjx3 | Authentication bypass by capture-replay in github.com/cosmos/ethermint | Cosmos Network Ethermint <= v0.4.0 is affected by a transaction replay vulnerability in the EVM module. If the victim sends a very large nonce transaction, the attacker can replay the transaction through the application. | {'CVE-2021-25834'} | 2022-04-12T22:56:36Z | 2022-02-15T01:57:18Z | HIGH | 7.5 | {'CWE-287', 'CWE-294'} | {'https://github.com/cosmos/ethermint/commit/d7bdbd7488644f0aaeee5cdcdc119c863f199f72', 'https://github.com/cosmos/ethermint/releases/tag/v0.4.1', 'https://github.com/advisories/GHSA-93p5-8fqw-wjx3', 'https://github.com/cosmos/ethermint/issues/686', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25834'} | null | {'https://github.com/cosmos/ethermint/commit/d7bdbd7488644f0aaeee5cdcdc119c863f199f72'} | {'https://github.com/cosmos/ethermint/commit/d7bdbd7488644f0aaeee5cdcdc119c863f199f72'} |
GHSA | GHSA-qhmp-h54x-38qr | CWE-730 Regex injection with IFTTT Plugin | ### Impact
Anyone _publicly_ hosting the Apprise library and granting them access to the IFTTT notification service.
### Patches
Update to Apprise v0.9.5.1
```bash
# Install Apprise v0.9.5.1 from PyPI
pip install apprise==0.9.5.1
```
The patch to the problem was performed [here](https://github.com/caronc/apprise/pull/436/files).
### Workarounds
Alternatively, if upgrading is not an option, you can safely remove the following file:
- `apprise/plugins/NotifyIFTTT.py`
The above will eliminate the ability to use IFTTT, but everything else will work smoothly.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Apprise](https://github.com/caronc/apprise/issues)
* Email me at [lead2gold@gmail.com](mailto:lead2gold@gmail.com)
### Additional Credit
Github would not allow me to additionally credit **Rasmus Petersen**, but I would like to put that here at the very least - thank you for finding and reporting this issue along with those already credited
## Additional Notes:
- Github would not allow me to add/tag the 2 CWE's this issue is applicable to (only CWE-400). The other is: CWE-730 (placed in the title)
| {'CVE-2021-39229'} | 2022-04-19T19:03:09Z | 2021-09-20T20:57:02Z | HIGH | 7.5 | {'CWE-400'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-39229', 'https://github.com/caronc/apprise/pull/436', 'https://github.com/caronc/apprise/blob/0007eade20934ddef0aba38b8f1aad980cfff253/apprise/plugins/NotifyIFTTT.py#L356-L359', 'https://github.com/caronc/apprise/commit/e20fce630d55e4ca9b0a1e325a5fea6997489831', 'https://github.com/caronc/apprise/security/advisories/GHSA-qhmp-h54x-38qr', 'https://github.com/advisories/GHSA-qhmp-h54x-38qr', 'https://github.com/caronc/apprise/releases/tag/v0.9.5.1'} | null | {'https://github.com/caronc/apprise/commit/e20fce630d55e4ca9b0a1e325a5fea6997489831'} | {'https://github.com/caronc/apprise/commit/e20fce630d55e4ca9b0a1e325a5fea6997489831'} |
GHSA | GHSA-cjg2-2fjg-fph4 | Integer underflow in Frontier | ### Impact
A bug in Frontier's MODEXP precompile implementation can cause an integer underflow in certain conditions. This will cause a node crash for debug builds. For release builds (and production WebAssembly binaries), the impact is limited as it can only cause a normal EVM out-of-gas. It is recommended that you apply the patch as soon as possible.
If you do not use MODEXP precompile in your runtime, then you are not impacted.
### Patches
Patches are applied in PR #549.
### Workarounds
None.
### References
Patch PR: #549
### Credits
Thanks to SR-Labs for discovering the security vulnerability, and thanks to PureStake team for the patches.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [Frontier repo](https://github.com/paritytech/frontier)
| {'CVE-2022-21685'} | 2022-01-15T00:03:46Z | 2022-01-14T21:03:36Z | MODERATE | 0 | {'CWE-191'} | {'https://github.com/paritytech/frontier/commit/8a93fdc6c9f4eb1d2f2a11b7ff1d12d70bf5a664', 'https://github.com/paritytech/frontier/pull/549', 'https://github.com/advisories/GHSA-cjg2-2fjg-fph4', 'https://github.com/paritytech/frontier/security/advisories/GHSA-cjg2-2fjg-fph4', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21685'} | null | {'https://github.com/paritytech/frontier/commit/8a93fdc6c9f4eb1d2f2a11b7ff1d12d70bf5a664'} | {'https://github.com/paritytech/frontier/commit/8a93fdc6c9f4eb1d2f2a11b7ff1d12d70bf5a664'} |
GHSA | GHSA-qm28-7hqv-wg5j | OS Command Injection in ng-packagr | The package ng-packagr before 10.1.1 are vulnerable to Command Injection via the styleIncludePaths option. | {'CVE-2020-7735'} | 2021-10-05T16:28:06Z | 2021-05-07T16:47:32Z | MODERATE | 6.6 | {'CWE-78'} | {'https://snyk.io/vuln/SNYK-JS-NGPACKAGR-1012427', 'https://github.com/advisories/GHSA-qm28-7hqv-wg5j', 'https://github.com/ng-packagr/ng-packagr/commit/bda0fff3443301f252930a73fdc8fb9502de596d', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7735'} | null | {'https://github.com/ng-packagr/ng-packagr/commit/bda0fff3443301f252930a73fdc8fb9502de596d'} | {'https://github.com/ng-packagr/ng-packagr/commit/bda0fff3443301f252930a73fdc8fb9502de596d'} |
GHSA | GHSA-p5hj-xxfr-pwc3 | Code Injection in microweber | Code Injection in Packagist microweber/microweber prior to 1.2.11. | {'CVE-2022-0282'} | 2022-01-27T18:32:44Z | 2022-01-21T18:02:39Z | HIGH | 7.5 | {'CWE-94'} | {'https://github.com/advisories/GHSA-p5hj-xxfr-pwc3', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0282', 'https://huntr.dev/bounties/8815b642-bd9b-4737-951b-bde7319faedd', 'https://github.com/microweber/microweber/commit/51b5a4e3ef01e587797c0109159a8ad9d2bac77a'} | null | {'https://github.com/microweber/microweber/commit/51b5a4e3ef01e587797c0109159a8ad9d2bac77a'} | {'https://github.com/microweber/microweber/commit/51b5a4e3ef01e587797c0109159a8ad9d2bac77a'} |
GHSA | GHSA-vwjj-2852-3765 | Cross-Site Scripting in forms | Affected versions of `forms` do not properly escape HTML in generated forms, which may result in cross-site scripting.
## Recommendation
Update to version 1.3.0 or later. | {'CVE-2017-16015'} | 2021-01-08T01:57:11Z | 2018-11-09T17:46:27Z | MODERATE | 0 | {'CWE-80'} | {'https://github.com/advisories/GHSA-vwjj-2852-3765', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16015', 'https://www.npmjs.com/advisories/158', 'https://nodesecurity.io/advisories/158', 'https://github.com/caolan/forms/commit/bc01e534a0ff863dedb2026a50bd03153bbc6a5d'} | null | {'https://github.com/caolan/forms/commit/bc01e534a0ff863dedb2026a50bd03153bbc6a5d'} | {'https://github.com/caolan/forms/commit/bc01e534a0ff863dedb2026a50bd03153bbc6a5d'} |
GHSA | GHSA-7vwg-39h8-8qp8 | /user/sessions endpoint allows detecting valid accounts | This Security Advisory is about a vulnerability in eZ Platform v1.13, v2.5, and v3.2, and in Ibexa DXP and Ibexa Open Source v3.3. The /user/sessions endpoint can let an attacker detect if a given username or email refers to a valid account. This can be detected through differences in the response data or response time of certain requests. The fix ensures neither attack is possible. The fix is distributed via Composer.
If you come across a security issue in our products, here is how you can report it to us: https://doc.ibexa.co/en/latest/guide/reporting_issues/#toc | null | 2021-03-11T17:42:01Z | 2021-03-11T17:42:01Z | HIGH | 0 | {'CWE-203'} | {'https://github.com/advisories/GHSA-7vwg-39h8-8qp8', 'https://github.com/ezsystems/ezplatform-rest/security/advisories/GHSA-7vwg-39h8-8qp8', 'https://packagist.org/packages/ezsystems/ezplatform-rest', 'https://github.com/ezsystems/ezplatform-rest/commit/e239bba8b154a3b4cf787e29b9f15edf8945d933'} | null | {'https://github.com/ezsystems/ezplatform-rest/commit/e239bba8b154a3b4cf787e29b9f15edf8945d933'} | {'https://github.com/ezsystems/ezplatform-rest/commit/e239bba8b154a3b4cf787e29b9f15edf8945d933'} |
GHSA | GHSA-gpqq-952q-5327 | XSS in the `of` option of the `.position()` util in jquery-ui | ### Impact
Accepting the value of the `of` option of the [`.position()`](https://api.jqueryui.com/position/) util from untrusted sources may execute untrusted code. For example, invoking the following code:
```js
$( "#element" ).position( {
my: "left top",
at: "right bottom",
of: "<img onerror='window.globalOf=true' src='/404' />",
collision: "none"
} );
```
will call the `doEvilThing()` function.
### Patches
The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `of` option is now treated as a CSS selector.
### Workarounds
A workaround is to not accept the value of the `of` option from untrusted sources.
### For more information
If you have any questions or comments about this advisory, search for a relevant issue in [the jQuery UI repo](https://github.com/jquery/jquery-ui/issues). If you don't find an answer, open a new issue. | {'CVE-2021-41184'} | 2022-04-22T15:40:38Z | 2021-10-26T14:55:12Z | MODERATE | 6.5 | {'CWE-79'} | {'https://github.com/jquery/jquery-ui/commit/effa323f1505f2ce7a324e4f429fa9032c72f280', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NXIUUBRVLA4E7G7MMIKCEN75YN7UFERW/', 'https://security.netapp.com/advisory/ntap-20211118-0004/', 'https://www.drupal.org/sa-core-2022-001', 'https://blog.jqueryui.com/2021/10/jquery-ui-1-13-0-released/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41184', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/O74SXYY7RGXREQDQUDQD4BPJ4QQTD2XQ/', 'https://www.tenable.com/security/tns-2022-09', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SNXA7XRKGINWSUIPIZ6ZBCTV6N3KSHES/', 'https://github.com/jquery/jquery-ui/security/advisories/GHSA-gpqq-952q-5327', 'https://github.com/advisories/GHSA-gpqq-952q-5327'} | null | {'https://github.com/jquery/jquery-ui/commit/effa323f1505f2ce7a324e4f429fa9032c72f280'} | {'https://github.com/jquery/jquery-ui/commit/effa323f1505f2ce7a324e4f429fa9032c72f280'} |
GHSA | GHSA-w3j4-76qw-wwjm | Older releases of better_errors open to Cross-Site Request Forgery attack | ### Impact
better_errors prior to 2.8.0 did not implement CSRF protection for its internal requests. It also did not enforce the correct "Content-Type" header for these requests, which allowed a cross-origin "simple request" to be made without CORS protection. These together left an application with better_errors enabled open to cross-origin attacks.
_As a developer tool, better_errors documentation strongly recommends addition only to the `development` bundle group, so this vulnerability should only affect development environments. Please ensure that your project limits better_errors to the `development` group (or the non-Rails equivalent)._
### Patches
Starting with release 2.8.x, CSRF protection is enforced. It is recommended that you upgrade to the latest release, or minimally to "~> 2.8.3".
### Workarounds
There are no known workarounds to mitigate the risk of using older releases of better_errors.
### References
- Chris Moberly provided [an example attack that uses a now-patched vulnerability of webpack-dev-server in conjunction with Better Errors](https://about.gitlab.com/blog/2021/09/07/why-are-developers-vulnerable-to-driveby-attacks/)
### For more information
If you have any questions or comments about this advisory, please
- Add to the [discussion in better_errors](https://github.com/BetterErrors/better_errors/discussions/507)
- Open an issue in [better_errors](https://github.com/BetterErrors/better_errors)
| {'CVE-2021-39197'} | 2022-04-19T19:03:07Z | 2021-09-07T23:08:24Z | MODERATE | 6.3 | {'CWE-352'} | {'https://github.com/BetterErrors/better_errors/commit/8e8e796bfbde4aa088741823c8a3fc6df2089bb0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39197', 'https://github.com/advisories/GHSA-w3j4-76qw-wwjm', 'https://github.com/BetterErrors/better_errors/pull/474', 'https://github.com/BetterErrors/better_errors/discussions/507', 'https://github.com/BetterErrors/better_errors/security/advisories/GHSA-w3j4-76qw-wwjm'} | null | {'https://github.com/BetterErrors/better_errors/commit/8e8e796bfbde4aa088741823c8a3fc6df2089bb0'} | {'https://github.com/BetterErrors/better_errors/commit/8e8e796bfbde4aa088741823c8a3fc6df2089bb0'} |
GHSA | GHSA-7ghq-fvr3-pj2x | Incomplete validation in `MaxPoolGrad` | ### Impact
An attacker can trigger a denial of service via a segmentation fault in `tf.raw_ops.MaxPoolGrad` caused by missing validation:
```python
import tensorflow as tf
tf.raw_ops.MaxPoolGrad(
orig_input = tf.constant([], shape=[3, 0, 0, 2], dtype=tf.float32),
orig_output = tf.constant([], shape=[3, 0, 0, 2], dtype=tf.float32),
grad = tf.constant([], shape=[3, 0, 0, 2], dtype=tf.float32),
ksize = [1, 16, 16, 1],
strides = [1, 16, 18, 1],
padding = "EXPLICIT",
explicit_paddings = [0, 0, 14, 3, 15, 5, 0, 0])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/maxpooling_op.cc) misses some validation for the `orig_input` and `orig_output` tensors.
The fixes for [CVE-2021-29579](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-068.md) were incomplete.
### Patches
We have patched the issue in GitHub commit [136b51f10903e044308cf77117c0ed9871350475](https://github.com/tensorflow/tensorflow/commit/136b51f10903e044308cf77117c0ed9871350475).
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 Yakun Zhang of Baidu Security. | {'CVE-2021-37674'} | 2021-08-25T14:41:33Z | 2021-08-25T14:41:33Z | MODERATE | 5.5 | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-37674', 'https://github.com/tensorflow/tensorflow/commit/136b51f10903e044308cf77117c0ed9871350475', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-7ghq-fvr3-pj2x', 'https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-068.md', 'https://github.com/advisories/GHSA-7ghq-fvr3-pj2x'} | null | {'https://github.com/tensorflow/tensorflow/commit/136b51f10903e044308cf77117c0ed9871350475'} | {'https://github.com/tensorflow/tensorflow/commit/136b51f10903e044308cf77117c0ed9871350475'} |
GHSA | GHSA-79mg-4w23-4fqc | Unauthenticated SQL Injection in Cachet | ### Impact
In Cachet versions through 2.3.18, there is a SQL injection which is in the `SearchableTrait#scopeSearch()`. Attackers without authentication can utilize this vulnerability to exfiltrate sensitive data from the database such as administrator's password and session.
### Patches
The original repository of [https://github.com/CachetHQ/Cachet](https://github.com/CachetHQ/Cachet) is not active, the stable version 2.3.18 and it's developing 2.4 branch is affected.
Update to version 2.5 or later in the [https://github.com/fiveai/Cachet fork](https://github.com/fiveai/Cachet) to fix this vulnerability. | {'CVE-2021-39165'} | 2022-04-19T19:03:05Z | 2021-08-30T16:12:58Z | HIGH | 8.1 | {'CWE-89', 'CWE-287'} | {'https://github.com/fiveai/Cachet/commit/27bca8280419966ba80c6fa283d985ddffa84bb6', 'https://github.com/advisories/GHSA-79mg-4w23-4fqc', 'https://github.com/fiveai/Cachet/security/advisories/GHSA-79mg-4w23-4fqc', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39165'} | null | {'https://github.com/fiveai/Cachet/commit/27bca8280419966ba80c6fa283d985ddffa84bb6'} | {'https://github.com/fiveai/Cachet/commit/27bca8280419966ba80c6fa283d985ddffa84bb6'} |
GHSA | GHSA-6rrw-4fm9-rghv | Use of Hard-coded Cryptographic Key in Netmaker | Netmaker prior to versions 0.8.5, 0.9.4, 0.10.0, and 0.10.1 uses a hard-coded cryptographic key. | {'CVE-2022-0664'} | 2022-02-26T01:51:36Z | 2022-02-19T00:01:36Z | HIGH | 8.8 | {'CWE-321'} | {'https://huntr.dev/bounties/29898a42-fd4f-4b5b-a8e3-ab573cb87eac', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0664', 'https://github.com/advisories/GHSA-6rrw-4fm9-rghv', 'https://github.com/gravitl/netmaker/commit/9bee12642986cb9534e268447b70e6f0f03c59cf'} | null | {'https://github.com/gravitl/netmaker/commit/9bee12642986cb9534e268447b70e6f0f03c59cf'} | {'https://github.com/gravitl/netmaker/commit/9bee12642986cb9534e268447b70e6f0f03c59cf'} |
GHSA | GHSA-9722-rr68-rfpg | Upload whitelisted files to any directory in OctoberCMS | ### Impact
An attacker can exploit this vulnerability to upload jpg, jpeg, bmp, png, webp, gif, ico, css, js, woff, woff2, svg, ttf, eot, json, md, less, sass, scss, xml files to any directory of an October CMS server. The vulnerability is only exploitable by an authenticated backend user with the `cms.manage_assets` permission.
### Patches
Issue has been patched in Build 466 (v1.0.466).
### Workarounds
Apply https://github.com/octobercms/october/commit/6711dae8ef70caf0e94cec434498012a2ccd86b8 to your installation manually if unable to upgrade to Build 466.
### References
Reported by [Sivanesh Ashok](https://stazot.com/)
### For more information
If you have any questions or comments about this advisory:
* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)
### Threat assessment:
<img width="1241" alt="Screen Shot 2020-03-31 at 12 21 10 PM" src="https://user-images.githubusercontent.com/7253840/78061230-255f5400-734a-11ea-92b4-1120f6960505.png"> | {'CVE-2020-5297'} | 2022-04-19T19:02:26Z | 2020-06-03T21:58:27Z | LOW | 3.4 | {'CWE-73'} | {'https://github.com/advisories/GHSA-9722-rr68-rfpg', 'https://github.com/octobercms/october/security/advisories/GHSA-9722-rr68-rfpg', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5297', 'http://packetstormsecurity.com/files/158730/October-CMS-Build-465-XSS-File-Read-File-Deletion-CSV-Injection.html', 'https://github.com/octobercms/october/commit/6711dae8ef70caf0e94cec434498012a2ccd86b8', 'http://seclists.org/fulldisclosure/2020/Aug/2'} | null | {'https://github.com/octobercms/october/commit/6711dae8ef70caf0e94cec434498012a2ccd86b8'} | {'https://github.com/octobercms/october/commit/6711dae8ef70caf0e94cec434498012a2ccd86b8'} |
GHSA | GHSA-rrp4-2xx3-mv29 | Command injection in gh-ost | Gh-ost version <= 1.1.2 allows users to inject DSN strings via the `-database` parameter.
This is a low severity vulnerability as the attacker must have access to the target host or trick an administrator into executing a malicious `gh-ost` command on a host running `gh-ost`, plus network access from host running `gh-ost` to the attack's malicious MySQL server.
### Impact
This issue may lead to arbitrary local file read.
### Patches
Fixed in 1.1.3+.
### Workarounds
None
### References
- https://advisory.dw1.io/51
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [github/gh-ost](http://github.com/github/gh-ost) | {'CVE-2022-21687'} | 2022-04-19T19:03:19Z | 2022-02-01T00:47:33Z | MODERATE | 6.8 | {'CWE-74', 'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-21687', 'https://github.com/advisories/GHSA-rrp4-2xx3-mv29', 'https://github.com/github/gh-ost/security/advisories/GHSA-rrp4-2xx3-mv29', 'https://github.com/github/gh-ost/commit/a91ab042de013cfd8fbb633763438932d9080d8f'} | null | {'https://github.com/github/gh-ost/commit/a91ab042de013cfd8fbb633763438932d9080d8f'} | {'https://github.com/github/gh-ost/commit/a91ab042de013cfd8fbb633763438932d9080d8f'} |
GHSA | GHSA-qmm9-x5gr-4gfm | Open Redirect in hekto | Versions of `hekto` before 0.2.4 are vulnerable to open redirect when a domain name is used as part of the `.html` filename.
## Recommendation
Update to version 0.2.4 or later. | {'CVE-2018-3743'} | 2021-01-08T01:58:33Z | 2018-07-18T21:20:12Z | LOW | 0 | {'CWE-601'} | {'https://github.com/herber/hekto/commit/1e5c75f8259ba0daf9b2600db3c246cda1934c46', 'https://github.com/advisories/GHSA-qmm9-x5gr-4gfm', 'https://github.com/herber/hekto/pull/3', 'https://www.npmjs.com/advisories/669', 'https://hackerone.com/reports/320693', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3743'} | null | {'https://github.com/herber/hekto/commit/1e5c75f8259ba0daf9b2600db3c246cda1934c46'} | {'https://github.com/herber/hekto/commit/1e5c75f8259ba0daf9b2600db3c246cda1934c46'} |
GHSA | GHSA-2pqj-h3vj-pqgw | Cross-Site Scripting in jquery | Affected versions of `jquery` are vulnerable to cross-site scripting. This occurs because the main `jquery` function uses a regular expression to differentiate between HTML and selectors, but does not properly anchor the regular expression. The result is that `jquery` may interpret HTML as selectors when given certain inputs, allowing for client side code execution.
## Proof of Concept
```
$("#log").html(
$("element[attribute='<img src=\"x\" onerror=\"alert(1)\" />']").html()
);
```
## Recommendation
Update to version 1.9.0 or later. | {'CVE-2012-6708'} | 2021-09-15T15:21:02Z | 2020-09-01T16:41:46Z | HIGH | 0 | {'CWE-64', 'CWE-79'} | {'http://packetstormsecurity.com/files/161972/Linksys-EA7500-2.0.8.194281-Cross-Site-Scripting.html', 'https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@%3Cdev.drill.apache.org%3E', 'https://github.com/jquery/jquery/commit/05531fc4080ae24070930d15ae0cea7ae056457d', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'https://github.com/advisories/GHSA-2pqj-h3vj-pqgw', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16011', 'http://packetstormsecurity.com/files/153237/RetireJS-CORS-Issue-Script-Execution.html', 'https://help.ecostruxureit.com/display/public/UADCE725/Security+fixes+in+StruxureWare+Data+Center+Expert+v7.6.0', 'https://bugs.jquery.com/ticket/11290', 'https://nvd.nist.gov/vuln/detail/CVE-2012-6708', 'http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00041.html', 'https://snyk.io/vuln/npm:jquery:20120206', 'https://bugs.jquery.com/ticket/12531', 'https://bugs.jquery.com/ticket/6429', 'http://www.securityfocus.com/bid/102792', 'https://www.npmjs.com/advisories/329', 'https://bugs.jquery.com/ticket/9521', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E'} | null | {'https://github.com/jquery/jquery/commit/05531fc4080ae24070930d15ae0cea7ae056457d'} | {'https://github.com/jquery/jquery/commit/05531fc4080ae24070930d15ae0cea7ae056457d'} |
GHSA | GHSA-5wmg-j84w-4jj4 | Arbitrary File Write via Archive Extraction in mholt/archiver | mholt/archiver golang package before e4ef56d48eb029648b0e895bb0b6a393ef0829c3 is vulnerable to directory traversal, allowing attackers to write to arbitrary files via a ../ (dot dot slash) in an archive entry that is mishandled during extraction. This vulnerability is also known as 'Zip-Slip'. | {'CVE-2018-1002207'} | 2022-04-12T22:36:10Z | 2022-02-15T01:57:18Z | MODERATE | 5.5 | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-1002207', 'https://github.com/advisories/GHSA-5wmg-j84w-4jj4', 'https://github.com/mholt/archiver/commit/e4ef56d48eb029648b0e895bb0b6a393ef0829c3', 'https://github.com/snyk/zip-slip-vulnerability', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMMHOLTARCHIVERCMDARCHIVER-50071', 'https://snyk.io/research/zip-slip-vulnerability', 'https://github.com/mholt/archiver/pull/65'} | null | {'https://github.com/mholt/archiver/commit/e4ef56d48eb029648b0e895bb0b6a393ef0829c3'} | {'https://github.com/mholt/archiver/commit/e4ef56d48eb029648b0e895bb0b6a393ef0829c3'} |
GHSA | GHSA-r92x-f52r-x54g | regular expression denial of service (ReDoS) | date-and-time is an npm package for manipulating date and time. In date-and-time before version 0.14.2, there a regular expression involved in parsing which can be exploited to to cause a denial of service. This is fixed in version 0.14.2. | {'CVE-2020-26289'} | 2021-01-07T22:33:13Z | 2020-12-24T20:49:02Z | HIGH | 7.5 | {'CWE-400'} | {'https://github.com/advisories/GHSA-r92x-f52r-x54g', 'https://github.com/knowledgecode/date-and-time/security/advisories/GHSA-r92x-f52r-x54g', 'https://github.com/knowledgecode/date-and-time/commit/9e4b501eacddccc8b1f559fb414f48472ee17c2a', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26289', 'https://www.npmjs.com/package/date-and-time', 'https://www.npmjs.com/advisories/1592'} | null | {'https://github.com/knowledgecode/date-and-time/commit/9e4b501eacddccc8b1f559fb414f48472ee17c2a'} | {'https://github.com/knowledgecode/date-and-time/commit/9e4b501eacddccc8b1f559fb414f48472ee17c2a'} |
GHSA | GHSA-vj62-g63v-f8mf | Validity check missing in Frontier | ### Impact
In the newly introduced signed Frontier-specific extrinsic for `pallet-ethereum`, a large part of transaction validation logic was only called in transaction pool validation, but not in block execution. Malicious validators can take advantage of this to put invalid transactions into a block.
The attack is limited in that the signature is always validated, and the majority of the validation is done again in the subsequent `pallet-evm` execution logic. However, do note that a chain ID replay attack was possible. In addition, spamming attacks are of main concerns, while they are limited by Substrate block size limits and other factors.
### Patches
The issue is patched in commit 146bb48849e5393004be5c88beefe76fdf009aba.
### References
Patch PR: https://github.com/paritytech/frontier/pull/495
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Frontier repo](https://github.com/paritytech/frontier/issues)
### Special thanks
Special thanks to @librelois, @nanocryk and the Moonbeam team for reporting and fixing this security vulnerability. | {'CVE-2021-41138'} | 2021-10-14T20:03:54Z | 2021-10-13T18:53:38Z | MODERATE | 5.3 | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-41138', 'https://github.com/paritytech/frontier/commit/146bb48849e5393004be5c88beefe76fdf009aba', 'https://github.com/advisories/GHSA-vj62-g63v-f8mf', 'https://github.com/paritytech/frontier/pull/497', 'https://github.com/paritytech/frontier/security/advisories/GHSA-vj62-g63v-f8mf', 'https://github.com/paritytech/frontier/pull/495'} | null | {'https://github.com/paritytech/frontier/commit/146bb48849e5393004be5c88beefe76fdf009aba'} | {'https://github.com/paritytech/frontier/commit/146bb48849e5393004be5c88beefe76fdf009aba'} |
GHSA | GHSA-x3r5-q6mj-m485 | Improper sanitization of target names | ### Impact
The tough library, prior to 0.12.0, does not properly sanitize target names when caching a repository, or when saving specific targets to an output directory. When targets are cached or saved, files could be overwritten with arbitrary content anywhere on the system.
AWS would like to thank https://github.com/jku for reporting this issue.
### Patches
A fix is available in version 0.12.0.
### Workarounds
No workarounds to this issue are known.
| {'CVE-2021-41149'} | 2021-10-20T15:39:06Z | 2021-10-19T20:16:15Z | HIGH | 8.2 | {'CWE-22'} | {'https://github.com/awslabs/tough/security/advisories/GHSA-x3r5-q6mj-m485', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41149', 'https://github.com/awslabs/tough/commit/1809b9bd1106d78a51fbea3071aa97a3530bac9a', 'https://github.com/advisories/GHSA-x3r5-q6mj-m485'} | null | {'https://github.com/awslabs/tough/commit/1809b9bd1106d78a51fbea3071aa97a3530bac9a'} | {'https://github.com/awslabs/tough/commit/1809b9bd1106d78a51fbea3071aa97a3530bac9a'} |
GHSA | GHSA-8xjq-8fcg-g5hw | Out-of-bounds Write in Pillow | An issue was discovered in Pillow before 8.1.1. In TiffDecode.c, there is a negative-offset memcpy with an invalid size. | {'CVE-2021-25290'} | 2021-12-06T21:37:00Z | 2021-03-29T16:35:36Z | HIGH | 7.5 | {'CWE-787'} | {'https://pillow.readthedocs.io/en/stable/releasenotes/8.1.1.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25290', 'https://github.com/python-pillow/Pillow/commit/86f02f7c70862a0954bfe8133736d352db978eaa', 'https://security.gentoo.org/glsa/202107-33', 'https://github.com/advisories/GHSA-8xjq-8fcg-g5hw', 'https://lists.debian.org/debian-lts-announce/2021/07/msg00018.html'} | null | {'https://github.com/python-pillow/Pillow/commit/86f02f7c70862a0954bfe8133736d352db978eaa'} | {'https://github.com/python-pillow/Pillow/commit/86f02f7c70862a0954bfe8133736d352db978eaa'} |
GHSA | GHSA-xgc3-m89p-vr3x | Heap buffer overflow in `Conv2DBackpropFilter` | ### Impact
An attacker can cause a heap buffer overflow to occur in `Conv2DBackpropFilter`:
```python
import tensorflow as tf
input_tensor = tf.constant([386.078431372549, 386.07843139643234],
shape=[1, 1, 1, 2], dtype=tf.float32)
filter_sizes = tf.constant([1, 1, 1, 1], shape=[4], dtype=tf.int32)
out_backprop = tf.constant([386.078431372549], shape=[1, 1, 1, 1],
dtype=tf.float32)
tf.raw_ops.Conv2DBackpropFilter(
input=input_tensor,
filter_sizes=filter_sizes,
out_backprop=out_backprop,
strides=[1, 66, 49, 1],
use_cudnn_on_gpu=True,
padding='VALID',
explicit_paddings=[],
data_format='NHWC',
dilations=[1, 1, 1, 1]
)
```
Alternatively, passing empty tensors also results in similar behavior:
```python
import tensorflow as tf
input_tensor = tf.constant([], shape=[0, 1, 1, 5], dtype=tf.float32)
filter_sizes = tf.constant([3, 8, 1, 1], shape=[4], dtype=tf.int32)
out_backprop = tf.constant([], shape=[0, 1, 1, 1], dtype=tf.float32)
tf.raw_ops.Conv2DBackpropFilter(
input=input_tensor,
filter_sizes=filter_sizes,
out_backprop=out_backprop,
strides=[1, 66, 49, 1],
use_cudnn_on_gpu=True,
padding='VALID',
explicit_paddings=[],
data_format='NHWC',
dilations=[1, 1, 1, 1]
)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/1b0296c3b8dd9bd948f924aa8cd62f87dbb7c3da/tensorflow/core/kernels/conv_grad_filter_ops.cc#L495-L497) computes the size of the filter tensor but does not validate that it matches the number of elements in `filter_sizes`. Later, when reading/writing to this buffer, code uses the value computed here, instead of the number of elements in the tensor.
### Patches
We have patched the issue in GitHub commit [c570e2ecfc822941335ad48f6e10df4e21f11c96](https://github.com/tensorflow/tensorflow/commit/c570e2ecfc822941335ad48f6e10df4e21f11c96).
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-29540'} | 2021-05-21T14:23:09Z | 2021-05-21T14:23:09Z | LOW | 2.5 | {'CWE-787', 'CWE-120'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-xgc3-m89p-vr3x', 'https://github.com/tensorflow/tensorflow/commit/c570e2ecfc822941335ad48f6e10df4e21f11c96', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29540', 'https://github.com/advisories/GHSA-xgc3-m89p-vr3x'} | null | {'https://github.com/tensorflow/tensorflow/commit/c570e2ecfc822941335ad48f6e10df4e21f11c96'} | {'https://github.com/tensorflow/tensorflow/commit/c570e2ecfc822941335ad48f6e10df4e21f11c96'} |
GHSA | GHSA-3c45-wgjp-7v9r | A single version of twisted does not respect the trustedRoot setting | Python Twisted 14.0 trustRoot is not respected in HTTP client | {'CVE-2014-7143'} | 2021-08-19T16:07:48Z | 2019-12-17T22:52:34Z | HIGH | 7.5 | {'CWE-295'} | {'https://nvd.nist.gov/vuln/detail/CVE-2014-7143', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/96135', 'https://github.com/twisted/twisted/commit/3b5942252f5f3e45862a0e12b266ab29e243cc33', 'https://security-tracker.debian.org/tracker/CVE-2014-7143', 'http://www.openwall.com/lists/oss-security/2014/09/22/2', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-7143', 'https://github.com/advisories/GHSA-3c45-wgjp-7v9r'} | null | {'https://github.com/twisted/twisted/commit/3b5942252f5f3e45862a0e12b266ab29e243cc33'} | {'https://github.com/twisted/twisted/commit/3b5942252f5f3e45862a0e12b266ab29e243cc33'} |
GHSA | GHSA-77gc-v2xv-rvvh | Out-of-bounds Read in Pillow | An issue was discovered in Pillow before 8.2.0. There is an out-of-bounds read in J2kDecode, in j2ku_graya_la. | {'CVE-2021-25287'} | 2022-03-03T21:47:12Z | 2021-06-08T18:49:02Z | CRITICAL | 9.1 | {'CWE-125'} | {'https://pillow.readthedocs.io/en/stable/releasenotes/8.2.0.html#cve-2021-25287-cve-2021-25288-fix-oob-read-in-jpeg2kdecode', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25287', 'https://github.com/python-pillow/Pillow/pull/5377/commits/3bf5eddb89afdf690eceaa52bc4d3546ba9a5f87', 'https://github.com/python-pillow/Pillow/pull/5377#issuecomment-833821470', 'https://security.gentoo.org/glsa/202107-33', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MQHA5HAIBOYI3R6HDWCLAGFTIQP767FL/', 'https://github.com/python-pillow/Pillow/commit/3bf5eddb89afdf690eceaa52bc4d3546ba9a5f87', 'https://github.com/advisories/GHSA-77gc-v2xv-rvvh'} | null | {'https://github.com/python-pillow/Pillow/commit/3bf5eddb89afdf690eceaa52bc4d3546ba9a5f87', 'https://github.com/python-pillow/Pillow/pull/5377/commits/3bf5eddb89afdf690eceaa52bc4d3546ba9a5f87'} | {'https://github.com/python-pillow/Pillow/commit/3bf5eddb89afdf690eceaa52bc4d3546ba9a5f87', 'https://github.com/python-pillow/Pillow/pull/5377/commits/3bf5eddb89afdf690eceaa52bc4d3546ba9a5f87'} |
GHSA | GHSA-xh2p-7p87-fhgh | Incorrect TCR calculation in batchLiquidateTroves() during Recovery Mode | TCR is temporarily miscalculated in the `batchLiquidateTroves` function during Recovery Mode.
The bug lies in [`batchLiquidateTroves` of `TroveManager`](https://github.com/liquity/dev/blob/7c83ea11378454629618b3808b16fbfda69ee3e5/packages/contracts/contracts/TroveManager.sol#L722).
When calculating system's entire collateral, we should also exclude the liquidated trove's surplus collateral, since liquidation closes the trove and makes the surplus collateral claimable by the trove owner. This means, this line of code should look like this:
```
vars.entireSystemColl = vars.entireSystemColl.sub(singleLiquidation.collToSendToSP).sub(singleLiquidation.collSurplus);
```
### Impact
The miscalculated entire collateral is used only to calculate the TCR and check if the system has been able to exit Recovery Mode. The miscalulation only persists temporarily, and within the`batchLiquidateTroves` transaction. Once the transaction completes the TCR and Recovery Mode will be calculated properly again. However, the bug could negatively impact the liquidation throughput and the gas efficiency gains from batching multiple liquidations in a single transaction.
In normal situations, the impact of the collateral surplus of a Trove on the global TCR would be tiny. For instance, we have calculated that liquidating a trove with a collateral representing 1% of the total system collateral (so in the order of at least $10M at current values), would lead to an extra 0.53% in the temporary miscalculation of TCR. So for this bug to be meaningful, in such a scenario, the resulting real TCR must be already be very close to the Recovery Mode boundary anyway - i.e. between 149.47% and 150%. The batch liquidation transaction should also be executed with a particular trove ordering to achieve the TCR distortion. When a different trove order for the liquidation transaction is selected, the bug has no impact. In summary, the bug only has a non-negligible impact in a very narrow, specific set of circumstances.
The potential effects of the bug after it occurs are:
- The next trove in the sequence is not liquidated because the `batchLiquidateTroves` function calculates a premature exit from Recovery Mode. It could be liquidated in a subsequent transaction if the price of Ether doesn’t recover.
- The next trove in the sequence has an ICR below 100% and it’s offset against the Stability Pool instead of redistributed among other troves because the function calculates a premature exit from Recovery Mode. For this to happen, the Ether price must have instantly plummeted by more than 10% (otherwise, the trove would have been already liquidated before).
- The next trove in the sequence is liquidated while its ICR is over the real TCR: the function calculates the TCR as being slightly too high, and thus can liquidate a trove that has ICR less than the calculated TCR, but greater than the true TCR. This is probably the worst outcome - however it is already possible to achieve the same effect, regardless of the bug. A liquidator can craft a `batchLiquidateTroves` transaction whereby they select troves for liquidation such that the TCR increases and makes a given trove liquidateable. To liquidate trove A, they can order troves such that they first liquidate troves which raise the TCR to between A's ICR and 150%. This is intended and expected behavior. As clearly stated in Liquity documentation, to be completely safe and guarantee immunity from liquidation in Recovery Mode, borrowers should keep their ICR above 150%.
We don't believe this bug creates a profitable exploit. Theoretically, and only in a very narrow set of circumstances, a liquidator could try to send a batch liquidation during Recovery Mode that lets the system very temporarily return to Normal Mode earlier than it should. In that case - _and only if the Ether price also happens to suddenly plummet by more than 10%_ - stability providers might take the haircut that should be taken by the borrowers (through redistribution).
### Patches
The problem has been patched in the source code but not on mainnet contracts. Liquity protocol is immutable, and this issue is not critical, so it doesn't merit a launch of a new version.
### Bug bounty
A reward of $1,000 (the maximum for its category) was awarded to Xiahong (`gaoxh06`) for reporting this bug.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [our repo](https://github.com/liquity/dev)
* Email us at [security@liquity.org](mailto:security@liquity.org)
| null | 2021-08-05T16:56:58Z | 2021-08-05T16:56:58Z | LOW | 3.1 | {'CWE-682'} | {'https://github.com/liquity/dev/security/advisories/GHSA-xh2p-7p87-fhgh', 'https://github.com/liquity/dev/commit/c69d0bae30b5457e89724d880851a03ba7477905', 'https://github.com/advisories/GHSA-xh2p-7p87-fhgh', 'https://www.npmjs.com/package/@liquity/contracts', 'https://github.com/liquity/dev/blob/7c83ea11378454629618b3808b16fbfda69ee3e5/packages/contracts/contracts/TroveManager.sol#L722'} | null | {'https://github.com/liquity/dev/commit/c69d0bae30b5457e89724d880851a03ba7477905'} | {'https://github.com/liquity/dev/commit/c69d0bae30b5457e89724d880851a03ba7477905'} |
GHSA | GHSA-rp2c-jrgp-cvr8 | Code injection in plupload | This affects the package plupload before 2.3.9. A file name containing JavaScript code could be uploaded and run. An attacker would need to trick a user to upload this kind of file. | {'CVE-2021-23562'} | 2021-12-16T15:32:31Z | 2021-12-16T15:32:31Z | MODERATE | 4.2 | {'CWE-434', 'CWE-75'} | {'https://github.com/moxiecode/plupload/commit/d12175d4b5fa799b994ee1bb17bfbeec55b386fb', 'https://snyk.io/vuln/SNYK-JS-PLUPLOAD-1583909', 'https://github.com/advisories/GHSA-rp2c-jrgp-cvr8', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-2306663', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23562', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBMOXIECODE-2306664', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARS-2306665', 'https://github.com/moxiecode/plupload/blob/master/js/jquery.plupload.queue/jquery.plupload.queue.js%23L226'} | null | {'https://github.com/moxiecode/plupload/commit/d12175d4b5fa799b994ee1bb17bfbeec55b386fb'} | {'https://github.com/moxiecode/plupload/commit/d12175d4b5fa799b994ee1bb17bfbeec55b386fb'} |
GHSA | GHSA-75p6-52g3-rqc8 | Privilege escalation vulnerability on Token Exchange feature | A privilege escalation flaw was found in the token exchange feature of keycloak. Missing authorization allows a client application holding a valid access token to exchange tokens for any target client by passing the client_id of the target. This could allow a client to gain unauthorized access to additional services. | {'CVE-2022-1245'} | 2022-05-02T19:51:27Z | 2022-04-26T21:21:00Z | MODERATE | 0 | {'CWE-284'} | {'https://github.com/advisories/GHSA-75p6-52g3-rqc8', 'https://github.com/keycloak/keycloak/security/advisories/GHSA-75p6-52g3-rqc8', 'https://github.com/keycloak/keycloak/commit/76d83f46fad94ebcbedaa49e6daad458e2894e52'} | null | {'https://github.com/keycloak/keycloak/commit/76d83f46fad94ebcbedaa49e6daad458e2894e52'} | {'https://github.com/keycloak/keycloak/commit/76d83f46fad94ebcbedaa49e6daad458e2894e52'} |
GHSA | GHSA-378p-hrq3-x4p3 | Cross-site scripting in Shopizer | A reflected cross-site scripting (XSS) vulnerability in Shopizer before 2.17.0 allows remote attackers to inject arbitrary web script or HTML via the ref parameter to a page about an arbitrary product, e.g., a product/insert-product-name-here.html/ref= URL. | {'CVE-2021-33562'} | 2021-06-08T23:08:20Z | 2021-06-08T23:08:20Z | MODERATE | 4.8 | {'CWE-79'} | {'https://www.exploit-db.com/exploits/49901', 'https://github.com/shopizer-ecommerce/shopizer/commit/197f8c78c8f673b957e41ca2c823afc654c19271', 'https://github.com/advisories/GHSA-378p-hrq3-x4p3', 'https://github.com/shopizer-ecommerce/shopizer/compare/2.16.0...2.17.0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-33562'} | null | {'https://github.com/shopizer-ecommerce/shopizer/commit/197f8c78c8f673b957e41ca2c823afc654c19271'} | {'https://github.com/shopizer-ecommerce/shopizer/commit/197f8c78c8f673b957e41ca2c823afc654c19271'} |
GHSA | GHSA-f248-v4qh-x2r6 | Improper Certificate Validation in blackduck | Synopsys hub-rest-api-python (aka blackduck on PyPI) version 0.0.25 - 0.0.52 does not validate SSL certificates in certain cases. | {'CVE-2020-27589'} | 2021-04-20T16:29:41Z | 2021-04-20T16:29:41Z | HIGH | 7.5 | {'CWE-295'} | {'https://github.com/blackducksoftware/hub-rest-api-python/pull/113/commits/273b27d0de1004389dd8cf43c40b1197c787e7cd', 'https://pypi.org/project/blackduck/', 'https://community.synopsys.com/s/question/0D52H00005JCZAXSA5/announcement-black-duck-defect-identified', 'https://github.com/blackducksoftware/hub-rest-api-python', 'https://github.com/advisories/GHSA-f248-v4qh-x2r6', 'https://www.optiv.com/explore-optiv-insights/source-zero/certificate-validation-disabled-black-duck-api-wrapper', 'https://nvd.nist.gov/vuln/detail/CVE-2020-27589'} | null | {'https://github.com/blackducksoftware/hub-rest-api-python/pull/113/commits/273b27d0de1004389dd8cf43c40b1197c787e7cd'} | {'https://github.com/blackducksoftware/hub-rest-api-python/pull/113/commits/273b27d0de1004389dd8cf43c40b1197c787e7cd'} |
GHSA | GHSA-2xvj-j3qh-x8c3 | High severity vulnerability that affects private_address_check | private_address_check ruby gem before 0.5.0 is vulnerable to a time-of-check time-of-use (TOCTOU) race condition due to the address the socket uses not being checked. DNS entries with a TTL of 0 can trigger this case where the initial resolution is a public address but the subsequent resolution is a private address. | {'CVE-2018-3759'} | 2021-01-08T20:05:48Z | 2018-07-31T18:13:05Z | HIGH | 0 | {'CWE-362'} | {'https://github.com/jtdowney/private_address_check/commit/4068228187db87fea7577f7020099399772bb147', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3759', 'https://github.com/advisories/GHSA-2xvj-j3qh-x8c3'} | null | {'https://github.com/jtdowney/private_address_check/commit/4068228187db87fea7577f7020099399772bb147'} | {'https://github.com/jtdowney/private_address_check/commit/4068228187db87fea7577f7020099399772bb147'} |
GHSA | GHSA-gwpx-q2h9-wxgx | elgg is vulnerable to Authorization Bypass Through User-Controlled Key | elgg is vulnerable to Authorization Bypass Through User-Controlled Key | {'CVE-2021-3964'} | 2021-12-03T20:43:25Z | 2021-12-03T20:43:25Z | MODERATE | 5.9 | {'CWE-639'} | {'https://huntr.dev/bounties/a4df45d6-b739-4299-967f-c960b569383a', 'https://github.com/advisories/GHSA-gwpx-q2h9-wxgx', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3964', 'https://github.com/elgg/elgg/commit/d9fcad76ee380ea17edd61d13d0f87828ea3f744'} | null | {'https://github.com/elgg/elgg/commit/d9fcad76ee380ea17edd61d13d0f87828ea3f744'} | {'https://github.com/elgg/elgg/commit/d9fcad76ee380ea17edd61d13d0f87828ea3f744'} |
GHSA | GHSA-35fg-hjcr-j65f | Information exposure in xwiki-platform | ### Impact
It's possible to guess if a user has an account on the wiki by using the "Forgot your password" form, even if the wiki is closed to guest users.
### Patches
The problem has been patched on XWiki 12.10.9, 13.4.1 and 13.6RC1.
### Workarounds
There's no easy workaround other than applying the upgrade.
### References
https://jira.xwiki.org/browse/XWIKI-18787
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [JIRA](https://jira.xwiki.org)
* Email us at [XWiki Security Mailing list](mailto:security@xwiki.org)
| {'CVE-2022-23619'} | 2022-02-16T22:23:42Z | 2022-02-09T21:51:19Z | MODERATE | 5.3 | {'CWE-200', 'CWE-640'} | {'https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-35fg-hjcr-j65f', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23619', 'https://jira.xwiki.org/browse/XWIKI-18787', 'https://github.com/advisories/GHSA-35fg-hjcr-j65f', 'https://github.com/xwiki/xwiki-platform/commit/d8a3cce48e0ac1a0f4a3cea7a19747382d9c9494'} | null | {'https://github.com/xwiki/xwiki-platform/commit/d8a3cce48e0ac1a0f4a3cea7a19747382d9c9494'} | {'https://github.com/xwiki/xwiki-platform/commit/d8a3cce48e0ac1a0f4a3cea7a19747382d9c9494'} |
GHSA | GHSA-x2w5-725j-gf2g | Prototype Pollution in convict | An attacker can inject attributes that are used in other components and override existing attributes with ones that have incompatible type, which may lead to a crash.
The main use case of Convict is for handling server-side configurations written by the admins owning the servers, and not random users. So it's unlikely that an admin would deliberately sabotage their own server. Still a situation can happen where an admin not knowledgeable about JavaScript could be tricked by an attacker into writing the malicious JavaScript code into some config files.
The problem is patched in `convict@6.2.2`. Users should upgrade to `convict@6.2.2`. There is no way for users to fix or remediate the vulnerability without upgrading. | {'CVE-2022-22143'} | 2022-05-03T02:25:28Z | 2022-04-20T16:21:03Z | HIGH | 8.4 | {'CWE-1321'} | {'https://github.com/mozilla/node-convict/blob/5eb1314f85346760a3c31cb14510f2f0af11d0d3/packages/convict/src/main.js%23L569', 'https://snyk.io/vuln/SNYK-JS-CONVICT-2340604', 'https://www.huntr.dev/bounties/1-npm-convict/', 'https://github.com/mozilla/node-convict/releases/tag/v6.2.2', 'https://github.com/mozilla/node-convict/pull/384', 'https://github.com/advisories/GHSA-x2w5-725j-gf2g', 'https://github.com/mozilla/node-convict/commit/3b86be087d8f14681a9c889d45da7fe3ad9cd880', 'https://github.com/mozilla/node-convict/security/advisories/GHSA-x2w5-725j-gf2g', 'https://nvd.nist.gov/vuln/detail/CVE-2022-22143'} | null | {'https://github.com/mozilla/node-convict/commit/3b86be087d8f14681a9c889d45da7fe3ad9cd880'} | {'https://github.com/mozilla/node-convict/commit/3b86be087d8f14681a9c889d45da7fe3ad9cd880'} |
GHSA | GHSA-673x-f5wx-fxpw | Cross Site Scripting and RCE in baserCMS | baserCMS 4.3.6 and earlier is affected by Cross Site Scripting (XSS) and Remote Code Execution (RCE).
* Impact: XSS to RCE via Arbitrary file upload.
* Attack vector is: Administrator must be logged in.
* Components are: ThemeFilesController.php, UploaderFilesController.php.
* Tested baserCMS Version : 4.3.6 (Latest)
* Affected baserCMS Version : 4.2.0 ~ 4.3.6 (XSS), 3.0.10 ~ 4.3.6 (RCE)
* Patches : https://basercms.net/security/20200827
Found by Vulnerability Research team in [Flatt Security Inc.](https://flatt.tech/) | {'CVE-2020-15159'} | 2022-04-19T19:02:28Z | 2020-08-28T21:45:15Z | LOW | 7.6 | {'CWE-79'} | {'https://basercms.net/security/20200827', 'https://github.com/baserproject/basercms/security/advisories/GHSA-673x-f5wx-fxpw', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15159', 'https://github.com/baserproject/basercms/commit/16a7b3cd09a0ca355474119c76897eac2034a66d', 'https://github.com/advisories/GHSA-673x-f5wx-fxpw'} | null | {'https://github.com/baserproject/basercms/commit/16a7b3cd09a0ca355474119c76897eac2034a66d'} | {'https://github.com/baserproject/basercms/commit/16a7b3cd09a0ca355474119c76897eac2034a66d'} |
GHSA | GHSA-hf2m-j98r-4fqw | API token verification can be bypassed in NodeBB | ### Impact
Incorrect logic present in the token verification step unintentionally allowed master token access to the API.
### Patches
The vulnerability has been patch as of v1.18.5.
### Workarounds
Cherry-pick commit hash 04dab1d550cdebf4c1567bca9a51f8b9ca48a500 to receive this patch in lieu of a full upgrade.
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@nodebb.org](mailto:security@nodebb.org)
| {'CVE-2021-43786'} | 2022-04-19T19:03:13Z | 2021-11-30T22:21:05Z | CRITICAL | 9.8 | {'CWE-287'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-43786', 'https://github.com/advisories/GHSA-hf2m-j98r-4fqw', 'https://github.com/NodeBB/NodeBB/releases/tag/v1.18.5', 'https://github.com/NodeBB/NodeBB/security/advisories/GHSA-hf2m-j98r-4fqw', 'https://github.com/NodeBB/NodeBB/commit/04dab1d550cdebf4c1567bca9a51f8b9ca48a500'} | null | {'https://github.com/NodeBB/NodeBB/commit/04dab1d550cdebf4c1567bca9a51f8b9ca48a500'} | {'https://github.com/NodeBB/NodeBB/commit/04dab1d550cdebf4c1567bca9a51f8b9ca48a500'} |
GHSA | GHSA-v88g-cgmw-v5xw | Prototype Pollution in Ajv | An issue was discovered in ajv.validate() in Ajv (aka Another JSON Schema Validator) 6.12.2. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code.) | {'CVE-2020-15366'} | 2022-02-10T23:30:59Z | 2022-02-10T23:30:59Z | MODERATE | 5.6 | {'CWE-915'} | {'https://github.com/ajv-validator/ajv/commit/65b2f7d76b190ac63a0d4e9154c712d7aa37049f', 'https://hackerone.com/bugs?subject=user&report_id=894259', 'https://github.com/advisories/GHSA-v88g-cgmw-v5xw', 'https://github.com/ajv-validator/ajv/releases/tag/v6.12.3', 'https://github.com/ajv-validator/ajv/tags', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15366'} | null | {'https://github.com/ajv-validator/ajv/commit/65b2f7d76b190ac63a0d4e9154c712d7aa37049f'} | {'https://github.com/ajv-validator/ajv/commit/65b2f7d76b190ac63a0d4e9154c712d7aa37049f'} |
GHSA | GHSA-579h-mv94-g4gp | Privilege Escalation in Kubernetes | In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in the kube-apiserver allowed specially crafted requests to establish a connection through the Kubernetes API server to backend servers, then send arbitrary requests over the same connection directly to the backend, authenticated with the Kubernetes API server's TLS credentials used to establish the backend connection. | {'CVE-2018-1002105'} | 2022-04-12T22:34:38Z | 2022-02-15T01:57:18Z | CRITICAL | 9.8 | {'CWE-269'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-1002105', 'https://access.redhat.com/errata/RHSA-2018:3624', 'https://www.openwall.com/lists/oss-security/2019/06/28/2', 'https://github.com/kubernetes/kubernetes/commit/2257c1ecbe3c0cf71dd50b82752ae189c94ec905', 'https://access.redhat.com/errata/RHSA-2018:3752', 'https://access.redhat.com/errata/RHSA-2018:3754', 'https://security.netapp.com/advisory/ntap-20190416-0001/', 'https://github.com/kubernetes/kubernetes/issues/71411', 'https://access.redhat.com/errata/RHSA-2018:3549', 'https://github.com/evict/poc_CVE-2018-1002105', 'https://access.redhat.com/errata/RHSA-2018:3537', 'https://access.redhat.com/errata/RHSA-2018:3551', 'https://access.redhat.com/errata/RHSA-2018:3598', 'https://github.com/advisories/GHSA-579h-mv94-g4gp', 'https://www.exploit-db.com/exploits/46053', 'https://www.exploit-db.com/exploits/46053/', 'https://access.redhat.com/errata/RHSA-2018:3742', 'https://groups.google.com/forum/#!topic/kubernetes-announce/GVllWCg6L88', 'https://www.openwall.com/lists/oss-security/2019/07/06/3', 'https://www.openwall.com/lists/oss-security/2019/07/06/4', 'https://www.exploit-db.com/exploits/46052/', 'https://lists.opensuse.org/opensuse-security-announce/2020-04/msg00041.html', 'https://www.coalfire.com/The-Coalfire-Blog/December-2018/Kubernetes-Vulnerability-What-You-Can-Should-Do', 'https://www.securityfocus.com/bid/106068'} | null | {'https://github.com/kubernetes/kubernetes/commit/2257c1ecbe3c0cf71dd50b82752ae189c94ec905'} | {'https://github.com/kubernetes/kubernetes/commit/2257c1ecbe3c0cf71dd50b82752ae189c94ec905'} |
GHSA | GHSA-xpfv-89vg-r562 | Cross Site Request Forgery in Moodle | A flaw was found in Moodle in versions 3.11 to 3.11.4, 3.10 to 3.10.8, 3.9 to 3.9.11 and earlier unsupported versions. The "delete badge alignment" functionality did not include the necessary token check to prevent a CSRF risk. | {'CVE-2022-0335'} | 2022-02-02T16:06:35Z | 2022-01-28T22:07:23Z | HIGH | 8.8 | {'CWE-352'} | {'https://github.com/moodle/moodle/commit/d40cc61eba229c6d1f47b9a525022fbc9136b9f6', 'https://github.com/advisories/GHSA-xpfv-89vg-r562', 'https://bugzilla.redhat.com/show_bug.cgi?id=2043666', 'https://moodle.org/mod/forum/discuss.php?d=431103', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0335'} | null | {'https://github.com/moodle/moodle/commit/d40cc61eba229c6d1f47b9a525022fbc9136b9f6'} | {'https://github.com/moodle/moodle/commit/d40cc61eba229c6d1f47b9a525022fbc9136b9f6'} |
GHSA | GHSA-68wg-qv6r-j4vp | SQL Injection in usmanhalalit/pixie | Pixie versions 1.0.x before 1.0.3, and 2.0.x before 2.0.2 allow SQL Injection in the limit() function due to improper sanitization. | {'CVE-2019-10766'} | 2021-08-18T22:44:59Z | 2019-11-20T17:44:54Z | CRITICAL | 9.8 | {'CWE-89'} | {'https://github.com/advisories/GHSA-68wg-qv6r-j4vp', 'https://snyk.io/vuln/SNYK-PHP-USMANHALALITPIXIE-534879', 'https://github.com/usmanhalalit/pixie/commit/9bd991021abbcbfb19347a07dca8b7e518b8abc9', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10766'} | null | {'https://github.com/usmanhalalit/pixie/commit/9bd991021abbcbfb19347a07dca8b7e518b8abc9'} | {'https://github.com/usmanhalalit/pixie/commit/9bd991021abbcbfb19347a07dca8b7e518b8abc9'} |
GHSA | GHSA-23f7-99jx-m54r | Remote code execution in dependabot-core branch names when cloning | ### Impact
Remote code execution vulnerability in `dependabot-common` and `dependabot-go_modules` when a source branch name contains malicious injectable bash code.
For example, if Dependabot is configured to use the following source branch name: `"/$({curl,127.0.0.1})"`, Dependabot will make a HTTP request to the following URL: 127.0.0.1 when cloning the source repository.
When Dependabot is configured to clone the source repository during an update, Dependabot runs a shell command to git clone the repository:
```bash
git clone --no-tags --no-recurse-submodules --depth=1 --branch=<BRANCH> --single-branch <GITHUB_REPO_URL> repo/contents/path
```
Dependabot will always clone the source repository for `go_modules` during the file fetching step and can be configured to clone the repository for other package managers using the `FileFetcher` class from `dependabot-common`.
```ruby
source = Dependabot::Source.new(
provider: "github",
repo: "repo/name",
directory: "/",
branch: "/$({curl,127.0.0.1})",
)
repo_contents_path = "./file/path"
fetcher = Dependabot::FileFetchers.for_package_manager("bundler").
new(source: source, credentials: [],
repo_contents_path: repo_contents_path)
fetcher.clone_repo_contents
```
### Patches
The fix was applied to version `0.125.1`: https://github.com/dependabot/dependabot-core/pull/2727
### Workarounds
Escape the branch name prior to passing it to the `Dependabot::Source` class.
For example using `shellwords`:
```ruby
require "shellwords"
branch = Shellwords.escape("/$({curl,127.0.0.1})")
source = Dependabot::Source.new(
provider: "github",
repo: "repo/name",
directory: "/",
branch: branch,
)
``` | {'CVE-2020-26222'} | 2022-04-19T19:02:40Z | 2020-11-13T15:47:50Z | LOW | 8.7 | {'CWE-74'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-26222', 'https://github.com/advisories/GHSA-23f7-99jx-m54r', 'https://rubygems.org/gems/dependabot-common', 'https://github.com/dependabot/dependabot-core/security/advisories/GHSA-23f7-99jx-m54r', 'https://rubygems.org/gems/dependabot-omnibus', 'https://github.com/dependabot/dependabot-core/pull/2727', 'https://github.com/dependabot/dependabot-core/commit/e089116abbe284425b976f7920e502b8e83a61b5'} | null | {'https://github.com/dependabot/dependabot-core/commit/e089116abbe284425b976f7920e502b8e83a61b5'} | {'https://github.com/dependabot/dependabot-core/commit/e089116abbe284425b976f7920e502b8e83a61b5'} |
GHSA | GHSA-85rr-4rh9-hhwh | Memory leak in Nanopb | ### Impact
Decoding specifically formed message can leak memory if dynamic allocation is enabled and an oneof field contains a static submessage that contains a dynamic field, and the message being decoded contains the submessage multiple times. This is rare in normal messages, but it is a concern when untrusted data is parsed.
### Patches
Preliminary patch is [available on git](https://github.com/nanopb/nanopb/commit/edf6dcbffee4d614ac0c2c1b258ab95185bdb6e9) and problem will be patched in versions 0.3.9.7 and 0.4.4 once testing has been completed.
### Workarounds
Following workarounds are available:
* Set the option `no_unions` for the oneof field. This will generate fields as separate instead of C union, and avoids triggering the problematic code.
* Set the type of the submessage field inside oneof to `FT_POINTER`. This way the whole submessage will be dynamically allocated and the problematic code is not executed.
* Use an arena allocator for nanopb, to make sure all memory can be released afterwards.
### References
Bug report: https://github.com/nanopb/nanopb/issues/615
### For more information
If you have any questions or comments about this advisory, comment on the bug report linked above. | {'CVE-2020-26243'} | 2021-01-07T22:39:40Z | 2020-11-25T16:53:27Z | MODERATE | 7.5 | {'CWE-119', 'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-26243', 'https://github.com/nanopb/nanopb/commit/4fe23595732b6f1254cfc11a9b8d6da900b55b0c', 'https://github.com/nanopb/nanopb/security/advisories/GHSA-85rr-4rh9-hhwh', 'https://github.com/advisories/GHSA-85rr-4rh9-hhwh', 'https://github.com/nanopb/nanopb/issues/615', 'https://github.com/nanopb/nanopb/blob/2b48a361786dfb1f63d229840217a93aae064667/CHANGELOG.txt'} | null | {'https://github.com/nanopb/nanopb/commit/4fe23595732b6f1254cfc11a9b8d6da900b55b0c'} | {'https://github.com/nanopb/nanopb/commit/4fe23595732b6f1254cfc11a9b8d6da900b55b0c'} |
GHSA | GHSA-384w-5v3f-q499 | Base class whitelist configuration ignored in OAuthenticator | ### Impact
__What goes wrong?__
The deprecated (in jupyterhub 1.2) configuration `Authenticator.whitelist`, which should be transparently mapped to `Authenticator.allowed_users` with a warning, is instead ignored by OAuthenticator classes, resulting in the same behavior as if this configuration has not been set. If this is the only mechanism of authorization restriction (i.e. no group or team restrictions in configuration) then all authenticated users will be allowed. Provider-based restrictions, including deprecated values such as `GitHubOAuthenticator.org_whitelist` are **not** affected.
__Who is impacted?__
All users of OAuthenticator 0.12.0 and 0.12.1 with JupyterHub 1.2 (JupyterHub Helm chart 0.10.0-0.10.5) who use the `admin.whitelist.users` configuration in the jupyterhub helm chart or the `c.Authenticator.whitelist` configuration directly. Users of other deprecated configuration, e.g. `c.GitHubOAuthenticator.team_whitelist` are **not** affected.
If you see a log line like this and expect a specific list of allowed usernames:
```
[I 2020-11-27 16:51:54.528 JupyterHub app:1717] Not using allowed_users. Any authenticated user will be allowed.
```
you are likely affected.
### Patches
- Replacing deprecated `c.Authenticator.whitelist = ...` with `c.Authenticator.allowed_users = ...` avoids the issue.
- Update oauthenticator to 0.12.2
- Update jupyterhub helm chart to 0.10.6
If any users have been authorized during this time who should not have been, they must be deleted via the API or admin interface, [per the documentation](https://jupyterhub.readthedocs.io/en/1.2.2/getting-started/authenticators-users-basics.html#add-or-remove-users-from-the-hub).
### Workarounds
Replacing `c.Authenticator.whitelist = ...` with `c.Authenticator.allowed_users = ...` avoids the issue.
In the jupyterhub helm chart prior to 0.10.6, this can be done via `hub.extraConfig`:
```yaml
auth:
allowedUsers:
- user1
- user2
hub:
extraConfig:
allowedUsers: |
# set new field not exposed in helm chart < 0.10.6
set_config_if_not_none(c.Authenticator, "allowed_users", "auth.allowedUsers")
```
### For more information
If you have any questions or comments about this advisory:
* Open a thread [on the Jupyter forum](http://discourse.jupyter.org)
* Email us at [security@ipython.org](mailto:security@ipython.org) | {'CVE-2020-26250'} | 2021-01-07T22:38:55Z | 2020-12-01T20:25:00Z | HIGH | 6.3 | {'CWE-863'} | {'https://github.com/advisories/GHSA-384w-5v3f-q499', 'https://jupyterhub.readthedocs.io/en/1.2.2/getting-started/authenticators-users-basics.html#add-or-remove-users-from-the-hub', 'https://github.com/jupyterhub/oauthenticator/security/advisories/GHSA-384w-5v3f-q499', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26250', 'https://github.com/jupyterhub/oauthenticator/blob/master/docs/source/changelog.md#0122---2020-11-30', 'https://github.com/jupyterhub/oauthenticator/commit/a4aac191c16cf6281f3d346615aefa75702b02d7'} | null | {'https://github.com/jupyterhub/oauthenticator/commit/a4aac191c16cf6281f3d346615aefa75702b02d7'} | {'https://github.com/jupyterhub/oauthenticator/commit/a4aac191c16cf6281f3d346615aefa75702b02d7'} |
GHSA | GHSA-gcvh-66ff-4mwm | `CHECK`-failures in Tensorflow | ### Impact
The [implementation of `MapStage`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/map_stage_op.cc#L519-L550) is vulnerable a `CHECK`-fail if the key tensor is not a scalar:
```python
import tensorflow as tf
import numpy as np
tf.raw_ops.MapStage(
key = tf.constant(value=[4], shape= (1,2), dtype=tf.int64),
indices = np.array([[6]]),
values = np.array([-60]),
dtypes = [tf.int64], capacity=0, memory_limit=0,
container='', shared_name='', name=None
)
```
### Patches
We have patched the issue in GitHub commit [f57315566d7094f322b784947093406c2aea0d7d](https://github.com/tensorflow/tensorflow/commit/f57315566d7094f322b784947093406c2aea0d7d).
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Faysal Hossain Shezan from University of Virginia.
~ | {'CVE-2022-21734'} | 2022-02-11T16:55:37Z | 2022-02-10T00:21:12Z | MODERATE | 6.5 | {'CWE-617', 'CWE-843'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-21734', 'https://github.com/advisories/GHSA-gcvh-66ff-4mwm', 'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/map_stage_op.cc#L519-L550', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-gcvh-66ff-4mwm', 'https://github.com/tensorflow/tensorflow/commit/f57315566d7094f322b784947093406c2aea0d7d'} | null | {'https://github.com/tensorflow/tensorflow/commit/f57315566d7094f322b784947093406c2aea0d7d'} | {'https://github.com/tensorflow/tensorflow/commit/f57315566d7094f322b784947093406c2aea0d7d'} |
GHSA | GHSA-crf2-xm6x-46p6 | Observable Timing Discrepancy in OpenMage LTS | ### Impact
This vulnerability allows to circumvent the **formkey protection** in the Admin Interface and increases the attack surface for **Cross Site Request Forgery** attacks
### Patches
The latest OpenMage Versions up from 19.4.6 and 20.0.2 have this Issue solved
### References
Related to Adobes CVE-2020-9690 ( https://helpx.adobe.com/security/products/magento/apsb20-47.html )
fixed in Magento2 https://github.com/magento/magento2/commit/52d72b8010c9cecb5b8e3d98ec5edc1ddcc65fb4
as part of 2.4.0/2.3.5-p2 | {'CVE-2020-15151'} | 2022-04-19T19:02:33Z | 2020-08-19T18:02:36Z | HIGH | 8 | {'CWE-352', 'CWE-203'} | {'https://helpx.adobe.com/security/products/magento/apsb20-47.html', 'https://github.com/advisories/GHSA-crf2-xm6x-46p6', 'https://github.com/OpenMage/magento-lts/commit/7c526bc6a6a51b57a1bab4c60f104dc36cde347a', 'https://github.com/OpenMage/magento-lts/security/advisories/GHSA-crf2-xm6x-46p6', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15151'} | null | {'https://github.com/OpenMage/magento-lts/commit/7c526bc6a6a51b57a1bab4c60f104dc36cde347a'} | {'https://github.com/OpenMage/magento-lts/commit/7c526bc6a6a51b57a1bab4c60f104dc36cde347a'} |
GHSA | GHSA-cghx-9gcr-r42x | Path Traversal in the Java Kubernetes Client | Kubernetes Java client libraries in version 10.0.0 and versions prior to 9.0.1 allow writes to paths outside of the current directory when copying multiple files from a remote pod which sends a maliciously crafted archive. This can potentially overwrite any files on the system of the process executing the client code. | {'CVE-2020-8570'} | 2021-04-12T20:53:33Z | 2021-01-29T18:12:54Z | MODERATE | 7.5 | {'CWE-22'} | {'https://groups.google.com/g/kubernetes-security-announce/c/sd5h73sFPrg', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8570', 'https://lists.apache.org/thread.html/r0c76b3d0be348f788cd947054141de0229af00c540564711e828fd40@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/rdb223e1b82e3d7d8e4eaddce8dd1ab87252e3935cc41c859f49767b6@%3Ccommits.druid.apache.org%3E', 'https://github.com/kubernetes-client/java/issues/1491', 'https://github.com/advisories/GHSA-cghx-9gcr-r42x', 'https://github.com/kubernetes-client/java/pull/1450', 'https://lists.apache.org/thread.html/rcafa485d63550657f068775801aeb706b7a07140a8ebbdef822b3bb3@%3Ccommits.druid.apache.org%3E', 'https://github.com/kubernetes-client/java/commit/858316ae8bc1145005a0310e1f65f95d2389a589', 'https://lists.apache.org/thread.html/r1975078e44d96f2a199aa90aa874b57a202eaf7f25f2fde6d1c44942@%3Ccommits.druid.apache.org%3E'} | null | {'https://github.com/kubernetes-client/java/commit/858316ae8bc1145005a0310e1f65f95d2389a589'} | {'https://github.com/kubernetes-client/java/commit/858316ae8bc1145005a0310e1f65f95d2389a589'} |
GHSA | GHSA-jxfh-8wgv-vfr2 | Prototype pollution in dojo | In affected versions of dojo (NPM package), the deepCopy method is vulnerable to Prototype Pollution.
Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects.
An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values.
This has been patched in versions 1.12.8, 1.13.7, 1.14.6, 1.15.3 and 1.16.2 | {'CVE-2020-5258'} | 2022-04-01T20:24:08Z | 2020-03-10T18:03:14Z | HIGH | 7.7 | {'CWE-94', 'CWE-74', 'CWE-1321'} | {'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://github.com/advisories/GHSA-jxfh-8wgv-vfr2', 'https://lists.apache.org/thread.html/r665fcc152bd0fec9f71511a6c2435ff24d3a71386b01b1a6df326fd3@%3Cusers.qpid.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2020/03/msg00012.html', 'https://github.com/dojo/dojo/commit/20a00afb68f5587946dc76fbeaa68c39bda2171d', 'https://www.oracle.com/security-alerts/cpujul2020.html', 'https://lists.apache.org/thread.html/rf481b3f25f05c52ba4e24991a941c1a6e88d281c6c9360a806554d00@%3Cusers.qpid.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://lists.apache.org/thread.html/r3638722360d7ae95f874280518b8d987d799a76df7a9cd78eac33a1b@%3Cusers.qpid.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5258', 'https://github.com/dojo/dojo/security/advisories/GHSA-jxfh-8wgv-vfr2', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/dojo/dojo/commit/20a00afb68f5587946dc76fbeaa68c39bda2171d'} | {'https://github.com/dojo/dojo/commit/20a00afb68f5587946dc76fbeaa68c39bda2171d'} |
GHSA | GHSA-832h-xg76-4gv6 | ReDoS in brace-expansion | Affected versions of `brace-expansion` are vulnerable to a regular expression denial of service condition.
## Proof of Concept
```
var expand = require('brace-expansion');
expand('{,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,\n}');
```
## Recommendation
Update to version 1.1.7 or later. | {'CVE-2017-18077'} | 2021-09-03T22:10:25Z | 2018-01-29T15:50:46Z | HIGH | 7.5 | {'CWE-20'} | {'https://www.npmjs.com/advisories/338', 'https://github.com/juliangruber/brace-expansion/issues/33', 'https://bugs.debian.org/862712', 'https://nvd.nist.gov/vuln/detail/CVE-2017-18077', 'https://nodesecurity.io/advisories/338', 'https://github.com/juliangruber/brace-expansion/pull/35/commits/b13381281cead487cbdbfd6a69fb097ea5e456c3', 'https://github.com/advisories/GHSA-832h-xg76-4gv6', 'https://github.com/juliangruber/brace-expansion/pull/35'} | null | {'https://github.com/juliangruber/brace-expansion/pull/35/commits/b13381281cead487cbdbfd6a69fb097ea5e456c3'} | {'https://github.com/juliangruber/brace-expansion/pull/35/commits/b13381281cead487cbdbfd6a69fb097ea5e456c3'} |
GHSA | GHSA-8h2j-cgx8-6xv7 | Cross-Site Request Forgery (CSRF) in FastAPI | ### Impact
FastAPI versions lower than `0.65.2` that used cookies for authentication in path operations that received JSON payloads sent by browsers were vulnerable to a Cross-Site Request Forgery (CSRF) attack.
In versions lower than `0.65.2`, FastAPI would try to read the request payload as JSON even if the `content-type` header sent was not set to `application/json` or a compatible JSON media type (e.g. `application/geo+json`).
So, a request with a content type of `text/plain` containing JSON data would be accepted and the JSON data would be extracted.
But requests with content type `text/plain` are exempt from [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) preflights, for being considered [Simple requests](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS#simple_requests). So, the browser would execute them right away including cookies, and the text content could be a JSON string that would be parsed and accepted by the FastAPI application.
### Patches
This is fixed in FastAPI `0.65.2`.
The request data is now parsed as JSON only if the `content-type` header is `application/json` or another JSON compatible media type like `application/geo+json`.
### Workarounds
It's best to upgrade to the latest FastAPI.
But still, it would be possible to add a middleware or a dependency that checks the `content-type` header and aborts the request if it is not `application/json` or another JSON compatible content type.
### References
* [CORS on Mozilla web docs](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS)
* [This answer on StackExchange](https://security.stackexchange.com/questions/157528/ways-to-bypass-browsers-cors-policy/157531#157531)
* [OWASP CSRF](https://owasp.org/www-community/attacks/csrf)
* Fixed in PR [#2118](https://github.com/tiangolo/fastapi/pull/2118)
### For more information
If you have any questions or comments, write to [security@tiangolo.com](mailto:security@tiangolo.com) | {'CVE-2021-32677'} | 2022-04-19T19:02:59Z | 2021-06-10T15:43:54Z | HIGH | 8.2 | {'CWE-352'} | {'https://github.com/tiangolo/fastapi/security/advisories/GHSA-8h2j-cgx8-6xv7', 'https://github.com/tiangolo/fastapi/commit/fa7e3c996edf2d5482fff8f9d890ac2390dede4d', 'https://github.com/advisories/GHSA-8h2j-cgx8-6xv7', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MATAWX25TYKNEKLDMKWNLYDB34UWTROA/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32677'} | null | {'https://github.com/tiangolo/fastapi/commit/fa7e3c996edf2d5482fff8f9d890ac2390dede4d'} | {'https://github.com/tiangolo/fastapi/commit/fa7e3c996edf2d5482fff8f9d890ac2390dede4d'} |
GHSA | GHSA-vr8q-g5c7-m54m | XXE in Nokogiri | ### Severity
Nokogiri maintainers have evaluated this as [__Low Severity__ (CVSS3 2.6)](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N).
### Description
In Nokogiri versions <= 1.11.0.rc3, XML Schemas parsed by `Nokogiri::XML::Schema` are **trusted** by default, allowing external resources to be accessed over the network, potentially enabling XXE or SSRF attacks.
This behavior is counter to the security policy followed by Nokogiri maintainers, which is to treat all input as **untrusted** by default whenever possible.
Please note that this security fix was pushed into a new minor version, 1.11.x, rather than a patch release to the 1.10.x branch, because it is a breaking change for some schemas and the risk was assessed to be "Low Severity".
### Affected Versions
Nokogiri `<= 1.10.10` as well as prereleases `1.11.0.rc1`, `1.11.0.rc2`, and `1.11.0.rc3`
### Mitigation
There are no known workarounds for affected versions. Upgrade to Nokogiri `1.11.0.rc4` or later.
If, after upgrading to `1.11.0.rc4` or later, you wish to re-enable network access for resolution of external resources (i.e., return to the previous behavior):
1. Ensure the input is trusted. Do not enable this option for untrusted input.
2. When invoking the `Nokogiri::XML::Schema` constructor, pass as the second parameter an instance of `Nokogiri::XML::ParseOptions` with the `NONET` flag turned off.
So if your previous code was:
``` ruby
# in v1.11.0.rc3 and earlier, this call allows resources to be accessed over the network
# but in v1.11.0.rc4 and later, this call will disallow network access for external resources
schema = Nokogiri::XML::Schema.new(schema)
# in v1.11.0.rc4 and later, the following is equivalent to the code above
# (the second parameter is optional, and this demonstrates its default value)
schema = Nokogiri::XML::Schema.new(schema, Nokogiri::XML::ParseOptions::DEFAULT_SCHEMA)
```
Then you can add the second parameter to indicate that the input is trusted by changing it to:
``` ruby
# in v1.11.0.rc3 and earlier, this would raise an ArgumentError
# but in v1.11.0.rc4 and later, this allows resources to be accessed over the network
schema = Nokogiri::XML::Schema.new(trusted_schema, Nokogiri::XML::ParseOptions.new.nononet)
```
### References
- [This issue's public advisory](https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-vr8q-g5c7-m54m)
- [Original Hackerone report (private)](https://hackerone.com/reports/747489)
- [OWASP description of XXE attack](https://www.owasp.org/index.php/XML_External_Entity_(XXE)_Processing)
- [OWASP description of SSRF attack](https://www.owasp.org/index.php/Server_Side_Request_Forgery)
### Credit
This vulnerability was independently reported by @eric-therond and @gucki.
The Nokogiri maintainers would like to thank [HackerOne](https://hackerone.com/nokogiri) for providing a secure, responsible mechanism for reporting, and for providing their fantastic service to us. | {'CVE-2020-26247'} | 2022-04-19T19:02:42Z | 2020-12-30T18:35:06Z | MODERATE | 4.3 | {'CWE-611'} | {'https://github.com/advisories/GHSA-vr8q-g5c7-m54m', 'https://rubygems.org/gems/nokogiri', 'https://github.com/sparklemotion/nokogiri/releases/tag/v1.11.0.rc4', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26247', 'https://lists.debian.org/debian-lts-announce/2021/06/msg00007.html', 'https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-vr8q-g5c7-m54m', 'https://github.com/sparklemotion/nokogiri/blob/main/CHANGELOG.md#v1110--2021-01-03', 'https://hackerone.com/reports/747489', 'https://github.com/sparklemotion/nokogiri/commit/9c87439d9afa14a365ff13e73adc809cb2c3d97b'} | null | {'https://github.com/sparklemotion/nokogiri/commit/9c87439d9afa14a365ff13e73adc809cb2c3d97b'} | {'https://github.com/sparklemotion/nokogiri/commit/9c87439d9afa14a365ff13e73adc809cb2c3d97b'} |
GHSA | GHSA-5jpf-pj32-xx53 | Authorization header is not sanitized in an error object in auth0 | ### Overview
Versions before and including `2.27.0` use a block list of specific keys that should be sanitized from the request object contained in the error object. When a request to Auth0 management API fails, the key for `Authorization` header is not sanitized and the `Authorization` header value can be logged exposing a bearer token.
### Am I affected?
You are affected by this vulnerability if all of the following conditions apply:
- You are using `auth0` npm package
- You are using a Machine to Machine application authorized to use Auth0's management API https://auth0.com/docs/flows/concepts/client-credentials
### How to fix that?
Upgrade to version `2.27.1`
### Will this update impact my users?
The fix provided in patch will not affect your users.
### Credit
http://github.com/osdiab | {'CVE-2020-15125'} | 2022-04-19T19:02:31Z | 2020-07-29T16:26:22Z | HIGH | 7.7 | {'CWE-209'} | {'https://github.com/auth0/node-auth0/tree/v2.27.1', 'https://github.com/advisories/GHSA-5jpf-pj32-xx53', 'https://github.com/auth0/node-auth0/pull/507/commits/62ca61b3348ec8e74d7d00358661af1a8bc98a3c', 'https://github.com/auth0/node-auth0/pull/507', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15125', 'https://github.com/auth0/node-auth0/security/advisories/GHSA-5jpf-pj32-xx53'} | null | {'https://github.com/auth0/node-auth0/pull/507/commits/62ca61b3348ec8e74d7d00358661af1a8bc98a3c'} | {'https://github.com/auth0/node-auth0/pull/507/commits/62ca61b3348ec8e74d7d00358661af1a8bc98a3c'} |
GHSA | GHSA-7rpj-hg47-cx62 | Improper Restriction of XML External Entity Reference in com.h2database:h2. | H2 is an embeddable RDBMS written in Java. The package com.h2database:h2 from 0 and before 2.0.202 are vulnerable to XML External Entity (XXE) Injection via the org.h2.jdbc.JdbcSQLXML class object, when it receives parsed string data from org.h2.jdbc.JdbcResultSet.getSQLXML() method. If it executes the getSource() method when the parameter is DOMSource.class it will trigger the vulnerability. | {'CVE-2021-23463'} | 2022-04-22T15:39:59Z | 2021-12-16T14:29:57Z | HIGH | 8.1 | {'CWE-611'} | {'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://github.com/h2database/h2database/pull/3199', 'https://snyk.io/vuln/SNYK-JAVA-COMH2DATABASE-1769238', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23463', 'https://github.com/advisories/GHSA-7rpj-hg47-cx62', 'https://github.com/h2database/h2database/issues/3195', 'https://github.com/h2database/h2database/commit/d83285fd2e48fb075780ee95badee6f5a15ea7f8%23diff-008c2e4462609982199cd83e7cf6f1d6b41296b516783f6752c44b9f15dc7bc3'} | null | {'https://github.com/h2database/h2database/commit/d83285fd2e48fb075780ee95badee6f5a15ea7f8#diff-008c2e4462609982199cd83e7cf6f1d6b41296b516783f6752c44b9f15dc7bc3'} | {'https://github.com/h2database/h2database/commit/d83285fd2e48fb075780ee95badee6f5a15ea7f8#diff-008c2e4462609982199cd83e7cf6f1d6b41296b516783f6752c44b9f15dc7bc3'} |
GHSA | GHSA-64fq-9c6w-rq44 | Improper Neutralization of Formula Elements in a CSV File in Kimai 2 | A CSV Injection vulnerablity exists in Kimai Kimai 2 prior to 1.14.1 via a description in a new timesheet. | {'CVE-2021-43515'} | 2022-04-22T20:21:49Z | 2022-04-09T00:00:25Z | HIGH | 7.8 | {'CWE-1236'} | {'https://github.com/advisories/GHSA-64fq-9c6w-rq44', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43515', 'https://github.com/kevinpapst/kimai2/pull/2532', 'https://github.com/kevinpapst/kimai2/commit/dad1b8b772947f1596175add1b4f33b791705507#diff-6774f5865dbaf8bc6c55b75bd92e6f9950ebe7834aa2efd828a19fd637e667cf'} | null | {'https://github.com/kevinpapst/kimai2/commit/dad1b8b772947f1596175add1b4f33b791705507#diff-6774f5865dbaf8bc6c55b75bd92e6f9950ebe7834aa2efd828a19fd637e667cf'} | {'https://github.com/kevinpapst/kimai2/commit/dad1b8b772947f1596175add1b4f33b791705507#diff-6774f5865dbaf8bc6c55b75bd92e6f9950ebe7834aa2efd828a19fd637e667cf'} |
GHSA | GHSA-vc3x-gx6c-g99f | Denial of Service in Bytom | In the client in Bytom before 1.0.6, checkTopicRegister in p2p/discover/net.go does not prevent negative idx values, leading to a crash. | {'CVE-2018-18206'} | 2022-04-12T22:33:07Z | 2022-02-15T01:57:18Z | HIGH | 7.5 | {'CWE-190'} | {'https://github.com/Bytom/bytom/commit/1ac3c8ac4f2b1e1df9675228290bda6b9586ba42', 'https://nvd.nist.gov/vuln/detail/CVE-2018-18206', 'https://github.com/Bytom/bytom/pull/1307', 'https://github.com/advisories/GHSA-vc3x-gx6c-g99f'} | null | {'https://github.com/Bytom/bytom/commit/1ac3c8ac4f2b1e1df9675228290bda6b9586ba42'} | {'https://github.com/Bytom/bytom/commit/1ac3c8ac4f2b1e1df9675228290bda6b9586ba42'} |
GHSA | GHSA-53r4-h27g-rg3x | 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-0991, CVE-2019-0993, CVE-2019-1002, CVE-2019-1003, CVE-2019-1024, CVE-2019-1051, CVE-2019-1052. | {'CVE-2019-0992'} | 2021-03-29T20:59:07Z | 2021-03-29T20:59:07Z | HIGH | 7.5 | {'CWE-787'} | {'https://github.com/advisories/GHSA-53r4-h27g-rg3x', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0992', 'https://nvd.nist.gov/vuln/detail/CVE-2019-0992', 'https://github.com/chakra-core/ChakraCore/commit/53b75c5f4a206740375f6a8a96934242d556e7c4', 'https://github.com/chakra-core/ChakraCore/commit/3d6226cc2d1077537220361c82e34a362c6c76ee'} | null | {'https://github.com/chakra-core/ChakraCore/commit/3d6226cc2d1077537220361c82e34a362c6c76ee', 'https://github.com/chakra-core/ChakraCore/commit/53b75c5f4a206740375f6a8a96934242d556e7c4'} | {'https://github.com/chakra-core/ChakraCore/commit/3d6226cc2d1077537220361c82e34a362c6c76ee', 'https://github.com/chakra-core/ChakraCore/commit/53b75c5f4a206740375f6a8a96934242d556e7c4'} |
GHSA | GHSA-43ch-2h55-2vj7 | Server-Side Request Forgery in private-ip | Insufficient RegEx in private-ip npm package v1.0.5 and below insufficiently filters reserved IP ranges resulting in indeterminate SSRF. An attacker can perform a large range of requests to ARIN reserved IP ranges, resulting in an indeterminable number of critical attack vectors, allowing remote attackers to request server-side resources or potentially execute arbitrary code through various SSRF techniques. | {'CVE-2020-28360'} | 2021-07-16T14:39:54Z | 2021-04-13T15:18:17Z | CRITICAL | 9.8 | {'CWE-918'} | {'https://github.com/frenchbread/private-ip', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28360', 'https://www.npmjs.com/package/private-ip', 'https://github.com/advisories/GHSA-43ch-2h55-2vj7', 'https://github.com/frenchbread/private-ip/commit/840664c4b9ba7888c41cfee9666e9a593db133e9', 'https://johnjhacking.com/blog/cve-2020-28360/'} | null | {'https://github.com/frenchbread/private-ip/commit/840664c4b9ba7888c41cfee9666e9a593db133e9'} | {'https://github.com/frenchbread/private-ip/commit/840664c4b9ba7888c41cfee9666e9a593db133e9'} |
GHSA | GHSA-57h3-9rgr-c24m | Out of bounds write in Pillow | An issue was discovered in Pillow before 8.1.1. TiffDecode has a heap-based buffer overflow when decoding crafted YCbCr files because of certain interpretation conflicts with LibTIFF in RGBA mode. NOTE: this issue exists because of an incomplete fix for CVE-2020-35654. | {'CVE-2021-25289'} | 2021-12-02T17:48:13Z | 2021-03-29T16:35:16Z | HIGH | 8.8 | {'CWE-787'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-25289', 'https://pillow.readthedocs.io/en/stable/releasenotes/8.1.1.html', 'https://github.com/advisories/GHSA-57h3-9rgr-c24m', 'https://security.gentoo.org/glsa/202107-33', 'https://github.com/python-pillow/Pillow/commit/3fee28eb9479bf7d59e0fa08068f9cc4a6e2f04c'} | null | {'https://github.com/python-pillow/Pillow/commit/3fee28eb9479bf7d59e0fa08068f9cc4a6e2f04c'} | {'https://github.com/python-pillow/Pillow/commit/3fee28eb9479bf7d59e0fa08068f9cc4a6e2f04c'} |
GHSA | GHSA-cf3w-g86h-35x4 | Code Injection vulnerability in CarrierWave::RMagick | ### Impact
[CarrierWave::RMagick](https://github.com/carrierwaveuploader/carrierwave/blob/master/lib/carrierwave/processing/rmagick.rb) has a Code Injection vulnerability. Its `#manipulate!` method inappropriately evals the content of mutation option(`:read`/`:write`), allowing attackers to craft a string that can be executed as a Ruby code.
If an application developer supplies untrusted inputs to the option, it will lead to remote code execution(RCE).
(But supplying untrusted input to the option itself is dangerous even in absence of this vulnerability, since is prone to DoS vulnerability - attackers can try to consume massive amounts of memory by resizing to a very large dimension)
### Proof of Concept
```ruby
class MyUploader < CarrierWave::Uploader::Base
include CarrierWave::RMagick
end
MyUploader.new.manipulate!({ read: { density: "1 }; p 'Hacked'; {" }}) # => shows "Hacked"
```
### Patches
Upgrade to [2.1.1](https://rubygems.org/gems/carrierwave/versions/2.1.1) or [1.3.2](https://rubygems.org/gems/carrierwave/versions/1.3.2).
### Workarounds
Stop supplying untrusted input to `#manipulate!`'s mutation option.
### References
[Code Injection Software Attack](https://owasp.org/www-community/attacks/Code_Injection)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [CarrierWave repo](https://github.com/carrierwaveuploader/carrierwave)
* Email me at [mit.shibuya@gmail.com](mailto:mit.shibuya@gmail.com) | {'CVE-2021-21305'} | 2022-04-27T19:58:19Z | 2021-02-08T19:16:39Z | HIGH | 7.4 | {'CWE-94', 'CWE-74'} | {'https://github.com/carrierwaveuploader/carrierwave/blob/master/CHANGELOG.md#211---2021-02-08', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21305', 'https://github.com/carrierwaveuploader/carrierwave/commit/387116f5c72efa42bc3938d946b4c8d2f22181b7', 'https://github.com/carrierwaveuploader/carrierwave/blob/master/CHANGELOG.md#132---2021-02-08', 'https://github.com/advisories/GHSA-cf3w-g86h-35x4', 'https://github.com/carrierwaveuploader/carrierwave/security/advisories/GHSA-cf3w-g86h-35x4', 'https://rubygems.org/gems/carrierwave'} | null | {'https://github.com/carrierwaveuploader/carrierwave/commit/387116f5c72efa42bc3938d946b4c8d2f22181b7'} | {'https://github.com/carrierwaveuploader/carrierwave/commit/387116f5c72efa42bc3938d946b4c8d2f22181b7'} |
GHSA | GHSA-8rf5-92jh-3vc9 | Uncaught Exception leading to Denial of Service in json-sanitizer | OWASP json-sanitizer before 1.2.2 can output invalid JSON or throw an undeclared exception for crafted input. This may lead to denial of service if the application is not prepared to handle these situations. | {'CVE-2021-23900'} | 2021-05-13T22:31:32Z | 2021-05-13T22:31:32Z | HIGH | 7.5 | {'CWE-248'} | {'https://github.com/OWASP/json-sanitizer/commit/a37f594f7378a1c76b3283e0dab9e1ab1dc0247e', 'https://github.com/OWASP/json-sanitizer/compare/v1.2.1...v1.2.2', 'https://groups.google.com/g/json-sanitizer-support/c/dAW1AeNMoA0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23900', 'https://github.com/advisories/GHSA-8rf5-92jh-3vc9'} | null | {'https://github.com/OWASP/json-sanitizer/commit/a37f594f7378a1c76b3283e0dab9e1ab1dc0247e'} | {'https://github.com/OWASP/json-sanitizer/commit/a37f594f7378a1c76b3283e0dab9e1ab1dc0247e'} |
GHSA | GHSA-q348-f93x-9gx4 | Lack of Input Validation in zendesk_api_client_php for Zendesk Subdomain | ### Impact
Lack of input validation of the Zendesk subdomain could expose users of the library to Server Side Request Forgery (SSRF).
### Resolution
Validate the provided Zendesk subdomain to be a valid subdomain in:
* getAuthUrl
* getAccessToken | {'CVE-2021-30492'} | 2021-04-29T21:53:06Z | 2021-04-29T21:53:06Z | CRITICAL | 0 | {'CWE-20', 'CWE-918'} | {'https://github.com/zendesk/zendesk_api_client_php/pull/466', 'https://github.com/zendesk/zendesk_api_client_php/commit/b451b743d9d6d81a9abf7cb86e70ec9c5332123e', 'https://github.com/zendesk/zendesk_api_client_php/security/advisories/GHSA-q348-f93x-9gx4', 'https://github.com/advisories/GHSA-q348-f93x-9gx4'} | null | {'https://github.com/zendesk/zendesk_api_client_php/commit/b451b743d9d6d81a9abf7cb86e70ec9c5332123e'} | {'https://github.com/zendesk/zendesk_api_client_php/commit/b451b743d9d6d81a9abf7cb86e70ec9c5332123e'} |
GHSA | GHSA-6x3v-rw2q-9gx7 | Improper implementation of the session fixation protection in Infinispan | A flaw was found in Infinispan through version 9.4.14.Final. An improper implementation of the session fixation protection in the Spring Session integration can result in incorrect session handling. | {'CVE-2019-10158'} | 2021-08-19T16:28:59Z | 2020-01-21T21:18:44Z | CRITICAL | 9.8 | {'CWE-384'} | {'https://github.com/advisories/GHSA-6x3v-rw2q-9gx7', 'https://github.com/infinispan/infinispan/commit/4b381c5910265972ccaabefbdbd16a2b929f6b72', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10158', 'https://github.com/infinispan/infinispan/pull/7025', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10158', 'https://github.com/infinispan/infinispan/pull/6960'} | null | {'https://github.com/infinispan/infinispan/commit/4b381c5910265972ccaabefbdbd16a2b929f6b72'} | {'https://github.com/infinispan/infinispan/commit/4b381c5910265972ccaabefbdbd16a2b929f6b72'} |
GHSA | GHSA-cxf7-qrc5-9446 | Remote shell execution vulnerability in image_processing | ### Impact
When using the `#apply` method from image_processing to apply a series of operations that are coming from unsanitized user input, this allows the attacker to execute shell commands:
```rb
ImageProcessing::Vips.apply({ system: "echo EXECUTED" })
#>> EXECUTED
```
This method is called internally by Active Storage variants, so Active Storage is vulnerable as well.
### Patches
The vulnerability has been fixed in version 1.12.2 of image_processing.
### Workarounds
If you're processing based on user input, it's highly recommended that you always sanitize the user input, by allowing only a constrained set of operations. For example:
```rb
operations = params[:operations]
.map { |operation| [operation[:name], *operation[:value]] }
.select { |name, *| name.to_s.include? %w[resize_to_limit strip ...] } # sanitization
ImageProcessing::Vips.apply(operations)
``` | {'CVE-2022-24720'} | 2022-03-10T15:56:29Z | 2022-03-01T22:22:26Z | CRITICAL | 9.8 | {'CWE-20', 'CWE-78'} | {'https://github.com/janko/image_processing/security/advisories/GHSA-cxf7-qrc5-9446', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24720', 'https://github.com/advisories/GHSA-cxf7-qrc5-9446', 'https://github.com/janko/image_processing/commit/038e4574e8f4f4b636a62394e09983c71980dada'} | null | {'https://github.com/janko/image_processing/commit/038e4574e8f4f4b636a62394e09983c71980dada'} | {'https://github.com/janko/image_processing/commit/038e4574e8f4f4b636a62394e09983c71980dada'} |
GHSA | GHSA-r3r5-jhw6-4634 | Insecure temporary file usage in SWHKD | SWHKD 1.1.5 unsafely uses the /tmp/swhkd.sock pathname. There can be an information leak or denial of service. | {'CVE-2022-27818'} | 2022-04-19T18:16:59Z | 2022-04-08T00:00:24Z | CRITICAL | 9.1 | {'CWE-668'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-27818', 'https://github.com/waycrate/swhkd/commit/f70b99dd575fab79d8a942111a6980431f006818', 'http://www.openwall.com/lists/oss-security/2022/04/14/1', 'https://github.com/waycrate/swhkd/releases', 'https://github.com/advisories/GHSA-r3r5-jhw6-4634', 'https://github.com/waycrate/swhkd/releases/tag/1.1.7'} | null | {'https://github.com/waycrate/swhkd/commit/f70b99dd575fab79d8a942111a6980431f006818'} | {'https://github.com/waycrate/swhkd/commit/f70b99dd575fab79d8a942111a6980431f006818'} |
GHSA | GHSA-xf7w-r453-m56c | Arbitrary File Overwrite in fstream | Versions of `fstream` prior to 1.0.12 are vulnerable to Arbitrary File Overwrite. Extracting tarballs containing a hardlink to a file that already exists in the system and a file that matches the hardlink will overwrite the system's file with the contents of the extracted file. The `fstream.DirWriter()` function is vulnerable.
## Recommendation
Upgrade to version 1.0.12 or later. | {'CVE-2019-13173'} | 2021-08-04T20:12:16Z | 2019-05-30T17:19:34Z | HIGH | 7.5 | {'CWE-59'} | {'https://www.npmjs.com/advisories/886', 'https://github.com/advisories/GHSA-xf7w-r453-m56c', 'https://github.com/npm/fstream/commit/6a77d2fa6e1462693cf8e46f930da96ec1b0bb22', 'https://nvd.nist.gov/vuln/detail/CVE-2019-13173', 'http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00010.html', 'https://usn.ubuntu.com/4123-1/', 'http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00052.html'} | null | {'https://github.com/npm/fstream/commit/6a77d2fa6e1462693cf8e46f930da96ec1b0bb22'} | {'https://github.com/npm/fstream/commit/6a77d2fa6e1462693cf8e46f930da96ec1b0bb22'} |
GHSA | GHSA-59x4-67mh-px54 | Crypt_GPG does not prevent additional options in GPG calls | The Crypt_GPG extension before 1.6.7 for PHP does not prevent additional options in GPG calls, which presents a risk for certain environments and GPG versions. | {'CVE-2022-24953'} | 2022-03-01T18:36:14Z | 2022-02-18T00:00:36Z | MODERATE | 5.3 | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-24953', 'https://github.com/pear/Crypt_GPG/commit/74c8f989cefbe0887274b461dc56197e121bfd04', 'https://github.com/advisories/GHSA-59x4-67mh-px54', 'https://github.com/pear/Crypt_GPG/commit/29c0fbe96d0d4063ecd5c9a4644cb65a7fb7cc4e'} | null | {'https://github.com/pear/Crypt_GPG/commit/29c0fbe96d0d4063ecd5c9a4644cb65a7fb7cc4e', 'https://github.com/pear/Crypt_GPG/commit/74c8f989cefbe0887274b461dc56197e121bfd04'} | {'https://github.com/pear/Crypt_GPG/commit/74c8f989cefbe0887274b461dc56197e121bfd04', 'https://github.com/pear/Crypt_GPG/commit/29c0fbe96d0d4063ecd5c9a4644cb65a7fb7cc4e'} |
GHSA | GHSA-5rcc-6cmj-7728 | Cross-site Scripting in BookStack | Iframe tags don't have a sandbox attribute, this makes an attacker able to execute malicious javascript via an iframe and perform phishing attacks. The sandbox attribute will block script execution and prevents the content to navigate its top-level browsing context which will stop this type of attack. | {'CVE-2022-0877'} | 2022-03-14T21:03:35Z | 2022-03-09T00:00:44Z | MODERATE | 5.4 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0877', 'https://github.com/advisories/GHSA-5rcc-6cmj-7728', 'https://github.com/bookstackapp/bookstack/commit/856fca8289b7370cafa033ea21c408e7d4303fd6', 'https://huntr.dev/bounties/b04df4e3-ae5a-4dc6-81ec-496248b15f3c'} | null | {'https://github.com/bookstackapp/bookstack/commit/856fca8289b7370cafa033ea21c408e7d4303fd6'} | {'https://github.com/bookstackapp/bookstack/commit/856fca8289b7370cafa033ea21c408e7d4303fd6'} |
GHSA | GHSA-qj26-7grj-whg3 | Privilege Escalation in fscrypt | The pam_fscrypt module in fscrypt before 0.2.4 may incorrectly restore primary and supplementary group IDs to the values associated with the root user, which allows attackers to gain privileges via a successful login through certain applications that use Linux-PAM (aka pam). | {'CVE-2018-6558'} | 2021-06-23T17:18:49Z | 2021-06-23T17:18:49Z | MODERATE | 6.5 | null | {'https://launchpad.net/bugs/1787548', 'https://github.com/google/fscrypt/commit/3022c1603d968c22f147b4a2c49c4637dd1be91b', 'https://github.com/advisories/GHSA-qj26-7grj-whg3', 'https://github.com/google/fscrypt/issues/77', 'https://github.com/google/fscrypt/commit/315f9b042237200174a1fb99427f74027e191d66', 'https://nvd.nist.gov/vuln/detail/CVE-2018-6558'} | null | {'https://github.com/google/fscrypt/commit/3022c1603d968c22f147b4a2c49c4637dd1be91b', 'https://github.com/google/fscrypt/commit/315f9b042237200174a1fb99427f74027e191d66'} | {'https://github.com/google/fscrypt/commit/315f9b042237200174a1fb99427f74027e191d66', 'https://github.com/google/fscrypt/commit/3022c1603d968c22f147b4a2c49c4637dd1be91b'} |
GHSA | GHSA-vpq7-m4qm-p2gp | Business Logic Errors in microweber | Business Logic Errors in Packagist microweber/microweber prior to 1.2.11. | {'CVE-2022-0596'} | 2022-02-24T13:55:55Z | 2022-02-16T00:01:45Z | MODERATE | 4.3 | null | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0596', 'https://github.com/advisories/GHSA-vpq7-m4qm-p2gp', 'https://github.com/microweber/microweber/commit/91a9d899741557c75050614ff7adb8c0e3feb005', 'https://huntr.dev/bounties/f68b994e-2b8b-49f5-af2a-8cd99e8048a5'} | null | {'https://github.com/microweber/microweber/commit/91a9d899741557c75050614ff7adb8c0e3feb005'} | {'https://github.com/microweber/microweber/commit/91a9d899741557c75050614ff7adb8c0e3feb005'} |
GHSA | GHSA-fpcp-9h7m-ffpx | Null pointer dereference in TensorFlow | ### Impact
When [building an XLA compilation cache](https://github.com/tensorflow/tensorflow/blob/274df9b02330b790aa8de1cee164b70f72b9b244/tensorflow/compiler/jit/xla_platform_info.cc#L43-L104), if default settings are used, TensorFlow triggers a null pointer dereference:
```cc
string allowed_gpus =
flr->config_proto()->gpu_options().visible_device_list();
```
In the default scenario, all devices are allowed, so `flr->config_proto` is `nullptr`.
### Patches
We have patched the issue in GitHub commit [e21af685e1828f7ca65038307df5cc06de4479e8](https://github.com/tensorflow/tensorflow/commit/e21af685e1828f7ca65038307df5cc06de4479e8).
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-23595'} | 2022-02-11T19:55:41Z | 2022-02-09T23:33:17Z | MODERATE | 5.3 | {'CWE-476'} | {'https://github.com/advisories/GHSA-fpcp-9h7m-ffpx', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-fpcp-9h7m-ffpx', 'https://github.com/tensorflow/tensorflow/commit/e21af685e1828f7ca65038307df5cc06de4479e8', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23595', 'https://github.com/tensorflow/tensorflow/blob/274df9b02330b790aa8de1cee164b70f72b9b244/tensorflow/compiler/jit/xla_platform_info.cc#L43-L104'} | null | {'https://github.com/tensorflow/tensorflow/commit/e21af685e1828f7ca65038307df5cc06de4479e8'} | {'https://github.com/tensorflow/tensorflow/commit/e21af685e1828f7ca65038307df5cc06de4479e8'} |
GHSA | GHSA-599h-8wpj-75xj | Authentication Bypass in tyk-identity-broker | The package github.com/tyktechnologies/tyk-identity-broker before 1.1.1 are vulnerable to Authentication Bypass via the Go XML parser which can cause SAML authentication bypass. This is because the XML parser doesn’t guarantee integrity in the XML round-trip (encoding/decoding XML data). | {'CVE-2021-23365'} | 2021-06-23T17:23:30Z | 2021-06-23T17:23:30Z | CRITICAL | 9.1 | {'CWE-287'} | {'https://github.com/TykTechnologies/tyk-identity-broker/pull/147', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMTYKTECHNOLOGIESTYKIDENTITYBROKER-1089720', 'https://github.com/TykTechnologies/tyk-identity-broker/releases/tag/v1.1.1', 'https://github.com/advisories/GHSA-599h-8wpj-75xj', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23365', 'https://github.com/TykTechnologies/tyk-identity-broker/commit/46f70420e0911e4e8b638575e29d394c227c75d0', 'https://github.com/TykTechnologies/tyk-identity-broker/commit/243092965b0f93a95a14cb882b5b9a3df61dd5c0'} | null | {'https://github.com/TykTechnologies/tyk-identity-broker/commit/46f70420e0911e4e8b638575e29d394c227c75d0', 'https://github.com/TykTechnologies/tyk-identity-broker/commit/243092965b0f93a95a14cb882b5b9a3df61dd5c0'} | {'https://github.com/TykTechnologies/tyk-identity-broker/commit/243092965b0f93a95a14cb882b5b9a3df61dd5c0', 'https://github.com/TykTechnologies/tyk-identity-broker/commit/46f70420e0911e4e8b638575e29d394c227c75d0'} |
GHSA | GHSA-xqp8-w826-hh6x | Crash server with query parameter | ### Impact
Parse Server crashes when if a query request contains an invalid value for the `explain` option. This is due to a bug in the MongoDB Node.js driver which throws an exception that Parse Server cannot catch.
### Patches
Upgrade to Parse Server 4.10.3 | {'CVE-2021-39187'} | 2022-04-19T19:03:07Z | 2021-09-02T16:51:14Z | HIGH | 7.5 | {'CWE-74', 'CWE-20', 'CWE-755'} | {'https://github.com/advisories/GHSA-xqp8-w826-hh6x', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39187', 'https://jira.mongodb.org/browse/NODE-3463', 'https://github.com/parse-community/parse-server/commit/308668c89474223e2448be92d6823b52c1c313ec', 'https://github.com/parse-community/parse-server/security/advisories/GHSA-xqp8-w826-hh6x', 'https://github.com/parse-community/parse-server/releases/tag/4.10.3'} | null | {'https://github.com/parse-community/parse-server/commit/308668c89474223e2448be92d6823b52c1c313ec'} | {'https://github.com/parse-community/parse-server/commit/308668c89474223e2448be92d6823b52c1c313ec'} |
GHSA | GHSA-6qgm-fv6v-rfpv | Overflow/denial of service in `tf.raw_ops.ReverseSequence` | ### Impact
The implementation of `tf.raw_ops.ReverseSequence` allows for stack overflow and/or `CHECK`-fail based denial of service.
```python
import tensorflow as tf
input = tf.zeros([1, 1, 1], dtype=tf.int32)
seq_lengths = tf.constant([0], shape=[1], dtype=tf.int32)
tf.raw_ops.ReverseSequence(
input=input, seq_lengths=seq_lengths, seq_dim=-2, batch_dim=0)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/5b3b071975e01f0d250c928b2a8f901cd53b90a7/tensorflow/core/kernels/reverse_sequence_op.cc#L114-L118) fails to validate that `seq_dim` and `batch_dim` arguments are valid.
Negative values for `seq_dim` can result in stack overflow or `CHECK`-failure, depending on the version of Eigen code used to implement the operation. Similar behavior can be exhibited by invalid values of `batch_dim`.
### Patches
We have patched the issue in GitHub commit [ecf768cbe50cedc0a45ce1ee223146a3d3d26d23](https://github.com/tensorflow/tensorflow/commit/ecf768cbe50cedc0a45ce1ee223146a3d3d26d23).
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-29575'} | 2021-05-21T14:26:13Z | 2021-05-21T14:26:13Z | LOW | 2.5 | {'CWE-119', 'CWE-120'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-6qgm-fv6v-rfpv', 'https://github.com/tensorflow/tensorflow/commit/ecf768cbe50cedc0a45ce1ee223146a3d3d26d23', 'https://github.com/advisories/GHSA-6qgm-fv6v-rfpv', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29575'} | null | {'https://github.com/tensorflow/tensorflow/commit/ecf768cbe50cedc0a45ce1ee223146a3d3d26d23'} | {'https://github.com/tensorflow/tensorflow/commit/ecf768cbe50cedc0a45ce1ee223146a3d3d26d23'} |
GHSA | GHSA-vqj2-4v8m-8vrq | Insecure Temporary File in mlflow | mlflow prior to 1.23.1 contains an insecure temporary file. The insecure function `tempfile.mktemp()` is deprecated and `mkstemp()` should be used instead. | {'CVE-2022-0736'} | 2022-03-03T19:18:19Z | 2022-02-24T00:00:54Z | HIGH | 8.2 | {'CWE-668', 'CWE-377'} | {'https://github.com/mlflow/mlflow/commit/61984e6843d2e59235d82a580c529920cd8f3711', 'https://github.com/advisories/GHSA-vqj2-4v8m-8vrq', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0736', 'https://huntr.dev/bounties/e5384764-c583-4dec-a1d8-4697f4e12f75'} | null | {'https://github.com/mlflow/mlflow/commit/61984e6843d2e59235d82a580c529920cd8f3711'} | {'https://github.com/mlflow/mlflow/commit/61984e6843d2e59235d82a580c529920cd8f3711'} |
GHSA | GHSA-gmjw-49p4-pcfm | Prototype poisoning | ### Impact
The issue is as follows: when `msgpack5` decodes a map containing a
key `"__proto__"`, it assigns the decoded value to `__proto__`. As you
are no doubt aware, `Object.prototype.__proto__` is an accessor
property for the receiver's prototype. If the value corresponding to
the key `__proto__` decodes to an object or `null`, `msgpack5` sets
the decoded object's prototype to that value.
An attacker who can submit crafted MessagePack data to a service can
use this to produce values that appear to be of other types; may have
unexpected prototype properties and methods (for example `length`,
numeric properties, and `push` et al if `__proto__`'s value decodes to
an `Array`); and/or may throw unexpected exceptions when used (for
example if the `__proto__` value decodes to a `Map` or `Date`). Other
unexpected behavior might be produced for other types.
There is no effect on the global prototype.
An example:
```js
const msgpack5 = require('msgpack5')();
const payload = {};
Object.defineProperty(payload, '__proto__', {
value: new Map().set(1, 2),
enumerable: true
});
const encoded = msgpack5.encode(payload);
console.log(encoded); // <Buffer 81 a9 5f 5f 70 72 6f 74 6f 5f 5f 81 01 02>
const decoded = msgpack5.decode(encoded);
// decoded's prototype has been overwritten
console.log(Object.getPrototypeOf(decoded)); // Map(1) { 1 => 2 }
console.log(decoded.get); // [Function: get]
// decoded appears to most common typechecks to be a Map
console.log(decoded instanceof Map); // true
console.log(decoded.toString()); // [object Map]
console.log(Object.prototype.toString.call(decoded)); // [object Map]
console.log(decoded.constructor.name); // Map
console.log(Object.getPrototypeOf(decoded).constructor.name); // Map
// decoded is not, however, a Map
console.log(Object.getPrototypeOf(decoded) === Map.prototype); // false
// using decoded as though it were a Map throws
try {
decoded.get(1);
} catch (error) {
console.log(error); // TypeError: Method Map.prototype.get called
// on incompatible receiver #<Map>
}
try {
decoded.size;
} catch (error) {
console.log(error); // TypeError: Method get Map.prototype.size
// called on incompatible receiver #<Map>
}
// re-encoding the decoded value throws
try {
msgpack5.encode(decoded);
} catch (error) {
console.log(error); // TypeError: Method Map.prototype.entries
// called on incompatible receiver #<Map>
}
```
This "prototype poisoning" is sort of a very limited inversion of a
prototype pollution attack. Only the decoded value's prototype is
affected, and it can only be set to `msgpack5` values (though if the
victim makes use of custom codecs, anything could be a `msgpack5`
value). We have not found a way to escalate this to true prototype
pollution (absent other bugs in the consumer's code).
### Patches
Versions v5.2.1, v4.5.1, v3.6.1 include the fix.
### Workarounds
Always validate incoming data after parsing before doing any processing.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [example link to repo](http://example.com)
* Email us at [example email address](mailto:example@example.com) | {'CVE-2021-21368'} | 2022-04-19T19:02:49Z | 2021-03-12T22:44:17Z | MODERATE | 6.7 | {'CWE-915'} | {'https://www.npmjs.com/package/msgpack5', 'https://github.com/mcollina/msgpack5/security/advisories/GHSA-gmjw-49p4-pcfm', 'https://github.com/mcollina/msgpack5/releases/tag/v5.2.1', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21368', 'https://github.com/mcollina/msgpack5/releases/tag/v4.5.1', 'https://github.com/mcollina/msgpack5/releases/tag/v3.6.1', 'https://github.com/advisories/GHSA-gmjw-49p4-pcfm', 'https://github.com/mcollina/msgpack5/commit/d4e6cb956ae51c8bb2828e71c7c1107c340cf1e8'} | null | {'https://github.com/mcollina/msgpack5/commit/d4e6cb956ae51c8bb2828e71c7c1107c340cf1e8'} | {'https://github.com/mcollina/msgpack5/commit/d4e6cb956ae51c8bb2828e71c7c1107c340cf1e8'} |
GHSA | GHSA-cqxw-3p7v-p9gr | Phusion Passenger uses a known /tmp filename | In Phusion Passenger before 5.1.0, a known /tmp filename was used during passenger-install-nginx-module execution, which could allow local attackers to gain the privileges of the passenger user | {'CVE-2016-10345'} | 2022-04-26T20:43:37Z | 2018-08-21T17:08:03Z | HIGH | 7.8 | null | {'https://github.com/phusion/passenger/commit/e5b4b0824d6b648525b4bf63d9fa37e5beeae441', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10345', 'https://github.com/phusion/passenger/blob/stable-5.1/CHANGELOG', 'https://github.com/advisories/GHSA-cqxw-3p7v-p9gr'} | null | {'https://github.com/phusion/passenger/commit/e5b4b0824d6b648525b4bf63d9fa37e5beeae441'} | {'https://github.com/phusion/passenger/commit/e5b4b0824d6b648525b4bf63d9fa37e5beeae441'} |
GHSA | GHSA-236h-rqv8-8q73 | GraphQL: Security breach on Viewer query | ### Impact
An authenticated user using the viewer GraphQL query can bypass all read security on his User object and can also bypass all objects linked via relation or Pointer on his User object.
### Patches
This vulnerability has been patched in Parse Server 4.3.0.
### Workarounds
No
### References
See [commit 78239ac](https://github.com/parse-community/parse-server/commit/78239ac9071167fdf243c55ae4bc9a2c0b0d89aa) for details. | {'CVE-2020-15126'} | 2022-04-19T19:02:30Z | 2020-07-22T23:06:47Z | HIGH | 6.5 | {'CWE-863'} | {'https://github.com/parse-community/parse-server/commit/78239ac9071167fdf243c55ae4bc9a2c0b0d89aa', 'https://github.com/parse-community/parse-server/security/advisories/GHSA-236h-rqv8-8q73', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15126', 'https://github.com/advisories/GHSA-236h-rqv8-8q73', 'https://github.com/parse-community/parse-server/blob/master/CHANGELOG.md#430'} | null | {'https://github.com/parse-community/parse-server/commit/78239ac9071167fdf243c55ae4bc9a2c0b0d89aa'} | {'https://github.com/parse-community/parse-server/commit/78239ac9071167fdf243c55ae4bc9a2c0b0d89aa'} |
GHSA | GHSA-232r-66cg-79px | Paramiko not properly checking authention before processing other requests | transport.py in the SSH server implementation of Paramiko before 1.17.6, 1.18.x before 1.18.5, 2.0.x before 2.0.8, 2.1.x before 2.1.5, 2.2.x before 2.2.3, 2.3.x before 2.3.2, and 2.4.x before 2.4.1 does not properly check whether authentication is completed before processing other requests, as demonstrated by channel-open. A customized SSH client can simply skip the authentication step. | {'CVE-2018-7750'} | 2022-04-26T20:43:25Z | 2018-07-12T20:29:30Z | CRITICAL | 9.8 | {'CWE-287'} | {'https://access.redhat.com/errata/RHSA-2018:1274', 'http://www.securityfocus.com/bid/103713', 'https://lists.debian.org/debian-lts-announce/2018/10/msg00018.html', 'https://usn.ubuntu.com/3603-2/', 'https://github.com/advisories/GHSA-232r-66cg-79px', 'https://access.redhat.com/errata/RHSA-2018:1972', 'https://lists.debian.org/debian-lts-announce/2021/12/msg00025.html', 'https://access.redhat.com/errata/RHSA-2018:0591', 'https://access.redhat.com/errata/RHSA-2018:1328', 'https://access.redhat.com/errata/RHSA-2018:1124', 'https://nvd.nist.gov/vuln/detail/CVE-2018-7750', 'https://access.redhat.com/errata/RHSA-2018:1125', 'https://usn.ubuntu.com/3603-1/', 'https://github.com/paramiko/paramiko/commit/fa29bd8446c8eab237f5187d28787727b4610516', 'https://access.redhat.com/errata/RHSA-2018:0646', 'https://github.com/paramiko/paramiko/blob/master/sites/www/changelog.rst', 'https://github.com/paramiko/paramiko/issues/1175', 'https://www.exploit-db.com/exploits/45712/', 'https://access.redhat.com/errata/RHSA-2018:1213', 'https://access.redhat.com/errata/RHSA-2018:1525'} | null | {'https://github.com/paramiko/paramiko/commit/fa29bd8446c8eab237f5187d28787727b4610516'} | {'https://github.com/paramiko/paramiko/commit/fa29bd8446c8eab237f5187d28787727b4610516'} |
GHSA | GHSA-7wwv-vh3v-89cq | ReDOS vulnerabities: multiple grammars | ### Impact: Potential ReDOS vulnerabilities (exponential and polynomial RegEx backtracking)
[oswasp](https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS):
> The Regular expression Denial of Service (ReDoS) is a Denial of Service attack, that exploits the fact that most Regular Expression implementations may reach extreme situations that cause them to work very slowly (exponentially related to input size). An attacker can then cause a program using a Regular Expression to enter these extreme situations and then hang for a very long time.
If are you are using Highlight.js to highlight user-provided data you are possibly vulnerable. On the client-side (in a browser or Electron environment) risks could include lengthy freezes or crashes... On the server-side infinite freezes could occur... effectively preventing users from accessing your app or service (ie, Denial of Service).
This is an issue with grammars shipped with the parser (and potentially 3rd party grammars also), not the parser itself. If you are using Highlight.js with any of the following grammars you are vulnerable. If you are using `highlightAuto` to detect the language (and have any of these grammars registered) you are vulnerable. Exponential grammars (C, Perl, JavaScript) are auto-registered when using the common grammar subset/library `require('highlight.js/lib/common')` as of 10.4.0 - see https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@10.4.0/build/highlight.js
All versions prior to 10.4.1 are vulnerable, including version 9.18.5.
**Grammars with exponential backtracking issues:**
- c-like (c, cpp, arduino)
- handlebars (htmlbars)
- gams
- perl
- jboss-cli
- r
- erlang-repl
- powershell
- routeros
- livescript (10.4.0 and 9.18.5 included this fix)
- javascript & typescript (10.4.0 included partial fixes)
And of course any aliases of those languages have the same issue. ie: `hpp` is no safer than `cpp`.
**Grammars with polynomial backtracking issues:**
- kotlin
- gcode
- d
- aspectj
- moonscript
- coffeescript/livescript
- csharp
- scilab
- crystal
- elixir
- basic
- ebnf
- ruby
- fortran/irpf90
- livecodeserver
- yaml
- x86asm
- dsconfig
- markdown
- ruleslanguage
- xquery
- sqf
And again: any aliases of those languages have the same issue. ie: `ruby` and `rb` share the same ruby issues.
### Patches
- Version 10.4.1 resolves these vulnerabilities. Please upgrade.
### Workarounds / Mitigations
- Discontinue use the affected grammars. (or perhaps use only those with poly vs exponential issues)
- Attempt cherry-picking the grammar fixes into older versions...
- Attempt using newer CDN versions of any affected languages. (ie using an older CDN version of the library with newer CDN grammars). Your mileage may vary.
### References
- https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS
### For more information
If you have any questions or comments about this advisory:
* Open an issue: https://github.com/highlightjs/highlight.js/issues
* Email us at [security@highlightjs.com](mailto:security@highlightjs.com) | null | 2022-05-03T08:27:46Z | 2020-12-04T16:47:20Z | MODERATE | 0 | {'CWE-20', 'CWE-400'} | {'https://www.npmjs.com/package/@highlightjs/cdn-assets', 'https://www.npmjs.com/package/highlight.js', 'https://github.com/highlightjs/highlight.js/commit/373b9d862401162e832ce77305e49b859e110f9c', 'https://github.com/advisories/GHSA-7wwv-vh3v-89cq', 'https://github.com/highlightjs/highlight.js/security/advisories/GHSA-7wwv-vh3v-89cq'} | null | {'https://github.com/highlightjs/highlight.js/commit/373b9d862401162e832ce77305e49b859e110f9c'} | {'https://github.com/highlightjs/highlight.js/commit/373b9d862401162e832ce77305e49b859e110f9c'} |
GHSA | GHSA-h7f9-cvh5-qw7f | Path traversal in pimcore/pimcore | This affects the package pimcore/pimcore before 6.8.8. A Local FIle Inclusion vulnerability exists in the downloadCsvAction function of the CustomReportController class (bundles/AdminBundle/Controller/Reports/CustomReportController.php). An authenticated user can reach this function with a GET request at the following endpoint: /admin/reports/custom-report/download-csv?exportFile=&91;filename]. Since exportFile variable is not sanitized, an attacker can exploit a local file inclusion vulnerability. | {'CVE-2021-23340'} | 2021-02-25T16:32:46Z | 2021-02-25T16:32:46Z | HIGH | 0 | {'CWE-22'} | {'https://github.com/pimcore/pimcore/commit/1786bdd4962ee51544fad537352c2b4223309442', 'https://github.com/advisories/GHSA-h7f9-cvh5-qw7f', 'https://github.com/pimcore/pimcore/blob/v6.7.2/bundles/AdminBundle/Controller/Reports/CustomReportController.php%23L454', 'https://snyk.io/vuln/SNYK-PHP-PIMCOREPIMCORE-1070132', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23340'} | null | {'https://github.com/pimcore/pimcore/commit/1786bdd4962ee51544fad537352c2b4223309442'} | {'https://github.com/pimcore/pimcore/commit/1786bdd4962ee51544fad537352c2b4223309442'} |
GHSA | GHSA-8462-q7x7-g2x4 | High severity vulnerability that affects bson | The MongoDB bson JavaScript module (also known as js-bson) versions 0.5.0 to 1.0.x before 1.0.5 is vulnerable to a Regular Expression Denial of Service (ReDoS) in lib/bson/decimal128.js. The flaw is triggered when the Decimal128.fromString() function is called to parse a long untrusted string. | {'CVE-2018-13863'} | 2021-09-03T22:29:40Z | 2018-09-17T20:44:58Z | HIGH | 7.5 | {'CWE-400', 'CWE-185'} | {'https://github.com/advisories/GHSA-8462-q7x7-g2x4', 'https://snyk.io/vuln/npm:bson:20180225', 'https://github.com/mongodb/js-bson/commit/bd61c45157c53a1698ff23770160cf4783e9ea4a', 'https://nvd.nist.gov/vuln/detail/CVE-2018-13863'} | null | {'https://github.com/mongodb/js-bson/commit/bd61c45157c53a1698ff23770160cf4783e9ea4a'} | {'https://github.com/mongodb/js-bson/commit/bd61c45157c53a1698ff23770160cf4783e9ea4a'} |
GHSA | GHSA-xcwj-wfcm-m23c | Invalid validation in `SparseMatrixSparseCholesky` | ### Impact
An attacker can trigger a null pointer dereference by providing an invalid `permutation` to `tf.raw_ops.SparseMatrixSparseCholesky`:
```python
import tensorflow as tf
import numpy as np
from tensorflow.python.ops.linalg.sparse import sparse_csr_matrix_ops
indices_array = np.array([[0, 0]])
value_array = np.array([-10.0], dtype=np.float32)
dense_shape = [1, 1]
st = tf.SparseTensor(indices_array, value_array, dense_shape)
input = sparse_csr_matrix_ops.sparse_tensor_to_csr_sparse_matrix(
st.indices, st.values, st.dense_shape)
permutation = tf.constant([], shape=[1, 0], dtype=tf.int32)
tf.raw_ops.SparseMatrixSparseCholesky(input=input, permutation=permutation, type=tf.float32)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/080f1d9e257589f78b3ffb75debf584168aa6062/tensorflow/core/kernels/sparse/sparse_cholesky_op.cc#L85-L86) fails to properly validate the input arguments:
```cc
void Compute(OpKernelContext* ctx) final {
...
const Tensor& input_permutation_indices = ctx->input(1);
...
ValidateInputs(ctx, *input_matrix, input_permutation_indices, &batch_size, &num_rows);
...
}
void ValidateInputs(OpKernelContext* ctx,
const CSRSparseMatrix& sparse_matrix,
const Tensor& permutation_indices, int* batch_size,
int64* num_rows) {
OP_REQUIRES(ctx, sparse_matrix.dtype() == DataTypeToEnum<T>::value, ...)
...
}
```
Although `ValidateInputs` is called and there are checks in the body of this function, the code proceeds to the next line in `ValidateInputs` since [`OP_REQUIRES`](https://github.com/tensorflow/tensorflow/blob/080f1d9e257589f78b3ffb75debf584168aa6062/tensorflow/core/framework/op_requires.h#L41-L48) is a macro that only exits the current function.
```cc
#define OP_REQUIRES(CTX, EXP, STATUS) \
do { \
if (!TF_PREDICT_TRUE(EXP)) { \
CheckNotInComputeAsync((CTX), "OP_REQUIRES_ASYNC"); \
(CTX)->CtxFailure(__FILE__, __LINE__, (STATUS)); \
return; \
} \
} while (0)
```
Thus, the first validation condition that fails in `ValidateInputs` will cause an early return from that function. However, the caller will continue execution from the next line. The fix is to either explicitly check `context->status()` or to convert `ValidateInputs` to return a `Status`.
### Patches
We have patched the issue in GitHub commit [e6a7c7cc18c3aaad1ae0872cb0a959f5c923d2bd](https://github.com/tensorflow/tensorflow/commit/e6a7c7cc18c3aaad1ae0872cb0a959f5c923d2bd).
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-29530'} | 2021-05-21T14:22:09Z | 2021-05-21T14:22:09Z | LOW | 2.5 | {'CWE-476'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29530', 'https://github.com/advisories/GHSA-xcwj-wfcm-m23c', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-xcwj-wfcm-m23c', 'https://github.com/tensorflow/tensorflow/commit/e6a7c7cc18c3aaad1ae0872cb0a959f5c923d2bd'} | null | {'https://github.com/tensorflow/tensorflow/commit/e6a7c7cc18c3aaad1ae0872cb0a959f5c923d2bd'} | {'https://github.com/tensorflow/tensorflow/commit/e6a7c7cc18c3aaad1ae0872cb0a959f5c923d2bd'} |
GHSA | GHSA-24x6-8c7m-hv3f | Heap OOB read in TFLite's implementation of `Minimum` or `Maximum` | ### Impact
The implementations of the `Minimum` and `Maximum` TFLite operators can be used to read data outside of bounds of heap allocated objects, if any of the two input tensor arguments are empty.
This is because [the broadcasting implementation](https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/internal/reference/maximum_minimum.h#L52-L56) indexes in both tensors with the same index but does not validate that the index is within bounds:
```cc
auto maxmin_func = [&](int indexes[N]) {
output_data[SubscriptToIndex(output_desc, indexes)] =
op(input1_data[SubscriptToIndex(desc1, indexes)],
input2_data[SubscriptToIndex(desc2, indexes)]);
};
```
### Patches
We have patched the issue in GitHub commit [953f28dca13c92839ba389c055587cfe6c723578](https://github.com/tensorflow/tensorflow/commit/953f28dca13c92839ba389c055587cfe6c723578).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-29590'} | 2021-05-21T14:26:53Z | 2021-05-21T14:26:53Z | LOW | 2.5 | {'CWE-125'} | {'https://github.com/advisories/GHSA-24x6-8c7m-hv3f', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29590', 'https://github.com/tensorflow/tensorflow/commit/953f28dca13c92839ba389c055587cfe6c723578', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-24x6-8c7m-hv3f'} | null | {'https://github.com/tensorflow/tensorflow/commit/953f28dca13c92839ba389c055587cfe6c723578'} | {'https://github.com/tensorflow/tensorflow/commit/953f28dca13c92839ba389c055587cfe6c723578'} |
GHSA | GHSA-xmh9-rg6f-j3mr | Verification flaw in Solid identity-token-verifier | ### Impact
#### Severity
Any Pod on a Solid server using a vulnerable version of the identity-token-verifier library is at risk of a spoofed Demonstration of Proof-of-Possession (DPoP) token binding. This vulnerability could give total and complete access to a targeted Pod.
#### Summary
A verification flaw in the implementation of the identity token verifier library (https://github.com/solid/identity-token-verifier) allows DPoP proofs to be spoofed.
DPoP proofs are used to bind access tokens to a private key meant to be in sole possession of a specific user. Instead of verifying against the hash of an embedded public key, the library instead verifies against a field that an attacker can modify to spoof another user’s DPoP.
A stolen DPoP proof, when used in the right context, therefore allows the rebinding of a DPoP-bound access token. Any attacker in possession of a targeted access token could build an attack environment to replay it on any Pod service with this vulnerability.
### Patches
A new version 0.5.2 of identity-token-verifier fixes the verification: https://github.com/solid/identity-token-verifier/blob/7e18d86d65ee681e8ae912b6a032a1bae3cae570/src/lib/DPoP.ts#L25-L35
### Workarounds
None
### References
_Are there any links users can visit to find out more?_
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [identity-token-verifier](https://github.com/solid/identity-token-verifier/) repository.
* Email: info@solidproject.org | null | 2021-03-12T22:39:01Z | 2021-03-12T22:39:01Z | MODERATE | 0 | {'CWE-290'} | {'https://github.com/solid/identity-token-verifier/security/advisories/GHSA-xmh9-rg6f-j3mr', 'https://github.com/solid/identity-token-verifier/commit/fbdeb4aa8c12694b3744cd0454acb826817d9e6c', 'https://github.com/advisories/GHSA-xmh9-rg6f-j3mr', 'https://www.npmjs.com/package/@solid/identity-token-verifier', 'https://github.com/solid/identity-token-verifier/releases/tag/0.5.2'} | null | {'https://github.com/solid/identity-token-verifier/commit/fbdeb4aa8c12694b3744cd0454acb826817d9e6c'} | {'https://github.com/solid/identity-token-verifier/commit/fbdeb4aa8c12694b3744cd0454acb826817d9e6c'} |
GHSA | GHSA-ph87-fvjr-v33w | CHECK-fail in `tf.raw_ops.RFFT` | ### Impact
An attacker can cause a denial of service by exploiting a `CHECK`-failure coming from the implementation of `tf.raw_ops.RFFT`:
```python
import tensorflow as tf
inputs = tf.constant([1], shape=[1], dtype=tf.float32)
fft_length = tf.constant([0], shape=[1], dtype=tf.int32)
tf.raw_ops.RFFT(input=inputs, fft_length=fft_length)
```
The above example causes Eigen code to operate on an empty matrix. This triggers on an assertion and causes program termination.
### Patches
We have patched the issue in GitHub commit [31bd5026304677faa8a0b77602c6154171b9aec1](https://github.com/tensorflow/tensorflow/commit/31bd5026304677faa8a0b77602c6154171b9aec1).
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-29563'} | 2021-05-21T14:25:05Z | 2021-05-21T14:25:05Z | LOW | 2.5 | {'CWE-617'} | {'https://github.com/advisories/GHSA-ph87-fvjr-v33w', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29563', 'https://github.com/tensorflow/tensorflow/commit/31bd5026304677faa8a0b77602c6154171b9aec1', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-ph87-fvjr-v33w'} | null | {'https://github.com/tensorflow/tensorflow/commit/31bd5026304677faa8a0b77602c6154171b9aec1'} | {'https://github.com/tensorflow/tensorflow/commit/31bd5026304677faa8a0b77602c6154171b9aec1'} |
GHSA | GHSA-h67m-xg8f-fxcf | Deadlock in mutually recursive `tf.function` objects | ### Impact
The [code behind `tf.function` API](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/python/eager/def_function.py#L542) can be made to deadlock when two `tf.function` decorated Python functions are mutually recursive:
```python
import tensorflow as tf
@tf.function()
def fun1(num):
if num == 1:
return
print(num)
fun2(num-1)
@tf.function()
def fun2(num):
if num == 0:
return
print(num)
fun1(num-1)
fun1(9)
```
This occurs due to using a non-reentrant `Lock` Python object.
Loading any model which contains mutually recursive functions is vulnerable. An attacker can cause denial of service by causing users to load such models and calling a recursive `tf.function`, although this is not a frequent scenario.
### Patches
We have patched the issue in GitHub commit [afac8158d43691661ad083f6dd9e56f327c1dcb7](https://github.com/tensorflow/tensorflow/commit/afac8158d43691661ad083f6dd9e56f327c1dcb7).
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-41213'} | 2021-11-10T18:59:32Z | 2021-11-10T18:59:32Z | MODERATE | 5.5 | {'CWE-667'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-h67m-xg8f-fxcf', 'https://github.com/advisories/GHSA-h67m-xg8f-fxcf', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41213', 'https://github.com/tensorflow/tensorflow/commit/afac8158d43691661ad083f6dd9e56f327c1dcb7'} | null | {'https://github.com/tensorflow/tensorflow/commit/afac8158d43691661ad083f6dd9e56f327c1dcb7'} | {'https://github.com/tensorflow/tensorflow/commit/afac8158d43691661ad083f6dd9e56f327c1dcb7'} |
GHSA | GHSA-p4v2-r99v-wjc2 | Improper Encoding or Escaping of Output in Nicotine+ | Denial of service (DoS) vulnerability in Nicotine+ starting with version 3.0.3 and prior to version 3.2.1 allows a user with a modified Soulseek client to crash Nicotine+ by sending a file download request with a file path containing a null character. | {'CVE-2021-45848'} | 2022-03-29T21:18:19Z | 2022-03-16T00:00:38Z | HIGH | 7.5 | {'CWE-116'} | {'https://github.com/nicotine-plus/nicotine-plus/issues/1777', 'https://github.com/nicotine-plus/nicotine-plus/commit/0e3e2fac27a518f0a84330f1ddf1193424522045', 'https://github.com/advisories/GHSA-p4v2-r99v-wjc2', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HWYV53KERFH2EC4XI2IVVQFTV75E5XM6/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-45848'} | null | {'https://github.com/nicotine-plus/nicotine-plus/commit/0e3e2fac27a518f0a84330f1ddf1193424522045'} | {'https://github.com/nicotine-plus/nicotine-plus/commit/0e3e2fac27a518f0a84330f1ddf1193424522045'} |
GHSA | GHSA-vj54-cjrx-x696 | Observable Discrepancy in Argo | Fixed in v1.5.1, Argo version v1.5.0 was vulnerable to a user-enumeration vulnerability which allowed attackers to determine the usernames of valid (non-SSO) accounts within Argo. | {'CVE-2020-11576'} | 2021-12-09T19:59:24Z | 2021-12-09T19:59:24Z | MODERATE | 5.3 | {'CWE-203'} | {'https://github.com/argoproj/argo-cd/commit/35a7350b7444bcaf53ee0bb11b9d8e3ae4b717a1', 'https://www.soluble.ai/blog/argo-cves-2020', 'https://github.com/advisories/GHSA-vj54-cjrx-x696', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11576', 'https://github.com/argoproj/argo-cd/pull/3215'} | null | {'https://github.com/argoproj/argo-cd/commit/35a7350b7444bcaf53ee0bb11b9d8e3ae4b717a1'} | {'https://github.com/argoproj/argo-cd/commit/35a7350b7444bcaf53ee0bb11b9d8e3ae4b717a1'} |
GHSA | GHSA-6gg3-pmm7-97xc | DOM-based XSS in auth0-lock | ### Overview
Versions before and including `11.25.1` are using `dangerouslySetInnerHTML` to display an informational message when used with a Passwordless or Enterprise connection.
- For Passwordless connection, the value of the input (email or phone number) is displayed back to the user while waiting for verification code input.
- For Enterprise connection, the value of the input (IdP Domain) from the Enterprise connection setup screen (Auth0 Dashboard) is displayed back to the user when the `lock` widget opens.
When Passwordless or Enterprise connection is used, the application and its users might be exposed to cross-site scripting (XSS) attacks.
### Am I affected?
You are affected by this vulnerability if all of the following conditions apply:
- You are using auth0-lock
- You are using Passwordless or Enterprise connection mode
### How to fix that?
Upgrade to version `11.26.3`
### Will this update impact my users?
The fix provided in patch will not affect your users.
### Credit
https://github.com/mvisat | {'CVE-2020-15119'} | 2022-04-19T19:02:31Z | 2020-08-19T21:05:03Z | LOW | 6.4 | {'CWE-79'} | {'https://github.com/auth0/lock/commit/3711fb5b42afd40073a61a58759251f51e768b1b', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15119', 'https://github.com/auth0/lock/security/advisories/GHSA-6gg3-pmm7-97xc', 'https://github.com/advisories/GHSA-6gg3-pmm7-97xc'} | null | {'https://github.com/auth0/lock/commit/3711fb5b42afd40073a61a58759251f51e768b1b'} | {'https://github.com/auth0/lock/commit/3711fb5b42afd40073a61a58759251f51e768b1b'} |
GHSA | GHSA-vwhq-49r4-gj9v | Reference binding to `nullptr` in `tf.ragged.cross` | ### Impact
The [shape inference code for `tf.ragged.cross`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/ragged_array_ops.cc#L64) has an undefined behavior due to binding a reference to `nullptr`. In the following scenario, this results in a crash:
```python
import tensorflow as tf
@tf.function
def test():
y = tf.ragged.cross([tf.ragged.constant([['1']]),'2'])
return y
test()
```
### Patches
We have patched the issue in GitHub commit [fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8](https://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8).
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-41214'} | 2021-11-10T18:58:16Z | 2021-11-10T18:58:16Z | HIGH | 7.8 | {'CWE-824'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-41214', 'https://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8', 'https://github.com/advisories/GHSA-vwhq-49r4-gj9v', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-vwhq-49r4-gj9v'} | null | {'https://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8'} | {'https://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8'} |
GHSA | GHSA-vh5c-jqfg-mhrh | Cross-Site Request Forgery in xwiki-platform | ### Impact
It's possible to know if a user has or not an account in a wiki related to an email address, and which username(s) is actually tight to that email by forging a request to the Forgot username page. Note that since this page does not have a CSRF check it's quite easy to perform a lot of those requests.
### Patches
This issue has been patched in XWiki 12.10.5 and 13.2RC1. Two different patches are provided:
- a first one to fix the CSRF problem
- a more complex one that now relies on sending an email for the Forgot username process.
### Workarounds
It's possible to fix the problem without uprading by editing the ForgotUsername page in version below 13.x, to use the following code: https://github.com/xwiki/xwiki-platform/blob/69548c0320cbd772540cf4668743e69f879812cf/xwiki-platform-core/xwiki-platform-administration/xwiki-platform-administration-ui/src/main/resources/XWiki/ForgotUsername.xml#L39-L123
In version after 13.x it's also possible to edit manually the forgotusername.vm file, but it's really encouraged to upgrade the version here.
### References
* https://jira.xwiki.org/browse/XWIKI-18384
* https://jira.xwiki.org/browse/XWIKI-18408
### 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 [security ML](mailto:security@xwiki.org)
| {'CVE-2021-32732'} | 2022-02-11T21:08:09Z | 2022-02-10T22:42:46Z | HIGH | 7.5 | {'CWE-352'} | {'https://jira.xwiki.org/browse/XWIKI-18408', 'https://github.com/advisories/GHSA-vh5c-jqfg-mhrh', 'https://github.com/xwiki/xwiki-platform/commit/f0440dfcbba705e03f7565cd88893dde57ca3fa8', 'https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-vh5c-jqfg-mhrh', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32732', 'https://github.com/xwiki/xwiki-platform/commit/69548c0320cbd772540cf4668743e69f879812cf', 'https://jira.xwiki.org/browse/XWIKI-18384'} | null | {'https://github.com/xwiki/xwiki-platform/commit/69548c0320cbd772540cf4668743e69f879812cf', 'https://github.com/xwiki/xwiki-platform/commit/f0440dfcbba705e03f7565cd88893dde57ca3fa8'} | {'https://github.com/xwiki/xwiki-platform/commit/69548c0320cbd772540cf4668743e69f879812cf', 'https://github.com/xwiki/xwiki-platform/commit/f0440dfcbba705e03f7565cd88893dde57ca3fa8'} |
GHSA | GHSA-grmf-4fq6-2r79 | Improper Restriction of Operations within the Bounds of a Memory Buffer in aubio | aubio v0.4.0 to v0.4.8 has a Buffer Overflow in new_aubio_tempo. | {'CVE-2018-19800'} | 2022-03-21T19:05:04Z | 2019-07-26T16:10:28Z | CRITICAL | 9.8 | {'CWE-119'} | {'https://github.com/aubio/aubio/commit/b1559f4c9ce2b304d8d27ffdc7128b6795ca82e5', 'https://github.com/advisories/GHSA-grmf-4fq6-2r79', 'https://github.com/aubio/aubio/blob/0.4.9/ChangeLog', 'https://nvd.nist.gov/vuln/detail/CVE-2018-19800'} | null | {'https://github.com/aubio/aubio/commit/b1559f4c9ce2b304d8d27ffdc7128b6795ca82e5'} | {'https://github.com/aubio/aubio/commit/b1559f4c9ce2b304d8d27ffdc7128b6795ca82e5'} |
GHSA | GHSA-fxh6-w476-hgr4 | Directory Traversal in SharpCompress | SharpCompress prior to version 0.21 is vulnerable to path traversal issue in archive extraction. | {'CVE-2018-1002206'} | 2021-08-17T22:21:47Z | 2019-09-11T22:59:57Z | MODERATE | 5.5 | {'CWE-22'} | {'https://github.com/adamhathcock/sharpcompress/commit/80ceb1c375fdb1b4ffba16528c99089e804ce61f', 'https://github.com/advisories/GHSA-fxh6-w476-hgr4'} | null | {'https://github.com/adamhathcock/sharpcompress/commit/80ceb1c375fdb1b4ffba16528c99089e804ce61f'} | {'https://github.com/adamhathcock/sharpcompress/commit/80ceb1c375fdb1b4ffba16528c99089e804ce61f'} |
GHSA | GHSA-mvvp-gwgc-5hrp | Path Traversal in elFinder.Net.Core | This affects the package elFinder.Net.Core from 0 and before 1.2.4. The user-controlled file name is not properly sanitized before it is used to create a file system path. | {'CVE-2021-23407'} | 2021-08-31T21:21:26Z | 2021-08-02T17:30:27Z | HIGH | 7.5 | {'CWE-22'} | {'https://github.com/advisories/GHSA-mvvp-gwgc-5hrp', 'https://github.com/trannamtrung1st/elFinder.Net.Core/commit/5498c8a86b76ef089cfbd7ef8be014b61fa11c73', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23407', 'https://snyk.io/vuln/SNYK-DOTNET-ELFINDERNETCORE-1315152', 'https://github.com/trannamtrung1st/elFinder.Net.Core/releases/tag/all-1.2.4'} | null | {'https://github.com/trannamtrung1st/elFinder.Net.Core/commit/5498c8a86b76ef089cfbd7ef8be014b61fa11c73'} | {'https://github.com/trannamtrung1st/elFinder.Net.Core/commit/5498c8a86b76ef089cfbd7ef8be014b61fa11c73'} |
GHSA | GHSA-q3j5-32m5-58c2 | Privilege Elevation in runc | libcontainer/user/user.go in runC before 0.1.0, as used in Docker before 1.11.2, improperly treats a numeric UID as a potential username, which allows local users to gain privileges via a numeric username in the password file in a container. | {'CVE-2016-3697'} | 2021-12-20T18:21:34Z | 2021-12-20T18:21:34Z | HIGH | 7.8 | null | {'https://github.com/opencontainers/runc/releases/tag/v0.1.0', 'https://lists.opensuse.org/opensuse-updates/2016-05/msg00111.html', 'https://rhn.redhat.com/errata/RHSA-2016-2634.html', 'https://github.com/advisories/GHSA-q3j5-32m5-58c2', 'https://security.gentoo.org/glsa/201612-28', 'https://nvd.nist.gov/vuln/detail/CVE-2016-3697', 'https://rhn.redhat.com/errata/RHSA-2016-1034.html', 'https://github.com/docker/docker/issues/21436', 'https://github.com/opencontainers/runc/commit/69af385de62ea68e2e608335cffbb0f4aa3db091', 'https://github.com/opencontainers/runc/pull/708'} | null | {'https://github.com/opencontainers/runc/commit/69af385de62ea68e2e608335cffbb0f4aa3db091'} | {'https://github.com/opencontainers/runc/commit/69af385de62ea68e2e608335cffbb0f4aa3db091'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.