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-88cw-3m6x-49f7
|
2021-07-29T20:39:52Z
|
2021-08-02T17:25:58Z
| null |
['CVE-2020-17054']
|
Out-of-bounds Write in ChakraCore
|
Chakra Scripting Engine Memory Corruption Vulnerability This CVE ID is unique from CVE-2020-17048.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'NuGet', 'name': 'Microsoft.ChakraCore'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.11.23'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-17054'}, {'type': 'WEB', 'url': 'https://github.com/chakra-core/ChakraCore/pull/6528'}, {'type': 'WEB', 'url': 'https://github.com/chakra-core/ChakraCore/pull/6528/commits/e81e8a51ec7ba3d0dfb6089254f166c2733216e1'}, {'type': 'WEB', 'url': 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-17054'}]
|
{'cwe_ids': ['CWE-787'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-04-20T19:10:19Z', 'nvd_published_at': '2020-11-11T07:15:00Z'}
|
1.4.0
|
GHSA-9p9m-9xww-qjcx
|
2021-08-19T21:21:44Z
|
2021-08-25T20:45:06Z
| null |
['CVE-2020-25791']
|
Array size is not checked in sized-chunks
|
An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with unit().
|
[{'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': 'crates.io', 'name': 'sized-chunks'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.6.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-25791'}, {'type': 'WEB', 'url': 'https://github.com/bodil/sized-chunks/issues/11'}, {'type': 'PACKAGE', 'url': 'https://github.com/bodil/sized-chunks'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0041.html'}]
|
{'cwe_ids': ['CWE-129'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:21:44Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-6p5r-g9mq-ggh2
|
2021-08-24T13:11:42Z
|
2021-08-25T14:42:49Z
| null |
['CVE-2021-37658']
|
Reference binding to nullptr in `MatrixSetDiagV*` ops
|
### Impact
An attacker can cause undefined behavior via binding a reference to null pointer in all operations of type `tf.raw_ops.MatrixSetDiagV*`:
```python
import tensorflow as tf
tf.raw_ops.MatrixSetDiagV3(
input=[1,2,3],
diagonal=[1,1],
k=[],
align='RIGHT_LEFT')
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/linalg/matrix_diag_op.cc) has incomplete validation that the value of `k` is a valid tensor. We have check that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong:
```cc
auto& diag_index = context->input(1);
...
lower_diag_index = diag_index.flat<int32>()(0);
```
### Patches
We have patched the issue in GitHub commit [ff8894044dfae5568ecbf2ed514c1a37dc394f1b](https://github.com/tensorflow/tensorflow/commit/ff8894044dfae5568ecbf2ed514c1a37dc394f1b).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-6p5r-g9mq-ggh2'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37658'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/ff8894044dfae5568ecbf2ed514c1a37dc394f1b'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-824'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T13:11:42Z', 'nvd_published_at': '2021-08-12T21:15:00Z'}
|
1.4.0
|
GHSA-f8h4-7rgh-q2gm
|
2021-08-23T22:09:33Z
|
2021-08-25T14:43:24Z
| null |
['CVE-2021-37650']
|
Segfault and heap buffer overflow in `{Experimental,}DatasetToTFRecord`
|
### Impact
The implementation for `tf.raw_ops.ExperimentalDatasetToTFRecord` and `tf.raw_ops.DatasetToTFRecord` can trigger heap buffer overflow and segmentation fault:
```python
import tensorflow as tf
dataset = tf.data.Dataset.range(3)
dataset = tf.data.experimental.to_variant(dataset)
tf.raw_ops.ExperimentalDatasetToTFRecord(
input_dataset=dataset,
filename='/tmp/output',
compression_type='')
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/data/experimental/to_tf_record_op.cc#L93-L102) assumes that all records in the dataset are of string type. However, there is no check for that, and the example given above uses numeric types.
### Patches
We have patched the issue in GitHub commit [e0b6e58c328059829c3eb968136f17aa72b6c876](https://github.com/tensorflow/tensorflow/commit/e0b6e58c328059829c3eb968136f17aa72b6c876).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
[{'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': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-f8h4-7rgh-q2gm'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37650'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/e0b6e58c328059829c3eb968136f17aa72b6c876'}]
|
{'cwe_ids': ['CWE-120', 'CWE-787'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T22:09:33Z', 'nvd_published_at': '2021-08-12T21:15:00Z'}
|
1.4.0
|
GHSA-44qp-qhfv-c7f6
|
2022-02-08T21:20:55Z
|
2021-08-13T15:21:02Z
| null |
['CVE-2021-30639']
|
Improper Handling of Exceptional Conditions in Apache Tomcat
|
A vulnerability in Apache Tomcat allows an attacker to remotely trigger a denial of service. An error introduced as part of a change to improve error handling during non-blocking I/O meant that the error flag associated with the Request object was not reset between requests. This meant that once a non-blocking I/O error occurred, all future requests handled by that request object would fail. Users were able to trigger non-blocking I/O errors, e.g. by dropping a connection, thereby creating the possibility of triggering a DoS. Applications that do not use non-blocking I/O are not exposed to this vulnerability. This issue affects Apache Tomcat 10.0.3 to 10.0.4; 9.0.44; 8.5.64.
|
[{'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': 'Maven', 'name': 'org.apache.tomcat:tomcat'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '10.0.3'}, {'fixed': '10.0.5'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.apache.tomcat:tomcat'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '9.0.0'}, {'fixed': '9.0.45'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.apache.tomcat:tomcat'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '8.5.65'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-30639'}, {'type': 'WEB', 'url': 'https://kc.mcafee.com/corporate/index?page=content&id=SB10366'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r79a7c019712b39aedf7cf4da9276d80610f04441b2a4f6506cb2daaf@%3Cdev.tomcat.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r79a7c019712b39aedf7cf4da9276d80610f04441b2a4f6506cb2daaf@%3Cusers.tomcat.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rd84fae1f474597bdf358f5bdc0a5c453c507bd527b83e8be6b5ea3f4%40%3Cannounce.tomcat.apache.org%3E'}, {'type': 'WEB', 'url': 'https://security.gentoo.org/glsa/202208-34'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20210827-0007/'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujan2022.html'}]
|
{'cwe_ids': ['CWE-755'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-07-13T20:59:46Z', 'nvd_published_at': '2021-07-12T15:15:00Z'}
|
1.4.0
|
GHSA-rh7x-ppxx-p34c
|
2021-08-19T20:53:37Z
|
2021-08-25T20:49:32Z
| null |
['CVE-2020-35896']
|
Insufficient size checks in ws
|
An issue was discovered in the ws crate through 2020-09-25 for Rust. The outgoing buffer is not properly limited, leading to a remote memory-consumption attack.
|
[{'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': 'crates.io', 'name': 'ws'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.9.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35896'}, {'type': 'WEB', 'url': 'https://github.com/housleyjk/ws-rs/issues/291'}, {'type': 'PACKAGE', 'url': 'https://github.com/housleyjk/ws-rs'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0043.html'}]
|
{'cwe_ids': ['CWE-400', 'CWE-770'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T20:53:37Z', 'nvd_published_at': '2020-12-31T10:15:00Z'}
|
1.4.0
|
GHSA-6q5w-m3c5-rv95
|
2021-08-19T21:08:01Z
|
2021-08-25T20:47:59Z
| null |
['CVE-2020-35866']
|
Data races in rusqlite
|
An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via VTab / VTabCursor.
|
[{'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': 'crates.io', 'name': 'rusqlite'}, 'ecosystem_specific': {'affected_functions': ['rusqlite::Connection::get_aux', 'rusqlite::Connection::set_aux', 'rusqlite::session::Session::attach', 'rusqlite::session::Session::diff', 'rusqlite::trace::log', 'rusqlite::vtab::create_module']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.23.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35866'}, {'type': 'WEB', 'url': 'https://github.com/rusqlite/rusqlite/commit/c9ef5bd63cad5c0c123344c072b490a1a9bcbe1f'}, {'type': 'PACKAGE', 'url': 'https://github.com/rusqlite/rusqlite'}, {'type': 'WEB', 'url': 'https://github.com/rusqlite/rusqlite/releases/tag/0.23.0'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0014.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:08:01Z', 'nvd_published_at': '2020-12-31T10:15:00Z'}
|
1.4.0
|
GHSA-m697-4v8f-55qg
|
2021-08-31T20:57:09Z
|
2021-08-05T17:04:21Z
| null |
['CVE-2021-32813']
|
Header dropping in traefik
|
# Impact
There exists a potential header vulnerability in Traefik's handling of the Connection header. Active exploitation of this issue is unlikely, as it requires that a removed header would lead to a privilege escalation, however, the Traefik team has addressed this issue to prevent any potential abuse.
# Details
If you have a chain of Traefik middlewares, and one of them sets a request header `Important-Security-Header`, then sending a request with the following Connection header will cause it to be removed before the request was sent:
```
curl 'https://example.com' -H "Connection: Important-Security-Header" -0
```
In this case, the backend does not see the request header `Important-Security-Header`.
# Patches
Traefik v2.4.x: https://github.com/traefik/traefik/releases/tag/v2.4.13
# Workarounds
No.
# For more information
If you have any questions or comments about this advisory, [open an issue](https://github.com/traefik/traefik/issues).
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/traefik/traefik/v2'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.13'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/traefik/traefik'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.7.30'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/traefik/traefik/security/advisories/GHSA-m697-4v8f-55qg'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-32813'}, {'type': 'WEB', 'url': 'https://github.com/traefik/traefik/pull/8319/commits/cbaf86a93014a969b8accf39301932c17d0d73f9'}, {'type': 'WEB', 'url': 'https://github.com/traefik/traefik/releases/tag/v2.4.13'}, {'type': 'PACKAGE', 'url': 'github.com/traefik/traefik'}]
|
{'cwe_ids': ['CWE-913'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-04T18:54:19Z', 'nvd_published_at': '2021-08-03T23:15:00Z'}
|
1.4.0
|
GHSA-fvhr-7j8m-3cvc
|
2021-08-24T19:08:25Z
|
2021-08-25T20:57:02Z
| null |
['CVE-2020-36469']
|
Data races in appendix
|
The `appendix` crate implements a key-value mapping data structure called
`Index<K, V>` that is stored on disk. The crate allows for any type to inhabit
the generic `K` and `V` type parameters and implements Send and Sync for them
unconditionally.
Using a type that is not marked as `Send` or `Sync` with `Index` can allow it
to be used across multiple threads leading to data races. Additionally using
reference types for the keys or values will lead to the segmentation faults
in the crate's code.
|
[{'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': 'crates.io', 'name': 'appendix'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.2.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36469'}, {'type': 'WEB', 'url': 'https://github.com/krl/appendix/issues/6'}, {'type': 'PACKAGE', 'url': 'https://github.com/krl/appendix'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0149.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T20:35:37Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-5wg8-7c9q-794v
|
2021-08-19T18:59:40Z
|
2021-08-25T20:50:00Z
| null |
['CVE-2020-35912']
|
Data races in lock_api
|
An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockWriteGuard unsoundness.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'lock_api'}, 'ecosystem_specific': {'affected_functions': ['lock_api::MappedRwLockWriteGuard']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35912'}, {'type': 'WEB', 'url': 'https://github.com/Amanieu/parking_lot/pull/262'}, {'type': 'PACKAGE', 'url': 'https://github.com/Amanieu/parking_lot'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0070.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:59:40Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-m9m5-cg5h-r582
|
2023-06-13T20:01:40Z
|
2021-08-25T20:50:24Z
| null |
['CVE-2020-35926']
|
Improper random number generation in nanorand
|
In versions of nanorand prior to 0.5.1, RandomGen implementations for standard unsigned integers could fail to properly generate numbers, due to using bit-shifting to truncate a 64-bit number, rather than just an as conversion. This often manifested as RNGs returning nothing but 0, including the cryptographically secure ChaCha random number generator.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'nanorand'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.5.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35926'}, {'type': 'WEB', 'url': 'https://github.com/Absolucy/nanorand-rs/commit/5ba218ac29df4786b002d7d12b47fa0c04a331f2'}, {'type': 'PACKAGE', 'url': 'https://github.com/Absolucy/nanorand-rs'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0089.html'}, {'type': 'WEB', 'url': 'https://twitter.com/aspenluxxxy/status/1336684692284772352'}]
|
{'cwe_ids': ['CWE-338'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:55:41Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-3xg5-6c3j-vp8x
|
2021-08-26T17:42:07Z
|
2021-08-30T16:23:34Z
| null |
['CVE-2020-18703']
|
Improper Restriction of XML External Entity Reference in Quokka
|
XML External Entities (XXE) in Quokka v0.4.0 allows remote attackers to execute arbitrary code via the component 'quokka/utils/atom.py'.
|
[{'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': 'quokka'}, 'ecosystem_specific': {'affected_functions': ['quokka.admin.wtforms_html5.set_title']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.4.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-18703'}, {'type': 'WEB', 'url': 'https://github.com/rochacbruno/quokka/issues/676'}, {'type': 'PACKAGE', 'url': '://github.com/rochacbruno/quokka'}]
|
{'cwe_ids': ['CWE-611'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-26T17:42:07Z', 'nvd_published_at': '2021-08-16T18:15:00Z'}
|
1.4.0
|
GHSA-cvh5-p6r6-g2qc
|
2021-08-26T20:11:49Z
|
2021-08-30T16:13:40Z
| null |
['CVE-2021-37704']
|
Exposed phpinfo() leadked via documentation files
|
### Impact
The `phpinfo()` can be exposed if the `/vendor` is not protected from public access. This is a rare situation today since the vendor directory is often located outside the web directory or protected via server rule (.htaccess, etc).
### Patches
Only the v6, v7 and v8 will be patched respectively in 8.0.7, 7.1.2, 6.1.5.
Older versions such as v5, v4 are not longer supported and will **NOT** be patched.
### Workarounds
Protect the `/vendor` directory from public access.
### References
The first issue revealing this vulnerability is located here: https://github.com/flextype/flextype/issues/567
V6 fix: https://github.com/PHPSocialNetwork/phpfastcache/pull/815
V7 fix: https://github.com/PHPSocialNetwork/phpfastcache/pull/814
V8 fix: https://github.com/PHPSocialNetwork/phpfastcache/pull/813
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [our issue tracker](https://github.com/PHPSocialNetwork/phpfastcache/issues)
* Email us at [security@geolim4.com](mailto:security@geolim4.com)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'phpfastcache/phpfastcache'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.1.5'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'phpfastcache/phpfastcache'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '7.0.0'}, {'fixed': '7.1.2'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'phpfastcache/phpfastcache'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '8.0.0'}, {'fixed': '8.0.7'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/PHPSocialNetwork/phpfastcache/security/advisories/GHSA-cvh5-p6r6-g2qc'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37704'}, {'type': 'WEB', 'url': 'https://github.com/flextype/flextype/issues/567'}, {'type': 'WEB', 'url': 'https://github.com/PHPSocialNetwork/phpfastcache/pull/813'}, {'type': 'WEB', 'url': 'https://github.com/PHPSocialNetwork/phpfastcache/pull/814'}, {'type': 'WEB', 'url': 'https://github.com/PHPSocialNetwork/phpfastcache/pull/815'}, {'type': 'WEB', 'url': 'https://github.com/PHPSocialNetwork/phpfastcache/commit/41a77d0d8f126dbd6fbedcd9e6a82e86cdaafa51'}, {'type': 'WEB', 'url': 'https://github.com/PHPSocialNetwork/phpfastcache/blob/master/CHANGELOG.md#807'}, {'type': 'WEB', 'url': 'https://packagist.org/packages/phpfastcache/phpfastcache'}]
|
{'cwe_ids': ['CWE-200', 'CWE-668'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-26T20:11:49Z', 'nvd_published_at': '2021-08-12T20:15:00Z'}
|
1.4.0
|
GHSA-4q4x-67hx-5mpg
|
2023-06-13T17:43:58Z
|
2021-08-25T20:44:08Z
| null |
['CVE-2019-15545']
|
Failure to properly verify ed25519 signatures in libp2p-core
|
Affected versions of this crate did not properly verify ed25519 signatures. Any signature with a correct length was considered valid. This allows an attacker to impersonate any node identity.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'libp2p-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.8.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-15545'}, {'type': 'PACKAGE', 'url': 'https://github.com/libp2p/rust-libp2p'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0004.html'}]
|
{'cwe_ids': ['CWE-347'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:23:31Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-r88h-6987-g79f
|
2023-06-13T21:54:46Z
|
2021-08-25T21:00:28Z
| null |
[]
|
Data races on syncpool
|
Affected versions of this crate unconditionally implements `Send` for `Bucket2`. This allows sending non-Send types to other threads.
This can lead to data races when non Send types like `Cell<T>` or `Rc<T>` are contained inside `Bucket2` and sent across thread boundaries. The data races can potentially lead to memory corruption (as demonstrated in the PoC from the original report issue).
The flaw was corrected in commit `15b2828` by adding a `T: Send` bound to the `Send` impl of `Bucket2<T>`.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'syncpool'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.1.6'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/Chopinsky/byte_buffer/issues/2'}, {'type': 'WEB', 'url': 'https://github.com/Chopinsky/byte_buffer/commit/15b282877d1e576de2b337d8162bbf43ed1a0f2d'}, {'type': 'PACKAGE', 'url': 'https://github.com/Chopinsky/byte_buffer/tree/master/syncpool'}, {'type': 'WEB', 'url': 'https://github.com/RustSec/advisory-db/blob/main/crates/syncpool/RUSTSEC-2020-0142.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0142.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-05T22:09:21Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-98hv-qff3-8793
|
2021-08-26T19:20:22Z
|
2021-08-30T16:24:08Z
| null |
['CVE-2020-18704']
|
Unrestricted Upload of File with Dangerous Type in django-widgy
|
Unrestricted Upload of File with Dangerous Type in Django-Widgy v0.8.4 allows remote attackers to execute arbitrary code via the 'image' widget in the component 'Change Widgy Page'.
|
[{'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': 'django-widgy'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.9.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-18704'}, {'type': 'WEB', 'url': 'https://github.com/fusionbox/django-widgy/issues/387'}, {'type': 'PACKAGE', 'url': 'https://github.com/fusionbox/django-widgy'}]
|
{'cwe_ids': ['CWE-434'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-26T19:20:22Z', 'nvd_published_at': '2021-08-16T18:15:00Z'}
|
1.4.0
|
GHSA-27wq-qx3q-fxm9
|
2021-10-21T14:15:51Z
|
2021-08-23T19:42:28Z
| null |
['CVE-2021-39131']
|
Improper Handling of Unexpected Data Type in ced
|
### Impact
In ced v0.1.0, passing data types other than `Buffer` causes the Node.js process to crash.
### Patches
The problem has been patched in [ced v1.0.0](https://github.com/sonicdoe/ced/releases/tag/v1.0.0). You can upgrade from v0.1.0 without any breaking changes.
### Workarounds
Before passing an argument to ced, verify it’s a `Buffer` using [`Buffer.isBuffer(obj)`](https://nodejs.org/api/buffer.html#buffer_static_method_buffer_isbuffer_obj).
### CVSS score
[CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/RL:O/RC:C](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/RL:O/RC:C)
Base Score: 7.5 (High)
Temporal Score: 7.2 (High)
Since ced is a library, the scoring is based on the “[reasonable worst-case implementation scenario](https://www.first.org/cvss/v3.1/user-guide#3-7-Scoring-Vulnerabilities-in-Software-Libraries-and-Similar)”, namely, accepting data from untrusted sources over a network and passing it directly to ced. Depending on your specific implementation, the vulnerability’s severity in your program may be different.
### Proof of concept
```js
const express = require("express");
const bodyParser = require("body-parser");
const ced = require("ced");
const app = express();
app.use(bodyParser.raw());
app.post("/", (req, res) => {
const encoding = ced(req.body);
res.end(encoding);
});
app.listen(3000);
```
`curl --request POST --header "Content-Type: text/plain" --data foo http://localhost:3000` crashes the server.
### References
- https://github.com/sonicdoe/ced/commit/a4d9f10b6bf1cd468d1a5b9a283cdf437f8bb7b3
|
[{'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': 'npm', 'name': 'ced'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.0.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/sonicdoe/ced/security/advisories/GHSA-27wq-qx3q-fxm9'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39131'}, {'type': 'WEB', 'url': 'https://github.com/sonicdoe/ced/commit/a4d9f10b6bf1cd468d1a5b9a283cdf437f8bb7b3'}, {'type': 'PACKAGE', 'url': 'https://github.com/sonicdoe/ced'}, {'type': 'WEB', 'url': 'https://github.com/sonicdoe/ced/releases/tag/v1.0.0'}]
|
{'cwe_ids': ['CWE-241'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T17:18:32Z', 'nvd_published_at': '2021-08-17T23:15:00Z'}
|
1.4.0
|
GHSA-9c8h-vvrj-w2p8
|
2021-08-23T18:35:20Z
|
2021-08-25T14:43:59Z
| null |
['CVE-2021-37641']
|
Heap OOB in `RaggedGather`
|
### Impact
If the arguments to `tf.raw_ops.RaggedGather` don't determine a valid ragged tensor code can trigger a read from outside of bounds of heap allocated buffers.
```python
import tensorflow as tf
tf.raw_ops.RaggedGather(
params_nested_splits = [0,0,0],
params_dense_values = [1,1],
indices = [0,0,9,0,0],
OUTPUT_RAGGED_RANK=0)
```
In debug mode, the same code triggers a `CHECK` failure.
The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/ragged_gather_op.cc#L70) directly reads the first dimension of a tensor shape before checking that said tensor has rank of at least 1 (i.e., it is not a scalar). Furthermore, the implementation does not check that the list given by `params_nested_splits` is not an empty list of tensors.
### Patches
We have patched the issue in GitHub commit [a2b743f6017d7b97af1fe49087ae15f0ac634373](https://github.com/tensorflow/tensorflow/commit/a2b743f6017d7b97af1fe49087ae15f0ac634373).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
[{'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': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9c8h-vvrj-w2p8'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37641'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/a2b743f6017d7b97af1fe49087ae15f0ac634373'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T18:35:20Z', 'nvd_published_at': '2021-08-12T21:15:00Z'}
|
1.4.0
|
GHSA-xmr7-v725-2jjr
|
2023-03-22T20:54:46Z
|
2021-08-25T20:52:12Z
| null |
['CVE-2021-27671']
|
Cross site scripting in comrak
|
An issue was discovered in the comrak crate before 0.9.1 for Rust. Cross site scripting (XSS) can occur because the protection mechanism for data: and javascript: URIs is case-sensitive, allowing (for example) Data: to be used in an attack.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'comrak'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.9.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-27671'}, {'type': 'WEB', 'url': 'https://github.com/kivikakk/comrak/commit/b3efbb6e427bcd33bb14db45753ad4fd98e0f5bf'}, {'type': 'PACKAGE', 'url': 'https://github.com/kivikakk/comrak'}, {'type': 'WEB', 'url': 'https://github.com/kivikakk/comrak/releases/tag/0.9.1'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0026.html'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:34:25Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-2jfv-g3fh-xq3v
|
2023-06-13T21:56:58Z
|
2021-08-25T20:46:54Z
| null |
['CVE-2020-35875']
|
Excessive memory usage in tokio-rustls
|
tokio-rustls does not call process_new_packets immediately after read, so the expected termination condition wants_read always returns true. As long as new incoming data arrives faster than it is processed and the reader does not return pending, data will be buffered. This may cause DoS.
|
[{'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': 'crates.io', 'name': 'tokio-rustls'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.12.0'}, {'fixed': '0.12.3'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'tokio-rustls'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.13.0'}, {'fixed': '0.13.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35875'}, {'type': 'WEB', 'url': 'https://github.com/tokio-rs/tls/pull/14'}, {'type': 'PACKAGE', 'url': 'https://github.com/tokio-rs/tls'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0019.html'}]
|
{'cwe_ids': ['CWE-400'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:19:01Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-5fg8-2547-mr8q
|
2022-01-04T19:36:30Z
|
2021-08-03T16:57:05Z
| null |
['CVE-2021-32796']
|
Misinterpretation of malicious XML input
|
### Impact
xmldom versions 0.6.0 and older do not correctly escape special characters when serializing elements removed from their ancestor. This may lead to unexpected syntactic changes during XML processing in some downstream applications.
### Patches
Update to one of the fixed versions of `@xmldom/xmldom` (`>=0.7.0`)
See issue #271 for the status of publishing `xmldom` to npm or join #270 for Q&A/discussion until it's resolved.
### Workarounds
Downstream applications can validate the input and reject the maliciously crafted documents.
### References
Similar to this one reported on the Go standard library:
- https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/
- https://mattermost.com/blog/securing-xml-implementations-across-the-web/
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [`xmldom/xmldom`](https://github.com/xmldom/xmldom)
* Email us: send an email to **all** addresses that are shown by `npm owner ls @xmldom/xmldom`
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'xmldom'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.7.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/xmldom/xmldom/security/advisories/GHSA-5fg8-2547-mr8q'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-32796'}, {'type': 'WEB', 'url': 'https://github.com/xmldom/xmldom/commit/7b4b743917a892d407356e055b296dcd6d107e8b'}, {'type': 'PACKAGE', 'url': 'https://github.com/xmldom/xmldom'}, {'type': 'WEB', 'url': 'https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/'}, {'type': 'WEB', 'url': 'https://mattermost.com/blog/securing-xml-implementations-across-the-web/'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/package/@xmldom/xmldom'}]
|
{'cwe_ids': ['CWE-116'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-02T23:21:11Z', 'nvd_published_at': '2021-07-27T22:15:00Z'}
|
1.4.0
|
GHSA-hwfp-hg2m-9vr2
|
2023-08-31T15:59:55Z
|
2021-08-09T20:43:44Z
| null |
['CVE-2021-32559']
|
Integer overflow in pywin32
|
An integer overflow exists in pywin32 prior to version b301 when adding an access control entry (ACE) to an access control list (ACL) that would cause the size to be greater than 65535 bytes. An attacker who successfully exploited this vulnerability could crash the vulnerable process.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'pywin32'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '301'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-32559'}, {'type': 'WEB', 'url': 'https://github.com/mhammond/pywin32/issues/1700'}, {'type': 'WEB', 'url': 'https://github.com/mhammond/pywin32/pull/1701'}, {'type': 'WEB', 'url': 'https://github.com/fireeye/Vulnerability-Disclosures/blob/master/FEYE-2021-0017/FEYE-2021-0017.md'}, {'type': 'PACKAGE', 'url': 'https://github.com/mhammond/pywin32'}, {'type': 'WEB', 'url': 'https://github.com/mhammond/pywin32/releases'}]
|
{'cwe_ids': ['CWE-190'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-07-07T16:45:27Z', 'nvd_published_at': '2021-07-06T12:15:00Z'}
|
1.4.0
|
GHSA-h7v4-7xg3-hxcc
|
2022-02-08T20:58:51Z
|
2021-08-25T14:47:46Z
| null |
['CVE-2021-39147']
|
XStream is vulnerable to an Arbitrary Code Execution attack
|
### Impact
The vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.
### Patches
XStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.
### Workarounds
See [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.
### References
See full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-39147](https://x-stream.github.io/CVE-2021-39147.html).
### Credits
wh1t3p1g from TSRC (Tencent Security Response Center) found and reported the issue to XStream and provided the required information to reproduce it.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)
* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)
|
[{'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': 'Maven', 'name': 'com.thoughtworks.xstream:xstream'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.4.18'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/x-stream/xstream/security/advisories/GHSA-h7v4-7xg3-hxcc'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39147'}, {'type': 'PACKAGE', 'url': 'https://github.com/x-stream/xstream'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2021/09/msg00017.html'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/22KVR6B5IZP3BGQ3HPWIO2FWWCKT3DHP/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PVPHZA7VW2RRSDCOIPP2W6O5ND254TU7/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QGXIU3YDPG6OGTDHMBLAFN7BPBERXREB/'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20210923-0003/'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2021/dsa-5004'}, {'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'}, {'type': 'WEB', 'url': 'https://x-stream.github.io/CVE-2021-39147.html'}]
|
{'cwe_ids': ['CWE-502'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T18:22:16Z', 'nvd_published_at': '2021-08-23T18:15:00Z'}
|
1.4.0
|
GHSA-hj9h-wrgg-hgmx
|
2021-08-19T18:59:37Z
|
2021-08-25T20:50:02Z
| null |
['CVE-2020-35913']
|
Data races in lock_api
|
An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockReadGuard unsoundness.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'lock_api'}, 'ecosystem_specific': {'affected_functions': ['lock_api::RwLockReadGuard']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35913'}, {'type': 'WEB', 'url': 'https://github.com/Amanieu/parking_lot/pull/262'}, {'type': 'PACKAGE', 'url': 'https://github.com/Amanieu/parking_lot'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0070.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:59:37Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-c3m3-c39q-pv23
|
2023-06-13T20:56:39Z
|
2021-08-25T20:44:10Z
| null |
['CVE-2019-15543']
|
Out of bounds write in slice-deque
|
Affected versions of this crate entered a corrupted state if mem::size_of::<T>() % allocation_granularity() != 0 and a specific allocation pattern was used: sufficiently shifting the deque elements over the mirrored page boundary.
This allows an attacker that controls controls both element insertion and removal to corrupt the deque, such that reading elements from it would read bytes corresponding to other elements in the deque. (e.g. a read of T could read some bytes from one value and some bytes from an adjacent one, resulting in a T whose value representation is not meaningful). This is undefined behavior.
The flaw was corrected by using a pair of pointers to track the head and tail of the deque instead of a pair of indices. This pair of pointers are represented using a Rust slice.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'slice-deque'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.2.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-15543'}, {'type': 'WEB', 'url': 'https://github.com/gnzlbg/slice_deque/issues/57'}, {'type': 'PACKAGE', 'url': 'https://github.com/gnzlbg/slice_deque'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0002.html'}]
|
{'cwe_ids': ['CWE-787'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:23:28Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-wxjf-9f4g-3v44
|
2021-08-24T18:02:25Z
|
2021-08-25T20:56:05Z
| null |
['CVE-2020-36461']
|
Data races in noise_search
|
Affected versions of the `noise_search` crate unconditionally implement Send/Sync for `MvccRwLock`.
This can lead to data races when types that are either `!Send` or `!Sync` (e.g. `Rc<T>`, `Arc<Cell<_>>`) are contained inside `MvccRwLock` and sent across thread boundaries. The data races can potentially lead to memory corruption (as demonstrated in the PoC from the original report issue).
Also, safe APIs of `MvccRwLock` allow aliasing violations by allowing `&T` and `LockResult<MutexGuard<Box<T>>>` to co-exist in conflicting lifetime regions. The APIs of `MvccRwLock` should either be marked as `unsafe` or `MbccRwLock` should be changed to private or pub(crate).
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'noise_search'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.7.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36461'}, {'type': 'WEB', 'url': 'https://github.com/pipedown/noise/issues/72'}, {'type': 'PACKAGE', 'url': 'https://github.com/pipedown/noise'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0141.html'}]
|
{'cwe_ids': ['CWE-362', 'CWE-77'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T21:19:50Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-mxv6-q98x-h958
|
2021-08-24T18:00:46Z
|
2021-08-25T20:56:07Z
| null |
['CVE-2020-36460']
|
Data races in model
|
`Shared` data structure in `model` crate implements `Send` and `Sync` traits regardless of the inner type.
This allows safe Rust code to trigger a data race, which is undefined behavior in Rust.
Users are advised to treat `Shared` as an unsafe type.
It should not be used outside of the testing context,
and care must be taken so that the testing code does not have a data race
besides a race condition that is expected to be caught by the test.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'model'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.1.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36460'}, {'type': 'WEB', 'url': 'https://github.com/spacejam/model/issues/3'}, {'type': 'PACKAGE', 'url': 'https://github.com/spacejam/model'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0140.html'}]
|
{'cwe_ids': ['CWE-362', 'CWE-843'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T21:17:33Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-jrf8-cmgg-gv2m
|
2023-06-13T20:29:54Z
|
2021-08-25T20:53:07Z
| null |
['CVE-2021-26307']
|
Error on unsupported architectures in raw-cpuid
|
native_cpuid::cpuid_count() exposes the unsafe __cpuid_count() intrinsic from core::arch::x86 or core::arch::x86_64 as a safe function, and uses it internally, without checking the safety requirement:
* The CPU the program is currently running on supports the function being called.
CPUID is available in most, but not all, x86/x86_64 environments. The crate compiles only on these architectures, so others are unaffected. This issue is mitigated by the fact that affected programs are expected to crash deterministically every time.
The flaw has been fixed in v9.0.0, by intentionally breaking compilation when targeting SGX or 32-bit x86 without SSE. This covers all affected CPUs.
|
[{'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': 'crates.io', 'name': 'raw-cpuid'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '9.0.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-26307'}, {'type': 'WEB', 'url': 'https://github.com/gz/rust-cpuid/issues/40'}, {'type': 'WEB', 'url': 'https://github.com/gz/rust-cpuid/issues/41'}, {'type': 'WEB', 'url': 'https://github.com/RustSec/advisory-db/pull/614'}, {'type': 'WEB', 'url': 'https://github.com/gz/rust-cpuid/commit/91b676eecd01f2163e2984215e2c0ac89e30ce75'}, {'type': 'PACKAGE', 'url': 'https://github.com/gz/rust-cpuid'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0013.html'}]
|
{'cwe_ids': ['CWE-400', 'CWE-657'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:02:32Z', 'nvd_published_at': '2021-01-29T03:15:00Z'}
|
1.4.0
|
GHSA-8q64-wrfr-q48c
|
2021-08-24T17:59:47Z
|
2021-08-25T20:59:24Z
|
2021-08-24T17:59:47Z
|
[]
|
Data races in model
|
`Shared` data structure in `model` crate implements `Send` and `Sync` traits regardless of the inner type.
This allows safe Rust code to trigger a data race, which is undefined behavior in Rust.
Users are advised to treat `Shared` as an unsafe type.
It should not be used outside of the testing context,
and care must be taken so that the testing code does not have a data race
besides a race condition that is expected to be caught by the test.
Check [the Rustonomicon](https://doc.rust-lang.org/nomicon/races.html) for the difference between
a data race and a general race condition.
|
[]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'model'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.1.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/spacejam/model/issues/3'}, {'type': 'PACKAGE', 'url': 'https://github.com/spacejam/model'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0140.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-09T17:22:47Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-9658-c26v-7qvf
|
2021-08-19T16:50:37Z
|
2021-08-25T20:55:30Z
| null |
['CVE-2021-27377']
|
Use-after-free in yottadb
|
An issue was discovered in the yottadb crate before 1.2.0 for Rust. For some memory-allocation patterns, ydb_subscript_next_st and ydb_subscript_prev_st have a use-after-free.
|
[{'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': 'crates.io', 'name': 'yottadb'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.2.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-27377'}, {'type': 'PACKAGE', 'url': 'https://gitlab.com/YottaDB/Lang/YDBRust'}, {'type': 'WEB', 'url': 'https://gitlab.com/YottaDB/Lang/YDBRust/-/issues/40'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0022.html'}]
|
{'cwe_ids': ['CWE-416'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T16:50:37Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-rm4w-6696-r77p
|
2023-06-13T18:30:56Z
|
2021-08-25T20:52:14Z
| null |
['CVE-2021-27376']
|
nb-connect invalidly assumes the memory layout of std::net::SocketAddr
|
The nb-connect crate has assumed std::net::SocketAddrV4 and std::net::SocketAddrV6 have the same memory layout as the system C representation sockaddr. It has simply casted the pointers to convert the socket addresses to the system representation. The standard library does not say anything about the memory layout, and this will cause invalid memory access if the standard library changes the implementation. No warnings or errors will be emitted once the change happens.
|
[{'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': 'crates.io', 'name': 'nb-connect'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.0.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-27376'}, {'type': 'WEB', 'url': 'https://github.com/smol-rs/nb-connect/issues/1'}, {'type': 'PACKAGE', 'url': 'https://github.com/smol-rs/nb-connect'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0021.html'}]
|
{'cwe_ids': ['CWE-119'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:34:37Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-2q8x-2p7f-574v
|
2022-02-08T20:43:56Z
|
2021-08-25T14:46:49Z
| null |
['CVE-2021-39153']
|
XStream is vulnerable to an Arbitrary Code Execution attack
|
### Impact
The vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream, if using the version out of the box with Java runtime version 14 to 8 or with JavaFX installed. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.
### Patches
XStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.
### Workarounds
See [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.
### References
See full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-39153](https://x-stream.github.io/CVE-2021-39153.html).
### Credits
Ceclin and YXXX from the Tencent Security Response Center found and reported the issue to XStream and provided the required information to reproduce it.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)
* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)
|
[{'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': 'Maven', 'name': 'com.thoughtworks.xstream:xstream'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.4.18'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/x-stream/xstream/security/advisories/GHSA-2q8x-2p7f-574v'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39153'}, {'type': 'PACKAGE', 'url': 'https://github.com/x-stream/xstream'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2021/09/msg00017.html'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/22KVR6B5IZP3BGQ3HPWIO2FWWCKT3DHP/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PVPHZA7VW2RRSDCOIPP2W6O5ND254TU7/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QGXIU3YDPG6OGTDHMBLAFN7BPBERXREB/'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20210923-0003/'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2021/dsa-5004'}, {'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'}, {'type': 'WEB', 'url': 'https://x-stream.github.io/CVE-2021-39153.html'}]
|
{'cwe_ids': ['CWE-502'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T18:22:32Z', 'nvd_published_at': '2021-08-23T18:15:00Z'}
|
1.4.0
|
GHSA-c5x2-p679-95wc
|
2021-08-23T19:27:50Z
|
2021-08-25T14:43:32Z
| null |
['CVE-2021-37647']
|
Null pointer dereference in `SparseTensorSliceDataset`
|
### Impact
When a user does not supply arguments that determine a valid sparse tensor, `tf.raw_ops.SparseTensorSliceDataset` implementation can be made to dereference a null pointer:
```python
import tensorflow as tf
tf.raw_ops.SparseTensorSliceDataset(
indices=[[],[],[]],
values=[1,2,3],
dense_shape=[3,3])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L240-L251) has some argument validation but fails to consider the case when either `indices` or `values` are provided for an empty sparse tensor when the other is not.
If `indices` is empty (as in the example above), then [code that performs validation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L260-L261) (i.e., checking that the indices are monotonically increasing) results in a null pointer dereference:
```cc
for (int64_t i = 0; i < indices->dim_size(0); ++i) {
int64_t next_batch_index = indices->matrix<int64>()(i, 0);
...
}
```
If `indices` as provided by the user is empty, then `indices` in the C++ code above is backed by an empty `std::vector`, hence calling `indices->dim_size(0)` results in null pointer dereferencing (same as calling `std::vector::at()` on an empty vector).
### Patches
We have patched the issue in GitHub commit [02cc160e29d20631de3859c6653184e3f876b9d7](https://github.com/tensorflow/tensorflow/commit/02cc160e29d20631de3859c6653184e3f876b9d7).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-c5x2-p679-95wc'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37647'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/02cc160e29d20631de3859c6653184e3f876b9d7'}]
|
{'cwe_ids': ['CWE-476'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T19:27:50Z', 'nvd_published_at': '2021-08-12T19:15:00Z'}
|
1.4.0
|
GHSA-hgjr-632x-qpp3
|
2021-08-26T15:08:57Z
|
2021-08-30T16:18:59Z
| null |
['CVE-2021-39136']
|
Cross-site scripting vulnerability in file upload
|
There is a cross-site scripting vulnerability in file upload on the management system of baserCMS.
This is a vulnerability that needs to be addressed when the management system is used by an unspecified number of users.
If you are eligible, please update to the new version as soon as possible.
### Target
baserCMS 4.5.1 and earlier versions
### Vulnerability
Execution of malicious JavaScript code may alter the display of the page or leak cookie information.
### Countermeasures
Update to the latest version of baserCMS
Please refer to the next page for details.
https://basercms.net/security/JVN_14134801
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'baserproject/basercms'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.5.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 4.5.0'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/baserproject/basercms/security/advisories/GHSA-hgjr-632x-qpp3'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39136'}, {'type': 'WEB', 'url': 'https://github.com/baserproject/basercms/commit/568d4cab5ba1cdee7bbf0133c676d02a98f6d7bc'}, {'type': 'WEB', 'url': 'https://basercms.net/security/JVN_14134801'}, {'type': 'PACKAGE', 'url': 'https://github.com/baserproject/basercms'}, {'type': 'WEB', 'url': 'http://jvn.jp/en/jp/JVN14134801/index.html'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-26T15:08:57Z', 'nvd_published_at': '2021-08-25T18:15:00Z'}
|
1.4.0
|
GHSA-3jc5-5hc5-33gj
|
2023-06-13T17:00:10Z
|
2021-08-25T20:50:49Z
| null |
['CVE-2020-36208']
|
Data races in conquer-once
|
Affected versions of conquer-once implements Sync for its OnceCell type without restricting it to Sendable types.
This allows non-Send but Sync types such as MutexGuard to be sent across threads leading to undefined behavior and memory corruption in concurrent programs.
The issue was fixed by adding a Send constraint to OnceCell.
|
[{'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': 'crates.io', 'name': 'conquer-once'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.3.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36208'}, {'type': 'WEB', 'url': 'https://github.com/oliver-giersch/conquer-once/issues/3'}, {'type': 'PACKAGE', 'url': 'https://github.com/oliver-giersch/conquer-once'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0101.html'}]
|
{'cwe_ids': ['CWE-662', 'CWE-787'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:51:18Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-hvqc-pc78-x9wh
|
2023-06-13T20:30:27Z
|
2021-08-25T20:53:10Z
| null |
['CVE-2021-26306']
|
Soundness issue in raw-cpuid
|
VendorInfo::as_string(), SoCVendorBrand::as_string(), and ExtendedFunctionInfo::processor_brand_string() construct byte slices using std::slice::from_raw_parts(), with data coming from #[repr(Rust)] structs. This is always undefined behavior.
This flaw has been fixed in v9.0.0, by making the relevant structs #[repr(C)].
|
[{'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': 'crates.io', 'name': 'raw-cpuid'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '9.0.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-26306'}, {'type': 'WEB', 'url': 'https://github.com/gz/rust-cpuid/issues/40'}, {'type': 'WEB', 'url': 'https://github.com/RustSec/advisory-db/pull/614'}, {'type': 'PACKAGE', 'url': 'https://github.com/gz/rust-cpuid'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0013.html'}]
|
{'cwe_ids': ['CWE-198', 'CWE-400'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:02:19Z', 'nvd_published_at': '2021-01-29T03:15:00Z'}
|
1.4.0
|
GHSA-9jjr-qqfp-ppwx
|
2021-08-26T14:47:49Z
|
2021-08-30T16:16:58Z
| null |
['CVE-2021-39159']
|
remote code execution via git repo provider
|
### Impact
A remote code execution vulnerability has been identified in BinderHub, where providing BinderHub with maliciously crafted input could execute code in the BinderHub context, with the potential to egress credentials of the BinderHub deployment, including JupyterHub API tokens, kubernetes service accounts, and docker registry credentials. This may provide the ability to manipulate images and other user created pods in the deployment, with the potential to escalate to the host depending on the underlying kubernetes configuration.
### Patches
Patch below, or [on GitHub](https://github.com/jupyterhub/binderhub/commit/195caac172690456dcdc8cc7a6ca50e05abf8182.patch)
```diff
From 9f4043d9dddc1174920e687773f27b7933f48ab6 Mon Sep 17 00:00:00 2001
From: Riccardo Castellotti <rcastell@cern.ch>
Date: Thu, 19 Aug 2021 15:49:43 +0200
Subject: [PATCH] Explicitly separate git-ls-remote options from positional
arguments
---
binderhub/repoproviders.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/binderhub/repoproviders.py b/binderhub/repoproviders.py
index f33347b..5d4b87c 100755
--- a/binderhub/repoproviders.py
+++ b/binderhub/repoproviders.py
@@ -484,7 +484,7 @@ class GitRepoProvider(RepoProvider):
self.sha1_validate(self.unresolved_ref)
except ValueError:
# The ref is a head/tag and we resolve it using `git ls-remote`
- command = ["git", "ls-remote", self.repo, self.unresolved_ref]
+ command = ["git", "ls-remote", "--", self.repo, self.unresolved_ref]
result = subprocess.run(command, universal_newlines=True, stdout=subprocess.PIPE, stderr=subprocess.PIPE)
if result.returncode:
raise RuntimeError("Unable to run git ls-remote to get the `resolved_ref`: {}".format(result.stderr))
--
2.25.1
```
### Workarounds
Disable the git repo provider by specifying the `BinderHub.repo_providers` config, e.g.:
```python
from binderhub.repoproviders import (GitHubRepoProvider,
GitLabRepoProvider, GistRepoProvider,
ZenodoProvider, FigshareProvider, HydroshareProvider,
DataverseProvider)
c.BinderHub.repo_providers = {
'gh': GitHubRepoProvider,
'gist': GistRepoProvider,
'gl': GitLabRepoProvider,
'zenodo': ZenodoProvider,
'figshare': FigshareProvider,
'hydroshare': HydroshareProvider,
'dataverse': DataverseProvider,
}
```
### References
Credit: Jose Carlos Luna Duran (CERN) and Riccardo Castellotti (CERN).
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@ipython.org](mailto:security@ipython.org)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'binderhub'}, 'ecosystem_specific': {'affected_functions': ['binderhub.repoproviders.GitRepoProvider.get_resolved_ref']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.2.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/jupyterhub/binderhub/security/advisories/GHSA-9jjr-qqfp-ppwx'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39159'}, {'type': 'WEB', 'url': 'https://github.com/jupyterhub/binderhub/commit/195caac172690456dcdc8cc7a6ca50e05abf8182'}, {'type': 'WEB', 'url': 'https://github.com/jupyterhub/binderhub/commit/195caac172690456dcdc8cc7a6ca50e05abf8182.patch'}, {'type': 'PACKAGE', 'url': 'https://github.com/jupyterhub/binderhub'}]
|
{'cwe_ids': ['CWE-78', 'CWE-94'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-25T15:20:56Z', 'nvd_published_at': '2021-08-25T19:15:00Z'}
|
1.4.0
|
GHSA-fg42-vwxx-xx5j
|
2023-06-13T22:05:30Z
|
2021-08-25T20:58:53Z
| null |
['CVE-2020-36438']
|
Data race in tiny_future
|
tiny_future contains a light-weight implementation of Futures. The Future type it has lacked bound on its Send and Sync traits. This allows for a bug where non-thread safe types such as Cell can be used in Futures and cause data races in concurrent programs. The flaw was corrected in commit `c791919` by adding trait bounds to Future's Send and Sync.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'tiny_future'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36438'}, {'type': 'WEB', 'url': 'https://github.com/KizzyCode/tiny_future/issues/1'}, {'type': 'WEB', 'url': 'https://github.com/KizzyCode/tiny_future-rust/commit/c7919199a0f6d1ce0e3c33499d1b37f862c990e4'}, {'type': 'PACKAGE', 'url': 'https://github.com/KizzyCode/tiny_future'}, {'type': 'WEB', 'url': 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/tiny_future/RUSTSEC-2020-0118.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0118.html'}]
|
{'cwe_ids': ['CWE-119', 'CWE-362'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-09T22:41:30Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-wp34-mqw5-jj85
|
2023-06-13T20:02:46Z
|
2021-08-25T20:52:00Z
| null |
['CVE-2021-28032']
|
Use after free in nano_arena
|
Affected versions of this crate assumed that Borrow<Idx> was guaranteed to return the same value on .borrow(). The borrowed index value was used to retrieve a mutable reference to a value.
If the Borrow<Idx> implementation returned a different index, the split arena would allow retrieving the index as a mutable reference creating two mutable references to the same element. This violates Rust's aliasing rules and allows for memory safety issues such as writing out of bounds and use-after-frees.
The flaw was corrected in commit `6b83f9d` by storing the .borrow() value in a temporary variable.
|
[{'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': 'crates.io', 'name': 'nano_arena'}, 'ecosystem_specific': {'affected_functions': ['nano_arena::Arena::split_at', 'nano_arena::ArenaSplit::split_at']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.5.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-28032'}, {'type': 'WEB', 'url': 'https://github.com/bennetthardwick/nano-arena/issues/1'}, {'type': 'WEB', 'url': 'https://github.com/bennetthardwick/nano-arena/commit/6b83f9d0708337a9f8b709c1624a8587021ceba2'}, {'type': 'PACKAGE', 'url': 'https://github.com/bennetthardwick/nano-arena'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0031.html'}]
|
{'cwe_ids': ['CWE-416'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:23:52Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-v5m7-53cv-f3hx
|
2022-08-10T23:46:00Z
|
2021-08-25T21:01:13Z
| null |
['CVE-2020-15254']
|
crossbeam-channel Undefined Behavior before v0.4.4
|
### Impact
The affected version of this crate's the `bounded` channel incorrectly assumes that `Vec::from_iter` has allocated capacity that same as the number of iterator elements. `Vec::from_iter` does not actually guarantee that and may allocate extra memory. The destructor of the `bounded` channel reconstructs `Vec` from the raw pointer based on the incorrect assumes described above. This is unsound and causing deallocation with the incorrect capacity when `Vec::from_iter` has allocated different sizes with the number of iterator elements.
### Patches
This has been fixed in crossbeam-channel 0.4.4.
We recommend users to upgrade to 0.4.4.
### References
See https://github.com/crossbeam-rs/crossbeam/pull/533, https://github.com/crossbeam-rs/crossbeam/issues/539, and https://github.com/RustSec/advisory-db/pull/425 for more details.
### License
This advisory is in the public domain.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'crossbeam-channel'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.4.3'}, {'fixed': '0.4.4'}]}], 'versions': ['0.4.3']}]
|
[{'type': 'WEB', 'url': 'https://github.com/crossbeam-rs/crossbeam/security/advisories/GHSA-v5m7-53cv-f3hx'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15254'}, {'type': 'WEB', 'url': 'https://github.com/crossbeam-rs/crossbeam/issues/539'}, {'type': 'WEB', 'url': 'https://github.com/RustSec/advisory-db/pull/425'}, {'type': 'WEB', 'url': 'https://github.com/crossbeam-rs/crossbeam/pull/533'}, {'type': 'PACKAGE', 'url': 'https://github.com/crossbeam-rs/crossbeam'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0052.html'}]
|
{'cwe_ids': ['CWE-119', 'CWE-401'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-03T22:53:34Z', 'nvd_published_at': '2020-10-16T17:15:00Z'}
|
1.4.0
|
GHSA-m833-jv95-mfjh
|
2021-08-19T20:56:31Z
|
2021-08-25T20:48:50Z
| null |
['CVE-2020-35889']
|
Memory safety violation in crayon
|
An issue was discovered in the crayon crate through 2020-08-31 for Rust. A TOCTOU issue has a resultant memory safety violation via HandleLike.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'crayon'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.7.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35889'}, {'type': 'WEB', 'url': 'https://github.com/shawnscode/crayon/issues/87'}, {'type': 'PACKAGE', 'url': 'https://github.com/shawnscode/crayon'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0037.html'}]
|
{'cwe_ids': ['CWE-367'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T20:56:31Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-vxhc-c4qm-647p
|
2021-10-21T13:35:03Z
|
2021-08-11T15:18:11Z
| null |
['CVE-2021-25954']
|
Improper Access Control in Dolibarr
|
In “Dolibarr” application, 2.8.1 to 13.0.4 don’t restrict or incorrectly restricts access to a resource from an unauthorized actor. A low privileged attacker can modify the Private Note which only an administrator has rights to do, the affected field is at “/adherents/note.php?id=1” endpoint.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'dolibarr/dolibarr'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.8.1'}, {'fixed': '14.0.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-25954'}, {'type': 'WEB', 'url': 'https://github.com/Dolibarr/dolibarr/commit/8cc100012d46282799fb19f735a53b7101569377'}, {'type': 'PACKAGE', 'url': 'https://github.com/Dolibarr/dolibarr'}, {'type': 'WEB', 'url': 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25954'}]
|
{'cwe_ids': ['CWE-284', 'CWE-863'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-10T17:28:01Z', 'nvd_published_at': '2021-08-09T17:15:00Z'}
|
1.4.0
|
GHSA-j52m-489x-v634
|
2023-06-13T17:45:35Z
|
2021-08-25T20:44:13Z
| null |
['CVE-2019-16880']
|
Double free in linea
|
Affected versions of this crate did not properly implements the Matrix::zip_elements method, which causes an double free when the given trait implementation might panic. This allows an attacker to corrupt or take control of the memory.
|
[{'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': 'crates.io', 'name': 'linea'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.9.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-16880'}, {'type': 'WEB', 'url': 'https://github.com/strake/linea.rs/issues/2'}, {'type': 'PACKAGE', 'url': 'https://github.com/strake/linea.rs'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0021.html'}]
|
{'cwe_ids': ['CWE-415'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:23:06Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-2wc6-2rcj-8v76
|
2023-06-13T20:56:05Z
|
2021-08-25T21:00:41Z
| null |
['CVE-2017-1000168']
|
scalarmult() vulnerable to degenerate public keys
|
The scalarmult() function included in previous versions of this crate accepted all-zero public keys, for which the resulting Diffie-Hellman shared secret will always be zero regardless of the private key used.
This issue was fixed by checking for this class of keys and rejecting them if they are used.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'sodiumoxide'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.0.14'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2017-1000168'}, {'type': 'WEB', 'url': 'https://github.com/dnaq/sodiumoxide/issues/154'}, {'type': 'WEB', 'url': 'https://github.com/sodiumoxide/sodiumoxide/commit/24c7a5550807ac8a09648b5878f19d14c3a69135'}, {'type': 'PACKAGE', 'url': 'https://github.com/sodiumoxide/sodiumoxide'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2017-0001.html'}]
|
{'cwe_ids': ['CWE-1240'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-05T21:10:47Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-f865-m6cq-j9vx
|
2021-10-08T20:45:06Z
|
2021-08-09T20:44:51Z
| null |
['CVE-2021-29063']
|
ReDOS in Mpmath
|
A Regular Expression Denial of Service (ReDOS) vulnerability was discovered in Mpmath v1.0.0 when the mpmathify function is called.
|
[{'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': 'PyPI', 'name': 'mpmath'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.3.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-29063'}, {'type': 'WEB', 'url': 'https://github.com/fredrik-johansson/mpmath/issues/548'}, {'type': 'WEB', 'url': 'https://github.com/mpmath/mpmath/pull/570'}, {'type': 'WEB', 'url': 'https://github.com/npm/hosted-git-info/pull/76'}, {'type': 'WEB', 'url': 'https://github.com/fredrik-johansson/mpmath/commit/46d44c3c8f3244017fe1eb102d564eb4ab8ef750'}, {'type': 'WEB', 'url': 'https://github.com/fredrik-johansson/mpmath/commit/c811b37c65a4372a7ce613111d2a508c204f9833'}, {'type': 'WEB', 'url': 'https://github.com/mpmath/mpmath/commit/c811b37c65a4372a7ce613111d2a508c204f9833'}, {'type': 'PACKAGE', 'url': 'https://github.com/fredrik-johansson/mpmath'}, {'type': 'WEB', 'url': 'https://github.com/mpmath/mpmath/releases/tag/1.3.0'}, {'type': 'WEB', 'url': 'https://github.com/pypa/advisory-database/tree/main/vulns/mpmath/PYSEC-2021-427.yaml'}, {'type': 'WEB', 'url': 'https://github.com/yetingli/PoCs/blob/main/CVE-2021-29063/Mpmath.md'}, {'type': 'WEB', 'url': 'https://github.com/yetingli/SaveResults/blob/main/js/hosted-git-info.js'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3M5O55E7VUDMXCPQR6MQTOIFDKHP36AA/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EIUX3XWY2K3MSO7QXMZXQQYAURARSPC5/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MS2U6GLXQSRZJE2HVUAUMVFR2DWQLCZG/'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/package/hosted-git-info'}]
|
{'cwe_ids': ['CWE-770'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-06-22T16:00:52Z', 'nvd_published_at': '2021-06-21T20:15:00Z'}
|
1.4.0
|
GHSA-hh27-ffr2-f2jc
|
2021-08-10T16:06:59Z
|
2021-08-10T16:07:08Z
| null |
['CVE-2021-3664']
|
Open redirect in url-parse
|
# Overview
Affected versions of npm `url-parse` are vulnerable to URL Redirection to Untrusted Site.
# Impact
Depending on library usage and attacker intent, impacts may include allow/block list bypasses, SSRF attacks, open redirects, or other undesired behavior.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'url-parse'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.5.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3664'}, {'type': 'WEB', 'url': 'https://github.com/unshiftio/url-parse/issues/205'}, {'type': 'WEB', 'url': 'https://github.com/unshiftio/url-parse/issues/206'}, {'type': 'WEB', 'url': 'https://github.com/unshiftio/url-parse/commit/81ab967889b08112d3356e451bf03e6aa0cbb7e0'}, {'type': 'PACKAGE', 'url': 'https://github.com/unshiftio/url-parse'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/1625557993985-unshiftio/url-parse'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2023/02/msg00030.html'}]
|
{'cwe_ids': ['CWE-601'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-02T21:28:20Z', 'nvd_published_at': '2021-07-26T12:15:00Z'}
|
1.4.0
|
GHSA-6wf9-jmg9-vxcc
|
2022-02-08T20:59:06Z
|
2021-08-25T14:48:39Z
| null |
['CVE-2021-39140']
|
XStream can cause a Denial of Service
|
### Impact
The vulnerability may allow a remote attacker to allocate 100% CPU time on the target system depending on CPU type or parallel execution of such a payload resulting in a denial of service only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.
### Patches
XStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.
### Workarounds
See [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.
### References
See full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-39140](https://x-stream.github.io/CVE-2021-39140.html).
### Credits
The vulnerability was discovered and reported by Lai Han of nsfocus security team.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)
* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'com.thoughtworks.xstream:xstream'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.4.18'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/x-stream/xstream/security/advisories/GHSA-6wf9-jmg9-vxcc'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39140'}, {'type': 'PACKAGE', 'url': 'https://github.com/x-stream/xstream'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2021/09/msg00017.html'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/22KVR6B5IZP3BGQ3HPWIO2FWWCKT3DHP/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PVPHZA7VW2RRSDCOIPP2W6O5ND254TU7/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QGXIU3YDPG6OGTDHMBLAFN7BPBERXREB/'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20210923-0003/'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2021/dsa-5004'}, {'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'}, {'type': 'WEB', 'url': 'https://x-stream.github.io/CVE-2021-39140.html'}]
|
{'cwe_ids': ['CWE-502', 'CWE-835'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T18:22:01Z', 'nvd_published_at': '2021-08-23T19:15:00Z'}
|
1.4.0
|
GHSA-xp5q-77mh-6hm2
|
2021-08-24T20:02:07Z
|
2021-08-25T14:50:17Z
| null |
['CVE-2021-3728']
|
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:N/A:H'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'grumpydictator/firefly-iii'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '5.6.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3728'}, {'type': 'WEB', 'url': 'https://github.com/firefly-iii/firefly-iii/commit/14cdce113e0eb8090d09066fcd2b5cf03b5ac84e'}, {'type': 'PACKAGE', 'url': 'https://github.com/firefly-iii/firefly-iii/'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/dd54c5a1-0d4a-4f02-a111-7ce4ddc67a4d'}]
|
{'cwe_ids': ['CWE-352'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T20:02:07Z', 'nvd_published_at': '2021-08-23T13:15:00Z'}
|
1.4.0
|
GHSA-mmc9-pwm7-qj5w
|
2021-08-18T20:45:24Z
|
2021-08-25T20:56:50Z
| null |
['CVE-2020-25576']
|
Unaligned memory access in rand_core
|
### Impact
Affected versions of this crate violated alignment when casting byte slices to integer slices, resulting in undefined behavior. `rand_core::BlockRng::next_u64` and `rand_core::BlockRng::fill_bytes` are affected.
### Patches
The flaw was corrected by Ralf Jung and Diggory Hardy for `rand_core >= 0.4.2`.
### Workarounds
None.
### References
See [Rand's changelog](https://github.com/rust-random/rand/blob/master/rand_core/CHANGELOG.md#050---2019-06-06).
### For more information
If you have any questions or comments about this advisory, [open an issue in the Rand repository](https://github.com/rust-random/rand/issues/new/choose).
|
[{'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': 'crates.io', 'name': 'rand_core'}, 'ecosystem_specific': {'affected_functions': ['rand_core::BlockRng::fill_bytes', 'rand_core::BlockRng::next_u64']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.4.0'}, {'fixed': '0.4.2'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'rand_core'}, 'ecosystem_specific': {'affected_functions': ['rand_core::BlockRng::fill_bytes', 'rand_core::BlockRng::next_u64']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.3.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/rust-random/rand/security/advisories/GHSA-mmc9-pwm7-qj5w'}, {'type': 'PACKAGE', 'url': 'https://github.com/rust-random/rand'}, {'type': 'WEB', 'url': 'https://github.com/rust-random/rand/blob/master/rand_core/CHANGELOG.md#050---2019-06-06'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0035.html'}]
|
{'cwe_ids': ['CWE-704'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T20:45:24Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-pq6v-x7gp-7776
|
2021-08-19T21:25:09Z
|
2021-08-25T20:43:09Z
| null |
['CVE-2016-10933']
|
Source code is downloaded over cleartext HTTP in portaudio
|
An issue was discovered in the portaudio crate through 0.7.0 for Rust. There is a man-in-the-middle issue because the source code is downloaded over cleartext HTTP.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'portaudio'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.7.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2016-10933'}, {'type': 'WEB', 'url': 'https://github.com/RustAudio/rust-portaudio/issues/144'}, {'type': 'PACKAGE', 'url': 'https://github.com/RustAudio/rust-portaudio'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2016-0003.html'}]
|
{'cwe_ids': ['CWE-319'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:25:09Z', 'nvd_published_at': '2019-08-26T13:15:00Z'}
|
1.4.0
|
GHSA-xr7r-88qv-q7hm
|
2023-06-13T21:04:01Z
|
2021-08-25T20:45:51Z
| null |
['CVE-2019-25001']
|
Out of bounds write in serde_cbor
|
Affected versions of this crate did not properly check if semantic tags were nested excessively during deserialization. This allows an attacker to craft small (< 1 kB) CBOR documents that cause a stack overflow. The flaw was corrected by limiting the allowed number of nested tags.
|
[{'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': 'crates.io', 'name': 'serde_cbor'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.10.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-25001'}, {'type': 'WEB', 'url': 'https://github.com/pyfisch/cbor/pull/153'}, {'type': 'WEB', 'url': 'https://github.com/pyfisch/cbor/commit/1aec4f9d71855dbfb223fa61ca60260400cc5d5f'}, {'type': 'PACKAGE', 'url': 'https://github.com/pyfisch/cbor'}, {'type': 'WEB', 'url': 'https://github.com/pyfisch/cbor/releases/tag/v0.10.2'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0025.html'}]
|
{'cwe_ids': ['CWE-787'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:20:43Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-qgm6-9472-pwq7
|
2022-02-08T21:34:31Z
|
2021-08-25T20:52:19Z
| null |
['CVE-2021-23840']
|
Integer Overflow in openssl-src
|
Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output length value will be negative. This could cause applications to behave incorrectly or crash. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).
|
[{'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': 'crates.io', 'name': 'openssl-src'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '111.14.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-23840'}, {'type': 'WEB', 'url': 'https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf'}, {'type': 'WEB', 'url': 'https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=6a51b9e1d0cf0bf8515f7201b68fb0a3482b3dc1'}, {'type': 'WEB', 'url': 'https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=9b1129239f3ebb1d1c98ce9ed41d5c9476c47cb2'}, {'type': 'PACKAGE', 'url': 'https://github.com/alexcrichton/openssl-src-rs'}, {'type': 'WEB', 'url': 'https://kb.pulsesecure.net/articles/Pulse_Security_Advisories/SA44846'}, {'type': 'WEB', 'url': 'https://kc.mcafee.com/corporate/index?page=content&id=SB10366'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r58af02e294bd07f487e2c64ffc0a29b837db5600e33b6e698b9d696b@%3Cissues.bookkeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rf4c02775860db415b4955778a131c2795223f61cb8c6a450893651e4@%3Cissues.bookkeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0057.html'}, {'type': 'WEB', 'url': 'https://security.gentoo.org/glsa/202103-03'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20210219-0009/'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2021/dsa-4855'}, {'type': 'WEB', 'url': 'https://www.openssl.org/news/secadv/20210216.txt'}, {'type': 'WEB', 'url': 'https://www.oracle.com//security-alerts/cpujul2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuApr2021.html'}, {'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/cpuoct2021.html'}, {'type': 'WEB', 'url': 'https://www.tenable.com/security/tns-2021-03'}, {'type': 'WEB', 'url': 'https://www.tenable.com/security/tns-2021-09'}, {'type': 'WEB', 'url': 'https://www.tenable.com/security/tns-2021-10'}]
|
{'cwe_ids': ['CWE-190'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:35:16Z', 'nvd_published_at': '2021-02-16T17:15:00Z'}
|
1.4.0
|
GHSA-6gv8-p3vj-pxvr
|
2021-08-23T21:14:27Z
|
2021-08-25T14:43:27Z
| null |
['CVE-2021-37649']
|
Null pointer dereference in `UncompressElement`
|
### Impact
The code for `tf.raw_ops.UncompressElement` can be made to trigger a null pointer dereference:
```python
import tensorflow as tf
data = tf.data.Dataset.from_tensors([0.0])
tf.raw_ops.UncompressElement(
compressed=tf.data.experimental.to_variant(data),
output_types=[tf.int64],
output_shapes=[2])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/data/experimental/compression_ops.cc#L50-L53) obtains a pointer to a `CompressedElement` from a `Variant` tensor and then proceeds to dereference it for decompressing. There is no check that the `Variant` tensor contained a `CompressedElement`, so the pointer is actually `nullptr`.
### Patches
We have patched the issue in GitHub commit [7bdf50bb4f5c54a4997c379092888546c97c3ebd](https://github.com/tensorflow/tensorflow/commit/7bdf50bb4f5c54a4997c379092888546c97c3ebd).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-6gv8-p3vj-pxvr'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37649'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/7bdf50bb4f5c54a4997c379092888546c97c3ebd'}]
|
{'cwe_ids': ['CWE-476'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T21:14:27Z', 'nvd_published_at': '2021-08-12T19:15:00Z'}
|
1.4.0
|
GHSA-96w3-p368-4h8c
|
2023-06-13T18:17:00Z
|
2021-08-25T20:46:51Z
| null |
['CVE-2020-35874']
|
Use after free in internment
|
ArcIntern::drop has a race condition where it can release memory which is about to get another user. The new user will get a reference to freed memory.
This was fixed by serializing access to an interned object while it is being deallocated.
Versions prior to 0.3.12 used stronger locking which avoided the problem.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'internment'}, 'ecosystem_specific': {'affected_functions': ['internment::ArcIntern::drop']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.3.12'}, {'fixed': '0.4.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35874'}, {'type': 'WEB', 'url': 'https://github.com/droundy/internment/issues/11'}, {'type': 'PACKAGE', 'url': 'https://github.com/droundy/internment'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0017.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:19:06Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-vc2p-r46x-m3vx
|
2021-08-18T20:59:57Z
|
2021-08-25T20:56:48Z
| null |
['CVE-2020-28247']
|
Argument injection in lettre
|
### Impact
Affected versions of lettre allowed argument injection to the sendmail command. It was possible, using forged to addresses, to pass arbitrary arguments to the sendmail executable.
Depending on the implementation (original sendmail, postfix, exim, etc.) it could be possible in some cases to write email data into abritrary files (using sendmail's logging features).
*NOTE*: This vulnerability only affects the sendmail transport. Others, including smtp, are not affected.
### Fix
The flaw is corrected by modifying the executed command to stop parsing arguments before passing the destination addresses.
### References
* [RUSTSEC-2020-0069](https://rustsec.org/advisories/RUSTSEC-2020-0069.html)
* [CVE-2020-28247](https://nvd.nist.gov/vuln/detail/CVE-2020-28247)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'lettre'}, 'ecosystem_specific': {'affected_functions': ['lettre::sendmail::SendmailTransport::send', 'lettre::transport::sendmail::SendmailTransport::send', 'lettre::transport::sendmail::SendmailTransport::send_raw']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.9.0'}, {'fixed': '0.9.5'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'lettre'}, 'ecosystem_specific': {'affected_functions': ['lettre::sendmail::SendmailTransport::send', 'lettre::transport::sendmail::SendmailTransport::send', 'lettre::transport::sendmail::SendmailTransport::send_raw']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.8.0'}, {'fixed': '0.8.4'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'lettre'}, 'ecosystem_specific': {'affected_functions': ['lettre::sendmail::SendmailTransport::send', 'lettre::transport::sendmail::SendmailTransport::send', 'lettre::transport::sendmail::SendmailTransport::send_raw']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.7.0'}, {'fixed': '0.7.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/lettre/lettre/security/advisories/GHSA-vc2p-r46x-m3vx'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-28247'}, {'type': 'WEB', 'url': 'https://github.com/RustSec/advisory-db/pull/478/files'}, {'type': 'WEB', 'url': 'https://github.com/lettre/lettre/pull/508/commits/bbe7cc5381c5380b54fb8bbb4f77a3725917ff0b'}, {'type': 'PACKAGE', 'url': 'https://github.com/lettre/lettre'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0069.html'}]
|
{'cwe_ids': ['CWE-77'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T20:59:57Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-r6ff-2q3c-v3pv
|
2021-08-09T17:13:06Z
|
2021-08-25T21:00:01Z
| null |
[]
|
Compiler optimisation leads to SEGFAULT
|
Affected versions of the `pnet` crate were optimized out by compiler, which caused dereference of uninitialized file descriptor which caused segfault.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'pnet'}, 'ecosystem_specific': {'affected_functions': ['pnet::transport::IcmpTransportChannelIterator']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.27.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/libpnet/libpnet/issues/449'}, {'type': 'WEB', 'url': 'https://github.com/libpnet/libpnet/pull/455'}, {'type': 'PACKAGE', 'url': 'https://github.com/libpnet/libpnet'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0037.html'}]
|
{'cwe_ids': ['CWE-908'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-09T17:13:06Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-gvcp-948f-8f2p
|
2021-08-18T19:04:08Z
|
2021-08-25T20:59:04Z
| null |
['CVE-2020-36443']
|
Use of Uninitialized Resource in libp2p-deflate
|
An issue was discovered in the libp2p-deflate crate before 0.27.1 for Rust. An uninitialized buffer is passed to AsyncRead::poll_read(), which is a user-provided trait function.
|
[{'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': 'crates.io', 'name': 'libp2p-deflate'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.27.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36443'}, {'type': 'PACKAGE', 'url': 'https://github.com/libp2p/rust-libp2p'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0123.html'}]
|
{'cwe_ids': ['CWE-908'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-09T22:18:41Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-pfjq-935c-4895
|
2023-06-13T22:27:40Z
|
2021-08-25T21:00:37Z
| null |
[]
|
Data races in v9
|
Affected versions of this crate unconditionally implement `Sync` for `SyncRef<T>`. This definition allows data races if `&T` is accessible through `&SyncRef`.
`SyncRef<T>` derives `Clone` and `Debug`, and the default implementations of those traits access `&T` by invoking `T::clone()` & `T::fmt()`. It is possible to create data races & undefined behavior by concurrently invoking `SyncRef<T>::clone()` or `SyncRef<T>::fmt()` from multiple threads with `T: !Sync`.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'v9'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.1.43'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/purpleposeidon/v9/issues/1'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0127.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-05T21:37:57Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-9xjr-m6f3-v5wm
|
2023-06-13T17:38:19Z
|
2021-08-25T20:43:06Z
| null |
['CVE-2016-10932']
|
HTTPS MitM vulnerability due to lack of hostname verification
|
When used on Windows platforms, all versions of Hyper prior to 0.9.4 did not perform hostname verification when making HTTPS requests.
This allows an attacker to perform MitM attacks by preventing any valid CA-issued certificate, even if there's a hostname mismatch.
The problem was addressed by leveraging rust-openssl's built-in support for hostname verification.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'hyper'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.9.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2016-10932'}, {'type': 'WEB', 'url': 'https://github.com/hyperium/hyper/issues/472'}, {'type': 'WEB', 'url': 'https://github.com/hyperium/hyper/commit/01160abd92956e5f995cc45790df7a2b86c8989f'}, {'type': 'WEB', 'url': 'https://github.com/hyperium/hyper/blob/master/CHANGELOG.md#v094-2016-05-09'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2016-0002.html'}]
|
{'cwe_ids': ['CWE-347'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:25:12Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-hr3c-6mmp-6m39
|
2023-06-13T20:55:45Z
|
2021-08-25T20:42:57Z
| null |
['CVE-2018-20995']
|
Memory corruption slice-deque
|
Affected versions of this crate did not properly update the head and tail of the deque when inserting and removing elements from the front if, before insertion or removal, the tail of the deque was in the mirrored memory region, and if, after insertion or removal, the head of the deque is exactly at the beginning of the mirrored memory region.
An attacker that controls both element insertion and removal into the deque could put it in a corrupted state. Once the deque enters such an state, its head and tail are corrupted, but in bounds of the allocated memory. This can result in partial reads and writes, reads of uninitialized memory, reads of memory containing previously dropped objects, etc. An attacker could exploit this to alter program execution.
The flaw was corrected by properly updating the head and tail of the deque in this case.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'slice-deque'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.1.16'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2018-20995'}, {'type': 'WEB', 'url': 'https://github.com/gnzlbg/slice_deque/issues/57'}, {'type': 'PACKAGE', 'url': 'https://github.com/gnzlbg/slice_deque'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2018-0008.html'}]
|
{'cwe_ids': ['CWE-119'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:25:30Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-5q2r-92f9-4m49
|
2021-10-27T17:03:38Z
|
2021-08-25T20:56:55Z
| null |
['CVE-2020-15093']
|
Improper verification of signature threshold in tough
|
## Impact
The tough library, prior to 0.7.1, does not properly verify the uniqueness of keys in the signatures provided to meet the threshold of cryptographic signatures. It allows someone with access to a valid signing key to create multiple valid signatures in order to circumvent TUF requiring a minimum threshold of unique keys before the metadata is considered valid.
AWS would like to thank Erick Tryzelaar of the Google Fuchsia Team for reporting this issue.
## Patches
A fix is available in version 0.7.1.
## Workarounds
No workarounds to this issue are known.
## References
CVE-2020-6174 is assigned to the same issue in the TUF reference implementation.
https://github.com/theupdateframework/tuf/pull/974
https://nvd.nist.gov/vuln/detail/CVE-2020-6174
## For more information
If you have any questions or comments about this advisory, [contact AWS Security](https://aws.amazon.com/security/vulnerability-reporting/) at [aws-security@amazon.com](mailto:aws-security@amazon.com).
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'tough'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.7.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/awslabs/tough/security/advisories/GHSA-5q2r-92f9-4m49'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15093'}, {'type': 'WEB', 'url': 'https://github.com/theupdateframework/tuf/pull/974'}, {'type': 'WEB', 'url': 'https://github.com/theupdateframework/tuf/commit/2977188139d065ff3356c3cb4aec60c582b57e0e'}, {'type': 'PACKAGE', 'url': 'https://github.com/awslabs/tough'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0024.html'}]
|
{'cwe_ids': ['CWE-347'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T20:40:25Z', 'nvd_published_at': '2020-07-09T19:15:00Z'}
|
1.4.0
|
GHSA-gh6x-4whr-2qv4
|
2021-08-23T18:18:09Z
|
2021-08-25T14:44:05Z
| null |
['CVE-2021-37639']
|
Null pointer dereference and heap OOB read in operations restoring tensors
|
### Impact
When restoring tensors via raw APIs, if the tensor name is not provided, TensorFlow can be tricked into dereferencing a null pointer:
```python
import tensorflow as tf
tf.raw_ops.Restore(
file_pattern=['/tmp'],
tensor_name=[],
default_value=21,
dt=tf.int,
preferred_shard=1)
```
The same undefined behavior can be triggered by `tf.raw_ops.RestoreSlice`:
```python
import tensorflow as tf
tf.raw_ops.RestoreSlice(
file_pattern=['/tmp'],
tensor_name=[],
shape_and_slice='2',
dt=inp.array([tf.int]),
preferred_shard=1)
```
Alternatively, attackers can read memory outside the bounds of heap allocated data by providing some tensor names but not enough for a successful restoration:
```python
import tensorflow as tf
tf.raw_ops.Restore(
file_pattern=['/tmp'],
tensor_name=['x'],
default_value=21,
dt=tf.int,
preferred_shard=42)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/save_restore_tensor.cc#L158-L159) retrieves the tensor list corresponding to the `tensor_name` user controlled input and immediately retrieves the tensor at the restoration index (controlled via `preferred_shard` argument). This occurs without validating that the provided list has enough values.
If the list is empty this results in dereferencing a null pointer (undefined behavior). If, however, the list has some elements, if the restoration index is outside the bounds this results in heap OOB read.
### Patches
We have patched the issue in GitHub commit [9e82dce6e6bd1f36a57e08fa85af213e2b2f2622](https://github.com/tensorflow/tensorflow/commit/9e82dce6e6bd1f36a57e08fa85af213e2b2f2622).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-gh6x-4whr-2qv4'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37639'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/9e82dce6e6bd1f36a57e08fa85af213e2b2f2622'}]
|
{'cwe_ids': ['CWE-125', 'CWE-476'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T18:18:09Z', 'nvd_published_at': '2021-08-12T19:15:00Z'}
|
1.4.0
|
GHSA-rxr4-x558-x7hw
|
2023-06-13T20:58:32Z
|
2021-08-25T20:42:54Z
| null |
['CVE-2018-20991']
|
Double free in smallvec
|
If an iterator passed to SmallVec::insert_many panicked in Iterator::next, destructors were run during unwinding while the vector was in an inconsistent state, possibly causing a double free (a destructor running on two copies of the same value).
This is fixed in smallvec 0.6.3 by ensuring that the vector's length is not updated to include moved items until they have been removed from their original positions. Items may now be leaked if Iterator::next panics, but they will not be dropped more than once.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'smallvec'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.3.2'}, {'fixed': '0.6.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2018-20991'}, {'type': 'WEB', 'url': 'https://github.com/servo/rust-smallvec/issues/96'}, {'type': 'PACKAGE', 'url': 'https://github.com/servo/rust-smallvec'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2018-0003.html'}]
|
{'cwe_ids': ['CWE-415'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:25:34Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-qf76-pr7x-h7r4
|
2021-04-22T23:02:07Z
|
2021-08-02T16:38:01Z
| null |
['CVE-2020-19676']
|
Incorrect Access Control in Nacos
|
Nacos 1.1.4 is affected by: Incorrect Access Control. An environment can be set up locally to get the service details interface. Then other Nacos service names can be accessed through the service list interface. Service details can then be accessed when not logged in. (detail:https://github.com/alibaba/nacos/issues/2284)
|
[{'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': 'com.alibaba.nacos:nacos-common'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.2.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-19676'}, {'type': 'WEB', 'url': 'https://github.com/alibaba/nacos/issues/1105'}, {'type': 'WEB', 'url': 'https://github.com/alibaba/nacos/issues/2284'}, {'type': 'WEB', 'url': 'https://github.com/alibaba/nacos/releases/tag/1.2.0'}]
|
{'cwe_ids': ['CWE-200'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-04-22T23:02:07Z', 'nvd_published_at': '2020-09-30T18:15:00Z'}
|
1.4.0
|
GHSA-3w8g-xr3f-2mp8
|
2021-08-24T18:08:59Z
|
2021-08-25T20:55:49Z
| null |
['CVE-2021-38190']
|
Out of bounds write in nalgebra
|
The `Deserialize` implementation for `VecStorage` did not maintain the invariant that the number of elements must equal `nrows * ncols`. Deserialization of specially crafted inputs could allow memory access beyond allocation of the vector.
This flaw was introduced in v0.11.0 ([`086e6e`](https://github.com/dimforge/nalgebra/commit/086e6e719f53fecba6dadad2e953a487976387f5)) due to the addition of an automatically derived implementation of `Deserialize` for `MatrixVec`. `MatrixVec` was later renamed to `VecStorage` in v0.16.13 ([`0f66403`](https://github.com/dimforge/nalgebra/commit/0f66403cbbe9eeac15cedd8a906c0d6a3d8841f2)) and continued to use the automatically derived implementation of `Deserialize`.
|
[{'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': 'crates.io', 'name': 'nalgebra'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.11.0'}, {'fixed': '0.27.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-38190'}, {'type': 'WEB', 'url': 'https://github.com/dimforge/nalgebra/issues/883'}, {'type': 'WEB', 'url': 'https://github.com/dimforge/nalgebra/pull/889'}, {'type': 'WEB', 'url': 'https://github.com/dimforge/nalgebra/commit/a803271fcce75b7c151e92aa099dfa546db4adc5'}, {'type': 'PACKAGE', 'url': 'https://github.com/dimforge/nalgebra'}, {'type': 'WEB', 'url': 'https://github.com/dimforge/nalgebra/blob/dev/CHANGELOG.md#0270'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0070.html'}]
|
{'cwe_ids': ['CWE-119', 'CWE-787'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T21:30:58Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-vcw4-8ph6-7vw8
|
2023-06-13T20:47:54Z
|
2021-08-25T20:54:20Z
| null |
['CVE-2021-29935']
|
Use after free in Rocket
|
Affected versions of this crate transmuted a &str to a &'static str before pushing it into a StackVec, this value was then popped later in the same function.
This was assumed to be safe because the reference would be valid while the method's stack was active. In between the push and the pop, however, a function f was called that could invoke a user provided function.
If the user provided panicked, then the assumption used by the function was no longer true and the transmute to &'static would create an illegal static reference to the string. This could result in a freed string being used during (such as in a Drop implementation) or after (e.g through catch_unwind) the panic unwinding.
This flaw was corrected in commit `e325e2f` by using a guard object to ensure that the &'static str was dropped inside the function.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'rocket'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.7'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-29935'}, {'type': 'WEB', 'url': 'https://github.com/SergioBenitez/Rocket/issues/1534'}, {'type': 'WEB', 'url': 'https://github.com/SergioBenitez/Rocket/commit/b53a906a8e170fe9b151381c66a76a872c419f9e'}, {'type': 'WEB', 'url': 'https://github.com/SergioBenitez/Rocket/commit/e325e2fce4d9f9f392761e9fb58b418a48cef8bb'}, {'type': 'PACKAGE', 'url': 'https://github.com/SergioBenitez/Rocket'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0044.html'}]
|
{'cwe_ids': ['CWE-416'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:09:45Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-23r4-5mxp-c7g5
|
2022-08-15T20:04:54Z
|
2021-08-23T19:41:52Z
| null |
['CVE-2021-39138']
|
parse-server new anonymous user session acts as if it's created with password
|
### Impact
Developers that use the REST API to signup users and also allow users to login anonymously. When an anonymous user is first signed up using REST, the server creates session incorrectly, particularly the `authProvider` field in `_Session` class under `createdWith` shows the user logged in creating a password. If a developer later depends on the `createdWith` field to provide a different level of access between a password user and anonymous user, the server incorrectly classified the session type as being created with a `password`.
The server currently doesn't use `createdWith` to make decisions on how things work internally, so if a developer isn't using `createdWith` directly, there's nothing to worry about. The vulnerability only affects users who depend on `createdWith` by using it directly.
### Patches
Upgrade to version 4.5.1.
### Workarounds
Don't use the `createdWith` Session field to make decisions if you allow anonymous login.
### References
n/a
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'parse-server'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.5.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/parse-community/parse-server/security/advisories/GHSA-23r4-5mxp-c7g5'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39138'}, {'type': 'WEB', 'url': 'https://github.com/parse-community/parse-server/commit/147bd9a3dc43391e92c36e05d5db860b04ca27db'}, {'type': 'PACKAGE', 'url': 'https://github.com/parse-community/parse-server'}, {'type': 'WEB', 'url': 'https://github.com/parse-community/parse-server/releases/tag/4.5.2'}]
|
{'cwe_ids': ['CWE-287', 'CWE-863'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T17:07:34Z', 'nvd_published_at': '2021-08-19T16:15:00Z'}
|
1.4.0
|
GHSA-7774-7vr3-cc8j
|
2021-12-13T13:09:54Z
|
2021-08-30T16:15:56Z
| null |
['CVE-2021-39155']
|
Authorization Policy Bypass Due to Case Insensitive Host Comparison
|
### Impact
According to [RFC 4343](https://datatracker.ietf.org/doc/html/rfc4343), Istio authorization policy should compare the hostname in the HTTP Host header in a case insensitive way, but currently the comparison is case sensitive. The Envoy proxy will route the request hostname in a case-insensitive way which means the authorization policy could be bypassed.
As an example, the user may have an authorization policy that rejects request with hostname "httpbin.foo" for some source IPs, but the attacker can bypass this by sending the request with hostname "Httpbin.Foo".
### Patches
* Istio 1.11.1 and above
* Istio 1.10.4 and above
* Istio 1.9.8 and above
### Workarounds
A Lua filter may be written to normalize Host header before the authorization check. This is similar to the Path normalization presented in the [Security Best Practices](https://istio.io/latest/docs/ops/best-practices/security/#case-normalization) guide.
### References
More details can be found in the [Istio Security Bulletin](https://istio.io/latest/news/security/istio-security-2021-008).
### For more information
If you have any questions or comments about this advisory, please email us at istio-security-vulnerability-reports@googlegroups.com
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'istio.io/istio'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.9.8'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'istio.io/istio'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.10.0'}, {'fixed': '1.10.4'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'istio.io/istio'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.11.0'}, {'fixed': '1.11.1'}]}], 'versions': ['1.11.0']}]
|
[{'type': 'WEB', 'url': 'https://github.com/istio/istio/security/advisories/GHSA-7774-7vr3-cc8j'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39155'}, {'type': 'WEB', 'url': 'https://github.com/istio/istio/commit/084b417a486dbe9b9024d4812877016a484572b1'}, {'type': 'WEB', 'url': 'https://github.com/istio/istio/commit/76ed51413ddd2a7fa253a368ab20a9cec5fb1cbe'}, {'type': 'WEB', 'url': 'https://github.com/istio/istio/commit/90b00bdf891e6c770cb3235c14a9b1fda96cc7c5'}, {'type': 'WEB', 'url': 'https://datatracker.ietf.org/doc/html/rfc4343'}, {'type': 'PACKAGE', 'url': 'https://github.com/istio/istio'}]
|
{'cwe_ids': ['CWE-178'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-25T22:29:16Z', 'nvd_published_at': '2021-08-24T23:15:00Z'}
|
1.4.0
|
GHSA-cgmg-2v6m-fjg7
|
2021-08-19T18:53:20Z
|
2021-08-25T20:50:41Z
| null |
['CVE-2020-36210']
|
Free of uninitialized memory in autorand
|
An issue was discovered in the autorand crate before 0.2.3 for Rust. Because of impl Random on arrays, uninitialized memory can be dropped when a panic occurs, leading to memory corruption.
|
[{'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': 'crates.io', 'name': 'autorand'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.2.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36210'}, {'type': 'WEB', 'url': 'https://github.com/mersinvald/autorand-rs/issues/5'}, {'type': 'PACKAGE', 'url': 'https://github.com/mersinvald/autorand-rs'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0103.html'}]
|
{'cwe_ids': ['CWE-908'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:53:20Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-xj6r-2jpm-qvxp
|
2021-08-24T18:50:59Z
|
2021-08-25T14:45:52Z
| null |
['CVE-2021-37694']
|
Code injection issue for java-spring-cloud-stream-template
|
The following was initially reported by @jonaslagoni:
Given the following command:
`ag ./dummy.json @asyncapi/java-spring-cloud-stream-template --force-write --output ./output`
With the following AsyncAPI document:
```json
{
"asyncapi": "2.0.0",
"info": {
"title": "Streetlight",
"version": "1.0.0"
},
"defaultContentType": "json",
"channels": {
"security/audit/channel": {
"description": "Channel for the turn on command which should turn on the streetlight",
"parameters": {
"streetlight_id": {
"description": "The ID of the streetlight",
"schema": {
"type": "string"
}
}
},
"publish": {
"operationId": "test() { System.out.println(\"injected\"); return test(0); }\n public Consumer<CustomClass> someothername",
"message": {
"name": "TurnonCommand",
"payload": {
"$ref": "#/components/schemas/CustomClass"
}
}
}
}
},
"components": {
"schemas" : {
"CustomClass": {
"type": "object",
"properties": {
"prop": {
"type": "string"
}
}
}
}
}
}
```
Which changes the following output:
```java
...
@Bean
public Consumer<CustomClass> test() {
// Add business logic here.
return null;
}
...
```
To
```java
...
@Bean
public Consumer<CustomClass> test() { System.out.println("injected"); return someothername(); }
public Consumer<CustomClass> someothername() {
// Add business logic here.
return null;
}
...
```
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': '@asyncapi/java-spring-cloud-stream-template'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.7.0'}]}], 'database_specific': {'last_known_affected_version_range': '<= 0.6.9'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/asyncapi/java-spring-cloud-stream-template/security/advisories/GHSA-xj6r-2jpm-qvxp'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37694'}, {'type': 'PACKAGE', 'url': 'https://github.com/asyncapi/java-spring-cloud-stream-template'}]
|
{'cwe_ids': ['CWE-94'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T18:50:59Z', 'nvd_published_at': '2021-08-11T18:15:00Z'}
|
1.4.0
|
GHSA-9frf-r7c7-j2vg
|
2023-06-13T20:54:15Z
|
2021-08-25T20:54:14Z
| null |
['CVE-2021-29939']
|
Out of bounds write in stackvector
|
StackVec::extend used the lower and upper bounds from an Iterator's size_hint to determine how many items to push into the stack based vector. If the size_hint implementation returned a lower bound that was larger than the upper bound, StackVec would write out of bounds and overwrite memory on the stack. As mentioned by the size_hint documentation, size_hint is mainly for optimization and incorrect implementations should not lead to memory safety issues.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'stackvector'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.0.9'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-29939'}, {'type': 'WEB', 'url': 'https://github.com/Alexhuszagh/rust-stackvector/issues/2'}, {'type': 'PACKAGE', 'url': 'https://github.com/Alexhuszagh/rust-stackvector'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0048.html'}]
|
{'cwe_ids': ['CWE-787'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:15:11Z', 'nvd_published_at': '2021-04-01T05:15:00Z'}
|
1.4.0
|
GHSA-xm9f-vxmx-4m58
|
2021-08-30T16:42:38Z
|
2021-08-30T17:20:41Z
| null |
['CVE-2021-32759']
|
Data Flow Sanitation Issue Fix
|
### Impact
Due to missing sanitation in data flow it was possible for admin users to upload arbitrary executable files to the server.
|
[]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'openmage/magento-lts'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '19.4.15'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'openmage/magento-lts'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '20.0.0'}, {'fixed': '20.0.13'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/OpenMage/magento-lts/security/advisories/GHSA-xm9f-vxmx-4m58'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-32759'}, {'type': 'WEB', 'url': 'https://github.com/OpenMage/magento-lts/commit/34709ac642d554aa1824892059186dd329db744b'}, {'type': 'WEB', 'url': 'https://github.com/OpenMage/magento-lts/releases/tag/v19.4.15'}, {'type': 'WEB', 'url': 'https://github.com/OpenMage/magento-lts/releases/tag/v20.0.13'}]
|
{'cwe_ids': ['CWE-20'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-30T16:42:38Z', 'nvd_published_at': '2021-08-27T22:15:00Z'}
|
1.4.0
|
GHSA-v666-6w97-pcwm
|
2021-08-02T21:55:20Z
|
2021-08-25T21:01:21Z
| null |
[]
|
Miner fails to get block template when a cell used as a cell dep has been destroyed.
|
### Impact
The RPC `get_block_template` fails when a cell has been used as a cell dep and an input in the different transactions.
Say cell C is used as a dep group in the transaction A, and is destroyed in the transaction B.
The node adds transaction A first, then B into the transaction pool. They are both valid. But when generating the block template, if the fee rate of B is higher, it comes before A, which will invalidate A. Currently the RPC `get_block_template` will fail instead of dropping A.
### Patch
First, the `get_block_template` should not fail but dropping the conflict transactions.
Then we can propose solution to this issue. Here is an example. When a transaction is added to the pool, the pool must consider it depending on all the transactions which dep cell (direct or indirect via dep group) has been destroyed in this transaction. Because future transactions using the destroyed cells as dep will be rejected, the spending transaction only need to wait for all the existing dep transactions on chain.
### Workaround
1. Submit transaction B when A is already on chain.
2. Let B depend on A explicitly, there are several solutions:
* a. Add any output cell on A as a dep cell or input in B.
* b. Merge A and B. CKB allows using the same cell as both dep and input in the same transaction.
3. Ensure the fee rate of B is less than A so A always has higher priority.
|
[]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'ckb'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.40.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/nervosnetwork/ckb/security/advisories/GHSA-v666-6w97-pcwm'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0107.html'}]
|
{'cwe_ids': ['CWE-367'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-02T21:55:20Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-m296-j53x-xv95
|
2023-06-13T21:47:59Z
|
2021-08-25T21:00:32Z
| null |
[]
|
Data races in tiny_future
|
`tiny_future` contains a light-weight implementation of `Future`s. The `Future` type it has lacked bound on its `Send` and `Sync` traits. This allows for a bug where non-thread safe types such as `Cell` can be used in `Future`s and cause data races in concurrent programs. The flaw was corrected in commit `c791919` by adding trait bounds to `Future`'s `Send` and `Sync`.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'tiny_future'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/KizzyCode/tiny_future/issues/1'}, {'type': 'WEB', 'url': 'https://github.com/KizzyCode/tiny_future/commit/7ab8a264980d23c2ed64e72f4636f38b7381eb39'}, {'type': 'WEB', 'url': 'https://github.com/KizzyCode/tiny_future/commit/c7919199a0f6d1ce0e3c33499d1b37f862c990e4'}, {'type': 'PACKAGE', 'url': 'https://github.com/KizzyCode/tiny_future'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0118.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-05T22:01:31Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-435p-f82x-mxwm
|
2021-08-26T15:21:24Z
|
2021-08-11T15:19:23Z
| null |
['CVE-2021-38305']
|
Command injection in Yamale
|
23andMe Yamale before 3.0.8 allows remote attackers to execute arbitrary code via a crafted schema file. The schema parser uses eval as part of its processing, and tries to protect from malicious expressions by limiting the builtins that are passed to the eval. When processing the schema, each line is run through Python's eval function to make the validator available. A well-constructed string within the schema rules can execute system commands; thus, by exploiting the vulnerability, an attacker can run arbitrary code on the image that invokes Yamale.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'yamale'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.0.8'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-38305'}, {'type': 'WEB', 'url': 'https://github.com/23andMe/Yamale/pull/165'}, {'type': 'PACKAGE', 'url': 'https://github.com/23andMe/Yamale'}, {'type': 'WEB', 'url': 'https://github.com/23andMe/Yamale/releases/tag/3.0.8'}]
|
{'cwe_ids': ['CWE-434', 'CWE-78'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-10T17:33:14Z', 'nvd_published_at': '2021-08-09T21:15:00Z'}
|
1.4.0
|
GHSA-hv7x-f3pv-gpwr
|
2023-06-13T20:55:22Z
|
2021-08-25T20:44:46Z
| null |
['CVE-2019-16137']
|
Wrong memory orderings violates mutual exclusion in spin
|
Wrong memory orderings inside the RwLock implementation allow for two writers to acquire the lock at the same time. The drop implementation used Ordering::Relaxed, which allows the compiler or CPU to reorder a mutable access on the locked data after the lock has been yielded.
Only users of the RwLock implementation are affected. Users of Once (including users of lazy_static with the spin_no_std feature enabled) are NOT affected.
On strongly ordered CPU architectures like x86, the only real way that this would lead to a memory corruption is if the compiler reorders an access after the lock is yielded, which is possible but in practice unlikely. It is a more serious issue on weakly ordered architectures such as ARM which, except in the presence of certain instructions, allow the hardware to decide which accesses are seen at what times. Therefore on an ARM system it is likely that using the wrong memory ordering would result in a memory corruption, even if the compiler itself doesn't reorder the memory accesses in a buggy way.
|
[{'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': 'crates.io', 'name': 'spin'}, 'ecosystem_specific': {'affected_functions': ['spin::RwLock::new']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.5.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-16137'}, {'type': 'WEB', 'url': 'https://github.com/mvdnes/spin-rs/issues/65'}, {'type': 'WEB', 'url': 'https://github.com/mvdnes/spin-rs/pull/66'}, {'type': 'PACKAGE', 'url': 'https://github.com/mvdnes/spin-rs'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0013.html'}]
|
{'cwe_ids': ['CWE-662'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:22:40Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-qr82-2c78-4m8h
|
2021-08-24T14:33:00Z
|
2021-08-25T14:41:42Z
| null |
['CVE-2021-37671']
|
Reference binding to nullptr in map operations
|
### Impact
An attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.Map*` and `tf.raw_ops.OrderedMap*` operations:
```python
import tensorflow as tf
tf.raw_ops.MapPeek(
key=tf.constant([8],dtype=tf.int64),
indices=[],
dtypes=[tf.int32],
capacity=8,
memory_limit=128)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L222-L248) has a check in place to ensure that `indices` is in ascending order, but does not check that `indices` is not empty.
### Patches
We have patched the issue in GitHub commit [532f5c5a547126c634fefd43bbad1dc6417678ac](https://github.com/tensorflow/tensorflow/commit/532f5c5a547126c634fefd43bbad1dc6417678ac).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
[{'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': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qr82-2c78-4m8h'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37671'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/532f5c5a547126c634fefd43bbad1dc6417678ac'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-824'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T14:33:00Z', 'nvd_published_at': '2021-08-12T22:15:00Z'}
|
1.4.0
|
GHSA-7cqg-8449-rmfv
|
2021-07-27T15:21:02Z
|
2021-08-25T21:01:27Z
| null |
['CVE-2019-20399']
|
Observable Discrepancy in libsecp256k1-rs
|
A timing vulnerability in the Scalar::check_overflow function in Parity libsecp256k1-rs before 0.3.1 potentially allows an attacker to leak information via a side-channel attack.
|
[{'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': 'crates.io', 'name': 'libsecp256k1-rs'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.3.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-20399'}, {'type': 'WEB', 'url': 'https://github.com/paritytech/libsecp256k1/commit/11ba23a9766a5079918cd9f515bc100bc8164b50'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0156.html'}]
|
{'cwe_ids': ['CWE-203', 'CWE-362'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-07-27T15:21:02Z', 'nvd_published_at': '2020-01-23T00:15:00Z'}
|
1.4.0
|
GHSA-qg24-8xj4-gj2h
|
2021-08-18T20:17:28Z
|
2021-08-25T20:58:13Z
| null |
['CVE-2020-36433']
|
Unaligned memory allocation in chunky
|
An issue was discovered in the chunky crate through 2020-08-25 for Rust. The Chunk API does not honor an alignment requirement.
|
[{'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': 'chunky'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.3.7'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36433'}, {'type': 'WEB', 'url': 'https://github.com/aeplay/chunky/issues/2'}, {'type': 'PACKAGE', 'url': 'https://github.com/aeplay/chunky'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0035.html'}]
|
{'cwe_ids': ['CWE-758'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T20:17:28Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-vjrq-cg9x-rfjp
|
2023-06-13T17:03:43Z
|
2021-08-25T20:43:02Z
| null |
['CVE-2017-18589']
|
Improper Input Validation in cookie
|
Affected versions of this crate use the time crate and the method Duration::seconds to parse the Max-Age duration cookie setting. This method will panic if the value is greater than 2^64/1000 and less than or equal to 2^64, which can result in denial of service for a client or server.
This flaw was corrected by explicitly checking for the Max-Age being in this integer range and clamping the value to the maximum duration value.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'cookie'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.7.6'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2017-18589'}, {'type': 'WEB', 'url': 'https://github.com/SergioBenitez/cookie-rs/pull/86'}, {'type': 'WEB', 'url': 'https://github.com/SergioBenitez/cookie-rs/commit/ee18b79fbf0903b73da525d302b09448009e0050'}, {'type': 'PACKAGE', 'url': 'https://github.com/alexcrichton/cookie-rs'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2017-0005.html'}]
|
{'cwe_ids': ['CWE-20'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:25:22Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-fg47-3c2x-m2wr
|
2021-09-13T20:30:10Z
|
2021-08-30T16:12:38Z
| null |
['CVE-2021-39167']
|
TimelockController vulnerability in OpenZeppelin Contracts
|
### Impact
A vulnerability in `TimelockController` allowed an actor with the executor role to take immediate control of the timelock, by resetting the delay to 0 and escalating privileges, thus gaining unrestricted access to assets held in the contract. Instances with the executor role set to "open" allow anyone to use the executor role, thus leaving the timelock at risk of being taken over by an attacker.
### Patches
A fix is included in the following releases of `@openzeppelin/contracts` and `@openzeppelin/contracts-upgradeable`:
- 4.3.1
- 3.4.2
- 3.4.2-solc-0.7
Deployed instances of `TimelockController` should be replaced with a fixed version by migrating all assets, ownership, and roles.
### Workarounds
Revoke the executor role from accounts not strictly under the team's control. We recommend revoking all executors that are not also proposers. When applying this mitigation, ensure there is at least one proposer and executor remaining.
### References
[Post-mortem](https://forum.openzeppelin.com/t/timelockcontroller-vulnerability-postmortem/14958).
### Credits
The issue was identified by an anonymous white hat hacker through [Immunefi](https://immunefi.com/).
### For more information
If you have any questions or comments about this advisory, or need assistance executing the mitigation, email us at security@openzeppelin.com.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'npm', 'name': '@openzeppelin/contracts'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.0.0'}, {'fixed': '4.3.1'}]}]}, {'package': {'ecosystem': 'npm', 'name': '@openzeppelin/contracts'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.3.0'}, {'fixed': '3.4.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/OpenZeppelin/openzeppelin-contracts/security/advisories/GHSA-fg47-3c2x-m2wr'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39167'}, {'type': 'WEB', 'url': 'https://github.com/OpenZeppelin/openzeppelin-contracts/commit/cec4f2ef57495d8b1742d62846da212515d99dd5'}, {'type': 'PACKAGE', 'url': 'https://github.com/OpenZeppelin/openzeppelin-contracts'}, {'type': 'WEB', 'url': 'https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/CHANGELOG.md#431'}]
|
{'cwe_ids': ['CWE-269'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-27T12:59:07Z', 'nvd_published_at': '2021-08-27T00:15:00Z'}
|
1.4.0
|
GHSA-5325-xw5m-phm3
|
2021-08-18T21:28:38Z
|
2021-08-25T20:55:56Z
| null |
['CVE-2021-38193']
|
Cross-site Scripting in ammonia
|
An issue was discovered in the ammonia crate before 3.1.0 for Rust. XSS can occur because the parsing differences for HTML, SVG, and MathML are mishandled, a similar issue to CVE-2020-26870.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'ammonia'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.0.0'}, {'fixed': '3.1.0'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'ammonia'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.1.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-38193'}, {'type': 'WEB', 'url': 'https://github.com/rust-ammonia/ammonia/pull/142'}, {'type': 'PACKAGE', 'url': 'https://github.com/rust-ammonia/ammonia'}, {'type': 'WEB', 'url': 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/ammonia/RUSTSEC-2021-0074.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0074.html'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T21:28:38Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-mp6r-fgw2-rxfx
|
2023-06-13T22:28:51Z
|
2021-08-25T20:53:27Z
| null |
['CVE-2021-26956']
|
Arbitrary return types in xcb
|
The function xcb::xproto::GetPropertyReply::value() returns a slice of type T where T is an unconstrained type parameter. The raw bytes received from the X11 server are interpreted as the requested type. The users of the xcb crate are advised to only call this function with the intended types. These are u8, u16, and u32.
This issue is tracked here: https://github.com/rust-x-bindings/rust-xcb/issues/95
|
[{'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': 'crates.io', 'name': 'xcb'}, 'ecosystem_specific': {'affected_functions': ['xcb::xproto::GetPropertyReply::value']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.0.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-26956'}, {'type': 'WEB', 'url': 'https://github.com/RustSec/advisory-db/issues/653'}, {'type': 'WEB', 'url': 'https://github.com/rust-x-bindings/rust-xcb/issues/95'}, {'type': 'PACKAGE', 'url': 'https://github.com/rtbo/rust-xcb'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0019.html'}]
|
{'cwe_ids': ['CWE-657'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:35:46Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-gffv-5hr2-f9gj
|
2023-06-13T20:12:57Z
|
2021-08-25T20:43:18Z
| null |
['CVE-2018-20999']
|
Flaw in streaming state in orion
|
Affected versions of this crate did not properly reset a streaming state. Resetting a streaming state, without finalising it first, creates incorrect results. The flaw was corrected by not first checking if the state had already been reset, when calling reset().
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'orion'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.11.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2018-20999'}, {'type': 'WEB', 'url': 'https://github.com/brycx/orion/issues/46'}, {'type': 'PACKAGE', 'url': 'https://github.com/brycx/orion'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2018-0012.html'}]
|
{'cwe_ids': ['CWE-682'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:24:37Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-jq65-29v4-4x35
|
2021-08-19T21:21:21Z
|
2021-08-25T20:45:15Z
| null |
['CVE-2020-1967']
|
Null pointer deference in openssl-src
|
Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due to a NULL pointer dereference as a result of incorrect handling of the "signature_algorithms_cert" TLS extension. The crash occurs if an invalid or unrecognised signature algorithm is received from the peer. This could be exploited by a malicious peer in a Denial of Service attack. OpenSSL version 1.1.1d, 1.1.1e, and 1.1.1f are affected by this issue. This issue did not affect OpenSSL versions prior to 1.1.1d. Fixed in OpenSSL 1.1.1g (Affected 1.1.1d-1.1.1f).
|
[{'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': 'crates.io', 'name': 'openssl-src'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '111.6.0'}, {'fixed': '111.9.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-1967'}, {'type': 'WEB', 'url': 'https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=eb563247aef3e83dda7679c43f9649270462e5b1'}, {'type': 'WEB', 'url': 'https://github.com/irsl/CVE-2020-1967'}, {'type': 'WEB', 'url': 'https://kb.pulsesecure.net/articles/Pulse_Security_Advisories/SA44440'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r66ea9c436da150683432db5fbc8beb8ae01886c6459ac30c2cea7345@%3Cdev.tomcat.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r94d6ac3f010a38fccf4f432b12180a13fa1cf303559bd805648c9064@%3Cdev.tomcat.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r9a41e304992ce6aec6585a87842b4f2e692604f5c892c37e3b0587ee@%3Cdev.tomcat.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DDHOAATPWJCXRNFMJ2SASDBBNU5RJONY/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EXDDAOWSAIEFQNBHWYE6PPYFV4QXGMCD/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XVEP3LAK4JSPRXFO4QF4GG2IVXADV3SO/'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0015.html'}, {'type': 'WEB', 'url': 'https://security.FreeBSD.org/advisories/FreeBSD-SA-20:11.openssl.asc'}, {'type': 'WEB', 'url': 'https://security.gentoo.org/glsa/202004-10'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20200424-0003/'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20200717-0004/'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2020/dsa-4661'}, {'type': 'WEB', 'url': 'https://www.openssl.org/news/secadv/20200421.txt'}, {'type': 'WEB', 'url': 'https://www.oracle.com//security-alerts/cpujul2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuApr2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujan2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujul2020.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2020.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2021.html'}, {'type': 'WEB', 'url': 'https://www.synology.com/security/advisory/Synology_SA_20_05'}, {'type': 'WEB', 'url': 'https://www.synology.com/security/advisory/Synology_SA_20_05_OpenSSL'}, {'type': 'WEB', 'url': 'https://www.tenable.com/security/tns-2020-03'}, {'type': 'WEB', 'url': 'https://www.tenable.com/security/tns-2020-04'}, {'type': 'WEB', 'url': 'https://www.tenable.com/security/tns-2020-11'}, {'type': 'WEB', 'url': 'https://www.tenable.com/security/tns-2021-10'}, {'type': 'WEB', 'url': 'http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00004.html'}, {'type': 'WEB', 'url': 'http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00011.html'}, {'type': 'WEB', 'url': 'http://packetstormsecurity.com/files/157527/OpenSSL-signature_algorithms_cert-Denial-Of-Service.html'}, {'type': 'WEB', 'url': 'http://seclists.org/fulldisclosure/2020/May/5'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2020/04/22/2'}]
|
{'cwe_ids': ['CWE-476'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:21:21Z', 'nvd_published_at': '2020-04-21T14:15:00Z'}
|
1.4.0
|
GHSA-h76r-vgf3-j6w5
|
2022-08-11T00:18:28Z
|
2021-08-30T16:13:50Z
| null |
['CVE-2021-29487']
|
October CMS auth bypass and account takeover
|
### Impact
An attacker can exploit this vulnerability to bypass authentication using a specially crafted persist cookie.
- To exploit this vulnerability, an attacker must obtain a Laravel’s secret key for cookie encryption and signing.
- Due to the logic of how this mechanism works, a targeted user account must be logged in while
the attacker is exploiting the vulnerability.
- Authorization via persist cookie not shown in access logs.
### Patches
- Issue has been patched in Build 472 and v1.1.5
- [Shortened patch instructions](https://github.com/daftspunk/CVE-2021-32648)
### Workarounds
Apply https://github.com/octobercms/library/commit/016a297b1bec55d2e53bc889458ed2cb5c3e9374 and https://github.com/octobercms/library/commit/5bd1a28140b825baebe6becd4f7562299d3de3b9 to your installation manually if you are unable to upgrade.
[**Update 2022-01-20**] [Shortened patch instructions](https://github.com/daftspunk/CVE-2021-32648) can be found here.
### Recommendations
We recommend the following steps to make sure your server stays secure:
- Keep server OS and system software up to date.
- Keep October CMS software up to date.
- Use a multi-factor authentication plugin.
- Change the [default backend URL](https://github.com/octobercms/october/blob/1.1/config/cms.php#L39) or block public access to the backend area.
- Include the [Roave/SecurityAdvisories](https://github.com/Roave/SecurityAdvisories) Composer package to ensure that your application doesn't have installed dependencies with known security vulnerabilities.
### References
Bugs found as part of Solar Security CMS Research. Credits to:
• Andrey Basarygin
• Andrey Guzei
• Mikhail Khramenkov
• Alexander Sidukov
• Maxim Teplykh
### For more information
If you have any questions or comments about this advisory:
* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'october/system'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.0.472'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'october/system'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.1.1'}, {'fixed': '1.1.5'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/octobercms/october/security/advisories/GHSA-h76r-vgf3-j6w5'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-29487'}, {'type': 'WEB', 'url': 'https://github.com/octobercms/library/commit/016a297b1bec55d2e53bc889458ed2cb5c3e9374'}, {'type': 'WEB', 'url': 'https://github.com/octobercms/library/commit/5bd1a28140b825baebe6becd4f7562299d3de3b9'}, {'type': 'PACKAGE', 'url': 'https://github.com/octobercms/october'}]
|
{'cwe_ids': ['CWE-287'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-26T20:09:50Z', 'nvd_published_at': '2021-08-26T19:15:00Z'}
|
1.4.0
|
GHSA-h5q8-5697-9p9h
|
2021-08-30T17:02:20Z
|
2021-08-30T17:22:15Z
| null |
['CVE-2020-22403']
|
Cross-Site Request Forgery in express-cart
|
The express-cart package through 1.1.10 for Node.js allows CSRF.
|
[{'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': 'npm', 'name': 'express-cart'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.1.17'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-22403'}, {'type': 'WEB', 'url': 'https://github.com/mrvautin/expressCart/issues/120'}, {'type': 'WEB', 'url': 'https://github.com/mrvautin/expressCart/commit/cd3ba1bc609c2f2946bfbc7ee2fccf3483eb71fb'}, {'type': 'WEB', 'url': 'https://hackerone.com/reports/395944'}, {'type': 'PACKAGE', 'url': 'https://github.com/mrvautin/expressCart'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20210909-0004/'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/package/express-cart'}]
|
{'cwe_ids': ['CWE-352'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-30T17:02:20Z', 'nvd_published_at': '2021-08-12T22:15:00Z'}
|
1.4.0
|
GHSA-q7f7-544h-67h9
|
2021-08-24T17:13:21Z
|
2021-08-25T14:40:13Z
| null |
['CVE-2021-37684']
|
FPE in TFLite pooling operations
|
### Impact
The implementations of pooling in TFLite are vulnerable to division by 0 errors as there are no checks for divisors not being 0.
### Patches
We have patched the issue in GitHub commit [dfa22b348b70bb89d6d6ec0ff53973bacb4f4695](https://github.com/tensorflow/tensorflow/commit/dfa22b348b70bb89d6d6ec0ff53973bacb4f4695).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
[{'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': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q7f7-544h-67h9'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37684'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-369'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T17:13:21Z', 'nvd_published_at': '2021-08-12T23:15:00Z'}
|
1.4.0
|
GHSA-5379-r78w-42h2
|
2021-08-27T23:25:28Z
|
2021-08-30T16:11:57Z
| null |
['CVE-2021-39171']
|
Unlimited transforms allowed for signed nodes
|
### Impact
A malicious SAML payload can require transforms that consume significant system resources to process, thereby resulting in reduced or denied service. This would be an effective way to perform a denial-of-service attack.
### Patches
This has been resolved in version 3.1.0. The resolution is to limit the number of allowable transforms to 2.
### References
https://github.com/node-saml/passport-saml/pull/595
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'passport-saml'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.1.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/node-saml/passport-saml/security/advisories/GHSA-5379-r78w-42h2'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39171'}, {'type': 'WEB', 'url': 'https://github.com/node-saml/passport-saml/pull/595'}, {'type': 'PACKAGE', 'url': 'https://github.com/node-saml/passport-saml'}]
|
{'cwe_ids': ['CWE-400'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-27T23:25:28Z', 'nvd_published_at': '2021-08-27T22:15:00Z'}
|
1.4.0
|
GHSA-5m69-3chg-6f8m
|
2021-08-26T19:21:15Z
|
2021-08-30T16:23:26Z
| null |
['CVE-2020-18702']
|
Cross Site Scripting (XSS) in Quokka
|
Cross Site Scripting (XSS) in Quokka v0.4.0 allows remote attackers to execute arbitrary code via the 'Username' parameter in the component 'quokka/admin/actions.py'.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'quokka'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.4.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-18702'}, {'type': 'WEB', 'url': 'https://github.com/rochacbruno/quokka/issues/675'}, {'type': 'PACKAGE', 'url': 'https://github.com/rochacbruno/quokka'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-26T19:21:15Z', 'nvd_published_at': '2021-08-16T18:15:00Z'}
|
1.4.0
|
GHSA-5hp8-35wj-m525
|
2021-08-19T21:23:38Z
|
2021-08-25T20:44:03Z
| null |
['CVE-2019-15542']
|
Uncontrolled recursion in ammonia
|
An issue was discovered in the ammonia crate before 2.1.0 for Rust. There is uncontrolled recursion during HTML DOM tree serialization.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'ammonia'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.1.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-15542'}, {'type': 'PACKAGE', 'url': 'https://github.com/rust-ammonia/ammonia'}, {'type': 'WEB', 'url': 'https://github.com/rust-ammonia/ammonia/blob/master/CHANGELOG.md#210'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0001.html'}]
|
{'cwe_ids': ['CWE-674'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:23:38Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-49fq-pw77-6qxj
|
2023-06-13T21:55:41Z
|
2021-08-25T20:44:15Z
| null |
['CVE-2019-16882']
|
Use after free in string-interner
|
Affected versions of this crate did not clone contained strings when an interner is cloned. Interners have raw pointers to the contained strings, and they keep pointing the strings which the old interner owns, after the interner is cloned. If a new cloned interner is alive and the old original interner is dead, the new interner has dangling pointers to the old interner's storage, which is already dropped.
This allows an attacker to read the already freed memory. The dangling pointers are used by the interners to check a string is already interned. An attacker can do brute force attack to get the data pointed by the dangling pointer.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'string-interner'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.7.0'}, {'fixed': '0.7.1'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'string-interner'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.6.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-16882'}, {'type': 'WEB', 'url': 'https://github.com/Robbepop/string-interner/issues/9'}, {'type': 'WEB', 'url': 'https://github.com/Robbepop/string-interner/pull/10'}, {'type': 'WEB', 'url': 'https://github.com/Robbepop/string-interner/commit/d91dac0cfe42512526879cdfaac0b81beff54089'}, {'type': 'PACKAGE', 'url': 'https://github.com/Robbepop/string-interner'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0023.html'}]
|
{'cwe_ids': ['CWE-416'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:23:01Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-9p29-94hp-8rvc
|
2023-01-24T15:08:52Z
|
2021-08-02T17:22:07Z
| null |
['CVE-2021-28833']
|
qiita-markdown Cross-site Scripting vulnerability
|
Increments Qiita::Markdown before 0.34.0 allows XSS via a crafted gist link, a different vulnerability than CVE-2021-28796.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'RubyGems', 'name': 'qiita-markdown'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.34.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-28833'}, {'type': 'WEB', 'url': 'https://github.com/increments/qiita-markdown/commit/b5d4e60bf537ceb177e70bf91653d29575e1aa21'}, {'type': 'PACKAGE', 'url': 'https://github.com/increments/qiita-markdown'}, {'type': 'WEB', 'url': 'https://github.com/increments/qiita-markdown/compare/v0.33.0...v0.34.0'}, {'type': 'WEB', 'url': 'https://github.com/increments/qiita-markdown/releases'}, {'type': 'WEB', 'url': 'https://vuln.ryotak.me/advisories/50'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-06-22T15:42:57Z', 'nvd_published_at': '2021-06-21T13:15:00Z'}
|
1.4.0
|
GHSA-w74j-v8xh-3w5h
|
2021-08-24T14:18:05Z
|
2021-08-25T14:42:09Z
| null |
['CVE-2021-37667']
|
Reference binding to nullptr in unicode encoding
|
### Impact
An attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.UnicodeEncode`:
```python
import tensorflow as tf
from tensorflow.python.ops import gen_string_ops
gen_string_ops.unicode_encode(
input_values=[],
input_splits=[],
output_encoding='UTF-8',
errors='ignore',
replacement_char='a')
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unicode_ops.cc#L533-L539) reads the first dimension of the `input_splits` tensor before validating that this tensor is not empty:
```cc
const Tensor& input_splits = context->input(1);
const auto input_splits_flat = input_splits.flat<SPLITS_TYPE>();
TensorShape output_shape({input_splits.dim_size(0) - 1});
```
### Patches
We have patched the issue in GitHub commit [2e0ee46f1a47675152d3d865797a18358881d7a6](https://github.com/tensorflow/tensorflow/commit/2e0ee46f1a47675152d3d865797a18358881d7a6).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
[{'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': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-w74j-v8xh-3w5h'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37667'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/2e0ee46f1a47675152d3d865797a18358881d7a6'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-824'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T14:18:05Z', 'nvd_published_at': '2021-08-12T22:15:00Z'}
|
1.4.0
|
GHSA-f3fg-5j9p-vchc
|
2023-04-03T19:22:33Z
|
2021-08-25T21:01:41Z
| null |
['CVE-2021-31153']
|
File exposure in pleaser
|
pleaser before 0.4.0 allows a local unprivileged attacker to gain knowledge about the existence of files or directories in privileged locations via the search_path function, the --check option, or the -d option.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'pleaser'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-31153'}, {'type': 'WEB', 'url': 'https://crates.io/crates/pleaser'}, {'type': 'WEB', 'url': 'https://gitlab.com/edneville/please/-/tree/master/src/bin'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0104.html'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/05/18/1'}]
|
{'cwe_ids': ['CWE-200', 'CWE-668'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2021-06-01T19:35:31Z', 'nvd_published_at': '2021-05-27T13:15:00Z'}
|
1.4.0
|
GHSA-87cj-px37-rc3x
|
2021-08-26T15:58:50Z
|
2021-08-30T16:25:35Z
| null |
['CVE-2021-23422']
|
OS Command Injection in bikeshed
|
This affects the package bikeshed before 3.0.0. This can occur when an untrusted source file containing Inline Tag Command metadata is processed. When an arbitrary OS command is executed, the command output would be included in the HTML output.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'bikeshed'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.0.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-23422'}, {'type': 'WEB', 'url': 'https://github.com/tabatkins/bikeshed/commit/b2f668fca204260b1cad28d5078e93471cb6b2dd'}, {'type': 'PACKAGE', 'url': 'https://github.com/tabatkins/bikeshed'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-PYTHON-BIKESHED-1537646'}]
|
{'cwe_ids': ['CWE-78'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-26T15:58:50Z', 'nvd_published_at': '2021-08-16T08:15:00Z'}
|
1.4.0
|
GHSA-2grh-hm3w-w7hv
|
2023-06-13T22:08:56Z
|
2021-08-25T20:55:51Z
| null |
['CVE-2021-38191']
|
Race condition in tokio
|
When aborting a task with JoinHandle::abort, the future is dropped in the thread calling abort if the task is not currently being executed. This is incorrect for tasks spawned on a LocalSet. This can easily result in race conditions as many projects use Rc or RefCell in their Tokio tasks for better performance.
|
[{'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': 'crates.io', 'name': 'tokio'}, 'ecosystem_specific': {'affected_functions': ['tokio::task::JoinHandle::abort']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.8.0'}, {'fixed': '1.8.1'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'tokio'}, 'ecosystem_specific': {'affected_functions': ['tokio::task::JoinHandle::abort']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.7.0'}, {'fixed': '1.7.2'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'tokio'}, 'ecosystem_specific': {'affected_functions': ['tokio::task::JoinHandle::abort']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.6.0'}, {'fixed': '1.6.3'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'tokio'}, 'ecosystem_specific': {'affected_functions': ['tokio::task::JoinHandle::abort']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.3.0'}, {'fixed': '1.5.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-38191'}, {'type': 'WEB', 'url': 'https://github.com/tokio-rs/tokio/issues/3929'}, {'type': 'PACKAGE', 'url': 'https://github.com/tokio-rs/tokio'}, {'type': 'WEB', 'url': 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/tokio/RUSTSEC-2021-0072.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0072.html'}]
|
{'cwe_ids': ['CWE-362', 'CWE-366'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T21:30:23Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-gpfj-4j6g-c4w9
|
2021-08-30T23:16:08Z
|
2021-08-12T20:42:17Z
| null |
['CVE-2021-37700']
|
Clipboard-based DOM-XSS
|
### Impact
A self Cross-Site Scripting vulnerability exists in the @github/paste-markdown library. If the clipboard data contains the string `<table>`, a **div** is dynamically created, and the clipboard content is copied into its **innerHTML** property without any sanitization, resulting in improper execution of JavaScript in the browser of the victim (the user who pasted the code). Users directed to copy text from a malicious website and paste it into pages that utilize this library are affected.
The following @github/paste-markdown code snippet is triggered when the user pastes something and the browser's clipboard data contains an entry whose content-type is **text/HTML**.
```typescript
function generateText(transfer: DataTransfer): string | undefined {
if (Array.from(transfer.types).indexOf('text/html') === -1) return
let html = transfer.getData('text/html')
if (!/<table/i.test(html)) return
html = html.replace(/<meta.*?>/, '')
const el = document.createElement('div')
el.innerHTML = html
const tables = el.querySelectorAll('table')
for (const table of tables) {
if (table.closest('[data-paste-markdown-skip]')) {
table.replaceWith(new Text(table.textContent || ''))
}
const formattedTable = tableMarkdown(table)
table.replaceWith(new Text(formattedTable))
}
return el.innerHTML
}
```
### Patches
A security patch was released in [version 0.3.4](https://github.com/github/paste-markdown/releases/tag/v0.3.4).
### Workarounds
A Content Security Policy that prevents `unsafe-inline` helps reduce the likelihood of this vulnerability being exploited in modern browsers.
<!--
### References
_Are there any links users can visit to find out more?_
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [example link to repo](http://example.com)
* Email us at [example email address](mailto:example@example.com)
*
-->
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': '@github/paste-markdown'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.3.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/github/paste-markdown/security/advisories/GHSA-gpfj-4j6g-c4w9'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37700'}, {'type': 'WEB', 'url': 'https://github.com/github/paste-markdown/commit/32b7ea3f29ae8f256f9d19768387be42678ddf30'}, {'type': 'PACKAGE', 'url': 'https://github.com/github/paste-markdown'}, {'type': 'WEB', 'url': 'https://github.com/github/paste-markdown/releases/tag/v0.3.4'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/package/@github/paste-markdown'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-12T20:41:45Z', 'nvd_published_at': '2021-08-12T21:15:00Z'}
|
1.4.0
|
GHSA-9f8f-574q-8jmf
|
2021-08-26T19:40:47Z
|
2021-08-30T16:14:00Z
| null |
['CVE-2021-37707']
|
Manipulation of product reviews via API
|
### Impact
Manipulation of product reviews via API
### Patches
We recommend updating to the current version 6.4.3.1. You can get the update to 6.4.3.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
|
[{'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': 'Packagist', 'name': 'shopware/platform'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.4.3.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.4.3.0'}}, {'package': {'ecosystem': 'Packagist', 'name': 'shopware/core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.4.3.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.4.3.0'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/shopware/platform/security/advisories/GHSA-9f8f-574q-8jmf'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37707'}, {'type': 'WEB', 'url': 'https://github.com/shopware/platform/commit/912b96de3b839c6c5525c98cbb58f537c2d838be'}, {'type': 'PACKAGE', 'url': 'https://github.com/shopware/platform'}]
|
{'cwe_ids': ['CWE-20'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-26T19:40:47Z', 'nvd_published_at': '2021-08-16T19:15:00Z'}
|
1.4.0
|
GHSA-v3j6-xf77-8r9c
|
2021-08-19T20:51:41Z
|
2021-08-25T20:49:39Z
| null |
['CVE-2020-35901']
|
Use-after-free in actix-http
|
An issue was discovered in the actix-http crate before 2.0.0-alpha.1 for Rust. There is a use-after-free in BodyStream.
|
[{'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': 'crates.io', 'name': 'actix-http'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.0.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35901'}, {'type': 'WEB', 'url': 'https://github.com/actix/actix-web/issues/1321'}, {'type': 'PACKAGE', 'url': 'https://github.com/actix/actix-web'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0048.html'}]
|
{'cwe_ids': ['CWE-416'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T20:51:41Z', 'nvd_published_at': None}
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.