ecosystem
stringclasses 14
values | vuln_id
stringlengths 10
19
| summary
stringlengths 4
267
⌀ | details
stringlengths 9
13.5k
| aliases
stringlengths 17
144
⌀ | modified_date
stringdate 2010-05-27 05:47:00
2022-05-10 08:46:52
| published_date
stringdate 2005-12-31 05:00:00
2022-05-10 08:46:50
| severity
stringclasses 5
values | score
float64 0
10
⌀ | cwe_id
stringclasses 988
values | refs
stringlengths 30
17.7k
⌀ | introduced
stringlengths 75
4.26k
⌀ |
|---|---|---|---|---|---|---|---|---|---|---|---|
PyPI
|
GHSA-h67m-xg8f-fxcf
|
Deadlock in mutually recursive `tf.function` objects
|
### Impact
The [code behind `tf.function` API](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/python/eager/def_function.py#L542) can be made to deadlock when two `tf.function` decorated Python functions are mutually recursive:
```python
import tensorflow as tf
@tf.function()
def fun1(num):
if num == 1:
return
print(num)
fun2(num-1)
@tf.function()
def fun2(num):
if num == 0:
return
print(num)
fun1(num-1)
fun1(9)
```
This occurs due to using a non-reentrant `Lock` Python object.
Loading any model which contains mutually recursive functions is vulnerable. An attacker can cause denial of service by causing users to load such models and calling a recursive `tf.function`, although this is not a frequent scenario.
### Patches
We have patched the issue in GitHub commit [afac8158d43691661ad083f6dd9e56f327c1dcb7](https://github.com/tensorflow/tensorflow/commit/afac8158d43691661ad083f6dd9e56f327c1dcb7).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
{'CVE-2021-41213'}
|
2022-03-03T05:12:53.950868Z
|
2021-11-10T18:59:32Z
|
MODERATE
| null |
{'CWE-667'}
|
{'https://github.com/tensorflow/tensorflow', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-h67m-xg8f-fxcf', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41213', 'https://github.com/tensorflow/tensorflow/commit/afac8158d43691661ad083f6dd9e56f327c1dcb7'}
| null |
PyPI
|
PYSEC-2021-148
| null |
In SiCKRAGE, versions 9.3.54.dev1 to 10.0.11.dev1 are vulnerable to Reflected Cross-Site-Scripting (XSS) due to user input not being validated properly in the `quicksearch` feature. Therefore, an attacker can steal a user's sessionID to masquerade as a victim user, to carry out any actions in the context of the user.
|
{'GHSA-x823-j7c4-vpc5', 'CVE-2021-25926'}
|
2021-08-27T03:22:21.656706Z
|
2021-04-12T14:15:00Z
| null | null | null |
{'https://github.com/advisories/GHSA-x823-j7c4-vpc5', 'https://github.com/SiCKRAGE/SiCKRAGE/commit/9f42426727e16609ad3d1337f6637588b8ed28e4', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25926,'}
| null |
PyPI
|
GHSA-p4v2-r99v-wjc2
|
Improper Encoding or Escaping of Output in Nicotine+
|
Denial of service (DoS) vulnerability in Nicotine+ starting with version 3.0.3 and prior to version 3.2.1 allows a user with a modified Soulseek client to crash Nicotine+ by sending a file download request with a file path containing a null character.
|
{'CVE-2021-45848'}
|
2022-03-29T15:31:46.064952Z
|
2022-03-16T00:00:38Z
|
HIGH
| null |
{'CWE-116'}
|
{'https://github.com/nicotine-plus/nicotine-plus', 'https://github.com/nicotine-plus/nicotine-plus/issues/1777', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HWYV53KERFH2EC4XI2IVVQFTV75E5XM6/', 'https://github.com/nicotine-plus/nicotine-plus/commit/0e3e2fac27a518f0a84330f1ddf1193424522045', 'https://nvd.nist.gov/vuln/detail/CVE-2021-45848'}
| null |
PyPI
|
PYSEC-2021-518
| null |
TensorFlow is an end-to-end open source platform for machine learning. The implementations of the `Minimum` and `Maximum` TFLite operators can be used to read data outside of bounds of heap allocated objects, if any of the two input tensor arguments are empty. This is because the broadcasting implementation(https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/internal/reference/maximum_minimum.h#L52-L56) indexes in both tensors with the same index but does not validate that the index is within bounds. 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.
|
{'GHSA-24x6-8c7m-hv3f', 'CVE-2021-29590'}
|
2021-12-09T06:34:57.326959Z
|
2021-05-14T20:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-24x6-8c7m-hv3f', 'https://github.com/tensorflow/tensorflow/commit/953f28dca13c92839ba389c055587cfe6c723578'}
| null |
PyPI
|
PYSEC-2016-24
| null |
redirect() in bottle.py in bottle 0.12.10 doesn't filter a "\r\n" sequence, which leads to a CRLF attack, as demonstrated by a redirect("233\r\nSet-Cookie: name=salt") call.
|
{'CVE-2016-9964'}
|
2021-08-27T03:21:56.402931Z
|
2016-12-16T09:59:00Z
| null | null | null |
{'https://github.com/bottlepy/bottle/issues/913', 'https://github.com/bottlepy/bottle/commit/6d7e13da0f998820800ecb3fe9ccee4189aefb54', 'http://www.debian.org/security/2016/dsa-3743', 'http://www.securityfocus.com/bid/94961'}
| null |
PyPI
|
PYSEC-2014-19
| null |
Django 1.4 before 1.4.13, 1.5 before 1.5.8, 1.6 before 1.6.5, and 1.7 before 1.7b4 does not properly include the (1) Vary: Cookie or (2) Cache-Control header in responses, which allows remote attackers to obtain sensitive information or poison the cache via a request from certain browsers.
|
{'CVE-2014-1418'}
|
2021-09-01T08:18:55.376993Z
|
2014-05-16T15:55:00Z
| null | null | null |
{'http://lists.opensuse.org/opensuse-updates/2014-09/msg00023.html', 'http://www.openwall.com/lists/oss-security/2014/05/15/3', 'http://secunia.com/advisories/61281', 'http://ubuntu.com/usn/usn-2212-1', 'https://www.djangoproject.com/weblog/2014/may/14/security-releases-issued/', 'http://www.openwall.com/lists/oss-security/2014/05/14/10', 'http://www.debian.org/security/2014/dsa-2934'}
| null |
PyPI
|
GHSA-jhjh-ghwx-6h7r
|
Low severity vulnerability that affects modulemd
|
modulemd 1.3.1 and earlier uses an unsafe function for processing externally provided data, leading to remote code execution.
|
{'CVE-2017-1002157'}
|
2022-03-03T05:13:08.108050Z
|
2019-01-17T13:56:18Z
|
LOW
| null |
{'CWE-242'}
|
{'https://pagure.io/modulemd/issue/55', 'https://github.com/advisories/GHSA-jhjh-ghwx-6h7r', 'https://nvd.nist.gov/vuln/detail/CVE-2017-1002157'}
| null |
PyPI
|
PYSEC-2020-148
| null |
urllib3 before 1.25.9 allows CRLF injection if the attacker controls the HTTP request method, as demonstrated by inserting CR and LF control characters in the first argument of putrequest(). NOTE: this is similar to CVE-2020-26116.
|
{'CVE-2020-26137', 'GHSA-wqvq-5m8c-6g24'}
|
2020-10-14T05:15:00Z
|
2020-09-30T18:15:00Z
| null | null | null |
{'https://github.com/urllib3/urllib3/pull/1800', 'https://github.com/advisories/GHSA-wqvq-5m8c-6g24', 'https://github.com/urllib3/urllib3/commit/1dd69c5c5982fae7c87a620d487c2ebf7a6b436b', 'https://bugs.python.org/issue39603', 'https://usn.ubuntu.com/4570-1/'}
| null |
PyPI
|
PYSEC-2022-81
| null |
Tensorflow is an Open Source Machine Learning Framework. Under certain scenarios, TensorFlow can fail to specialize a type during shape inference. This case is covered by the `DCHECK` function however, `DCHECK` is a no-op in production builds and an assertion failure in debug builds. In the first case execution proceeds to the `ValueOrDie` line. This results in an assertion failure as `ret` contains an error `Status`, not a value. In the second case we also get a crash due to the assertion failure. 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.
|
{'GHSA-rww7-2gpw-fv6j', 'CVE-2022-23572'}
|
2022-03-09T00:17:33.923211Z
|
2022-02-04T23:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/commit/cb164786dc891ea11d3a900e90367c339305dc7b', 'https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/framework/shape_inference.cc#L168-L174', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-rww7-2gpw-fv6j'}
| null |
PyPI
|
PYSEC-2020-53
| null |
An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. Any user authenticated within a limited scope (trust/oauth/application credential) can create an EC2 credential with an escalated permission, such as obtaining admin while the user is on a limited viewer role. This potentially allows a malicious user to act as the admin on a project another user has the admin role on, which can effectively grant that user global admin privileges.
|
{'CVE-2020-12689'}
|
2020-09-02T16:15:00Z
|
2020-05-07T00:15:00Z
| null | null | null |
{'https://bugs.launchpad.net/keystone/+bug/1872735', 'https://lists.apache.org/thread.html/re4ffc55cd2f1b55a26e07c83b3c22c3fe4bae6054d000a57fb48d8c2@%3Ccommits.druid.apache.org%3E', 'https://security.openstack.org/ossa/OSSA-2020-004.html', 'https://usn.ubuntu.com/4480-1/', 'https://www.openwall.com/lists/oss-security/2020/05/06/5', 'http://www.openwall.com/lists/oss-security/2020/05/07/2'}
| null |
PyPI
|
PYSEC-2022-141
| null |
Tensorflow is an Open Source Machine Learning Framework. The implementation of `GetInitOp` is vulnerable to a crash caused by dereferencing a null pointer. 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.
|
{'GHSA-8cxv-76p7-jxwr', 'CVE-2022-23577'}
|
2022-03-09T00:18:27.968735Z
|
2022-02-04T23:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/commit/4f38b1ac8e42727e18a2f0bde06d3bee8e77b250', 'https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/cc/saved_model/loader_util.cc#L31-L61', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-8cxv-76p7-jxwr'}
| null |
PyPI
|
PYSEC-2015-34
| null |
The build_index_from_tree function in index.py in Dulwich before 0.9.9 allows remote attackers to execute arbitrary code via a commit with a directory path starting with .git/, which is not properly handled when checking out a working tree.
|
{'CVE-2014-9706'}
|
2021-08-27T03:22:03.389388Z
|
2015-03-31T14:59:00Z
| null | null | null |
{'https://lists.launchpad.net/dulwich-users/msg00827.html', 'http://lists.fedoraproject.org/pipermail/package-announce/2015-April/154551.html', 'http://www.openwall.com/lists/oss-security/2015/03/22/26', 'http://www.openwall.com/lists/oss-security/2015/03/21/1', 'http://lists.fedoraproject.org/pipermail/package-announce/2015-April/154523.html', 'https://git.samba.org/?p=jelmer/dulwich.git;a=commitdiff;h=091638be3c89f46f42c3b1d57dc1504af5729176', 'http://www.debian.org/security/2015/dsa-3206'}
| null |
PyPI
|
PYSEC-2020-324
| null |
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one. The runtime assumes that these buffers are written to before a possible read, hence they are initialized with `nullptr`. However, by changing the buffer index for a tensor and implicitly converting that tensor to be a read-write one, as there is nothing in the model that writes to it, we get a null pointer dereference. The issue is patched in commit 0b5662bc, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
|
{'GHSA-qh32-6jjc-qprm', 'CVE-2020-15209'}
|
2021-12-09T06:35:15.002754Z
|
2020-09-25T19:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/commit/0b5662bc2be13a8c8f044d925d87fb6e56247cd8', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qh32-6jjc-qprm', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html'}
| null |
PyPI
|
PYSEC-2019-227
| null |
In TensorFlow before 1.15, a heap buffer overflow in UnsortedSegmentSum can be produced when the Index template argument is int32. In this case data_size and num_segments fields are truncated from int64 to int32 and can produce negative numbers, resulting in accessing out of bounds heap memory. This is unlikely to be exploitable and was detected and fixed internally in TensorFlow 1.15 and 2.0.
|
{'CVE-2019-16778', 'GHSA-844w-j86r-4x2j'}
|
2021-08-27T03:22:22.453759Z
|
2019-12-16T21:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2019-002.md', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-844w-j86r-4x2j', 'https://github.com/tensorflow/tensorflow/commit/db4f9717c41bccc3ce10099ab61996b246099892'}
| null |
PyPI
|
GHSA-vwhq-49r4-gj9v
|
Reference binding to `nullptr` in `tf.ragged.cross`
|
### Impact
The [shape inference code for `tf.ragged.cross`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/ragged_array_ops.cc#L64) has an undefined behavior due to binding a reference to `nullptr`. In the following scenario, this results in a crash:
```python
import tensorflow as tf
@tf.function
def test():
y = tf.ragged.cross([tf.ragged.constant([['1']]),'2'])
return y
test()
```
### Patches
We have patched the issue in GitHub commit [fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8](https://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
{'CVE-2021-41214'}
|
2022-03-03T05:12:46.112671Z
|
2021-11-10T18:58:16Z
|
HIGH
| null |
{'CWE-824'}
|
{'https://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41214', 'https://github.com/tensorflow/tensorflow', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-vwhq-49r4-gj9v'}
| null |
PyPI
|
PYSEC-2021-774
| null |
TensorFlow is an end-to-end open source platform for machine learning. In affected versions due to incomplete validation in `tf.raw_ops.QuantizeV2`, an attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays. The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/quantize_op.cc#L59) has some validation but does not check that `min_range` and `max_range` both have the same non-zero number of elements. If `axis` is provided (i.e., not `-1`), then validation should check that it is a value in range for the rank of `input` tensor and then the lengths of `min_range` and `max_range` inputs match the `axis` dimension of the `input` tensor. We have patched the issue in GitHub commit 6da6620efad397c85493b8f8667b821403516708. 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.
|
{'GHSA-g25h-jr74-qp5j', 'CVE-2021-37663'}
|
2021-12-09T06:35:37.816605Z
|
2021-08-12T23:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-g25h-jr74-qp5j', 'https://github.com/tensorflow/tensorflow/commit/6da6620efad397c85493b8f8667b821403516708'}
| null |
PyPI
|
PYSEC-2021-91
| null |
The Python "Flask-Security-Too" package is used for adding security features to your Flask application. It is an is a independently maintained version of Flask-Security based on the 3.0.0 version of Flask-Security. In Flask-Security-Too from version 3.3.0 and before version 3.4.5, the /login and /change endpoints can return the authenticated user's authentication token in response to a GET request. Since GET requests aren't protected with a CSRF token, this could lead to a malicious 3rd party site acquiring the authentication token. Version 3.4.5 and version 4.0.0 are patched. As a workaround, if you aren't using authentication tokens - you can set the SECURITY_TOKEN_MAX_AGE to "0" (seconds) which should make the token unusable.
|
{'CVE-2021-21241'}
|
2021-06-09T05:01:03.786366Z
|
2021-01-11T21:15:00Z
| null | null | null |
{'https://github.com/Flask-Middleware/flask-security/releases/tag/3.4.5', 'https://github.com/Flask-Middleware/flask-security/commit/6d50ee9169acf813257c37b75babe9c28e83542a', 'https://github.com/Flask-Middleware/flask-security/security/advisories/GHSA-hh7m-rx4f-4vpv', 'https://github.com/Flask-Middleware/flask-security/commit/61d313150b5f620d0b800896c4f2199005e84b1f', 'https://github.com/Flask-Middleware/flask-security/pull/422', 'https://pypi.org/project/Flask-Security-Too'}
| null |
PyPI
|
PYSEC-2021-324
| null |
An issue was discovered in LIEF through 0.11.4. A heap-buffer-overflow exists in the function main located in pe_reader.c. It allows an attacker to cause code Execution.
|
{'CVE-2021-32297'}
|
2021-09-20T18:35:23.431537Z
|
2021-09-20T16:15:00Z
| null | null | null |
{'https://github.com/lief-project/LIEF/issues/449'}
| null |
PyPI
|
PYSEC-2019-17
| null |
In Django 1.11.x before 1.11.18, 2.0.x before 2.0.10, and 2.1.x before 2.1.5, an Improper Neutralization of Special Elements in Output Used by a Downstream Component issue exists in django.views.defaults.page_not_found(), leading to content spoofing (in a 404 error page) if a user fails to recognize that a crafted URL has malicious content.
|
{'CVE-2019-3498', 'GHSA-337x-4q8g-prc5'}
|
2019-04-23T13:11:00Z
|
2019-01-09T23:29:00Z
| null | null | null |
{'https://www.debian.org/security/2019/dsa-4363', 'http://www.securityfocus.com/bid/106453', 'https://github.com/advisories/GHSA-337x-4q8g-prc5', 'https://usn.ubuntu.com/3851-1/', 'https://groups.google.com/forum/#!topic/django-announce/VYU7xQQTEPQ', 'https://lists.debian.org/debian-lts-announce/2019/01/msg00005.html', 'https://www.djangoproject.com/weblog/2019/jan/04/security-releases/', 'https://docs.djangoproject.com/en/dev/releases/security/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HVXDOVCXLD74SHR2BENGCE2OOYYYWJHZ/'}
| null |
PyPI
|
PYSEC-2021-631
| null |
TensorFlow is an open source platform for machine learning. In affected versions the implementation of `SplitV` can trigger a segfault is an attacker supplies negative arguments. This occurs whenever `size_splits` contains more than one value and at least one value is negative. 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.
|
{'GHSA-cpf4-wx82-gxp6', 'CVE-2021-41222'}
|
2021-12-09T06:35:10.661498Z
|
2021-11-05T23:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/commit/25d622ffc432acc736b14ca3904177579e733cc6', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cpf4-wx82-gxp6'}
| null |
PyPI
|
GHSA-grmf-4fq6-2r79
|
Improper Restriction of Operations within the Bounds of a Memory Buffer in aubio
|
aubio v0.4.0 to v0.4.8 has a Buffer Overflow in new_aubio_tempo.
|
{'CVE-2018-19800'}
|
2022-03-21T19:16:59.028066Z
|
2019-07-26T16:10:28Z
|
CRITICAL
| null |
{'CWE-119'}
|
{'https://github.com/aubio/aubio/commit/b1559f4c9ce2b304d8d27ffdc7128b6795ca82e5', 'https://nvd.nist.gov/vuln/detail/CVE-2018-19800', 'https://github.com/aubio/aubio', 'https://github.com/aubio/aubio/blob/0.4.9/ChangeLog'}
| null |
PyPI
|
PYSEC-2021-261
| null |
TensorFlow is an end-to-end open source platform for machine learning. When restoring tensors via raw APIs, if the tensor name is not provided, TensorFlow can be tricked into dereferencing a null pointer. Alternatively, attackers can read memory outside the bounds of heap allocated data by providing some tensor names but not enough for a successful restoration. The [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/save_restore_tensor.cc#L158-L159) retrieves the tensor list corresponding to the `tensor_name` user controlled input and immediately retrieves the tensor at the restoration index (controlled via `preferred_shard` argument). This occurs without validating that the provided list has enough values. If the list is empty this results in dereferencing a null pointer (undefined behavior). If, however, the list has some elements, if the restoration index is outside the bounds this results in heap OOB read. We have patched the issue in GitHub commit 9e82dce6e6bd1f36a57e08fa85af213e2b2f2622. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
|
{'GHSA-gh6x-4whr-2qv4', 'CVE-2021-37639'}
|
2021-08-27T03:22:43.020795Z
|
2021-08-12T19:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/commit/9e82dce6e6bd1f36a57e08fa85af213e2b2f2622', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-gh6x-4whr-2qv4'}
| null |
PyPI
|
GHSA-5rpc-gwh9-q9fg
|
Improper Restriction of Operations within the Bounds of a Memory Buffer in OpenCV
|
In modules/imgcodecs/src/grfmt_pxm.cpp, the length of buffer AutoBuffer _src is small than expected, which will cause copy buffer overflow later. If the image is from remote, may lead to remote code execution or denial of service. This affects OpenCV 3.3 (corresponding to OpenCV-Python 3.3.0.9) and earlier.
|
{'CVE-2017-12862'}
|
2022-03-03T05:13:56.010393Z
|
2021-10-12T22:02:21Z
|
HIGH
| null |
{'CWE-787', 'CWE-119'}
|
{'https://lists.debian.org/debian-lts-announce/2021/10/msg00028.html', 'https://github.com/opencv/opencv/issues/9370', 'https://nvd.nist.gov/vuln/detail/CVE-2017-12862', 'https://lists.debian.org/debian-lts-announce/2018/07/msg00030.html', 'https://security.gentoo.org/glsa/201712-02', 'https://github.com/opencv/opencv/pull/9376', 'https://github.com/opencv/opencv-python'}
| null |
PyPI
|
PYSEC-2020-261
| null |
A weak robustness vulnerability exists in the AWS Encryption SDKs for Java, Python, C and Javalcript prior to versions 2.0.0. Due to the non-committing property of AES-GCM (and other AEAD ciphers such as AES-GCM-SIV or (X)ChaCha20Poly1305) used by the SDKs to encrypt messages, an attacker can craft a unique cyphertext which will decrypt to multiple different results, and becomes especially relevant in a multi-recipient setting. We recommend users update their SDK to 2.0.0 or later.
|
{'GHSA-wqgp-vphw-hphf', 'CVE-2020-8897'}
|
2021-09-26T23:32:16.436833Z
|
2020-11-16T12:15:00Z
| null | null | null |
{'https://github.com/google/security-research/security/advisories/GHSA-wqgp-vphw-hphf', 'https://aws.amazon.com/blogs/security/improved-client-side-encryption-explicit-keyids-and-key-commitment/'}
| null |
PyPI
|
PYSEC-2022-97
| null |
Tensorflow is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a `SavedModel` such that Grappler optimizer would attempt to build a tensor using a reference `dtype`. This would result in a crash due to a `CHECK`-fail in the `Tensor` constructor as reference types are not allowed. 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.
|
{'GHSA-fx5c-h9f6-rv7c', 'CVE-2022-23588'}
|
2022-03-09T00:17:35.928489Z
|
2022-02-04T23:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-fx5c-h9f6-rv7c', 'https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/framework/tensor.cc#L733-L781', 'https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/grappler/optimizers/constant_folding.cc#L1328-L1402', 'https://github.com/tensorflow/tensorflow/commit/6b5adc0877de832b2a7c189532dbbbc64622eeb6'}
| null |
PyPI
|
PYSEC-2016-32
| null |
The FontManager._get_nix_font_path function in formatters/img.py in Pygments 1.2.2 through 2.0.2 allows remote attackers to execute arbitrary commands via shell metacharacters in a font name.
|
{'CVE-2015-8557'}
|
2021-08-27T03:22:17.226462Z
|
2016-01-08T20:59:00Z
| null | null | null |
{'http://www.debian.org/security/2016/dsa-3445', 'https://bitbucket.org/birkenfeld/pygments-main/pull-requests/501/fix-shell-injection-in/diff', 'http://www.openwall.com/lists/oss-security/2015/12/14/6', 'http://packetstormsecurity.com/files/133823/Pygments-FontManager._get_nix_font_path-Shell-Injection.html', 'https://security.gentoo.org/glsa/201612-05', 'http://seclists.org/fulldisclosure/2015/Oct/4', 'http://www.ubuntu.com/usn/USN-2862-1', 'http://www.openwall.com/lists/oss-security/2015/12/14/17', 'http://www.oracle.com/technetwork/topics/security/bulletinjan2016-2867206.html'}
| null |
PyPI
|
PYSEC-2022-157
| null |
Tensorflow is an Open Source Machine Learning Framework. The `simplifyBroadcast` function in the MLIR-TFRT infrastructure in TensorFlow is vulnerable to a segfault (hence, denial of service), if called with scalar shapes. If all shapes are scalar, then `maxRank` is 0, so we build an empty `SmallVector`. The fix will be included in TensorFlow 2.8.0. This is the only affected version.
|
{'GHSA-gwcx-jrx4-92w2', 'CVE-2022-23593'}
|
2022-03-09T00:18:30.081576Z
|
2022-02-04T23:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/commit/35f0fabb4c178253a964d7aabdbb15c6a398b69a', 'https://github.com/tensorflow/tensorflow/blob/274df9b02330b790aa8de1cee164b70f72b9b244/tensorflow/compiler/mlir/tfrt/jit/transforms/tf_cpurt_symbolic_shape_optimization.cc#L149-L205', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-gwcx-jrx4-92w2'}
| null |
PyPI
|
GHSA-m5ff-3wj3-8ph4
|
HTTP Request Smuggling: Invalid whitespace characters in headers in Waitress
|
### Impact
If a proxy server is used in front of waitress, an invalid request may be sent by an attacker that bypasses the front-end and is parsed differently by waitress leading to a potential for HTTP request smuggling.
```
Content-Length: 10
Transfer-Encoding: [\x0b]chunked
```
For clarity:
```
0x0b == vertical tab
```
Would get parsed by Waitress as being a `chunked` request, but a front-end server would use the `Content-Length` instead as the `Transfer-Encoding` header is considered invalid due to containing invalid characters.
If a front-end server does HTTP pipelining to a backend Waitress server this could lead to HTTP request splitting which may lead to potential cache poisoning or unexpected information disclosure.
### Patches
Please upgrade to Waitress 1.4.1 which fixes this issue with stricter HTTP field validation.
Waitress 1.4.1 due to this change has become much more strict in what is allowed in header values, while the maintainers don't believe that these changes will cause any issues, it may cause failures with non-conformist reverse proxies or clients, and it is highly recommend that users validate the changes in their environment and make sure it won't cause any unacceptable failures.
### Workarounds
You may enable additional protections on front-end servers, those that follow RFC7230 correctly would drop the request with a 400 Bad Request.
Waitress will now correctly responds to the request with a 400 Bad Request, and will drop the connection to avoid any potential HTTP pipelining issues.
### References
This was mentioned in https://portswigger.net/research/http-desync-attacks-what-happened-next and was specifically mentioned as being an issue in HAProxy which did not properly filter it in this article: https://nathandavison.com/blog/haproxy-http-request-smuggling
### Thanks
The Pylons Project would like to thank ZeddYu Lu for doing extended testing against Waitress 1.4.0 and bringing this to our attention!
### For more information
If you have any questions or comments about this advisory:
* open an issue at https://github.com/Pylons/waitress/issues (if not sensitive or security related)
* email the Pylons Security mailing list: pylons-project-security@googlegroups.com (if security related)
| null |
2022-04-25T23:17:08.149249Z
|
2019-12-26T16:34:38Z
|
HIGH
| null |
{'CWE-444'}
|
{'https://github.com/Pylons/waitress/security/advisories/GHSA-m5ff-3wj3-8ph4'}
| null |
PyPI
|
PYSEC-2019-118
| null |
In RPyC 4.1.x through 4.1.1, a remote attacker can dynamically modify object attributes to construct a remote procedure call that executes code for an RPyC service with default configuration settings.
|
{'CVE-2019-16328', 'GHSA-pj4g-4488-wmxm', 'GHSA-9ggp-4jpr-7ppj'}
|
2020-08-24T17:37:00Z
|
2019-10-03T20:15:00Z
| null | null | null |
{'http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00046.html', 'https://rpyc.readthedocs.io/en/latest/docs/security.html', 'https://github.com/tomerfiliba/rpyc', 'https://github.com/advisories/GHSA-pj4g-4488-wmxm', 'https://github.com/advisories/GHSA-9ggp-4jpr-7ppj', 'http://lists.opensuse.org/opensuse-security-announce/2020-06/msg00004.html'}
| null |
PyPI
|
PYSEC-2020-45
| null |
An issue was discovered in OpenStack Horizon before 15.3.2, 16.x before 16.2.1, 17.x and 18.x before 18.3.3, 18.4.x, and 18.5.x. There is a lack of validation of the "next" parameter, which would allow someone to supply a malicious URL in Horizon that can cause an automatic redirect to the provided malicious URL.
|
{'CVE-2020-29565'}
|
2021-03-09T15:08:00Z
|
2020-12-04T08:15:00Z
| null | null | null |
{'https://bugs.launchpad.net/horizon/+bug/1865026', 'https://security.openstack.org/ossa/OSSA-2020-008.html', 'https://review.opendev.org/c/openstack/horizon/+/758843/', 'https://review.opendev.org/c/openstack/horizon/+/758841/', 'http://www.openwall.com/lists/oss-security/2020/12/08/2', 'https://www.debian.org/security/2020/dsa-4820'}
| null |
PyPI
|
PYSEC-2022-78
| null |
Tensorflow is an Open Source Machine Learning Framework. Multiple operations in TensorFlow can be used to trigger a denial of service via `CHECK`-fails (i.e., assertion failures). This is similar to TFSA-2021-198 and has similar fixes. We have patched the reported issues in multiple GitHub commits. It is possible that other similar instances exist in TensorFlow, we will issue fixes as these are discovered. 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.
|
{'GHSA-qj5r-f9mv-rffh', 'CVE-2022-23569'}
|
2022-03-09T00:17:33.554776Z
|
2022-02-03T13:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-198.md', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qj5r-f9mv-rffh'}
| null |
PyPI
|
PYSEC-2021-332
| null |
This affects all versions of package sqlite-web. The SQL dashboard area allows sensitive actions to be performed without validating that the request originated from the application. This could enable an attacker to trick a user into performing these actions unknowingly through a Cross Site Request Forgery (CSRF) attack.
|
{'SNYK-PYTHON-SQLITEWEB-1316324', 'CVE-2021-23404', 'GHSA-2j58-pwwv-x666'}
|
2021-10-14T13:17:51.118876Z
|
2021-09-08T11:15:00Z
| null | null | null |
{'https://github.com/coleifer/sqlite-web/blob/2e7c85da3d37f80074ed3ae39b5851069b4f301c/sqlite_web/__main__.py%23L1', 'https://snyk.io/vuln/SNYK-PYTHON-SQLITEWEB-1316324', 'https://github.com/advisories/GHSA-2j58-pwwv-x666'}
| null |
PyPI
|
PYSEC-2021-87
| null |
Cranelift is an open-source code generator maintained by Bytecode Alliance. It translates a target-independent intermediate representation into executable machine code. There is a bug in 0.73 of the Cranelift x64 backend that can create a scenario that could result in a potential sandbox escape in a Wasm program. This bug was introduced in the new backend on 2020-09-08 and first included in a release on 2020-09-30, but the new backend was not the default prior to 0.73. The recently-released version 0.73 with default settings, and prior versions with an explicit build flag to select the new backend, are vulnerable. The bug in question performs a sign-extend instead of a zero-extend on a value loaded from the stack, under a specific set of circumstances. If those circumstances occur, the bug could allow access to memory addresses upto 2GiB before the start of the Wasm program heap. If the heap bound is larger than 2GiB, then it would be possible to read memory from a computable range dependent on the size of the heaps bound. The impact of this bug is highly dependent on heap implementation, specifically: * if the heap has bounds checks, and * does not rely exclusively on guard pages, and * the heap bound is 2GiB or smaller * then this bug cannot be used to reach memory from another Wasm program heap. The impact of the vulnerability is mitigated if there is no memory mapped in the range accessible using this bug, for example, if there is a 2 GiB guard region before the Wasm program heap. The bug in question performs a sign-extend instead of a zero-extend on a value loaded from the stack, when the register allocator reloads a spilled integer value narrower than 64 bits. This interacts poorly with another optimization: the instruction selector elides a 32-to-64-bit zero-extend operator when we know that an instruction producing a 32-bit value actually zeros the upper 32 bits of its destination register. Hence, we rely on these zeroed bits, but the type of the value is still i32, and the spill/reload reconstitutes those bits as the sign extension of the i32’s MSB. The issue would thus occur when: * An i32 value in a Wasm program is greater than or equal to 0x8000_0000; * The value is spilled and reloaded by the register allocator due to high register pressure in the program between the value’s definition and its use; * The value is produced by an instruction that we know to be “special” in that it zeroes the upper 32 bits of its destination: add, sub, mul, and, or; * The value is then zero-extended to 64 bits in the Wasm program; * The resulting 64-bit value is used. Under these circumstances there is a potential sandbox escape when the i32 value is a pointer. The usual code emitted for heap accesses zero-extends the Wasm heap address, adds it to a 64-bit heap base, and accesses the resulting address. If the zero-extend becomes a sign-extend, the program could reach backward and access memory up to 2GiB before the start of its heap. In addition to assessing the nature of the code generation bug in Cranelift, we have also determined that under specific circumstances, both Lucet and Wasmtime using this version of Cranelift may be exploitable. See referenced GitHub Advisory for more details.
|
{'GHSA-hpqh-2wqx-7qp5', 'CVE-2021-32629'}
|
2021-06-02T03:48:07.159295Z
|
2021-05-24T16:15:00Z
| null | null | null |
{'https://github.com/bytecodealliance/wasmtime/commit/95559c01aaa7c061088a433040f31e8291fb09d0', 'https://www.fastly.com/security-advisories/memory-access-due-to-code-generation-flaw-in-cranelift-module', 'https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-hpqh-2wqx-7qp5', 'https://crates.io/crates/cranelift-codegen'}
| null |
PyPI
|
PYSEC-2021-762
| null |
TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation for `tf.raw_ops.FractionalAvgPoolGrad` can be tricked into accessing data outside of bounds of heap allocated buffers. The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/fractional_avg_pool_op.cc#L205) does not validate that the input tensor is non-empty. Thus, code constructs an empty `EigenDoubleMatrixMap` and then accesses this buffer with indices that are outside of the empty area. We have patched the issue in GitHub commit 0f931751fb20f565c4e94aa6df58d54a003cdb30. 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.
|
{'GHSA-hpv4-7p9c-mvfr', 'CVE-2021-37651'}
|
2021-12-09T06:35:36.737111Z
|
2021-08-12T21:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hpv4-7p9c-mvfr', 'https://github.com/tensorflow/tensorflow/commit/0f931751fb20f565c4e94aa6df58d54a003cdb30'}
| null |
PyPI
|
GHSA-rgcm-rpq9-9cgr
|
Missing Authentication for Critical Function in Saleor
|
An issue was discovered in Mirumee Saleor 2.x before 2.9.1. Incorrect access control in the checkoutCustomerAttach mutations allows attackers to attach their checkouts to any user ID and consequently leak user data (e.g., name, address, and previous orders of any other customer).
|
{'CVE-2020-7964'}
|
2021-07-27T15:13:34Z
|
2021-07-28T17:57:09Z
|
MODERATE
| null |
{'CWE-306'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-7964', 'https://github.com/mirumee/saleor/releases/tag/2.9.1', 'https://github.com/mirumee/saleor/commit/233b8890c60fa6d90daf99e4d90fea85867732c3'}
| null |
PyPI
|
PYSEC-2021-298
| null |
TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.SparseFillEmptyRows`. The shape inference [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/sparse_ops.cc#L608-L634) does not validate that the input arguments are not empty tensors. We have patched the issue in GitHub commit 578e634b4f1c1c684d4b4294f9e5281b2133b3ed. 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.
|
{'CVE-2021-37676', 'GHSA-v768-w7m9-2vmm'}
|
2021-08-27T03:22:46.384345Z
|
2021-08-12T22:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/commit/578e634b4f1c1c684d4b4294f9e5281b2133b3ed', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-v768-w7m9-2vmm'}
| null |
PyPI
|
PYSEC-2019-231
| null |
Google TensorFlow 1.6.x and earlier is affected by: Null Pointer Dereference. The type of exploitation is: context-dependent.
|
{'CVE-2018-7576'}
|
2021-12-09T06:35:11.756170Z
|
2019-04-23T21:29:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2018-002.md'}
| null |
PyPI
|
GHSA-2cpx-427x-q2c6
|
CHECK-fail in AddManySparseToTensorsMap
|
### Impact
An attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.AddManySparseToTensorsMap`:
```python
import tensorflow as tf
import numpy as np
sparse_indices = tf.constant(530, shape=[1, 1], dtype=tf.int64)
sparse_values = tf.ones([1], dtype=tf.int64)
shape = tf.Variable(tf.ones([55], dtype=tf.int64))
shape[:8].assign(np.array([855, 901, 429, 892, 892, 852, 93, 96], dtype=np.int64))
tf.raw_ops.AddManySparseToTensorsMap(sparse_indices=sparse_indices,
sparse_values=sparse_values,
sparse_shape=shape)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/kernels/sparse_tensors_map_ops.cc#L257) takes the values specified in `sparse_shape` as dimensions for the output shape:
```cc
TensorShape tensor_input_shape(input_shape->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-29523'}
|
2022-03-03T05:13:59.631408Z
|
2021-05-21T14:21:43Z
|
LOW
| null |
{'CWE-190'}
|
{'https://github.com/tensorflow/tensorflow/commit/69c68ecbb24dff3fa0e46da0d16c821a2dd22d7c', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-2cpx-427x-q2c6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29523'}
| null |
PyPI
|
PYSEC-2020-332
| null |
In affected versions of TensorFlow under certain cases a saved model can trigger use of uninitialized values during code execution. This is caused by having tensor buffers be filled with the default value of the type but forgetting to default initialize the quantized floating point types in Eigen. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0.
|
{'GHSA-qhxx-j73r-qpm2', 'CVE-2020-26266'}
|
2021-12-09T06:35:15.994631Z
|
2020-12-10T23:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/commit/ace0c15a22f7f054abcc1f53eabbcb0a1239a9e2', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qhxx-j73r-qpm2'}
| null |
PyPI
|
PYSEC-2015-22
| null |
contrib.sessions.middleware.SessionMiddleware in Django 1.8.x before 1.8.4, 1.7.x before 1.7.10, 1.4.x before 1.4.22, and possibly other versions allows remote attackers to cause a denial of service (session store consumption or session record removal) via a large number of requests to contrib.auth.views.logout, which triggers the creation of an empty session record.
|
{'CVE-2015-5963'}
|
2021-07-15T02:22:09.927134Z
|
2015-08-24T14:59:00Z
| null | null | null |
{'https://access.redhat.com/errata/RHSA-2015:1876', 'http://www.securityfocus.com/bid/76428', 'http://lists.opensuse.org/opensuse-updates/2015-09/msg00026.html', 'http://rhn.redhat.com/errata/RHSA-2015-1894.html', 'http://rhn.redhat.com/errata/RHSA-2015-1766.html', 'https://www.djangoproject.com/weblog/2015/aug/18/security-releases/', 'http://www.ubuntu.com/usn/USN-2720-1', 'http://www.oracle.com/technetwork/topics/security/bulletinoct2015-2511968.html', 'http://lists.opensuse.org/opensuse-updates/2015-09/msg00035.html', 'http://www.securitytracker.com/id/1033318', 'http://rhn.redhat.com/errata/RHSA-2015-1767.html', 'http://lists.fedoraproject.org/pipermail/package-announce/2015-November/172084.html', 'http://www.debian.org/security/2015/dsa-3338'}
| null |
PyPI
|
PYSEC-2020-298
| null |
In affected versions of TensorFlow the tf.raw_ops.DataFormatVecPermute API does not validate the src_format and dst_format attributes. The code assumes that these two arguments define a permutation of NHWC. This can result in uninitialized memory accesses, read outside of bounds and even crashes. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0.
|
{'CVE-2020-26267', 'GHSA-c9f3-9wfr-wgh7'}
|
2021-12-09T06:34:44.408160Z
|
2020-12-10T23:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-c9f3-9wfr-wgh7', 'https://github.com/tensorflow/tensorflow/commit/ebc70b7a592420d3d2f359e4b1694c236b82c7ae'}
| null |
PyPI
|
PYSEC-2020-277
| null |
In Tensorflow before version 2.3.1, the `SparseCountSparseOutput` implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the `indices` tensor has rank 2. This tensor must be a matrix because code assumes its elements are accessed as elements of a matrix. However, malicious users can pass in tensors of different rank, resulting in a `CHECK` assertion failure and a crash. This can be used to cause denial of service in serving installations, if users are allowed to control the components of the input sparse tensor. The issue is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1.
|
{'CVE-2020-15197', 'GHSA-qc53-44cj-vfvx'}
|
2021-12-09T06:34:41.476873Z
|
2020-09-25T19:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1', 'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qc53-44cj-vfvx'}
| null |
PyPI
|
GHSA-22gh-3r9q-xf38
|
Lacking Protection against HTTP Request Smuggling in mitmproxy
|
### Impact
In mitmproxy 7.0.2 and below, a malicious client or server is able to perform [HTTP request smuggling](https://en.wikipedia.org/wiki/HTTP_request_smuggling) attacks through mitmproxy. This means that a malicious client/server could smuggle a request/response through mitmproxy as part of another request/response's HTTP message body. While mitmproxy would only see one request, the target server would see multiple requests. A smuggled request is still captured as part of another request's body, but it does not appear in the request list and does not go through the usual mitmproxy event hooks, where users may have implemented custom access control checks or input sanitization.
Unless you use mitmproxy to protect an HTTP/1 service, no action is required.
### Patches
The vulnerability has been fixed in mitmproxy 7.0.3 and above.
### Acknowledgements
We thank João Sobral (@chinchila) for responsibly disclosing this vulnerability to the mitmproxy team.
### Timeline
- **2021-09-08**: Received initial report for mitmproxy <= 6.0.2.
- **2021-09-08**: Requested clarification if 7.x is affected.
- **2021-09-10**: Received additional details, 7.x situation still unclear.
- **2021-09-13**: Internally determined that 7.x is also affected.
- **2021-09-13**: Shared initial fix with researcher.
- **2021-09-14**: Received confirmation that fix is working, but H2.TE/H2.CL should also be looked at.
- **2021-09-14**: Shared revised fix that includes additional H2.TE mitigations.
- **2021-09-14**: Received confirmation that revised fix is working.
- **2021-09-16**: Completed internal patch review.
- **2021-09-16**: Published patch release and advisory.
|
{'CVE-2021-39214'}
|
2022-03-03T05:13:51.641837Z
|
2021-09-20T19:53:30Z
|
HIGH
| null |
{'CWE-444'}
|
{'https://github.com/mitmproxy/mitmproxy/security/advisories/GHSA-22gh-3r9q-xf38', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39214', 'https://github.com/mitmproxy/mitmproxy'}
| null |
PyPI
|
GHSA-xgxc-v2qg-chmh
|
Directory Traversal in Django
|
In Django 2.2 before 2.2.20, 3.0 before 3.0.14, and 3.1 before 3.1.8, MultiPartParser allowed directory traversal via uploaded files with suitably crafted file names. Built-in upload handlers were not affected by this vulnerability.
|
{'CVE-2021-28658'}
|
2022-03-03T05:13:36.016810Z
|
2021-04-08T18:11:48Z
|
MODERATE
| null |
{'CWE-22'}
|
{'https://docs.djangoproject.com/en/3.1/releases/security/', 'https://www.djangoproject.com/weblog/2021/apr/06/security-releases/', 'https://groups.google.com/g/django-announce/c/ePr5j-ngdPU', 'https://pypi.org/project/Django/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28658', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZVKYPHR3TKR2ESWXBPOJEKRO2OSJRZUE/', 'https://security.netapp.com/advisory/ntap-20210528-0001/', 'https://lists.debian.org/debian-lts-announce/2021/04/msg00008.html'}
| null |
PyPI
|
PYSEC-2021-277
| null |
TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can trigger a read from outside of bounds of heap allocated data by sending invalid arguments to `tf.raw_ops.ResourceScatterUpdate`. The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L919-L923) has an incomplete validation of the relationship between the shapes of `indices` and `updates`: instead of checking that the shape of `indices` is a prefix of the shape of `updates` (so that broadcasting can happen), code only checks that the number of elements in these two tensors are in a divisibility relationship. We have patched the issue in GitHub commit 01cff3f986259d661103412a20745928c727326f. 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.
|
{'GHSA-7fvx-3jfc-2cpc', 'CVE-2021-37655'}
|
2021-08-27T03:22:44.439225Z
|
2021-08-12T21:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-7fvx-3jfc-2cpc', 'https://github.com/tensorflow/tensorflow/commit/01cff3f986259d661103412a20745928c727326f'}
| null |
PyPI
|
PYSEC-2021-68
| null |
An issue was discovered in NFStream 5.2.0. Because some allocated modules are not correctly freed, if the nfstream object is directly destroyed without being used after it is created, it will cause a memory leak that may result in a local denial of service (DoS).
|
{'CVE-2020-25340'}
|
2021-02-19T21:11:00Z
|
2021-02-16T15:15:00Z
| null | null | null |
{'https://github.com/ntop/nDPI/issues/994'}
| null |
PyPI
|
PYSEC-2021-627
| null |
TensorFlow is an open source platform for machine learning. In affected versions the shape inference code for `AllToAll` can be made to execute a division by 0. This occurs whenever the `split_count` argument is 0. 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.
|
{'CVE-2021-41218', 'GHSA-9crf-c6qr-r273'}
|
2021-12-09T06:35:10.125473Z
|
2021-11-05T22:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/commit/a8ad3e5e79c75f36edb81e0ba3f3c0c5442aeddc', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9crf-c6qr-r273'}
| null |
PyPI
|
PYSEC-2021-109
| null |
Django 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL injection if order_by is untrusted input from a client of a web application.
|
{'GHSA-xpfp-f569-q3p2', 'CVE-2021-35042'}
|
2021-07-08T03:14:19.151485Z
|
2021-07-02T10:15:00Z
| null | null | null |
{'https://groups.google.com/forum/#!forum/django-announce', 'https://docs.djangoproject.com/en/3.2/releases/security/', 'https://www.openwall.com/lists/oss-security/2021/07/02/2', 'https://github.com/advisories/GHSA-xpfp-f569-q3p2', 'https://www.djangoproject.com/weblog/2021/jul/01/security-releases/'}
| null |
PyPI
|
GHSA-x4qx-4fjv-hmw6
|
Integer overflow leading to crash in Tensorflow
|
### Impact
The [implementation of `SparseCountSparseOutput`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/count_ops.cc#L168-L273) can be made to crash a TensorFlow process by an integer overflow whose result is then used in a memory allocation:
```python
import tensorflow as tf
import numpy as np
tf.raw_ops.SparseCountSparseOutput(
indices=[[1,1]],
values=[2],
dense_shape=[2 ** 31, 2 ** 32],
weights=[1],
binary_output=True,
minlength=-1,
maxlength=-1,
name=None)
```
### Patches
We have patched the issue in GitHub commit [6f4d3e8139ec724dbbcb40505891c81dd1052c4a](https://github.com/tensorflow/tensorflow/commit/6f4d3e8139ec724dbbcb40505891c81dd1052c4a).
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Faysal Hossain Shezan from University of Virginia.
|
{'CVE-2022-21738'}
|
2022-03-03T05:13:56.550338Z
|
2022-02-09T23:45:09Z
|
MODERATE
| null |
{'CWE-190'}
|
{'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/count_ops.cc#L168-L273', 'https://github.com/tensorflow/tensorflow', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21738', 'https://github.com/tensorflow/tensorflow/commit/6f4d3e8139ec724dbbcb40505891c81dd1052c4a', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-x4qx-4fjv-hmw6'}
| null |
PyPI
|
PYSEC-2021-559
| null |
TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation of `tf.raw_ops.StringNGrams` is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/string_ngrams_op.cc#L184) calls `reserve` on a `tstring` with a value that sometimes can be negative if user supplies negative `ngram_widths`. The `reserve` method calls `TF_TString_Reserve` which has an `unsigned long` argument for the size of the buffer. Hence, the implicit conversion transforms the negative value to a large integer. We have patched the issue in GitHub commit c283e542a3f422420cfdb332414543b62fc4e4a5. 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.
|
{'CVE-2021-37646', 'GHSA-h6jh-7gv5-28vg'}
|
2021-12-09T06:35:02.920127Z
|
2021-08-12T21:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/commit/c283e542a3f422420cfdb332414543b62fc4e4a5', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6jh-7gv5-28vg'}
| null |
PyPI
|
GHSA-99cv-8cvv-666c
|
High severity vulnerability that affects apache-airflow
|
In Apache Airflow before 1.10.2, a malicious admin user could edit the state of objects in the Airflow metadata database to execute arbitrary javascript on certain page views.
|
{'CVE-2018-20244'}
|
2022-03-03T05:13:27.928344Z
|
2019-03-06T17:35:58Z
|
MODERATE
| null |
{'CWE-79'}
|
{'https://github.com/advisories/GHSA-99cv-8cvv-666c', 'https://lists.apache.org/thread.html/2de387213d45bc626d27554a1bde7b8c67d08720901f82a50b6f4231@%3Cdev.airflow.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2018-20244', 'http://www.openwall.com/lists/oss-security/2019/04/10/6', 'https://lists.apache.org/thread.html/f656fddf9c49293b3ec450437c46709eb01a12d1645136b2f1b8573b@%3Cdev.airflow.apache.org%3E'}
| null |
PyPI
|
PYSEC-2014-58
| null |
The WYSIWYG component (wysiwyg.py) in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allows remote attackers to obtain sensitive information via a crafted URL, which reveals the installation path in an error message.
|
{'CVE-2013-4194'}
|
2021-07-25T23:34:46.598296Z
|
2014-03-11T19:37:00Z
| null | null | null |
{'http://plone.org/products/plone-hotfix/releases/20130618', 'http://seclists.org/oss-sec/2013/q3/261', 'http://plone.org/products/plone/security/advisories/20130618-announcement', 'https://bugzilla.redhat.com/show_bug.cgi?id=978470'}
| null |
PyPI
|
GHSA-g4rf-pc26-6hmr
|
OMERO webclient does not validate URL redirects on login or switching group.
|
### Background
OMERO.web supports redirection to a given URL after performing login or switching the group context. These URLs are not validated, allowing redirection to untrusted sites. OMERO.web 5.9.0 adds URL validation before redirecting. External URLs are not considered valid, unless specified in the ``omero.web.redirect_allowed_hosts`` setting.
### Impact
OMERO.web before 5.9.0
### Patches
5.9.0
### Workarounds
No workaround
### References
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [omero-web](https://github.com/ome/omero-web)
* Email us at [security](mailto:security@openmicroscopy.org.uk)
|
{'CVE-2021-21377'}
|
2022-03-03T05:13:57.027034Z
|
2021-03-23T15:26:49Z
|
MODERATE
| null |
{'CWE-601'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-21377', 'https://github.com/ome/omero-web/security/advisories/GHSA-g4rf-pc26-6hmr', 'https://pypi.org/project/omero-web/', 'https://github.com/ome/omero-web/commit/952f8e5d28532fbb14fb665982211329d137908c', 'https://www.openmicroscopy.org/security/advisories/2021-SV2/', 'https://github.com/ome/omero-web/blob/master/CHANGELOG.md#590-march-2021'}
| null |
PyPI
|
PYSEC-2020-109
| null |
In some conditions, a snap package built by snapcraft includes the current directory in LD_LIBRARY_PATH, allowing a malicious snap to gain code execution within the context of another snap if both plug the home interface or similar. This issue affects snapcraft versions prior to 4.4.4, prior to 2.43.1+16.04.1, and prior to 2.43.1+18.04.1.
|
{'CVE-2020-27348'}
|
2020-12-14T20:36:00Z
|
2020-12-04T03:15:00Z
| null | null | null |
{'https://github.com/snapcore/snapcraft/pull/3345', 'https://bugs.launchpad.net/bugs/1901572', 'https://usn.ubuntu.com/usn/usn-4661-1'}
| null |
PyPI
|
PYSEC-2018-94
| null |
Live-migrated instances are briefly able to inspect traffic for other instances on the same hypervisor. This brief window could be extended indefinitely if the instance's port is set administratively down prior to live-migration and kept down after the migration is complete. This is possible due to the Open vSwitch integration bridge being connected to the instance during migration. When connected to the integration bridge, all traffic for instances using the same Open vSwitch instance would potentially be visible to the migrated guest, as the required Open vSwitch VLAN filters are only applied post-migration. Versions of openstack-neutron before 13.0.0.0b2, 12.0.3, 11.0.5 are vulnerable.
|
{'CVE-2018-14636'}
|
2021-08-27T03:22:08.615958Z
|
2018-09-10T19:29:00Z
| null | null | null |
{'https://bugs.launchpad.net/neutron/+bug/1734320', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-14636', 'https://bugs.launchpad.net/neutron/+bug/1767422'}
| null |
PyPI
|
PYSEC-2020-12
| null |
A flaw was found in Ansible Engine when using Ansible Vault for editing encrypted files. When a user executes "ansible-vault edit", another user on the same computer can read the old and new secret, as it is created in a temporary file with mkstemp and the returned file descriptor is closed and the method write_data is called to write the existing secret in the file. This method will delete the file before recreating it insecurely. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable.
|
{'GHSA-vcg8-98q8-g7mj', 'CVE-2020-1740'}
|
2020-06-13T04:15:00Z
|
2020-03-16T16:15:00Z
| null | null | null |
{'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WQVOQD4VAIXXTVQAJKTN7NUGTJFE2PCB/', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1740', 'https://lists.debian.org/debian-lts-announce/2020/05/msg00005.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MRRYUU5ZBLPBXCYG6CFP35D64NP2UB2S/', 'https://github.com/advisories/GHSA-vcg8-98q8-g7mj', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DKPA4KC3OJSUFASUYMG66HKJE7ADNGFW/', 'https://security.gentoo.org/glsa/202006-11', 'https://github.com/ansible/ansible/issues/67798'}
| null |
PyPI
|
PYSEC-2022-100
| null |
Tensorflow is an Open Source Machine Learning Framework. The `GraphDef` format in TensorFlow does not allow self recursive functions. The runtime assumes that this invariant is satisfied. However, a `GraphDef` containing a fragment such as the following can be consumed when loading a `SavedModel`. This would result in a stack overflow during execution as resolving each `NodeDef` means resolving the function itself and its nodes. 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.
|
{'CVE-2022-23591', 'GHSA-247x-2f9f-5wp7'}
|
2022-03-09T00:17:36.268189Z
|
2022-02-04T23:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-247x-2f9f-5wp7', 'https://github.com/tensorflow/tensorflow/commit/448a16182065bd08a202d9057dd8ca541e67996c'}
| null |
PyPI
|
GHSA-74xw-82v7-hmrm
|
Improper Input Validation in python-dbusmock
|
python-dbusmock before version 0.15.1 AddTemplate() D-Bus method call or DBusTestCase.spawn_server_template() method could be tricked into executing malicious code if an attacker supplies a .pyc file.
|
{'CVE-2015-1326'}
|
2022-03-03T05:13:12.559537Z
|
2019-04-23T16:04:36Z
|
HIGH
| null |
{'CWE-20'}
|
{'https://github.com/martinpitt/python-dbusmock/commit/4e7d0df9093', 'https://nvd.nist.gov/vuln/detail/CVE-2015-1326'}
| null |
PyPI
|
GHSA-33h2-69j3-r336
|
Out-of-bounds Read in OpenCV
|
OpenCV (Open Source Computer Vision Library) through 3.3 (corresponding to OpenCV-Python 3.3.0.9) has an out-of-bounds read error in the cv::RBaseStream::readBlock function in modules/imgcodecs/src/bitstrm.cpp when reading an image file by using cv::imread, as demonstrated by the 8-opencv-invalid-read-fread test case.
|
{'CVE-2017-12598'}
|
2022-03-03T05:12:57.714788Z
|
2021-10-12T22:00:51Z
|
HIGH
| null |
{'CWE-125'}
|
{'https://github.com/opencv/opencv-python/releases/tag/11', 'https://github.com/xiaoqx/pocs/blob/master/opencv.md', 'https://lists.debian.org/debian-lts-announce/2021/10/msg00028.html', 'https://github.com/opencv/opencv/issues/9309', 'https://lists.debian.org/debian-lts-announce/2018/07/msg00030.html', 'https://security.gentoo.org/glsa/201712-02', 'https://nvd.nist.gov/vuln/detail/CVE-2017-12598', 'https://github.com/opencv/opencv-python/releases/tag/9', 'https://github.com/opencv/opencv/pull/9376', 'https://github.com/opencv/opencv-python'}
| null |
PyPI
|
GHSA-h2g5-2rhx-ffgj
|
Command injection in Weblate
|
Weblate is a web based localization tool with tight version control integration. Prior to version 4.11.1, Weblate didn't properly sanitize some arguments passed to Git and Mercurial, allowing them to change their behavior in an unintended way. Instances where untrusted users cannot create new components are not affected. The issues were fixed in the 4.11.1 release.
|
{'CVE-2022-24727'}
|
2022-03-14T23:16:46.391080Z
|
2022-03-05T00:00:44Z
|
HIGH
| null |
{'CWE-77'}
|
{'https://github.com/WeblateOrg/weblate', 'https://github.com/WeblateOrg/weblate/commit/d83672a3e7415da1490334e2c9431e5da1966842', 'https://github.com/WeblateOrg/weblate/security/advisories/GHSA-3872-f48p-pxqj', 'https://github.com/WeblateOrg/weblate/commit/35d59f1f040541c358cece0a8d4a63183ca919b8', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24727'}
| null |
PyPI
|
PYSEC-2017-48
| null |
Openpyxl 2.4.1 resolves external entities by default, which allows remote attackers to conduct XXE attacks via a crafted .xlsx document.
|
{'CVE-2017-5992'}
|
2021-07-15T02:22:16.681254Z
|
2017-02-15T19:59:00Z
| null | null | null |
{'https://bitbucket.org/openpyxl/openpyxl/commits/3b4905f428e1', 'https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854442', 'https://bitbucket.org/openpyxl/openpyxl/issues/749', 'http://www.openwall.com/lists/oss-security/2017/02/07/5'}
| null |
PyPI
|
PYSEC-2021-735
| null |
TensorFlow is an end-to-end open source platform for machine learning. Incomplete validation in `SparseAdd` results in allowing attackers to exploit undefined behavior (dereferencing null pointers) as well as write outside of bounds of heap allocated data. The implementation(https://github.com/tensorflow/tensorflow/blob/656e7673b14acd7835dc778867f84916c6d1cac2/tensorflow/core/kernels/sparse_add_op.cc) has a large set of validation for the two sparse tensor inputs (6 tensors in total), but does not validate that the tensors are not empty or that the second dimension of `*_indices` matches the size of corresponding `*_shape`. This allows attackers to send tensor triples that represent invalid sparse tensors to abuse code assumptions that are not protected by validation. 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.
|
{'GHSA-cjc7-49v2-jp64', 'CVE-2021-29609'}
|
2021-12-09T06:35:33.559422Z
|
2021-05-14T20:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/commit/41727ff06111117bdf86b37db198217fd7a143cc', 'https://github.com/tensorflow/tensorflow/commit/6fd02f44810754ae7481838b6a67c5df7f909ca3', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cjc7-49v2-jp64'}
| null |
PyPI
|
PYSEC-2021-365
| null |
Vyper is a Pythonic Smart Contract Language for the EVM. In affected versions when performing a function call inside a literal struct, there is a memory corruption issue that occurs because of an incorrect pointer to the the top of the stack. This issue has been resolved in version 0.3.0.
|
{'CVE-2021-41121', 'GHSA-xv8x-pr4h-73jv'}
|
2021-10-11T01:16:43.176882Z
|
2021-10-06T18:15:00Z
| null | null | null |
{'https://github.com/vyperlang/vyper/security/advisories/GHSA-xv8x-pr4h-73jv', 'https://github.com/vyperlang/vyper/pull/2447'}
| null |
PyPI
|
PYSEC-2021-670
| null |
TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.QuantizeAndDequantizeV4Grad`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L162-L163) does not validate the rank of the `input_*` tensors. In turn, this results in the tensors being passes as they are to `QuantizeAndDequantizePerChannelGradientImpl`(https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.h#L295-L306). However, the `vec<T>` method, requires the rank to 1 and triggers a `CHECK` failure otherwise. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 as this is the only other affected version.
|
{'CVE-2021-29544', 'GHSA-6g85-3hm8-83f9'}
|
2021-12-09T06:35:22.335925Z
|
2021-05-14T20:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-6g85-3hm8-83f9', 'https://github.com/tensorflow/tensorflow/commit/20431e9044cf2ad3c0323c34888b192f3289af6b'}
| null |
PyPI
|
GHSA-gpvv-69j7-gwj8
|
Path Traversal in pip
|
The pip package before 19.2 for Python allows Directory Traversal when a URL is given in an install command, because a Content-Disposition header can have ../ in a filename, as demonstrated by overwriting the /root/.ssh/authorized_keys file. This occurs in _download_http_url in _internal/download.py. A fix was committed 6704f2ace.
|
{'CVE-2019-20916'}
|
2022-04-21T15:46:57.757453Z
|
2021-06-09T17:35:04Z
|
HIGH
| null |
{'CWE-22'}
|
{'https://github.com/pypa/pip/issues/6413', 'https://lists.debian.org/debian-lts-announce/2020/09/msg00010.html', 'https://github.com/gzpan123/pip/commit/a4c735b14a62f9cb864533808ac63936704f2ace', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00010.html', 'https://nvd.nist.gov/vuln/detail/CVE-2019-20916', 'https://github.com/pypa/pip/', 'https://github.com/pypa/pip/compare/19.1.1...19.2', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00005.html'}
| null |
PyPI
|
PYSEC-2021-220
| null |
TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.raw_ops.FusedBatchNorm` is vulnerable to a heap buffer overflow. If the tensors are empty, the same implementation can trigger undefined behavior by dereferencing null pointers. The implementation(https://github.com/tensorflow/tensorflow/blob/57d86e0db5d1365f19adcce848dfc1bf89fdd4c7/tensorflow/core/kernels/fused_batch_norm_op.cc) fails to validate that `scale`, `offset`, `mean` and `variance` (the last two only when required) all have the same number of elements as the number of channels of `x`. This results in heap out of bounds reads when the buffers backing these tensors are indexed past their boundary. If the tensors are empty, the validation mentioned in the above paragraph would also trigger and prevent the undefined behavior. 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.
|
{'GHSA-9xh4-23q4-v6wr', 'CVE-2021-29583'}
|
2021-08-27T03:22:36.144215Z
|
2021-05-14T20:15:00Z
| null | null | null |
{'https://github.com/tensorflow/tensorflow/commit/6972f9dfe325636b3db4e0bc517ee22a159365c0', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9xh4-23q4-v6wr'}
| null |
PyPI
|
PYSEC-2020-220
| null |
A flaw was found in Ansible Base when using the aws_ssm connection plugin as garbage collector is not happening after playbook run is completed. Files would remain in the bucket exposing the data. This issue affects directly data confidentiality.
|
{'CVE-2020-25635'}
|
2022-05-04T22:49:27.670722Z
|
2020-10-05T14:15:00Z
| null | null | null |
{'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-25635', 'https://github.com/ansible-collections/community.aws/issues/222'}
| null |
RubyGems
|
GHSA-wg6j-r28m-7293
|
Code Injection in simple_captcha2
|
The simple_captcha2 gem 0.2.3 for Ruby, as distributed on RubyGems.org, included a code-execution backdoor inserted by a third party.
|
{'CVE-2019-14282'}
|
2021-08-17T20:23:37Z
|
2019-07-31T04:21:19Z
|
CRITICAL
| null |
{'CWE-94'}
|
{'https://github.com/rubygems/rubygems.org/issues/2073', 'https://rubygems.org/gems/simple_captcha2/versions/', 'https://nvd.nist.gov/vuln/detail/CVE-2019-14282'}
| null |
RubyGems
|
GHSA-p6p8-q4pj-f74m
|
Improper Certificate Validation in twitter-stream
|
In voloko twitter-stream 0.1.16, missing TLS hostname validation allows an attacker to perform a man-in-the-middle attack against users of the library (because eventmachine is misused).
|
{'CVE-2020-24392'}
|
2022-03-03T05:12:43.672458Z
|
2021-03-29T16:28:42Z
|
MODERATE
| null |
{'CWE-295'}
|
{'https://securitylab.github.com/advisories/GHSL-2020-097-voloko-twitter-stream', 'https://nvd.nist.gov/vuln/detail/CVE-2020-24392', 'https://github.com/voloko/twitter-stream'}
| null |
RubyGems
|
GHSA-46f2-3v63-3xrp
|
Path traversal in Tempfile on Windows
|
There is an unintentional directory creation vulnerability in `tmpdir` library bundled with Ruby on Windows. And there is also an unintentional file creation vulnerability in tempfile library bundled with Ruby on Windows, because it uses tmpdir internally.
|
{'CVE-2021-28966'}
|
2022-03-03T05:13:55.780986Z
|
2021-05-06T15:01:36Z
|
MODERATE
| null |
{'CWE-22'}
|
{'https://github.com/ruby/tmpdir/pull/8', 'https://security.netapp.com/advisory/ntap-20210902-0004/', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/tmpdir/CVE-2021-28966.yml', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28966', 'https://www.ruby-lang.org/en/news/2021/04/05/tempfile-path-traversal-on-windows-cve-2021-28966/', 'https://github.com/ruby/tmpdir/commit/93798c01cb7c10476e50a4d80130a329ba47f348', 'https://hackerone.com/reports/1131465', 'https://rubygems.org/gems/tmpdir', 'https://github.com/ruby/tmpdir'}
| null |
RubyGems
|
GHSA-2w67-526p-gm73
|
redis-store deserializes untrusted data the affected version range and description should be adjust to match as well
|
Redis-store <=v1.3.0 allows unsafe objects to be loaded from redis
|
{'CVE-2017-1000248'}
|
2022-04-25T22:16:55.481411Z
|
2017-12-06T16:41:25Z
|
CRITICAL
| null |
{'CWE-502'}
|
{'https://github.com/advisories/GHSA-2w67-526p-gm73', 'https://nvd.nist.gov/vuln/detail/CVE-2017-1000248', 'https://github.com/redis-store/redis-store/commit/e0c1398d54a9661c8c70267c3a925ba6b192142e', 'https://github.com/redis-store/redis-store'}
| null |
RubyGems
|
GHSA-vxf6-w9mp-95hm
|
Low severity vulnerability that affects puppet
|
lib/puppet/network/authstore.rb in Puppet before 2.7.18, and Puppet Enterprise before 2.5.2, supports use of IP addresses in certnames without warning of potential risks, which might allow remote attackers to spoof an agent by acquiring a previously used IP address.
|
{'CVE-2012-3408'}
|
2022-03-03T05:14:03.717923Z
|
2017-10-24T18:33:38Z
|
LOW
| null |
{'CWE-287'}
|
{'http://puppetlabs.com/security/cve/cve-2012-3408/', 'https://github.com/puppetlabs/puppet/commit/ab9150baa1b738467a33b01df1d90e076253fbbd', 'https://nvd.nist.gov/vuln/detail/CVE-2012-3408', 'https://bugzilla.redhat.com/show_bug.cgi?id=839166', 'https://github.com/puppetlabs/puppet', 'https://github.com/advisories/GHSA-vxf6-w9mp-95hm'}
| null |
RubyGems
|
GHSA-hxx6-p24v-wg8c
|
High severity vulnerability that affects curl
|
lib/curl.rb in the Curl Gem for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a URL.
|
{'CVE-2013-2617'}
|
2022-03-03T05:14:05.200557Z
|
2017-10-24T18:33:37Z
|
HIGH
| null |
{'CWE-94'}
|
{'https://github.com/advisories/GHSA-hxx6-p24v-wg8c', 'http://seclists.org/fulldisclosure/2013/Mar/124', 'http://www.osvdb.org/91230', 'https://nvd.nist.gov/vuln/detail/CVE-2013-2617', 'http://www.openwall.com/lists/oss-security/2013/03/19/9', 'http://packetstormsecurity.com/files/120778/Ruby-Gem-Curl-Command-Execution.html'}
| null |
RubyGems
|
GHSA-qh4w-7pw3-p4rp
|
Potential denial of service in bson rubygem
|
The Moped::BSON::ObjecId.legal? method in mongodb/bson-ruby before 3.0.4 as used in rubygem-moped allows remote attackers to cause a denial of service (worker resource consumption) via a crafted string. NOTE: This issue is due to an incomplete fix to CVE-2015-4410.
|
{'CVE-2015-4411'}
|
2022-03-03T05:13:31.309816Z
|
2020-04-29T15:34:50Z
|
HIGH
| null |
{'CWE-400'}
|
{'https://homakov.blogspot.ru/2012/05/saferweb-injects-in-various-ruby.html', 'https://github.com/mongodb/bson-ruby/commit/fef6f75413511d653c76bf924a932374a183a24f#diff-8c8558c185bbb548ccb5a6d6ac4bfee5R191', 'https://nvd.nist.gov/vuln/detail/CVE-2015-4411', 'https://bugzilla.redhat.com/show_bug.cgi?id=1229706', 'https://sakurity.com/blog/2015/06/04/mongo_ruby_regexp.html', 'http://lists.fedoraproject.org/pipermail/package-announce/2015-July/161964.html', 'https://github.com/mongodb/bson-ruby/compare/7446d7c6764dfda8dc4480ce16d5c023e74be5ca...28f34978a85b689a4480b4d343389bf4886522e7', 'https://www.securityfocus.com/bid/75045', 'https://github.com/mongodb/bson-ruby', 'https://seclists.org/oss-sec/2015/q2/653', 'https://security-tracker.debian.org/tracker/CVE-2015-4411', 'http://www.openwall.com/lists/oss-security/2015/06/06/3', 'https://github.com/mongoid/moped/commit/dd5a7c14b5d2e466f7875d079af71ad19774609b#diff-3b93602f64c2fe46d38efd9f73ef5358R24', 'http://lists.fedoraproject.org/pipermail/package-announce/2015-July/161987.html', 'https://github.com/mongodb/bson-ruby/commit/976da329ff03ecdfca3030eb6efe3c85e6db9999', 'http://www.securityfocus.com/bid/75045'}
| null |
RubyGems
|
GHSA-q7wx-62r7-j2x7
|
Moderate severity vulnerability that affects nokogiri
|
The xmlreader in libxml allows remote attackers to cause a denial of service (memory consumption) via crafted XML data, related to an XML Entity Expansion (XEE) attack.
|
{'CVE-2015-1819'}
|
2022-03-03T05:14:08.002216Z
|
2018-08-08T22:31:12Z
|
MODERATE
| null | null |
{'https://github.com/advisories/GHSA-q7wx-62r7-j2x7', 'http://lists.opensuse.org/opensuse-updates/2016-01/msg00031.html', 'https://support.apple.com/HT206166', 'http://www.debian.org/security/2015/dsa-3430', 'http://lists.apple.com/archives/security-announce/2016/Mar/msg00002.html', 'http://lists.fedoraproject.org/pipermail/package-announce/2015-November/172710.html', 'https://nvd.nist.gov/vuln/detail/CVE-2015-1819', 'http://lists.apple.com/archives/security-announce/2016/Mar/msg00004.html', 'http://xmlsoft.org/news.html', 'http://lists.apple.com/archives/security-announce/2016/Mar/msg00001.html', 'https://support.apple.com/HT206167', 'http://www.ubuntu.com/usn/USN-2812-1', 'https://support.apple.com/HT206169', 'http://www.securitytracker.com/id/1034243', 'https://support.apple.com/HT206168', 'http://lists.fedoraproject.org/pipermail/package-announce/2015-November/172943.html', 'http://lists.opensuse.org/opensuse-updates/2015-12/msg00120.html', 'https://git.gnome.org/browse/libxml2/commit/?id=213f1fe0d76d30eaed6e5853057defc43e6df2c9', 'http://www.oracle.com/technetwork/topics/security/bulletinoct2015-2511968.html', 'http://www.securityfocus.com/bid/75570', 'http://www.oracle.com/technetwork/topics/security/linuxbulletinoct2015-2719645.html', 'https://security.gentoo.org/glsa/201507-08', 'https://security.gentoo.org/glsa/201701-37', 'http://rhn.redhat.com/errata/RHSA-2015-1419.html', 'http://rhn.redhat.com/errata/RHSA-2015-2550.html', 'http://lists.apple.com/archives/security-announce/2016/Mar/msg00000.html'}
| null |
RubyGems
|
GHSA-g6wq-qcwm-j5g2
|
Regular Expression Denial of Service in websocket-extensions (RubyGem)
|
### Impact
The ReDoS flaw allows an attacker to exhaust the server's capacity to process
incoming requests by sending a WebSocket handshake request containing a header
of the following form:
Sec-WebSocket-Extensions: a; b="\c\c\c\c\c\c\c\c\c\c ...
That is, a header containing an unclosed string parameter value whose content is
a repeating two-byte sequence of a backslash and some other character. The
parser takes exponential time to reject this header as invalid, and this will
block the processing of any other work on the same thread. Thus if you are
running a single-threaded server, such a request can render your service
completely unavailable.
### Patches
Users should upgrade to version 0.1.5.
### Workarounds
There are no known work-arounds other than disabling any public-facing
WebSocket functionality you are operating.
### References
- https://blog.jcoglan.com/2020/06/02/redos-vulnerability-in-websocket-extensions/
|
{'CVE-2020-7663'}
|
2022-03-03T05:13:04.470258Z
|
2020-06-05T14:21:29Z
|
HIGH
| null |
{'CWE-400'}
|
{'https://usn.ubuntu.com/4502-1/', 'https://github.com/faye/websocket-extensions-ruby', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7663', 'https://github.com/faye/websocket-extensions-ruby/security/advisories/GHSA-g6wq-qcwm-j5g2', 'https://github.com/faye/websocket-extensions-ruby/commit/aa156a439da681361ed6f53f1a8131892418838b', 'https://blog.jcoglan.com/2020/06/02/redos-vulnerability-in-websocket-extensions', 'https://lists.debian.org/debian-lts-announce/2020/08/msg00031.html', 'https://snyk.io/vuln/SNYK-RUBY-WEBSOCKETEXTENSIONS-570830'}
| null |
RubyGems
|
GHSA-m7p8-9w66-9frm
|
Moderate severity vulnerability that affects net-ldap
|
The Net::LDAP (aka net-ldap) gem before 0.16.0 for Ruby has Missing SSL Certificate Validation.
|
{'CVE-2017-17718'}
|
2022-03-03T05:13:54.644589Z
|
2018-01-06T01:11:34Z
|
MODERATE
| null |
{'CWE-295'}
|
{'https://github.com/ruby-ldap/ruby-net-ldap/issues/258', 'https://github.com/ruby-ldap/ruby-net-ldap/pull/279', 'http://openwall.com/lists/oss-security/2017/12/17/10', 'https://nvd.nist.gov/vuln/detail/CVE-2017-17718', 'https://github.com/advisories/GHSA-m7p8-9w66-9frm', 'https://github.com/ruby-ldap/ruby-net-ldap'}
| null |
RubyGems
|
GHSA-2j55-pcw5-x4h2
|
Critical severity vulnerability that affects active-support
|
The `active-support` ruby gem gem is malware and duplicates the official `activesupport` (no hyphen) gem, but adds a compiled extension. The extension attempts to resolve a base64 encoded domain (29faea63.planfhntage.de), downloads a payload, and executes.
This trojan horse gem could allow a remote attacker to execute arbitrary code on the system, caused by containing a malicious backdoor. An attacker could exploit this vulnerability to execute arbitrary code on the system. No version of this gem should be considered safe.
|
{'CVE-2018-3779'}
|
2021-01-08T20:07:49Z
|
2018-08-13T15:02:49Z
|
CRITICAL
| null |
{'CWE-77'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2018-3779', 'https://hackerone.com/reports/392311', 'https://github.com/advisories/GHSA-2j55-pcw5-x4h2'}
| null |
RubyGems
|
GHSA-xrr4-p6fq-hjg7
|
Directory traversal vulnerability in Action View in Ruby on Rails
|
Directory traversal vulnerability in Action View in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 allows remote attackers to read arbitrary files by leveraging an application's unrestricted use of the render method and providing a .. (dot dot) in a pathname.
|
{'CVE-2016-0752'}
|
2022-04-25T20:46:59.469264Z
|
2017-10-24T18:33:35Z
|
HIGH
| null |
{'CWE-22'}
|
{'https://www.exploit-db.com/exploits/40561/', 'http://rhn.redhat.com/errata/RHSA-2016-0296.html', 'http://www.openwall.com/lists/oss-security/2016/01/25/13', 'http://lists.opensuse.org/opensuse-updates/2016-02/msg00034.html', 'http://lists.opensuse.org/opensuse-updates/2016-02/msg00043.html', 'http://www.securityfocus.com/bid/81801', 'http://www.securitytracker.com/id/1034816', 'http://www.debian.org/security/2016/dsa-3464', 'https://github.com/advisories/GHSA-xrr4-p6fq-hjg7', 'http://lists.fedoraproject.org/pipermail/package-announce/2016-February/178069.html', 'https://groups.google.com/forum/message/raw?msg=ruby-security-ann/335P1DcLG00/JXcBnTtZEgAJ', 'https://nvd.nist.gov/vuln/detail/CVE-2016-0752', 'http://lists.fedoraproject.org/pipermail/package-announce/2016-February/178044.html', 'http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00053.html'}
| null |
RubyGems
|
GHSA-fqfj-cmh6-hj49
|
Ruby OpenID
|
Ruby OpenID (aka ruby-openid) through 2.8.0 has a remotely exploitable flaw. This library is used by Rails web applications to integrate with OpenID Providers. Severity can range from medium to critical, depending on how a web application developer chose to employ the ruby-openid library. Developers who based their OpenID integration heavily on the "example app" provided by the project are at highest risk.
|
{'CVE-2019-11027'}
|
2022-03-03T05:13:23.175758Z
|
2019-06-13T16:15:56Z
|
CRITICAL
| null |
{'CWE-918'}
|
{'https://marc.info/?l=openid-security&m=155154717027534&w=2', 'https://lists.debian.org/debian-lts-announce/2019/10/msg00014.html', 'https://github.com/openid/ruby-openid/issues/122', 'https://security.gentoo.org/glsa/202003-09', 'https://nvd.nist.gov/vuln/detail/CVE-2019-11027'}
| null |
RubyGems
|
GHSA-gcqq-w6gr-h9j9
|
Directory traversal vulnerability in RubyZip
|
The Zip::File component in the rubyzip gem before 1.2.1 for Ruby has a directory traversal vulnerability. If a site allows uploading of .zip files, an attacker can upload a malicious file that uses "../" pathname substrings to write arbitrary files to the filesystem.
|
{'CVE-2017-5946'}
|
2022-04-25T16:47:10.179089Z
|
2017-10-24T18:33:35Z
|
CRITICAL
| null |
{'CWE-22'}
|
{'http://www.debian.org/security/2017/dsa-3801', 'https://nvd.nist.gov/vuln/detail/CVE-2017-5946', 'https://github.com/rubyzip/rubyzip/releases', 'https://github.com/rubyzip/rubyzip', 'http://www.securityfocus.com/bid/96445', 'https://github.com/rubyzip/rubyzip/issues/315', 'https://github.com/advisories/GHSA-gcqq-w6gr-h9j9'}
| null |
RubyGems
|
GHSA-6j63-35hj-vmcg
|
Moderate severity vulnerability that affects mysql-binuuid-rails
|
mysql-binuuid-rails 1.1.0 and earlier allows SQL Injection because it removes default string escaping for affected database columns.
|
{'CVE-2018-18476'}
|
2022-03-03T05:14:03.497530Z
|
2018-10-30T20:34:06Z
|
CRITICAL
| null |
{'CWE-89'}
|
{'https://gist.github.com/viraptor/881276ea61e8d56bac6e28454c79f1e6', 'https://github.com/nedap/mysql-binuuid-rails/pull/18', 'https://github.com/nedap/mysql-binuuid-rails', 'https://nvd.nist.gov/vuln/detail/CVE-2018-18476', 'https://github.com/advisories/GHSA-6j63-35hj-vmcg'}
| null |
RubyGems
|
GHSA-qrqm-fpv6-6r8g
|
Command Injection Vulnerability in Mechanize
|
This security advisory has been created for public disclosure of a Command Injection vulnerability that was responsibly reported by @kyoshidajp (Katsuhiko YOSHIDA).
### Impact
Mechanize `>= v2.0`, `< v2.7.7` allows for OS commands to be injected using several classes' methods which implicitly use Ruby's `Kernel.open` method. Exploitation is possible only if untrusted input is used as a local filename and passed to any of these calls:
- `Mechanize::CookieJar#load`: since v2.0 (see 208e3ed)
- `Mechanize::CookieJar#save_as`: since v2.0 (see 5b776a4)
- `Mechanize#download`: since v2.2 (see dc91667)
- `Mechanize::Download#save` and `#save!` since v2.1 (see 98b2f51, bd62ff0)
- `Mechanize::File#save` and `#save_as`: since v2.1 (see 2bf7519)
- `Mechanize::FileResponse#read_body`: since v2.0 (see 01039f5)
### Patches
These vulnerabilities are patched in Mechanize v2.7.7.
### Workarounds
No workarounds are available. We recommend upgrading to v2.7.7 or later.
### References
See https://docs.rubocop.org/rubocop/cops_security.html#securityopen for background on why `Kernel.open` should not be used with untrusted input.
### For more information
If you have any questions or comments about this advisory, please open an issue in [sparklemotion/mechanize](https://github.com/sparklemotion/mechanize/issues/new).
|
{'CVE-2021-21289'}
|
2022-04-27T20:31:57.937283Z
|
2021-02-02T18:50:27Z
|
HIGH
| null |
{'CWE-78'}
|
{'https://github.com/sparklemotion/mechanize/security/advisories/GHSA-qrqm-fpv6-6r8g', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LBVVJUL4P4KCJH4IQTHFZ4ATXY7XXZPV/', 'https://rubygems.org/gems/mechanize/', 'https://github.com/sparklemotion/mechanize/releases/tag/v2.7.7', 'https://security.gentoo.org/glsa/202107-17', 'https://github.com/sparklemotion/mechanize', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YNFZ7ROYS6V4J5L5PRAJUG2AWC7VXR2V/', 'https://lists.debian.org/debian-lts-announce/2021/02/msg00021.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21289', 'https://github.com/sparklemotion/mechanize/commit/66a6a1bfa653a5f13274a396a5e5441238656aa0'}
| null |
RubyGems
|
GHSA-52p9-v744-mwjj
|
Remote code execution in Kramdown
|
Kramdown before 2.3.1 does not restrict Rouge formatters to the Rouge::Formatters namespace, and thus arbitrary classes can be instantiated.
|
{'CVE-2021-28834'}
|
2022-03-03T05:13:10.234883Z
|
2021-03-29T16:30:34Z
|
HIGH
| null |
{'CWE-94'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-28834', 'https://gitlab.com/gitlab-org/gitlab/-/commit/179329b5c3c118924fb242dc449d06b4ed6ccb66', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SYOLQKFL6IJCQLBXV34Z4TI4O54GESPR/', 'https://github.com/stanhu/kramdown/commit/d6a1cbcb2caa2f8a70927f176070d126b2422760', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S3BBLUIDCUUR3NEE4NJLOCCAV3ALQ3O6/', 'https://github.com/gettalong/kramdown/pull/708', 'https://github.com/stanhu/kramdown/commit/ff0218aefcf00cd5a389e17e075d36cd46d011e2', 'https://www.debian.org/security/2021/dsa-4890', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NJCJVYHPY6LNUFM6LYZIAUIYOMVT5QGV/', 'https://github.com/gettalong/kramdown/compare/REL_2_3_0...REL_2_3_1', 'https://about.gitlab.com/releases/2021/03/17/security-release-gitlab-13-9-4-released/#remote-code-execution-via-unsafe-user-controlled-markdown-rendering-options'}
| null |
RubyGems
|
GHSA-m6f7-46hw-grcj
|
Critical severity vulnerability that affects cremefraiche
|
The set_meta_data function in lib/cremefraiche.rb in the Creme Fraiche gem before 0.6.1 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in the file name of an email attachment. NOTE: some of these details are obtained from third party information.
|
{'CVE-2013-2090'}
|
2020-06-16T21:45:09Z
|
2017-10-24T18:33:37Z
|
CRITICAL
| null |
{'CWE-78'}
|
{'https://github.com/advisories/GHSA-m6f7-46hw-grcj', 'http://www.vapid.dhs.org/advisories/cremefraiche-cmd-inj.html', 'http://packetstormsecurity.com/files/121635/Ruby-Gem-Creme-Fraiche-0.6-Command-Injection.html', 'http://secunia.com/advisories/53391', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/84271', 'https://nvd.nist.gov/vuln/detail/CVE-2013-2090', 'http://osvdb.org/93395'}
| null |
RubyGems
|
GHSA-rp63-jfmw-532w
|
High severity vulnerability that affects mail
|
The Mail gem before 2.4.3 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a (1) sendmail or (2) exim delivery.
|
{'CVE-2012-2140'}
|
2022-03-03T05:13:28.878669Z
|
2017-10-24T18:33:38Z
|
HIGH
| null |
{'CWE-20'}
|
{'https://github.com/advisories/GHSA-rp63-jfmw-532w', 'https://github.com/mikel/mail', 'https://github.com/mikel/mail/commit/ac56f03bdfc30b379aeecd4ff317d08fdaa328c2', 'http://lists.fedoraproject.org/pipermail/package-announce/2012-May/080648.html', 'http://secunia.com/advisories/48970', 'https://bugzilla.redhat.com/show_bug.cgi?id=816352', 'https://github.com/mikel/mail/blob/9beb079c70d236a5ad2e1ba95b2c977e55deb7af/CHANGELOG.rdoc', 'http://lists.fedoraproject.org/pipermail/package-announce/2012-May/080747.html', 'https://nvd.nist.gov/vuln/detail/CVE-2012-2140', 'http://www.openwall.com/lists/oss-security/2012/04/26/1', 'http://www.openwall.com/lists/oss-security/2012/04/25/8', 'https://bugzilla.novell.com/show_bug.cgi?id=759092', 'http://lists.fedoraproject.org/pipermail/package-announce/2012-May/080645.html', 'https://github.com/mikel/mail/commit/39b590ddb08f90ddbe445837359a2c8843e533d0'}
| null |
RubyGems
|
GHSA-99ch-8mvp-g7m5
|
Critical severity vulnerability that affects md2pdf
|
converter.rb in the md2pdf gem 0.0.1 for Ruby allows context-dependent attackers to execute arbitrary commands via shell metacharacters in a filename.
|
{'CVE-2013-1948'}
|
2022-03-03T05:13:03.218446Z
|
2017-10-24T18:33:37Z
|
CRITICAL
| null | null |
{'https://nvd.nist.gov/vuln/detail/CVE-2013-1948', 'https://github.com/advisories/GHSA-99ch-8mvp-g7m5', 'http://www.securityfocus.com/bid/59061', 'http://osvdb.org/92290', 'https://github.com/rwestgeest/md2pdf', 'http://vapid.dhs.org/advisories/md2pdf-remote-exec.html', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/83416'}
| null |
RubyGems
|
GHSA-f2rp-4rv7-fc95
|
Exposure of Sensitive Information to an Unauthorized Actor in foreman_fog_proxmox
|
A flaw was found in the Foreman project. The Proxmox compute resource exposes the password through the API to an authenticated local attacker with view_hosts permission. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. Versions before foreman_fog_proxmox 0.13.1 are affected
|
{'CVE-2021-20259'}
|
2022-03-03T05:12:50.674375Z
|
2021-06-10T15:54:43Z
|
HIGH
| null |
{'CWE-200'}
|
{'https://bugzilla.redhat.com/show_bug.cgi?id=1932144', 'https://github.com/theforeman/foreman_fog_proxmox/releases/tag/v0.13.1', 'https://github.com/theforeman/foreman_fog_proxmox/pull/184/commits/b7e910bf61563f5d447c71b1b41e2a373a794d7b', 'https://nvd.nist.gov/vuln/detail/CVE-2021-20259'}
| null |
RubyGems
|
GHSA-c92m-rrrc-q5wf
|
High severity vulnerability that affects safemode
|
The Safemode gem before 1.2.4 for Ruby, when initialized with a delegate object that is a Rails controller, allows context-dependent attackers to obtain sensitive information via the inspect method.
|
{'CVE-2016-3693'}
|
2022-03-03T05:14:04.550026Z
|
2017-10-24T18:33:35Z
|
HIGH
| null |
{'CWE-200'}
|
{'https://github.com/theforeman/foreman/commit/82f9b93c54f72c5814df6bab7fad057eab65b2f2', 'http://rubysec.com/advisories/CVE-2016-3693/', 'https://github.com/advisories/GHSA-c92m-rrrc-q5wf', 'http://theforeman.org/security.html#2016-3693', 'http://www.openwall.com/lists/oss-security/2016/04/20/8', 'http://projects.theforeman.org/issues/14635', 'https://access.redhat.com/errata/RHSA-2018:0336', 'https://nvd.nist.gov/vuln/detail/CVE-2016-3693', 'https://github.com/svenfuchs/safemode/commit/0f764a1720a3a68fd2842e21377c8bfad6d7126f', 'https://github.com/svenfuchs/safemode'}
| null |
RubyGems
|
GHSA-x3v4-pxvm-63j8
|
HTTP Request Smuggling in reel
|
reel through 0.6.1 allows Request Smuggling attacks due to incorrect Content-Length and Transfer encoding header parsing. It is possible to conduct HTTP request smuggling attacks by sending the Content-Length header twice. Furthermore, invalid Transfer Encoding headers were found to be parsed as valid which could be leveraged for TECL smuggling attacks. Note, This project is deprecated, and is not maintained any more.
|
{'CVE-2020-7659'}
|
2022-03-03T05:13:58.550872Z
|
2021-05-24T18:13:36Z
|
MODERATE
| null |
{'CWE-444'}
|
{'https://snyk.io/vuln/SNYK-RUBY-REEL-569135', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7659'}
| null |
RubyGems
|
GHSA-6x45-86q6-rcmr
|
Gyazo allows local users to write arbitrary files
|
lib/gyazo/client.rb in the gyazo gem 1.0.0 for Ruby allows local users to write to arbitrary files via a symlink attack on a temporary file, related to time-based filenames.
|
{'CVE-2014-4994'}
|
2022-04-25T22:11:07Z
|
2018-01-22T23:17:39Z
|
MODERATE
| null |
{'CWE-20'}
|
{'http://www.vapid.dhs.org/advisories/gyazo-1.0.0.html', 'http://www.openwall.com/lists/oss-security/2014/07/07/13', 'https://github.com/advisories/GHSA-6x45-86q6-rcmr', 'https://nvd.nist.gov/vuln/detail/CVE-2014-4994', 'http://www.openwall.com/lists/oss-security/2014/07/17/5'}
| null |
RubyGems
|
GHSA-hxhj-hp9m-qwc4
|
Moderate severity vulnerability that affects private_address_check
|
The private_address_check ruby gem before 0.4.0 is vulnerable to a bypass due to use of Ruby's Resolv.getaddresses method, which is OS-dependent and should not be relied upon for security measures, such as when used to blacklist private network addresses to prevent server-side request forgery.
|
{'CVE-2017-0904'}
|
2022-03-03T05:14:08.022941Z
|
2017-11-29T23:21:05Z
|
MODERATE
| null |
{'CWE-242'}
|
{'https://github.com/advisories/GHSA-hxhj-hp9m-qwc4', 'https://edoverflow.com/2017/ruby-resolv-bug/', 'https://github.com/jtdowney/private_address_check/commit/58a0d7fe31de339c0117160567a5b33ad82b46af', 'https://hackerone.com/reports/287835', 'https://hackerone.com/reports/287245', 'https://github.com/jtdowney/private_address_check/issues/1', 'https://nvd.nist.gov/vuln/detail/CVE-2017-0904'}
| null |
RubyGems
|
GHSA-qpxp-5j56-gg3x
|
Improper Input Validation in Zendesk Samlr
|
Zendesk Samlr before 2.6.2 allows an XML nodes comment attack such as a name_id node with user@example.com followed by <!---->. and then the attacker's domain name.
|
{'CVE-2018-20857'}
|
2022-03-03T05:14:21.824668Z
|
2019-07-31T04:22:03Z
|
HIGH
| null |
{'CWE-20'}
|
{'https://github.com/zendesk/samlr/compare/v2.6.1...v2.6.2', 'https://nvd.nist.gov/vuln/detail/CVE-2018-20857'}
| null |
RubyGems
|
GHSA-3crr-9vmg-864v
|
Moderate severity vulnerability that affects activerecord
|
The Active Record component in Ruby on Rails 2.3.x before 2.3.18, 3.1.x before 3.1.12, and 3.2.x before 3.2.13 processes certain queries by converting hash keys to symbols, which allows remote attackers to cause a denial of service via crafted input to a where method.
|
{'CVE-2013-1854'}
|
2022-03-03T05:11:55.125829Z
|
2017-10-24T18:33:37Z
|
MODERATE
| null |
{'CWE-20'}
|
{'http://support.apple.com/kb/HT5784', 'http://lists.opensuse.org/opensuse-updates/2013-04/msg00078.html', 'http://weblog.rubyonrails.org/2013/3/18/SEC-ANN-Rails-3-2-13-3-1-12-and-2-3-18-have-been-released/', 'http://lists.opensuse.org/opensuse-updates/2013-04/msg00070.html', 'https://groups.google.com/group/ruby-security-ann/msg/34e0d780b04308de?dmode=source&output=gplain', 'http://lists.apple.com/archives/security-announce/2013/Oct/msg00006.html', 'http://lists.opensuse.org/opensuse-updates/2013-04/msg00079.html', 'http://rhn.redhat.com/errata/RHSA-2014-1863.html', 'https://nvd.nist.gov/vuln/detail/CVE-2013-1854', 'https://github.com/advisories/GHSA-3crr-9vmg-864v', 'http://lists.apple.com/archives/security-announce/2013/Jun/msg00000.html', 'http://rhn.redhat.com/errata/RHSA-2013-0699.html', 'http://lists.opensuse.org/opensuse-updates/2013-04/msg00075.html', 'http://lists.opensuse.org/opensuse-updates/2013-04/msg00071.html'}
| null |
RubyGems
|
GHSA-gm25-fpmr-43fj
|
Moderate severity vulnerability that affects rails
|
Cross-site scripting (XSS) vulnerability in the to_json (ActiveRecord::Base#to_json) function in Ruby on Rails before edge 9606 allows remote attackers to inject arbitrary web script via the input values.
|
{'CVE-2007-3227'}
|
2022-03-03T05:14:17.662408Z
|
2017-10-24T18:33:38Z
|
MODERATE
| null |
{'CWE-79'}
|
{'http://weblog.rubyonrails.org/2007/10/12/rails-1-2-5-maintenance-release', 'http://security.gentoo.org/glsa/glsa-200711-17.xml', 'http://bugs.gentoo.org/show_bug.cgi?id=195315', 'https://github.com/advisories/GHSA-gm25-fpmr-43fj', 'http://www.novell.com/linux/security/advisories/2007_24_sr.html', 'http://pastie.caboo.se/65550.txt', 'https://nvd.nist.gov/vuln/detail/CVE-2007-3227', 'http://weblog.rubyonrails.org/2007/10/5/rails-1-2-4-maintenance-release', 'http://secunia.com/advisories/25699', 'http://www.vupen.com/english/advisories/2007/2216', 'http://osvdb.org/36378', 'http://secunia.com/advisories/27756', 'http://secunia.com/advisories/27657', 'http://www.securityfocus.com/bid/24161', 'http://dev.rubyonrails.org/ticket/8371'}
| null |
RubyGems
|
GHSA-hg78-4f6x-99wq
|
Moderate severity vulnerability that affects rack
|
There is a possible DoS vulnerability in the multipart parser in Rack before 2.0.6. Specially crafted requests can cause the multipart parser to enter a pathological state, causing the parser to use CPU resources disproportionate to the request size.
|
{'CVE-2018-16470'}
|
2022-03-03T05:13:33.168267Z
|
2018-11-15T15:58:58Z
|
MODERATE
| null |
{'CWE-400'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2018-16470', 'https://github.com/advisories/GHSA-hg78-4f6x-99wq', 'https://groups.google.com/forum/#!msg/rubyonrails-security/U_x-YkfuVTg/xhvYAmp6AAAJ', 'https://access.redhat.com/errata/RHSA-2019:3172'}
| null |
RubyGems
|
GHSA-mf6w-45cf-qhmp
|
Git-fastclone passes user modifiable strings directly to a shell command
|
git-fastclone before 1.0.5 passes user modifiable strings directly to a shell command. An attacker can execute malicious commands by modifying the strings that are passed as arguments to "cd " and "git clone " commands in the library.
|
{'CVE-2015-8969'}
|
2022-04-26T18:33:05.969331Z
|
2018-08-15T20:04:44Z
|
CRITICAL
| null |
{'CWE-77'}
|
{'https://github.com/square/git-fastclone/pull/5', 'https://hackerone.com/reports/105190', 'https://github.com/square/git-fastclone', 'https://nvd.nist.gov/vuln/detail/CVE-2015-8969', 'https://github.com/advisories/GHSA-mf6w-45cf-qhmp', 'http://www.securityfocus.com/bid/81433'}
| null |
RubyGems
|
GHSA-q86f-fmqf-qrf6
|
Moderate severity vulnerability that affects mail
|
The mail gem before 2.5.5 for Ruby (aka A Really Ruby Mail Library) is vulnerable to SMTP command injection via CRLF sequences in a RCPT TO or MAIL FROM command, as demonstrated by CRLF sequences immediately before and after a DATA substring.
|
{'CVE-2015-9097'}
|
2022-03-03T05:13:34.066169Z
|
2017-10-24T18:33:36Z
|
MODERATE
| null |
{'CWE-93'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2015-9097', 'https://hackerone.com/reports/137631', 'https://github.com/mikel/mail/pull/1097', 'http://www.mbsd.jp/Whitepaper/smtpi.pdf', 'https://github.com/mikel/mail/commit/72befdc4dab3e6e288ce226a7da2aa474cf5be83', 'https://rubysec.com/advisories/mail-OSVDB-131677', 'https://github.com/rubysec/ruby-advisory-db', 'https://github.com/advisories/GHSA-q86f-fmqf-qrf6', 'http://openwall.com/lists/oss-security/2015/12/11/3', 'https://github.com/rubysec/ruby-advisory-db/issues/215'}
| null |
RubyGems
|
GHSA-w754-gq8r-pf5f
|
High severity vulnerability that affects mini_magick
|
lib/mini_magick.rb in the MiniMagick Gem 1.3.1 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a URL.
|
{'CVE-2013-2616'}
|
2022-03-03T05:13:52.698929Z
|
2017-10-24T18:33:37Z
|
HIGH
| null |
{'CWE-94'}
|
{'http://www.osvdb.org/91231', 'http://packetstormsecurity.com/files/120777/Ruby-Gem-Minimagic-Command-Execution.html', 'http://www.securityfocus.com/bid/58448', 'http://www.openwall.com/lists/oss-security/2013/03/19/9', 'https://nvd.nist.gov/vuln/detail/CVE-2013-2616', 'http://seclists.org/fulldisclosure/2013/Mar/123', 'https://github.com/advisories/GHSA-w754-gq8r-pf5f'}
| null |
RubyGems
|
GHSA-h3fg-h5v3-vf8m
|
CSRF forgery protection bypass in solidus_frontend
|
### Impact
CSRF vulnerability that allows a malicious site to add an item to the user's cart without their knowledge.
All `solidus_frontend` versions are affected. If you're using your own storefront, please, follow along to make sure you're not affected.
To reproduce the issue:
- Pick the id for a variant with available stock. From the rails console:
```ruby
Spree::Variant.in_stock.pluck(:id)
```
Say we pick variant id `2`.
- Launch your application, for instance, on `http://localhost:3000`:
```bash
bin/rails server
```
- Open your browser dev tools.
- Click on whatever link in your store.
- Copy the value of the `Cookie` request header sent for the previous request from your browser dev tools.
- Execute the following, using your previously selected variant id and the value of the `Cookie` header (notice how it doesn't contain any authentication token):
```bash
curl -X POST -d "variant_id=2&quantity=1" -H "Cookie: guest_token=eyJfcmFpbHMiOnsibWVzc2FnZSI6IklrWlRVMWRQWnpKMVZVdFNXRzlPVW1aaWJHTjZZa0VpIiwiZXhwIjpudWxsLCJwdXIiOiJjb29raWUuZ3Vlc3RfdG9rZW4ifX0%3D--5006ba5d346f621c760a29b6a797bf351d17d1b8; _sandbox_session=vhutu5%2FL9NmWrUpGc3DxrFA%2FFsQD1dHn1cNsD7nvE84zcjWf17Af4%2F%2F2Vab3md71b6KTb9NP6WktdXktpwH4eU01jEGIBXG5%2BMzW5nL0nb4W269qk1io4LYljvoOg8%2BZVll7oJCVkJLKKh0sSoS0Kg8j%2FCHHs%2BsShohP%2BGnA%2Bfr9Ub8H6HofpSmloSpsfHHygmX0ho03fEgzHJ4DD5wJctaNKwg7NhVikHh5kgIPPHl84OGCgv3p2oe9jR19HTxOKq7BtyvDd7XZsecWhkcfS8BPnvDDUWZG6qpAEFI5kWo81KkpSJ%2Bp6Q1HOo8%3D--n3G2vgaDG7VS%2B%2FhF--ZTjxBAkfGG3hpr4GRQ2S1Q%3D%3D; __profilin=p%3Dt" http://localhost:3000/orders/populate
```
- Reload your browser and look at how your cart got updated.
### Patches
Please, upgrade `solidus` to versions `3.1.5`, `3.0.5` or `2.11.14`.
After upgrading, make sure you read the "Upgrade notes" section below.
### Upgrade notes
The patch adds CSRF token verification to the "Add to cart" action. Adding forgery protection to a form that missed it can have some side effects.
#### `InvalidAuthenticityToken` errors
If you're using the `:exception` strategy, it's likely that after upgrading, you'll see more `ActionController::InvalidAuthenticityToken` errors popping out in your logs. Due to browser-side cache, a form can be re-rendered and sent without any attached request cookie (for instance, when re-opening a mobile browser). That will cause an authentication error, as the sent token won't match with the one in the session (none in this case). That's a known problem in the Rails community (see https://github.com/rails/rails/issues/21948), and, at this point, there's no perfect solution.
Any attempt to mitigate the issue should be seen at the application level. For an excellent survey of all the available options, take a look at https://github.com/betagouv/demarches-simplifiees.fr/blob/5b4f7f9ae9eaf0ac94008b62f7047e4714626cf9/doc/adr-csrf-forgery.md. The latter is a third-party link. As the information is relevant here, we're going to copy it below, but it should be clear that all the credit goes to @kemenaran:
> # Protecting against request forgery using CRSF tokens
>
> ## Context
>
> Rails has CSRF protection enabled by default, to protect against POST-based CSRF attacks.
>
> To protect from this, Rails stores two copies of a random token (the so-named CSRF token) on each request:
> - one copy embedded in each HTML page,
> - another copy in the user session.
>
> When performing a POST request, Rails checks that the two copies match – and otherwise denies the request. This protects against an attacker that would generate a form secretly pointing to our website: the attacker can't read the token in the session, and so can't post a form with a valid token.
>
> The problem is that, much more often, this has false positives. There are several cases for that, including:
>
> 1. The web browser (often mobile) loads a page containing a form, then is closed by the user. Later, when the browser is re-opened, it restores the page from the cache. But the session cookie has expired, and so is not restored – so the copy of the CSRF token stored in the session is missing. When the user submits the form, they get an "InvalidAuthenticityToken" exception.
>
> 2. The user attempts to fill a form, and gets an error message (usually in response to a POST request). They close the browser. When the browser is re-opened, it attempts to restore the page. On Chrome this is blocked by the browser, because the browser denies retrying a (probably non-idempotent) POST request. Safari however happily retries the POST request – but without sending any cookies (in an attempt to avoid having unexpected side-effects). So the copy of the CSRF token in the session is missing (because no cookie was sent), and the user get an "InvalidAuthenticityToken" exception.
>
> ## Options considered
>
> ### Extend the session cookie duration
>
> We can configure the session cookie to be valid for a longer time (like 2 weeks).
>
> Pros:
> - It solves 1., because when the browser restores the page, the session cookie is still valid.
>
> Cons:
> - Users would be signed-in for a much longer time by default, which has unacceptable security implications.
> - It doesn't solve 2. (because Safari doesn't send any cookie when restoring a page from a POST request)
>
> ### Change the cache parameters
>
> We can send a HTTP cache header stating 'Cache-Control: no-store, no-cache'. This instructs the browser to never keep any copy of the page, and to always make a request to the server to restore it.
>
> This solution was attempted during a year in production, and solved 1. – but also introduced another type of InvalidAuthenticityToken errors. In that scenario, the user attempts to fill a form, and gets an error message (usually in response to a POST request). They then navigate on another domain (like France Connect), then hit the "Back" button. Crossing back the domain boundary may cause the browser to either block the request or retry an invalid POST request.
>
> Pros:
> - It solves 1., because on relaunch the browser requests a fresh page again (instead of serving it from its cache), thus retrieving a fresh session and a fresh matching CSRF token.
>
> Cons:
> - It doesn't solve 2.
> - It causes another type of InvalidAuthenticityToken errors.
>
> ### Using a null-session strategy
>
> We can change the default protect_from_forgery strategy to :null_session. This makes the current request use an empty session for the request duration.
>
> Pros:
> - It kind of solves 1., by redirecting to a "Please sign-in" page when a stale form is submitted.
>
> Cons:
> - The user is asked to sign-in only after filling and submitting the form, losing their time and data
> - The user will not be redirected to their original page after signing-in
> - It has potential security implications: as the (potentically malicious) request runs anyway, variables cached by a controller before the Null session is created may allow the form submission to succeed anyway (https://www.veracode.com/blog/managing-appsec/when-rails-protectfromforgery-fails)
>
> ### Using a reset-session strategy
>
> We can change the default protect_from_forgery strategy to :reset_session. This clears the user session permanently, logging them out until they log in again.
>
> Pros:
> - It kind of solves 1., by redirecting to a "Please sign-in" page when a stale form is submitted.
>
> Cons:
> - A forgery error in a browser tab will disconnect the user in all its open tabs
> - It has potential security implications: as the (potentically malicious) request runs anyway, variables cached by a controller before the Null session is created may allow the form submission to succeed anyway (https://www.veracode.com/blog/managing-appsec/when-rails-protectfromforgery-fails)
> - It allows an attacker to disconnect an user on demand, which is not only inconvenient, but also has security implication (the attacker could then log the user on it's own attacker account, pretending to be the user account)
>
> ### Redirect to login form
>
> When a forgery error occurs, we can instead redirect to the login form.
>
> Pros:
> - It kind of solves 1., by redirecting to a "Please sign-in" page when a stale form is submitted (but the user data is lost).
> - It kind of solves 2., by redirecting to a "Please sign-in" page when a previously POSTed form is reloaded.
>
> Cons:
> - Not all forms require authentication – so for public forms there is no point redirecting to the login form.
> - The user will not be redirected to their original page after signing-in (because setting the redirect path is a state-changing action, and it is dangerous to let an unauthorized request changing the state – an attacker could control the path where an user is automatically redirected to.)
> - The implementation is finicky, and may introduce security errors. For instance, a naive implementation that catches the exception and redirect_to the sign-in page will prevent Devise from running a cleanup code – which means the user will still be logged, and the CSRF protection is bypassed. However a well-tested implementation that lets Devise code run should avoid these pittfalls.
>
> ### Using a long-lived cookie for CSRF tokens
>
> Instead of storing the CSRF token in the session cookie (which is deleted when the browser is closed), we can instead store it in a longer-lived cookie. For this we need to patch Rails.
>
> Pros:
> - It solves 1., because when the user submits a stale form, even if the session cookie because stale, the long-lived CSRF cookie is still valid.
>
> Cons:
> - It doesn't solve 2., because when Safari retries a POST request, it sends none of the cookies (not even long-lived ones).
> - Patching Rails may introduce security issues (now or in the future)
#### Broken behavior due to session expiration + template cache
Although pretty unlikely, you should make sure that your current setup for cache/session expiration is compatible. The upgrade can break the addition of products to the cart if both:
- The "Add to cart" form is being cached (usually along with the variant information).
- A user session is reset at every or every few requests.
The token validation depends on the issuing and consuming sessions being the same. If a product page is cached with the token in it, it can become stale on a subsequent rendering if the session changes.
To check that you're safe, after having upgraded locally, go through the following steps:
- Enable cache on dev mode:
```bash
bin/rails dev:cache
```
- Visit the page for a variant with stock.
- Reload that page several times.
- Click on the "Add to cart" button.
- Remember to rerun `bin/rails dev:cache` to turn off cache again.
No error or session reset should happen.
Otherwise, you can try with:
- Revisiting how your session gets expired.
- Changing the caching strategy to exclude the token.
#### Using weaker CSRF protection strategies
It's also important to understand that a complete fix will only be in place when using the `:exception` forgery protection strategy. The `solidus_frontend` engine can't do pretty much anything otherwise. Using weaker CSRF strategies should be an informed and limited decision made by the application team. After the upgrade:
- An app using `:null_session` should also be safe, but there will be side effects. That strategy runs with a null object session. As such, no order and no user is found on it. A new `cart` state order is created in the database, associated with no user. Next time the user visits the site, they won't find any difference in its cart state.
- An app using `:reset_session` is not entirely safe. That strategy resets the session. That means that registered users will be logged out. Next time a user visits, they'll see the cart with the items added during the CSRF attack, although it won't be associated with their account in the case of registered users.
#### Reversing the update
If you still want to deploy the upgraded version before changing your application code (if the latter is needed), you can add the following workaround to your `config/application.rb` (however, take into account that you'll keep being vulnerable):
```ruby
config.after_initialize do
Spree::OrdersController.skip_before_action :verify_authenticity_token, only: [:populate]
end
```
### Workarounds
If an upgrade is not an option, you can work around the issue by adding the following to `config/application.rb`:
```ruby
config.after_initialize do
Spree::OrdersController.protect_from_forgery with: ApplicationController.forgery_protection_strategy.name.demodulize.underscore.to_sym, only: [:populate]
end
```
However, go through the same safety check detailed on "Upgrade notes" above.
### References
- [CSRF on the Rails guides](https://guides.rubyonrails.org/security.html#cross-site-request-forgery-csrf)
- [How CSRF tokens are generated and validated on Rails](https://medium.com/rubyinside/a-deep-dive-into-csrf-protection-in-rails-19fa0a42c0ef)
- [Solidus security](https://solidus.io/security/)
### For more information
If you have any questions or comments about this advisory:
* Open an [issue](https://github.com/solidusio/solidus/issues) or a [discussion](https://github.com/solidusio/solidus/discussions) in Solidus.
* Email us at [security@solidus.io](mailto:security@soliidus.io)
* Contact the core team on [Slack](http://slack.solidus.io/)
|
{'CVE-2021-43846'}
|
2022-03-03T05:13:47.735941Z
|
2022-01-06T18:33:44Z
|
MODERATE
| null |
{'CWE-352'}
|
{'https://github.com/solidusio/solidus/security/advisories/GHSA-h3fg-h5v3-vf8m', 'https://github.com/solidusio/solidus/commit/4d17cacf066d9492fc04eb3a0b16084b47376d81', 'https://github.com/solidusio/solidus', 'https://github.com/solidusio/solidus/commit/a1b9bf7f24f9b8684fc4d943eacb02b1926c77c6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43846'}
| null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.