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-66p5-j55p-32r9
|
2021-08-06T16:36:54Z
|
2021-08-25T21:00:25Z
| null |
[]
|
smallvec creates uninitialized value of any type
|
Affected versions of this crate called `mem::uninitialized()` to create values of a user-supplied type `T`.
This is unsound e.g. if `T` is a reference type (which must be non-null and thus may not remain uninitialized).
The flaw was corrected by avoiding the use of `mem::uninitialized()`, using `MaybeUninit` instead.
|
[]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'smallvec'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.6.13'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/servo/rust-smallvec/issues/126'}, {'type': 'WEB', 'url': 'https://github.com/servo/rust-smallvec/pull/162'}, {'type': 'PACKAGE', 'url': 'https://github.com/servo/rust-smallvec'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2018-0018.html'}]
|
{'cwe_ids': ['CWE-457'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-06T16:36:54Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-rfgg-vccr-m46m
|
2021-08-19T21:20:37Z
|
2021-08-25T20:45:58Z
| null |
['CVE-2020-25794']
|
Missing release of memory in sized-chunks
|
An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, clone can have a memory-safety issue upon a panic.
|
[{'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-25794'}, {'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-401'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:20:37Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-v3cg-h3f6-2242
|
2022-02-08T21:01:17Z
|
2021-08-30T16:24:38Z
| null |
['CVE-2021-32827']
|
Injection in MockServer
|
MockServer is open source software which enables easy mocking of any system you integrate with via HTTP or HTTPS. An attacker that can trick a victim into visiting a malicious site while running MockServer locally, will be able to run arbitrary code on the MockServer machine. With an overly broad default CORS configuration MockServer allows any site to send cross-site requests. Additionally, MockServer allows you to create dynamic expectations using Javascript or Velocity templates. Both engines may allow an attacker to execute arbitrary code on-behalf of MockServer. By combining these two issues (Overly broad CORS configuration + Script injection), an attacker could serve a malicious page so that if a developer running MockServer visits it, they will get compromised. For more details including a PoC see the referenced GHSL-2021-059.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:H/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.mock-server:mockserver'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '5.11.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-32827'}, {'type': 'PACKAGE', 'url': 'https://github.com/mock-server/mockserver'}, {'type': 'ADVISORY', 'url': 'https://securitylab.github.com/advisories/GHSL-2021-059-mockserver/'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujan2022.html'}]
|
{'cwe_ids': ['CWE-74', 'CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-26T19:35:37Z', 'nvd_published_at': '2021-08-16T21:15:00Z'}
|
1.4.0
|
GHSA-f997-8gxg-r354
|
2022-05-05T18:16:25Z
|
2021-08-25T20:58:09Z
| null |
['CVE-2020-36458']
|
Data races in lexer
|
lexer is a plugin based lexical reader.Affected versions of this crate implements Sync for ReaderResult<T, E> with the trait bound T: Send, E: Send. Since matching on the public enum ReaderResult<T, E> provides access to &T & &E, allowing data race to a non-Sync type T or E. This can result in a memory corruption when multiple threads concurrently access &T or &E. Suggested fix for the bug is change the trait bounds imposed on T & E to be T: Sync, E: 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': 'lexer'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.1.16'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36458'}, {'type': 'PACKAGE', 'url': 'https://gitlab.com/nathanfaucett/rs-lexer'}, {'type': 'WEB', 'url': 'https://gitlab.com/nathanfaucett/rs-lexer/-/issues/2'}, {'type': 'WEB', 'url': 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/lexer/RUSTSEC-2020-0138.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0138.html'}]
|
{'cwe_ids': ['CWE-362', 'CWE-77'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T20:18:45Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-8q5c-93vg-c747
|
2021-08-19T19:03:37Z
|
2021-08-25T21:00:30Z
|
2021-08-19T19:03:37Z
|
[]
|
WITHDRAWN
|
WITHDRAWN
|
[]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'toolshed'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.8.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/ratel-rust/toolshed/issues/12'}, {'type': 'PACKAGE', 'url': 'https://github.com/ratel-rust/toolshed'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0136.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-05T22:05:47Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-75cq-g75g-rxff
|
2021-08-18T22:36:31Z
|
2021-08-25T21:00:43Z
| null |
['CVE-2020-35900']
|
use-after-free vulnerability in Rust array-queue
|
An issue was discovered in the array-queue crate through 2020-09-26 for Rust. A pop_back() call may lead to a use-after-free.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'array-queue'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.3.0'}, {'last_affected': '0.3.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35900'}, {'type': 'WEB', 'url': 'https://github.com/raviqqe/array-queue/issues/2'}, {'type': 'PACKAGE', 'url': 'https://github.com/raviqqe/array-queue'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0047.html'}]
|
{'cwe_ids': ['CWE-416'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-05T19:46:12Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-r6jx-9g48-2r5r
|
2021-08-24T16:15:38Z
|
2021-08-25T14:41:12Z
| null |
['CVE-2021-37678']
|
Arbitrary code execution due to YAML deserialization
|
### Impact
TensorFlow and Keras can be tricked to perform arbitrary code execution when deserializing a Keras model from YAML format.
```python
from tensorflow.keras import models
payload = '''
!!python/object/new:type
args: ['z', !!python/tuple [], {'extend': !!python/name:exec }]
listitems: "__import__('os').system('cat /etc/passwd')"
'''
models.model_from_yaml(payload)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/python/keras/saving/model_config.py#L66-L104) uses `yaml.unsafe_load` which can perform arbitrary code execution on the input.
### Patches
Given that YAML format support requires a significant amount of work, we have removed it for now.
We have patched the issue in GitHub commit [23d6383eb6c14084a8fc3bdf164043b974818012](https://github.com/tensorflow/tensorflow/commit/23d6383eb6c14084a8fc3bdf164043b974818012).
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 Arjun Shibu.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ecosystem_specific': {'affected_functions': ['tensorflow.keras.Model.to_yaml', 'tensorflow.keras.models.model_from_yaml']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ecosystem_specific': {'affected_functions': ['tensorflow.keras.Model.to_yaml', 'tensorflow.keras.models.model_from_yaml']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ecosystem_specific': {'affected_functions': ['tensorflow.keras.Model.to_yaml', 'tensorflow.keras.models.model_from_yaml']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ecosystem_specific': {'affected_functions': ['tensorflow.keras.Model.to_yaml', 'tensorflow.keras.models.model_from_yaml']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ecosystem_specific': {'affected_functions': ['tensorflow.keras.Model.to_yaml', 'tensorflow.keras.models.model_from_yaml']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ecosystem_specific': {'affected_functions': ['tensorflow.keras.Model.to_yaml', 'tensorflow.keras.models.model_from_yaml']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ecosystem_specific': {'affected_functions': ['tensorflow.keras.Model.to_yaml', 'tensorflow.keras.models.model_from_yaml']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ecosystem_specific': {'affected_functions': ['tensorflow.keras.Model.to_yaml', 'tensorflow.keras.models.model_from_yaml']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ecosystem_specific': {'affected_functions': ['tensorflow.keras.Model.to_yaml', 'tensorflow.keras.models.model_from_yaml']}, '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-r6jx-9g48-2r5r'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37678'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/1df5a69e9f1a18a937e7907223066e606bf466b9'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/23d6383eb6c14084a8fc3bdf164043b974818012'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/8e47a685785bef8f81bcb996048921dfde08a9ab'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/a09ab4e77afdcc6e1e045c9d41d5edab63aafc1a'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-502'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T16:15:38Z', 'nvd_published_at': '2021-08-12T23:15:00Z'}
|
1.4.0
|
GHSA-xxfr-jrgh-x392
|
2021-05-04T22:11:30Z
|
2021-08-02T17:29:01Z
| null |
['CVE-2020-1172']
|
Remote code execution in ChakraCore
|
A remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-1057, CVE-2020-1180.
|
[{'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.22'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-1172'}, {'type': 'WEB', 'url': 'https://github.com/chakra-core/ChakraCore/pull/6500'}, {'type': 'WEB', 'url': 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-1172'}]
|
{'cwe_ids': ['CWE-787'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-05-04T22:11:30Z', 'nvd_published_at': '2020-09-11T17:15:00Z'}
|
1.4.0
|
GHSA-jf43-3v8j-qwwr
|
2023-06-13T20:04:37Z
|
2021-08-25T20:59:56Z
| null |
[]
|
Data races in multiqueue
|
Affected versions of multiqueue unconditionally implemented `Send` for types used in queue implementations (`InnerSend<RW, T>`, `InnerRecv<RW, T>`, `FutInnerSend<RW, T>`, `FutInnerRecv<RW, T>`). This allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior.
|
[{'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': 'multiqueue'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.3.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/schets/multiqueue/issues/31'}, {'type': 'PACKAGE', 'url': 'https://github.com/schets/multiqueue'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0143.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-09T17:20:06Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-v5r6-6r3c-wqxc
|
2021-08-19T21:22:28Z
|
2021-08-25T20:44:56Z
| null |
['CVE-2019-15549']
|
Memory exhaustion in asn1_der
|
An issue was discovered in the asn1_der crate before 0.6.2 for Rust. Attackers can trigger memory exhaustion by supplying a large value in a length field.
|
[{'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': 'asn1_der'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.6.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-15549'}, {'type': 'WEB', 'url': 'https://github.com/KizzyCode/asn1_der/issues/1'}, {'type': 'PACKAGE', 'url': 'https://github.com/KizzyCode/asn1_der'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0007.html'}]
|
{'cwe_ids': ['CWE-400'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:22:28Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-278g-rq84-9hmg
|
2021-08-24T15:39:40Z
|
2021-08-25T14:41:36Z
| null |
['CVE-2021-37673']
|
`CHECK`-fail in `MapStage`
|
### Impact
An attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.MapStage`:
```python
import tensorflow as tf
tf.raw_ops.MapStage(
key=tf.constant([], shape=[0, 0, 0, 0], dtype=tf.int64),
indices=tf.constant((0), dtype=tf.int32),
values=[tf.constant((0), dtype=tf.int32)],
dtypes=[tf.int32,
tf.int64],
capacity=0,
memory_limit=0,
container='',
shared_name='')
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L513) does not check that the `key` input is a valid non-empty tensor.
### Patches
We have patched the issue in GitHub commit [d7de67733925de196ec8863a33445b73f9562d1d](https://github.com/tensorflow/tensorflow/commit/d7de67733925de196ec8863a33445b73f9562d1d).
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 Ying Wang and Yakun Zhang of Baidu X-Team.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '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-278g-rq84-9hmg'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37673'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/d7de67733925de196ec8863a33445b73f9562d1d'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-20'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T15:34:22Z', 'nvd_published_at': '2021-08-12T23:15:00Z'}
|
1.4.0
|
GHSA-9697-98pf-4rw7
|
2021-08-24T14:24:19Z
|
2021-08-25T14:41:44Z
| null |
['CVE-2021-37670']
|
Heap OOB in `UpperBound` and `LowerBound`
|
### Impact
An attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to `tf.raw_ops.UpperBound`:
```python
import tensorflow as tf
tf.raw_ops.UpperBound(
sorted_input=[1,2,3],
values=tf.constant(value=[[0,0,0],[1,1,1],[2,2,2]],dtype=tf.int64),
out_type=tf.int64)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/searchsorted_op.cc#L85-L104) does not validate the rank of `sorted_input` argument:
```cc
void Compute(OpKernelContext* ctx) override {
const Tensor& sorted_inputs_t = ctx->input(0);
// ...
OP_REQUIRES(ctx, sorted_inputs_t.dim_size(0) == values_t.dim_size(0),
Status(error::INVALID_ARGUMENT,
"Leading dim_size of both tensors must match."));
// ...
if (output_t->dtype() == DT_INT32) {
OP_REQUIRES(ctx,
FastBoundsCheck(sorted_inputs_t.dim_size(1), ...));
// ...
}
```
As we access the first two dimensions of `sorted_inputs_t` tensor, it must have rank at least 2.
A similar issue occurs in `tf.raw_ops.LowerBound`.
### Patches
We have patched the issue in GitHub commit [42459e4273c2e47a3232cc16c4f4fff3b3a35c38](https://github.com/tensorflow/tensorflow/commit/42459e4273c2e47a3232cc16c4f4fff3b3a35c38).
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:N'}]
|
[{'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-9697-98pf-4rw7'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37670'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/42459e4273c2e47a3232cc16c4f4fff3b3a35c38'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T14:24:19Z', 'nvd_published_at': '2021-08-12T23:15:00Z'}
|
1.4.0
|
GHSA-h3qr-rq2j-74w4
|
2023-06-13T17:40:10Z
|
2021-08-25T20:46:08Z
| null |
['CVE-2020-35863']
|
HTTP Request Smuggling in hyper
|
Vulnerable versions of hyper allow GET requests to have bodies, even if there is no Transfer-Encoding or Content-Length header. As per the HTTP 1.1 specification, such requests do not have bodies, so the body will be interpreted as a separate HTTP request.
This allows an attacker who can control the body and method of an HTTP request made by hyper to inject a request with headers that would not otherwise be allowed, as demonstrated by sending a malformed HTTP request from a Substrate runtime. This allows bypassing CORS restrictions. In combination with other vulnerabilities, such as an exploitable web server listening on loopback, it may allow remote code execution.
The flaw was corrected in hyper version 0.12.34.
|
[{'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': 'hyper'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.11.0'}, {'fixed': '0.12.34'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35863'}, {'type': 'WEB', 'url': 'https://github.com/hyperium/hyper/issues/1925'}, {'type': 'PACKAGE', 'url': 'https://github.com/hyperium/hyper'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0008.html'}]
|
{'cwe_ids': ['CWE-444'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:20:11Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-2rqw-v265-jf8c
|
2023-07-03T22:56:34Z
|
2021-08-26T20:36:51Z
| null |
['CVE-2021-22942']
|
Open Redirect in ActionPack
|
# Overview
There is a possible open redirect vulnerability in the Host Authorization
middleware in Action Pack. This vulnerability has been assigned the CVE
identifier CVE-2021-22942.
Versions Affected: >= 6.0.0.
Not affected: < 6.0.0
Fixed Versions: 6.1.4.1, 6.0.4.1
# Impact
Specially crafted “X-Forwarded-Host” headers in combination with certain
“allowed host” formats can cause the Host Authorization middleware in
Action Pack to redirect users to a malicious website.
Impacted applications will have allowed hosts with a leading dot.
For example, configuration files that look like this:
```ruby
config.hosts << '.EXAMPLE.com'
```
When an allowed host contains a leading dot, a specially crafted
Host header can be used to redirect to a malicious website.
This vulnerability is similar to CVE-2021-22881, but CVE-2021-22881 did not
take in to account domain name case sensitivity.
# Releases
The fixed releases are available at the normal locations.
# Workarounds
In the case a patch can’t be applied, the following monkey patch can be
used in an initializer:
```ruby
module ActionDispatch
class HostAuthorization
HOSTNAME = /[a-z0-9.-]+|\[[a-f0-9]*:[a-f0-9.:]+\]/i
VALID_ORIGIN_HOST = /\A(#{HOSTNAME})(?::\d+)?\z/
VALID_FORWARDED_HOST = /(?:\A|,[ ]?)(#{HOSTNAME})(?::\d+)?\z/
private
def authorized?(request)
origin_host =
request.get_header("HTTP_HOST")&.slice(VALID_ORIGIN_HOST, 1) || ""
forwarded_host =
request.x_forwarded_host&.slice(VALID_FORWARDED_HOST, 1) || ""
@permissions.allows?(origin_host) &&
(forwarded_host.blank? || @permissions.allows?(forwarded_host))
end
end
end
```
|
[{'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': 'actionpack'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '6.0.0'}, {'fixed': '6.0.4.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.0.4'}}, {'package': {'ecosystem': 'RubyGems', 'name': 'actionpack'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '6.1.0'}, {'fixed': '6.1.4.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.1.4'}}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-22942'}, {'type': 'WEB', 'url': 'https://access.redhat.com/security/cve/cve-2021-22942'}, {'type': 'PACKAGE', 'url': 'https://github.com/rails/rails/tree/main/actionpack'}, {'type': 'WEB', 'url': 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/actionpack/CVE-2021-22942.yml'}, {'type': 'WEB', 'url': 'https://groups.google.com/g/rubyonrails-security/c/wB5tRn7h36c'}, {'type': 'WEB', 'url': 'https://rubygems.org/gems/actionpack'}, {'type': 'WEB', 'url': 'https://weblog.rubyonrails.org/2021/8/19/Rails-6-0-4-1-and-6-1-4-1-have-been-released/'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2023/dsa-5372'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/12/14/5'}]
|
{'cwe_ids': ['CWE-601'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-26T20:36:25Z', 'nvd_published_at': '2021-10-18T13:15:00Z'}
|
1.4.0
|
GHSA-rjh8-p66p-jrh5
|
2021-08-19T21:18:47Z
|
2021-08-25T20:46:59Z
| null |
['CVE-2020-35871']
|
Data races in rusqlite
|
An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via an Auxdata API data race.
|
[{'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': '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-35871'}, {'type': 'WEB', 'url': 'https://github.com/rusqlite/rusqlite/commit/2ef3628dac35aeba0a97d5fb3a57746b4e1d62b3'}, {'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': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:18:47Z', 'nvd_published_at': '2020-12-31T10:15:00Z'}
|
1.4.0
|
GHSA-c5c9-8c6m-727v
|
2021-10-21T13:56:39Z
|
2021-08-19T15:53:12Z
| null |
['CVE-2021-32768']
|
Cross-Site Scripting via Rich-Text Content
|
> ### Meta
> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.7)
### Problem
Failing to properly parse, sanitize and encode malicious rich-text content, the content rendering process in the website frontend is vulnerable to cross-site scripting. Corresponding rendering instructions via TypoScript functionality _[HTMLparser](https://docs.typo3.org/m/typo3/reference-typoscript/10.4/en-us/Functions/Htmlparser.html)_ do not consider all potentially malicious HTML tag & attribute combinations per default.
In addition, the lack of comprehensive default node configuration for rich-text fields in the backend user interface fosters this malfunction.
In default scenarios, a valid backend user account is needed to exploit this vulnerability. In case custom plugins used in the website frontend accept and reflect rich-text content submitted by users, no authentication is required.
### Solution
Update to TYPO3 versions 7.6.53 ELTS, 8.7.42 ELTS, 9.5.29, 10.4.19, 11.3.2 that fix the problem described above.
Custom package _[typo3/html-sanitizer](https://github.com/TYPO3/html-sanitizer)_ - based on allow-lists only - takes care of sanitizing potentially malicious markup. The default behavior is based on safe and commonly used markup - however, this can be extended or restricted further in case it is necessary for individual scenarios.
During the frontend rendering process, sanitization is applied to the default TypoScript path `lib.parseFunc`, which is implicitly used by the Fluid view-helper instruction `f:format.html`. Rich-text data persisted using the backend user interface is sanitized as well. Implementation details are explained in corresponding [ChangeLog documentation](https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/9.5.x/Important-94484-IntroduceHTMLSanitizer.html).
### Credits
Thanks to Benjamin Stiber, Gert-Jan Jansma, Gábor Ács-Kurucz, Alexander Kellner, Richie Lee, Nina Rösch who reported this issue, and to TYPO3 security team member Oliver Hader, as well as TYPO3 contributor Susanne Moog who fixed the issue.
### References
* [TYPO3-CORE-SA-2021-013](https://typo3.org/security/advisory/typo3-core-sa-2021-013)
|
[{'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': 'Packagist', 'name': 'typo3/cms-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '7.0.0'}, {'fixed': '7.6.53'}]}], 'database_specific': {'last_known_affected_version_range': '<= 7.6.52'}}, {'package': {'ecosystem': 'Packagist', 'name': 'typo3/cms-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '8.0.0'}, {'fixed': '8.7.42'}]}], 'database_specific': {'last_known_affected_version_range': '<= 8.7.41'}}, {'package': {'ecosystem': 'Packagist', 'name': 'typo3/cms-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '9.0.0'}, {'fixed': '9.5.29'}]}], 'database_specific': {'last_known_affected_version_range': '<= 9.5.28'}}, {'package': {'ecosystem': 'Packagist', 'name': 'typo3/cms-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '10.0.0'}, {'fixed': '10.4.19'}]}], 'database_specific': {'last_known_affected_version_range': '<= 10.4.18'}}, {'package': {'ecosystem': 'Packagist', 'name': 'typo3/cms-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '11.0.0'}, {'fixed': '11.3.2'}]}], 'database_specific': {'last_known_affected_version_range': '<= 11.3.1'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-c5c9-8c6m-727v'}, {'type': 'WEB', 'url': 'https://github.com/TYPO3/typo3/security/advisories/GHSA-c5c9-8c6m-727v'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-32768'}, {'type': 'WEB', 'url': 'https://typo3.org/security/advisory/typo3-core-sa-2021-013'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-16T22:38:47Z', 'nvd_published_at': '2021-08-10T17:15:00Z'}
|
1.4.0
|
GHSA-jpwg-6gf5-5vh9
|
2023-06-13T20:49:19Z
|
2021-08-25T20:54:10Z
| null |
['CVE-2021-29942']
|
Out of bounds write in reorder
|
swap_index takes an iterator and swaps the items with their corresponding indexes. It reserves capacity and sets the length of the vector based on the .len() method of the iterator.
If the len() returned by the iterator is larger than the actual number of elements yielded, then swap_index creates a vector containing uninitialized members. If the len() returned by the iterator is smaller than the actual number of members yielded, then swap_index can write out of bounds past its allocated vector.
As noted by the Rust documentation, len() and size_hint() are primarily meant for optimization and incorrect values from their implementations should not lead to memory safety violations.
|
[{'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': 'reorder'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.1.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-29942'}, {'type': 'WEB', 'url': 'https://github.com/tiby312/reorder/issues/1'}, {'type': 'PACKAGE', 'url': 'https://github.com/tiby312/reorder'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0050.html'}]
|
{'cwe_ids': ['CWE-787'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:17:03Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-hqc8-j86x-2764
|
2021-08-19T21:06:47Z
|
2021-08-25T20:48:33Z
| null |
['CVE-2020-35893']
|
Off-by-one error in simple-slab
|
An issue was discovered in the simple-slab crate before 0.3.3 for Rust. remove() has an off-by-one error, causing memory leakage and a drop of uninitialized memory.
|
[{'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': 'simple-slab'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.3.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35893'}, {'type': 'WEB', 'url': 'https://github.com/nathansizemore/simple-slab/issues/2'}, {'type': 'WEB', 'url': 'https://github.com/nathansizemore/simple-slab/commit/5e0524c1db836e2192e1cd818848d96937c0b587'}, {'type': 'PACKAGE', 'url': 'https://github.com/nathansizemore/simple-slab'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0039.html'}]
|
{'cwe_ids': ['CWE-193'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:06:47Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-27qf-jwm8-g7f3
|
2021-08-24T18:17:31Z
|
2021-08-25T14:39:17Z
| null |
['CVE-2021-37691']
|
FPE in LSH in TFLite
|
### Impact
An attacker can craft a TFLite model that would trigger a division by zero error in LSH [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/lsh_projection.cc#L118).
```cc
int RunningSignBit(const TfLiteTensor* input, const TfLiteTensor* weight,
float seed) {
int input_item_bytes = input->bytes / SizeOfDimension(input, 0);
// ...
}
```
There is no check that the first dimension of the input is non zero.
### Patches
We have patched the issue in GitHub commit [0575b640091680cfb70f4dd93e70658de43b94f9](https://github.com/tensorflow/tensorflow/commit/0575b640091680cfb70f4dd93e70658de43b94f9).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick thiscommit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Yakun Zhang of Baidu Security.
|
[{'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-27qf-jwm8-g7f3'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37691'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/0575b640091680cfb70f4dd93e70658de43b94f9'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-369'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T18:17:31Z', 'nvd_published_at': '2021-08-12T23:15:00Z'}
|
1.4.0
|
GHSA-8gf5-q9p9-wvmc
|
2021-08-19T18:48:32Z
|
2021-08-25T20:51:42Z
| null |
['CVE-2020-36219']
|
Data race in atomic-option
|
An issue was discovered in the atomic-option crate through 2020-10-31 for Rust. Because AtomicOption<T> implements Sync unconditionally, a data race can occur.
|
[{'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': 'atomic-option'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.1.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36219'}, {'type': 'WEB', 'url': 'https://github.com/reem/rust-atomic-option/issues/4'}, {'type': 'PACKAGE', 'url': 'https://github.com/reem/rust-atomic-option'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0113.html'}]
|
{'cwe_ids': ['CWE-662'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:48:32Z', 'nvd_published_at': '2021-01-26T18:15:00Z'}
|
1.4.0
|
GHSA-w47j-hqpf-qw9w
|
2021-08-19T18:45:15Z
|
2021-08-25T20:52:59Z
| null |
['CVE-2021-25901']
|
Out of bounds read in lazy-init
|
An issue was discovered in the lazy-init crate through 2021-01-17 for Rust. Lazy lacks a Send bound, leading to a data race.
|
[{'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': 'crates.io', 'name': 'lazy-init'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-25901'}, {'type': 'WEB', 'url': 'https://github.com/khuey/lazy-init/issues/9'}, {'type': 'PACKAGE', 'url': 'https://github.com/khuey/lazy-init'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0004.html'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:45:15Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-pphf-f93w-gc84
|
2021-08-19T18:48:04Z
|
2021-08-25T20:51:47Z
| null |
['CVE-2020-36217']
|
Data race in may_queue
|
An issue was discovered in the may_queue crate through 2020-11-10 for Rust. Because Queue does not have bounds on its Send trait or Sync trait, memory corruption can occur.
|
[{'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': 'may_queue'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.1.8'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36217'}, {'type': 'WEB', 'url': 'https://github.com/Xudong-Huang/may/issues/88'}, {'type': 'PACKAGE', 'url': 'https://github.com/Xudong-Huang/may'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0111.html'}]
|
{'cwe_ids': ['CWE-662', 'CWE-787'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:48:04Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-xh2p-7p87-fhgh
|
2021-07-29T20:43:48Z
|
2021-08-05T16:56:58Z
| null |
[]
|
Incorrect TCR calculation in batchLiquidateTroves() during Recovery Mode
|
TCR is temporarily miscalculated in the `batchLiquidateTroves` function during Recovery Mode.
The bug lies in [`batchLiquidateTroves` of `TroveManager`](https://github.com/liquity/dev/blob/7c83ea11378454629618b3808b16fbfda69ee3e5/packages/contracts/contracts/TroveManager.sol#L722).
When calculating system's entire collateral, we should also exclude the liquidated trove's surplus collateral, since liquidation closes the trove and makes the surplus collateral claimable by the trove owner. This means, this line of code should look like this:
```
vars.entireSystemColl = vars.entireSystemColl.sub(singleLiquidation.collToSendToSP).sub(singleLiquidation.collSurplus);
```
### Impact
The miscalculated entire collateral is used only to calculate the TCR and check if the system has been able to exit Recovery Mode. The miscalulation only persists temporarily, and within the`batchLiquidateTroves` transaction. Once the transaction completes the TCR and Recovery Mode will be calculated properly again. However, the bug could negatively impact the liquidation throughput and the gas efficiency gains from batching multiple liquidations in a single transaction.
In normal situations, the impact of the collateral surplus of a Trove on the global TCR would be tiny. For instance, we have calculated that liquidating a trove with a collateral representing 1% of the total system collateral (so in the order of at least $10M at current values), would lead to an extra 0.53% in the temporary miscalculation of TCR. So for this bug to be meaningful, in such a scenario, the resulting real TCR must be already be very close to the Recovery Mode boundary anyway - i.e. between 149.47% and 150%. The batch liquidation transaction should also be executed with a particular trove ordering to achieve the TCR distortion. When a different trove order for the liquidation transaction is selected, the bug has no impact. In summary, the bug only has a non-negligible impact in a very narrow, specific set of circumstances.
The potential effects of the bug after it occurs are:
- The next trove in the sequence is not liquidated because the `batchLiquidateTroves` function calculates a premature exit from Recovery Mode. It could be liquidated in a subsequent transaction if the price of Ether doesn’t recover.
- The next trove in the sequence has an ICR below 100% and it’s offset against the Stability Pool instead of redistributed among other troves because the function calculates a premature exit from Recovery Mode. For this to happen, the Ether price must have instantly plummeted by more than 10% (otherwise, the trove would have been already liquidated before).
- The next trove in the sequence is liquidated while its ICR is over the real TCR: the function calculates the TCR as being slightly too high, and thus can liquidate a trove that has ICR less than the calculated TCR, but greater than the true TCR. This is probably the worst outcome - however it is already possible to achieve the same effect, regardless of the bug. A liquidator can craft a `batchLiquidateTroves` transaction whereby they select troves for liquidation such that the TCR increases and makes a given trove liquidateable. To liquidate trove A, they can order troves such that they first liquidate troves which raise the TCR to between A's ICR and 150%. This is intended and expected behavior. As clearly stated in Liquity documentation, to be completely safe and guarantee immunity from liquidation in Recovery Mode, borrowers should keep their ICR above 150%.
We don't believe this bug creates a profitable exploit. Theoretically, and only in a very narrow set of circumstances, a liquidator could try to send a batch liquidation during Recovery Mode that lets the system very temporarily return to Normal Mode earlier than it should. In that case - _and only if the Ether price also happens to suddenly plummet by more than 10%_ - stability providers might take the haircut that should be taken by the borrowers (through redistribution).
### Patches
The problem has been patched in the source code but not on mainnet contracts. Liquity protocol is immutable, and this issue is not critical, so it doesn't merit a launch of a new version.
### Bug bounty
A reward of $1,000 (the maximum for its category) was awarded to Xiahong (`gaoxh06`) for reporting this bug.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [our repo](https://github.com/liquity/dev)
* Email us at [security@liquity.org](mailto:security@liquity.org)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': '@liquity/contracts'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.0.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/liquity/dev/security/advisories/GHSA-xh2p-7p87-fhgh'}, {'type': 'WEB', 'url': 'https://github.com/liquity/dev/commit/c69d0bae30b5457e89724d880851a03ba7477905'}, {'type': 'WEB', 'url': 'https://github.com/liquity/dev/blob/7c83ea11378454629618b3808b16fbfda69ee3e5/packages/contracts/contracts/TroveManager.sol#L722'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/package/@liquity/contracts'}]
|
{'cwe_ids': ['CWE-682'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2021-07-29T20:43:48Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-hpv4-7p9c-mvfr
|
2021-08-23T23:20:28Z
|
2021-08-25T14:43:21Z
| null |
['CVE-2021-37651']
|
Heap buffer overflow in `FractionalAvgPoolGrad`
|
### Impact
The implementation for `tf.raw_ops.FractionalAvgPoolGrad` can be tricked into accessing data outside of bounds of heap allocated buffers:
```python
import tensorflow as tf
tf.raw_ops.FractionalAvgPoolGrad(
orig_input_tensor_shape=[0,1,2,3],
out_backprop = np.array([[[[541],[541]],[[541],[541]]]]),
row_pooling_sequence=[0, 0, 0, 0, 0],
col_pooling_sequence=[-2, 0, 0, 2, 0],
overlapping=True)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/fractional_avg_pool_op.cc#L205) does not validate that the input tensor is non-empty. Thus, code constructs an empty `EigenDoubleMatrixMap` and then accesses this buffer with indices that are outside of the empty area.
### Patches
We have patched the issue in GitHub commit [0f931751fb20f565c4e94aa6df58d54a003cdb30](https://github.com/tensorflow/tensorflow/commit/0f931751fb20f565c4e94aa6df58d54a003cdb30).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### 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:N'}]
|
[{'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-hpv4-7p9c-mvfr'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37651'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/0f931751fb20f565c4e94aa6df58d54a003cdb30'}]
|
{'cwe_ids': ['CWE-125', 'CWE-787'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T23:20:28Z', 'nvd_published_at': '2021-08-12T21:15:00Z'}
|
1.4.0
|
GHSA-r98r-j25q-rmpr
|
2023-08-25T00:12:20Z
|
2021-08-25T20:46:38Z
| null |
['CVE-2019-25010']
|
Rust Failure Crate Vulnerable to Type confusion
|
Safe Rust code can implement malfunctioning `__private_get_type_id__` and cause type confusion when downcasting, which is an undefined behavior.
Users who derive Fail trait are not affected.
|
[{'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': 'failure'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.1.8'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-25010'}, {'type': 'WEB', 'url': 'https://github.com/rust-lang-nursery/failure/issues/336'}, {'type': 'PACKAGE', 'url': 'https://github.com/rust-lang-nursery/failure'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0036.html'}]
|
{'cwe_ids': ['CWE-843'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:19:54Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-3vjm-36rr-7qrq
|
2021-08-19T21:18:36Z
|
2021-08-25T20:47:16Z
| null |
['CVE-2020-35860']
|
NULL Pointer Dereference in cbox
|
An issue was discovered in the cbox crate through 2020-03-19 for Rust. The CBox API allows dereferencing raw pointers without a requirement for unsafe code.
|
[{'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': 'cbox'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.3.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35860'}, {'type': 'WEB', 'url': 'https://github.com/TomBebbington/cbox-rs/issues/2'}, {'type': 'PACKAGE', 'url': 'https://github.com/TomBebbington/cbox-rs'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0005.html'}]
|
{'cwe_ids': ['CWE-476'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:18:36Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-26rr-v2j2-25fh
|
2021-08-30T16:42:41Z
|
2021-08-30T17:20:52Z
| null |
['CVE-2021-32758']
|
Layout XML Arbitrary Code Fix
|
### Impact
Layout XML enabled admin users to execute arbitrary commands via block methods.
|
[]
|
[{'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-26rr-v2j2-25fh'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-32758'}, {'type': 'WEB', 'url': 'https://github.com/OpenMage/magento-lts/commit/b99307d00b59c4a226a1e3e4083f02cf2fc8fce7'}, {'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-91'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-30T16:42:41Z', 'nvd_published_at': '2021-08-27T18:15:00Z'}
|
1.4.0
|
GHSA-hq5m-mqmx-fw6m
|
2023-04-25T16:37:13Z
|
2021-08-23T19:41:22Z
| null |
['CVE-2021-37627']
|
Privilege escalation via form generator
|
### Impact
It is possible for untrusted users to gain administrator rights with the form generator.
Installations are only affected if there are untrusted back end users with access to the form generator.
### Patches
Update to Contao 4.4.56, 4.9.18 or 4.11.7.
### Workarounds
Disable the form generator or disable the login for untrusted back end users.
### References
https://contao.org/en/security-advisories/privilege-escalation-with-the-form-generator
### For more information
If you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'contao/core-bundle'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.0.0'}, {'fixed': '4.4.56'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'contao/core-bundle'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.5.0'}, {'fixed': '4.9.18'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'contao/core-bundle'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.10.0'}, {'fixed': '4.11.7'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/contao/contao/security/advisories/GHSA-hq5m-mqmx-fw6m'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37627'}, {'type': 'WEB', 'url': 'https://contao.org/en/security-advisories/privilege-escalation-with-the-form-generator.html'}, {'type': 'PACKAGE', 'url': 'https://github.com/contao/contao'}]
|
{'cwe_ids': ['CWE-269'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T16:52:36Z', 'nvd_published_at': '2021-08-11T23:15:00Z'}
|
1.4.0
|
GHSA-fhv4-fx3v-77w6
|
2023-06-13T20:31:29Z
|
2021-08-25T20:52:05Z
| null |
['CVE-2021-28036']
|
quinn invalidly assumes the memory layout of std::net::SocketAddr
|
The quinn 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:N/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'quinn'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.5.4'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'quinn'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.6.0'}, {'fixed': '0.6.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-28036'}, {'type': 'WEB', 'url': 'https://github.com/quinn-rs/quinn/issues/968'}, {'type': 'PACKAGE', 'url': 'https://github.com/quinn-rs/quinn'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0035.html'}]
|
{'cwe_ids': ['CWE-119'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:25:47Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-ch4f-829c-v5pw
|
2021-08-23T18:58:49Z
|
2021-08-25T14:43:56Z
| null |
['CVE-2021-37642']
|
Division by 0 in `ResourceScatterDiv`
|
### Impact
The implementation of `tf.raw_ops.ResourceScatterDiv` is vulnerable to a division by 0 error:
```python
import tensorflow as tf
v= tf.Variable([1,2,3])
tf.raw_ops.ResourceScatterDiv(
resource=v.handle,
indices=[1],
updates=[0])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/resource_variable_ops.cc#L865) uses a common class for all binary operations but fails to treat the division by 0 case separately.
### Patches
We have patched the issue in GitHub commit [4aacb30888638da75023e6601149415b39763d76](https://github.com/tensorflow/tensorflow/commit/4aacb30888638da75023e6601149415b39763d76).
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-ch4f-829c-v5pw'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37642'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/4aacb30888638da75023e6601149415b39763d76'}]
|
{'cwe_ids': ['CWE-369'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T18:58:49Z', 'nvd_published_at': '2021-08-12T18:15:00Z'}
|
1.4.0
|
GHSA-h563-xh25-x54q
|
2021-08-30T23:23:11Z
|
2021-08-09T20:37:50Z
| null |
['CVE-2021-37914']
|
Workflow re-write vulnerability using input parameter
|
### Impact
* Allow end-users to set input parameters, but otherwise expect workflows to be secure.
### Patches
Not yet.
### Workarounds
* Set `EXPRESSION_TEMPLATES=false` for the workflow controller
### References
* https://github.com/argoproj/argo-workflows/issues/6441
### 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)
|
[]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/argoproj/argo-workflows/v3'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.1.0'}, {'fixed': '3.1.6'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/argoproj/argo-workflows/security/advisories/GHSA-h563-xh25-x54q'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37914'}, {'type': 'WEB', 'url': 'https://github.com/argoproj/argo-workflows/issues/6441'}, {'type': 'WEB', 'url': 'https://github.com/argoproj/argo-workflows/pull/6285'}, {'type': 'WEB', 'url': 'https://github.com/argoproj/argo-workflows/pull/6442'}, {'type': 'WEB', 'url': 'https://github.com/argoproj/argo-workflows/commit/2a2ecc916925642fd8cb1efd026588e6828f82e1'}, {'type': 'PACKAGE', 'url': 'github.com/argoproj/argo-workflows/v3'}]
|
{'cwe_ids': ['CWE-20'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-04T18:26:07Z', 'nvd_published_at': '2021-08-03T00:15:00Z'}
|
1.4.0
|
GHSA-28ph-f7gx-fqj8
|
2021-08-19T21:08:12Z
|
2021-08-25T20:47:57Z
| null |
['CVE-2020-35867']
|
Data races in rusqlite
|
An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via create_module.
|
[{'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-35867'}, {'type': 'WEB', 'url': 'https://github.com/rusqlite/rusqlite/commit/3c6b57fe1b2cc87e7ebecde43dd836ffb1c4ea5c'}, {'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:12Z', 'nvd_published_at': '2020-12-31T10:15:00Z'}
|
1.4.0
|
GHSA-3933-wvjf-pcvc
|
2023-06-13T20:06:37Z
|
2021-08-25T20:46:16Z
| null |
['CVE-2020-35859']
|
Out of bounds access in lucet-runtime-internals
|
An embedding using affected versions of lucet-runtime configured to use non-default Wasm globals sizes of more than 4KiB, or compiled in debug mode without optimizations, could leak data from the signal handler stack to guest programs. This can potentially cause data from the embedding host to leak to guest programs or cause corruption of guest program memory. This flaw was resolved by correcting the sigstack allocation logic.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'lucet-runtime-internals'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.3'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'lucet-runtime-internals'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.5.0'}, {'fixed': '0.5.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35859'}, {'type': 'WEB', 'url': 'https://github.com/bytecodealliance/lucet/pull/401'}, {'type': 'PACKAGE', 'url': 'https://github.com/fastly/lucet'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0004.html'}]
|
{'cwe_ids': ['CWE-125', 'CWE-787'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:19:58Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-369h-pjr2-6wrh
|
2023-06-13T22:25:06Z
|
2021-08-25T20:43:16Z
| null |
['CVE-2018-20994']
|
Uncontrolled recursion in trust-dns-proto
|
There's a stack overflow leading to a crash when Trust-DNS's parses a malicious DNS packet. Affected versions of this crate did not properly handle parsing of DNS message compression (RFC1035 section 4.1.4). The parser could be tricked into infinite loop when a compression offset pointed back to the same domain name to be parsed. This allows an attacker to craft a malicious DNS packet which when consumed with Trust-DNS could cause stack overflow and crash the affected software.
|
[{'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': 'trust-dns-proto'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2018-20994'}, {'type': 'PACKAGE', 'url': 'https://github.com/bluejekyll/trust-dns'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2018-0007.html'}]
|
{'cwe_ids': ['CWE-674'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:24:41Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-r626-fc64-3q28
|
2023-06-13T22:20:26Z
|
2021-08-25T20:59:06Z
| null |
['CVE-2020-36441']
|
Data race in abox
|
Affected versions of this crate implements `Send`/`Sync` for `AtomicBox<T>` without requiring `T: Send`/`T: Sync`. This allows to create data races to `T: !Sync` and send `T: !Send` to another thread. Such behavior breaks the compile-time thread safety guarantees of Rust, and allows users to incur undefined behavior using safe Rust (e.g. memory corruption from data race). The flaw was corrected in commit `34c2b9e` by adding trait bound `T: Send` to `Send` impl for `AtomicBox<T>` and trait bound `T: Sync` to `Sync` impl for `AtomicBox<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': 'abox'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36441'}, {'type': 'WEB', 'url': 'https://github.com/SonicFrog/abox/issues/1'}, {'type': 'WEB', 'url': 'https://github.com/SonicFrog/abox/pull/2'}, {'type': 'WEB', 'url': 'https://github.com/SonicFrog/abox/commit/34c2b9e'}, {'type': 'PACKAGE', 'url': 'https://github.com/SonicFrog/abox'}, {'type': 'WEB', 'url': 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/abox/RUSTSEC-2020-0121.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0121.html'}]
|
{'cwe_ids': ['CWE-119', 'CWE-362'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-09T21:56:03Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-5rc4-8qqh-vq7f
|
2023-09-12T20:58:59Z
|
2021-08-09T22:24:26Z
| null |
['CVE-2018-3718']
|
vercel/serve allows access to restricted files if filename is URL encoded.
|
serve node module suffers from Improper Handling of URL Encoding by permitting access to ignored files if a filename is URL encoded.
|
[{'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': 'npm', 'name': 'serve'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.5.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2018-3718'}, {'type': 'WEB', 'url': 'https://hackerone.com/reports/308721'}, {'type': 'PACKAGE', 'url': 'https://github.com/vercel/serve'}]
|
{'cwe_ids': ['CWE-177'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-09T22:24:10Z', 'nvd_published_at': '2018-06-07T02:29:00Z'}
|
1.4.0
|
GHSA-pf3p-x6qj-6j7q
|
2023-06-13T18:42:58Z
|
2021-08-25T20:50:33Z
| null |
['CVE-2020-35922']
|
mio invalidly assumes the memory layout of std::net::SocketAddr
|
The mio 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:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'mio'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.7.0'}, {'fixed': '0.7.6'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35922'}, {'type': 'WEB', 'url': 'https://github.com/tokio-rs/mio/issues/1386'}, {'type': 'WEB', 'url': 'https://github.com/tokio-rs/mio/pull/1388'}, {'type': 'WEB', 'url': 'https://github.com/tokio-rs/mio/commit/152e0751f0be1c9b0cbd6778645b76bcb0eba93c'}, {'type': 'PACKAGE', 'url': 'https://github.com/tokio-rs/mio'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0081.html'}]
|
{'cwe_ids': ['CWE-188'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:54:14Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-9f5r-vqm5-m342
|
2023-06-13T20:06:12Z
|
2021-08-25T20:53:16Z
| null |
['CVE-2021-26952']
|
Use of Uninitialized Resource in ms3d
|
Affected versions of this crate passes an uninitialized buffer to a user-provided Read implementation. Arbitrary Read implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.
The flaw was fixed in commit `599313b` by zero-initializing the buffer (via self.buf.resize(len, 0)) before passing it to Read.
|
[{'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': 'ms3d'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.1.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-26952'}, {'type': 'WEB', 'url': 'https://github.com/andrewhickman/ms3d/issues/1'}, {'type': 'WEB', 'url': 'https://github.com/andrewhickman/ms3d/commit/599313b'}, {'type': 'PACKAGE', 'url': 'https://github.com/andrewhickman/ms3d'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0016.html'}]
|
{'cwe_ids': ['CWE-908'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:44:22Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-27j5-4p9v-pp67
|
2021-08-23T19:16:53Z
|
2021-08-25T14:43:40Z
| null |
['CVE-2021-37644']
|
`std::abort` raised from `TensorListReserve`
|
### Impact
Providing a negative element to `num_elements` list argument of `tf.raw_ops.TensorListReserve` causes the runtime to abort the process due to reallocating a `std::vector` to have a negative number of elements:
```python
import tensorflow as tf
tf.raw_ops.TensorListReserve(
element_shape = tf.constant([1]),
num_elements=tf.constant([-1]),
element_dtype = tf.int32)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/list_kernels.cc#L312) calls `std::vector.resize()` with the new size controlled by input given by the user, without checking that this input is valid.
### Patches
We have patched the issue in GitHub commit [8a6e874437670045e6c7dc6154c7412b4a2135e2](https://github.com/tensorflow/tensorflow/commit/8a6e874437670045e6c7dc6154c7412b4a2135e2).
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-27j5-4p9v-pp67'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37644'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/8a6e874437670045e6c7dc6154c7412b4a2135e2'}]
|
{'cwe_ids': ['CWE-617'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T19:16:53Z', 'nvd_published_at': '2021-08-12T21:15:00Z'}
|
1.4.0
|
GHSA-gppw-3h6h-v6q2
|
2021-08-19T17:26:00Z
|
2021-08-25T20:52:08Z
| null |
['CVE-2021-28037']
|
Data race in internment
|
An issue was discovered in the internment crate before 0.4.2 for Rust. There is a data race that can cause memory corruption because of the unconditional implementation of Sync for Intern<T>.
|
[{'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': 'internment'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-28037'}, {'type': 'WEB', 'url': 'https://github.com/droundy/internment/issues/20'}, {'type': 'PACKAGE', 'url': 'https://github.com/droundy/internment'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0036.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:26:00Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-f2c9-5jqw-3xh3
|
2023-09-05T21:59:59Z
|
2021-08-02T17:23:39Z
| null |
['CVE-2021-28796']
|
Cross-Site Scripting in Qiita-Markdown
|
Increments Qiita-Markdown before 0.33.0 allows XSS in transformers.
|
[{'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'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.33.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-28796'}, {'type': 'ADVISORY', 'url': 'https://github.com/advisories/GHSA-f2c9-5jqw-3xh3'}, {'type': 'PACKAGE', 'url': 'https://github.com/increments/qiita-markdown'}, {'type': 'WEB', 'url': 'https://github.com/increments/qiita-markdown/compare/v0.32.0...v0.33.0'}, {'type': 'WEB', 'url': 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/qiita-markdown/CVE-2021-28796.yml'}, {'type': 'WEB', 'url': 'https://vuln.ryotak.me/advisories/15'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-02T17:23:26Z', 'nvd_published_at': '2021-03-18T16:15:00Z'}
|
1.4.0
|
GHSA-whc7-5p35-4ww2
|
2021-08-19T20:54:21Z
|
2021-08-25T20:49:06Z
| null |
['CVE-2020-35899']
|
Use after free in actix-service
|
An issue was discovered in the actix-service crate before 1.0.6 for Rust. The Cell implementation allows obtaining more than one mutable reference to the same data.
|
[{'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': 'actix-service'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.0.6'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35899'}, {'type': 'WEB', 'url': 'https://github.com/actix/actix-net/pull/158'}, {'type': 'PACKAGE', 'url': 'https://github.com/actix/actix-net'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0046.html'}]
|
{'cwe_ids': ['CWE-416'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T20:54:21Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-36cg-4jff-5863
|
2023-06-13T20:41:14Z
|
2021-08-25T20:59:13Z
| null |
['CVE-2020-36446']
|
Data races in signal-simple
|
Affected versions of this crate unconditionally implement Send/Sync for SyncChannel<T>. SyncChannel<T> doesn't provide access to &T but merely serves as a channel that consumes and returns owned T.
Users can create UB in safe Rust by sending T: !Send to other threads with SyncChannel::send/recv APIs. Using T = Arc<Cell<_> allows to create data races (which can lead to memory corruption), and using T = MutexGuard<T> allows to unlock a mutex from a thread that didn't lock the mutex.
|
[{'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': 'signal-simple'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.1.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36446'}, {'type': 'WEB', 'url': 'https://github.com/kitsuneninetails/signal-rust/issues/2'}, {'type': 'WEB', 'url': 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/signal-simple/RUSTSEC-2020-0126.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0126.html'}, {'type': 'PACKAGE', 'url': 'http://github.com/kitsuneninetails/signal-rust'}]
|
{'cwe_ids': ['CWE-119', 'CWE-362'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-09T21:44:31Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-qpgv-g792-wh6x
|
2021-08-19T17:21:25Z
|
2021-08-25T20:54:04Z
| null |
['CVE-2021-29932']
|
Uncontrolled Resource Consumption in parse_duration
|
An issue was discovered in the parse_duration crate through 2021-03-18 for Rust. It allows attackers to cause a denial of service (CPU and memory consumption) via a duration string with a large exponent.
|
[{'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': 'parse_duration'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '2.1.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-29932'}, {'type': 'WEB', 'url': 'https://github.com/zeta12ti/parse_duration/issues/21'}, {'type': 'PACKAGE', 'url': 'https://github.com/zeta12ti/parse_duration'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0041.html'}]
|
{'cwe_ids': ['CWE-400'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:21:25Z', 'nvd_published_at': '2021-04-01T05:15:00Z'}
|
1.4.0
|
GHSA-r43h-gmrm-h5c9
|
2021-08-19T21:21:41Z
|
2021-08-25T20:45:09Z
| null |
['CVE-2020-25573']
|
Access of Uninitialized Pointer in linked-hash-map
|
An issue was discovered in the linked-hash-map crate before 0.5.3 for Rust. It creates an uninitialized NonNull pointer, which violates a non-null constraint.
|
[{'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': 'linked-hash-map'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.5.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-25573'}, {'type': 'WEB', 'url': 'https://github.com/contain-rs/linked-hash-map/pull/100'}, {'type': 'PACKAGE', 'url': 'https://github.com/contain-rs/linked-hash-map'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0026.html'}]
|
{'cwe_ids': ['CWE-824'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:21:41Z', 'nvd_published_at': '2020-09-14T19:15:00Z'}
|
1.4.0
|
GHSA-39wr-f4ff-xm6p
|
2023-06-13T21:56:16Z
|
2021-08-25T20:46:41Z
| null |
['CVE-2019-25007']
|
Incorrect implementation in streebog
|
Internal update-sigma function was implemented incorrectly and depending on debug-assertions it could've caused an incorrect result or panic for certain inputs.
|
[{'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': 'streebog'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.8.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-25007'}, {'type': 'WEB', 'url': 'https://github.com/RustCrypto/hashes/pull/91'}, {'type': 'PACKAGE', 'url': 'https://github.com/RustCrypto/hashes/tree/master/streebog'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0030.html'}]
|
{'cwe_ids': ['CWE-617'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:19:50Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-vh4p-6j7g-f4j9
|
2021-08-19T20:49:28Z
|
2021-08-25T20:49:56Z
| null |
['CVE-2020-35911']
|
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 MappedRwLockReadGuard 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::MappedRwLockReadGuard']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35911'}, {'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-19T20:49:28Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-vj72-mwrj-m2xq
|
2021-08-31T21:21:45Z
|
2021-08-10T16:09:25Z
| null |
['CVE-2021-23417']
|
Prototype Pollution in deepmergefn
|
All versions of package deepmergefn are vulnerable to Prototype Pollution via deepMerge function.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'deepmergefn'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.1.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-23417'}, {'type': 'PACKAGE', 'url': 'https://github.com/jesusgm/deepmergefn'}, {'type': 'WEB', 'url': 'https://github.com/jesusgm/deepmergefn/blob/master/index.js#23L6'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JS-DEEPMERGEFN-1310984'}]
|
{'cwe_ids': ['CWE-1321', 'CWE-915'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-02T18:38:21Z', 'nvd_published_at': '2021-07-28T16:15:00Z'}
|
1.4.0
|
GHSA-j9h8-phrw-h4fh
|
2022-02-08T21:00:39Z
|
2021-08-25T14:48:19Z
| null |
['CVE-2021-39144']
|
XStream is vulnerable to a Remote Command Execution attack
|
### Impact
The vulnerability may allow a remote attacker has sufficient rights to execute commands of the 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-39144](https://x-stream.github.io/CVE-2021-39144.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)
* Email 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-j9h8-phrw-h4fh'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39144'}, {'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-39144.html'}, {'type': 'WEB', 'url': 'http://packetstormsecurity.com/files/169859/VMware-NSX-Manager-XStream-Unauthenticated-Remote-Code-Execution.html'}]
|
{'cwe_ids': ['CWE-306', 'CWE-502', 'CWE-94'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T18:22:07Z', 'nvd_published_at': '2021-08-23T18:15:00Z'}
|
1.4.0
|
GHSA-rh89-x75f-rh3c
|
2023-06-13T18:43:22Z
|
2021-08-25T20:44:00Z
| null |
['CVE-2019-15553']
|
Exposure of uninitialized memory in memoffset
|
Affected versions of this crate caused traps and/or memory unsafety by zero-initializing references. They also could lead to uninitialized memory being dropped if the field for which the offset is requested was behind a deref coercion, and that deref coercion caused a panic. The flaw was corrected by using MaybeUninit.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'memoffset'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.5.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-15553'}, {'type': 'WEB', 'url': 'https://github.com/Gilnaa/memoffset/issues/9#issuecomment-505461490'}, {'type': 'PACKAGE', 'url': 'https://github.com/Gilnaa/memoffset'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0011.html'}]
|
{'cwe_ids': ['CWE-908'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:23:41Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-wp77-4gmm-7cq8
|
2021-08-23T21:12:17Z
|
2021-08-25T14:43:29Z
| null |
['CVE-2021-37648']
|
Incorrect validation of `SaveV2` inputs
|
### Impact
The code for `tf.raw_ops.SaveV2` does not properly validate the inputs and an attacker can trigger a null pointer dereference:
```python
import tensorflow as tf
tf.raw_ops.SaveV2(
prefix=['tensorflow'],
tensor_name=['v'],
shape_and_slices=[],
tensors=[1,2,3])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/save_restore_v2_ops.cc) uses `ValidateInputs` to check that the input arguments are valid. This validation would have caught the illegal state represented by the reproducer above.
However, the validation uses `OP_REQUIRES` which translates to setting the `Status` object of the current `OpKernelContext` to an error status, followed by an empty `return` statement which just terminates the execution of the function it is present in. However, this does not mean that the kernel execution is finalized: instead, execution continues from the next line in `Compute` that follows the call to `ValidateInputs`. This is equivalent to lacking the validation.
### Patches
We have patched the issue in GitHub commit [9728c60e136912a12d99ca56e106b7cce7af5986](https://github.com/tensorflow/tensorflow/commit/9728c60e136912a12d99ca56e106b7cce7af5986).
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-wp77-4gmm-7cq8'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37648'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/9728c60e136912a12d99ca56e106b7cce7af5986'}]
|
{'cwe_ids': ['CWE-476'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T21:12:17Z', 'nvd_published_at': '2021-08-12T22:15:00Z'}
|
1.4.0
|
GHSA-vpw8-43wm-rxw5
|
2021-08-19T17:21:10Z
|
2021-08-25T20:54:06Z
| null |
['CVE-2021-29929']
|
Double free in endian_trait
|
An issue was discovered in the endian_trait crate through 2021-01-04 for Rust. A double drop can occur when a user-provided Endian impl panics.
|
[{'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': 'endian_trait'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.6.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-29929'}, {'type': 'PACKAGE', 'url': 'https://gitlab.com/myrrlyn/endian_trait'}, {'type': 'WEB', 'url': 'https://gitlab.com/myrrlyn/endian_trait/-/issues/1'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0039.html'}]
|
{'cwe_ids': ['CWE-415'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:21:10Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-w5cr-frph-hw7f
|
2021-05-25T20:52:53Z
|
2021-08-25T21:01:50Z
| null |
['CVE-2021-31919']
|
Use of uninitialized buffer in rkyv
|
An issue was discovered in the rkyv crate before 0.6.0 for Rust. When an archive is created via serialization, the archive content may contain uninitialized values of certain parts of a struct.
|
[{'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': 'rkyv'}, 'ecosystem_specific': {'affected_functions': ['rkyv::Archive::resolve']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.6.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-31919'}, {'type': 'WEB', 'url': 'https://github.com/djkoloski/rkyv/issues/113'}, {'type': 'WEB', 'url': 'https://github.com/djkoloski/rkyv/commit/9c65ae9c2c67dd949b5c3aba9b8eba6da802ab7e'}, {'type': 'WEB', 'url': 'https://github.com/djkoloski/rkyv/commit/f141b560523a20557db6540576d153010bd18712'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0054.html'}]
|
{'cwe_ids': ['CWE-772', 'CWE-908'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-05-25T20:52:53Z', 'nvd_published_at': '2021-04-30T03:15:00Z'}
|
1.4.0
|
GHSA-g5w6-mrj7-75h2
|
2022-02-08T20:58:58Z
|
2021-08-25T14:48:31Z
| null |
['CVE-2021-39141']
|
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-39141](https://x-stream.github.io/CVE-2021-39141.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-g5w6-mrj7-75h2'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39141'}, {'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-39141.html'}]
|
{'cwe_ids': ['CWE-502'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T18:22:04Z', 'nvd_published_at': '2021-08-23T18:15:00Z'}
|
1.4.0
|
GHSA-qcc4-3rxf-gf4m
|
2021-09-03T20:35:31Z
|
2021-08-30T16:16:38Z
| null |
['CVE-2021-33605']
|
Unauthorized property update in CheckboxGroup component in Vaadin 12-14 and 15-20
|
Improper check in `CheckboxGroup` in `com.vaadin:vaadin-checkbox-flow` versions 1.2.0 prior to 2.0.0 (Vaadin 12.0.0 prior to 14.0.0), 2.0.0 prior to 3.0.0 (Vaadin 14.0.0 prior to 14.5.0), 3.0.0 through 4.0.1 (Vaadin 15.0.0 through 17.0.11), 14.5.0 through 14.6.7 (Vaadin 14.5.0 through 14.6.7), and 18.0.0 through 20.0.5 (Vaadin 18.0.0 through 20.0.5) allows attackers to modify the value of a disabled `Checkbox` inside enabled `CheckboxGroup` component via unspecified vectors.
- https://vaadin.com/security/cve-2021-33605
|
[{'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': 'Maven', 'name': 'com.vaadin:vaadin-checkbox-flow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '12.0.0'}, {'fixed': '14.6.8'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'com.vaadin:vaadin-checkbox-flow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '15.0.0'}, {'fixed': '20.0.6'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/vaadin/flow-components/security/advisories/GHSA-qcc4-3rxf-gf4m'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-33605'}, {'type': 'WEB', 'url': 'https://github.com/vaadin/flow-components/pull/1903'}, {'type': 'WEB', 'url': 'https://github.com/vaadin/flow-components/commit/1aa6bc94c763023bc3fc5849c2a1e8cab3bf6766'}, {'type': 'WEB', 'url': 'https://github.com/vaadin/flow-components/commit/f136532a735f703f1144f19fee48c9009c659f03'}, {'type': 'PACKAGE', 'url': 'https://github.com/vaadin/flow-components'}, {'type': 'WEB', 'url': 'https://vaadin.com/security/cve-2021-33605'}]
|
{'cwe_ids': ['CWE-754'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-25T16:15:42Z', 'nvd_published_at': '2021-08-25T13:15:00Z'}
|
1.4.0
|
GHSA-7v2r-wxmg-mgvc
|
2023-06-13T21:49:09Z
|
2021-08-25T20:48:56Z
| null |
['CVE-2020-35884']
|
HTTP Request smuggling in tiny_http
|
HTTP pipelining issues and request smuggling attacks are possible due to incorrect Transfer encoding header parsing. It is possible conduct HTTP request smuggling attacks (CL:TE/TE:TE) by sending invalid Transfer Encoding headers. By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack, or obtain sensitive information from requests other than their own.
|
[{'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': 'crates.io', 'name': 'tiny_http'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.8.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35884'}, {'type': 'WEB', 'url': 'https://github.com/tiny-http/tiny-http/issues/173'}, {'type': 'WEB', 'url': 'https://github.com/tiny-http/tiny-http/pull/190'}, {'type': 'WEB', 'url': 'https://github.com/tiny-http/tiny-http/commit/623b87397a569729c4bcabae747823c5668cce94'}, {'type': 'PACKAGE', 'url': 'https://github.com/tiny-http/tiny-http'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/M3JDNRE5RXJOWZZZF5QSCG4GUCSLTHF2/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VO6SRTCEPEYO2OX647I3H5XUWLFDRDWL/'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0031.html'}]
|
{'cwe_ids': ['CWE-444'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T20:56:20Z', 'nvd_published_at': '2020-12-31T10:15:00Z'}
|
1.4.0
|
GHSA-wr55-mf5c-hhwm
|
2023-06-13T18:16:02Z
|
2021-08-25T20:50:44Z
| null |
['CVE-2020-36209']
|
Data races in late-static
|
Affected versions of this crate implemented Sync for LateStatic with T: Send, so that it is possible to create a data race to a type T: Send + !Sync (e.g. Cell<T>).
This can result in a memory corruption or other kinds of undefined behavior.
The flaw was corrected in commit 11f396c by replacing the T: Send bound to T: Sync bound in the Sync impl for LateStatic<T>.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'late-static'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36209'}, {'type': 'WEB', 'url': 'https://github.com/Richard-W/late-static/issues/1'}, {'type': 'WEB', 'url': 'https://github.com/Richard-W/late-static/commit/11f396c'}, {'type': 'PACKAGE', 'url': 'https://github.com/Richard-W/late-static'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0102.html'}]
|
{'cwe_ids': ['CWE-662'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:52:13Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-vqx7-pw4r-29rr
|
2021-08-19T21:18:29Z
|
2021-08-25T20:47:13Z
| null |
['CVE-2020-35861']
|
Out of bounds read in bumpalo
|
An issue was discovered in the bumpalo crate before 3.2.1 for Rust. The realloc feature allows the reading of unknown memory. Attackers can potentially read cryptographic keys.
|
[{'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': 'bumpalo'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.0.0'}, {'fixed': '3.2.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35861'}, {'type': 'WEB', 'url': 'https://github.com/fitzgen/bumpalo/issues/69'}, {'type': 'PACKAGE', 'url': 'https://github.com/fitzgen/bumpalo'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0006.html'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:18:29Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-q89x-f52w-6hj2
|
2023-06-13T17:39:45Z
|
2021-08-25T20:43:04Z
| null |
['CVE-2017-18587']
|
Headers containing newline characters can split messages in hyper
|
Serializing of headers to the socket did not filter the values for newline bytes (\r or \n), which allowed for header values to split a request or response. People would not likely include newlines in the headers in their own applications, so the way for most people to exploit this is if an application constructs headers based on unsanitized user input.
This issue was fixed by replacing all newline characters with a space during serialization of a header value.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'hyper'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.10.0'}, {'fixed': '0.10.2'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'hyper'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.9.18'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2017-18587'}, {'type': 'PACKAGE', 'url': 'https://github.com/hyperium/hyper'}, {'type': 'WEB', 'url': 'https://github.com/hyperium/hyper/wiki/Security-001'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2017-0002.html'}]
|
{'cwe_ids': ['CWE-93'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:25:19Z', 'nvd_published_at': '2019-08-26T13:15:00Z'}
|
1.4.0
|
GHSA-mm7v-vpv8-xfc3
|
2023-06-13T20:57:37Z
|
2021-08-25T20:44:59Z
| null |
['CVE-2019-15551']
|
Double free in smallvec
|
Attempting to call grow on a spilled SmallVec with a value equal to the current capacity causes it to free the existing data. This performs a double free immediately and may lead to use-after-free on subsequent accesses to the SmallVec contents. An attacker that controls the value passed to grow may exploit this flaw to obtain memory contents or gain remote code execution.
|
[{'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'}, 'ecosystem_specific': {'affected_functions': ['smallvec::SmallVec::grow']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.6.5'}, {'fixed': '0.6.10'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-15551'}, {'type': 'WEB', 'url': 'https://github.com/servo/rust-smallvec/issues/148'}, {'type': 'WEB', 'url': 'https://github.com/servo/rust-smallvec/issues/149'}, {'type': 'WEB', 'url': 'https://github.com/servo/rust-smallvec/commit/c20cfa8584e649f00dc0767ab6fad63a3f59a296'}, {'type': 'WEB', 'url': 'https://github.com/servo/rust-smallvec/commit/f96322b9243405cc82701cc73f1b19313b413ab4'}, {'type': 'PACKAGE', 'url': 'https://github.com/servo/rust-smallvec'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0009.html'}]
|
{'cwe_ids': ['CWE-415'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:22:23Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-qq89-hq3f-393p
|
2021-08-31T16:02:04Z
|
2021-08-31T16:05:17Z
| null |
['CVE-2021-37712']
|
Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links
|
### Impact
Arbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution
node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created.
This logic was insufficient when extracting tar files that contained two directories and a symlink with names containing unicode values that normalized to the same value. Additionally, on Windows systems, long path portions would resolve to the same file system entities as their 8.3 "short path" counterparts. A specially crafted tar archive could thus include directories with two forms of the path that resolve to the same file system entity, followed by a symbolic link with a name in the first form, lastly followed by a file using the second form. It led to bypassing node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite.
The v3 branch of `node-tar` has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of `node-tar`. If this is not possible, a workaround is available below.
### Patches
6.1.9 || 5.0.10 || 4.4.18
### Workarounds
Users may work around this vulnerability without upgrading by creating a custom filter method which prevents the extraction of symbolic links.
```js
const tar = require('tar')
tar.x({
file: 'archive.tgz',
filter: (file, entry) => {
if (entry.type === 'SymbolicLink') {
return false
} else {
return true
}
}
})
```
Users are encouraged to upgrade to the latest patched versions, rather than attempt to sanitize tar input themselves.
#### Fix
The problem is addressed in the following ways, when comparing paths in the directory cache and path reservation systems:
1. The `String.normalize('NFKD')` method is used to first normalize all unicode to its maximally compatible and multi-code-point form.
2. All slashes are normalized to `/` on Windows systems (on posix systems, `\` is a valid filename character, and thus left intact).
3. When a symbolic link is encountered on Windows systems, the entire directory cache is cleared. Collisions related to use of 8.3 short names to replace directories with other (non-symlink) types of entries may make archives fail to extract properly, but will not result in arbitrary file writes.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'tar'}, 'ecosystem_specific': {'affected_functions': ['tar.Unpack']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.4.18'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'tar'}, 'ecosystem_specific': {'affected_functions': ['tar.Unpack']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '5.0.0'}, {'fixed': '5.0.10'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'tar'}, 'ecosystem_specific': {'affected_functions': ['tar.Unpack']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '6.0.0'}, {'fixed': '6.1.9'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/npm/node-tar/security/advisories/GHSA-qq89-hq3f-393p'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37712'}, {'type': 'WEB', 'url': 'https://github.com/isaacs/node-tar/commit/1739408d3122af897caefd09662bce2ea477533b'}, {'type': 'WEB', 'url': 'https://github.com/isaacs/node-tar/commit/b6162c7fafe797f856564ef37f4b82747f051455'}, {'type': 'WEB', 'url': 'https://github.com/isaacs/node-tar/commit/bb93ba243746f705092905da1955ac3b0509ba1e'}, {'type': 'WEB', 'url': 'https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf'}, {'type': 'PACKAGE', 'url': 'https://github.com/npm/node-tar'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2022/12/msg00023.html'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2021/dsa-5008'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/package/tar'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2021.html'}]
|
{'cwe_ids': ['CWE-22', 'CWE-59'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-31T16:02:04Z', 'nvd_published_at': '2021-08-31T17:15:00Z'}
|
1.4.0
|
GHSA-fqq2-xp7m-xvm8
|
2021-08-24T17:45:32Z
|
2021-08-25T20:58:19Z
| null |
['CVE-2020-36435']
|
Data race in ruspiro-singleton
|
`Singleton<T>` is meant to be a static object that can be initialized lazily. In
order to satisfy the requirement that `static` items must implement `Sync`,
`Singleton` implemented both `Sync` and `Send` unconditionally.
This allows for a bug where non-`Sync` types such as `Cell` can be used in
singletons and cause data races in concurrent programs.
The flaw was corrected in commit `b0d2bd20e` by adding trait bounds, requiring
the contaiend type to implement `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': 'ruspiro-singleton'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36435'}, {'type': 'WEB', 'url': 'https://github.com/RusPiRo/ruspiro-singleton/issues/10'}, {'type': 'WEB', 'url': 'https://github.com/RusPiRo/ruspiro-singleton/pull/11'}, {'type': 'WEB', 'url': 'https://github.com/RusPiRo/ruspiro-singleton/commit/b0d2bd20eb40b9cbc2958b981ba2dcd9e6f9396e'}, {'type': 'PACKAGE', 'url': 'https://github.com/RusPiRo/ruspiro-singleton'}, {'type': 'WEB', 'url': 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/ruspiro-singleton/RUSTSEC-2020-0115.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0115.html'}]
|
{'cwe_ids': ['CWE-119', 'CWE-362'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T20:14:26Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-gvvv-w559-2hg6
|
2021-08-24T17:59:17Z
|
2021-08-25T20:57:17Z
| null |
['CVE-2020-36453']
|
Data races in scottqueue
|
An issue was discovered in the scottqueue crate through 2020-11-15 for Rust. There are unconditional implementations of Send and Sync for Queue<T>. This allows (1) creating data races to a `T: !Sync` and (2) sending `T: !Send` to other threads, resulting in memory corruption or other undefined behavior.
|
[{'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': 'scottqueue'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.1.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36453'}, {'type': 'WEB', 'url': 'https://github.com/rossdylan/rust-scottqueue/issues/1'}, {'type': 'PACKAGE', 'url': 'https://github.com/rossdylan/rust-scottqueue'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0133.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T20:26:07Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-4wj3-p7hj-cvx8
|
2023-06-13T20:13:30Z
|
2021-08-25T20:48:47Z
| null |
['CVE-2020-35891']
|
Double free in ordnung
|
An issue was discovered in the ordnung crate through version 0.0.1 for Rust. compact::Vec violates memory safety via a remove() double free.
|
[{'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': 'ordnung'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.0.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35891'}, {'type': 'WEB', 'url': 'https://github.com/maciejhirsz/ordnung/issues/8'}, {'type': 'PACKAGE', 'url': 'https://github.com/maciejhirsz/ordnung'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0038.html'}]
|
{'cwe_ids': ['CWE-415'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:06:30Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-rpxm-vmr7-5f5f
|
2021-08-24T18:24:04Z
|
2021-08-25T20:59:15Z
| null |
['CVE-2020-36445']
|
Data races in convec
|
Affected versions of this crate unconditionally implement Send/Sync for `ConVec<T>`.
This allows users to insert `T` that is not Send or not Sync.
This allows users to create data races by using non-Send types like `Arc<Cell<_>>` or `Rc<_>` as `T` in `ConVec<T>`. It is also possible to create data races by using types like `Cell<_>` or `RefCell<_>` as `T` (types that are `Send` but not `Sync`).
Such data races can lead to memory corruption.
|
[{'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': 'convec'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '2.0.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36445'}, {'type': 'PACKAGE', 'url': 'https://github.com/krl/convec'}, {'type': 'WEB', 'url': 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/convec/RUSTSEC-2020-0125.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0125.html'}]
|
{'cwe_ids': ['CWE-119', 'CWE-362'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-09T21:35:28Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-vp6r-mrq9-8f4h
|
2023-06-13T21:50:03Z
|
2021-08-25T20:58:11Z
| null |
['CVE-2020-36462']
|
Data race in 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': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36462'}, {'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://raw.githubusercontent.com/rustsec/advisory-db/main/crates/syncpool/RUSTSEC-2020-0142.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0142.html'}]
|
{'cwe_ids': ['CWE-362', 'CWE-77'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T20:18:30Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-6226-h7ff-ch6c
|
2022-02-08T21:01:57Z
|
2021-08-23T19:40:48Z
| null |
['CVE-2021-32808']
|
Widget feature vulnerability allowing to execute JavaScript code using undo functionality
|
### Affected packages
The vulnerability has been discovered in [Widget](https://ckeditor.com/cke4/addon/clipboard) plugin if used alongside [Undo](https://ckeditor.com/cke4/addon/undo) feature.
### Impact
A potential vulnerability has been discovered in CKEditor 4 [Widget](https://ckeditor.com/cke4/addon/widget) package. The vulnerability allowed to abuse undo functionality using malformed widget HTML, which could result in executing JavaScript code. It affects all users using the CKEditor 4 plugins listed above at version >= 4.13.0.
### Patches
The problem has been recognized and patched. The fix will be available in version 4.16.2.
### For more information
Email us at security@cksource.com if you have any questions or comments about this advisory.
### Acknowledgements
The CKEditor 4 team would like to thank Anton Subbotin ([skavans](https://github.com/skavans)) for recognizing and reporting this vulnerability.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'ckeditor4'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.13.0'}, {'fixed': '4.16.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/ckeditor/ckeditor4/security/advisories/GHSA-6226-h7ff-ch6c'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-32808'}, {'type': 'PACKAGE', 'url': 'https://github.com/ckeditor/ckeditor4'}, {'type': 'WEB', 'url': 'https://github.com/ckeditor/ckeditor4/releases/tag/4.16.2'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NYA354LJP47KCVJMTUO77ZCX3ZK42G3T/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UVOYN2WKDPLKCNILIGEZM236ABQASLGW/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WAGNWHFIQAVCP537KFFS2A2GDG66J7XD/'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujan2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2021.html'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T16:49:07Z', 'nvd_published_at': '2021-08-12T17:15:00Z'}
|
1.4.0
|
GHSA-hf6p-4rv2-9qrp
|
2021-08-26T15:45:24Z
|
2021-08-30T16:25:42Z
| null |
['CVE-2021-23423']
|
Path Traversal in bikshed
|
This affects the package bikeshed before 3.0.0. This can occur when an untrusted source file containing include, include-code or include-raw block is processed. The contents of arbitrary files could be disclosed in the HTML output.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'bikeshed'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.0.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-23423'}, {'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-1537647'}]
|
{'cwe_ids': ['CWE-22'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-26T15:45:24Z', 'nvd_published_at': '2021-08-16T08:15:00Z'}
|
1.4.0
|
GHSA-4hjg-cx88-g9f9
|
2023-06-13T18:10:45Z
|
2021-08-25T20:49:58Z
| null |
['CVE-2020-35915']
|
Data races in futures-intrusive
|
GenericMutexGuard<T> was given the Sync auto trait as long as T is Send due to its contained members. However, since the guard is supposed to represent an acquired lock and allows concurrent access to the underlying data from different threads, it should only be Sync when the underlying data is.
This is a soundness issue and allows data races, potentially leading to crashes and segfaults from safe Rust code.
The flaw was corrected by adding a T: Send + Sync bound for GenericMutexGuard's Sync trait.
|
[{'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': 'futures-intrusive'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35915'}, {'type': 'WEB', 'url': 'https://github.com/Matthias247/futures-intrusive/issues/53'}, {'type': 'PACKAGE', 'url': 'https://github.com/Matthias247/futures-intrusive'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0072.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T20:49:04Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-6xx3-rg99-gc3p
|
2021-05-21T17:50:36Z
|
2021-08-13T15:22:31Z
| null |
['CVE-2020-15522']
|
Timing based private key exposure in Bouncy Castle
|
Bouncy Castle BC Java before 1.66, BC C# .NET before 1.8.7, BC-FJA before 1.0.2.1, BC before 1.66, BC-FNA before 1.0.1.1 have a timing issue within the EC math library that can expose information about the private key when an attacker is able to observe timing information for the generation of multiple deterministic ECDSA signatures.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.bouncycastle:bc-fips'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.0.2.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 1.0.2'}}, {'package': {'ecosystem': 'Maven', 'name': 'org.bouncycastle:bcprov-ext-jdk15on'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.66'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.bouncycastle:bcprov-ext-jdk16'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.66'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.bouncycastle:bcprov-jdk14'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.66'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.bouncycastle:bcprov-jdk15'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.66'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.bouncycastle:bcprov-jdk15on'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.66'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.bouncycastle:bcprov-jdk15to18'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.66'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.bouncycastle:bcprov-jdk16'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.66'}]}]}, {'package': {'ecosystem': 'NuGet', 'name': 'BouncyCastle'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.8.7'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-15522'}, {'type': 'WEB', 'url': 'https://github.com/bcgit/bc-csharp/wiki/CVE-2020-15522'}, {'type': 'WEB', 'url': 'https://github.com/bcgit/bc-java/wiki/CVE-2020-15522'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20210622-0007/'}, {'type': 'WEB', 'url': 'https://www.bouncycastle.org/releasenotes.html'}]
|
{'cwe_ids': ['CWE-203', 'CWE-362'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-05-21T17:50:36Z', 'nvd_published_at': '2021-05-20T12:15:00Z'}
|
1.4.0
|
GHSA-jrcf-4jp8-m28v
|
2023-06-13T18:42:34Z
|
2021-08-25T20:50:35Z
| null |
['CVE-2020-35921']
|
miow invalidly assumes the memory layout of std::net::SocketAddr
|
The miow 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:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'miow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.3.0'}, {'fixed': '0.3.6'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35921'}, {'type': 'WEB', 'url': 'https://github.com/yoshuawuyts/miow/issues/38'}, {'type': 'WEB', 'url': 'https://github.com/yoshuawuyts/miow/pull/39'}, {'type': 'WEB', 'url': 'https://github.com/yoshuawuyts/miow/pull/40'}, {'type': 'PACKAGE', 'url': 'https://github.com/yoshuawuyts/miow'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0080.html'}]
|
{'cwe_ids': ['CWE-188'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:54:07Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-mvvp-gwgc-5hrp
|
2021-08-31T21:21:23Z
|
2021-08-02T17:30:27Z
| null |
['CVE-2021-23407']
|
Path Traversal in elFinder.Net.Core
|
This affects the package elFinder.Net.Core from 0 and before 1.2.4. The user-controlled file name is not properly sanitized before it is used to create a file system path.
|
[{'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': 'NuGet', 'name': 'elFinder.Net.Core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.2.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-23407'}, {'type': 'WEB', 'url': 'https://github.com/trannamtrung1st/elFinder.Net.Core/commit/5498c8a86b76ef089cfbd7ef8be014b61fa11c73'}, {'type': 'PACKAGE', 'url': 'https://github.com/trannamtrung1st/elFinder.Net.Core'}, {'type': 'WEB', 'url': 'https://github.com/trannamtrung1st/elFinder.Net.Core/releases/tag/all-1.2.4'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-DOTNET-ELFINDERNETCORE-1315152'}]
|
{'cwe_ids': ['CWE-22'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-07-15T18:45:24Z', 'nvd_published_at': '2021-07-14T17:15:00Z'}
|
1.4.0
|
GHSA-c9qf-r67m-p7cg
|
2021-08-23T17:58:44Z
|
2021-08-25T14:44:12Z
| null |
['CVE-2021-37637']
|
Null pointer dereference in `CompressElement`
|
### Impact
It is possible to trigger a null pointer dereference in TensorFlow by passing an invalid input to `tf.raw_ops.CompressElement`:
```python
import tensorflow as tf
tf.raw_ops.CompressElement(components=[[]])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/data/compression_utils.cc#L34) was accessing the size of a buffer obtained from the return of a separate function call before validating that said buffer is valid.
### Patches
We have patched the issue in GitHub commit [5dc7f6981fdaf74c8c5be41f393df705841fb7c5](https://github.com/tensorflow/tensorflow/commit/5dc7f6981fdaf74c8c5be41f393df705841fb7c5).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. Concurrently, it was resolved in `master` branch as it was also discovered internally and fixed before the report was handled.
|
[{'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-c9qf-r67m-p7cg'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37637'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/5dc7f6981fdaf74c8c5be41f393df705841fb7c5'}]
|
{'cwe_ids': ['CWE-476'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T17:58:44Z', 'nvd_published_at': '2021-08-12T19:15:00Z'}
|
1.4.0
|
GHSA-7qcc-g2m9-8533
|
2021-08-19T17:22:29Z
|
2021-08-25T20:53:53Z
| null |
['CVE-2021-28307']
|
Null pointer deference in fltk
|
An issue was discovered in the fltk crate before 0.15.3 for Rust. There is a NULL pointer dereference during attempted use of a non-raster image for a window icon.
|
[{'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': 'fltk'}, 'ecosystem_specific': {'affected_functions': ['fltk::prelude::WindowExt::set_icon']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.15.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-28307'}, {'type': 'WEB', 'url': 'https://github.com/MoAlyousef/fltk-rs/issues/519'}, {'type': 'PACKAGE', 'url': 'https://github.com/MoAlyousef/fltk-rs'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0038.html'}]
|
{'cwe_ids': ['CWE-476'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:22:29Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-g489-xrw3-3v8w
|
2021-08-19T18:51:25Z
|
2021-08-25T20:50:46Z
| null |
['CVE-2020-36207']
|
Data races in aovec
|
An issue was discovered in the aovec crate through 2020-12-10 for Rust. Because Aovec<T> does not have bounds on its Send trait or Sync trait, a data race and memory corruption can occur.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'aovec'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.1.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36207'}, {'type': 'PACKAGE', 'url': 'https://github.com/krl/aovec'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0099.html'}]
|
{'cwe_ids': ['CWE-662', 'CWE-787'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:51:25Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-pwhf-7427-9vv2
|
2023-06-13T16:46:48Z
|
2021-08-25T20:56:57Z
| null |
['CVE-2020-36468']
|
Non-atomic writes in cgc
|
# Multiple soundness issues in `Ptr` in cgc
Affected versions of this crate have the following issues:
1. `Ptr` implements `Send` and `Sync` for all types, this can lead to data
races by sending non-thread safe types across threads.
2. `Ptr::get` violates mutable alias rules by returning multiple mutable
references to the same object.
3. `Ptr::write` uses non-atomic writes to the underlying pointer. This means
that when used across threads it can lead to data races.
|
[{'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': 'cgc'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.4.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36468'}, {'type': 'WEB', 'url': 'https://github.com/playXE/cgc/issues/5'}, {'type': 'PACKAGE', 'url': 'https://github.com/playXE/cgc'}, {'type': 'WEB', 'url': 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/cgc/RUSTSEC-2020-0148.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0148.html'}]
|
{'cwe_ids': ['CWE-657'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T20:39:03Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-ppqp-78xx-3r38
|
2022-04-26T18:11:53Z
|
2021-08-25T20:53:25Z
| null |
['CVE-2021-26951']
|
Out of bounds write in calamine
|
An issue was discovered in the calamine crate before 0.17.0 for Rust. It allows attackers to overwrite heap-memory locations because Vec::set_len is used without proper memory claiming, and this uninitialized memory is used for a user-provided Read operation, as demonstrated by Sectors::get.
|
[{'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': 'calamine'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.17.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-26951'}, {'type': 'WEB', 'url': 'https://github.com/tafia/calamine/issues/199'}, {'type': 'PACKAGE', 'url': 'https://github.com/tafia/calamine'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0015.html'}]
|
{'cwe_ids': ['CWE-787'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:35:56Z', 'nvd_published_at': '2021-02-09T23:15:00Z'}
|
1.4.0
|
GHSA-g8wg-cjwc-xhhp
|
2021-08-24T16:17:59Z
|
2021-08-25T14:41:00Z
| null |
['CVE-2021-37679']
|
Heap OOB in nested `tf.map_fn` with `RaggedTensor`s
|
### Impact
It is possible to nest a `tf.map_fn` within another `tf.map_fn` call. However, if the input tensor is a `RaggedTensor` and there is no function signature provided, code assumes the output is a fully specified tensor and fills output buffer with uninitialized contents from the heap:
```python
import tensorflow as tf
x = tf.ragged.constant([[1,2,3], [4,5], [6]])
t = tf.map_fn(lambda r: tf.map_fn(lambda y: r, r), x)
z = tf.ragged.constant([[[1,2,3],[1,2,3],[1,2,3]],[[4,5],[4,5]],[[6]]])
```
The `t` and `z` outputs should be identical, however this is not the case. The last row of `t` contains data from the heap which can be used to leak other memory information.
The bug lies in the conversion from a `Variant` tensor to a `RaggedTensor`. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_from_variant_op.cc#L177-L190) does not check that all inner shapes match and this results in the additional dimensions in the above example.
The same implementation can result in data loss, if input tensor is tweaked:
```python
import tensorflow as tf
x = tf.ragged.constant([[1,2], [3,4,5], [6]])
t = tf.map_fn(lambda r: tf.map_fn(lambda y: r, r), x)
```
Here, the output tensor will only have 2 elements for each inner dimension.
### Patches
We have patched the issue in GitHub commit [4e2565483d0ffcadc719bd44893fb7f609bb5f12](https://github.com/tensorflow/tensorflow/commit/4e2565483d0ffcadc719bd44893fb7f609bb5f12).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Haris Sahovic.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'}]
|
[{'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-g8wg-cjwc-xhhp'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37679'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/4e2565483d0ffcadc719bd44893fb7f609bb5f12'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-125', 'CWE-681'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T16:17:59Z', 'nvd_published_at': '2021-08-12T23:15:00Z'}
|
1.4.0
|
GHSA-7fvx-3jfc-2cpc
|
2021-08-24T12:55:28Z
|
2021-08-25T14:42:58Z
| null |
['CVE-2021-37655']
|
Heap OOB in `ResourceScatterUpdate`
|
### Impact
An attacker can trigger a read from outside of bounds of heap allocated data by sending invalid arguments to `tf.raw_ops.ResourceScatterUpdate`:
```python
import tensorflow as tf
v = tf.Variable([b'vvv'])
tf.raw_ops.ResourceScatterUpdate(
resource=v.handle,
indices=[0],
updates=['1', '2', '3', '4', '5'])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L919-L923) has an incomplete validation of the relationship between the shapes of `indices` and `updates`: instead of checking that the shape of `indices` is a prefix of the shape of `updates` (so that broadcasting can happen), code only checks that the number of elements in these two tensors are in a divisibility relationship.
### Patches
We have patched the issue in GitHub commit [01cff3f986259d661103412a20745928c727326f](https://github.com/tensorflow/tensorflow/commit/01cff3f986259d661103412a20745928c727326f).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A: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-7fvx-3jfc-2cpc'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37655'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/01cff3f986259d661103412a20745928c727326f'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T12:55:28Z', 'nvd_published_at': '2021-08-12T21:15:00Z'}
|
1.4.0
|
GHSA-gx5w-rrhp-f436
|
2021-08-18T21:06:53Z
|
2021-08-25T20:56:20Z
| null |
['CVE-2020-26297']
|
XSS in mdBook
|
> This is a cross-post of [the official security advisory][ml]. The official post contains a signed version with our PGP key, as well.
[ml]: https://groups.google.com/g/rustlang-security-announcements/c/3-sO6of29O0
The Rust Security Response Working Group was recently notified of a security issue affecting the search feature of mdBook, which could allow an attacker to execute arbitrary JavaScript code on the page.
The CVE for this vulnerability is [CVE-2020-26297](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26297).
## Overview
The search feature of mdBook (introduced in version 0.1.4) was affected by a cross site scripting vulnerability that allowed an attacker to execute arbitrary JavaScript code on an user's browser by tricking the user into typing a malicious search query, or tricking the user into clicking a link to the search page with the malicious search query prefilled.
mdBook 0.4.5 fixes the vulnerability by properly escaping the search query.
## Mitigations
Owners of websites built with mdBook have to upgrade to mdBook 0.4.5 or greater and rebuild their website contents with it. It's possible to install mdBook 0.4.5 on the local system with:
```
cargo install mdbook --version 0.4.5 --force
```
## Acknowledgements
Thanks to Kamil Vavra for responsibly disclosing the vulnerability to us according to [our security policy](https://www.rust-lang.org/policies/security).
## Timeline of events
All times are listed in UTC.
- 2020-12-30 20:14 - The issue is reported to the Rust Security Response WG
- 2020-12-30 20:32 - The issue is acknowledged and the investigation began
- 2020-12-30 21:21 - Found the cause of the vulnerability and prepared the patch
- 2021-01-04 15:00 - Patched version released and vulnerability disclosed
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'mdBook'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.1.4'}, {'fixed': '0.4.5'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/rust-lang/mdBook/security/advisories/GHSA-gx5w-rrhp-f436'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-26297'}, {'type': 'WEB', 'url': 'https://github.com/rust-lang/mdBook/commit/32abeef088e98327ca0dfccdad92e84afa9d2e9b'}, {'type': 'PACKAGE', 'url': 'https://github.com/rust-lang/mdBook'}, {'type': 'WEB', 'url': 'https://github.com/rust-lang/mdBook/blob/master/CHANGELOG.md#mdbook-045'}, {'type': 'WEB', 'url': 'https://groups.google.com/g/rustlang-security-announcements/c/3-sO6of29O0'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0001.html'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T21:06:53Z', 'nvd_published_at': '2021-01-04T19:15:00Z'}
|
1.4.0
|
GHSA-7hfm-57qf-j43q
|
2022-02-08T21:08:33Z
|
2021-08-02T16:55:07Z
| null |
['CVE-2021-35515']
|
Excessive Iteration in Compress
|
When reading a specially crafted 7Z archive, the construction of the list of codecs that decompress an entry can result in an infinite loop. This could be used to mount a denial of service attack against services that use Compress' sevenz package.
|
[{'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.commons:commons-compress'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.21'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-35515'}, {'type': 'WEB', 'url': 'https://commons.apache.org/proper/commons-compress/security-reports.html'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r19ebfd71770ec0617a9ea180e321ef927b3fefb4c81ec5d1902d20ab%40%3Cuser.commons.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r67ef3c07fe3b8c1b02d48012149d280ad6da8e4cec253b527520fb2b@%3Cdev.poi.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r9f54c0caa462267e0cc68b49f141e91432b36b23348d18c65bd0d040@%3Cnotifications.skywalking.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rab292091eadd1ecc63c516e9541a7f241091cf2e652b8185a6059945@%3Ccommits.druid.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/racd0c0381c8404f298b226cd9db2eaae965b14c9c568224aa3f437ae@%3Cnotifications.skywalking.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rb064d705fdfa44b5dae4c366b369ef6597951083196321773b983e71@%3Ccommits.pulsar.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rb6e1fa80d34e5ada45f72655d84bfd90db0ca44ef19236a49198c88c@%3Cnotifications.skywalking.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rb7adf3e55359819e77230b4586521e5c6874ce5ed93384bdc14d6aee@%3Cnotifications.skywalking.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rba65ed5ddb0586f5b12598f55ec7db3633e7b7fede60466367fbf86a@%3Cnotifications.skywalking.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rbaea15ddc5a7c0c6b66660f1d6403b28595e2561bb283eade7d7cd69@%3Cannounce.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rbe91c512c5385181149ab087b6c909825d34299f5c491c6482a2ed57@%3Ccommits.druid.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rd4332baaf6debd03d60deb7ec93bee49e5fdbe958cb6800dff7fb00e@%3Cnotifications.skywalking.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rf2f4d7940371a7c7c5b679f50e28fc7fcc82cd00670ced87e013ac88@%3Ccommits.druid.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rfba19167efc785ad3561e7ef29f340d65ac8f0d897aed00e0731e742@%3Cnotifications.skywalking.apache.org%3E'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20211022-0001/'}, {'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://www.oracle.com/security-alerts/cpuoct2021.html'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/07/13/1'}]
|
{'cwe_ids': ['CWE-834', 'CWE-835'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-07-14T17:35:41Z', 'nvd_published_at': '2021-07-13T08:15:00Z'}
|
1.4.0
|
GHSA-g4rw-8m5q-6453
|
2023-06-13T20:26:14Z
|
2021-08-25T20:45:12Z
| null |
['CVE-2020-25016']
|
Out of bounds access in rgb
|
Affected versions of rgb crate allow viewing and modifying data of any type T wrapped in RGB<T> as bytes, and do not correctly constrain RGB<T> and other wrapper structures to the types for which it is safe to do so.
Safety violation possible for a type wrapped in RGB<T> and similar wrapper structures:
* If T contains padding, viewing it as bytes may lead to exposure of contents of uninitialized memory.
* If T contains a pointer, modifying it as bytes may lead to dereferencing of arbitrary pointers.
* Any safety and/or validity invariants for T may be violated.
The issue was resolved by requiring all types wrapped in structures provided by RGB crate to implement an unsafe marker trait.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'rgb'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.5.4'}, {'fixed': '0.8.20'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-25016'}, {'type': 'WEB', 'url': 'https://github.com/kornelski/rust-rgb/issues/35'}, {'type': 'PACKAGE', 'url': 'https://github.com/kornelski/rust-rgb'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0029.html'}]
|
{'cwe_ids': ['CWE-119', 'CWE-843'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:21:37Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-v42f-j8fx-99f3
|
2021-08-24T17:58:36Z
|
2021-08-25T21:00:13Z
|
2021-08-24T17:58:36Z
|
[]
|
Queue<T> should have a Send bound on its Send/Sync traits
|
Affected versions of this crate unconditionally implements `Send`/`Sync` for `Queue<T>`.
This allows (1) creating data races to a `T: !Sync` and (2) sending `T: !Send` to other threads, resulting in memory corruption or other undefined behavior.
|
[]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'scottqueue'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.1.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/rossdylan/rust-scottqueue/issues/1'}, {'type': 'PACKAGE', 'url': 'https://github.com/rossdylan/rust-scottqueue'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0133.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-06T18:34:31Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-9mxw-4856-9cm5
|
2023-06-13T20:46:48Z
|
2021-08-25T20:50:51Z
| null |
['CVE-2020-36206']
|
Data races in rusb
|
Affected versions of rusb did not require UsbContext to implement Send and Sync. However, through Device and DeviceHandle it is possible to use UsbContexts across threads. This issue allows non-thread safe UsbContext types to be used concurrently leading to data races and memory corruption. The issue was fixed by adding Send and Sync bounds to UsbContext.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'rusb'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.7.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36206'}, {'type': 'WEB', 'url': 'https://github.com/a1ien/rusb/issues/44'}, {'type': 'PACKAGE', 'url': 'https://github.com/a1ien/rusb'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0098.html'}]
|
{'cwe_ids': ['CWE-662', 'CWE-787'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:51:05Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-w9vv-q986-vj7x
|
2021-08-19T17:09:13Z
|
2021-08-25T20:54:24Z
| null |
['CVE-2021-29934']
|
Out of bounds read in uu_od
|
An issue was discovered in PartialReader in the uu_od crate before 0.0.4 for Rust. Attackers can read the contents of uninitialized memory locations via a user-provided Read operation.
|
[{'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': 'uu_od'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.0.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-29934'}, {'type': 'WEB', 'url': 'https://github.com/uutils/coreutils/issues/1729'}, {'type': 'WEB', 'url': 'https://github.com/uutils/coreutils/pull/1730'}, {'type': 'WEB', 'url': 'https://github.com/uutils/coreutils/pull/1738'}, {'type': 'WEB', 'url': 'https://github.com/uutils/coreutils/pull/1739'}, {'type': 'WEB', 'url': 'https://github.com/uutils/coreutils/commit/39d62c6c1f809022c903180471c10fde6ecd12d1'}, {'type': 'WEB', 'url': 'https://github.com/uutils/coreutils/commit/5935876f38498b0c1f657d031171eb17028def6f'}, {'type': 'WEB', 'url': 'https://github.com/uutils/coreutils/commit/7341a1a033aa5980ac59bc9d4df978b396de4fad'}, {'type': 'PACKAGE', 'url': 'https://github.com/uutils/coreutils'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0043.html'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:09:13Z', 'nvd_published_at': '2021-04-01T05:15:00Z'}
|
1.4.0
|
GHSA-32v7-ghpr-c8hg
|
2023-06-13T18:30:35Z
|
2021-08-25T20:58:47Z
| null |
['CVE-2019-15547']
|
Mishandling of format strings in ncurses
|
ncurses exposes functions from the ncurses library which:
* Pass buffers without length to C functions that may write an arbitrary amount of data, leading to a buffer overflow. (instr, mvwinstr, etc)
* Passes rust &str to strings expecting C format arguments, allowing hostile input to execute a format string attack, which trivially allows writing arbitrary data to stack memory (functions in the printw family).
|
[{'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': 'ncurses'}, 'ecosystem_specific': {'affected_functions': ['ncurses::instr', 'ncurses::mvprintw', 'ncurses::mvwinstr', 'ncurses::mvwprintw', 'ncurses::printw']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '5.101.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-15547'}, {'type': 'WEB', 'url': 'https://github.com/RustSec/advisory-db/issues/106'}, {'type': 'WEB', 'url': 'https://github.com/jeaye/ncurses-rs/issues/172'}, {'type': 'PACKAGE', 'url': 'https://github.com/jeaye/ncurses-rs'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0006.html'}]
|
{'cwe_ids': ['CWE-134'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T17:45:13Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-9wgh-vjj7-7433
|
2023-06-13T18:17:31Z
|
2021-08-25T20:49:54Z
| null |
['CVE-2020-35916']
|
Mutable reference with immutable provenance in image
|
A mutable reference to a struct was constructed by dereferencing a pointer obtained from slice::as_ptr. Instead, slice::as_mut_ptr should have been called on the mutable slice argument. The former performs an implicit reborrow as an immutable shared reference which does not allow writing through the derived pointer.
|
[{'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': 'image'}, 'ecosystem_specific': {'affected_functions': ['image::Bgr::from_slice_mut', 'image::Bgra::from_slice_mut', 'image::Luma::from_slice_mut', 'image::LumaA::from_slice_mut', 'image::Rgb::from_slice_mut', 'image::Rgba::from_slice_mut']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.23.12'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35916'}, {'type': 'WEB', 'url': 'https://github.com/image-rs/image/issues/1357'}, {'type': 'WEB', 'url': 'https://github.com/image-rs/image/pull/1358'}, {'type': 'WEB', 'url': 'https://github.com/image-rs/image/commit/5cbe1e6767d11aff3f14c7ad69a06b04e8d583c7'}, {'type': 'PACKAGE', 'url': 'https://github.com/image-rs/image'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0073.html'}]
|
{'cwe_ids': ['CWE-400'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T20:49:50Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-q7cg-43mg-qp69
|
2022-08-11T14:54:06Z
|
2021-08-25T14:45:28Z
| null |
['CVE-2021-34532']
|
ASP.NET Core Information Disclosure Vulnerability
|
Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 5.0, .NET Core 3.1 and .NET Core 2.1. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
An information disclosure vulnerability exists in .NET 5.0, .NET Core 3.1 and .NET Core 2.1 where a JWT token is logged if it cannot be parsed.
### Patches
* If you're using .NET 5.0, you should download and install Runtime 5.0.9 or SDK 5.0.206 (for Visual Studio 2019 v16.8) or SDK 5.0.303 (for Visual Studio 2019 V16.10) from https://dotnet.microsoft.com/download/dotnet-core/5.0.
* If you're using .NET Core 3.1, you should download and install Runtime 3.1.18 or SDK 3.1.118 (for Visual Studio 2019 v16.4) or 3.1.412 (for Visual Studio 2019 v16.7 or later) from https://dotnet.microsoft.com/download/dotnet-core/3.1.
* If you're using .NET Core 2.1, you should download and install Runtime 2.1.29 or SDK 2.1.525 (for Visual Studio 2019 v15.9) or 2.1.817 from https://dotnet.microsoft.com/download/dotnet-core/2.1.
* If your application is using .NET Core 2.1 running on .NET Framework see the [Updating .NET Core 2.1 on .NET Framework](#updating-2.1) section below.
### <a name="updating-2.1"></a> Updating .NET Core 2.1 on .NET Framework
If you are running .NET Core 2.1 on .NET Framework you need to check your projects for dependencies and update them accordingly.
#### Direct dependencies
Direct dependencies are discoverable by examining your `csproj` file. They can be fixed by [editing the project file](#fixing-direct-dependencies) or using NuGet to update the dependency.
#### Transitive dependencies
Transitive dependencies occur when you add a package to your project that in turn relies on another package. For example, if Contoso publishes a package `Contoso.Utility` which, in turn, depends on `Contoso.Internals` and you add the `Contoso.Utility` package to your project now your project has a direct dependency on `Contoso.Utility` and, because `Contoso.Utility` depends 'Contoso.Internals', your application gains a transitive dependency on the `Contoso.Internals` package.
Transitive dependencies are reviewable in two ways:
* In the Visual Studio Solution Explorer window, which supports searching.
* By examining the `project.assets.json` file contained in the obj directory of your project for `csproj` based projects
The `project.assets.json` files are the authoritative list of all packages used by your project, containing both direct and transitive dependencies.
There are two ways to view transitive dependencies. You can either [use Visual Studio’s Solution Explorer](#vs-solution-explorer), or you can review [the `project.assets.json` file](#project-assets-json)).
##### <a name="vs-solution-explorer"></a>Using Visual Studio Solution Explorer
To use Solution Explorer, open the project in Visual Studio, and then press Ctrl+; to activate the search in Solution Explorer. Search for the [vulnerable package](#affected-software) and make a note of the version numbers of any results you find.
For example, search for `Microsoft.AspNetCore.Authentication.JwtBearer` and update the package to the latest version
##### <a name="project-assets-json"></a> Manually reviewing project.assets.json
Open the *project.assets.json* file from your project’s obj directory in your editor. We suggest you use an editor that understands JSON and allows you to collapse and expand nodes to review this file.
Visual Studio and Visual Studio Code provide JSON friendly editing.
Search the *project.assets.json* file for the [vulnerable package](#affected-software), using the format `packagename/` for each of the package names from the preceding table. If you find the assembly name in your search:
* Examine the line on which they are found, the version number is after the `/`.
* Compare to the [vulnerable versions table](#affected-software).
For example, a search result that shows `Microsoft.AspNetCore.Authentication.JwtBearer/2.1.0` is a reference to version 2.1.1 of `Microsoft.AspNetCore.Authentication.JwtBearer`.
If your *project.assets.json* file includes references to the [vulnerable package](#affected-software), then you need to fix the transitive dependencies.
If you have not found any reference to any vulnerable packages, this means either
* None of your direct dependencies depend on any vulnerable packages, or
* You have already fixed the problem by updating the direct dependencies.
#### Other Details
- Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/195
- An Issue for this can be found at https://github.com/dotnet/aspnetcore/issues/35246
- MSRC details for this can be found at https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2021-34532
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'NuGet', 'name': 'Microsoft.AspNetCore.Authentication.JwtBearer'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.1.0'}, {'fixed': '2.1.29'}]}]}, {'package': {'ecosystem': 'NuGet', 'name': 'Microsoft.AspNetCore.Authentication.JwtBearer'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.0.0'}, {'fixed': '3.1.18'}]}]}, {'package': {'ecosystem': 'NuGet', 'name': 'Microsoft.AspNetCore.Authentication.JwtBearer'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '5.0.0'}, {'fixed': '5.0.9'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/dotnet/aspnetcore/security/advisories/GHSA-q7cg-43mg-qp69'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-34532'}, {'type': 'PACKAGE', 'url': 'https://github.com/dotnet/aspnetcore'}, {'type': 'WEB', 'url': 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2021-34532'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T18:52:16Z', 'nvd_published_at': '2021-08-12T18:15:00Z'}
|
1.4.0
|
GHSA-qpjr-ch72-2qq4
|
2023-06-13T20:35:06Z
|
2021-08-25T20:45:17Z
| null |
['CVE-2019-16881']
|
Use after free in portaudio-rs
|
Affected versions of this crate is not panic safe within callback functions stream_callback and stream_finished_callback. The call to user-provided closure might panic before a mem::forget call, which then causes a use after free that grants attacker to control the callback function pointer. This allows an attacker to construct an arbitrary code execution .
|
[{'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': 'portaudio-rs'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.3.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-16881'}, {'type': 'WEB', 'url': 'https://github.com/mvdnes/portaudio-rs/issues/20'}, {'type': 'WEB', 'url': 'https://github.com/mvdnes/portaudio-rs/commit/7466df019f6739732fd91401017942c22364ef61'}, {'type': 'PACKAGE', 'url': 'https://github.com/mvdnes/portaudio-rs'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0022.html'}]
|
{'cwe_ids': ['CWE-416'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:21:17Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-wrvc-72w7-xpmj
|
2023-08-25T00:12:27Z
|
2021-08-25T20:45:54Z
| null |
['CVE-2019-25002']
|
Incorrect Comparison in sodiumoxide
|
An issue was discovered in the sodiumoxide crate starting with 0.2.0 and prior to 0.2.5 for Rust. `generichash::Digest::eq` compares itself to itself and thus has degenerate security properties.
|
[{'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': 'sodiumoxide'}, 'ecosystem_specific': {'affected_functions': ['sodiumoxide::crypto::generichash::Digest::eq', 'sodiumoxide::crypto::generichash::Digest::ne']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.2.0'}, {'fixed': '0.2.5'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-25002'}, {'type': 'WEB', 'url': 'https://github.com/sodiumoxide/sodiumoxide/pull/381'}, {'type': 'WEB', 'url': 'https://github.com/sodiumoxide/sodiumoxide/pull/381/commits/fae052b834b097ced9a89a8fff8466e18f383070'}, {'type': 'WEB', 'url': 'https://github.com/sodiumoxide/sodiumoxide/commit/38490723927f230498adf795153e6cd3cb08b6a8'}, {'type': 'PACKAGE', 'url': 'https://github.com/sodiumoxide/sodiumoxide'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0026.html'}]
|
{'cwe_ids': ['CWE-697'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:20:40Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-wf5p-c75w-w3wh
|
2021-08-24T17:58:35Z
|
2021-08-25T14:39:36Z
| null |
['CVE-2021-37689']
|
Null pointer dereference in TFLite MLIR optimizations
|
### Impact
An attacker can craft a TFLite model that would trigger a null pointer dereference, which would result in a crash and denial of service:
This is caused by the MLIR optimization of `L2NormalizeReduceAxis` operator. The [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/compiler/mlir/lite/transforms/optimize.cc#L67-L70) unconditionally dereferences a pointer to an iterator to a vector without checking that the vector has elements:
```cc
bool L2NormalizeReduceAxis(Value sq_op, DenseElementsAttr axis) {
if (sq_op.getType().cast<ShapedType>().getRank() - 1 ==
*axis.getValues<int>().begin() ||
*axis.getValues<int>().begin() == -1) {
// ...
}
// ...
}
```
### Patches
We have patched the issue in GitHub commit [d6b57f461b39fd1aa8c1b870f1b974aac3554955](https://github.com/tensorflow/tensorflow/commit/d6b57f461b39fd1aa8c1b870f1b974aac3554955).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Yakun Zhang of Baidu Security.
|
[{'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']}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-wf5p-c75w-w3wh'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37689'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/d6b57f461b39fd1aa8c1b870f1b974aac3554955'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-476'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T17:58:35Z', 'nvd_published_at': '2021-08-12T22:15:00Z'}
|
1.4.0
|
GHSA-r7rv-2rph-hvhj
|
2021-08-19T18:48:19Z
|
2021-08-25T20:51:45Z
| null |
['CVE-2020-36218']
|
Improper synchronization in buttplug
|
An issue was discovered in the buttplug crate before 1.0.4 for Rust. ButtplugFutureStateShared does not properly consider (!Send|!Sync) objects, leading to a data race.
|
[{'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': 'buttplug'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.0.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36218'}, {'type': 'WEB', 'url': 'https://github.com/buttplugio/buttplug-rs/issues/225'}, {'type': 'PACKAGE', 'url': 'https://github.com/buttplugio/buttplug-rs'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0112.html'}]
|
{'cwe_ids': ['CWE-662'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:48:19Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-79mg-4w23-4fqc
|
2021-08-27T12:54:52Z
|
2021-08-30T16:12:58Z
| null |
['CVE-2021-39165']
|
Unauthenticated SQL Injection in Cachet
|
### Impact
In Cachet versions through 2.3.18, there is a SQL injection which is in the `SearchableTrait#scopeSearch()`. Attackers without authentication can utilize this vulnerability to exfiltrate sensitive data from the database such as administrator's password and session.
### Patches
The original repository of [https://github.com/CachetHQ/Cachet](https://github.com/CachetHQ/Cachet) is not active, the stable version 2.3.18 and it's developing 2.4 branch is affected.
Update to version 2.5 or later in the [https://github.com/fiveai/Cachet fork](https://github.com/fiveai/Cachet) to fix this vulnerability.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'cachethq/cachet'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '2.3.18'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/fiveai/Cachet/security/advisories/GHSA-79mg-4w23-4fqc'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39165'}, {'type': 'WEB', 'url': 'https://github.com/fiveai/Cachet/commit/27bca8280419966ba80c6fa283d985ddffa84bb6'}]
|
{'cwe_ids': ['CWE-287', 'CWE-89'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-26T20:21:00Z', 'nvd_published_at': '2021-08-26T21:15:00Z'}
|
1.4.0
|
GHSA-gcvv-gq92-x94r
|
2021-08-23T17:22:58Z
|
2021-08-23T19:42:49Z
| null |
['CVE-2021-37711']
|
Authenticated server-side request forgery in file upload via URL.
|
### Impact
Authenticated server-side request forgery in file upload via URL.
### 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.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': '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-gcvv-gq92-x94r'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37711'}, {'type': 'WEB', 'url': 'https://github.com/shopware/platform/commit/b9f330e652b743dd2374c02bbe68f28b59a3f502'}, {'type': 'PACKAGE', 'url': 'https://github.com/shopware/platform'}]
|
{'cwe_ids': ['CWE-918'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T17:22:58Z', 'nvd_published_at': '2021-08-16T23:15:00Z'}
|
1.4.0
|
GHSA-56cx-wf47-hx7w
|
2023-07-06T21:34:16Z
|
2021-08-09T20:38:37Z
| null |
['CVE-2021-3663']
|
No Restriction of Excessive Authentication Attempts in Firefly III
|
firefly-iii is vulnerable to Improper Lack of Restriction of Excessive Authentication Attempts
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'grumpydictator/firefly-iii'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '5.5.13'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3663'}, {'type': 'WEB', 'url': 'https://github.com/firefly-iii/firefly-iii/commit/afc9f4b7ebc8a240c85864a6e1abda62bfeefae8'}, {'type': 'PACKAGE', 'url': 'https://github.com/firefly-iii/firefly-iii'}, {'type': 'WEB', 'url': 'https://github.com/firefly-iii/firefly-iii/releases/tag/5.5.13'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/497bdf6d-7dba-49c3-8011-1c64dfbb3380'}]
|
{'cwe_ids': ['CWE-307'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-02T22:13:58Z', 'nvd_published_at': '2021-07-25T14:15:00Z'}
|
1.4.0
|
GHSA-q948-x8rf-888m
|
2023-06-13T20:12:22Z
|
2021-08-25T20:47:55Z
| null |
['CVE-2020-35865']
|
os_str_bytes relies on undefined behavior of `char::from_u32_unchecked`
|
The Windows implementation of this crate relied on the behavior of std::char::from_u32_unchecked when its safety clause is violated. Even though this worked with Rust versions up to 1.42 (at least), that behavior could change with any new Rust version, possibly leading a security issue.
The flaw was corrected in version 2.0.0.
|
[{'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': 'os_str_bytes'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.0.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35865'}, {'type': 'WEB', 'url': 'https://github.com/dylni/os_str_bytes/pull/1'}, {'type': 'PACKAGE', 'url': 'https://github.com/dylni/os_str_bytes'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0012.html'}]
|
{'cwe_ids': ['CWE-704'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:08:17Z', 'nvd_published_at': '2020-12-31T10:15:00Z'}
|
1.4.0
|
GHSA-2f5j-3mhq-xv58
|
2023-06-13T22:04:49Z
|
2021-08-25T20:58:15Z
| null |
['CVE-2020-36434']
|
Double free in sys-info
|
Affected versions of sys-info use a static, global, list to store temporary disk information while running. The function that cleans up this list, DFCleanup, assumes a single threaded environment and will try to free the same memory twice in a multithreaded environment. This results in consistent double-frees and segfaults when calling sys_info::disk_info from multiple threads at once. The issue was fixed by moving the global variable into a local scope.
|
[{'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': 'sys-info'}, 'ecosystem_specific': {'affected_functions': ['sys_info::disk_info']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.8.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36434'}, {'type': 'WEB', 'url': 'https://github.com/FillZpp/sys-info-rs/issues/63'}, {'type': 'PACKAGE', 'url': 'https://github.com/FillZpp/sys-info-rs'}, {'type': 'WEB', 'url': 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/sys-info/RUSTSEC-2020-0100.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0100.html'}]
|
{'cwe_ids': ['CWE-415'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T20:16:40Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-mh6h-f25p-98f8
|
2023-06-13T20:32:32Z
|
2021-08-25T20:44:05Z
| null |
['CVE-2019-15544']
|
Uncontrolled memory consumption in protobuf
|
Affected versions of this crate called Vec::reserve() on user-supplied input. This allows an attacker to cause an Out of Memory condition while calling the vulnerable method on untrusted data.
|
[{'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': 'protobuf'}, 'ecosystem_specific': {'affected_functions': ['protobuf::stream::read_raw_bytes_into']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.6.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-15544'}, {'type': 'WEB', 'url': 'https://github.com/stepancheg/rust-protobuf/issues/411'}, {'type': 'PACKAGE', 'url': 'https://github.com/stepancheg/rust-protobuf'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r00097d0b5b6164ea428554007121d5dc1f88ba2af7b9e977a10572cd@%3Cdev.hbase.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r4ef574a5621b0e670a3ce641e9922543e34f22bf4c9ee9584aa67fcf@%3Cissues.hbase.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r7fed8dd9bee494094e7011cf3c2ab75bd8754ea314c6734688c42932@%3Ccommon-issues.hadoop.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rd64381fb8f92d640c1975dc50dcdf1b8512e02a2a7b20292d3565cae@%3Cissues.hbase.apache.org%3E'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0003.html'}]
|
{'cwe_ids': ['CWE-770'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:23:35Z', 'nvd_published_at': '2019-08-26T18:15:00Z'}
|
1.4.0
|
GHSA-qfpc-5pjr-mh26
|
2021-08-24T15:50:58Z
|
2021-08-25T14:41:23Z
| null |
['CVE-2021-37677']
|
Missing validation in shape inference for `Dequantize`
|
### Impact
The shape inference code for `tf.raw_ops.Dequantize` has a vulnerability that could trigger a denial of service via a segfault if an attacker provides invalid arguments:
```python
import tensorflow as tf
tf.compat.v1.disable_v2_behavior()
tf.raw_ops.Dequantize(
input_tensor = tf.constant(-10.0, dtype=tf.float32),
input_tensor = tf.cast(input_tensor, dtype=tf.quint8),
min_range = tf.constant([], shape=[0], dtype=tf.float32),
max_range = tf.constant([], shape=[0], dtype=tf.float32),
mode = 'MIN_COMBINED',
narrow_range=False,
axis=-10,
dtype=tf.dtypes.float32)
```
The shape inference [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/array_ops.cc#L2999-L3014) uses `axis` to select between two different values for `minmax_rank` which is then used to retrieve tensor dimensions. However, code assumes that `axis` can be either `-1` or a value greater than `-1`, with no validation for the other values.
### Patches
We have patched the issue in GitHub commit [da857cfa0fde8f79ad0afdbc94e88b5d4bbec764](https://github.com/tensorflow/tensorflow/commit/da857cfa0fde8f79ad0afdbc94e88b5d4bbec764).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Yakun Zhang of Baidu Security.
|
[{'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-qfpc-5pjr-mh26'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37677'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/da857cfa0fde8f79ad0afdbc94e88b5d4bbec764'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-1284', 'CWE-20'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T15:50:15Z', 'nvd_published_at': '2021-08-12T23:15:00Z'}
|
1.4.0
|
GHSA-7889-rm5j-hpgg
|
2022-02-08T21:01:48Z
|
2021-08-23T19:40:57Z
| null |
['CVE-2021-32809']
|
Clipboard feature vulnerability allowing to inject arbitrary HTML into the editor using paste functionality
|
### Affected packages
The vulnerability has been discovered in [clipboard](https://ckeditor.com/cke4/addon/clipboard) plugin. All plugins with [clipboard](https://ckeditor.com/cke4/addon/clipboard) plugin dependency are affected:
* [clipboard](https://ckeditor.com/cke4/addon/clipboard)
* [pastetext](https://ckeditor.com/cke4/addon/pastetext)
* [pastetools](https://ckeditor.com/cke4/addon/pastetools)
* [widget](https://ckeditor.com/cke4/addon/widget)
* [uploadwidget](https://ckeditor.com/cke4/addon/uploadwidget)
* [autolink](https://ckeditor.com/cke4/addon/autolink)
* [tableselection](https://ckeditor.com/cke4/addon/tableselection)
### Impact
A potential vulnerability has been discovered in CKEditor 4 [Clipboard](https://ckeditor.com/cke4/addon/clipboard) package. The vulnerability allowed to abuse paste functionality using malformed HTML, which could result in injecting arbitrary HTML into the editor. It affects all users using the CKEditor 4 plugins listed above at version >= 4.5.2.
### Patches
The problem has been recognized and patched. The fix will be available in version 4.16.2.
### For more information
Email us at security@cksource.com if you have any questions or comments about this advisory.
### Acknowledgements
The CKEditor 4 team would like to thank Anton Subbotin ([skavans](https://github.com/skavans)) for recognizing and reporting this vulnerability.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'ckeditor4'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.5.2'}, {'fixed': '4.16.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/ckeditor/ckeditor4/security/advisories/GHSA-7889-rm5j-hpgg'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-32809'}, {'type': 'PACKAGE', 'url': 'https://github.com/ckeditor/ckeditor4'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NYA354LJP47KCVJMTUO77ZCX3ZK42G3T/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UVOYN2WKDPLKCNILIGEZM236ABQASLGW/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WAGNWHFIQAVCP537KFFS2A2GDG66J7XD/'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujan2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2021.html'}]
|
{'cwe_ids': ['CWE-79', 'CWE-94'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T16:49:10Z', 'nvd_published_at': '2021-08-12T17:15:00Z'}
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.