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-273r-mgr4-v34f | Uncaught Exception in engine.io | ### Impact
A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process.
> RangeError: Invalid WebSocket frame: RSV2 and RSV3 must be clear
> at Receiver.getInfo (/.../node_modules/ws/lib/receiver.js:176:14)
> at Receiver.startLoop (/.../node_modules/ws/lib/receiver.js:136:22)
> at Receiver._write (/.../node_modules/ws/lib/receiver.js:83:10)
> at writeOrBuffer (internal/streams/writable.js:358:12)
This impacts all the users of the [`engine.io`](https://www.npmjs.com/package/engine.io) package starting from version `4.0.0`, including those who uses depending packages like [`socket.io`](https://www.npmjs.com/package/socket.io).
### Patches
A fix has been released for each major branch:
| Version range | Fixed version |
| --- | --- |
| `engine.io@4.x.x` | `4.1.2` |
| `engine.io@5.x.x` | `5.2.1` |
| `engine.io@6.x.x` | `6.1.1` |
Previous versions (`< 4.0.0`) are not impacted.
For `socket.io` users:
| Version range | `engine.io` version | Needs minor update? |
| --- | --- | --- |
| `socket.io@4.4.x` | `~6.1.0` | -
| `socket.io@4.3.x` | `~6.0.0` | Please upgrade to `socket.io@4.4.x`
| `socket.io@4.2.x` | `~5.2.0` | -
| `socket.io@4.1.x` | `~5.1.1` | Please upgrade to `socket.io@4.4.x`
| `socket.io@4.0.x` | `~5.0.0` | Please upgrade to `socket.io@4.4.x`
| `socket.io@3.1.x` | `~4.1.0` | -
| `socket.io@3.0.x` | `~4.0.0` | Please upgrade to `socket.io@3.1.x` or `socket.io@4.4.x` (see [here](https://socket.io/docs/v4/migrating-from-3-x-to-4-0/))
In most cases, running `npm audit fix` should be sufficient. You can also use `npm update engine.io --depth=9999`.
### Workarounds
There is no known workaround except upgrading to a safe version.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [`engine.io`](https://github.com/socketio/engine.io)
Thanks to Marcus Wejderot from Mevisio for the responsible disclosure.
| {'CVE-2022-21676'} | 2022-04-19T19:03:20Z | 2022-01-13T16:14:17Z | HIGH | 7.5 | {'CWE-754'} | {'https://github.com/socketio/engine.io/commit/c0e194d44933bd83bf9a4b126fca68ba7bf5098c', 'https://github.com/socketio/engine.io/commit/a70800d7e96da32f6e6622804ef659ebc58659db', 'https://github.com/socketio/engine.io/releases/tag/4.1.2', 'https://github.com/socketio/engine.io/releases/tag/5.2.1', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21676', 'https://github.com/socketio/engine.io/security/advisories/GHSA-273r-mgr4-v34f', 'https://github.com/socketio/engine.io/releases/tag/6.1.1', 'https://github.com/advisories/GHSA-273r-mgr4-v34f', 'https://github.com/socketio/engine.io/commit/66f889fc1d966bf5bfa0de1939069153643874ab'} | null | {'https://github.com/socketio/engine.io/commit/66f889fc1d966bf5bfa0de1939069153643874ab', 'https://github.com/socketio/engine.io/commit/a70800d7e96da32f6e6622804ef659ebc58659db', 'https://github.com/socketio/engine.io/commit/c0e194d44933bd83bf9a4b126fca68ba7bf5098c'} | {'https://github.com/socketio/engine.io/commit/a70800d7e96da32f6e6622804ef659ebc58659db', 'https://github.com/socketio/engine.io/commit/c0e194d44933bd83bf9a4b126fca68ba7bf5098c', 'https://github.com/socketio/engine.io/commit/66f889fc1d966bf5bfa0de1939069153643874ab'} |
GHSA | GHSA-j8qc-5fqr-52fp | Division by zero in `Conv2DBackpropFilter` | ### Impact
An attacker can cause a division by zero to occur in `Conv2DBackpropFilter`:
```python
import tensorflow as tf
input_tensor = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)
filter_sizes = tf.constant([0, 0, 0, 0], shape=[4], dtype=tf.int32)
out_backprop = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)
tf.raw_ops.Conv2DBackpropFilter(
input=input_tensor,
filter_sizes=filter_sizes,
out_backprop=out_backprop,
strides=[1, 1, 1, 1],
use_cudnn_on_gpu=False,
padding='SAME',
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#L513-L522) computes a divisor based on user provided data (i.e., the shape of the tensors given as arguments):
```cc
const size_t size_A = output_image_size * filter_total_size;
const size_t size_B = output_image_size * dims.out_depth;
const size_t size_C = filter_total_size * dims.out_depth;
const size_t work_unit_size = size_A + size_B + size_C;
const size_t shard_size = (target_working_set_size + work_unit_size - 1) / work_unit_size;
```
If all shapes are empty then `work_unit_size` is 0. Since there is no check for this case before division, this results in a runtime exception, with potential to be abused for a denial of service.
### 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-29538'} | 2021-05-21T14:22:38Z | 2021-05-21T14:22:38Z | LOW | 2.5 | {'CWE-369'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-j8qc-5fqr-52fp', 'https://github.com/tensorflow/tensorflow/commit/c570e2ecfc822941335ad48f6e10df4e21f11c96', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29538', 'https://github.com/advisories/GHSA-j8qc-5fqr-52fp'} | null | {'https://github.com/tensorflow/tensorflow/commit/c570e2ecfc822941335ad48f6e10df4e21f11c96'} | {'https://github.com/tensorflow/tensorflow/commit/c570e2ecfc822941335ad48f6e10df4e21f11c96'} |
GHSA | GHSA-cx3w-xqmc-84g5 | Git LFS can execute a Git binary from the current directory on Windows | ### Impact
On Windows, if Git LFS operates on a malicious repository with a git.bat or git.exe file in the current directory, that program would be executed, permitting the attacker to execute arbitrary code. This does not affect Unix systems.
This is the result of an incomplete fix for CVE-2020-27955.
This issue occurs because on Windows, [Go includes (and prefers) the current directory when the name of a command run does not contain a directory separator](https://github.com/golang/go/issues/38736).
### Patches
This version should be patched in v2.13.2, which will be released in coordination with this security advisory.
### Workarounds
Other than avoiding untrusted repositories or using a different operating system, there is no workaround.
### 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:
- Start a discussion in [the Git LFS discussion page](https://github.com/git-lfs/git-lfs/discussions).
- If you cannot open a discussion, please email the core team using their usernames at `github.com`. | {'CVE-2021-21237'} | 2022-04-20T16:24:42Z | 2022-02-15T00:30:37Z | HIGH | 7.2 | {'CWE-94', 'CWE-426'} | {'https://github.com/advisories/GHSA-cx3w-xqmc-84g5', 'https://github.com/git-lfs/git-lfs/commit/fc664697ed2c2081ee9633010de0a7f9debea72a', 'https://github.com/git-lfs/git-lfs/security/advisories/GHSA-cx3w-xqmc-84g5', 'https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27955', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21237', 'https://github.com/git-lfs/git-lfs/releases/tag/v2.13.2'} | null | {'https://github.com/git-lfs/git-lfs/commit/fc664697ed2c2081ee9633010de0a7f9debea72a'} | {'https://github.com/git-lfs/git-lfs/commit/fc664697ed2c2081ee9633010de0a7f9debea72a'} |
GHSA | GHSA-jp6r-xcjj-5h7r | Cross-Site Scripting in cyberchef | Versions of `cyberchef` prior to 8.31.3 are vulnerable to Cross-Site Scripting. In `Text Encoding Brute Force` the table rows are created by concatenating the `value` variable unsanitized in the HTML code. If this variable is controlled by user input it allows attackers to execute arbitrary JavaScript in a victim's browser.
## Recommendation
Upgrade to version 8.31.3 or later. | {'CVE-2019-15532'} | 2021-08-17T22:11:12Z | 2019-08-27T17:36:32Z | MODERATE | 6.1 | {'CWE-79'} | {'https://github.com/gchq/CyberChef/commit/01f0625d6a177f9c5df9281f12a27c814c2d8bcf', 'https://github.com/gchq/CyberChef/compare/v8.31.1...v8.31.2', 'https://github.com/advisories/GHSA-jp6r-xcjj-5h7r', 'https://snyk.io/vuln/SNYK-JS-CYBERCHEF-460296', 'https://www.npmjs.com/advisories/1149', 'https://nvd.nist.gov/vuln/detail/CVE-2019-15532', 'https://github.com/gchq/CyberChef/issues/539', 'https://github.com/gchq/CyberChef/issues/544'} | null | {'https://github.com/gchq/CyberChef/commit/01f0625d6a177f9c5df9281f12a27c814c2d8bcf'} | {'https://github.com/gchq/CyberChef/commit/01f0625d6a177f9c5df9281f12a27c814c2d8bcf'} |
GHSA | GHSA-gprm-xqrc-c2j3 | Command Injection in Kylin | Kylin has some restful apis which will concatenate os command with the user input string, a user is likely to be able to execute any os command without any protection or validation. | {'CVE-2020-1956'} | 2021-09-22T21:56:35Z | 2020-07-27T22:51:44Z | HIGH | 8.8 | {'CWE-78'} | {'https://lists.apache.org/thread.html/r250a867961cfd6e0506240a9c7eaee782d84c6ab0091c7c4bc45f3eb@%3Cuser.kylin.apache.org%3E', 'https://lists.apache.org/thread.html/r61666760d8a4e8764b2d5fe158d8a48b569414480fbfadede574cdc0@%3Ccommits.kylin.apache.org%3E', 'https://github.com/advisories/GHSA-gprm-xqrc-c2j3', 'https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEKYLIN-570207', 'https://community.sonarsource.com/t/apache-kylin-3-0-1-command-injection-vulnerability/25706', 'https://github.com/apache/kylin/commit/58fad56ac6aaa43c6bd8f962d7f2d84438664092', 'https://lists.apache.org/thread.html/r021baf9d8d4ae41e8c8332c167c4fa96c91b5086563d9be55d2d7acf@%3Ccommits.kylin.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-1956', 'https://lists.apache.org/thread.html/r250a867961cfd6e0506240a9c7eaee782d84c6ab0091c7c4bc45f3eb@%3Cdev.kylin.apache.org%3E', 'https://lists.apache.org/thread.html/r1332ef34cf8e2c0589cf44ad269fb1fb4c06addec6297f0320f5111d%40%3Cuser.kylin.apache.org%3E', 'https://lists.apache.org/thread.html/r250a867961cfd6e0506240a9c7eaee782d84c6ab0091c7c4bc45f3eb@%3Cannounce.apache.org%3E', 'http://www.openwall.com/lists/oss-security/2020/07/14/1'} | null | {'https://github.com/apache/kylin/commit/58fad56ac6aaa43c6bd8f962d7f2d84438664092'} | {'https://github.com/apache/kylin/commit/58fad56ac6aaa43c6bd8f962d7f2d84438664092'} |
GHSA | GHSA-6j9c-grc6-5m6g | CHECK-fail in SparseConcat | ### Impact
An attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.SparseConcat`:
```python
import tensorflow as tf
import numpy as np
indices_1 = tf.constant([[514, 514], [514, 514]], dtype=tf.int64)
indices_2 = tf.constant([[514, 530], [599, 877]], dtype=tf.int64)
indices = [indices_1, indices_2]
values_1 = tf.zeros([0], dtype=tf.int64)
values_2 = tf.zeros([0], dtype=tf.int64)
values = [values_1, values_2]
shape_1 = tf.constant([442, 514, 514, 515, 606, 347, 943, 61, 2], dtype=tf.int64)
shape_2 = tf.zeros([9], dtype=tf.int64)
shapes = [shape_1, shape_2]
tf.raw_ops.SparseConcat(indices=indices, values=values, shapes=shapes, concat_dim=2)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/b432a38fe0e1b4b904a6c222cbce794c39703e87/tensorflow/core/kernels/sparse_concat_op.cc#L76) takes the values specified in `shapes[0]` as dimensions for the output shape:
```cc
TensorShape input_shape(shapes[0].vec<int64>());
```
The [`TensorShape` constructor](https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L183-L188) uses a `CHECK` operation which triggers when [`InitDims`](https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L212-L296) returns a non-OK status.
```cc
template <class Shape>
TensorShapeBase<Shape>::TensorShapeBase(gtl::ArraySlice<int64> dim_sizes) {
set_tag(REP16);
set_data_type(DT_INVALID);
TF_CHECK_OK(InitDims(dim_sizes));
}
```
In our scenario, this occurs when adding a dimension from the argument results in overflow:
```cc
template <class Shape>
Status TensorShapeBase<Shape>::InitDims(gtl::ArraySlice<int64> dim_sizes) {
...
Status status = Status::OK();
for (int64 s : dim_sizes) {
status.Update(AddDimWithStatus(internal::SubtleMustCopy(s)));
if (!status.ok()) {
return status;
}
}
}
template <class Shape>
Status TensorShapeBase<Shape>::AddDimWithStatus(int64 size) {
...
int64 new_num_elements;
if (kIsPartial && (num_elements() < 0 || size < 0)) {
new_num_elements = -1;
} else {
new_num_elements = MultiplyWithoutOverflow(num_elements(), size);
if (TF_PREDICT_FALSE(new_num_elements < 0)) {
return errors::Internal("Encountered overflow when multiplying ",
num_elements(), " with ", size,
", result: ", new_num_elements);
}
}
...
}
```
This is a legacy implementation of the constructor and operations should use `BuildTensorShapeBase` or `AddDimWithStatus` to prevent `CHECK`-failures in the presence of overflows.
### Patches
We have patched the issue in GitHub commit [69c68ecbb24dff3fa0e46da0d16c821a2dd22d7c](https://github.com/tensorflow/tensorflow/commit/69c68ecbb24dff3fa0e46da0d16c821a2dd22d7c).
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-29534'} | 2021-05-21T14:22:24Z | 2021-05-21T14:22:24Z | LOW | 2.5 | {'CWE-754'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29534', 'https://github.com/tensorflow/tensorflow/commit/69c68ecbb24dff3fa0e46da0d16c821a2dd22d7c', 'https://github.com/advisories/GHSA-6j9c-grc6-5m6g', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-6j9c-grc6-5m6g'} | null | {'https://github.com/tensorflow/tensorflow/commit/69c68ecbb24dff3fa0e46da0d16c821a2dd22d7c'} | {'https://github.com/tensorflow/tensorflow/commit/69c68ecbb24dff3fa0e46da0d16c821a2dd22d7c'} |
GHSA | GHSA-5f7m-mmpc-qhh4 | Remote Memory Exposure in mysql | Versions of `mysql` before 2.14.0 are vulnerable to remove memory exposure.
Affected versions of `mysql` package allocate and send an uninitialized memory over the network when a number is provided as a password.
Only `mysql` running on Node.js versions below 6.0.0 is affected due to a throw added in newer node.js versions.
Proof of Concept:
```
require('mysql').createConnection({
host: 'localhost',
user: 'user',
password : USERPROVIDEDINPUT, // number
database : 'my_db'
}).connect();
```
## Recommendation
Update to version 2.14.0 or later. | null | 2021-08-04T15:50:29Z | 2019-05-23T09:27:00Z | MODERATE | 0 | {'CWE-201'} | {'https://github.com/mysqljs/mysql/commit/310c6a7d1b2e14b63b572dbfbfa10128f20c6d52', 'https://www.npmjs.com/advisories/602', 'https://github.com/advisories/GHSA-5f7m-mmpc-qhh4', 'https://nodesecurity.io/advisories/602'} | null | {'https://github.com/mysqljs/mysql/commit/310c6a7d1b2e14b63b572dbfbfa10128f20c6d52'} | {'https://github.com/mysqljs/mysql/commit/310c6a7d1b2e14b63b572dbfbfa10128f20c6d52'} |
GHSA | GHSA-jv35-xqg7-f92r | Prototype Pollution | Prototype pollution vulnerability in ‘set-getter’ version 0.1.0 allows an attacker to cause a denial of service and may lead to remote code execution. | {'CVE-2021-25949'} | 2021-10-21T13:11:55Z | 2021-06-21T17:16:09Z | CRITICAL | 9.8 | {'CWE-1321'} | {'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25949', 'https://github.com/advisories/GHSA-jv35-xqg7-f92r', 'https://github.com/doowb/set-getter/blob/5bc2750fe1c3db9651d936131be187744111378d/index.js#L56', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25949', 'https://github.com/doowb/set-getter/commit/66eb3f0d4686a4a8c7c3d6f7ecd8e570b580edc4'} | null | {'https://github.com/doowb/set-getter/commit/66eb3f0d4686a4a8c7c3d6f7ecd8e570b580edc4'} | {'https://github.com/doowb/set-getter/commit/66eb3f0d4686a4a8c7c3d6f7ecd8e570b580edc4'} |
GHSA | GHSA-92x2-jw7w-xvvx | Cookie and header exposure in twisted | ### Impact
Cookie and Authorization headers are leaked when following cross-origin redirects in `twited.web.client.RedirectAgent` and `twisted.web.client.BrowserLikeRedirectAgent`. | {'CVE-2022-21712'} | 2022-04-25T07:14:43Z | 2022-02-07T22:36:00Z | HIGH | 7.5 | {'CWE-200', 'CWE-346'} | {'https://github.com/twisted/twisted/releases/tag/twisted-22.1.0', 'https://github.com/advisories/GHSA-92x2-jw7w-xvvx', 'https://lists.debian.org/debian-lts-announce/2022/02/msg00021.html', 'https://github.com/twisted/twisted/security/advisories/GHSA-92x2-jw7w-xvvx', 'https://github.com/twisted/twisted/commit/af8fe78542a6f2bf2235ccee8158d9c88d31e8e2', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21712'} | null | {'https://github.com/twisted/twisted/commit/af8fe78542a6f2bf2235ccee8158d9c88d31e8e2'} | {'https://github.com/twisted/twisted/commit/af8fe78542a6f2bf2235ccee8158d9c88d31e8e2'} |
GHSA | GHSA-px4w-rcv2-6x8x | Arbitrary code execution in Apache ServiceComb java-chassis | When handler-router component is enabled in servicecomb-java-chassis, authenticated user may inject some data and cause arbitrary code execution.
The problem happens in versions between 2.0.0 ~ 2.1.3 and fixed in Apache ServiceComb-Java-Chassis 2.1.5 | {'CVE-2020-17532'} | 2022-02-09T22:19:00Z | 2022-02-09T22:19:00Z | HIGH | 8.8 | {'CWE-502'} | {'https://seclists.org/oss-sec/2021/q1/60', 'https://issues.apache.org/jira/browse/SCB-2145', 'https://nvd.nist.gov/vuln/detail/CVE-2020-17532', 'https://github.com/apache/servicecomb-java-chassis/commit/839a52e27c754cb5ce14f20063902f21065bd26c', 'https://github.com/advisories/GHSA-px4w-rcv2-6x8x', 'https://github.com/apache/servicecomb-java-chassis/commit/ba4fb37b6ab8bd3a6c3d0693f295d99a94879838'} | null | {'https://github.com/apache/servicecomb-java-chassis/commit/839a52e27c754cb5ce14f20063902f21065bd26c', 'https://github.com/apache/servicecomb-java-chassis/commit/ba4fb37b6ab8bd3a6c3d0693f295d99a94879838'} | {'https://github.com/apache/servicecomb-java-chassis/commit/839a52e27c754cb5ce14f20063902f21065bd26c', 'https://github.com/apache/servicecomb-java-chassis/commit/ba4fb37b6ab8bd3a6c3d0693f295d99a94879838'} |
GHSA | GHSA-mq6c-fh97-4gwv | Denial of Service vulnerability with large JSON payloads in fastify | Affected versions of `fastify` are vulnerable to a denial of service when processing a request with `Content-Type` set to `application/json` and a very large payload.
## Recommendation
Update to version 0.38.0 or later. | {'CVE-2018-3711'} | 2022-04-19T19:03:25Z | 2018-07-18T21:20:34Z | HIGH | 0 | {'CWE-770'} | {'https://github.com/fastify/fastify/pull/627', 'https://hackerone.com/reports/303632', 'https://www.npmjs.com/advisories/564', 'https://github.com/fastify/fastify/commit/fabd2a011f2ffbb877394abe699f549513ffbd76', 'https://github.com/advisories/GHSA-mq6c-fh97-4gwv', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3711'} | null | {'https://github.com/fastify/fastify/commit/fabd2a011f2ffbb877394abe699f549513ffbd76'} | {'https://github.com/fastify/fastify/commit/fabd2a011f2ffbb877394abe699f549513ffbd76'} |
GHSA | GHSA-c582-c96p-r5cq | Memory exhaustion in Tensorflow | ### Impact
The [implementation of `ThreadPoolHandle`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/data/experimental/threadpool_dataset_op.cc#L79-L135) can be used to trigger a denial of service attack by allocating too much memory:
```python
import tensorflow as tf
y = tf.raw_ops.ThreadPoolHandle(num_threads=0x60000000,display_name='tf')
```
This is because the `num_threads` argument is only checked to not be negative, but there is no upper bound on its value.
### Patches
We have patched the issue in GitHub commit [e3749a6d5d1e8d11806d4a2e9cc3123d1a90b75e](https://github.com/tensorflow/tensorflow/commit/e3749a6d5d1e8d11806d4a2e9cc3123d1a90b75e).
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 Yu Tian of Qihoo 360 AIVul Team. | {'CVE-2022-21732'} | 2022-02-11T17:05:43Z | 2022-02-10T00:20:29Z | MODERATE | 4.3 | {'CWE-400', 'CWE-770'} | {'https://github.com/tensorflow/tensorflow/commit/e3749a6d5d1e8d11806d4a2e9cc3123d1a90b75e', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21732', 'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/data/experimental/threadpool_dataset_op.cc#L79-L135', 'https://github.com/advisories/GHSA-c582-c96p-r5cq', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-c582-c96p-r5cq'} | null | {'https://github.com/tensorflow/tensorflow/commit/e3749a6d5d1e8d11806d4a2e9cc3123d1a90b75e'} | {'https://github.com/tensorflow/tensorflow/commit/e3749a6d5d1e8d11806d4a2e9cc3123d1a90b75e'} |
GHSA | GHSA-74fj-2j2h-c42q | Exposure of sensitive information in follow-redirects | follow-redirects is vulnerable to Exposure of Private Personal Information to an Unauthorized Actor | {'CVE-2022-0155'} | 2022-01-20T15:34:49Z | 2022-01-12T22:46:26Z | HIGH | 8 | {'CWE-359'} | {'https://github.com/follow-redirects/follow-redirects/commit/8b347cbcef7c7b72a6e9be20f5710c17d6163c22', 'https://github.com/advisories/GHSA-74fj-2j2h-c42q', 'https://huntr.dev/bounties/fc524e4b-ebb6-427d-ab67-a64181020406', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0155'} | null | {'https://github.com/follow-redirects/follow-redirects/commit/8b347cbcef7c7b72a6e9be20f5710c17d6163c22'} | {'https://github.com/follow-redirects/follow-redirects/commit/8b347cbcef7c7b72a6e9be20f5710c17d6163c22'} |
GHSA | GHSA-9p77-mmrw-69c7 | Null-dereference in Tensorflow | ### Impact
When decoding a tensor from protobuf, TensorFlow might do a null-dereference if attributes of some mutable arguments to some operations are missing from the proto. This is [guarded by a `DCHECK`](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/framework/full_type_util.cc#L104-L106):
```cc
const auto* attr = attrs.Find(arg->s());
DCHECK(attr != nullptr);
if (attr->value_case() == AttrValue::kList) {
// ...
}
```
However, `DCHECK` is a no-op in production builds and an assertion failure in debug builds. In the first case execution proceeds to the dereferencing of the null pointer, whereas in the second case it results in a crash due to the assertion failure.
### Patches
We have patched the issue in GitHub commit [8a513cec4bec15961fbfdedcaa5376522980455c](https://github.com/tensorflow/tensorflow/commit/8a513cec4bec15961fbfdedcaa5376522980455c).
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.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-23570'} | 2022-02-11T20:48:51Z | 2022-02-09T23:33:35Z | MODERATE | 6.5 | {'CWE-476'} | {'https://github.com/tensorflow/tensorflow/commit/8a513cec4bec15961fbfdedcaa5376522980455c', 'https://github.com/advisories/GHSA-9p77-mmrw-69c7', 'https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/framework/full_type_util.cc#L104-L106', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23570', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9p77-mmrw-69c7'} | null | {'https://github.com/tensorflow/tensorflow/commit/8a513cec4bec15961fbfdedcaa5376522980455c'} | {'https://github.com/tensorflow/tensorflow/commit/8a513cec4bec15961fbfdedcaa5376522980455c'} |
GHSA | GHSA-px9h-x66r-8mpc | path traversal in Jooby | ### Impact
Access to sensitive information available from classpath.
### Patches
Patched version: 1.6.7 and 2.8.2
Commit 1.x: https://github.com/jooby-project/jooby/commit/34f526028e6cd0652125baa33936ffb6a8a4a009
Commit 2.x: https://github.com/jooby-project/jooby/commit/c81479de67036993f406ccdec23990b44b0bec32
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
### References
Latest 1.x version: 1.6.6
#### Arbitrary class path resource access 1
When sharing a *File System* directory as in:
``` java
assets("/static/**", Paths.get("static"));
```
The class path is also searched for the file (`org.jooby.handlers.AssetHandler.loader`):
[jooby/AssetHandler.java at 1.x · jooby-project/jooby · GitHub](https://github.com/jooby-project/jooby/blob/1.x/jooby/src/main/java/org/jooby/handlers/AssetHandler.java)
``` java
private static Loader loader(final Path basedir, final ClassLoader classloader) {
if (Files.exists(basedir)) {
return name -> {
Path path = basedir.resolve(name).normalize();
if (Files.exists(path) && path.startsWith(basedir)) {
try {
return path.toUri().toURL();
} catch (MalformedURLException x) {
// shh
}
}
return classloader.getResource(name);
};
}
return classloader::getResource;
}
```
If we send `/static/WEB-INF/web.xml` it will fail to load it from the file system but will go into `classloader.getResource(name)` where name equals `/WEB-INF/web.xml` so will succeed and return the requested file. This way we can get any configuration file or even the application class files
If assets are configured for a certain extension we can still bypass it. eg:
```java
assets("/static/**/*.js", Paths.get("static"));
```
We can send:
```
http://localhost:8080/static/io/yiss/App.class.js
```
#### Arbitrary class path resource access 2
This vulnerability also affects assets configured to access resources from the root of the class path. eg:
```java
assets("/static/**");
```
In this case we can traverse `static` by sending:
```
http://localhost:8080/static/..%252fio/yiss/App.class
```
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [jooby](https://github.com/jooby-project/jooby/issues)
* Email us at [support@jooby.io](mailto:support@jooby.io) | {'CVE-2020-7647'} | 2021-08-25T21:08:33Z | 2020-05-13T16:29:26Z | MODERATE | 5.3 | {'CWE-22'} | {'https://snyk.io/vuln/SNYK-JAVA-IOJOOBY-568806', 'https://snyk.io/vuln/SNYK-JAVA-ORGJOOBY-568807,', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7647', 'https://github.com/jooby-project/jooby/security/advisories/GHSA-px9h-x66r-8mpc', 'https://github.com/advisories/GHSA-px9h-x66r-8mpc', 'https://github.com/jooby-project/jooby/commit/34f526028e6cd0652125baa33936ffb6a8a4a009', 'https://snyk.io/vuln/SNYK-JAVA-ORGJOOBY-568807', 'https://snyk.io/vuln/SNYK-JAVA-IOJOOBY-568806,'} | null | {'https://github.com/jooby-project/jooby/commit/34f526028e6cd0652125baa33936ffb6a8a4a009'} | {'https://github.com/jooby-project/jooby/commit/34f526028e6cd0652125baa33936ffb6a8a4a009'} |
GHSA | GHSA-67c7-5v9j-227r | Cross-site Scripting in kimai2 | kimai2 is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). | {'CVE-2021-3983'} | 2021-12-03T20:43:06Z | 2021-12-03T20:43:06Z | MODERATE | 6.3 | {'CWE-79'} | {'https://github.com/kevinpapst/kimai2/commit/89bfa82c61da0d3639e4038e689e25467baac8a0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3983', 'https://huntr.dev/bounties/c96f3480-dccf-4cc2-99a4-d2b3a7462413', 'https://github.com/advisories/GHSA-67c7-5v9j-227r', 'https://github.com/kevinpapst/kimai2/releases/tag/1.16.3'} | null | {'https://github.com/kevinpapst/kimai2/commit/89bfa82c61da0d3639e4038e689e25467baac8a0'} | {'https://github.com/kevinpapst/kimai2/commit/89bfa82c61da0d3639e4038e689e25467baac8a0'} |
GHSA | GHSA-43m5-c88r-cjvv | XSS due to lack of CSRF validation for replying/publishing | ### Impact
Due to lack of CSRF validation, a logged in user is potentially vulnerable to an XSS attack which could allow a third party to post on their behalf on the forum.
### Patches
Upgrade to the latest version v0.7.0
### Workarounds
You can cherry-pick the following commit: [https://github.com/psychobunny/nodebb-plugin-blog-comments/commit/cf43beedb05131937ef46f365ab0a0c6fa6ac618](https://github.com/psychobunny/nodebb-plugin-blog-comments/commit/cf43beedb05131937ef46f365ab0a0c6fa6ac618)
### References
Visit https://community.nodebb.org if you have any questions about this issue or on how to patch / upgrade your instance. | {'CVE-2020-15156'} | 2022-04-19T19:02:33Z | 2020-08-26T18:55:38Z | MODERATE | 6.8 | {'CWE-352'} | {'https://www.npmjs.com/package/nodebb-plugin-blog-comments', 'https://github.com/psychobunny/nodebb-plugin-blog-comments/security/advisories/GHSA-43m5-c88r-cjvv', 'https://github.com/psychobunny/nodebb-plugin-blog-comments/commit/cf43beedb05131937ef46f365ab0a0c6fa6ac618', 'https://github.com/advisories/GHSA-43m5-c88r-cjvv', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15156'} | null | {'https://github.com/psychobunny/nodebb-plugin-blog-comments/commit/cf43beedb05131937ef46f365ab0a0c6fa6ac618'} | {'https://github.com/psychobunny/nodebb-plugin-blog-comments/commit/cf43beedb05131937ef46f365ab0a0c6fa6ac618'} |
GHSA | GHSA-qcg2-h349-vwm3 | Cross-site Scripting in React Draft Wysiwyg | react-draft-wysiwyg (aka React Draft Wysiwyg) before 1.14.6 allows a javascript: URi in a Link Target of the link decorator in decorators/Link/index.js when a draft is shared across users, leading to XSS. | {'CVE-2021-31712'} | 2021-05-06T15:52:35Z | 2021-05-06T15:52:35Z | HIGH | 0 | {'CWE-79'} | {'https://github.com/jpuri/react-draft-wysiwyg/issues/1102', 'https://nvd.nist.gov/vuln/detail/CVE-2021-31712', 'https://github.com/advisories/GHSA-qcg2-h349-vwm3', 'https://github.com/jpuri/react-draft-wysiwyg/commit/d2faeb612b53f10dff048de7dc57e1f4044b5380', 'https://github.com/jpuri/react-draft-wysiwyg/pull/1104'} | null | {'https://github.com/jpuri/react-draft-wysiwyg/commit/d2faeb612b53f10dff048de7dc57e1f4044b5380'} | {'https://github.com/jpuri/react-draft-wysiwyg/commit/d2faeb612b53f10dff048de7dc57e1f4044b5380'} |
GHSA | GHSA-vx6j-pjrh-vgjh | PHP file inclusion in the Sulu admin panel | ### Impact
_What kind of vulnerability is it? Who is impacted?_
An attacker can read arbitrary local files via a PHP file include. In a default configuration this also leads to remote code execution.
* Compromised components: Arbitrary file read on the server, (Potential) Remote code execution
* Exploitation pre-requisite: User account on the backend
### Patches
_Has the problem been patched? What versions should users upgrade to?_
The problem is patched with the Versions 1.6.44, 2.2.18, 2.3.8, 2.4.0
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
Overwrite the service `sulu_route.generator.expression_token_provider` and wrap the translator before passing it to the expression language.
### References
_Are there any links users can visit to find out more?_
Currently not.
### 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-43836'} | 2021-12-16T14:08:49Z | 2021-12-15T22:54:20Z | HIGH | 8.5 | {'CWE-22'} | {'https://github.com/sulu/sulu/commit/9c948f9ce350c68b53af8c3910e2cefc7f722b54', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43836', 'https://github.com/advisories/GHSA-vx6j-pjrh-vgjh', 'https://github.com/sulu/sulu/security/advisories/GHSA-vx6j-pjrh-vgjh'} | null | {'https://github.com/sulu/sulu/commit/9c948f9ce350c68b53af8c3910e2cefc7f722b54'} | {'https://github.com/sulu/sulu/commit/9c948f9ce350c68b53af8c3910e2cefc7f722b54'} |
GHSA | GHSA-rqgp-ccph-5w65 | Cross-Site Request Forgery in firefly-iii | firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF). | {'CVE-2021-3901'} | 2021-11-02T18:42:31Z | 2021-10-28T23:14:14Z | LOW | 3.5 | {'CWE-352'} | {'https://github.com/firefly-iii/firefly-iii/commit/b42d8d1e305cad70d9b83b33cd8e0d7a4b2060c2', 'https://huntr.dev/bounties/62508fdc-c26b-4312-bf75-fd3a3f997464', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3901', 'https://github.com/advisories/GHSA-rqgp-ccph-5w65'} | null | {'https://github.com/firefly-iii/firefly-iii/commit/b42d8d1e305cad70d9b83b33cd8e0d7a4b2060c2'} | {'https://github.com/firefly-iii/firefly-iii/commit/b42d8d1e305cad70d9b83b33cd8e0d7a4b2060c2'} |
GHSA | GHSA-22wc-c9wj-6q2v | VVE-2021-0001: Memory corruption using function calls within arrays | ### Impact
When performing a function call inside an array, there is a memory corruption issue that occurs because of an incorrect pointer to the the tip of the stack.
### Patches
This issue was partially fixed in [VVE-2020-0004](https://github.com/vyperlang/vyper/security/advisories/GHSA-2r3x-4mrv-mcxf), however the fix did not update similar code for arrays, which had a similar issue. The issue is fully fixed in https://github.com/vyperlang/vyper/pull/2345 | null | 2021-04-19T15:12:05Z | 2021-04-19T15:12:05Z | MODERATE | 0 | {'CWE-129'} | {'https://github.com/vyperlang/vyper/security/advisories/GHSA-22wc-c9wj-6q2v', 'https://github.com/vyperlang/vyper/commit/11b7b5b7e59bc9dc859d51cd41a924b59fe47c9e', 'https://github.com/vyperlang/vyper/pull/2345', 'https://github.com/advisories/GHSA-22wc-c9wj-6q2v', 'https://pypi.org/project/vyper'} | null | {'https://github.com/vyperlang/vyper/commit/11b7b5b7e59bc9dc859d51cd41a924b59fe47c9e'} | {'https://github.com/vyperlang/vyper/commit/11b7b5b7e59bc9dc859d51cd41a924b59fe47c9e'} |
GHSA | GHSA-rf3m-mhv7-x39f | Denial of Service in OpenShift Origin | The API server in OpenShift Origin 1.0.5 allows remote attackers to cause a denial of service (master process crash) via crafted JSON data. | {'CVE-2015-5250'} | 2021-12-20T16:58:22Z | 2021-12-20T16:58:22Z | MODERATE | 4.3 | {'CWE-20'} | {'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-5250', 'https://nvd.nist.gov/vuln/detail/CVE-2015-5250', 'https://bugzilla.redhat.com/show_bug.cgi?id=1259867', 'https://access.redhat.com/errata/RHSA-2015:1736', 'https://github.com/openshift/origin/commit/dace5075e31b74703e944b6b3ebe8836be8d1b9a', 'https://github.com/advisories/GHSA-rf3m-mhv7-x39f', 'https://github.com/openshift/origin/issues/4374'} | null | {'https://github.com/openshift/origin/commit/dace5075e31b74703e944b6b3ebe8836be8d1b9a'} | {'https://github.com/openshift/origin/commit/dace5075e31b74703e944b6b3ebe8836be8d1b9a'} |
GHSA | GHSA-f2jv-r9rf-7988 | Remote code execution in handlebars when compiling templates | The package handlebars before 4.7.7 are vulnerable to Remote Code Execution (RCE) when selecting certain compiling options to compile templates coming from an untrusted source. | {'CVE-2021-23369'} | 2021-06-09T23:21:51Z | 2021-05-06T15:57:44Z | CRITICAL | 9.8 | {'CWE-94'} | {'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1074952', 'https://github.com/advisories/GHSA-f2jv-r9rf-7988', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-1074951', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23369', 'https://github.com/handlebars-lang/handlebars.js/commit/b6d3de7123eebba603e321f04afdbae608e8fea8', 'https://snyk.io/vuln/SNYK-JS-HANDLEBARS-1056767', 'https://github.com/handlebars-lang/handlebars.js/commit/f0589701698268578199be25285b2ebea1c1e427', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARS-1074950', 'https://security.netapp.com/advisory/ntap-20210604-0008/'} | null | {'https://github.com/handlebars-lang/handlebars.js/commit/b6d3de7123eebba603e321f04afdbae608e8fea8', 'https://github.com/handlebars-lang/handlebars.js/commit/f0589701698268578199be25285b2ebea1c1e427'} | {'https://github.com/handlebars-lang/handlebars.js/commit/b6d3de7123eebba603e321f04afdbae608e8fea8', 'https://github.com/handlebars-lang/handlebars.js/commit/f0589701698268578199be25285b2ebea1c1e427'} |
GHSA | GHSA-93pj-4p65-qmr9 | Insufficient user authorization 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. Insufficient capability checks could lead to users accessing their grade report for courses where they did not have the required gradereport/user:view capability. | {'CVE-2022-0334'} | 2022-02-02T16:13:31Z | 2022-01-28T22:07:40Z | MODERATE | 4.3 | {'CWE-668', 'CWE-863'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=2043664', 'https://github.com/moodle/moodle/commit/6d18f136ae88ec97e351a723df570816a959ec68', 'https://github.com/moodle/moodle/commit/1964d68f8500ea3c7b776fa8a2af6266ed109f84', 'https://github.com/advisories/GHSA-93pj-4p65-qmr9', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0334', 'https://moodle.org/mod/forum/discuss.php?d=431102'} | null | {'https://github.com/moodle/moodle/commit/1964d68f8500ea3c7b776fa8a2af6266ed109f84', 'https://github.com/moodle/moodle/commit/6d18f136ae88ec97e351a723df570816a959ec68'} | {'https://github.com/moodle/moodle/commit/6d18f136ae88ec97e351a723df570816a959ec68', 'https://github.com/moodle/moodle/commit/1964d68f8500ea3c7b776fa8a2af6266ed109f84'} |
GHSA | GHSA-627q-g293-49q7 | Abort caused by allocating a vector that is too large in Tensorflow | ### Impact
During shape inference, TensorFlow can [allocate a large vector](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/framework/shape_inference.cc#L788-L790) based on a value from a tensor controlled by the user:
```cc
const auto num_dims = Value(shape_dim);
std::vector<DimensionHandle> dims;
dims.reserve(num_dims);
```
### Patches
We have patched the issue in GitHub commit [1361fb7e29449629e1df94d44e0427ebec8c83c7](https://github.com/tensorflow/tensorflow/commit/1361fb7e29449629e1df94d44e0427ebec8c83c7).
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-23580'} | 2022-02-11T20:38:57Z | 2022-02-07T22:01:24Z | MODERATE | 6.5 | {'CWE-400'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-23580', 'https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/framework/shape_inference.cc#L788-L790', 'https://github.com/tensorflow/tensorflow/commit/1361fb7e29449629e1df94d44e0427ebec8c83c7', 'https://github.com/advisories/GHSA-627q-g293-49q7', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-627q-g293-49q7'} | null | {'https://github.com/tensorflow/tensorflow/commit/1361fb7e29449629e1df94d44e0427ebec8c83c7'} | {'https://github.com/tensorflow/tensorflow/commit/1361fb7e29449629e1df94d44e0427ebec8c83c7'} |
GHSA | GHSA-55mm-5399-7r63 | Reliance on Cookies without validation in OctoberCMS | ### Impact
Previously encrypted cookie values were not tied to the name of the cookie the value belonged to. This meant that certain classes of attacks that took advantage of other theoretical vulnerabilities in user facing code (nothing exploitable in the core project itself) had a higher chance of succeeding.
Specifically, if your usage exposed a way for users to provide unfiltered user input and have it returned to them as an encrypted cookie (ex. storing a user provided search query in a cookie) they could then use the generated cookie in place of other more tightly controlled cookies; or if your usage exposed the plaintext version of an encrypted cookie at any point to the user they could theoretically provide encrypted content from your application back to it as an encrypted cookie and force the framework to decrypt it for them.
### Patches
Issue has been patched in Build 468 (v1.0.468).
>**NOTE**: If you are using the cookie session driver, all of your session data will be invalidated. All other session drivers should smoothly upgrade to the changes (although the backend authentication persist cookie will also be invalidated requiring users to login again once their current session expires).
### Workarounds
Apply https://github.com/octobercms/library/commit/28310d4fb336a1741b39498f4474497644a6875c to your installation manually if unable to upgrade to Build 468.
### References
- https://blog.laravel.com/laravel-cookie-security-releases
- https://github.com/laravel/framework/compare/4c7d118181d6c7f1f883643702df807ced016c5e...a731824421f9ebc586728ea9c7cff231a249aaa9
### For more information
If you have any questions or comments about this advisory:
* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)
### Threat Assessment
Assessed as Low given that it is not directly exploitable within the core but requires other security vulnerabilities within the application to have an effect and the severity of its effect depends entirely on the severity of those other holes in the application's defences.
### Acknowledgements
Thanks to [Takashi Terada of Mitsui Bussan Secure Directions, Inc.](https://www.linkedin.com/in/takeshi-terada-b570a6100/) for finding the original issue in Laravel and @taylorotwell for sharing the report with the October CMS team. | {'CVE-2020-15128'} | 2022-04-26T18:12:52Z | 2020-08-05T14:52:54Z | MODERATE | 6.1 | {'CWE-565'} | {'https://github.com/advisories/GHSA-55mm-5399-7r63', 'https://github.com/octobercms/library/commit/28310d4fb336a1741b39498f4474497644a6875c', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15128', 'https://github.com/octobercms/library/pull/508', 'https://github.com/octobercms/october/security/advisories/GHSA-55mm-5399-7r63'} | null | {'https://github.com/octobercms/library/commit/28310d4fb336a1741b39498f4474497644a6875c'} | {'https://github.com/octobercms/library/commit/28310d4fb336a1741b39498f4474497644a6875c'} |
GHSA | GHSA-jfp7-4j67-8r3q | Heap buffer overflow caused by rounding | ### Impact
An attacker can trigger a heap buffer overflow in `tf.raw_ops.QuantizedResizeBilinear` by manipulating input values so that float rounding results in off-by-one error in accessing image elements:
```python
import tensorflow as tf
l = [256, 328, 361, 17, 361, 361, 361, 361, 361, 361, 361, 361, 361, 361, 384]
images = tf.constant(l, shape=[1, 1, 15, 1], dtype=tf.qint32)
size = tf.constant([12, 6], shape=[2], dtype=tf.int32)
min = tf.constant(80.22522735595703)
max = tf.constant(80.39215850830078)
tf.raw_ops.QuantizedResizeBilinear(images=images, size=size, min=min, max=max,
align_corners=True, half_pixel_centers=True)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/44b7f486c0143f68b56c34e2d01e146ee445134a/tensorflow/core/kernels/quantized_resize_bilinear_op.cc#L62-L66) computes two integers (representing the upper and lower bounds for interpolation) by ceiling and flooring a floating point value:
```cc
const float in_f = std::floor(in);
interpolation->lower[i] = std::max(static_cast<int64>(in_f), static_cast<int64>(0));
interpolation->upper[i] = std::min(static_cast<int64>(std::ceil(in)), in_size - 1);
```
For some values of `in`, `interpolation->upper[i]` might be smaller than `interpolation->lower[i]`. This is an issue if `interpolation->upper[i]` is capped at `in_size-1` as it means that `interpolation->lower[i]` points outside of the image. Then, [in the interpolation code](https://github.com/tensorflow/tensorflow/blob/44b7f486c0143f68b56c34e2d01e146ee445134a/tensorflow/core/kernels/quantized_resize_bilinear_op.cc#L245-L264), this would result in heap buffer overflow:
```cc
template <int RESOLUTION, typename T, typename T_SCALE, typename T_CALC>
inline void OutputLerpForChannels(const InterpolationCache<T_SCALE>& xs,
const int64 x, const T_SCALE ys_ilerp,
const int channels, const float min,
const float max, const T* ys_input_lower_ptr,
const T* ys_input_upper_ptr,
T* output_y_ptr) {
const int64 xs_lower = xs.lower[x];
...
for (int c = 0; c < channels; ++c) {
const T top_left = ys_input_lower_ptr[xs_lower + c];
...
}
}
```
For the other cases where `interpolation->upper[i]` is smaller than `interpolation->lower[i]`, we can set them to be equal without affecting the output.
### Patches
We have patched the issue in GitHub commit [f851613f8f0fb0c838d160ced13c134f778e3ce7](https://github.com/tensorflow/tensorflow/commit/f851613f8f0fb0c838d160ced13c134f778e3ce7).
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-29529'} | 2021-05-21T17:06:51Z | 2021-05-21T14:22:05Z | LOW | 2.5 | {'CWE-131', 'CWE-193'} | {'https://github.com/tensorflow/tensorflow/commit/f851613f8f0fb0c838d160ced13c134f778e3ce7', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-jfp7-4j67-8r3q', 'https://github.com/advisories/GHSA-jfp7-4j67-8r3q', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29529'} | null | {'https://github.com/tensorflow/tensorflow/commit/f851613f8f0fb0c838d160ced13c134f778e3ce7'} | {'https://github.com/tensorflow/tensorflow/commit/f851613f8f0fb0c838d160ced13c134f778e3ce7'} |
GHSA | GHSA-mc22-5q92-8v85 | Memory Safety Issue when using patch or merge on state and assign the result back to state |
### Impact
This vulnerability is a memory safety Issue when using [`patch`](https://www.tremor.rs/docs/tremor-script/index#patch) or [`merge`](https://www.tremor.rs/docs/tremor-script/index#merge) on `state` and assign the result back to `state`.
In this case affected versions of Tremor and the [tremor-script crate](https://crates.io/crates/tremor-script) maintains references to memory that might have been freed already. And these memory regions can be accessed by retrieving the `state`, e.g. send it over TCP or HTTP. This requires the Tremor server (or any other program using tremor-script) to execute a tremor-script script that uses the mentioned language construct.
#### Details
If affects the following two tremor-script language constructs:
* A [Merge](https://www.tremor.rs/docs/tremor-script/index#merge) where we assign the result back to the target expression
and the expression to be merged needs to reference the `event`:
```
let state = merge state of event end;
```
* A [Patch](https://www.tremor.rs/docs/tremor-script/index#patch) where we assign the result back to the target expression
and the patch operations used need to reference the `event`:
```
let state = patch state of insert event.key => event.value end;
```
For constructs like this (it does not matter what it references in the expression to be merged or the patch operations) an optimization
was applied to manipulate the target value in-place, instead of cloning it.
Our `Value` struct, which underpins all event data in `tremor-script`, is representing strings as borrowed `beef::Cow<'lifetime, str>`,
that reference the raw data `Vec<u8>` the event is based upon. We keep this raw byte-array next to the `Value` structure inside our `Event` as a self-referential struct,
so we make sure that the structured `Value` and its references are valid across its whole lifetime.
The optimization was considered safe as long as it was only possible to merge or patch `event` data or static data.
When `state` was introduced to `tremor-script` (in version 0.7.3) a new possibility to keep `Value` data around for longer than the lifetime of an event emerged.
If `event` data is merged or patched into `state` without cloning it first, it can still reference keys or values from
the previous event, which will now be invalid. This allows access to those already freed regions of memory and to get their content out over the wire.
### Patches
The issue has been patched in https://crates.io/crates/tremor-script/0.11.6 and https://github.com/tremor-rs/tremor-runtime/releases/tag/v0.11.6 via commit [1a2efcd](https://github.com/tremor-rs/tremor-runtime/commit/1a2efcdbe68e5e7fd0a05836ac32d2cde78a0b2e) by removing the optimization
and always clone the target expression of a [Merge](https://www.tremor.rs/docs/tremor-script/index#merge) or [Patch](https://www.tremor.rs/docs/tremor-script/index#patch.
### Workarounds
If an upgrade is not possible, a possible workaround is to avoid the optimization
by introducing a temporary variable and not immediately reassigning to `state`:
```
let tmp = merge state of event end;
let state = tmp
```
### References
The actual fix is applied in this PR: https://github.com/tremor-rs/tremor-runtime/pull/1217
### For more information
If you have any questions or comments about this advisory:
* Open an issue on our repository [tremor-rs/tremor-runtime](https://github.com/tremor-rs/tremor-runtime)
* Please join our discord https://chat.tremor.rs and reach out to the team.
| {'CVE-2021-39228'} | 2021-09-20T19:52:53Z | 2021-09-20T19:52:53Z | MODERATE | 6.5 | {'CWE-416', 'CWE-825'} | {'https://github.com/tremor-rs/tremor-runtime/pull/1217', 'https://github.com/tremor-rs/tremor-runtime/security/advisories/GHSA-mc22-5q92-8v85', 'https://github.com/advisories/GHSA-mc22-5q92-8v85', 'https://github.com/tremor-rs/tremor-runtime/releases/tag/v0.11.6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39228', 'https://github.com/tremor-rs/tremor-runtime/commit/1a2efcdbe68e5e7fd0a05836ac32d2cde78a0b2e'} | null | {'https://github.com/tremor-rs/tremor-runtime/commit/1a2efcdbe68e5e7fd0a05836ac32d2cde78a0b2e'} | {'https://github.com/tremor-rs/tremor-runtime/commit/1a2efcdbe68e5e7fd0a05836ac32d2cde78a0b2e'} |
GHSA | GHSA-4852-vrh7-28rf | Reflected XSS in GraphQL Playground | ### Impact
**directly impacted:**
- `graphql-playground-html@<1.6.22` - all unsanitized user input for `renderPlaygroundPage()`
**all of our consuming packages** of `graphql-playground-html` are impacted:
- `graphql-playground-middleware-express@<1.7.16` - unsanitized user input to `expressPlayground()`
- `graphql-playground-middleware-koa@<1.6.15` - unsanitized user input to `koaPlayground()`
- `graphql-playground-middleware-lambda@<1.7.17` - unsanitized user input to `lambdaPlayground()`
- `graphql-playground-middleware-hapi@<1.6.13` - unsanitized user input to `hapiPlayground()`
as well as ***any other packages*** that use these methods with unsanitized user input.
**not impacted:**
- `graphql-playground-electron` - uses `renderPlaygroundPage()` statically for a webpack build for electron bundle, no dynamic user input
- `graphql-playground-react` - usage of the component directly in a react application does not expose reflected XSS vulnerabilities. only the demo in `public/` contains the vulnerability, because it uses an old version of the html pacakge.
### Patches
upgrading to the above mentioned versions will solve the issue.
If you're using `graphql-playground-html` directly, then:
```
yarn add graphql-playground-html@^1.6.22
```
or
```
npm install --save graphql-playground-html@^1.6.22
```
Then, similar steps need to be taken for each middleware:
- [Upgrade Express Middleware](https://www.npmjs.com/package/graphql-playground-middleware-express#security-upgrade-steps)
- [Upgrade Koa Middleware](https://www.npmjs.com/package/graphql-playground-middleware-koa#security-upgrade-steps)
- [Upgrade Lambda Middleware](https://www.npmjs.com/package/graphql-playground-middleware-lambda#security-upgrade-steps)
- [Upgrade Hapi Middleware](https://www.npmjs.com/package/graphql-playground-middleware-hapi#security-upgrade-steps)
### Workarounds
Ensure you properly sanitize *all* user input for options you use for whatever function to initialize GraphQLPlayground:
for example, with `graphql-playground-html` and express:
```js
const { sanitizeUrl } = require('@braintree/sanitize-url');
const qs = require('querystringify');
const { renderPlaygroundPage } = require('graphql-playground-html');
module.exports = (req, res, next) => {
const { endpoint } = qs.parse(req.url)
res.html(renderPlaygroundPage({endpoint: sanitizeUrl(endpoint) })).status(200)
next()
}
```
or, with `graphql-playground-express`:
```js
const { expressPlayground } = require('graphql-playground-middleware-express');
const { sanitizeUrl } = require('@braintree/sanitize-url');
const qs = require('querystringify');
const { renderPlaygroundPage } = require('graphql-playground-html');
module.exports = (req, res, next) => {
const { endpoint } = qs.parse(req.url)
res.html(expressPlayground({endpoint: sanitizeUrl(endpoint) })).status(200)
next()
}
```
### References
- [OWASP: How to Test for CSS Reflection Attacks](https://github.com/OWASP/wstg/blob/master/document/4-Web_Application_Security_Testing/07-Input_Validation_Testing/01-Testing_for_Reflected_Cross_Site_Scripting.md)
- [Original Report from Cure53](https://user-images.githubusercontent.com/1368727/84191028-dfb7b980-aa65-11ea-8e18-4b8706f538e2.jpg) (jpg)
### Credits
Masato Kinugawa of Cure53
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [graphql-playground](https://github.com/prisma-labs/graphql-playground/issues/new/choose)
* Email us at [rikki.schulte@gmail.com](mailto:rikki.schulte@gmail.com)
| {'CVE-2020-4038'} | 2021-11-04T17:11:47Z | 2020-06-09T00:24:57Z | HIGH | 7.4 | {'CWE-79'} | {'https://github.com/advisories/GHSA-4852-vrh7-28rf', 'https://nvd.nist.gov/vuln/detail/CVE-2020-4038', 'https://github.com/prisma-labs/graphql-playground/commit/bf1883db538c97b076801a60677733816cb3cfb7', 'https://github.com/prisma-labs/graphql-playground#security-details', 'https://github.com/prisma-labs/graphql-playground/security/advisories/GHSA-4852-vrh7-28rf', 'https://github.com/graphql/graphql-playground/security/advisories/GHSA-4852-vrh7-28rf'} | null | {'https://github.com/prisma-labs/graphql-playground/commit/bf1883db538c97b076801a60677733816cb3cfb7'} | {'https://github.com/prisma-labs/graphql-playground/commit/bf1883db538c97b076801a60677733816cb3cfb7'} |
GHSA | GHSA-6x98-fx9j-7c78 | Disabled users able to log in with third party SSO plugin | ### Impact
Mautic versions 2.0.0 - 2.11.0 with a SSO plugin installed could allow a disabled user to still login using email address
### Patches
Upgrade to 2.12.0 or later.
### Workarounds
None.
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@mautic.org](mailto:security@mautic.org) | {'CVE-2017-1000489'} | 2022-04-19T19:02:45Z | 2021-01-19T21:16:19Z | MODERATE | 8.1 | {'CWE-287'} | {'https://github.com/mautic/mautic/commit/fd933cbef795b04cabdc50527cb18e037488fef9', 'https://github.com/mautic/mautic/releases/tag/2.12.0', 'https://github.com/advisories/GHSA-6x98-fx9j-7c78', 'https://nvd.nist.gov/vuln/detail/CVE-2017-1000489', 'https://github.com/mautic/mautic/security/advisories/GHSA-6x98-fx9j-7c78'} | null | {'https://github.com/mautic/mautic/commit/fd933cbef795b04cabdc50527cb18e037488fef9'} | {'https://github.com/mautic/mautic/commit/fd933cbef795b04cabdc50527cb18e037488fef9'} |
GHSA | GHSA-cqhg-xjhh-p8hf | Out-of-bounds reads in Pillow | Pillow before 6.2.3 and 7.x before 7.0.1 has multiple out-of-bounds reads in libImaging/FliDecode.c. | {'CVE-2020-10177'} | 2021-09-22T21:50:28Z | 2020-07-27T21:52:43Z | MODERATE | 5.5 | {'CWE-125'} | {'https://github.com/python-pillow/Pillow/commits/master/src/libImaging', 'https://lists.debian.org/debian-lts-announce/2020/08/msg00012.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-10177', 'https://github.com/python-pillow/Pillow/pull/4503', 'https://pillow.readthedocs.io/en/stable/releasenotes/6.2.3.html', 'https://snyk.io/vuln/SNYK-PYTHON-PILLOW-574573', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HOKHNWV2VS5GESY7IBD237E7C6T3I427/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BEBCPE4F2VHTIT6EZA2YZQZLPVDEBJGD/', 'https://usn.ubuntu.com/4430-2/', 'https://github.com/advisories/GHSA-cqhg-xjhh-p8hf', 'https://pillow.readthedocs.io/en/stable/releasenotes/7.1.0.html', 'https://usn.ubuntu.com/4430-1/', 'https://github.com/python-pillow/Pillow/pull/4538'} | null | {'https://github.com/python-pillow/Pillow/commits/master/src/libImaging'} | {'https://github.com/python-pillow/Pillow/commits/master/src/libImaging'} |
GHSA | GHSA-wg8p-w946-c482 | Cross-site Scripting in ShowDoc | ShowDoc prior to 2.10.4 is vulnerable to stored cross-site scripting via file upload. | {'CVE-2022-0956'} | 2022-03-29T21:23:18Z | 2022-03-16T00:00:47Z | MODERATE | 5.4 | {'CWE-79'} | {'https://huntr.dev/bounties/5b0e3f02-309f-4b59-8020-d7ac0f1999f2', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0956', 'https://github.com/star7th/showdoc/commit/56e450c3adf75c707500d7231a78c9fc894c7f13', 'https://github.com/advisories/GHSA-wg8p-w946-c482'} | null | {'https://github.com/star7th/showdoc/commit/56e450c3adf75c707500d7231a78c9fc894c7f13'} | {'https://github.com/star7th/showdoc/commit/56e450c3adf75c707500d7231a78c9fc894c7f13'} |
GHSA | GHSA-79fv-9865-4qcv | Heap buffer overflow in `MaxPoolGrad` | ### Impact
The implementation of `tf.raw_ops.MaxPoolGrad` is vulnerable to a heap buffer overflow:
```python
import tensorflow as tf
orig_input = tf.constant([0.0], shape=[1, 1, 1, 1], dtype=tf.float32)
orig_output = tf.constant([0.0], shape=[1, 1, 1, 1], dtype=tf.float32)
grad = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32)
ksize = [1, 1, 1, 1]
strides = [1, 1, 1, 1]
padding = "SAME"
tf.raw_ops.MaxPoolGrad(
orig_input=orig_input, orig_output=orig_output, grad=grad, ksize=ksize,
strides=strides, padding=padding, explicit_paddings=[])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/ab1e644b48c82cb71493f4362b4dd38f4577a1cf/tensorflow/core/kernels/maxpooling_op.cc#L194-L203) fails to validate that indices used to access elements of input/output arrays are valid:
```cc
for (int index = out_start; index < out_end; ++index) {
int input_backprop_index = out_arg_max_flat(index);
FastBoundsCheck(input_backprop_index - in_start, in_end - in_start);
input_backprop_flat(input_backprop_index) += out_backprop_flat(index);
}
```
Whereas accesses to `input_backprop_flat` are guarded by `FastBoundsCheck`, the indexing in `out_backprop_flat` can result in OOB access.
### Patches
We have patched the issue in GitHub commit [a74768f8e4efbda4def9f16ee7e13cf3922ac5f7](https://github.com/tensorflow/tensorflow/commit/a74768f8e4efbda4def9f16ee7e13cf3922ac5f7).
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-29579'} | 2021-05-21T17:08:37Z | 2021-05-21T14:26:23Z | LOW | 2.5 | {'CWE-119', 'CWE-787'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29579', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-79fv-9865-4qcv', 'https://github.com/tensorflow/tensorflow/commit/a74768f8e4efbda4def9f16ee7e13cf3922ac5f7', 'https://github.com/advisories/GHSA-79fv-9865-4qcv'} | null | {'https://github.com/tensorflow/tensorflow/commit/a74768f8e4efbda4def9f16ee7e13cf3922ac5f7'} | {'https://github.com/tensorflow/tensorflow/commit/a74768f8e4efbda4def9f16ee7e13cf3922ac5f7'} |
GHSA | GHSA-jp55-vvmf-63mv | URL Redirection to Untrusted Site ('Open Redirect') | ### Impact
There's no protection against URL redirection to untrusted site, in particular some well known parameters (xredirect) can be used to perform such redirections.
### Patches
The problem has been patched in XWiki 12.10.7 and XWiki 13.3RC1.
### Workarounds
There's no known workaround for this issue.
### References
https://jira.xwiki.org/browse/XWIKI-10309
### 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 [Security ML](mailto:security@xwiki.org)
| {'CVE-2022-23618'} | 2022-02-11T15:00:57Z | 2022-02-09T21:42:47Z | MODERATE | 4.7 | {'CWE-601'} | {'https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-jp55-vvmf-63mv', 'https://github.com/xwiki/xwiki-platform/commit/5251c02080466bf9fb55288f04a37671108f8096', 'https://github.com/advisories/GHSA-jp55-vvmf-63mv', 'https://jira.xwiki.org/browse/XWIKI-10309', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23618'} | null | {'https://github.com/xwiki/xwiki-platform/commit/5251c02080466bf9fb55288f04a37671108f8096'} | {'https://github.com/xwiki/xwiki-platform/commit/5251c02080466bf9fb55288f04a37671108f8096'} |
GHSA | GHSA-425c-ccf3-3jrr | Critical severity vulnerability that affects slpjs | ## Validator parsing discrepancy due to string encoding
### Impact
A specially crafted Bitcoin script can cause a discrepancy between the specified SLP consensus rules and the validation result of the slpjs npm package. An attacker could create a specially crafted Bitcoin script in order to cause a hard-fork from the SLP consensus.
### Patches
All versions > 0.21.3 are patched.
### Workarounds
Upgrade to any version >= 0.21.4.
### References
The bug was located and fixed [here](https://github.com/simpleledger/slpjs/commit/ac8809b42e47790a6f0205991b36f2699ed10c84#diff-fe58606994c412ba56a65141a7aa4a62L701).
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [slpjs repo](https://github.com/simpleledger/slpjs/issues)
* Email us at [info@slp.cash](mailto:info@slp.cash) | {'CVE-2019-16762'} | 2021-01-08T19:58:00Z | 2019-11-15T23:10:35Z | CRITICAL | 5.7 | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-16762', 'https://github.com/simpleledger/slpjs/security/advisories/GHSA-425c-ccf3-3jrr', 'https://github.com/simpleledger/slpjs/commit/ac8809b42e47790a6f0205991b36f2699ed10c84#diff-fe58606994c412ba56a65141a7aa4a62L701', 'https://github.com/advisories/GHSA-425c-ccf3-3jrr'} | null | {'https://github.com/simpleledger/slpjs/commit/ac8809b42e47790a6f0205991b36f2699ed10c84#diff-fe58606994c412ba56a65141a7aa4a62L701'} | {'https://github.com/simpleledger/slpjs/commit/ac8809b42e47790a6f0205991b36f2699ed10c84#diff-fe58606994c412ba56a65141a7aa4a62L701'} |
GHSA | GHSA-pfv6-prqm-85q8 | Prototype Pollution in madlib-object-utils | The package madlib-object-utils before version 0.1.8 is vulnerable to Prototype Pollution via the `setValue` method, as it allows an attacker to merge object prototypes into it. *Note:* This vulnerability derives from an incomplete fix of [CVE-2020-7701](https://security.snyk.io/vuln/SNYK-JS-MADLIBOBJECTUTILS-598676) | {'CVE-2022-24279'} | 2022-04-22T20:50:34Z | 2022-04-16T00:00:26Z | HIGH | 7.5 | {'CWE-1321'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-24279', 'https://github.com/advisories/GHSA-pfv6-prqm-85q8', 'https://snyk.io/vuln/SNYK-JS-MADLIBOBJECTUTILS-2388572', 'https://github.com/Qwerios/madlib-object-utils/commit/8d5d54c11c8fb9a7980a99778329acd13e3ef98f'} | null | {'https://github.com/Qwerios/madlib-object-utils/commit/8d5d54c11c8fb9a7980a99778329acd13e3ef98f'} | {'https://github.com/Qwerios/madlib-object-utils/commit/8d5d54c11c8fb9a7980a99778329acd13e3ef98f'} |
GHSA | GHSA-mc6h-4qgp-37qh | Deserialization of untrusted data in Jackson Databind | FasterXML jackson-databind 2.x before 2.9.10.5 mishandles the interaction between serialization gadgets and typing, related to org.jsecurity.realm.jndi.JndiRealmFactory (aka org.jsecurity). | {'CVE-2020-14195'} | 2021-10-21T21:05:46Z | 2020-06-18T14:44:43Z | HIGH | 8.1 | {'CWE-502'} | {'https://github.com/advisories/GHSA-mc6h-4qgp-37qh', 'https://github.com/FasterXML/jackson-databind/issues/2765', 'https://nvd.nist.gov/vuln/detail/CVE-2020-14195', 'https://lists.debian.org/debian-lts-announce/2020/07/msg00001.html', 'https://security.netapp.com/advisory/ntap-20200702-0003/', 'https://github.com/FasterXML/jackson-databind/commit/f6d9c664f6d481703138319f6a0f1fdbddb3a259', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://www.oracle.com/security-alerts/cpujan2021.html', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/FasterXML/jackson-databind/commit/f6d9c664f6d481703138319f6a0f1fdbddb3a259'} | {'https://github.com/FasterXML/jackson-databind/commit/f6d9c664f6d481703138319f6a0f1fdbddb3a259'} |
GHSA | GHSA-p4q6-qxjx-8jgp | Directory Traversal in spring-boot-actuator-logview | ### Impact
The nature of this library is to expose a log file directory via admin (spring boot actuator) HTTP endpoints. Both the filename to view and a base folder (relative to the logging folder root) can be specified via request parameters. While the filename parameter was checked to prevent directory traversal exploits (so that `filename=../somefile` would not work), the base folder parameter was not sufficiently checked, so that `filename=somefile&base=../` could access a file outside the logging base directory).
### Patches
The vulnerability has been patched in release 0.2.13. Any users of 0.2.12 should be able to update without any issues as there are no other changes in that release.
### Workarounds
There is no workaround to fix the vulnerability other than updating or removing the dependency. However, removing read access of the user the application is run with to any directory not required for running the application can limit the impact. Additionally, access to the logview endpoint can be limited by deploying the application behind a reverse proxy.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [github repo](https://github.com/lukashinsch/spring-boot-actuator-logview) | {'CVE-2021-21234'} | 2022-04-19T19:02:44Z | 2021-01-05T17:29:40Z | HIGH | 7.7 | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-21234', 'https://github.com/lukashinsch/spring-boot-actuator-logview/commit/1c76e1ec3588c9f39e1a94bf27b5ff56eb8b17d6', 'https://github.com/lukashinsch/spring-boot-actuator-logview/commit/760acbb939a8d1f7d1a7dfcd51ca848eea04e772', 'https://github.com/advisories/GHSA-p4q6-qxjx-8jgp', 'https://github.com/lukashinsch/spring-boot-actuator-logview/security/advisories/GHSA-p4q6-qxjx-8jgp', 'https://search.maven.org/artifact/eu.hinsch/spring-boot-actuator-logview'} | null | {'https://github.com/lukashinsch/spring-boot-actuator-logview/commit/760acbb939a8d1f7d1a7dfcd51ca848eea04e772', 'https://github.com/lukashinsch/spring-boot-actuator-logview/commit/1c76e1ec3588c9f39e1a94bf27b5ff56eb8b17d6'} | {'https://github.com/lukashinsch/spring-boot-actuator-logview/commit/1c76e1ec3588c9f39e1a94bf27b5ff56eb8b17d6', 'https://github.com/lukashinsch/spring-boot-actuator-logview/commit/760acbb939a8d1f7d1a7dfcd51ca848eea04e772'} |
GHSA | GHSA-2vj5-px25-gjrp | pytorch-lightning is vulnerable to Deserialization of Untrusted Data | pytorch-lightning is vulnerable to Deserialization of Untrusted Data. | {'CVE-2021-4118'} | 2022-03-30T18:25:55Z | 2022-01-06T23:58:59Z | HIGH | 7.8 | {'CWE-502'} | {'https://github.com/advisories/GHSA-2vj5-px25-gjrp', 'https://github.com/pytorchlightning/pytorch-lightning/commit/62f1e82e032eb16565e676d39e0db0cac7e34ace', 'https://github.com/PyTorchLightning/pytorch-lightning/releases/tag/1.6.0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4118', 'https://huntr.dev/bounties/31832f0c-e5bb-4552-a12c-542f81f111e6', 'https://github.com/PyTorchLightning/pytorch-lightning/pull/11099', 'https://github.com/PyTorchLightning/pytorch-lightning/issues/11045'} | null | {'https://github.com/pytorchlightning/pytorch-lightning/commit/62f1e82e032eb16565e676d39e0db0cac7e34ace'} | {'https://github.com/pytorchlightning/pytorch-lightning/commit/62f1e82e032eb16565e676d39e0db0cac7e34ace'} |
GHSA | GHSA-hj8g-cw8x-2c6m | Cross-site Scripting in Microweber | Microweber prior to version 1.3 is vulnerable to reflected cross-site scripting. | {'CVE-2022-0719'} | 2022-02-26T01:18:28Z | 2022-02-24T00:00:53Z | HIGH | 7.6 | {'CWE-79'} | {'https://github.com/microweber/microweber/commit/a5925f74d39775771d4c37c8d4c1acbb762fda0a', 'https://github.com/advisories/GHSA-hj8g-cw8x-2c6m', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0719', 'https://huntr.dev/bounties/bcdce15b-7f40-4971-a061-c25c6053c312'} | null | {'https://github.com/microweber/microweber/commit/a5925f74d39775771d4c37c8d4c1acbb762fda0a'} | {'https://github.com/microweber/microweber/commit/a5925f74d39775771d4c37c8d4c1acbb762fda0a'} |
GHSA | GHSA-q3wr-qw3g-3p4h | Injection/XSS in Redcarpet | Redcarpet is a Ruby library for Markdown processing. In Redcarpet before version 3.5.1, there is an injection vulnerability which can enable a cross-site scripting attack. In affected versions no HTML escaping was being performed when processing quotes. This applies even when the `:escape_html` option was being used. This is fixed in version 3.5.1 by the referenced commit. | {'CVE-2020-26298'} | 2021-01-19T18:16:40Z | 2021-01-11T19:06:10Z | MODERATE | 6.8 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-26298', 'https://rubygems.org/gems/redcarpet', 'https://lists.debian.org/debian-lts-announce/2021/01/msg00014.html', 'https://github.com/advisories/GHSA-q3wr-qw3g-3p4h', 'https://github.com/vmg/redcarpet/blob/master/CHANGELOG.md#version-351-security', 'https://github.com/vmg/redcarpet/commit/a699c82292b17c8e6a62e1914d5eccc252272793', 'https://www.debian.org/security/2021/dsa-4831'} | null | {'https://github.com/vmg/redcarpet/commit/a699c82292b17c8e6a62e1914d5eccc252272793'} | {'https://github.com/vmg/redcarpet/commit/a699c82292b17c8e6a62e1914d5eccc252272793'} |
GHSA | GHSA-hq37-853p-g5cf | Regular Expression Denial of Service in CairoSVG | # Doyensec Vulnerability Advisory
* Regular Expression Denial of Service (REDoS) in cairosvg
* Affected Product: CairoSVG v2.0.0+
* Vendor: https://github.com/Kozea
* Severity: Medium
* Vulnerability Class: Denial of Service
* Author(s): Ben Caller ([Doyensec](https://doyensec.com))
## Summary
When processing SVG files, the python package CairoSVG uses two regular expressions which are vulnerable to Regular Expression Denial of Service (REDoS).
If an attacker provides a malicious SVG, it can make cairosvg get stuck processing the file for a very long time.
## Technical description
The vulnerable regular expressions are
https://github.com/Kozea/CairoSVG/blob/9c4a982b9a021280ad90e89707eacc1d114e4ac4/cairosvg/colors.py#L190-L191
The section between 'rgb(' and the final ')' contains multiple overlapping groups.
Since all three infinitely repeating groups accept spaces, a long string of spaces causes catastrophic backtracking when it is not followed by a closing parenthesis.
The complexity is cubic, so doubling the length of the malicious string of spaces makes processing take 8 times as long.
## Reproduction steps
Create a malicious SVG of the form:
<svg width="1" height="1"><rect fill="rgb( ;"/></svg>
with the following code:
'<svg width="1" height="1"><rect fill="rgb(' + (' ' * 3456) + ';"/></svg>'
Note that there is no closing parenthesis before the semi-colon.
Run cairosvg e.g.:
cairosvg cairo-redos.svg -o x.png
and notice that it hangs at 100% CPU. Increasing the number of spaces increases the processing time with cubic complexity.
## Remediation
Fix the regexes to avoid overlapping parts. Perhaps remove the [ \n\r\t]* groups from the regex, and use .strip() on the returned capture group.
## Disclosure timeline
- 2020-12-30: Vulnerability disclosed via email to CourtBouillon | {'CVE-2021-21236'} | 2022-04-19T19:02:44Z | 2021-01-06T16:57:50Z | MODERATE | 0 | {'CWE-400'} | {'https://github.com/Kozea/CairoSVG/commit/cfc9175e590531d90384aa88845052de53d94bf3', 'https://pypi.org/project/CairoSVG/', 'https://github.com/advisories/GHSA-hq37-853p-g5cf', 'https://github.com/Kozea/CairoSVG/releases/tag/2.5.1', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21236', 'https://github.com/Kozea/CairoSVG/security/advisories/GHSA-hq37-853p-g5cf'} | null | {'https://github.com/Kozea/CairoSVG/commit/cfc9175e590531d90384aa88845052de53d94bf3'} | {'https://github.com/Kozea/CairoSVG/commit/cfc9175e590531d90384aa88845052de53d94bf3'} |
GHSA | GHSA-3ff2-r28g-w7h9 | Heap buffer overflow in `Transpose` | ### Impact
The [shape inference function for `Transpose`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/array_ops.cc#L121-L185) is vulnerable to a heap buffer overflow:
```python
import tensorflow as tf
@tf.function
def test():
y = tf.raw_ops.Transpose(x=[1,2,3,4],perm=[-10])
return y
test()
```
This occurs whenever `perm` contains negative elements. The shape inference function does not validate that the indices in `perm` are all valid:
```cc
for (int32_t i = 0; i < rank; ++i) {
int64_t in_idx = data[i];
if (in_idx >= rank) {
return errors::InvalidArgument("perm dim ", in_idx,
" is out of range of input rank ", rank);
}
dims[i] = c->Dim(input, in_idx);
}
```
where `Dim(tensor, index)` accepts either a positive index less than the rank of the tensor or the special value `-1` for unknown dimensions.
### Patches
We have patched the issue in GitHub commit [c79ba87153ee343401dbe9d1954d7f79e521eb14](https://github.com/tensorflow/tensorflow/commit/c79ba87153ee343401dbe9d1954d7f79e521eb14).
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-41216'} | 2021-11-10T18:57:19Z | 2021-11-10T18:57:19Z | MODERATE | 5.5 | {'CWE-787', 'CWE-120'} | {'https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/array_ops.cc#L121-L185', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41216', 'https://github.com/tensorflow/tensorflow/commit/c79ba87153ee343401dbe9d1954d7f79e521eb14', 'https://github.com/advisories/GHSA-3ff2-r28g-w7h9', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-3ff2-r28g-w7h9'} | null | {'https://github.com/tensorflow/tensorflow/commit/c79ba87153ee343401dbe9d1954d7f79e521eb14'} | {'https://github.com/tensorflow/tensorflow/commit/c79ba87153ee343401dbe9d1954d7f79e521eb14'} |
GHSA | GHSA-gxr4-xjj5-5px2 | Potential XSS vulnerability in jQuery | ### Impact
Passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. `.html()`, `.append()`, and others) may execute untrusted code.
### Patches
This problem is patched in jQuery 3.5.0.
### Workarounds
To workaround the issue without upgrading, adding the following to your code:
```js
jQuery.htmlPrefilter = function( html ) {
return html;
};
```
You need to use at least jQuery 1.12/2.2 or newer to be able to apply this workaround.
### References
https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/
https://jquery.com/upgrade-guide/3.5/
### For more information
If you have any questions or comments about this advisory, search for a relevant issue in [the jQuery repo](https://github.com/jquery/jquery/issues). If you don't find an answer, open a new issue. | {'CVE-2020-11022'} | 2022-04-25T23:06:54Z | 2020-04-29T22:18:55Z | MODERATE | 6.9 | {'CWE-79'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QPN2L2XVQGUA2V5HNQJWHK3APSK3VN7K/', 'https://github.com/advisories/GHSA-gxr4-xjj5-5px2', 'https://www.tenable.com/security/tns-2020-11', 'https://lists.debian.org/debian-lts-announce/2021/03/msg00033.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AVKYXLWCLZBV2N7M46KYK4LVA5OXWPBY/', 'https://lists.apache.org/thread.html/rede9cfaa756e050a3d83045008f84a62802fc68c17f2b4eabeaae5e4@%3Cissues.flink.apache.org%3E', 'https://lists.apache.org/thread.html/r706cfbc098420f7113968cc377247ec3d1439bce42e679c11c609e2d@%3Cissues.flink.apache.org%3E', 'https://security.gentoo.org/glsa/202007-03', 'https://lists.apache.org/thread.html/re4ae96fa5c1a2fe71ccbb7b7ac1538bd0cb677be270a2bf6e2f8d108@%3Cissues.flink.apache.org%3E', 'https://github.com/jquery/jquery/commit/1d61fd9407e6fbe82fe55cb0b938307aa0791f77', 'https://github.com/jquery/jquery/security/advisories/GHSA-gxr4-xjj5-5px2', 'https://lists.apache.org/thread.html/r49ce4243b4738dd763caeb27fa8ad6afb426ae3e8c011ff00b8b1f48@%3Cissues.flink.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'http://packetstormsecurity.com/files/162159/jQuery-1.2-Cross-Site-Scripting.html', 'https://www.tenable.com/security/tns-2020-10', 'https://lists.apache.org/thread.html/r54565a8f025c7c4f305355fdfd75b68eca442eebdb5f31c2e7d977ae@%3Cissues.flink.apache.org%3E', 'https://jquery.com/upgrade-guide/3.5/', 'https://lists.apache.org/thread.html/r0483ba0072783c2e1bfea613984bfb3c86e73ba8879d780dc1cc7d36@%3Cissues.flink.apache.org%3E', 'https://github.com/jquery/jquery/releases/tag/3.5.0', 'http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00067.html', 'https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://lists.apache.org/thread.html/r8f70b0f65d6bedf316ecd899371fd89e65333bc988f6326d2956735c@%3Cissues.flink.apache.org%3E', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VOE7P7APPRQKD4FGNHBKJPDY6FFCOH3W/', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://lists.apache.org/thread.html/r564585d97bc069137e64f521e68ba490c7c9c5b342df5d73c49a0760@%3Cissues.flink.apache.org%3E', 'https://www.drupal.org/sa-core-2020-002', 'https://www.npmjs.com/advisories/1518', 'https://lists.apache.org/thread.html/rdf44341677cf7eec7e9aa96dcf3f37ed709544863d619cca8c36f133@%3Ccommits.airflow.apache.org%3E', 'https://www.oracle.com/security-alerts/cpujan2021.html', 'http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00085.html', 'https://lists.apache.org/thread.html/ree3bd8ddb23df5fa4e372d11c226830ea3650056b1059f3965b3fce2@%3Cissues.flink.apache.org%3E', 'http://lists.opensuse.org/opensuse-security-announce/2020-11/msg00039.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11022', 'https://www.debian.org/security/2020/dsa-4693', 'https://security.netapp.com/advisory/ntap-20200511-0006/', 'https://www.oracle.com/security-alerts/cpujul2020.html', 'https://lists.apache.org/thread.html/rbb448222ba62c430e21e13f940be4cb5cfc373cd3bce56b48c0ffa67@%3Cdev.flink.apache.org%3E', 'https://www.tenable.com/security/tns-2021-02', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SFP4UK4EGP4AFH2MWYJ5A5Z4I7XVFQ6B/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SAPQVX3XDNPGFT26QAQ6AJIXZZBZ4CD4/', 'https://www.tenable.com/security/tns-2021-10', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/jquery/jquery/commit/1d61fd9407e6fbe82fe55cb0b938307aa0791f77'} | {'https://github.com/jquery/jquery/commit/1d61fd9407e6fbe82fe55cb0b938307aa0791f77'} |
GHSA | GHSA-jw37-5gqr-cf9j | Server-Side Request Forgery in ftp-srv | ### Background
The FTP protocol creates two connections, one for commands and one for transferring data.
This second data connection can be created in two ways, on the server by sending the PASV command, or on the client by sending the PORT command.
The PORT command sends the IP and port for the server to connect to the client with.
### Issue
Since the client can send an arbitrary IP with the PORT command, this can be used to cause the server to make a connection elsewhere.
### Patches
* _fix: disallow PORT connections to alternate hosts_: e449e75219d918c400dec65b4b0759f60476abca
Deprecation notices have been published for older versions.
### Workarounds
Blacklisting the FTP Command `PORT` will prevent the server from exposing this behaviour through active connections until a fix is applied.
```js
const ftp = new FtpSrv({
blacklist: ['PORT']
});
```
### References
https://www.npmjs.com/advisories/1445
### Credits
Thank you to;
@trs for fixing it
@andreeleuterio for reporting it to us for an anonymous user (Vincent) through the NPM platform
@quiquelhappy for bringing it to our attention after it slipped through the cracks during Christmas
### For more information
If you have any questions or comments about this advisory:
* Open an issue at [https://github.com/autovance/ftp-srv](https://github.com/autovance/ftp-srv)
* Email us directly; security@autovance.com | {'CVE-2020-15152'} | 2022-04-19T19:02:33Z | 2020-08-17T21:44:54Z | CRITICAL | 9.1 | {'CWE-918'} | {'https://github.com/autovance/ftp-srv/commit/5508c2346cf23b24c20070ff2e8a47c647d3d5b5', 'https://github.com/advisories/GHSA-jw37-5gqr-cf9j', 'https://www.npmjs.com/advisories/1445', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15152', 'https://github.com/autovance/ftp-srv/security/advisories/GHSA-jw37-5gqr-cf9j', 'https://www.npmjs.com/package/ftp-srv', 'https://github.com/autovance/ftp-srv/commit/e449e75219d918c400dec65b4b0759f60476abca', 'https://github.com/autovance/ftp-srv/commit/fb32b012c3baf48ee804e1dc36544cbba70b00d3'} | null | {'https://github.com/autovance/ftp-srv/commit/e449e75219d918c400dec65b4b0759f60476abca', 'https://github.com/autovance/ftp-srv/commit/fb32b012c3baf48ee804e1dc36544cbba70b00d3', 'https://github.com/autovance/ftp-srv/commit/5508c2346cf23b24c20070ff2e8a47c647d3d5b5'} | {'https://github.com/autovance/ftp-srv/commit/5508c2346cf23b24c20070ff2e8a47c647d3d5b5', 'https://github.com/autovance/ftp-srv/commit/e449e75219d918c400dec65b4b0759f60476abca', 'https://github.com/autovance/ftp-srv/commit/fb32b012c3baf48ee804e1dc36544cbba70b00d3'} |
GHSA | GHSA-g622-r636-qfqh | SQL Injection in Couchbase Sync Gateway | The Couchbase Sync Gateway 2.1.2 in combination with a Couchbase Server is affected by a previously undisclosed N1QL-injection vulnerability in the REST API. An attacker with access to the public REST API can insert additional N1QL statements through the parameters ?startkey? and ?endkey? of the ?_all_docs? endpoint. | {'CVE-2019-9039'} | 2022-04-12T22:49:51Z | 2022-02-15T01:57:18Z | CRITICAL | 9.8 | {'CWE-89'} | {'https://research.hisolutions.com/2019/06/n1ql-injection-in-couchbase-sync-gateway-cve-2019-9039/', 'https://www.couchbase.com/resources/security#SecurityAlerts', 'https://github.com/advisories/GHSA-g622-r636-qfqh', 'https://docs.couchbase.com/sync-gateway/2.5/release-notes.html', 'https://github.com/couchbase/sync_gateway/commit/97adb5b496aa96aa70398018ea96da913ffd8d8c', 'https://nvd.nist.gov/vuln/detail/CVE-2019-9039'} | null | {'https://github.com/couchbase/sync_gateway/commit/97adb5b496aa96aa70398018ea96da913ffd8d8c'} | {'https://github.com/couchbase/sync_gateway/commit/97adb5b496aa96aa70398018ea96da913ffd8d8c'} |
GHSA | GHSA-4fc4-chg7-h8gh | Unprotected dynamically loaded chunks | ### Impact
All dynamically loaded chunks receive an invalid integrity hash that is ignored by the browser, and therefore the browser cannot validate their integrity. This removes the additional level of protection offered by SRI for such chunks. Top-level chunks are unaffected.
### Patches
This issue is patched in version 1.5.1.
### Workarounds
N/A
### References
https://github.com/waysact/webpack-subresource-integrity/issues/131
### For more information
If you have any questions or comments about this advisory:
* Comment on [webpack-subresource-integrity issue #131](https://github.com/waysact/webpack-subresource-integrity/issues/131)
* Or email us at [security@waysact.com](mailto:security@waysact.com) | {'CVE-2020-15262'} | 2021-11-19T14:40:52Z | 2020-10-19T20:02:44Z | LOW | 3.7 | {'CWE-345'} | {'https://github.com/advisories/GHSA-4fc4-chg7-h8gh', 'https://github.com/waysact/webpack-subresource-integrity/issues/131', 'https://github.com/waysact/webpack-subresource-integrity/security/advisories/GHSA-4fc4-chg7-h8gh', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15262', 'https://github.com/waysact/webpack-subresource-integrity/commit/3d7090c08c333fcfb10ad9e2d6cf72e2acb7d87f'} | null | {'https://github.com/waysact/webpack-subresource-integrity/commit/3d7090c08c333fcfb10ad9e2d6cf72e2acb7d87f'} | {'https://github.com/waysact/webpack-subresource-integrity/commit/3d7090c08c333fcfb10ad9e2d6cf72e2acb7d87f'} |
GHSA | GHSA-26xx-m4q2-xhq8 | Authentication Bypass by CSRF Weakness | ### Impact
CSRF vulnerability that allows user account takeover.
All applications using any version of the frontend component of `spree_auth_devise` are affected if `protect_from_forgery` method is both:
* Executed whether as:
* A before_action callback (the default)
* A prepend_before_action (option prepend: true given) before the :load_object hook in Spree::UserController (most likely order to find).
* Configured to use :null_session or :reset_session strategies (:null_session is the default in case the no strategy is given, but rails --new generated skeleton use :exception).
That means that applications that haven't been configured differently from what it's generated with Rails aren't affected.
Thanks @waiting-for-dev for reporting and providing a patch 👏
### Patches
Spree 4.3 users should update to spree_auth_devise 4.4.1
Spree 4.2 users should update to spree_auth_devise 4.2.1
Spree 4.1 users should update to spree_auth_devise 4.1.1
Older Spree version users should update to spree_auth_devise 4.0.1
### Workarounds
If possible, change your strategy to :exception:
```ruby
class ApplicationController < ActionController::Base
protect_from_forgery with: :exception
end
```
Add the following to`config/application.rb `to at least run the `:exception` strategy on the affected controller:
```ruby
config.after_initialize do
Spree::UsersController.protect_from_forgery with: :exception
end
```
### References
https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2
| {'CVE-2021-41275'} | 2021-11-25T00:20:46Z | 2021-11-18T20:14:19Z | CRITICAL | 9.3 | {'CWE-352'} | {'https://github.com/spree/spree_auth_devise/commit/adf6ed4cd94d66091776b5febd4ff3767362de63', 'https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2', 'https://github.com/advisories/GHSA-26xx-m4q2-xhq8', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41275', 'https://github.com/spree/spree_auth_devise/security/advisories/GHSA-26xx-m4q2-xhq8'} | null | {'https://github.com/spree/spree_auth_devise/commit/adf6ed4cd94d66091776b5febd4ff3767362de63'} | {'https://github.com/spree/spree_auth_devise/commit/adf6ed4cd94d66091776b5febd4ff3767362de63'} |
GHSA | GHSA-257v-vj4p-3w2h | Regular Expression Denial of Service (ReDOS) | In the npm package `color-string`, there is a ReDos (Regular Expression Denial of Service) vulnerability regarding an exponential time complexity for
linearly increasing input lengths for `hwb()` color strings.
Strings reaching more than 5000 characters would see several
milliseconds of processing time; strings reaching more than
50,000 characters began seeing 1500ms (1.5s) of processing time.
The cause was due to a the regular expression that parses
hwb() strings - specifically, the hue value - where
the integer portion of the hue value used a 0-or-more quantifier
shortly thereafter followed by a 1-or-more quantifier.
This caused excessive backtracking and a cartesian scan,
resulting in exponential time complexity given a linear
increase in input length. | {'CVE-2021-29060'} | 2021-06-30T18:03:29Z | 2021-06-22T01:14:09Z | MODERATE | 5.3 | {'CWE-770'} | {'https://github.com/yetingli/SaveResults/blob/main/js/color-string.js', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29060', 'https://github.com/Qix-/color-string/commit/0789e21284c33d89ebc4ab4ca6f759b9375ac9d3', 'https://github.com/advisories/GHSA-257v-vj4p-3w2h', 'https://www.npmjs.com/package/color-string', 'https://github.com/Qix-/color-string/releases/tag/1.5.5', 'https://github.com/yetingli/PoCs/blob/main/CVE-2021-29060/Color-String.md'} | null | {'https://github.com/Qix-/color-string/commit/0789e21284c33d89ebc4ab4ca6f759b9375ac9d3'} | {'https://github.com/Qix-/color-string/commit/0789e21284c33d89ebc4ab4ca6f759b9375ac9d3'} |
GHSA | GHSA-m5pq-gvj9-9vr8 | Regular expression denial of service in Rust's regex crate | > This is a cross-post of [the official security advisory][advisory]. The official advisory contains a signed version with our PGP key, as well.
[advisory]: https://groups.google.com/g/rustlang-security-announcements/c/NcNNL1Jq7Yw
The Rust Security Response WG was notified that the `regex` crate did not properly limit the complexity of the regular expressions (regex) it parses. An attacker could use this security issue to perform a denial of service, by sending a specially crafted regex to a service accepting untrusted regexes. No known vulnerability is present when parsing untrusted input with trusted regexes.
This issue has been assigned CVE-2022-24713. The severity of this vulnerability is "high" when the `regex` crate is used to parse untrusted regexes. Other uses of the `regex` crate are not affected by this vulnerability.
## Overview
The `regex` crate features built-in mitigations to prevent denial of service attacks caused by untrusted regexes, or untrusted input matched by trusted regexes. Those (tunable) mitigations already provide sane defaults to prevent attacks. This guarantee is documented and it's considered part of the crate's API.
Unfortunately a bug was discovered in the mitigations designed to prevent untrusted regexes to take an arbitrary amount of time during parsing, and it's possible to craft regexes that bypass such mitigations. This makes it possible to perform denial of service attacks by sending specially crafted regexes to services accepting user-controlled, untrusted regexes.
## Affected versions
All versions of the `regex` crate before or equal to 1.5.4 are affected by this issue. The fix is include starting from `regex` 1.5.5.
## Mitigations
We recommend everyone accepting user-controlled regexes to upgrade immediately to the latest version of the `regex` crate.
Unfortunately there is no fixed set of problematic regexes, as there are practically infinite regexes that could be crafted to exploit this vulnerability. Because of this, we do not recommend denying known problematic regexes.
## Acknowledgements
We want to thank Addison Crump for responsibly disclosing this to us according to the [Rust security policy](https://www.rust-lang.org/policies/security), and for helping review the fix.
We also want to thank Andrew Gallant for developing the fix, and Pietro Albini for coordinating the disclosure and writing this advisory. | {'CVE-2022-24713'} | 2022-04-20T19:12:42Z | 2022-03-08T20:00:36Z | HIGH | 7.5 | {'CWE-400'} | {'https://www.debian.org/security/2022/dsa-5113', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24713', 'https://github.com/rust-lang/regex/security/advisories/GHSA-m5pq-gvj9-9vr8', 'https://lists.debian.org/debian-lts-announce/2022/04/msg00009.html', 'https://groups.google.com/g/rustlang-security-announcements/c/NcNNL1Jq7Yw', 'https://github.com/advisories/GHSA-m5pq-gvj9-9vr8', 'https://github.com/rust-lang/regex/commit/ae70b41d4f46641dbc45c7a4f87954aea356283e', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PDOWTHNVGBOP2HN27PUFIGRYNSNDTYRJ/', 'https://www.debian.org/security/2022/dsa-5118', 'https://lists.debian.org/debian-lts-announce/2022/04/msg00003.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/O3YB7CURSG64CIPCDPNMGPE4UU24AB6H/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JANLZ3JXWJR7FSHE57K66UIZUIJZI67T/'} | null | {'https://github.com/rust-lang/regex/commit/ae70b41d4f46641dbc45c7a4f87954aea356283e'} | {'https://github.com/rust-lang/regex/commit/ae70b41d4f46641dbc45c7a4f87954aea356283e'} |
GHSA | GHSA-8px5-63x9-5c7p | Command Injection in pullit | Versions of `pullit` prior to 1.4.0 are vulnerable to Command Injection. The package does not validate input on git branch names and concatenates it to an exec call, allowing attackers to run arbitrary commands in the system.
## Recommendation
Upgrade to version 1.4.0 or later.
## Credits
This vulnerability was discovered by @lirantal | null | 2022-04-01T19:35:32Z | 2020-09-03T16:47:30Z | HIGH | 0 | {'CWE-77'} | {'https://github.com/advisories/GHSA-8px5-63x9-5c7p', 'https://github.com/jkup/pullit/issues/23', 'https://hackerone.com/reports/315773', 'https://www.npmjs.com/advisories/1004', 'https://github.com/jkup/pullit/commit/4fec455774ee08f4dce0ef2ef934ffcc37219bfb'} | null | {'https://github.com/jkup/pullit/commit/4fec455774ee08f4dce0ef2ef934ffcc37219bfb'} | {'https://github.com/jkup/pullit/commit/4fec455774ee08f4dce0ef2ef934ffcc37219bfb'} |
GHSA | GHSA-7xxv-wpxj-mx5v | Out-of-bounds read in typed-ast and cpython may allow an attacker to crash the interpreter process (ast_for_arguments case). | typed_ast 1.3.0 and 1.3.1 has an ast_for_arguments out-of-bounds read. An attacker with the ability to cause a Python interpreter to parse Python source (but not necessarily execute it) may be able to crash the interpreter process. This could be a concern, for example, in a web-based service that parses (but does not execute) Python code. (This issue also affected certain Python 3.8.0-alpha prereleases.) | {'CVE-2019-19275'} | 2021-08-19T15:07:51Z | 2019-12-02T18:03:09Z | HIGH | 7.5 | {'CWE-125'} | {'https://github.com/python/cpython/commit/a4d78362397fc3bced6ea80fbc7b5f4827aec55e', 'https://nvd.nist.gov/vuln/detail/CVE-2019-19275', 'https://bugs.python.org/issue36495', 'https://github.com/python/cpython/commit/dcfcd146f8e6fc5c2fc16a4c192a0c5f5ca8c53c', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LG5H4Q6LFVRX7SFXLBEJMNQFI4T5SCEA/', 'https://github.com/python/typed_ast/commit/156afcb26c198e162504a57caddfe0acd9ed7dce', 'https://github.com/advisories/GHSA-7xxv-wpxj-mx5v', 'https://github.com/python/typed_ast/commit/dc317ac9cff859aa84eeabe03fb5004982545b3b'} | null | {'https://github.com/python/cpython/commit/dcfcd146f8e6fc5c2fc16a4c192a0c5f5ca8c53c', 'https://github.com/python/cpython/commit/a4d78362397fc3bced6ea80fbc7b5f4827aec55e', 'https://github.com/python/typed_ast/commit/dc317ac9cff859aa84eeabe03fb5004982545b3b', 'https://github.com/python/typed_ast/commit/156afcb26c198e162504a57caddfe0acd9ed7dce'} | {'https://github.com/python/cpython/commit/a4d78362397fc3bced6ea80fbc7b5f4827aec55e', 'https://github.com/python/typed_ast/commit/dc317ac9cff859aa84eeabe03fb5004982545b3b', 'https://github.com/python/cpython/commit/dcfcd146f8e6fc5c2fc16a4c192a0c5f5ca8c53c', 'https://github.com/python/typed_ast/commit/156afcb26c198e162504a57caddfe0acd9ed7dce'} |
GHSA | GHSA-r9w3-g83q-m6hq | Prototype Pollution in deepmerge-ts | deepmerge-ts is used to merge 2 or more objects respecting type information. deepmerge-ts is vulnerable to Prototype Pollution via file deepmerge.ts, function defaultMergeRecords(). A fix was released in version 4.0.2. Currently, there is no known workaround. | {'CVE-2022-24802'} | 2022-04-13T16:28:11Z | 2022-04-01T17:26:03Z | HIGH | 8.1 | {'CWE-1321', 'CWE-915'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-24802', 'https://github.com/RebeccaStevens/deepmerge-ts/commit/b39f1a93d9e1c3541bd2fe159fd696a16dbe1c72', 'https://github.com/RebeccaStevens/deepmerge-ts/commit/d637db7e4fb2bfb113cb4bc1c85a125936d7081b', 'https://github.com/advisories/GHSA-r9w3-g83q-m6hq', 'https://github.com/RebeccaStevens/deepmerge-ts/security/advisories/GHSA-r9w3-g83q-m6hq'} | null | {'https://github.com/RebeccaStevens/deepmerge-ts/commit/b39f1a93d9e1c3541bd2fe159fd696a16dbe1c72', 'https://github.com/RebeccaStevens/deepmerge-ts/commit/d637db7e4fb2bfb113cb4bc1c85a125936d7081b'} | {'https://github.com/RebeccaStevens/deepmerge-ts/commit/b39f1a93d9e1c3541bd2fe159fd696a16dbe1c72', 'https://github.com/RebeccaStevens/deepmerge-ts/commit/d637db7e4fb2bfb113cb4bc1c85a125936d7081b'} |
GHSA | GHSA-55xv-f85c-248q | Regular Expression Denial of Service (ReDoS) in jsx-slack | jsx-slack v4.5.1 and earlier versions are vulnerable to a regular expression denial-of-service (ReDoS) attack.
### Impact
If attacker can put a lot of JSX elements into `<blockquote>` tag, an internal regular expression for escaping characters may consume an excessive amount of computing resources.
```javascript
/** @jsxImportSource jsx-slack */
import { Section } from 'jsx-slack'
console.log(
<Section>
<blockquote>
{[...Array(40)].map((_, i) => (
<p>{i + 1}</p>
))}
</blockquote>
</Section>
)
```
### Patches
_See also: https://github.com/yhatt/jsx-slack/security/advisories/GHSA-hp68-xhvj-x6j6_
jsx-slack v4.5.2 has updated regular expressions to prevent catastrophic backtracking.
jsx-slack v4.5.1 also had patched a workaround. It has no problems to contents with ASCII characters, but _still vulnerable to contents with multibyte characters_. (https://github.com/yhatt/jsx-slack/commit/36e4a10405e4c7745333e245fcc5029c02c7065d)
### References
- https://nvd.nist.gov/vuln/detail/CVE-2021-43838
- https://github.com/yhatt/jsx-slack/commit/36e4a10405e4c7745333e245fcc5029c02c7065d
### Credits
Thanks to @hieki for finding out this vulnerability. | {'CVE-2021-43838'} | 2022-04-19T19:03:18Z | 2021-12-17T19:59:02Z | LOW | 3.7 | {'CWE-400'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-43838', 'https://github.com/yhatt/jsx-slack/commit/36e4a10405e4c7745333e245fcc5029c02c7065d', 'https://github.com/yhatt/jsx-slack/security/advisories/GHSA-55xv-f85c-248q', 'https://github.com/advisories/GHSA-55xv-f85c-248q'} | null | {'https://github.com/yhatt/jsx-slack/commit/36e4a10405e4c7745333e245fcc5029c02c7065d'} | {'https://github.com/yhatt/jsx-slack/commit/36e4a10405e4c7745333e245fcc5029c02c7065d'} |
GHSA | GHSA-c9hq-g4q8-w893 | Privilage Escalation in moodle | If the upload course tool in Moodle was used to delete an enrollment method which did not exist or was not already enabled, the tool would erroneously enable that enrollment method. This could lead to unintended users gaining access to the course. Versions affected: 3.9 to 3.9.2, 3.8 to 3.8.5, 3.7 to 3.7.8, 3.5 to 3.5.14 and earlier unsupported versions. This is fixed in moodle 3.9.3, 3.8.6, 3.7.9, 3.5.15, and 3.10. | {'CVE-2020-25701'} | 2021-03-29T20:42:55Z | 2021-03-29T20:42:55Z | MODERATE | 5.3 | {'CWE-863'} | {'https://github.com/moodle/moodle/commit/b8e1eec4c77c858de87fedf4e405e929539ea0c5', 'https://nvd.nist.gov/vuln/detail/CVE-2020-25701', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4NNFCHPPHRJNJROIX6SYMHOC6HMKP3GU/', 'https://moodle.org/mod/forum/discuss.php?d=413939', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/B55KXBVAT45MDASJ3EK6VIGQOYGJ4NH6/', 'https://bugzilla.redhat.com/show_bug.cgi?id=1895432', 'https://github.com/advisories/GHSA-c9hq-g4q8-w893'} | null | {'https://github.com/moodle/moodle/commit/b8e1eec4c77c858de87fedf4e405e929539ea0c5'} | {'https://github.com/moodle/moodle/commit/b8e1eec4c77c858de87fedf4e405e929539ea0c5'} |
GHSA | GHSA-c8hm-7hpq-7jhg | High severity vulnerability that affects com.fasterxml.jackson.core:jackson-databind | FasterXML jackson-databind 2.x before 2.9.8 might allow attackers to have unspecified impact by leveraging failure to block the jboss-common-core class from polymorphic deserialization. | {'CVE-2018-19362'} | 2021-06-10T23:51:27Z | 2019-01-04T19:07:03Z | HIGH | 9.8 | {'CWE-502'} | {'http://www.securityfocus.com/bid/107985', 'https://access.redhat.com/errata/RHSA-2019:3140', 'https://nvd.nist.gov/vuln/detail/CVE-2018-19362', 'https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html', 'https://lists.apache.org/thread.html/ff8dcfe29377088ab655fda9d585dccd5b1f07fabd94ae84fd60a7f8@%3Ccommits.pulsar.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2019:2804', 'https://lists.apache.org/thread.html/rf1bbc0ea4a9f014cf94df9a12a6477d24a27f52741dbc87f2fd52ff2@%3Cissues.geode.apache.org%3E', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2019/03/msg00005.html', 'https://access.redhat.com/errata/RHBA-2019:0959', 'https://access.redhat.com/errata/RHSA-2019:1797', 'https://seclists.org/bugtraq/2019/May/68', 'https://access.redhat.com/errata/RHSA-2019:4037', 'https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.9.8', 'https://www.debian.org/security/2019/dsa-4452', 'https://github.com/FasterXML/jackson-databind/commit/42912cac4753f3f718ece875e4d486f8264c2f2b', 'https://lists.apache.org/thread.html/c70da3cb6e3f03e0ad8013e38b6959419d866c4a7c80fdd34b73f25c@%3Ccommits.pulsar.apache.org%3E', 'https://security.netapp.com/advisory/ntap-20190530-0003/', 'https://access.redhat.com/errata/RHSA-2019:2858', 'https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'https://www.oracle.com/security-alerts/cpujan2020.html', 'https://access.redhat.com/errata/RHSA-2019:1822', 'https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html', 'https://github.com/FasterXML/jackson-databind/issues/2186', 'https://access.redhat.com/errata/RHSA-2019:0782', 'https://access.redhat.com/errata/RHSA-2019:0877', 'https://access.redhat.com/errata/RHSA-2019:3149', 'https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/r1b103833cb5bc8466e24ff0ecc5e75b45a705334ab6a444e64e840a0@%3Cissues.bookkeeper.apache.org%3E', 'https://lists.apache.org/thread.html/37e1ed724a1b0e5d191d98c822c426670bdfde83804567131847d2a3@%3Cdevnull.infra.apache.org%3E', 'https://lists.apache.org/thread.html/bcce5a9c532b386c68dab2f6b3ce8b0cc9b950ec551766e76391caa3@%3Ccommits.nifi.apache.org%3E', 'https://github.com/advisories/GHSA-c8hm-7hpq-7jhg', 'https://access.redhat.com/errata/RHSA-2019:3002', 'https://issues.apache.org/jira/browse/TINKERPOP-2121', 'https://access.redhat.com/errata/RHSA-2019:1782', 'https://lists.apache.org/thread.html/rca37935d661f4689cb4119f1b3b224413b22be161b678e6e6ce0c69b@%3Ccommits.nifi.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'https://access.redhat.com/errata/RHSA-2019:3892', 'https://access.redhat.com/errata/RHSA-2019:1823'} | null | {'https://github.com/FasterXML/jackson-databind/commit/42912cac4753f3f718ece875e4d486f8264c2f2b'} | {'https://github.com/FasterXML/jackson-databind/commit/42912cac4753f3f718ece875e4d486f8264c2f2b'} |
GHSA | GHSA-9w7f-m4j4-j3xw | Gerapy < 0.9.8 may cause remote code execution | ### Impact
project_configure function exist remote code execute in Gerapy < 0.9.8
### Patches
Patched in version 0.9.8, please install with:
```
pip3 install -U gerapy
``` | {'CVE-2021-43857'} | 2022-01-06T20:20:10Z | 2022-01-06T17:36:38Z | HIGH | 9.8 | {'CWE-78'} | {'http://packetstormsecurity.com/files/165459/Gerapy-0.9.7-Remote-Code-Execution.html', 'https://github.com/Gerapy/Gerapy/issues/219', 'https://github.com/Gerapy/Gerapy/commit/49bcb19be5e0320e7e1535f34fe00f16a3cf3b28', 'https://github.com/advisories/GHSA-9w7f-m4j4-j3xw', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43857', 'https://github.com/Gerapy/Gerapy/security/advisories/GHSA-9w7f-m4j4-j3xw'} | null | {'https://github.com/Gerapy/Gerapy/commit/49bcb19be5e0320e7e1535f34fe00f16a3cf3b28'} | {'https://github.com/Gerapy/Gerapy/commit/49bcb19be5e0320e7e1535f34fe00f16a3cf3b28'} |
GHSA | GHSA-mjvc-j6rv-9xj8 | Insertion of Sensitive Information Into Debugging Code in Microweber | Microweber prior to 1.3 may expose sensitive information about a server and a user when running the server in debug mode. | {'CVE-2022-0721'} | 2022-02-26T01:18:18Z | 2022-02-24T00:00:54Z | HIGH | 8.8 | {'CWE-215'} | {'https://github.com/microweber/microweber/commit/b12e1a490c79460bff019f34b2e17112249b16ec', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0721', 'https://github.com/advisories/GHSA-mjvc-j6rv-9xj8', 'https://huntr.dev/bounties/ae267d39-9750-4c69-be8b-4f915da089fb'} | null | {'https://github.com/microweber/microweber/commit/b12e1a490c79460bff019f34b2e17112249b16ec'} | {'https://github.com/microweber/microweber/commit/b12e1a490c79460bff019f34b2e17112249b16ec'} |
GHSA | GHSA-59r9-6jp6-jcm7 | XSS vulnerability in GraphQL Playground from untrusted schemas | ## GraphQL Playground introspection schema template injection attack: Advisory Statement
This is a security advisory for an XSS vulnerability in `graphql-playground`.
A similar vulnerability affects `graphiql`, the package from which `graphql-playground` was forked. There is a corresponding `graphiql` [advisory](https://github.com/graphql/graphiql/security/advisories/GHSA-x4r7-m2q9-69c8).
- [1. Impact](#1-impact)
- [2. Scope](#2-scope)
- [3. Patches](#3-patches)
- [4. Reproducing the exploit](#4-reproducing-the-exploit)
- [5. Credit](#5-credit)
- [6. For more information](#6-for-more-information)
### 1. Impact
All versions of `graphql-playground-react` older than `graphql-playground-react@1.7.28` are vulnerable to compromised HTTP schema introspection responses or `schema` prop values with malicious GraphQL type names, exposing a dynamic XSS attack surface that can allow code injection on operation autocomplete.
In order for the attack to take place, the user must load a malicious schema in `graphql-playground`. There are several ways this can occur, including by specifying the URL to a malicious schema in the `endpoint` query parameter. If a user clicks on a link to a GraphQL Playground installation that specifies a malicious server, arbitrary JavaScript can run in the user's browser, which can be used to exfiltrate user credentials or other harmful goals.
### 2. Scope
This advisory describes the impact on the `graphql-playground-react` package. The vulnerability also affects `graphiql`, the package from which `graphql-playground` was forked, with a less severe impact; see the [`graphiql` advisory](https://github.com/graphql/graphiql/security/advisories/GHSA-x4r7-m2q9-69c8) for details. It affects all versions of `graphql-playground-react` older than `v1.7.28`.
This vulnerability was introduced with the first public release of `graphql-playground`, so it impacts both the original legacy `graphql-playground` and the contemporary `graphql-playground-react` npm package. It is most easily exploited on `graphql-playground-react@1.7.0` and newer, as that release added functionality which made it possible to override the endpoint URL via query parameter even if it is explicitly specified in the code.
`graphql-playground-react` is commonly loaded via the `graphql-playground-html` package or a middleware package that wraps it (`graphql-playground-express`, `graphql-playground-middleware-koa`, `graphql-playground-middleware-hapi`, or `graphql-playground-middleware-lambda`). By default, these packages render an HTML page which loads the *latest* version of `graphql-playground-react` through a CDN. If you are using one of these packages to install GraphQL Playground on your domain *and you do not explicitly pass the `version` option to `renderPlaygroundPage` or the middleware function*, then you do not need to take any action to resolve this vulnerability, as the latest version of the React app will automatically be loaded.
`graphql-playground-react` is also commonly loaded via HTML served by Apollo Server. Apollo Server always pins a specific version of `graphql-playground-react`, so if you are using Apollo Server you do need to take action to resolve this vulnerability. See the [Apollo Server advisory](https://github.com/apollographql/apollo-server/security/advisories/GHSA-qm7x-rc44-rrqw) for details.
### 3. Patches
`graphql-playground-react@1.7.28` addresses this issue via defense in depth:
- **HTML-escaping text** that should be treated as text rather than HTML. In most of the app, this happens automatically because React escapes all interpolated text by default. However, one vulnerable component uses the unsafe `innerHTML` API and interpolated type names directly into HTML. We now properly escape that type name, which fixes the known vulnerability.
- **Validates the schema** upon receiving the introspection response or schema changes. Schemas with names that violate the GraphQL spec will no longer be loaded. (This includes preventing the Doc Explorer from loading.) This change is also sufficient to fix the known vulnerability.
- **Ensuring that user-generated HTML is safe**. Schemas can contain Markdown in `description` and `deprecationReason` fields, and the web app renders them to HTML using the `markdown-it` library. Prior to `graphql-playground-react@1.7.28`, GraphQL Playground used two separate libraries to render Markdown: `markdown-it` and `marked`. As part of the development of `graphql-playground-react@1.7.28`, we verified that our use of `markdown-it` prevents the inclusion of arbitrary HTML. We use `markdown-it` without setting `html: true`, so we are comfortable relying on [`markdown-it`'s HTML escaping](https://github.com/markdown-it/markdown-it/blob/master/docs/security.md) here. We considered running a second level of sanitization over all rendered Markdown using a library such as `dompurify` but believe that is unnecessary as `markdown-it`'s sanitization appears to be adequate. `graphiql@1.4.3` does update to the latest version of `markdown-it` (v12, from v10) so that any security fixes in v11 and v12 will take effect. On the other hand, [`marked`](https://github.com/markedjs/marked) recommends the use of a separate HTML sanitizer if its input is untrusted. In this release, we switch the one component which uses `marked` to use `markdown-it` like the rest of the app.
**If you are using `graphql-playground-react` directly in your client app**, upgrade to version 1.7.28 or later.
**If you are using `graphql-playground-html` or a package which starts with `graphql-playground-middleware-` in your server** and you are passing the `version` option to a function imported from that package, change that `version` option to be at least `"1.7.28"`.
**If you are using `graphql-playground-html` or a package which starts with `graphql-playground-middleware-` in your server** and you are **NOT** passing the `version` option to a function imported from that package, no action is necessary; your app automatically loads the latest version of `graphql-playground-react` from CDN.
### 4. Reproducing the exploit
We are hosting a "malicious" server at https://graphql-xss-schema.netlify.app/graphql . This server has a hard-coded introspection result that includes unsafe HTML in type names.
If you manually change a GraphQL Playground installation to use that endpoint, clear the operation pane, and type `{x` into the operation pane, an alert will pop up; this demonstrates execution of code provided by the malicious server.
An URL like https://YOUR-PLAYGROUND-SERVER/?endpoint=https%3A%2F%2Fgraphql-xss-schema.netlify.app%2Fgraphql&query=%7B will load already configured with the endpoint in question. (This URL-based exploit works on `graphql-playground-react@1.7.0` and newer; older versions may be protected from this particular URL-based exploit depending on their configuration.)
### 5. Credit
This vulnerability was discovered by [@Ry0taK](https://github.com/Ry0taK), thank you! :1st_place_medal:
Others who contributed:
- extensive help from [@glasser](https://github.com/glasser) at [Apollo](https://github.com/apollographql)
- [@acao](https://github.com/acao)
- [@imolorhe](https://github.com/imolorhe)
- [@divyenduz](https://github.com/divyenduz)
- [@dotansimha](https://github.com/dotansimha)
- [@timsuchanek](http://github.com/timsuchanek)
- [@benjie](https://github.com/Ry0taK) and many others who provided morale support
### 6. For more information
If you have any questions or comments about this advisory:
- The `graphiql` advisory document contains [more information](https://github.com/graphql/graphiql/blob/main/docs/security/2021-introspection-schema-xss.md#2-more-details-on-the-vulnerability) about how both the client-side and server-side vulnerabilities work
- Open an issue in the [graphql-playground repo](https://github.com/graphql/graphql-playground/new/issues)
| {'CVE-2021-41249'} | 2022-04-19T19:03:03Z | 2021-11-08T18:06:09Z | HIGH | 7.1 | {'CWE-79'} | {'https://github.com/graphql/graphiql/security/advisories/GHSA-x4r7-m2q9-69c8', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41249', 'https://github.com/advisories/GHSA-59r9-6jp6-jcm7', 'https://github.com/graphql/graphiql/blob/main/docs/security/2021-introspection-schema-xss.md#2-more-details-on-the-vulnerability', 'https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7', 'https://github.com/graphql/graphql-playground/commit/b8a956006835992f12c46b90384a79ab82bcadad'} | null | {'https://github.com/graphql/graphql-playground/commit/b8a956006835992f12c46b90384a79ab82bcadad'} | {'https://github.com/graphql/graphql-playground/commit/b8a956006835992f12c46b90384a79ab82bcadad'} |
GHSA | GHSA-32m2-9f76-4gv8 | Business Logic Errors in SilverStripe Framework | SilverStripe Framework prior to version 4.10.1 is vulnerable to business logic errors. | {'CVE-2022-0227'} | 2022-02-11T20:51:41Z | 2022-02-06T00:01:01Z | MODERATE | 4.3 | null | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0227', 'https://github.com/silverstripe/silverstripe-framework/commit/cbf2987a616e9ef4d7eccae5d763ef2179bdbcc2', 'https://huntr.dev/bounties/35631e3a-f4b9-41ad-857c-7e3021932a72', 'https://github.com/advisories/GHSA-32m2-9f76-4gv8'} | null | {'https://github.com/silverstripe/silverstripe-framework/commit/cbf2987a616e9ef4d7eccae5d763ef2179bdbcc2'} | {'https://github.com/silverstripe/silverstripe-framework/commit/cbf2987a616e9ef4d7eccae5d763ef2179bdbcc2'} |
GHSA | GHSA-3w67-q784-6w7c | Division by zero in TFLite's implementation of `GatherNd` | ### Impact
The reference implementation of the `GatherNd` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/internal/reference/reference_ops.h#L966):
```cc
ret.dims_to_count[i] = remain_flat_size / params_shape.Dims(i);
```
An attacker can craft a model such that `params` input would be an empty tensor. In turn, `params_shape.Dims(.)` would be zero, in at least one dimension.
### Patches
We have patched the issue in GitHub commit [8e45822aa0b9f5df4b4c64f221e64dc930a70a9d](https://github.com/tensorflow/tensorflow/commit/8e45822aa0b9f5df4b4c64f221e64dc930a70a9d).
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-29589'} | 2021-05-21T14:26:51Z | 2021-05-21T14:26:51Z | LOW | 2.5 | {'CWE-369'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-3w67-q784-6w7c', 'https://github.com/tensorflow/tensorflow/commit/8e45822aa0b9f5df4b4c64f221e64dc930a70a9d', 'https://github.com/advisories/GHSA-3w67-q784-6w7c', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29589'} | null | {'https://github.com/tensorflow/tensorflow/commit/8e45822aa0b9f5df4b4c64f221e64dc930a70a9d'} | {'https://github.com/tensorflow/tensorflow/commit/8e45822aa0b9f5df4b4c64f221e64dc930a70a9d'} |
GHSA | GHSA-qq97-vm5h-rrhg | OCI Manifest Type Confusion Issue | ### Impact
Systems that rely on digest equivalence for image attestations may be vulnerable to type confusion.
### Patches
Upgrade to at least `v2.8.0-beta.1` if you are running `v2.x` release. If you use the code from the `main` branch, update at least to the commit after [b59a6f827947f9e0e67df0cfb571046de4733586](https://github.com/distribution/distribution/commit/b59a6f827947f9e0e67df0cfb571046de4733586).
### Workarounds
There is no way to work around this issue without patching.
### References
Due to [an oversight in the OCI Image Specification](https://github.com/opencontainers/image-spec/pull/411) that removed the embedded `mediaType` field from manifests, a maliciously crafted OCI Container Image can cause registry clients to parse the same image in two different ways without modifying the image’s digest by modifying the `Content-Type` header returned by a registry. This can invalidate a common pattern of relying on container image digests for equivalence.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [distribution](https://github.com/distribution/distribution)
* Open an issue in [distribution-spec](https://github.com/opencontainers/distribution-spec)
* Email us at [cncf-distribution-security@lists.cncf.io](mailto:cncf-distribution-security@lists.cncf.io)
| null | 2022-04-19T19:03:14Z | 2022-02-08T18:53:56Z | LOW | 3 | {'CWE-843'} | {'https://github.com/distribution/distribution/security/advisories/GHSA-qq97-vm5h-rrhg', 'https://github.com/distribution/distribution/commit/b59a6f827947f9e0e67df0cfb571046de4733586', 'https://github.com/opencontainers/image-spec/pull/411', 'https://github.com/advisories/GHSA-qq97-vm5h-rrhg'} | null | {'https://github.com/distribution/distribution/commit/b59a6f827947f9e0e67df0cfb571046de4733586'} | {'https://github.com/distribution/distribution/commit/b59a6f827947f9e0e67df0cfb571046de4733586'} |
GHSA | GHSA-j3f7-7rmc-6wqj | Improper certificate management in AWS IoT Device SDK v2 | The AWS IoT Device SDK v2 for Java, Python, C++ and Node.js appends a user supplied Certificate Authority (CA) to the root CAs instead of overriding it on macOS systems. Additionally, SNI validation is also not enabled when the CA has been “overridden”. TLS handshakes will thus succeed if the peer can be verified either from the user-supplied CA or the system’s default trust-store. Attackers with access to a host’s trust stores or are able to compromise a certificate authority already in the host's trust store (note: the attacker must also be able to spoof DNS in this case) may be able to use this issue to bypass CA pinning. An attacker could then spoof the MQTT broker, and either drop traffic and/or respond with the attacker's data, but they would not be able to forward this data on to the MQTT broker because the attacker would still need the user's private keys to authenticate against the MQTT broker. The 'aws_tls_ctx_options_override_default_trust_store_*' function within the aws-c-io submodule has been updated to address this behavior. This issue affects: Amazon Web Services AWS IoT Device SDK v2 for Java versions prior to 1.5.0 on macOS. Amazon Web Services AWS IoT Device SDK v2 for Python versions prior to 1.7.0 on macOS. Amazon Web Services AWS IoT Device SDK v2 for C++ versions prior to 1.14.0 on macOS. Amazon Web Services AWS IoT Device SDK v2 for Node.js versions prior to 1.6.0 on macOS. Amazon Web Services AWS-C-IO 0.10.7 on macOS. | {'CVE-2021-40831'} | 2021-12-03T15:22:23Z | 2021-11-24T20:35:03Z | MODERATE | 6.3 | {'CWE-295'} | {'https://github.com/aws/aws-iot-device-sdk-python-v2/commit/5aef82573202309063eb540b72cee0e565f85a2d', 'https://github.com/advisories/GHSA-j3f7-7rmc-6wqj', 'https://github.com/aws/aws-iot-device-sdk-python-v2', 'https://github.com/awslabs/aws-c-io/', 'https://github.com/aws/aws-iot-device-sdk-cpp-v2', 'https://github.com/aws/aws-iot-device-sdk-js-v2', 'https://github.com/aws/aws-iot-device-sdk-js-v2/commit/22f1989f5bdb0bdd9c912a5a2d255ee6c0854f68', 'https://github.com/aws/aws-iot-device-sdk-java-v2', 'https://nvd.nist.gov/vuln/detail/CVE-2021-40831', 'https://github.com/aws/aws-iot-device-sdk-java-v2/commit/46375e9b1bfb34109b9ff3b1eff9c770f9daa186'} | null | {'https://github.com/aws/aws-iot-device-sdk-js-v2/commit/22f1989f5bdb0bdd9c912a5a2d255ee6c0854f68', 'https://github.com/aws/aws-iot-device-sdk-java-v2/commit/46375e9b1bfb34109b9ff3b1eff9c770f9daa186', 'https://github.com/aws/aws-iot-device-sdk-python-v2/commit/5aef82573202309063eb540b72cee0e565f85a2d'} | {'https://github.com/aws/aws-iot-device-sdk-js-v2/commit/22f1989f5bdb0bdd9c912a5a2d255ee6c0854f68', 'https://github.com/aws/aws-iot-device-sdk-python-v2/commit/5aef82573202309063eb540b72cee0e565f85a2d', 'https://github.com/aws/aws-iot-device-sdk-java-v2/commit/46375e9b1bfb34109b9ff3b1eff9c770f9daa186'} |
GHSA | GHSA-j6px-jwvv-vpwq | Angular Expressions - Remote Code Execution | ### Impact
The vulnerability, reported by GoSecure Inc, allows Remote Code Execution, if you call `expressions.compile(userControlledInput)` where `userControlledInput` is text that comes from user input.
This time, the security of the package could be bypassed by using a more complex payload, using a `.constructor.constructor` technique.
* If running angular-expressions in the browser, an attacker could run any browser script when the application code calls expressions.compile(userControlledInput).
* If running angular-expressions on the server, an attacker could run any Javascript expression, thus gaining Remote Code Execution.
### Patches
Users should upgrade to version 1.1.2 of angular-expressions
### Workarounds
A temporary workaround might be either to :
* disable user-controlled input that will be fed into angular-expressions in your application
OR
* allow only following characters in the userControlledInput :
```js
if (/^[|a-zA-Z.0-9 :"'+-?]+$/.test(userControlledInput)) {
var result = expressions.compile(userControlledInput);
}
else {
result = undefined;
}
```
### References
[Removal of angular-expression sandbox](http://blog.angularjs.org/2016/09/angular-16-expression-sandbox-removal.html)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [angular-expressions](https://github.com/peerigon/angular-expressions/issues)
* [Email us](mailto:contact@javascript-ninja.fr)
### Credits
The issue was reported by Maxime Nadeau from GoSecure, Inc. | {'CVE-2021-21277'} | 2021-02-02T15:23:09Z | 2021-02-01T15:01:26Z | LOW | 0 | {'CWE-74'} | {'https://github.com/peerigon/angular-expressions/commit/07edb62902b1f6127b3dcc013da61c6316dd0bf1', 'http://blog.angularjs.org/2016/09/angular-16-expression-sandbox-removal.html', 'https://www.npmjs.com/package/angular-expressions', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21277', 'https://github.com/advisories/GHSA-j6px-jwvv-vpwq', 'https://github.com/peerigon/angular-expressions/security/advisories/GHSA-j6px-jwvv-vpwq'} | null | {'https://github.com/peerigon/angular-expressions/commit/07edb62902b1f6127b3dcc013da61c6316dd0bf1'} | {'https://github.com/peerigon/angular-expressions/commit/07edb62902b1f6127b3dcc013da61c6316dd0bf1'} |
GHSA | GHSA-x345-32rc-8h85 | Denial of service attack via push rule patterns in matrix-synapse | ### Impact
"Push rules" can specify [conditions](https://matrix.org/docs/spec/client_server/r0.6.1#conditions) under which they will match, including `event_match`, which matches event content against a pattern including wildcards.
Certain patterns can cause very poor performance in the matching engine, leading to a denial-of-service when processing moderate length events.
### Patches
The issue is patched by https://github.com/matrix-org/synapse/commit/03318a766cac9f8b053db2214d9c332a977d226c.
### Workarounds
A potential workaround might be to prevent users from making custom push rules, by blocking such requests at a reverse-proxy.
### For more information
If you have any questions or comments about this advisory, email us at security@matrix.org. | {'CVE-2021-29471'} | 2022-04-07T15:09:54Z | 2021-05-13T20:22:51Z | LOW | 3.7 | {'CWE-331', 'CWE-400'} | {'https://github.com/matrix-org/synapse/releases/tag/v1.33.2', 'https://github.com/advisories/GHSA-x345-32rc-8h85', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29471', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TNNAJOZNMVMXM6AS7RFFKB4QLUJ4IFEY/', 'https://github.com/matrix-org/synapse/security/advisories/GHSA-x345-32rc-8h85', 'https://github.com/matrix-org/synapse/commit/03318a766cac9f8b053db2214d9c332a977d226c'} | null | {'https://github.com/matrix-org/synapse/commit/03318a766cac9f8b053db2214d9c332a977d226c'} | {'https://github.com/matrix-org/synapse/commit/03318a766cac9f8b053db2214d9c332a977d226c'} |
GHSA | GHSA-jp32-vmm6-3vf5 | Directory Traversal in Kubernetes | Directory traversal vulnerability in Kubernetes, as used in Red Hat OpenShift Enterprise 3.0, allows attackers to write to arbitrary files via a crafted object type name, which is not properly handled before passing it to etcd. | {'CVE-2015-5305'} | 2022-04-12T22:38:09Z | 2022-02-15T01:57:18Z | MODERATE | 6.5 | {'CWE-22'} | {'https://github.com/kubernetes/kubernetes/commit/68f2add9bd5d43b9da1424d87d88f83d120e17d0', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-5305', 'https://nvd.nist.gov/vuln/detail/CVE-2015-5305', 'https://github.com/advisories/GHSA-jp32-vmm6-3vf5', 'https://access.redhat.com/errata/RHSA-2015:1945', 'https://bugzilla.redhat.com/show_bug.cgi?id=1273969'} | null | {'https://github.com/kubernetes/kubernetes/commit/68f2add9bd5d43b9da1424d87d88f83d120e17d0'} | {'https://github.com/kubernetes/kubernetes/commit/68f2add9bd5d43b9da1424d87d88f83d120e17d0'} |
GHSA | GHSA-j24p-r6wx-r79w | High severity vulnerability that affects thin | lib/thin/connection.rb in Thin web server before 1.2.4 relies on the X-Forwarded-For header to determine the IP address of the client, which allows remote attackers to spoof the IP address and hide activities via a modified X-Forwarded-For header. | {'CVE-2009-3287'} | 2021-09-14T18:09:45Z | 2017-10-24T18:33:38Z | HIGH | 0 | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2009-3287', 'http://github.com/macournoyer/thin/commit/7bd027914c5ffd36bb408ef47dc749de3b6e063a', 'http://www.openwall.com/lists/oss-security/2009/09/12/1', 'https://github.com/advisories/GHSA-j24p-r6wx-r79w', 'http://github.com/macournoyer/thin/blob/master/CHANGELOG'} | null | {'http://github.com/macournoyer/thin/commit/7bd027914c5ffd36bb408ef47dc749de3b6e063a'} | {'http://github.com/macournoyer/thin/commit/7bd027914c5ffd36bb408ef47dc749de3b6e063a'} |
GHSA | GHSA-8wf2-3ggj-78q9 | Improper Authentication in phpmyadmin | An issue was discovered in phpMyAdmin 4.9 before 4.9.8 and 5.1 before 5.1.2. A valid user who is already authenticated to phpMyAdmin can manipulate their account to bypass two-factor authentication for future login instances. | {'CVE-2022-23807'} | 2022-01-28T22:44:40Z | 2022-01-28T22:44:40Z | MODERATE | 4.3 | {'CWE-287'} | {'https://github.com/phpmyadmin/phpmyadmin/commit/ca54f1db050859eb8555875c6aa5d7796fdf4b32', 'https://www.phpmyadmin.net/security/PMASA-2022-1/', 'https://github.com/advisories/GHSA-8wf2-3ggj-78q9', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23807'} | null | {'https://github.com/phpmyadmin/phpmyadmin/commit/ca54f1db050859eb8555875c6aa5d7796fdf4b32'} | {'https://github.com/phpmyadmin/phpmyadmin/commit/ca54f1db050859eb8555875c6aa5d7796fdf4b32'} |
GHSA | GHSA-g8wg-cjwc-xhhp | Heap OOB in nested `tf.map_fn` with `RaggedTensor`s | ### Impact
It is possible to nest a `tf.map_fn` within another `tf.map_fn` call. However, if the input tensor is a `RaggedTensor` and there is no function signature provided, code assumes the output is a fully specified tensor and fills output buffer with uninitialized contents from the heap:
```python
import tensorflow as tf
x = tf.ragged.constant([[1,2,3], [4,5], [6]])
t = tf.map_fn(lambda r: tf.map_fn(lambda y: r, r), x)
z = tf.ragged.constant([[[1,2,3],[1,2,3],[1,2,3]],[[4,5],[4,5]],[[6]]])
```
The `t` and `z` outputs should be identical, however this is not the case. The last row of `t` contains data from the heap which can be used to leak other memory information.
The bug lies in the conversion from a `Variant` tensor to a `RaggedTensor`. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_from_variant_op.cc#L177-L190) does not check that all inner shapes match and this results in the additional dimensions in the above example.
The same implementation can result in data loss, if input tensor is tweaked:
```python
import tensorflow as tf
x = tf.ragged.constant([[1,2], [3,4,5], [6]])
t = tf.map_fn(lambda r: tf.map_fn(lambda y: r, r), x)
```
Here, the output tensor will only have 2 elements for each inner dimension.
### Patches
We have patched the issue in GitHub commit [4e2565483d0ffcadc719bd44893fb7f609bb5f12](https://github.com/tensorflow/tensorflow/commit/4e2565483d0ffcadc719bd44893fb7f609bb5f12).
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 Haris Sahovic. | {'CVE-2021-37679'} | 2021-08-25T14:41:00Z | 2021-08-25T14:41:00Z | HIGH | 7.1 | {'CWE-681', 'CWE-125'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-g8wg-cjwc-xhhp', 'https://github.com/tensorflow/tensorflow/commit/4e2565483d0ffcadc719bd44893fb7f609bb5f12', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37679', 'https://github.com/advisories/GHSA-g8wg-cjwc-xhhp'} | null | {'https://github.com/tensorflow/tensorflow/commit/4e2565483d0ffcadc719bd44893fb7f609bb5f12'} | {'https://github.com/tensorflow/tensorflow/commit/4e2565483d0ffcadc719bd44893fb7f609bb5f12'} |
GHSA | GHSA-4xww-6h7v-29jg | User enumeration in livehelperchat | livehelperchat is vulnerable to Generation of Error Message Containing Sensitive Information. There is an observable discrepancy between errors generated for users that exist and those that do not. | {'CVE-2022-0083'} | 2022-01-21T23:37:07Z | 2022-01-21T23:37:07Z | MODERATE | 0 | {'CWE-209'} | {'https://huntr.dev/bounties/4c477440-3b03-42eb-a6e2-a31b55090736', 'https://github.com/advisories/GHSA-4xww-6h7v-29jg', 'https://github.com/livehelperchat/livehelperchat/commit/fbed8728be59040a7218610e72f6eceb5f8bc152', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0083'} | null | {'https://github.com/livehelperchat/livehelperchat/commit/fbed8728be59040a7218610e72f6eceb5f8bc152'} | {'https://github.com/livehelperchat/livehelperchat/commit/fbed8728be59040a7218610e72f6eceb5f8bc152'} |
GHSA | GHSA-9w6v-m7wp-jwg4 | Http request which redirect to another hostname do not strip authorization header in @actions/http-client | ### Impact
If consumers of the http-client:
1. make an http request with an authorization header
2. that request leads to a redirect (302) and
3. the redirect url redirects to another domain or hostname
The authorization header will get passed to the other domain.
Note that since this library is for actions, the GITHUB_TOKEN that is available in actions is generated and scoped per job with [these permissions](https://help.github.com/en/actions/configuring-and-managing-workflows/authenticating-with-the-github_token#permissions-for-the-github_token).
### Patches
The problem is fixed in 1.0.8 at [npm here](https://www.npmjs.com/package/@actions/http-client). In 1.0.8, the authorization header is stripped before making the redirected request if the hostname is different.
### Workarounds
None.
### References
https://github.com/actions/http-client/pull/27
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/actions/http-client/issues | {'CVE-2020-11021'} | 2021-08-25T21:03:12Z | 2020-04-29T17:58:53Z | MODERATE | 6.3 | {'CWE-200'} | {'https://github.com/actions/http-client/commit/f6aae3dda4f4c9dc0b49737b36007330f78fd53a', 'https://github.com/actions/http-client/security/advisories/GHSA-9w6v-m7wp-jwg4', 'https://github.com/advisories/GHSA-9w6v-m7wp-jwg4', 'https://github.com/actions/http-client/pull/27', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11021'} | null | {'https://github.com/actions/http-client/commit/f6aae3dda4f4c9dc0b49737b36007330f78fd53a'} | {'https://github.com/actions/http-client/commit/f6aae3dda4f4c9dc0b49737b36007330f78fd53a'} |
GHSA | GHSA-77xq-cpvg-7xm2 | Prototype pollution in @tsed/core | "This affects the package @tsed/core before 5.65.7. This vulnerability relates to the deepExtend function which is used as part of the utils directory. Depending on if user input is provided, an attacker can overwrite and pollute the object prototype of a program." | {'CVE-2020-7748'} | 2021-08-02T15:31:01Z | 2021-05-10T19:07:56Z | MODERATE | 5.6 | {'CWE-915'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-7748', 'https://github.com/TypedProject/tsed/commit/1395773ddac35926cf058fc6da9fb8e82266761b', 'https://github.com/TypedProject/tsed/blob/production/packages/core/src/utils/deepExtends.ts%23L36', 'https://github.com/advisories/GHSA-77xq-cpvg-7xm2', 'https://snyk.io/vuln/SNYK-JS-TSEDCORE-1019382'} | null | {'https://github.com/TypedProject/tsed/commit/1395773ddac35926cf058fc6da9fb8e82266761b'} | {'https://github.com/TypedProject/tsed/commit/1395773ddac35926cf058fc6da9fb8e82266761b'} |
GHSA | GHSA-c9qf-r67m-p7cg | Null pointer dereference in `CompressElement` | ### Impact
It is possible to trigger a null pointer dereference in TensorFlow by passing an invalid input to `tf.raw_ops.CompressElement`:
```python
import tensorflow as tf
tf.raw_ops.CompressElement(components=[[]])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/data/compression_utils.cc#L34) was accessing the size of a buffer obtained from the return of a separate function call before validating that said buffer is valid.
### Patches
We have patched the issue in GitHub commit [5dc7f6981fdaf74c8c5be41f393df705841fb7c5](https://github.com/tensorflow/tensorflow/commit/5dc7f6981fdaf74c8c5be41f393df705841fb7c5).
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. Concurrently, it was resolved in `master` branch as it was also discovered internally and fixed before the report was handled. | {'CVE-2021-37637'} | 2021-08-25T14:44:12Z | 2021-08-25T14:44:12Z | HIGH | 7.7 | {'CWE-476'} | {'https://github.com/tensorflow/tensorflow/commit/5dc7f6981fdaf74c8c5be41f393df705841fb7c5', 'https://github.com/advisories/GHSA-c9qf-r67m-p7cg', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-c9qf-r67m-p7cg', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37637'} | null | {'https://github.com/tensorflow/tensorflow/commit/5dc7f6981fdaf74c8c5be41f393df705841fb7c5'} | {'https://github.com/tensorflow/tensorflow/commit/5dc7f6981fdaf74c8c5be41f393df705841fb7c5'} |
GHSA | GHSA-3cgf-9m6x-pwwr | Data races in rusqlite | An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via UnlockNotification. | {'CVE-2020-35868'} | 2021-08-25T20:47:50Z | 2021-08-25T20:47:50Z | CRITICAL | 9.8 | {'CWE-362'} | {'https://github.com/rusqlite/rusqlite/releases/tag/0.23.0', 'https://github.com/rusqlite/rusqlite/commit/45fd77ee43c38eea4d6f4e2e56c1667a55ec654f', 'https://rustsec.org/advisories/RUSTSEC-2020-0014.html', 'https://github.com/advisories/GHSA-3cgf-9m6x-pwwr', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35868'} | null | {'https://github.com/rusqlite/rusqlite/commit/45fd77ee43c38eea4d6f4e2e56c1667a55ec654f'} | {'https://github.com/rusqlite/rusqlite/commit/45fd77ee43c38eea4d6f4e2e56c1667a55ec654f'} |
GHSA | GHSA-x7jg-6pwg-fx5h | HTTP Smuggling via Transfer-Encoding Header in Puma | ### Impact
By using an invalid transfer-encoding header, an attacker could [smuggle an HTTP response.](https://portswigger.net/web-security/request-smuggling)
Originally reported by @ZeddYu, who has our thanks for the detailed report.
### Patches
The problem has been fixed in Puma 3.12.5 and Puma 4.3.4.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Puma](https://github.com/puma/puma)
* See our [security policy](https://github.com/puma/puma/security/policy) | {'CVE-2020-11076'} | 2022-04-19T19:02:26Z | 2020-05-22T14:55:05Z | HIGH | 7.5 | {'CWE-444'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-11076', 'https://github.com/advisories/GHSA-x7jg-6pwg-fx5h', 'http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00034.html', 'https://github.com/puma/puma/commit/f24d5521295a2152c286abb0a45a1e1e2bd275bd', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SKIY5H67GJIGJL6SMFWFLUQQQR3EMVPR/', 'https://lists.debian.org/debian-lts-announce/2020/10/msg00009.html', 'https://github.com/puma/puma/security/advisories/GHSA-x7jg-6pwg-fx5h', 'https://github.com/puma/puma/blob/master/History.md#434435-and-31253126--2020-05-22', 'http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00038.html'} | null | {'https://github.com/puma/puma/commit/f24d5521295a2152c286abb0a45a1e1e2bd275bd'} | {'https://github.com/puma/puma/commit/f24d5521295a2152c286abb0a45a1e1e2bd275bd'} |
GHSA | GHSA-pgcq-h79j-2f69 | Incomplete validation of shapes in multiple TF ops | ### Impact
Several TensorFlow operations are missing validation for the shapes of the tensor arguments involved in the call. Depending on the API, this can result in undefined behavior and segfault or `CHECK`-fail related crashes but in some scenarios writes and reads from heap populated arrays are also possible.
We have discovered these issues internally via tooling while working on improving/testing GPU op determinism. As such, we don't have reproducers and there will be multiple fixes for these issues.
### Patches
We have patched the issue in GitHub commits [68422b215e618df5ad375bcdc6d2052e9fd3080a](https://github.com/tensorflow/tensorflow/commit/68422b215e618df5ad375bcdc6d2052e9fd3080a), [4d74d8a00b07441cba090a02e0dd9ed385145bf4](https://github.com/tensorflow/tensorflow/commit/4d74d8a00b07441cba090a02e0dd9ed385145bf4), [579261dcd446385831fe4f7457d802a59685121d](https://github.com/tensorflow/tensorflow/commit/579261dcd446385831fe4f7457d802a59685121d), [da4aad5946be30e5f049920fa076e1f7ef021261](https://github.com/tensorflow/tensorflow/commit/da4aad5946be30e5f049920fa076e1f7ef021261), [4dddb2fd0b01cdd196101afbba6518658a2c9e07](https://github.com/tensorflow/tensorflow/commit/4dddb2fd0b01cdd196101afbba6518658a2c9e07), and [e7f497570abb6b4ae5af4970620cd880e4c0c904](https://github.com/tensorflow/tensorflow/commit/e7f497570abb6b4ae5af4970620cd880e4c0c904).
These fixes will be included in TensorFlow 2.7.0. We will also cherrypick these commits 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. | {'CVE-2021-41206'} | 2021-11-10T19:03:38Z | 2021-11-10T19:03:38Z | HIGH | 7 | {'CWE-354'} | {'https://github.com/tensorflow/tensorflow/commit/579261dcd446385831fe4f7457d802a59685121d', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41206', 'https://github.com/advisories/GHSA-pgcq-h79j-2f69', 'https://github.com/tensorflow/tensorflow/commit/da4aad5946be30e5f049920fa076e1f7ef021261', 'https://github.com/tensorflow/tensorflow/commit/4dddb2fd0b01cdd196101afbba6518658a2c9e07', 'https://github.com/tensorflow/tensorflow/commit/e7f497570abb6b4ae5af4970620cd880e4c0c904', 'https://github.com/tensorflow/tensorflow/commit/68422b215e618df5ad375bcdc6d2052e9fd3080a', 'https://github.com/tensorflow/tensorflow/commit/4d74d8a00b07441cba090a02e0dd9ed385145bf4', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-pgcq-h79j-2f69'} | null | {'https://github.com/tensorflow/tensorflow/commit/68422b215e618df5ad375bcdc6d2052e9fd3080a', 'https://github.com/tensorflow/tensorflow/commit/e7f497570abb6b4ae5af4970620cd880e4c0c904', 'https://github.com/tensorflow/tensorflow/commit/4dddb2fd0b01cdd196101afbba6518658a2c9e07', 'https://github.com/tensorflow/tensorflow/commit/da4aad5946be30e5f049920fa076e1f7ef021261', 'https://github.com/tensorflow/tensorflow/commit/4d74d8a00b07441cba090a02e0dd9ed385145bf4', 'https://github.com/tensorflow/tensorflow/commit/579261dcd446385831fe4f7457d802a59685121d'} | {'https://github.com/tensorflow/tensorflow/commit/4d74d8a00b07441cba090a02e0dd9ed385145bf4', 'https://github.com/tensorflow/tensorflow/commit/4dddb2fd0b01cdd196101afbba6518658a2c9e07', 'https://github.com/tensorflow/tensorflow/commit/68422b215e618df5ad375bcdc6d2052e9fd3080a', 'https://github.com/tensorflow/tensorflow/commit/579261dcd446385831fe4f7457d802a59685121d', 'https://github.com/tensorflow/tensorflow/commit/e7f497570abb6b4ae5af4970620cd880e4c0c904', 'https://github.com/tensorflow/tensorflow/commit/da4aad5946be30e5f049920fa076e1f7ef021261'} |
GHSA | GHSA-3m3h-v9hv-9j4h | Cross-site Scripting in django-wiki | In Django-wiki, versions 0.0.20 to 0.7.8 are vulnerable to Stored Cross-Site Scripting (XSS) in Notifications Section. An attacker who has access to edit pages can inject JavaScript payload in the title field. When a victim gets a notification regarding the changes made in the application, the payload in the notification panel renders and loads external JavaScript. | {'CVE-2021-25986'} | 2021-12-02T17:49:40Z | 2021-12-02T17:49:40Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/advisories/GHSA-3m3h-v9hv-9j4h', 'https://github.com/django-wiki/django-wiki/pull/1148', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25986', 'https://github.com/django-wiki/django-wiki/commit/9eaccc7519e4206a4d2f22640882f0737b2da9c5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25986'} | null | {'https://github.com/django-wiki/django-wiki/commit/9eaccc7519e4206a4d2f22640882f0737b2da9c5'} | {'https://github.com/django-wiki/django-wiki/commit/9eaccc7519e4206a4d2f22640882f0737b2da9c5'} |
GHSA | GHSA-57wx-m983-2f88 | Incomplete validation in boosted trees code | ### Impact
The [code for boosted trees in TensorFlow](https://github.com/tensorflow/tensorflow/blob/e0b6e58c328059829c3eb968136f17aa72b6c876/tensorflow/core/kernels/boosted_trees/stats_ops.cc) is still missing validation. As a result, attackers can trigger denial of service (via dereferencing `nullptr`s or via `CHECK`-failures) as well as abuse undefined behavior (binding references to `nullptr`s). An attacker can also read and write from heap buffers, depending on the API that gets used and the arguments that are passed to the call.
**Note**: Given that the boosted trees implementation in TensorFlow is unmaintained, it is recommend to no longer use these APIs. Instead, please use the downstream [TensorFlow Decision Forests](https://github.com/tensorflow/decision-forests) project which is newer and supports more features. We will deprecate TensorFlow's boosted trees APIs in subsequent releases.
### Patches
We have patched the issue in GitHub commit [5c8c9a8bfe750f9743d0c859bae112060b216f5c](https://github.com/tensorflow/tensorflow/commit/5c8c9a8bfe750f9743d0c859bae112060b216f5c).
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-41208'} | 2021-11-10T19:37:56Z | 2021-11-10T19:37:56Z | CRITICAL | 9.3 | {'CWE-476', 'CWE-824'} | {'https://github.com/advisories/GHSA-57wx-m983-2f88', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-57wx-m983-2f88', 'https://github.com/tensorflow/tensorflow/commit/5c8c9a8bfe750f9743d0c859bae112060b216f5c', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41208'} | null | {'https://github.com/tensorflow/tensorflow/commit/5c8c9a8bfe750f9743d0c859bae112060b216f5c'} | {'https://github.com/tensorflow/tensorflow/commit/5c8c9a8bfe750f9743d0c859bae112060b216f5c'} |
GHSA | GHSA-rcvx-rmvf-mxch | Cross-site Scripting in Eclipse Hawkbit | In all version of Eclipse Hawkbit prior to 0.3.0M7, the HTTP 404 (Not Found) JSON response body returned by the REST API may contain unsafe characters within the path attribute. Sending a POST request to a non existing resource will return the full path from the given URL unescaped to the client. | {'CVE-2020-27219'} | 2022-02-09T22:19:44Z | 2022-02-09T22:19:44Z | MODERATE | 6.1 | {'CWE-79'} | {'https://bugs.eclipse.org/bugs/show_bug.cgi?id=570289', 'https://nvd.nist.gov/vuln/detail/CVE-2020-27219', 'https://github.com/advisories/GHSA-rcvx-rmvf-mxch', 'https://github.com/eclipse/hawkbit/issues/1067', 'https://github.com/eclipse/hawkbit/commit/94b7c12cde1b38eda5414bd88d6d068008cfb9f9'} | null | {'https://github.com/eclipse/hawkbit/commit/94b7c12cde1b38eda5414bd88d6d068008cfb9f9'} | {'https://github.com/eclipse/hawkbit/commit/94b7c12cde1b38eda5414bd88d6d068008cfb9f9'} |
GHSA | GHSA-x55w-vjjp-222r | Inefficient Regular Expression in inflect | inflect is customizable inflections for nodejs. inflect is vulnerable to Inefficient Regular Expression Complexity | {'CVE-2021-3820'} | 2022-05-05T13:49:05Z | 2021-09-29T17:12:19Z | MODERATE | 5.3 | {'CWE-400', 'CWE-697', 'CWE-1333'} | {'https://huntr.dev/bounties/4612b31a-072b-4f61-a916-c7e4cbc2042a', 'https://github.com/pksunkara/inflect/commit/a9a0a8e9561c3487854c7cae42565d9652ec858b', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3820', 'https://github.com/advisories/GHSA-x55w-vjjp-222r'} | null | {'https://github.com/pksunkara/inflect/commit/a9a0a8e9561c3487854c7cae42565d9652ec858b'} | {'https://github.com/pksunkara/inflect/commit/a9a0a8e9561c3487854c7cae42565d9652ec858b'} |
GHSA | GHSA-q34h-97wf-8r8j | vault-cli contains possible RCE when reading user-defined data | ### Impact
_What kind of vulnerability is it? Who is impacted?_
vault-cli features the ability for rendering templated values (as explained in the [documentation](https://github.com/peopledoc/vault-cli/blob/2.2.1/docs/howto/templated_secrets.rst)). When a secret starts with the prefix `!template!`, vault-cli interprets the rest of the contents of the secret as a Jinja2 template.
Jinja2 is a powerful templating engine and it's not designed to safely render arbitrary templates. An attacker controlling a jinja2 template rendered on a machine can trigger arbitrary code, making this a Remote Code Execution (RCE) risk.
If the content of the vault can be completely trusted, then this is not a problem. Otherwise, if your threat model includes cases where an attacker can manipulate a secret value read from the vault using vault-cli, then this vulnerability may impact you.
This does not impact `vault` itself, except for the fact that the attacker, having an RCE on the machine that executes `vault-cli`, may abuse the token that `vault-cli` uses, to read, write or delete other data from the vault.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
In 3.0.0, the code related to interpreting vault templated secrets has been removed entirely.
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
Using the environment variable `VAULT_CLI_RENDER=false` or the flag `--no-render` (placed between `vault-cli` and the subcommand, e.g. `vault-cli --no-render get-all`) or adding `render: false` to the vault-cli configuration yaml file disables rendering and removes the vulnerability.
Using the python library, you can use: `vault_cli.get_client(render=False)` when creating your client to get a client that will not render templated secrets and thus operates securely.
### References
_Are there any links users can visit to find out more?_
Here's an article explaining how jinja2 templates might be exploited to have side effects: https://podalirius.net/en/publications/grehack-2021-optimizing-ssti-payloads-for-jinja2/
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the vault-cli repo](https://github.com/peopledoc/vault-cli/issues/new)
| {'CVE-2021-43837'} | 2022-04-19T19:03:18Z | 2021-12-16T21:02:12Z | HIGH | 8.4 | {'CWE-74'} | {'https://github.com/advisories/GHSA-q34h-97wf-8r8j', 'https://github.com/peopledoc/vault-cli/releases/tag/3.0.0', 'https://github.com/peopledoc/vault-cli/commit/3ba3955887fd6b7d4d646c8b260f21cebf5db852', 'https://github.com/peopledoc/vault-cli/security/advisories/GHSA-q34h-97wf-8r8j', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43837', 'https://github.com/peopledoc/vault-cli/pull/198', 'https://podalirius.net/en/publications/grehack-2021-optimizing-ssti-payloads-for-jinja2/'} | null | {'https://github.com/peopledoc/vault-cli/commit/3ba3955887fd6b7d4d646c8b260f21cebf5db852'} | {'https://github.com/peopledoc/vault-cli/commit/3ba3955887fd6b7d4d646c8b260f21cebf5db852'} |
GHSA | GHSA-6j89-jhpr-849f | 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-1308, CVE-2019-1335, CVE-2019-1366. | {'CVE-2019-1307'} | 2021-03-29T20:55:46Z | 2021-03-29T20:55:46Z | HIGH | 7.5 | {'CWE-787'} | {'https://github.com/chakra-core/ChakraCore/commit/cc871514deeaeaedb5b757c2ca8cd4ab9abccb5d', 'https://github.com/chakra-core/ChakraCore/commit/3fe5e24694729966a157dc613f5586a6c75f1e9b', 'https://nvd.nist.gov/vuln/detail/CVE-2019-1307', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1307', 'https://github.com/advisories/GHSA-6j89-jhpr-849f'} | null | {'https://github.com/chakra-core/ChakraCore/commit/cc871514deeaeaedb5b757c2ca8cd4ab9abccb5d', 'https://github.com/chakra-core/ChakraCore/commit/3fe5e24694729966a157dc613f5586a6c75f1e9b'} | {'https://github.com/chakra-core/ChakraCore/commit/3fe5e24694729966a157dc613f5586a6c75f1e9b', 'https://github.com/chakra-core/ChakraCore/commit/cc871514deeaeaedb5b757c2ca8cd4ab9abccb5d'} |
GHSA | GHSA-59qg-grp7-5r73 | Weave Net clusters susceptible to MitM attacks via IPv6 rogue router advertisements | ### Impact
An attacker able to run a process as root in a container is able to respond to DNS requests from the host and thereby insert themselves as a fake service.
In a cluster with an IPv4 internal network, if IPv6 is not totally disabled on the host (via ipv6.disable=1 on the kernel cmdline), it will be either unconfigured or configured on some interfaces, but it’s pretty likely that ipv6 forwarding is disabled, ie /proc/sys/net/ipv6/conf//forwarding == 0. Also by default, /proc/sys/net/ipv6/conf//accept_ra == 1. The combination of these 2 sysctls means that the host accepts router advertisements and configure the IPv6 stack using them.
By sending “rogue” router advertisements, an attacker can reconfigure the host to redirect part or all of the IPv6 traffic of the host to the attacker controlled container.
Even if there was no IPv6 traffic before, if the DNS returns A (IPv4) and AAAA (IPv6) records, many HTTP libraries will try to connect via IPv6 first then fallback to IPv4, giving an opportunity to the attacker to respond.
If by chance you also have on the host a vulnerability like last year’s RCE in apt (CVE-2019-3462), you can now escalate to the host.
### Patches
Weave Net version 2.6.3 (to be released soon) will disable the accept_ra option on the veth devices that it creates.
### Workarounds
Users should not run containers with CAP_NET_RAW capability. This has been the advice from Weave Net for years.
https://www.weave.works/docs/net/latest/kubernetes/kube-addon/#-securing-the-setup
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the Weave Net repo](https://github.com/weaveworks/weave/issues/new)
* Join the <a href="https://slack.weave.works/" target="_blank">Weave Users Slack</a>. | {'CVE-2020-11091'} | 2021-05-27T19:00:08Z | 2021-05-27T19:00:08Z | MODERATE | 5.8 | {'CWE-350'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-11091', 'https://github.com/weaveworks/weave/security/advisories/GHSA-59qg-grp7-5r73', 'https://github.com/weaveworks/weave/commit/15f21f1899060f7716c70a8555a084e836f39a60', 'https://github.com/advisories/GHSA-59qg-grp7-5r73'} | null | {'https://github.com/weaveworks/weave/commit/15f21f1899060f7716c70a8555a084e836f39a60'} | {'https://github.com/weaveworks/weave/commit/15f21f1899060f7716c70a8555a084e836f39a60'} |
GHSA | GHSA-g694-m8vq-gv9h | URL Confusion When Scheme Not Supplied in medialize/uri.js | When parsing a URL without a scheme and with excessive slashes, like ///www.example.com, URI.js will parse the hostname as null and the path as /www.example.com.
Such behaviour is different from that exhibited by browsers, which will parse ///www.example.com as http://www.example.com instead. For example, the following will cause a redirect to http://www.example.com: | {'CVE-2022-1233'} | 2022-04-15T02:53:33Z | 2022-04-05T00:00:17Z | MODERATE | 6.5 | {'CWE-601', 'CWE-115'} | {'https://github.com/advisories/GHSA-g694-m8vq-gv9h', 'https://github.com/medialize/uri.js/commit/88805fd3da03bd7a5e60947adb49d182011f1277', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1233', 'https://huntr.dev/bounties/228d5548-1109-49f8-8aee-91038e88371c'} | null | {'https://github.com/medialize/uri.js/commit/88805fd3da03bd7a5e60947adb49d182011f1277'} | {'https://github.com/medialize/uri.js/commit/88805fd3da03bd7a5e60947adb49d182011f1277'} |
GHSA | GHSA-hj48-42vr-x3v9 | Regular Expression Denial of Service in path-parse | Affected versions of npm package `path-parse` are vulnerable to Regular Expression Denial of Service (ReDoS) via splitDeviceRe, splitTailRe, and splitPathRe regular expressions. ReDoS exhibits polynomial worst-case time complexity. | {'CVE-2021-23343'} | 2021-08-10T15:34:57Z | 2021-08-10T15:33:47Z | MODERATE | 5.3 | {'CWE-400'} | {'https://github.com/jbgutierrez/path-parse/commit/eca63a7b9a473bf6978a2f5b7b3343662d1506f7', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23343', 'https://github.com/jbgutierrez/path-parse/pull/10', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1279028', 'https://github.com/advisories/GHSA-hj48-42vr-x3v9', 'https://lists.apache.org/thread.html/r6a32cb3eda3b19096ad48ef1e7aa8f26e005f2f63765abb69ce08b85@%3Cdev.myfaces.apache.org%3E', 'https://github.com/jbgutierrez/path-parse/issues/8', 'https://snyk.io/vuln/SNYK-JS-PATHPARSE-1077067'} | null | {'https://github.com/jbgutierrez/path-parse/commit/eca63a7b9a473bf6978a2f5b7b3343662d1506f7'} | {'https://github.com/jbgutierrez/path-parse/commit/eca63a7b9a473bf6978a2f5b7b3343662d1506f7'} |
GHSA | GHSA-q485-j897-qc27 | Moderate severity vulnerability that affects com.mchange:c3p0 | c3p0 0.9.5.2 allows XXE in extractXmlConfigFromInputStream in com/mchange/v2/c3p0/cfg/C3P0ConfigXmlUtils.java during initialization. | {'CVE-2018-20433'} | 2021-09-16T19:29:38Z | 2019-01-07T19:14:34Z | CRITICAL | 9.8 | {'CWE-611'} | {'https://github.com/zhutougg/c3p0/commit/2eb0ea97f745740b18dd45e4a909112d4685f87b', 'https://github.com/advisories/GHSA-q485-j897-qc27', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MQ47OFV57Y2DAHMGA5H3JOL4WHRWRFN4/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BFIVX6HOVNLAM7W3SUAMHYRNLCVQSAWR/', 'https://lists.debian.org/debian-lts-announce/2018/12/msg00021.html', 'https://nvd.nist.gov/vuln/detail/CVE-2018-20433'} | null | {'https://github.com/zhutougg/c3p0/commit/2eb0ea97f745740b18dd45e4a909112d4685f87b'} | {'https://github.com/zhutougg/c3p0/commit/2eb0ea97f745740b18dd45e4a909112d4685f87b'} |
GHSA | GHSA-h5q8-5697-9p9h | Cross-Site Request Forgery in express-cart | The express-cart package through 1.1.10 for Node.js allows CSRF. | {'CVE-2020-22403'} | 2021-09-10T17:11:55Z | 2021-08-30T17:22:15Z | HIGH | 8.8 | {'CWE-352'} | {'https://security.netapp.com/advisory/ntap-20210909-0004/', 'https://hackerone.com/reports/395944', 'https://github.com/advisories/GHSA-h5q8-5697-9p9h', 'https://www.npmjs.com/package/express-cart', 'https://nvd.nist.gov/vuln/detail/CVE-2020-22403', 'https://github.com/mrvautin/expressCart/commit/cd3ba1bc609c2f2946bfbc7ee2fccf3483eb71fb'} | null | {'https://github.com/mrvautin/expressCart/commit/cd3ba1bc609c2f2946bfbc7ee2fccf3483eb71fb'} | {'https://github.com/mrvautin/expressCart/commit/cd3ba1bc609c2f2946bfbc7ee2fccf3483eb71fb'} |
GHSA | GHSA-728c-42pc-fwxg | Unrestricted Upload of File with Dangerous Type in Crater | Unrestricted Upload of File with Dangerous Type in GitHub repository crater-invoice/crater prior to 6.0. | {'CVE-2022-0242'} | 2022-01-21T23:54:50Z | 2022-01-21T23:54:50Z | HIGH | 7.2 | {'CWE-434'} | {'https://github.com/advisories/GHSA-728c-42pc-fwxg', 'https://github.com/crater-invoice/crater/commit/dcb3ddecb9f4cde622cc42c51a2760747797624f', 'https://huntr.dev/bounties/19f3e5f7-b419-44b1-9c37-7e4404cbec94', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0242'} | null | {'https://github.com/crater-invoice/crater/commit/dcb3ddecb9f4cde622cc42c51a2760747797624f'} | {'https://github.com/crater-invoice/crater/commit/dcb3ddecb9f4cde622cc42c51a2760747797624f'} |
GHSA | GHSA-qp49-3pvw-x4m5 | sinatra does not validate expanded path matches | Sinatra before 2.2.0 does not validate that the expanded path matches public_dir when serving static files. | {'CVE-2022-29970'} | 2022-05-03T20:59:52Z | 2022-05-03T00:00:43Z | MODERATE | 0 | {'CWE-426'} | {'https://github.com/skylightio/skylight-ruby/pull/294', 'https://nvd.nist.gov/vuln/detail/CVE-2022-29970', 'https://github.com/advisories/GHSA-qp49-3pvw-x4m5', 'https://github.com/sinatra/sinatra/pull/1683/commits/462c3ca1db53ed3cfc394cf5948e9c948ad1c10e'} | null | {'https://github.com/sinatra/sinatra/pull/1683/commits/462c3ca1db53ed3cfc394cf5948e9c948ad1c10e'} | {'https://github.com/sinatra/sinatra/pull/1683/commits/462c3ca1db53ed3cfc394cf5948e9c948ad1c10e'} |
GHSA | GHSA-w973-2qcc-p78x | User Impersonation in converse.js | Versions of `converse.js` prior to 1.0.7 for 1.x or 2.0.5 for 2.x are vulnerable to User Impersonation. The package provides an incorrect implementation of [XEP-0280: Message Carbons](https://xmpp.org/extensions/xep-0280.html) that allows a remote attacker to impersonate any user, including contacts, in the vulnerable application's display. This allows for various kinds of social engineering attacks.
## Recommendation
If you're using `converse.js` 1.x, upgrade to 1.0.7 or later.
If you're using `converse.js` 2.x, upgrade to 2.0.5 or later. | {'CVE-2017-5858'} | 2021-09-28T16:56:36Z | 2020-09-11T21:19:09Z | MODERATE | 5.9 | {'CWE-346', 'CWE-20'} | {'https://github.com/jcbrand/converse.js/commit/42f249cabbbf5c026398e6d3b350f6f9536ea572', 'https://www.openwall.com/lists/oss-security/2017/02/09/29', 'https://nvd.nist.gov/vuln/detail/CVE-2017-5858', 'https://rt-solutions.de/wp-content/uploads/2017/02/CVE-2017-5589_xmpp_carbons.pdf', 'http://openwall.com/lists/oss-security/2017/02/09/29', 'https://www.npmjs.com/advisories/974', 'http://www.securityfocus.com/bid/96183', 'https://rt-solutions.de/en/2017/02/CVE-2017-5589_xmpp_carbons/', 'https://github.com/advisories/GHSA-w973-2qcc-p78x', 'https://snyk.io/vuln/SNYK-JS-CONVERSEJS-449664'} | null | {'https://github.com/jcbrand/converse.js/commit/42f249cabbbf5c026398e6d3b350f6f9536ea572'} | {'https://github.com/jcbrand/converse.js/commit/42f249cabbbf5c026398e6d3b350f6f9536ea572'} |
GHSA | GHSA-hxmg-hm46-cf62 | Remote code execution in mongo-express | mongo-express before 1.0.0 offers support for certain advanced syntax but implements this in an unsafe way. NOTE: this may overlap CVE-2019-10769. | {'CVE-2020-24391'} | 2021-04-13T15:41:01Z | 2021-04-13T15:41:01Z | HIGH | 0 | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-24391', 'https://github.com/mongo-express/mongo-express/commit/3a26b079e7821e0e209c3ee0cc2ae15ad467b91a', 'https://github.com/advisories/GHSA-hxmg-hm46-cf62', 'https://github.com/mongodb-js/query-parser/issues/16'} | null | {'https://github.com/mongo-express/mongo-express/commit/3a26b079e7821e0e209c3ee0cc2ae15ad467b91a'} | {'https://github.com/mongo-express/mongo-express/commit/3a26b079e7821e0e209c3ee0cc2ae15ad467b91a'} |
GHSA | GHSA-rv62-4pmj-xw6h | Moderate severity vulnerability that affects jupyterhub and notebook | An Open Redirect vulnerability for all browsers in Jupyter Notebook before 5.7.8 and some browsers (Chrome, Firefox) in JupyterHub before 0.9.6 allows crafted links to the login page, which will redirect to a malicious site after successful login. Servers running on a base_url prefix are not affected. | {'CVE-2019-10255'} | 2021-09-17T20:42:44Z | 2019-04-02T15:46:54Z | MODERATE | 6.1 | {'CWE-601'} | {'https://github.com/jupyter/notebook/commit/70fe9f0ddb3023162ece21fbb77d5564306b913b', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UP5RLEES2JBBNSNLBR65XM6PCD4EMF7D/', 'https://github.com/jupyter/notebook/commit/08c4c898182edbe97aadef1815cce50448f975cb', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VMDPJBVXOVO6LYGAT46VZNHH6JKSCURO/', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10255', 'https://github.com/jupyter/notebook/compare/05aa4b2...16cf97c', 'https://blog.jupyter.org/open-redirect-vulnerability-in-jupyter-jupyterhub-adf43583f1e4', 'https://github.com/jupyter/notebook/commit/d65328d4841892b412aef9015165db1eb029a8ed', 'https://github.com/advisories/GHSA-rv62-4pmj-xw6h'} | null | {'https://github.com/jupyter/notebook/commit/d65328d4841892b412aef9015165db1eb029a8ed', 'https://github.com/jupyter/notebook/commit/70fe9f0ddb3023162ece21fbb77d5564306b913b', 'https://github.com/jupyter/notebook/commit/08c4c898182edbe97aadef1815cce50448f975cb'} | {'https://github.com/jupyter/notebook/commit/70fe9f0ddb3023162ece21fbb77d5564306b913b', 'https://github.com/jupyter/notebook/commit/08c4c898182edbe97aadef1815cce50448f975cb', 'https://github.com/jupyter/notebook/commit/d65328d4841892b412aef9015165db1eb029a8ed'} |
GHSA | GHSA-gf2c-93hm-r9j5 | Cross-site Scripting in kimai2 | kimai2 is vulnerable to Cross-Site Request Forgery (CSRF) in deleting invoice templates. This vulnerability is capable of tricking admin user to delete invoice templates. | {'CVE-2021-3963'} | 2021-11-23T18:16:43Z | 2021-11-23T18:16:43Z | MODERATE | 4.3 | {'CWE-352'} | {'https://github.com/kevinpapst/kimai2/commit/95796ab2560ad93f44068a88f0fad758c2053514', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3963', 'https://huntr.dev/bounties/3abf308b-7dbd-4864-b1a9-5c45b876def8', 'https://github.com/advisories/GHSA-gf2c-93hm-r9j5'} | null | {'https://github.com/kevinpapst/kimai2/commit/95796ab2560ad93f44068a88f0fad758c2053514'} | {'https://github.com/kevinpapst/kimai2/commit/95796ab2560ad93f44068a88f0fad758c2053514'} |
GHSA | GHSA-h76r-vgf3-j6w5 | Auth bypass and account takeover in October CMS | ### Impact
An attacker can exploit this vulnerability to bypass authentication using a specially crafted persist cookie.
- To exploit this vulnerability, an attacker must obtain a Laravel’s secret key for cookie encryption and signing.
- Due to the logic of how this mechanism works, a targeted user account must be logged in while
the attacker is exploiting the vulnerability.
- Authorization via persist cookie not shown in access logs.
### Patches
- Issue has been patched in Build 472 and v1.1.5
- [Shortened patch instructions](https://github.com/daftspunk/CVE-2021-32648)
### Workarounds
Apply https://github.com/octobercms/library/commit/016a297b1bec55d2e53bc889458ed2cb5c3e9374 and https://github.com/octobercms/library/commit/5bd1a28140b825baebe6becd4f7562299d3de3b9 to your installation manually if you are unable to upgrade.
[**Update 2022-01-20**] [Shortened patch instructions](https://github.com/daftspunk/CVE-2021-32648) can be found here.
### Recommendations
We recommend the following steps to make sure your server stays secure:
- Keep server OS and system software up to date.
- Keep October CMS software up to date.
- Use a multi-factor authentication plugin.
- Change the [default backend URL](https://github.com/octobercms/october/blob/1.1/config/cms.php#L39) or block public access to the backend area.
- Include the [Roave/SecurityAdvisories](https://github.com/Roave/SecurityAdvisories) Composer package to ensure that your application doesn't have installed dependencies with known security vulnerabilities.
### References
Bugs found as part of Solar Security CMS Research. Credits to:
• Andrey Basarygin
• Andrey Guzei
• Mikhail Khramenkov
• Alexander Sidukov
• Maxim Teplykh
### For more information
If you have any questions or comments about this advisory:
* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)
| {'CVE-2021-29487'} | 2022-01-20T15:39:15Z | 2021-08-30T16:13:50Z | HIGH | 7.4 | {'CWE-287'} | {'https://github.com/octobercms/october/security/advisories/GHSA-h76r-vgf3-j6w5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29487', 'https://github.com/octobercms/library/commit/5bd1a28140b825baebe6becd4f7562299d3de3b9', 'https://github.com/advisories/GHSA-h76r-vgf3-j6w5', 'https://github.com/octobercms/library/commit/016a297b1bec55d2e53bc889458ed2cb5c3e9374'} | null | {'https://github.com/octobercms/library/commit/5bd1a28140b825baebe6becd4f7562299d3de3b9', 'https://github.com/octobercms/library/commit/016a297b1bec55d2e53bc889458ed2cb5c3e9374'} | {'https://github.com/octobercms/library/commit/5bd1a28140b825baebe6becd4f7562299d3de3b9', 'https://github.com/octobercms/library/commit/016a297b1bec55d2e53bc889458ed2cb5c3e9374'} |
GHSA | GHSA-jj53-8fmw-f2w2 | Adding a private/unlisted room to a community exposes room metadata in an unauthorised manner. | ### Impact
Unauthorised users can access the name, avatar, topic and number of members of a room if they know the ID of the room. This vulnerability is limited to homeservers where:
- the vulnerable homeserver is in the room; and
- untrusted users are permitted to create groups (communities).
By default, only homeserver administrators can create groups. However, homeserver administrators can already access this information in the database or using the admin API. As a result, only homeservers where the configuration setting `enable_group_creation` has been set to `true` are impacted.
### Patches
Server administrators should upgrade to 1.41.1 or higher.
### Workarounds
Server administrators can set `enable_group_creation` to `false` in their homeserver configuration (this is the default value) to prevent creation of groups by non-administrators.
Administrators that are using a reverse proxy could, with partial loss of group functionality, block the following endpoints:
* `/_matrix/client/r0/groups/{group_id}/rooms`
* `/_matrix/client/unstable/groups/{group_id}/rooms`
### References
n/a
### For more information
If you have any questions or comments about this advisory, e-mail us at security@matrix.org.
| {'CVE-2021-39163'} | 2022-04-19T19:03:11Z | 2021-09-01T18:25:44Z | LOW | 3.1 | {'CWE-200'} | {'https://github.com/matrix-org/synapse/commit/cb35df940a', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PXT7ID7DNBRN2TVTETU3SYQHJKEG6PXN/', 'https://github.com/advisories/GHSA-jj53-8fmw-f2w2', 'https://github.com/matrix-org/synapse/releases/tag/v1.41.1', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39163', 'https://github.com/matrix-org/synapse/security/advisories/GHSA-jj53-8fmw-f2w2', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2VHDEPCZ22GJFMZCWA2XZAGPOEV72POF/'} | null | {'https://github.com/matrix-org/synapse/commit/cb35df940a'} | {'https://github.com/matrix-org/synapse/commit/cb35df940a'} |
GHSA | GHSA-x7cr-6qr6-2hh6 | Missing input validation can lead to command execution in composer | The Composer method `VcsDriver::getFileContent()` with user-controlled `$file` or `$identifier` arguments is susceptible to an argument injection vulnerability. It can be leveraged to gain arbitrary command execution if the Mercurial or the Git driver are used.
This led to a vulnerability on Packagist.org and Private Packagist, i.e., using the composer.json `readme` field as a vector for injecting parameters into the `$file` argument for the Mercurial driver or via the `$identifier` argument for the Git and Mercurial drivers.
Composer itself can be attacked through branch names by anyone controlling a Git or Mercurial repository, which is explicitly listed by URL in a project's composer.json.
To the best of our knowledge, this was not actively exploited. The vulnerability has been patched on Packagist.org and Private Packagist within a day of the vulnerability report. | {'CVE-2022-24828'} | 2022-04-26T18:00:17Z | 2022-04-22T20:15:38Z | HIGH | 8.3 | {'CWE-94', 'CWE-20'} | {'https://github.com/composer/composer/commit/2c40c53637c5c7e43fff7c09d3d324d632734709', 'https://www.tenable.com/security/tns-2022-09', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GWT6LDSRY7SFMTDZWJ4MS2ZBXHL7VQEF/', 'https://github.com/advisories/GHSA-x7cr-6qr6-2hh6', 'https://github.com/composer/composer/security/advisories/GHSA-x7cr-6qr6-2hh6', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24828', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QD7JQWL6C4GVROO25DTXWYWM6BPOPPCG/'} | null | {'https://github.com/composer/composer/commit/2c40c53637c5c7e43fff7c09d3d324d632734709'} | {'https://github.com/composer/composer/commit/2c40c53637c5c7e43fff7c09d3d324d632734709'} |
GHSA | GHSA-95xm-g58g-3p88 | Integer division by 0 in sparse reshaping | ### Impact
The implementation of `tf.raw_ops.SparseReshape` can be made to trigger an integral division by 0 exception:
```python
import tensorflow as tf
tf.raw_ops.SparseReshape(
input_indices = np.ones((1,3)),
input_shape = np.array([1,1,0]),
new_shape = np.array([1,0]))
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L176-L181) calls the reshaping functor whenever there is at least an index in the input but does not check that shape of the input or the target shape have both a non-zero number of elements.
The [reshape functor](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L40-L78) blindly divides by the dimensions of the target shape. Hence, if this is not checked, code will result in a division by 0.
### Patches
We have patched the issue in GitHub commit [4923de56ec94fff7770df259ab7f2288a74feb41](https://github.com/tensorflow/tensorflow/commit/4923de56ec94fff7770df259ab7f2288a74feb41).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1 as this is the other affected version.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-37640'} | 2021-08-25T14:44:02Z | 2021-08-25T14:44:02Z | MODERATE | 5.5 | {'CWE-369'} | {'https://github.com/advisories/GHSA-95xm-g58g-3p88', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37640', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-95xm-g58g-3p88', 'https://github.com/tensorflow/tensorflow/commit/4923de56ec94fff7770df259ab7f2288a74feb41'} | null | {'https://github.com/tensorflow/tensorflow/commit/4923de56ec94fff7770df259ab7f2288a74feb41'} | {'https://github.com/tensorflow/tensorflow/commit/4923de56ec94fff7770df259ab7f2288a74feb41'} |
GHSA | GHSA-ppxc-pmx9-qjv9 | Out-of-bounds write | A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1131, CVE-2019-1139, CVE-2019-1140, CVE-2019-1141, CVE-2019-1196, CVE-2019-1197. | {'CVE-2019-1195'} | 2021-03-29T20:57:59Z | 2021-03-29T20:57:59Z | HIGH | 7.5 | {'CWE-787'} | {'https://github.com/advisories/GHSA-ppxc-pmx9-qjv9', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1195', 'https://nvd.nist.gov/vuln/detail/CVE-2019-1195', 'https://github.com/chakra-core/ChakraCore/commit/c70af488e435ebd552f3da0547dee39dc8437a64', 'https://github.com/chakra-core/ChakraCore/commit/6b1250b6ffea7006226dd937e52cf5b353fcfc15'} | null | {'https://github.com/chakra-core/ChakraCore/commit/c70af488e435ebd552f3da0547dee39dc8437a64', 'https://github.com/chakra-core/ChakraCore/commit/6b1250b6ffea7006226dd937e52cf5b353fcfc15'} | {'https://github.com/chakra-core/ChakraCore/commit/c70af488e435ebd552f3da0547dee39dc8437a64', 'https://github.com/chakra-core/ChakraCore/commit/6b1250b6ffea7006226dd937e52cf5b353fcfc15'} |
GHSA | GHSA-xp82-jmw8-mjxp | Unrestricted Upload of File with Dangerous Type in ShowDoc | There is a Unrestricted Upload of File vulnerability in ShowDoc prior to version 2.10.4. | {'CVE-2022-1034'} | 2022-03-30T20:49:29Z | 2022-03-23T00:00:23Z | HIGH | 7.2 | {'CWE-434'} | {'https://github.com/star7th/showdoc/commit/bd792a89c0325836fbd64784f4c4117c0171416b', 'https://github.com/advisories/GHSA-xp82-jmw8-mjxp', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1034', 'https://huntr.dev/bounties/d205c489-3266-4ac4-acb7-c8ee570887f7'} | null | {'https://github.com/star7th/showdoc/commit/bd792a89c0325836fbd64784f4c4117c0171416b'} | {'https://github.com/star7th/showdoc/commit/bd792a89c0325836fbd64784f4c4117c0171416b'} |
GHSA | GHSA-jrg3-qq99-35g7 | Deserialization of Untrusted Data in Jodd | Jodd before 5.0.4 performs Deserialization of Untrusted JSON Data when setClassMetadataName is set. | {'CVE-2018-21234'} | 2022-04-26T17:59:30Z | 2022-02-10T23:03:26Z | CRITICAL | 9.8 | {'CWE-502'} | {'https://lists.apache.org/thread.html/rdce006b282e56c5cc73cdf452c51c5097154d0503396d62f48abbeae@%3Cgitbox.hive.apache.org%3E', 'https://github.com/advisories/GHSA-jrg3-qq99-35g7', 'https://lists.apache.org/thread.html/rf458683390d6650b26a2c8ba8ad396e038e520ad1cc3f3f1e20514d9@%3Cdev.hive.apache.org%3E', 'https://lists.apache.org/thread.html/r317aec95c436848233047af7ecb3ce04ce446eb6031f981aef50df0d@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/rc85b650b4ad2c77d7c39c69824488e40dce6d0ebbb4204777d094375@%3Cgitbox.hive.apache.org%3E', 'https://lists.apache.org/thread.html/r965503b27d67a2d934e34fc1d088c9547d51d927c43b8b9bd9b7e695@%3Cissues.hive.apache.org%3E', 'https://lists.apache.org/thread.html/r157d01c96a2c10e7ceb3e005f42c52cfe87b11dd018935e1c4277433@%3Cgitbox.hive.apache.org%3E', 'https://lists.apache.org/thread.html/rd575d9877424a2d8776f5c2ff33bf3dc3382cd83f031d483f29c11ab@%3Cissues.hive.apache.org%3E', 'https://lists.apache.org/thread.html/r729bc1e0f367fe8a857ac8a14641dba284ac4cf5131edf483022cf59@%3Cissues.hive.apache.org%3E', 'https://github.com/oblac/jodd/commit/9bffc3913aeb8472c11bb543243004b4b4376f16', 'https://lists.apache.org/thread.html/r0bacc701ab7105500a0ab2769270d18f332cb379e6a62ec7553f3327@%3Cissues.hive.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2018-21234', 'https://github.com/oblac/jodd/issues/628', 'https://lists.apache.org/thread.html/rc23200043872384e0fc48a4a4502f4c6b4b5ddc79ba4076414150d59@%3Cissues.hive.apache.org%3E', 'https://github.com/oblac/jodd/compare/v5.0.3...v5.0.4', 'https://lists.apache.org/thread.html/rdbb99b43334b59d3d3478d360c87e3235ba22edb1de7d39019194347@%3Cissues.hive.apache.org%3E'} | null | {'https://github.com/oblac/jodd/commit/9bffc3913aeb8472c11bb543243004b4b4376f16'} | {'https://github.com/oblac/jodd/commit/9bffc3913aeb8472c11bb543243004b4b4376f16'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.