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-438g-fx34-4h9m
|
2021-08-19T21:06:40Z
|
2021-08-25T20:48:38Z
| null |
['CVE-2020-35892']
|
Out of bounds read in simple-slab
|
An issue was discovered in the simple-slab crate before 0.3.3 for Rust. index() allows an out-of-bounds read.
|
[{'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': 'simple-slab'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.3.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35892'}, {'type': 'WEB', 'url': 'https://github.com/nathansizemore/simple-slab/issues/2'}, {'type': 'PACKAGE', 'url': 'https://github.com/nathansizemore/simple-slab'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0039.html'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:06:40Z', 'nvd_published_at': '2020-12-31T10:15:00Z'}
|
1.4.0
|
GHSA-vj88-5667-w56p
|
2021-08-24T17:44:58Z
|
2021-08-25T21:00:11Z
|
2021-08-24T17:44:58Z
|
[]
|
Singleton lacks bounds on Send and Sync.
|
`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`.
|
[]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'ruspiro-singleton'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/RusPiRo/ruspiro-singleton/issues/10'}, {'type': 'PACKAGE', 'url': 'https://github.com/RusPiRo/ruspiro-singleton'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0115.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-06T19:10:18Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-hw7r-qrhp-5pff
|
2021-08-25T15:42:30Z
|
2021-08-30T16:16:46Z
| null |
[]
|
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-bom'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '12.0.0'}, {'fixed': '14.6.8'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'com.vaadin:vaadin-bom'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '15.0.0'}, {'fixed': '20.0.6'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/vaadin/platform/security/advisories/GHSA-hw7r-qrhp-5pff'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-25T15:42:30Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-fcwc-p4fc-c5cc
|
2021-08-23T19:11:53Z
|
2021-08-25T14:43:42Z
| null |
['CVE-2021-37643']
|
Null pointer dereference in `MatrixDiagPartOp`
|
### Impact
If a user does not provide a valid padding value to `tf.raw_ops.MatrixDiagPartOp`, then the code triggers a null pointer dereference (if input is empty) or produces invalid behavior, ignoring all values after the first:
```python
import tensorflow as tf
tf.raw_ops.MatrixDiagPartV2(
input=tf.ones(2,dtype=tf.int32),
k=tf.ones(2,dtype=tf.int32),
padding_value=[])
```
Although this example is given for `MatrixDiagPartV2`, all versions of the operation are affected.
The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/linalg/matrix_diag_op.cc#L89) reads the first value from a tensor buffer without first checking that the tensor has values to read from.
### Patches
We have patched the issue in GitHub commit [482da92095c4d48f8784b1f00dda4f81c28d2988](https://github.com/tensorflow/tensorflow/commit/482da92095c4d48f8784b1f00dda4f81c28d2988).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-fcwc-p4fc-c5cc'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37643'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/482da92095c4d48f8784b1f00dda4f81c28d2988'}]
|
{'cwe_ids': ['CWE-476'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T19:11:53Z', 'nvd_published_at': '2021-08-12T19:15:00Z'}
|
1.4.0
|
GHSA-368f-29c3-4f2r
|
2023-06-13T22:36:54Z
|
2021-08-25T20:58:50Z
| null |
['CVE-2020-36437']
|
Data race in conqueue
|
Affected versions of this crate unconditionally implemented `Send`/`Sync` for `QueueSender<T>`, allowing to send non-Send `T` to other threads by invoking `(&QueueSender<T>).send()`.
This fails to prevent users from creating data races by sending types like `Rc<T>` or `Arc<Cell<T>>` to other threads, which can lead to memory corruption. The flaw was corrected in commit `1e462c3` by imposing `T: Send` to both `Send`/`Sync` impls for `QueueSender<T>`/`QueueReceiver<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': 'conqueue'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36437'}, {'type': 'WEB', 'url': 'https://github.com/longshorej/conqueue/commit/1e462c32e7933821ddb26dc49fd4ffa5aeca97b8'}, {'type': 'PACKAGE', 'url': 'https://github.com/longshorej/conqueue'}, {'type': 'WEB', 'url': 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/conqueue/RUSTSEC-2020-0117.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0117.html'}]
|
{'cwe_ids': ['CWE-119', 'CWE-362'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-10T17:36:54Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-9279-7hph-r3xw
|
2021-07-26T23:00:52Z
|
2021-08-02T16:54:09Z
| null |
['CVE-2021-30129']
|
Buffer Overflow in Apache Mina SSHD
|
A vulnerability in sshd-core of Apache Mina SSHD allows an attacker to overflow the server causing an OutOfMemory error. This issue affects the SFTP and port forwarding features of Apache Mina SSHD version 2.0.0 and later versions. It was addressed in Apache Mina SSHD 2.7.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': 'Maven', 'name': 'org.apache.sshd:sshd-mina'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.0.0'}, {'fixed': '2.7.0'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.apache.sshd:sshd-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.0.0'}, {'fixed': '2.7.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-30129'}, {'type': 'WEB', 'url': 'https://issues.apache.org/jira/browse/SSHD-1125'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r6d4f78e192a0c8eabd671a018da464024642980ecd24096bde6db36f%40%3Cusers.mina.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r6d4f78e192a0c8eabd671a018da464024642980ecd24096bde6db36f@%3Cusers.mina.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/red01829efa2a8c893c4baff4f23c9312bd938543a9b8658e172b853b@%3Cannounce.apache.org%3E'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuapr2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujul2022.html'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/07/12/1'}]
|
{'cwe_ids': ['CWE-772'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-07-13T23:19:33Z', 'nvd_published_at': '2021-07-12T12:15:00Z'}
|
1.4.0
|
GHSA-cpv8-6xgr-rmf6
|
2022-08-10T23:57:35Z
|
2021-08-30T16:22:46Z
| null |
['CVE-2021-25955']
|
Dolibarr Cross-site Scripting vulnerability
|
In `Dolibarr ERP CRM`, WYSIWYG Editor module, v2.8.1 to v13.0.2 are affected by a stored XSS vulnerability that allows low privileged application users to store malicious scripts in the `Private Note` field at `/adherents/note.php?id=1` endpoint. These scripts are executed in a victim’s browser when they open the page containing the vulnerable field. In the worst case, the victim who inadvertently triggers the attack is a highly privileged administrator. The injected scripts can extract the Session ID, which can lead to full Account takeover of the admin and due to other vulnerability (Improper Access Control on Private notes) a low privileged user can update the private notes which could lead to privilege escalation.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'dolibarr/dolibarr'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.8.1'}, {'fixed': '14.0.0'}]}], 'database_specific': {'last_known_affected_version_range': '<= 13.0.2'}}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-25955'}, {'type': 'WEB', 'url': 'https://github.com/Dolibarr/dolibarr/commit/796b2d201acb9938b903fb2afa297db289ecc93e'}, {'type': 'PACKAGE', 'url': 'https://github.com/Dolibarr/dolibarr/'}, {'type': 'WEB', 'url': 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25955'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-26T19:42:53Z', 'nvd_published_at': '2021-08-15T21:15:00Z'}
|
1.4.0
|
GHSA-wcg3-cvx6-7396
|
2022-12-06T00:16:25Z
|
2021-08-25T20:56:46Z
| null |
['CVE-2020-26235']
|
Segmentation fault in time
|
### Impact
Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
The affected functions from time 0.2.7 through 0.2.22 are:
- `time::UtcOffset::local_offset_at`
- `time::UtcOffset::try_local_offset_at`
- `time::UtcOffset::current_local_offset`
- `time::UtcOffset::try_current_local_offset`
- `time::OffsetDateTime::now_local`
- `time::OffsetDateTime::try_now_local`
The affected functions in time 0.1 (all versions) are:
- `at`
- `at_utc`
- `now`
Non-Unix targets (including Windows and wasm) are unaffected.
### Patches
In some versions of `time`, the internal method that determines the local offset has been modified to always return `None` on the affected operating systems. This has the effect of returning an `Err` on the `try_*` methods and `UTC` on the non-`try_*` methods. In later versions, `time` will attempt to determine the number of threads running in the process. If the process is single-threaded, the call will proceed as its safety invariant is upheld.
Users and library authors with time in their dependency tree must perform `cargo update`, which will pull in the updated, unaffected code.
Users of time 0.1 do not have a patch and must upgrade to an unaffected version: time 0.2.23 or greater or the 0.3 series.
### Workarounds
Library authors must ensure that the program only has one running thread at the time of calling any affected method. Binary authors may do the same and/or ensure that no other thread is actively mutating the environment.
### References
[time-rs/time#293](https://github.com/time-rs/time/issues/293).
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'time'}, 'ecosystem_specific': {'affected_functions': ['time::UtcOffset::local_offset_at', 'time::UtcOffset::try_local_offset_at', 'time::UtcOffset::current_local_offset', 'time::UtcOffset::try_current_local_offset', 'time::OffsetDateTime::now_local', 'time::OffsetDateTime::try_now_local', 'time::at', 'time::at_utc', 'time::now']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.1.0'}, {'fixed': '0.2.23'}]}], 'database_specific': {'last_known_affected_version_range': '< 0.2.0'}}, {'package': {'ecosystem': 'crates.io', 'name': 'time'}, 'ecosystem_specific': {'affected_functions': ['time::UtcOffset::local_offset_at', 'time::UtcOffset::try_local_offset_at', 'time::UtcOffset::current_local_offset', 'time::UtcOffset::try_current_local_offset', 'time::OffsetDateTime::now_local', 'time::OffsetDateTime::try_now_local']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.2.7'}, {'fixed': '0.2.23'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/time-rs/time/security/advisories/GHSA-wcg3-cvx6-7396'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-26235'}, {'type': 'WEB', 'url': 'https://github.com/time-rs/time/issues/293'}, {'type': 'WEB', 'url': 'https://crates.io/crates/time/0.2.23'}, {'type': 'PACKAGE', 'url': 'https://github.com/time-rs/time'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0071.html'}]
|
{'cwe_ids': ['CWE-476'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T21:06:21Z', 'nvd_published_at': '2020-11-24T22:15:00Z'}
|
1.4.0
|
GHSA-qrx8-8545-4wg2
|
2022-02-08T20:59:49Z
|
2021-08-25T14:47:38Z
| null |
['CVE-2021-39148']
|
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-39148](https://x-stream.github.io/CVE-2021-39148.html).
### Credits
wh1t3p1g from TSRC (Tencent Security Response Center) found and reported the issue to XStream and provided the required information to reproduce it.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)
* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'com.thoughtworks.xstream:xstream'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.4.18'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/x-stream/xstream/security/advisories/GHSA-qrx8-8545-4wg2'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39148'}, {'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-39148.html'}]
|
{'cwe_ids': ['CWE-502'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T18:22:19Z', 'nvd_published_at': '2021-08-23T18:15:00Z'}
|
1.4.0
|
GHSA-qxjq-v4wf-ppvh
|
2023-06-13T17:12:14Z
|
2021-08-25T20:49:47Z
| null |
['CVE-2020-35903']
|
Out of bounds read in dync
|
VecCopy::data is created as a Vec of u8 but can be used to store and retrieve elements of different types leading to misaligned access.
The issue was resolved in v0.5.0 by replacing data being stored by Vec<u8> with a custom managed pointer. Elements are now stored and retrieved using types with proper alignment corresponding to original types.
|
[{'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': 'dync'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.5.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35903'}, {'type': 'WEB', 'url': 'https://github.com/elrnv/dync/issues/4'}, {'type': 'PACKAGE', 'url': 'https://github.com/elrnv/dync'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0050.html'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T20:50:45Z', 'nvd_published_at': '2020-12-31T09:15:00Z'}
|
1.4.0
|
GHSA-m7fm-4jfh-jrg6
|
2021-08-24T12:39:49Z
|
2021-08-25T14:43:07Z
| null |
['CVE-2021-37652']
|
Use after free in boosted trees creation
|
### Impact
The implementation for `tf.raw_ops.BoostedTreesCreateEnsemble` can result in a use after free error if an attacker supplies specially crafted arguments:
```python
import tensorflow as tf
v= tf.Variable([0.0])
tf.raw_ops.BoostedTreesCreateEnsemble(
tree_ensemble_handle=v.handle,
stamp_token=[0],
tree_ensemble_serialized=['0'])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/boosted_trees/resource_ops.cc#L55) uses a reference counted resource and decrements the refcount if the initialization fails, as it should. However, when the code was written, the resource was represented as a naked pointer but later refactoring has changed it to be a smart pointer. Thus, when the pointer leaves the scope, a subsequent `free`-ing of the resource occurs, but this fails to take into account that the refcount has already reached 0, thus the resource has been already freed. During this double-free process, members of the resource object are accessed for cleanup but they are invalid as the entire resource has been freed.
### Patches
We have patched the issue in GitHub commit [5ecec9c6fbdbc6be03295685190a45e7eee726ab](https://github.com/tensorflow/tensorflow/commit/5ecec9c6fbdbc6be03295685190a45e7eee726ab).
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-m7fm-4jfh-jrg6'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37652'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/5ecec9c6fbdbc6be03295685190a45e7eee726ab'}]
|
{'cwe_ids': ['CWE-415', 'CWE-416'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T12:39:49Z', 'nvd_published_at': '2021-08-12T22:15:00Z'}
|
1.4.0
|
GHSA-36xw-hgfv-jwm7
|
2023-06-13T16:51:41Z
|
2021-08-25T20:48:36Z
| null |
['CVE-2020-35888']
|
Multiple security issues including data race, buffer overflow, and uninitialized memory drop in arr
|
arr crate contains multiple security issues. Specifically,
1. It incorrectly implements Sync/Send bounds, which allows to smuggle non-Sync/Send types across the thread boundary.
2. Index and IndexMut implementation does not check the array bound.
3. Array::new_from_template() drops uninitialized memory.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'arr'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.6.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35888'}, {'type': 'WEB', 'url': 'https://github.com/sjep/array/issues/1'}, {'type': 'PACKAGE', 'url': 'https://github.com/sjep/array'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0034.html'}]
|
{'cwe_ids': ['CWE-908'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:06:43Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-f3mq-99jr-ww4r
|
2023-06-13T16:55:13Z
|
2021-08-25T20:56:16Z
| null |
['CVE-2020-36467']
|
Multiple soundness issues 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-36467'}, {'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-18T21:11:39Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-hxwm-x553-x359
|
2021-08-02T19:02:32Z
|
2021-08-05T17:07:39Z
| null |
[]
|
Arbitrary Command Injection due to Improper Command Sanitization
|
### Summary
There exists a command injection vulnerability in `npmcli/git` versions <2.0.8 which may result in arbitrary shell command execution due to improper argument sanitization when `npmcli/git` is used to execute Git commands based on user controlled input.
The impact of this issue is possible Arbitrary Command Injection when `npmcli/git` is run with untrusted (user controlled) Git command arguments.
### Impact
Arbitrary Command Injection
### Details
`npmcli/git` prior to release `2.0.8` passed user controlled input as arguments to a shell command without properly sanitizing this input. Passing unsanitized input to a shell can lead to arbitrary command injection. For example passing `git+https://github.com/npm/git; echo hello world` would trigger the shell execution of `echo hello world`.
This issue was remediated by no longer running `npmcli/git` git commands through an intermediate shell.
### Patches
This issue has been patched in release `2.0.8`
### Acknowledgements
This report was reported to us by @tyage (Ierae Security) through the [GitHub Bug Bounty Program](https://bounty.github.com).
|
[]
|
[{'package': {'ecosystem': 'npm', 'name': '@npmcli/git'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.0.8'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/npm/git/security/advisories/GHSA-hxwm-x553-x359'}, {'type': 'WEB', 'url': 'https://github.com/npm/git/pull/29'}]
|
{'cwe_ids': ['CWE-78'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-02T19:02:32Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-9c8w-jrw3-q2c3
|
2022-02-08T21:02:36Z
|
2021-08-02T16:58:43Z
| null |
['CVE-2021-35043']
|
Cross-site Scripting in OWASP AntiSamy
|
OWASP AntiSamy before 1.6.4 allows XSS via HTML attributes when using the HTML output serializer (XHTML is not affected). This was demonstrated by a javascript: URL with : as the replacement for the : character.
|
[{'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': 'Maven', 'name': 'org.owasp.antisamy:antisamy'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.6.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-35043'}, {'type': 'WEB', 'url': 'https://github.com/nahsra/antisamy/pull/87'}, {'type': 'PACKAGE', 'url': 'https://github.com/nahsra/antisamy'}, {'type': 'WEB', 'url': 'https://github.com/nahsra/antisamy/releases/tag/v1.6.4'}, {'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'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-07-19T21:38:51Z', 'nvd_published_at': '2021-07-19T15:15:00Z'}
|
1.4.0
|
GHSA-95xm-g58g-3p88
|
2021-08-23T18:28:24Z
|
2021-08-25T14:44:02Z
| null |
['CVE-2021-37640']
|
Integer division by 0 in sparse reshaping
|
### Impact
The implementation of `tf.raw_ops.SparseReshape` can be made to trigger an integral division by 0 exception:
```python
import tensorflow as tf
tf.raw_ops.SparseReshape(
input_indices = np.ones((1,3)),
input_shape = np.array([1,1,0]),
new_shape = np.array([1,0]))
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L176-L181) calls the reshaping functor whenever there is at least an index in the input but does not check that shape of the input or the target shape have both a non-zero number of elements.
The [reshape functor](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L40-L78) blindly divides by the dimensions of the target shape. Hence, if this is not checked, code will result in a division by 0.
### Patches
We have patched the issue in GitHub commit [4923de56ec94fff7770df259ab7f2288a74feb41](https://github.com/tensorflow/tensorflow/commit/4923de56ec94fff7770df259ab7f2288a74feb41).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1 as this is the other affected version.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
[{'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-95xm-g58g-3p88'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37640'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/4923de56ec94fff7770df259ab7f2288a74feb41'}]
|
{'cwe_ids': ['CWE-369'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T18:28:24Z', 'nvd_published_at': '2021-08-12T18:15:00Z'}
|
1.4.0
|
GHSA-m7w4-8wp8-m2xq
|
2021-08-24T18:35:48Z
|
2021-08-25T20:59:08Z
| null |
['CVE-2020-36442']
|
Data races in beef
|
An issue was discovered in the beef crate before 0.5.0 for Rust.
Affected versions of this crate did not have a `T: Sync` bound in the `Send` impl for `Cow<'_, T, U>`. This allows users to create data races by making `Cow` contain types that are (Send && !Sync) like `Cell<_>` or `RefCell<_>`.
Such data races can lead to memory corruption.
The flaw was corrected in commit d1c7658 by adding trait bounds `T: Sync` and `T::Owned: Send` to the `Send` impl for `Cow<'_, T, U>`.
|
[{'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': 'beef'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.5.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36442'}, {'type': 'WEB', 'url': 'https://github.com/maciejhirsz/beef/issues/37'}, {'type': 'PACKAGE', 'url': 'https://github.com/maciejhirsz/beef'}, {'type': 'WEB', 'url': 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/beef/RUSTSEC-2020-0122.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0122.html'}]
|
{'cwe_ids': ['CWE-119', 'CWE-362'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-09T21:50:28Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-2r8p-fg3c-wcj4
|
2021-08-24T12:46:02Z
|
2021-08-25T14:43:01Z
| null |
['CVE-2021-37654']
|
Heap OOB and CHECK fail in `ResourceGather`
|
### Impact
An attacker can trigger a crash via a `CHECK`-fail in debug builds of TensorFlow using `tf.raw_ops.ResourceGather` or a read from outside the bounds of heap allocated data in the same API in a release build:
```python
import tensorflow as tf
tensor = tf.constant(value=[[1,2],[3,4],[5,6]],shape=(3,2),dtype=tf.uint32)
v = tf.Variable(tensor)
tf.raw_ops.ResourceGather(
resource=v.handle,
indices=[0],
dtype=tf.uint32,
batch_dims=10,
validate_indices=False)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L660-L668) does not check that the `batch_dims` value that the user supplies is less than the rank of the input tensor.
Since the implementation uses several for loops over the dimensions of `tensor`, this results in reading data from outside the bounds of heap allocated buffer backing the tensor:
```cc
// batch_dims_ = > params.dims() (10 > 2)
for (int i = 0; i < batch_dims_; ++i) {
result_shape.AddDim(params.dim_size(i));
}
for (int i = batch_dims_; i < indices.dims(); ++i) {
result_shape.AddDim(indices.dim_size(i));
}
for (int i = batch_dims_ + 1; i < params.dims(); ++i) {
result_shape.AddDim(params.dim_size(i));
}
```
In debug mode, `.dim_size(i)` validates that the argument is less than `.dims()` using a `DCHECK`. But the `DCHECK` is a no-op in release builds.
### Patches
We have patched the issue in GitHub commit [bc9c546ce7015c57c2f15c168b3d9201de679a1d](https://github.com/tensorflow/tensorflow/commit/bc9c546ce7015c57c2f15c168b3d9201de679a1d).
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-2r8p-fg3c-wcj4'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37654'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/bc9c546ce7015c57c2f15c168b3d9201de679a1d'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow/'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T12:46:02Z', 'nvd_published_at': '2021-08-12T21:15:00Z'}
|
1.4.0
|
GHSA-hpqh-2wqx-7qp5
|
2023-01-25T18:03:21Z
|
2021-08-25T21:01:55Z
| null |
['CVE-2021-32629']
|
Memory access due to code generation flaw in Cranelift module
|
There is a bug in 0.73.0 of the Cranelift x64 backend that can create a scenario that could result in a potential sandbox escape in a WebAssembly module. Users of versions 0.73.0 of Cranelift should upgrade to either 0.73.1 or 0.74 to remediate this vulnerability. Users of Cranelift prior to 0.73.0 should update to 0.73.1 or 0.74 if they were not using the old default backend.
### Description
This bug was introduced in the new backend on 2020-09-08 and first included in a release on 2020-09-30, but the new backend was not the default prior to 0.73.0. The recently-released version 0.73.0 with default settings, and prior versions with an explicit build flag to select the new backend, are vulnerable. The bug in question performs a sign-extend instead of a zero-extend on a value loaded from the stack, under a specific set of circumstances. If those circumstances occur, the bug could allow access to memory addresses up to 2GiB before the start of the heap allocated for the WebAssembly module.
If the heap bound is larger than 2GiB, then it would be possible to read memory from a computable range dependent on the size of the heap's bound.
The impact of this bug is highly dependent on heap implementation; specifically:
* if the heap has bounds checks, and
* does not rely exclusively on guard pages, and
* the heap bound is 2GiB or smaller
then this bug cannot be used to reach memory from another WebAssembly module heap.
The impact of the vulnerability is mitigated if there is no memory mapped in the range accessible using this bug, for example, if there is a 2 GiB guard region before the WebAssembly module heap.
The bug in question performs a sign-extend instead of a zero-extend on a value loaded from the stack when the register allocator reloads a spilled integer value narrower than 64 bits. This interacts poorly with another optimization: the instruction selector elides a 32-to-64-bit zero-extend operator when we know that an instruction producing a 32-bit value actually zeros the upper 32 bits of its destination register. Hence, we rely on these zeroed bits, but the type of the value is still i32, and the spill/reload reconstitutes those bits as the sign extension of the i32’s MSB.
The issue would thus occur when:
* An i32 value is greater than or equal to 0x8000_0000;
* The value is spilled and reloaded by the register allocator due to high register pressure in the program between the value’s definition and its use;
* The value is produced by an instruction that we know to be "special" in that it zeroes the upper 32 bits of its destination: add, sub, mul, and, or;
* The value is then zero-extended to 64 bits;
* The resulting 64-bit value is used.
Under these circumstances there is a potential sandbox escape when the i32 value is a pointer. The usual code emitted for heap accesses zero-extends the WebAssembly heap address, adds it to a 64-bit heap base, and accesses the resulting address. If the zero-extend becomes a sign-extend, the module could reach backward and access memory up to 2GiB before the start of its heap.
This bug was identified by developers at Fastly following a report from Javier Cabrera Arteaga, KTH Royal Institute of Technology, with support from project Trustful of Stiftelsen för Strategisk Forskning. In addition to supporting the analysis and remediation of this vulnerability, Fastly will publish a related Fastly Security Advisory at [https://www.fastly.com/security-advisories](https://www.fastly.com/security-advisories).
In addition to assessing the nature of the code generation bug in Cranelift, we have also determined that under specific circumstances, both Lucet and Wasmtime using this version of Cranelift may be exploitable.
### General Impact to Lucet
Lucet inherits the heap address computation and bounds-checks of Cranelift, which it uses as its backend code generator. Of particular importance specifically is the address-space layout used by Lucet. In the default configuration for Lucet, only a single module is running, and therefore it is not possible to access memory from another module.
By default, the open source implementation of Lucet uses a maximum heap size of 4 GiB, and an instance slot size of 8 GiB, when invoking an instance from the lucet-wasi command-line tool. These settings are within the range of vulnerability described above, but only a single instance is running, so there is no other instance to read. When embedding the runtime (for example, in a long-running daemon), the default for the heap size as described in the source is 1MB; with this setting, the runtime is not vulnerable.
Lucet allocates its WebAssembly module instances into "instance slots", which are contiguous zones of virtual address space that contain the VM context at the bottom, the WebAssembly heap in the next page after that, a guard region in the middle, and other data at the top: the stack and the globals.
If the instance slot size is less than (max heap) + 2GiB, then the lowest accessible address using the bug will overlap with the prior instance’s heap. If the size of VM context + stack + globals is greater than (4GiB - heap limit), then the highest accessible address using the bug will overlap with this critical data. If neither of these conditions are true, the bug should only result in an access to the prior instance’s guard region.
Generally, if the limit is between 2GiB and 4GiB - ~1MB (depending on stack/global size) and the instance slot size is less than 6GiB, the configuration is vulnerable. If the limit is greater than 4GiB - ~1MB, the configuration is vulnerable regardless of instance slot size. Otherwise, the configuration is not vulnerable.
### General Impact on Wasmtime
In Wasmtime, the same Cranelift heap address computations and heap types are used as above. The memory layout, however, is slightly different, with different outcomes:
* With the mmap implementation impact is mitigated probabilistically if ASLR is enabled.
* With the pooling allocator, the vulnerability only exists if a memory reservation size lower than the default of 6GB is used.
With the default mmap-based instance memory implementation, Wasmtime uses mmap() to allocate a block of memory large enough for the heap and guard region, as specified in its configuration. If the underlying OS implements ASLR (modern Linux, macOS and Windows do) then this address will be randomized, and the region below it will (probabilistically) be free. Hence, the bug is mitigated probabilistically in the default configuration if ASLR is enabled.
If using the pooling allocator, the vulnerability exists if instance memory size (`memory_reservation_size` in InstanceLimit) is strictly less than 6GiB (4 GiB + 2 GiB of guard pages). The default is 6GiB, so the vulnerability is masked in the default pooling allocator configuration.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'cranelift-codegen'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.73.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-hpqh-2wqx-7qp5'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-32629'}, {'type': 'WEB', 'url': 'https://github.com/bytecodealliance/wasmtime/commit/95559c01aaa7c061088a433040f31e8291fb09d0'}, {'type': 'WEB', 'url': 'https://crates.io/crates/cranelift-codegen'}, {'type': 'WEB', 'url': 'https://github.com/RustSec/advisory-db/blob/main/crates/cranelift-codegen/RUSTSEC-2021-0067.md'}, {'type': 'PACKAGE', 'url': 'https://github.com/bytecodealliance/wasmtime/tree/main/cranelift'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0067.html'}, {'type': 'WEB', 'url': 'https://www.fastly.com/security-advisories/memory-access-due-to-code-generation-flaw-in-cranelift-module'}]
|
{'cwe_ids': ['CWE-125', 'CWE-788'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-05-25T20:51:32Z', 'nvd_published_at': '2021-05-24T16:15:00Z'}
|
1.4.0
|
GHSA-p9gf-gmfv-398m
|
2023-03-30T23:01:08Z
|
2021-08-25T20:54:16Z
| null |
['CVE-2021-29938']
|
Double free in slice-deque
|
An issue was discovered in the slice-deque crate through 2021-02-19 for Rust. A double drop can occur in SliceDeque::drain_filter upon a panic in a predicate function.
|
[{'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': 'slice-deque'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.3.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-29938'}, {'type': 'WEB', 'url': 'https://github.com/gnzlbg/slice_deque/issues/90'}, {'type': 'PACKAGE', 'url': 'https://github.com/gnzlbg/slice_deque'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0047.html'}]
|
{'cwe_ids': ['CWE-415'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:14:58Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-4vhw-4rw7-jfpv
|
2023-02-09T14:23:48Z
|
2021-08-25T20:49:02Z
| null |
['CVE-2020-35883']
|
Path traversal in mozwire
|
An issue was discovered in the mozwire crate through 2020-08-18 for Rust. A ../ directory-traversal situation allows overwriting local files that have .conf at the end of the filename.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'mozwire'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.5.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35883'}, {'type': 'WEB', 'url': 'https://github.com/NilsIrl/MozWire/issues/14'}, {'type': 'WEB', 'url': 'https://github.com/NilsIrl/MozWire/pull/17/commits/dd0639bf2876773b66382f47285f7db701f628d9'}, {'type': 'PACKAGE', 'url': 'https://github.com/NilsIrl/MozWire/'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0030.html'}]
|
{'cwe_ids': ['CWE-22'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T20:56:07Z', 'nvd_published_at': '2020-12-31T10:15:00Z'}
|
1.4.0
|
GHSA-29v7-3v4c-gf38
|
2023-06-13T20:11:11Z
|
2021-08-25T20:57:24Z
| null |
['CVE-2020-36454']
|
Data races in parc
|
In the affected versions of this crate, LockWeak<T> unconditionally implemented Send with no trait bounds on T. LockWeak<T> doesn't own T and only provides &T. This allows concurrent access to a non-Sync T, which can cause undefined behavior like data races.
|
[{'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': 'parc'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.0.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36454'}, {'type': 'WEB', 'url': 'https://github.com/hyyking/rustracts/pull/6'}, {'type': 'PACKAGE', 'url': 'https://github.com/hyyking/rustracts/tree/master/parc'}, {'type': 'WEB', 'url': 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/parc/RUSTSEC-2020-0134.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0134.html'}]
|
{'cwe_ids': ['CWE-119', 'CWE-362'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T20:23:35Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-wv4p-jp67-jr97
|
2023-06-13T18:44:57Z
|
2021-08-25T20:50:05Z
| null |
['CVE-2020-35925']
|
Data races in magnetic
|
Affected versions of this crate unconditionally implemented Sync and Send traits for MPMCConsumer and MPMCProducer types. This allows users to send types that do not implement Send trait across thread boundaries, which can cause a data race. The flaw was corrected in the 2.0.1 release by adding T: Send bound to affected Sync/Send trait implementations.
|
[{'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': 'magnetic'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.0.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35925'}, {'type': 'WEB', 'url': 'https://github.com/johnshaw/magnetic/issues/9'}, {'type': 'PACKAGE', 'url': 'https://github.com/johnshaw/magnetic'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0088.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:56:44Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-f8pv-x7h8-687v
|
2021-09-02T18:50:42Z
|
2021-08-30T16:22:25Z
| null |
['CVE-2020-19709']
|
Cross-site scripting in feehicms
|
Insufficient filtering of the tag parameters in feehicms 0.1.3 allows attackers to execute arbitrary web or HTML via a crafted payload.
|
[{'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': 'feehi/feehicms'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.1.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-19709'}, {'type': 'WEB', 'url': 'https://github.com/liufee/feehicms/issues/2'}, {'type': 'PACKAGE', 'url': 'https://github.com/liufee/feehicms'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-27T12:52:23Z', 'nvd_published_at': '2021-08-26T03:15:00Z'}
|
1.4.0
|
GHSA-5pg8-h4gv-m3p8
|
2021-08-19T17:22:27Z
|
2021-08-25T20:53:56Z
| null |
['CVE-2021-28306']
|
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 multi label type if the image is nonexistent.
|
[{'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::WidgetExt::set_label_type']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.15.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-28306'}, {'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:27Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-ch3r-vp46-8g22
|
2021-08-31T21:00:31Z
|
2021-08-09T20:39:52Z
| null |
['CVE-2020-17952']
|
Code injection in topthink/think
|
A remote code execution (RCE) vulnerability in /library/think/App.php of Twothink v2.0 allows attackers to execute arbitrary PHP 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': 'Packagist', 'name': 'topthink/think'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '6.0.9'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-17952'}, {'type': 'WEB', 'url': 'https://github.com/twothink/twothink/issues/1'}, {'type': 'PACKAGE', 'url': 'https://github.com/twothink/twothink'}]
|
{'cwe_ids': ['CWE-74'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-02T21:43:12Z', 'nvd_published_at': '2021-07-26T20:15:00Z'}
|
1.4.0
|
GHSA-cgfm-62j4-v4rf
|
2021-08-23T16:57:40Z
|
2021-08-25T14:44:17Z
| null |
['CVE-2021-37635']
|
Heap out of bounds access in sparse reduction operations
|
### Impact
The implementation of sparse reduction operations in TensorFlow can trigger accesses outside of bounds of heap allocated data:
```python
import tensorflow as tf
x = tf.SparseTensor(
indices=[[773, 773, 773], [773, 773, 773]],
values=[1, 1],
dense_shape=[337, 337, 337])
tf.sparse.reduce_sum(x, 1)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/a1bc56203f21a5a4995311825ffaba7a670d7747/tensorflow/core/kernels/sparse_reduce_op.cc#L217-L228) fails to validate that each reduction group does not overflow and that each corresponding index does not point to outside the bounds of the input tensor.
### Patches
We have patched the issue in GitHub commit [87158f43f05f2720a374f3e6d22a7aaa3a33f750](https://github.com/tensorflow/tensorflow/commit/87158f43f05f2720a374f3e6d22a7aaa3a33f750).
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-cgfm-62j4-v4rf'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37635'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/87158f43f05f2720a374f3e6d22a7aaa3a33f750'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T16:57:40Z', 'nvd_published_at': '2021-08-12T21:15:00Z'}
|
1.4.0
|
GHSA-4cww-f7w5-x525
|
2023-06-13T22:25:56Z
|
2021-08-25T20:46:13Z
| null |
['CVE-2020-35857']
|
Stack consumption in trust-dns-server
|
There's a stack overflow leading to a crash and potential DOS when processing additional records for return of MX or SRV record types from the server. This is only possible when a zone is configured with a null target for MX or SRV records. Prior to 0.16.0 the additional record processing was not supported by trust-dns-server. There Are no known issues with upgrading from 0.16 or 0.17 to 0.18.1. The remidy should be to upgrade to 0.18.1. If unable to do so, MX, SRV or other record types with a target to the null type, should be avoided.
|
[{'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': 'trust-dns-server'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.16.0'}, {'fixed': '0.18.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35857'}, {'type': 'WEB', 'url': 'https://github.com/bluejekyll/trust-dns/issues/980'}, {'type': 'PACKAGE', 'url': 'https://github.com/bluejekyll/trust-dns'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0001.html'}]
|
{'cwe_ids': ['CWE-400'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:20:03Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-mm4m-qg48-f7wc
|
2022-06-14T20:12:33Z
|
2021-08-25T21:01:29Z
| null |
['CVE-2020-13759']
|
Improper Synchronization and Race Condition in vm-memory
|
rust-vmm vm-memory before 0.1.1 and 0.2.x before 0.2.1 allows attackers to cause a denial of service (loss of IP networking) because read_obj and write_obj do not properly access memory. This affects aarch64 (with musl or glibc) and x86_64 (with musl).
|
[{'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': 'vm-memory'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.1.1'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'vm-memory'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.2.0'}, {'fixed': '0.2.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-13759'}, {'type': 'WEB', 'url': 'https://github.com/rust-vmm/vm-memory/issues/93'}, {'type': 'PACKAGE', 'url': 'https://github.com/rust-vmm/vm-memory'}, {'type': 'WEB', 'url': 'https://github.com/rust-vmm/vm-memory/releases/tag/v0.1.1'}, {'type': 'WEB', 'url': 'https://github.com/rust-vmm/vm-memory/releases/tag/v0.2.1'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0157.html'}]
|
{'cwe_ids': ['CWE-362', 'CWE-662'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-07-26T20:45:48Z', 'nvd_published_at': '2020-06-02T19:15:00Z'}
|
1.4.0
|
GHSA-f6px-w8rh-7r89
|
2023-09-15T17:59:24Z
|
2021-08-02T17:15:05Z
| null |
['CVE-2019-16354']
|
Beego has a file creation race condition
|
The File Session Manager in Beego 1.10.0 allows local users to read session files because there is a race condition involving file creation within a directory with weak permissions.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/beego/beego'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.12.2'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/astaxie/beego'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.12.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-16354'}, {'type': 'WEB', 'url': 'https://github.com/astaxie/beego/issues/3763'}, {'type': 'WEB', 'url': 'https://github.com/beego/beego/issues/3763'}, {'type': 'WEB', 'url': 'https://github.com/beego/beego/pull/3975'}, {'type': 'WEB', 'url': 'https://github.com/beego/beego/pull/3975/commits/f99cbe0fa40936f2f8dd28e70620c559b6e5e2fd'}, {'type': 'WEB', 'url': 'https://github.com/astaxie/beego/commit/f99cbe0fa40936f2f8dd28e70620c559b6e5e2fd'}, {'type': 'WEB', 'url': 'https://github.com/beego/beego/commit/bac2b31afecc65d9a89f9e473b8006c5edc0c8d1'}, {'type': 'PACKAGE', 'url': 'https://github.com/astaxie/beego'}, {'type': 'WEB', 'url': 'https://github.com/astaxie/beego/blob/v1.12.2/session/sess_file.go#L142'}, {'type': 'WEB', 'url': 'https://pkg.go.dev/vuln/GO-2021-0084'}]
|
{'cwe_ids': ['CWE-362', 'CWE-732'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-07-22T21:51:41Z', 'nvd_published_at': '2019-09-16T15:15:00Z'}
|
1.4.0
|
GHSA-3cgf-9m6x-pwwr
|
2021-08-19T21:08:22Z
|
2021-08-25T20:47:50Z
| null |
['CVE-2020-35868']
|
Data races in rusqlite
|
An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via UnlockNotification.
|
[{'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-35868'}, {'type': 'WEB', 'url': 'https://github.com/rusqlite/rusqlite/commit/45fd77ee43c38eea4d6f4e2e56c1667a55ec654f'}, {'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:22Z', 'nvd_published_at': '2020-12-31T10:15:00Z'}
|
1.4.0
|
GHSA-4x25-f45x-grv5
|
2021-08-10T16:54:25Z
|
2021-08-09T20:40:53Z
| null |
['CVE-2021-33900']
|
Missing encryption in Apache Directory Studio
|
While investigating DIRSTUDIO-1219 it was noticed that configured StartTLS encryption was not applied when any SASL authentication mechanism (DIGEST-MD5, GSSAPI) was used. While investigating DIRSTUDIO-1220 it was noticed that any configured SASL confidentiality layer was not applied. This issue affects Apache Directory Studio version 2.0.0.v20210213-M16 and prior versions.
|
[{'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': 'Maven', 'name': 'org.apache.directory.studio:org.apache.directory.studio.parent'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.0.0.v20210717-M17'}]}], 'database_specific': {'last_known_affected_version_range': '<= 2.0.0.v20210213-M16'}}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-33900'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rb1dbcc43a5b406e45d335343a1704f4233de613140a01929d102fdc9%40%3Cusers.directory.apache.org%3E'}]
|
{'cwe_ids': ['CWE-311', 'CWE-319'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-02T21:23:12Z', 'nvd_published_at': '2021-07-26T07:15:00Z'}
|
1.4.0
|
GHSA-vxf5-wxwp-m7g9
|
2022-04-28T20:32:19Z
|
2021-08-12T14:51:14Z
| null |
['CVE-2021-37699']
|
Open Redirect in Next.js
|
Next.js is an open source website development framework to be used with the React library. In affected versions specially encoded paths could be used when `pages/_error.js` was statically generated, allowing an open redirect to occur to an external site. In general, this redirect does not directly harm users although it can allow for phishing attacks by redirecting to an attacker's domain from a trusted domain.
### Impact
- **Affected:** Users of Next.js between `10.0.5` and `10.2.0`
- **Affected:** Users of Next.js between `11.0.0` and `11.0.1` using `pages/_error.js` without `getInitialProps`
- **Affected:** Users of Next.js between `11.0.0` and `11.0.1` using `pages/_error.js` and `next export`
- **Not affected**: Deployments on Vercel ([vercel.com](https://vercel.com)) are not affected
- **Not affected:** Deployments **with** `pages/404.js`
- Note that versions prior to 0.9.9 package `next` npm package hosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions.
We recommend upgrading to the latest version of Next.js to improve the overall security of your application.
### Patches
https://github.com/vercel/next.js/releases/tag/v11.1.0
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'next'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.9.9'}, {'fixed': '11.1.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/vercel/next.js/security/advisories/GHSA-vxf5-wxwp-m7g9'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37699'}, {'type': 'PACKAGE', 'url': 'https://github.com/vercel/next.js'}, {'type': 'WEB', 'url': 'https://github.com/vercel/next.js/releases/tag/v11.1.0'}]
|
{'cwe_ids': ['CWE-601'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-12T14:50:18Z', 'nvd_published_at': '2021-08-12T00:15:00Z'}
|
1.4.0
|
GHSA-9cg2-2j2h-59v9
|
2023-06-13T16:47:45Z
|
2021-08-25T20:49:11Z
| null |
['CVE-2020-35897']
|
Data races in atom
|
The atom crate contains a security issue revolving around its implementation of the Send trait. It incorrectly allows any arbitrary type to be sent across threads potentially leading to use-after-free issues through memory races.
|
[{'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': 'atom'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.3.6'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35897'}, {'type': 'WEB', 'url': 'https://github.com/slide-rs/atom/issues/13'}, {'type': 'PACKAGE', 'url': 'https://github.com/slide-rs/atom'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0044.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T20:53:48Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-phwj-86vx-cfjc
|
2021-07-09T01:55:01Z
|
2021-08-13T15:21:35Z
| null |
['CVE-2021-33192']
|
Cross-site scripting in Apache Jena Fuseki
|
A vulnerability in the HTML pages of Apache Jena Fuseki allows an attacker to execute arbitrary javascript on certain page views. This issue affects Apache Jena Fuseki from version 2.0.0 to version 4.0.0 (inclusive).
|
[{'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': 'Maven', 'name': 'org.apache.jena:jena-fuseki'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.0.0'}, {'fixed': '4.1.0'}]}], 'database_specific': {'last_known_affected_version_range': '<= 4.0.0'}}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-33192'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r684d8943d755a96fe90f8cd8df196737b6bde3f2b74e15a9bd479975%40%3Cusers.jena.apache.org%3E'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-07-06T15:42:15Z', 'nvd_published_at': '2021-07-05T10:15:00Z'}
|
1.4.0
|
GHSA-hp4c-x6r7-6555
|
2021-08-23T17:57:14Z
|
2021-08-25T14:44:14Z
| null |
['CVE-2021-37636']
|
Floating point exception in `SparseDenseCwiseDiv`
|
### Impact
The implementation of `tf.raw_ops.SparseDenseCwiseDiv` is vulnerable to a division by 0 error:
```python
import tensorflow as tf
import numpy as np
tf.raw_ops.SparseDenseCwiseDiv(
sp_indices=np.array([[4]]),
sp_values=np.array([-400]),
sp_shape=np.array([647.]),
dense=np.array([0]))
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/a1bc56203f21a5a4995311825ffaba7a670d7747/tensorflow/core/kernels/sparse_dense_binary_op_shared.cc#L56) 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 [d9204be9f49520cdaaeb2541d1dc5187b23f31d9](https://github.com/tensorflow/tensorflow/commit/d9204be9f49520cdaaeb2541d1dc5187b23f31d9).
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-hp4c-x6r7-6555'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37636'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/d9204be9f49520cdaaeb2541d1dc5187b23f31d9'}]
|
{'cwe_ids': ['CWE-369'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T17:57:14Z', 'nvd_published_at': '2021-08-12T18:15:00Z'}
|
1.4.0
|
GHSA-fjr6-hm39-4cf9
|
2021-08-19T18:46:23Z
|
2021-08-25T20:52:50Z
| null |
['CVE-2021-25906']
|
Double free in basic_dsp_matrix
|
An issue was discovered in the basic_dsp_matrix crate before 0.9.2 for Rust. When a TransformContent panic occurs, a double drop can be performed.
|
[{'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': 'basic_dsp_matrix'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.9.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-25906'}, {'type': 'WEB', 'url': 'https://github.com/liebharc/basic_dsp/issues/47'}, {'type': 'PACKAGE', 'url': 'https://github.com/liebharc/basic_dsp'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0009.html'}]
|
{'cwe_ids': ['CWE-415'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:46:23Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-45p7-c959-rgcm
|
2021-08-02T21:57:02Z
|
2021-08-25T21:01:18Z
| null |
[]
|
Process crashes when the cell used as DepGroup is not alive
|
### Impact
It's easy to create a malign transaction which uses the dead cell as the DepGroup in the DepCells. The transaction can crash all the receiving nodes.
|
[]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'ckb'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.40.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/nervosnetwork/ckb/security/advisories/GHSA-45p7-c959-rgcm'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0109.html'}]
|
{'cwe_ids': [], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-02T21:57:02Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-3393-hvrj-w7v3
|
2021-08-02T19:21:25Z
|
2021-08-09T20:41:17Z
| null |
['CVE-2021-22144']
|
Denial of Service in Elasticsearch
|
In Elasticsearch versions before 7.13.3 and 6.8.17 an uncontrolled recursion vulnerability that could lead to a denial of service attack was identified in the Elasticsearch Grok parser. A user with the ability to submit arbitrary queries to Elasticsearch could create a malicious Grok query that will crash the Elasticsearch node.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.elasticsearch:elasticsearch'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.8.17'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.elasticsearch:elasticsearch'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '7.0.0-alpha1'}, {'fixed': '7.13.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-22144'}, {'type': 'WEB', 'url': 'https://discuss.elastic.co/t/elasticsearch-7-13-3-and-6-8-17-security-update/278100'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20210827-0006/'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuapr2022.html'}]
|
{'cwe_ids': ['CWE-674'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-02T19:21:25Z', 'nvd_published_at': '2021-07-26T12:15:00Z'}
|
1.4.0
|
GHSA-4xj5-vv9x-63jp
|
2021-08-19T18:56:22Z
|
2021-08-25T20:50:22Z
| null |
['CVE-2020-35928']
|
Data races in concread
|
An issue was discovered in the concread crate before 0.2.6 for Rust. Attackers can cause an ARCache<K,V> data race by sending types that do not implement Send/Sync.
|
[{'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': 'concread'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.2.6'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35928'}, {'type': 'WEB', 'url': 'https://github.com/kanidm/concread/issues/48'}, {'type': 'PACKAGE', 'url': 'https://github.com/kanidm/concread'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0092.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:56:11Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-cx4j-fxr7-jxg8
|
2023-06-13T18:09:24Z
|
2021-08-25T20:53:01Z
| null |
['CVE-2021-25902']
|
Double free in glsl-layout
|
Affected versions of this crate did not guard against panic within the user-provided function f (2nd parameter of fn map_array), and thus panic within f causes double drop of a single object.
The flaw was corrected in the 0.4.0 release by wrapping the object vulnerable to a double drop within ManuallyDrop<T>.
|
[{'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': 'glsl-layout'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-25902'}, {'type': 'WEB', 'url': 'https://github.com/rustgd/glsl-layout/pull/10'}, {'type': 'PACKAGE', 'url': 'https://github.com/rustgd/glsl-layout'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0005.html'}]
|
{'cwe_ids': ['CWE-415'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:43:30Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-hwvq-6gjx-j797
|
2022-01-18T23:01:35Z
|
2021-08-23T19:40:38Z
| null |
['CVE-2021-32798']
|
Special Element Injection in notebook
|
### Impact
Untrusted notebook can execute code on load. This is a remote code execution, but requires user action to open a notebook.
### Patches
5.7.11, 6.4.1
### References
[OWASP Page on Injection Prevention](https://cheatsheetseries.owasp.org/cheatsheets/Injection_Prevention_Cheat_Sheet.html#injection-prevention-rules)
### For more information
If you have any questions or comments about this advisory, or vulnerabilities to report, please email our security list security@ipython.org.
Credit: Guillaume Jeanne from Google
### Example:
A notebook with the following content in a cell and it would display an alert when opened for the first time in Notebook (in an untrusted state):
```
{ "cell_type": "code", "execution_count": 0, "metadata": {}, "outputs": [ { "data": { "text/html": [ "<select><iframe></select><img src=x: onerror=alert('xss')>\n"], "text/plain": [] }, "metadata": {}, "output_type": "display_data" } ], "source": [ "" ] }
````
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'notebook'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '5.7.11'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'notebook'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '6.0.0'}, {'fixed': '6.4.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/jupyter/notebook/security/advisories/GHSA-hwvq-6gjx-j797'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-32798'}, {'type': 'WEB', 'url': 'https://github.com/jupyter/notebook/commit/79fc76e890a8ec42f73a3d009e44ef84c14ef0d5'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T16:44:43Z', 'nvd_published_at': '2021-08-09T21:15:00Z'}
|
1.4.0
|
GHSA-prqf-xr2j-xf65
|
2021-08-23T17:05:11Z
|
2021-08-23T19:41:41Z
| null |
[]
|
Potential privilege escalation on Kubernetes >= v1.19 when the Argo Sever is run with `--auth-mode=client`
|
### Impact
This is pro-active fix. No know exploits exist.
Impacted:
* You're running Kubernetes >= v1.19
* You're running Argo Server
* It is configured to with `--auth-mode=client`
* Is not configured with `--auth-mode=server`
* You are not running Argo Server in Kubernetes pod. E.g. on bare metal or other VM.
* You're using client key to authenticate on the server.
* The server has more permissions that the connecting client's account.
The client's authentication will be ignored and the server's authentication will be used. This will result in privilege escalation to that of the the server's account.
### Patches
https://github.com/argoproj/argo-workflows/pull/6506
### Workarounds
None.
|
[]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/argoproj/argo-workflows/v3'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.0.0'}, {'fixed': '3.0.9'}]}]}, {'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-prqf-xr2j-xf65'}]
|
{'cwe_ids': ['CWE-285'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T17:05:11Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-mp6f-p9gp-vpj9
|
2022-06-14T20:54:51Z
|
2021-08-25T20:46:06Z
| null |
['CVE-2020-25792']
|
Array size is not checked in sized-chunks
|
An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with pair().
|
[{'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-25792'}, {'type': 'WEB', 'url': 'https://github.com/bodil/sized-chunks/issues/11'}, {'type': 'PACKAGE', 'url': 'https://github.com/bodil/sized-chunks'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0041.html'}]
|
{'cwe_ids': ['CWE-129'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:20:31Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-773q-5334-5gf9
|
2021-08-18T21:38:27Z
|
2021-08-25T20:55:36Z
| null |
[]
|
Memory over-allocation in evm-core
|
Prior to the patch, when executing specific EVM opcodes related
to memory operations that use `evm_core::Memory::copy_large`, the
crate can over-allocate memory when it is not needed, making it
possible for an attacker to perform denial-of-service attack.
The flaw was corrected in commit `19ade85`.
|
[]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'evm-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.26.0'}, {'fixed': '0.26.1'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'evm-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.25.0'}, {'fixed': '0.25.1'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'evm-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.24.0'}, {'fixed': '0.24.1'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'evm-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.23.0'}, {'fixed': '0.23.1'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'evm-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.21.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/rust-blockchain/evm/commit/19ade85'}, {'type': 'PACKAGE', 'url': 'https://github.com/rust-blockchain/evm'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0066.html'}]
|
{'cwe_ids': ['CWE-789'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T21:38:27Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-jh2g-xhqq-x4w9
|
2021-08-24T17:52:52Z
|
2021-08-25T21:00:07Z
|
2021-08-24T17:52:52Z
|
[]
|
Send/Sync bound needed on T for Send/Sync impl of RcuCell<T>
|
Affected versions of this crate unconditionally implement Send/Sync for `RcuCell<T>`.
This allows users to send `T: !Send` to other threads (while `T` enclosed within `RcuCell<T>`), and allows users to concurrently access `T: !Sync` by using the APIs of `RcuCell<T>` that provide access to `&T`.
This can result in memory corruption caused by data races.
|
[]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'rcu_cell'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.1.9'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/Xudong-Huang/rcu_cell/issues/3'}, {'type': 'WEB', 'url': 'https://github.com/Xudong-Huang/rcu_cell/pull/4/commits/1faf18eee11f14969b77ae0f76dcd9ebd437d0c2'}, {'type': 'PACKAGE', 'url': 'https://github.com/Xudong-Huang/rcu_cell'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0131.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-06T20:11:31Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-8928-2fgm-6x9x
|
2021-08-18T20:13:40Z
|
2021-08-25T20:58:21Z
| null |
['CVE-2021-38512']
|
HTTP Request Smuggling in actix-http
|
Affected versions of this crate did not properly detect invalid requests that could allow HTTP/1 request smuggling (HRS) attacks when running alongside a vulnerable front-end proxy server. This can result in leaked internal and/or user data, including credentials, when the front-end proxy is also vulnerable.
Popular front-end proxies and load balancers already mitigate HRS attacks so it is recommended that they are also kept up to date; check your specific set up. You should upgrade even if the front-end proxy receives exclusively HTTP/2 traffic and connects to the back-end using HTTP/1; several downgrade attacks are known that can also expose HRS vulnerabilities.
|
[{'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': 'actix-http'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.2.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-38512'}, {'type': 'WEB', 'url': 'https://github.com/actix/actix-web/pull/2363'}, {'type': 'WEB', 'url': 'https://github.com/actix/actix-web/commit/e965d8298f421e9c89fe98b1300b8361e948c324'}, {'type': 'PACKAGE', 'url': 'https://github.com/actix/actix-web'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/67URRW4K47SR6LNQB4YALPLGGQMQK7HO/'}, {'type': 'WEB', 'url': 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/actix-http/RUSTSEC-2021-0081.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0081.html'}]
|
{'cwe_ids': ['CWE-444'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T20:13:40Z', 'nvd_published_at': '2021-08-10T23:15:00Z'}
|
1.4.0
|
GHSA-8c6g-4xc5-w96c
|
2023-06-13T16:57:24Z
|
2021-08-25T20:43:52Z
| null |
['CVE-2018-20992']
|
Uninitialized memory exposure in claxon
|
Affected versions of Claxon made an invalid assumption about the decode buffer size being a multiple of a value read from the bitstream. This could cause parts of the decode buffer to not be overwritten. If the decode buffer was newly allocated and uninitialized, this uninitialized memory could be exposed.
This allows an attacker to observe parts of the uninitialized memory in the decoded audio stream.
The flaw was corrected by checking that the value read from the bitstream divides the decode buffer size, and returning a format error if it does not. If an error is returned, the decode buffer is not exposed. Regression tests and an additional fuzzer have been added to prevent similar flaws in the future.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'claxon'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.4.0'}, {'fixed': '0.4.1'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'claxon'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.3.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2018-20992'}, {'type': 'WEB', 'url': 'https://github.com/ruuda/claxon/commit/8f28ec275e412dd3af4f3cda460605512faf332c'}, {'type': 'PACKAGE', 'url': 'https://github.com/ruuda/claxon'}, {'type': 'WEB', 'url': 'https://github.com/ruuda/claxon/releases/tag/v0.3.2'}, {'type': 'WEB', 'url': 'https://github.com/ruuda/claxon/releases/tag/v0.4.1'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2018-0004.html'}]
|
{'cwe_ids': ['CWE-908'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:24:16Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-m3ww-7hrp-gw9w
|
2023-06-13T19:52:17Z
|
2021-08-25T20:47:41Z
| null |
['CVE-2020-35878']
|
Drop of uninitialized memory in Ozone
|
An issue was discovered in the ozone crate through version 0.1.0 for Rust. Memory safety is violated because of the dropping of uninitialized memory.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'ozone'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.1.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35878'}, {'type': 'PACKAGE', 'url': 'https://github.com/bqv/ozone'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0022.html'}]
|
{'cwe_ids': ['CWE-119', 'CWE-908'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:08:59Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-rccq-j2m7-8fwr
|
2023-06-13T18:19:30Z
|
2021-08-25T20:55:14Z
| null |
['CVE-2021-30457']
|
Double-free in id-map
|
A double free can occur in remove_set upon a panic in a Drop impl. When removing a set of elements, ptr::drop_in_place is called on each of the element to be removed. If the Drop impl of one of these elements panics then the previously dropped elements can be dropped again.
|
[{'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': 'id-map'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.2.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-30457'}, {'type': 'WEB', 'url': 'https://github.com/andrewhickman/id-map/issues/3'}, {'type': 'PACKAGE', 'url': 'https://github.com/andrewhickman/id-map'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0052.html'}]
|
{'cwe_ids': ['CWE-415'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:04:15Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-vfqx-hv88-f9cv
|
2023-06-13T18:19:49Z
|
2021-08-25T20:55:22Z
| null |
['CVE-2021-30456']
|
Double-free in id-map
|
A double free can occur in get_or_insert upon a panic of a user-provided f function. get_or_insert reserves space for a value, before calling the user provided insertion function f. If the function f panics then uninitialized or previously freed memory can be dropped.
|
[{'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': 'id-map'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.2.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-30456'}, {'type': 'WEB', 'url': 'https://github.com/andrewhickman/id-map/issues/3'}, {'type': 'PACKAGE', 'url': 'https://github.com/andrewhickman/id-map'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0052.html'}]
|
{'cwe_ids': ['CWE-415'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:04:13Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-gx73-2498-r55c
|
2023-06-13T17:17:49Z
|
2021-08-25T20:46:49Z
| null |
['CVE-2019-25004']
|
Unsound casting in flatbuffers
|
The implementation of impl Follow for bool allows to reinterpret arbitrary bytes as a bool.
In Rust bool has stringent requirements for its in-memory representation. Use of this function allows to violate these requirements and invoke undefined behaviour in safe 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': 'flatbuffers'}, 'ecosystem_specific': {'affected_functions': ['flatbuffers::Follow::follow']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.4.0'}, {'fixed': '0.6.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-25004'}, {'type': 'WEB', 'url': 'https://github.com/google/flatbuffers/issues/5530'}, {'type': 'PACKAGE', 'url': 'https://github.com/google/flatbuffers'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0028.html'}]
|
{'cwe_ids': ['CWE-704'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:19:36Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-ghpq-vjxw-ch5w
|
2021-08-18T20:41:10Z
|
2021-08-25T20:56:52Z
| null |
[]
|
Use after free in libpulse-binding
|
### Overview
Version 1.2.1 of the `libpulse-binding` Rust crate, released on the 15th of June 2018, fixed a pair of use-after-free issues with the objects returned by the `get_format_info` and `get_context` methods of `Stream` objects. These objects were mistakenly being constructed without setting an important flag to prevent destruction of the underlying C objects they reference upon their own destruction.
This advisory is being written retrospectively, having previously only been noted in the changelog. No CVE assignment was sought.
### Patches
Users are required to update to version 1.2.1 or newer.
Versions older than 1.2.1 have been yanked from crates.io. This was believed to have already been done at the time of the 1.2.1 release, but upon double checking now they were found to still be available, so has been done now (22nd October 2020).
|
[]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'libpulse-binding'}, 'ecosystem_specific': {'affected_functions': ['libpulse_binding::stream::Stream::get_context', 'libpulse_binding::stream::Stream::get_format_info']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.2.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/jnqnfe/pulse-binding-rust/security/advisories/GHSA-ghpq-vjxw-ch5w'}, {'type': 'PACKAGE', 'url': 'https://github.com/jnqnfe/pulse-binding-rust'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2018-0021.html'}]
|
{'cwe_ids': ['CWE-416'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T20:41:10Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-pp74-39w2-v4w9
|
2023-04-03T19:13:35Z
|
2021-08-25T21:01:44Z
| null |
['CVE-2021-31154']
|
Permissions bypass in pleaser
|
pleaseedit in pleaser before 0.4.0 uses predictable temporary filenames in /tmp and the target directory. This allows a local attacker to gain full root privileges by staging a symlink attack.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'pleaser'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-31154'}, {'type': 'WEB', 'url': 'https://crates.io/crates/pleaser'}, {'type': 'WEB', 'url': 'https://gitlab.com/edneville/please'}, {'type': 'WEB', 'url': 'https://gitlab.com/edneville/please/-/tree/master/src/bin'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0102.html'}, {'type': 'WEB', 'url': 'https://www.openwall.com/lists/oss-security/2021/05/18/1'}]
|
{'cwe_ids': ['CWE-340', 'CWE-59'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-06-01T19:34:12Z', 'nvd_published_at': '2021-05-27T13:15:00Z'}
|
1.4.0
|
GHSA-q3m9-9fj2-mfwr
|
2021-08-30T23:21:07Z
|
2021-08-05T17:02:12Z
| null |
['CVE-2021-32806']
|
URL Redirection to Untrusted Site ('Open Redirect') in Products.isurlinportal
|
### Impact
Various parts of Plone use the 'is url in portal' check for security, mostly to see if it is safe to redirect to a url. A url like `https://example.org` is not in the portal.
But the url `https:example.org` without slashes tricks our code and it _is_ considered to be in the portal.
When redirecting, some browsers go to `https://example.org`, others give an error.
Attackers may use this to redirect you to their site, especially as part of a phishing attack.
### Patches
The problem has been patched in `Products.isurlinportal` 1.2.0.
This is a recommended upgrade for all users of Plone 4.3 and 5, on Python 2.7 or higher.
It has not been tested on earlier Plone or Python versions.
Upcoming Plone 5.2.5 and higher will include the new version.
### Discovered
This vulnerability was discovered and reported by Yuji Tounai of Mitsui Bussan Secure Directions, Inc. Thank you!
### For more information
If you have any questions or comments about this advisory:
* Email the Plone Security Team at [security@plone.org](mailto:security@plone.org), especially when you think you have discovered a security problem or when you are not sure.
* Open an issue in [the tracker](https://github.com/plone/Products.isurlinportal/issues) if your question or comment can be public.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'Products.isurlinportal'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.2.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/plone/Products.isurlinportal/security/advisories/GHSA-q3m9-9fj2-mfwr'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-32806'}, {'type': 'WEB', 'url': 'https://github.com/plone/Products.isurlinportal/commit/d4fd34990d18adf05a10dc5e2bb4b066798280ba'}, {'type': 'PACKAGE', 'url': 'https://github.com/plone/Products.isurlinportal'}, {'type': 'WEB', 'url': 'http://jvn.jp/en/jp/JVN50804280/index.html'}]
|
{'cwe_ids': ['CWE-601'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-02T23:19:30Z', 'nvd_published_at': '2021-08-02T19:15:00Z'}
|
1.4.0
|
GHSA-x3v2-fgr6-3wmm
|
2021-08-19T18:40:57Z
|
2021-08-25T20:53:03Z
| null |
['CVE-2021-25908']
|
Double free in fil-ocl
|
An issue was discovered in the fil-ocl crate through 2021-01-04 for Rust. From<EventList> can lead to a 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': 'fil-ocl'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.12.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-25908'}, {'type': 'WEB', 'url': 'https://github.com/cogciprocate/ocl/issues/194'}, {'type': 'PACKAGE', 'url': 'https://github.com/filecoin-project/fil-ocl'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0011.html'}]
|
{'cwe_ids': ['CWE-415'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:40:57Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-5xwc-mrhx-5g3m
|
2021-08-24T13:10:06Z
|
2021-08-25T14:42:52Z
| null |
['CVE-2021-37657']
|
Reference binding to nullptr in `MatrixDiagV*` ops
|
### Impact
An attacker can cause undefined behavior via binding a reference to null pointer in all operations of type `tf.raw_ops.MatrixDiagV*`:
```python
import tensorflow as tf
tf.raw_ops.MatrixDiagV3(
diagonal=[1,0],
k=[],
num_rows=[1,2,3],
num_cols=[4,5],
padding_value=[],
align='RIGHT_RIGHT')
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/linalg/matrix_diag_op.cc) has incomplete validation that the value of `k` is a valid tensor. We have check that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong:
```cc
auto& diag_index = context->input(1);
...
lower_diag_index = diag_index.flat<int32>()(0);
```
### Patches
We have patched the issue in GitHub commit [f2a673bd34f0d64b8e40a551ac78989d16daad09](https://github.com/tensorflow/tensorflow/commit/f2a673bd34f0d64b8e40a551ac78989d16daad09).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-5xwc-mrhx-5g3m'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37657'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/f2a673bd34f0d64b8e40a551ac78989d16daad09'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-824'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T13:10:06Z', 'nvd_published_at': '2021-08-12T21:15:00Z'}
|
1.4.0
|
GHSA-69vj-xx27-g45w
|
2023-06-13T18:12:42Z
|
2021-08-25T20:51:49Z
| null |
['CVE-2020-36216']
|
Data race in eventio
|
Input<R> implements Send without requiring R: Send.
Affected versions of this crate allows users to send non-Send types to other threads, which can lead to undefined behavior such as data race and memory corruption.
The flaw was corrected in version 0.5.1 by adding R: Send bound to the Send impl of Input<R>.
|
[{'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': 'eventio'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.5.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36216'}, {'type': 'WEB', 'url': 'https://github.com/petabi/eventio/issues/33'}, {'type': 'PACKAGE', 'url': 'https://github.com/petabi/eventio'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0108.html'}]
|
{'cwe_ids': ['CWE-662', 'CWE-787'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:47:45Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-8xw8-mmqv-frqq
|
2021-08-18T21:41:18Z
|
2021-08-25T20:55:33Z
| null |
[]
|
fake-static allows converting any reference into a `'static` reference
|
fake-static allows converting a reference with any lifetime into
a reference with `'static` lifetime without the `unsafe` keyword.
Internally, this crate does not use unsafe code, it instead
exploits a soundness bug in rustc
|
[]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'fake-static'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.1.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/rust-lang/rust/issues/25860'}, {'type': 'PACKAGE', 'url': 'https://github.com/NieDzejkob/fake-static'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0013.html'}]
|
{'cwe_ids': ['CWE-657'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T21:41:18Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-gf88-j2mg-cc82
|
2021-08-24T13:23:52Z
|
2021-08-25T14:42:28Z
| null |
['CVE-2021-37661']
|
Crash caused by integer conversion to unsigned
|
### Impact
An attacker can cause a denial of service in `boosted_trees_create_quantile_stream_resource` by using negative arguments:
```python
import tensorflow as tf
from tensorflow.python.ops import gen_boosted_trees_ops
import numpy as np
v= tf.Variable([0.0, 0.0, 0.0, 0.0, 0.0])
gen_boosted_trees_ops.boosted_trees_create_quantile_stream_resource(
quantile_stream_resource_handle = v.handle,
epsilon = [74.82224],
num_streams = [-49],
max_elements = np.int32(586))
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantile_ops.cc#L96) does not validate that `num_streams` only contains non-negative numbers. In turn, [this results in using this value to allocate memory](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantiles/quantile_stream_resource.h#L31-L40):
```cc
class BoostedTreesQuantileStreamResource : public ResourceBase {
public:
BoostedTreesQuantileStreamResource(const float epsilon,
const int64 max_elements,
const int64 num_streams)
: are_buckets_ready_(false),
epsilon_(epsilon),
num_streams_(num_streams),
max_elements_(max_elements) {
streams_.reserve(num_streams_);
...
}
}
```
However, `reserve` receives an unsigned integer so there is an implicit conversion from a negative value to a large positive unsigned. This results in a crash from the standard library.
### Patches
We have patched the issue in GitHub commit [8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992](https://github.com/tensorflow/tensorflow/commit/8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992).
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-gf88-j2mg-cc82'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37661'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-681'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T13:23:52Z', 'nvd_published_at': '2021-08-12T21:15:00Z'}
|
1.4.0
|
GHSA-wq8f-46ww-6c2h
|
2023-06-13T22:27:01Z
|
2021-08-25T20:43:49Z
| null |
['CVE-2018-20989']
|
Integer underflow in untrusted
|
A mistake in error handling in untrusted before 0.6.2 could lead to an integer underflow and panic if a user of the crate didn't properly check for errors returned by untrusted. Combination of these two programming errors (one in untrusted and another by user of this crate) could lead to a panic and maybe a denial of service of affected software. The error in untrusted is fixed in release 0.6.2 released 2018-06-21. It's also advisable that users of untrusted check for their sources for cases where errors returned by untrusted are not handled correctly.
|
[{'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': 'untrusted'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.6.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2018-20989'}, {'type': 'WEB', 'url': 'https://github.com/briansmith/untrusted/pull/20'}, {'type': 'PACKAGE', 'url': 'https://github.com/briansmith/untrusted'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2018-0001.html'}]
|
{'cwe_ids': ['CWE-191'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:24:20Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-hph2-m3g5-xxv4
|
2022-02-08T20:44:04Z
|
2021-08-25T14:47:09Z
| null |
['CVE-2021-39151']
|
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-39151](https://x-stream.github.io/CVE-2021-39151.html).
### Credits
Smi1e of DBAPPSecurity WEBIN Lab 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-hph2-m3g5-xxv4'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39151'}, {'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-39151.html'}]
|
{'cwe_ids': ['CWE-434', 'CWE-502'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T18:22:27Z', 'nvd_published_at': '2021-08-23T18:15:00Z'}
|
1.4.0
|
GHSA-vcjj-9vg7-vf68
|
2021-08-24T17:57:25Z
|
2021-08-25T14:39:54Z
| null |
['CVE-2021-37688']
|
Null pointer dereference in TFLite
|
### 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:
```python
import tensorflow as tf
model = tf.keras.models.Sequential()
model.add(tf.keras.Input(shape=(1, 2, 3)))
model.add(tf.keras.layers.Dense(0, activation='relu'))
converter = tf.lite.TFLiteConverter.from_keras_model(model)
tflite_model = converter.convert()
interpreter = tf.lite.Interpreter(model_content=tflite_model)
interpreter.allocate_tensors()
interpreter.invoke()
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/internal/optimized/optimized_ops.h#L268-L285) unconditionally dereferences a pointer.
```cc
if (y4 > 1) {
// ...
} else {
for (int i0 = 0; i0 < y0; ++i0) {
const T* input2_data_ptr = nullptr;
for (int i1 = 0; i1 < y1; ++i1) {
input2_data_ptr = input2_data_reset;
for (int i2 = 0; i2 < y2; ++i2) {
scalar_broadcast_f(y3, params, *input1_data_ptr, input2_data_ptr,
output_data_ptr);
}
}
}
}
```
### Patches
We have patched the issue in GitHub commit [15691e456c7dc9bd6be203b09765b063bf4a380c](https://github.com/tensorflow/tensorflow/commit/15691e456c7dc9bd6be203b09765b063bf4a380c).
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-vcjj-9vg7-vf68'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37688'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/15691e456c7dc9bd6be203b09765b063bf4a380c'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow/'}]
|
{'cwe_ids': ['CWE-476'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T17:57:25Z', 'nvd_published_at': '2021-08-12T22:15:00Z'}
|
1.4.0
|
GHSA-352p-rhvq-7g78
|
2021-08-19T18:45:49Z
|
2021-08-25T20:52:55Z
| null |
['CVE-2021-25904']
|
Null pointer deference in av-data
|
An issue was discovered in the av-data crate before 0.3.0 for Rust. A raw pointer is dereferenced, leading to a read of an arbitrary memory address, sometimes causing a segfault.
|
[{'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': 'av-data'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.3.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-25904'}, {'type': 'WEB', 'url': 'https://github.com/rust-av/rust-av/issues/136'}, {'type': 'PACKAGE', 'url': 'https://github.com/rust-av/rust-av'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0007.html'}]
|
{'cwe_ids': ['CWE-476'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:45:49Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-8rc5-mr4f-m243
|
2021-08-19T21:18:55Z
|
2021-08-25T20:46:57Z
| null |
['CVE-2020-35876']
|
Use after free in rio
|
An issue was discovered in the rio crate through 2020-05-11 for Rust. A struct can be leaked, allowing attackers to obtain sensitive information, cause a use-after-free, or cause a data race.
|
[{'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': 'rio'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.9.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35876'}, {'type': 'WEB', 'url': 'https://github.com/spacejam/rio/issues/11'}, {'type': 'WEB', 'url': 'https://github.com/spacejam/rio/pull/31'}, {'type': 'PACKAGE', 'url': 'https://github.com/spacejam/rio'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0021.html'}]
|
{'cwe_ids': ['CWE-416', 'CWE-772'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:18:55Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-hc92-9h3m-c39j
|
2021-08-18T21:32:29Z
|
2021-08-25T20:55:45Z
| null |
['CVE-2021-38187']
|
Incorrect cast in anymap
|
An issue was discovered in the anymap crate through 0.12.1 for Rust. It violates soundness via conversion of a *u8 to a *u64.
|
[{'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': 'anymap'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.12.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-38187'}, {'type': 'WEB', 'url': 'https://github.com/chris-morgan/anymap/issues/37'}, {'type': 'PACKAGE', 'url': 'https://github.com/chris-morgan/anymap'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0065.html'}]
|
{'cwe_ids': ['CWE-681', 'CWE-704'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T21:32:29Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-q3cc-7p7g-392c
|
2021-08-19T21:08:56Z
|
2021-08-25T20:47:43Z
| null |
['CVE-2020-35873']
|
Use after free in rusqlite
|
An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated because sessions.rs has a use-after-free.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': '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-35873'}, {'type': 'WEB', 'url': 'https://github.com/rusqlite/rusqlite/commit/ac30e169ae51b262bc8cf7026469851ce39b23c6'}, {'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-416'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:08:56Z', 'nvd_published_at': '2020-12-31T10:15:00Z'}
|
1.4.0
|
GHSA-83r8-p8v6-6gfm
|
2022-06-14T20:53:20Z
|
2021-08-25T21:00:20Z
| null |
[]
|
Slock<T> allows sending non-Send types across thread boundaries
|
`Slock<T>` unconditionally implements `Send`/`Sync`.
Affected versions of this crate allows sending non-Send types to other threads,
which can lead to data races and memory corruption due to the 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': 'slock'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.2.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/BrokenLamp/slock-rs/issues/2'}, {'type': 'PACKAGE', 'url': 'https://github.com/BrokenLamp/slock-rs'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0135.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-06T17:28:42Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-r2mj-8wgq-73m6
|
2021-08-31T21:14:36Z
|
2021-08-09T20:43:14Z
| null |
['CVE-2021-23418']
|
XML External Entity Reference in Glances
|
The package glances before 3.2.1 are vulnerable to XML External Entity (XXE) Injection via the use of Fault to parse untrusted XML data, which is known to be vulnerable to XML attacks.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'Glances'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.2.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-23418'}, {'type': 'WEB', 'url': 'https://github.com/nicolargo/glances/issues/1025'}, {'type': 'WEB', 'url': 'https://github.com/nicolargo/glances/commit/4b87e979afdc06d98ed1b48da31e69eaa3a9fb94'}, {'type': 'WEB', 'url': 'https://github.com/nicolargo/glances/commit/85d5a6b4af31fcf785d5a61086cbbd166b40b07a'}, {'type': 'WEB', 'url': 'https://github.com/nicolargo/glances/commit/9d6051be4a42f692392049fdbfc85d5dfa458b32'}, {'type': 'PACKAGE', 'url': 'https://github.com/nicolargo/glances'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-PYTHON-GLANCES-1311807'}]
|
{'cwe_ids': ['CWE-611'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-02T18:18:37Z', 'nvd_published_at': '2021-07-29T18:15:00Z'}
|
1.4.0
|
GHSA-x67x-vg9m-65c3
|
2021-08-19T17:02:46Z
|
2021-08-25T20:55:27Z
| null |
['CVE-2017-1000430']
|
Integer overflow in base64
|
Affected versions of this crate suffered from an integer overflow bug when
calculating the size of a buffer to use when encoding base64 using the
`encode_config_buf` and `encode_config` functions. If the input string
was large, this would cause a buffer to be allocated that was too small.
Since this function writes to the buffer using unsafe code, it would
allow an attacker to write beyond the buffer, causing memory corruption
and possibly the execution of arbitrary code.
This flaw was corrected by using checked arithmetic to calculate
the size of the buffer.
|
[{'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': 'base64'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.5.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2017-1000430'}, {'type': 'WEB', 'url': 'https://github.com/alicemaz/rust-base64/commit/24ead980daf11ba563e4fb2516187a56a71ad319'}, {'type': 'PACKAGE', 'url': 'https://github.com/alicemaz/rust-base64'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2017-0004.html'}]
|
{'cwe_ids': ['CWE-119'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:02:46Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-f5cx-5wr3-5qrc
|
2021-08-24T13:33:26Z
|
2021-08-25T14:42:26Z
| null |
['CVE-2021-37662']
|
Reference binding to nullptr in boosted trees
|
### Impact
An attacker can generate undefined behavior via a reference binding to nullptr in `BoostedTreesCalculateBestGainsPerFeature`:
```python
import tensorflow as tf
tf.raw_ops.BoostedTreesCalculateBestGainsPerFeature(
node_id_range=[],
stats_summary_list=[[1,2,3]],
l1=[1.0],
l2=[1.0],
tree_complexity =[1.0],
min_node_weight =[1.17],
max_splits=5)
```
A similar attack can occur in `BoostedTreesCalculateBestFeatureSplitV2`:
```python
import tensorflow as tf
tf.raw_ops.BoostedTreesCalculateBestFeatureSplitV2(
node_id_range=[],
stats_summaries_list=[[1,2,3]],
split_types=[''],
candidate_feature_ids=[1,2,3,4],
l1=[1],
l2=[1],
tree_complexity=[1.0],
min_node_weight=[1.17],
logits_dimension=5)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) does not validate the input values.
### Patches
We have patched the issue in GitHub commit [9c87c32c710d0b5b53dc6fd3bfde4046e1f7a5ad](https://github.com/tensorflow/tensorflow/commit/9c87c32c710d0b5b53dc6fd3bfde4046e1f7a5ad) and in commit. [429f009d2b2c09028647dd4bb7b3f6f414bbaad7](https://github.com/tensorflow/tensorflow/commit/429f009d2b2c09028647dd4bb7b3f6f414bbaad7).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-f5cx-5wr3-5qrc'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37662'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/429f009d2b2c09028647dd4bb7b3f6f414bbaad7'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/9c87c32c710d0b5b53dc6fd3bfde4046e1f7a5ad'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-824'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T13:33:26Z', 'nvd_published_at': '2021-08-12T21:15:00Z'}
|
1.4.0
|
GHSA-qhxh-9hhx-6p7v
|
2021-07-26T17:47:03Z
|
2021-08-02T16:59:35Z
| null |
['CVE-2021-23408']
|
Prototype Pollution in GraphHopper
|
This affects the package `com.graphhopper:graphhopper-web-bundle` before 3.2, from 4.0-pre1 and before 4.0. The URL parser could be tricked into adding or modifying properties of Object.prototype using a constructor or __proto__ payload.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'com.graphhopper:graphhopper-web-bundle'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-23408'}, {'type': 'WEB', 'url': 'https://github.com/graphhopper/graphhopper/pull/2370'}, {'type': 'WEB', 'url': 'https://github.com/graphhopper/graphhopper/releases/tag/3.1'}, {'type': 'WEB', 'url': 'https://github.com/graphhopper/graphhopper/releases/tag/3.2'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JAVA-COMGRAPHHOPPER-1320114'}]
|
{'cwe_ids': ['CWE-1321'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-07-26T17:47:03Z', 'nvd_published_at': '2021-07-21T16:15:00Z'}
|
1.4.0
|
GHSA-4vww-mc66-62m6
|
2022-02-08T21:20:44Z
|
2021-08-13T15:21:14Z
| null |
['CVE-2021-33037']
|
HTTP Request Smuggling in Apache Tomcat
|
Apache Tomcat 10.0.0-M1 to 10.0.6, 9.0.0.M1 to 9.0.46 and 8.5.0 to 8.5.66 did not correctly parse the HTTP transfer-encoding request header in some circumstances leading to the possibility to request smuggling when used with a reverse proxy. Specifically: - Tomcat incorrectly ignored the transfer encoding header if the client declared it would only accept an HTTP/1.0 response; - Tomcat honoured the identify encoding; and - Tomcat did not ensure that, if present, the chunked encoding was the final encoding.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.apache.tomcat:tomcat'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '10.0.0-M1'}, {'fixed': '10.0.7'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.apache.tomcat:tomcat'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '9.0.0-M1'}, {'fixed': '9.0.48'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.apache.tomcat:tomcat'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '8.5.0'}, {'fixed': '8.5.68'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-33037'}, {'type': 'WEB', 'url': 'https://kc.mcafee.com/corporate/index?page=content&id=SB10366'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r290aee55b72811fd19e75ac80f6143716c079170c5671b96932ed44b@%3Ccommits.tomee.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r40f921575aee8d7d34e53182f862c45cbb8f3d898c9d4e865c2ec262@%3Ccommits.tomee.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r612a79269b0d5e5780c62dfd34286a8037232fec0bc6f1a7e60c9381%40%3Cannounce.tomcat.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rc6ef52453bb996a98cb45442871a1db56b7c349939e45d829bf9ae37@%3Ccommits.tomee.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rd0dfea39829bc0606c936a16f6fca338127c86c0a1083970b45ac8d2@%3Ccommits.tomee.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/re01e7e93154e8bdf78a11a23f9686427bd3d51fc6e12c508645567b7@%3Ccommits.tomee.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rf1b54fd3f52f998ca4829159a88cc4c23d6cef5c6447d00948e75c97@%3Ccommits.tomee.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread/kovg1bft77xo34ksrcskh5nl50p69962'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2021/08/msg00009.html'}, {'type': 'WEB', 'url': 'https://security.gentoo.org/glsa/202208-34'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20210827-0007/'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2021/dsa-4952'}, {'type': 'WEB', 'url': 'https://www.oracle.com//security-alerts/cpujul2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuapr2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujan2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2021.html'}]
|
{'cwe_ids': ['CWE-444'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-07-13T19:38:16Z', 'nvd_published_at': '2021-07-12T15:15:00Z'}
|
1.4.0
|
GHSA-7qfm-6m33-rgg9
|
2021-06-28T19:08:40Z
|
2021-08-13T15:21:59Z
| null |
[]
|
XML External Entity Reference
|
An issue was discovered in service-api before 4.3.12 and 5.x before 5.1.1 for Report Portal. It allows XXE, with resultant secrets disclosure and SSRF, via JUnit XML launch import.
|
[{'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': 'Maven', 'name': 'com.epam.reportportal:service-api'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.3.12'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'com.epam.reportportal:service-api'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '5.0.0'}, {'fixed': '5.1.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-12642'}, {'type': 'WEB', 'url': 'https://github.com/reportportal/reportportal/blob/master/SECURITY_ADVISORIES.md'}]
|
{'cwe_ids': ['CWE-611'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-06-28T19:08:40Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-fqpx-cq8x-9wp4
|
2021-08-19T21:20:35Z
|
2021-08-25T20:46:03Z
| null |
['CVE-2020-25796']
|
Unaligned references in sized-chunks
|
An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the InlineArray implementation, an unaligned reference may be generated for a type that has a large alignment requirement.
|
[{'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-25796'}, {'type': 'WEB', 'url': 'https://github.com/bodil/sized-chunks/issues/11'}, {'type': 'PACKAGE', 'url': 'https://github.com/bodil/sized-chunks'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0041.html'}]
|
{'cwe_ids': ['CWE-129'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:20:35Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-q3g3-h9r4-prrc
|
2021-08-24T13:19:13Z
|
2021-08-25T14:42:47Z
| null |
['CVE-2021-37659']
|
Reference binding to nullptr and heap OOB in binary cwise ops
|
### Impact
An attacker can cause undefined behavior via binding a reference to null pointer in all binary cwise operations that don't require broadcasting (e.g., gradients of binary cwise operations):
```python
import tensorflow as tf
tf.raw_ops.SqrtGrad(y=[4, 16],dy=[])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/cwise_ops_common.h#L264) assumes that the two inputs have exactly the same number of elements but does not check that. Hence, when the eigen functor executes it triggers heap OOB reads and undefined behavior due to binding to nullptr.
### Patches
We have patched the issue in GitHub commit [93f428fd1768df147171ed674fee1fc5ab8309ec](https://github.com/tensorflow/tensorflow/commit/93f428fd1768df147171ed674fee1fc5ab8309ec).
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-q3g3-h9r4-prrc'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37659'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/93f428fd1768df147171ed674fee1fc5ab8309ec'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T13:19:13Z', 'nvd_published_at': '2021-08-12T21:15:00Z'}
|
1.4.0
|
GHSA-v82p-hv3v-p6qp
|
2021-08-24T13:55:57Z
|
2021-08-25T14:42:16Z
| null |
['CVE-2021-37665']
|
Incomplete validation in MKL requantization
|
### Impact
Due to incomplete validation in MKL implementation of requantization, an attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays:
```python
import tensorflow as tf
tf.raw_ops.RequantizationRangePerChannel(
input=[],
input_min=[0,0,0,0,0],
input_max=[1,1,1,1,1],
clip_value_max=1)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantization_range_per_channel_op.cc) does not validate the dimensions of the `input` tensor.
A similar issue occurs in `MklRequantizePerChannelOp`:
```python
import tensorflow as tf
from tensorflow.python.ops import gen_math_ops
gen_math_ops.requantize_per_channel(
input=[],
input_min=[-100,-100,-100,-100,-100],
input_max=[-100,-100,-100],
requested_output_min=[-100,-100,-100,-100,-100],
requested_output_max=[],
out_type=tf.int)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantize_per_channel_op.cc) does not perform full validation for all the input arguments.
### Patches
We have patched the issue in GitHub commit [9e62869465573cb2d9b5053f1fa02a81fce21d69](https://github.com/tensorflow/tensorflow/commit/9e62869465573cb2d9b5053f1fa02a81fce21d69) and in the Github commit [203214568f5bc237603dbab6e1fd389f1572f5c9](https://github.com/tensorflow/tensorflow/commit/203214568f5bc237603dbab6e1fd389f1572f5c9).
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-v82p-hv3v-p6qp'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37665'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/203214568f5bc237603dbab6e1fd389f1572f5c9'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/9e62869465573cb2d9b5053f1fa02a81fce21d69'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-20'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T13:55:57Z', 'nvd_published_at': '2021-08-12T23:15:00Z'}
|
1.4.0
|
GHSA-hxw9-jxqw-jc8j
|
2021-08-24T18:21:21Z
|
2021-08-25T20:58:05Z
| null |
['CVE-2020-36459']
|
Data races in dces
|
An issue was discovered in the dces crate through 2020-12-09 for Rust. The World type is marked as Send but lacks bounds on its EntityStore and ComponentStore. This allows non-thread safe `EntityStore` and `ComponentStore`s to be sent
across threads and cause data races.
|
[{'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': 'dces'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.3.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36459'}, {'type': 'PACKAGE', 'url': 'https://gitlab.redox-os.org/redox-os/dces-rust'}, {'type': 'WEB', 'url': 'https://gitlab.redox-os.org/redox-os/dces-rust/-/issues/8'}, {'type': 'WEB', 'url': 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/dces/RUSTSEC-2020-0139.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0139.html'}]
|
{'cwe_ids': ['CWE-362', 'CWE-77'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T20:20:09Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-rqgx-hpg4-456r
|
2021-08-19T20:50:52Z
|
2021-08-25T20:49:45Z
| null |
['CVE-2020-35902']
|
Use-after-free in actix-codec
|
An issue was discovered in the actix-codec crate before 0.3.0-beta.1 for Rust. There is a use-after-free in Framed.
|
[{'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': 'actix-codec'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.3.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35902'}, {'type': 'WEB', 'url': 'https://github.com/actix/actix-net/issues/91'}, {'type': 'PACKAGE', 'url': 'https://github.com/actix/actix-net'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0049.html'}]
|
{'cwe_ids': ['CWE-416'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T20:50:52Z', 'nvd_published_at': '2020-12-31T09:15:00Z'}
|
1.4.0
|
GHSA-hrjm-c879-pp86
|
2023-08-25T00:12:24Z
|
2021-08-25T20:46:46Z
| null |
['CVE-2019-25003']
|
libsecp256k1 contains side-channel timing attack
|
Versions of libsecp256k1 prior to 0.3.1 did not execute `Scalar::check_overflow` in constant time. This allows an attacker to potentially leak information via a timing attack. The flaw was corrected by modifying `Scalar::check_overflow` to execute in constant time.
|
[{'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': 'libsecp256k1'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.3.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-25003'}, {'type': 'WEB', 'url': 'https://github.com/paritytech/libsecp256k1/commit/11ba23a9766a5079918cd9f515bc100bc8164b50'}, {'type': 'PACKAGE', 'url': 'https://github.com/paritytech/libsecp256k1'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0027.html'}]
|
{'cwe_ids': ['CWE-208'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:19:40Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-8q2v-67v7-6vc6
|
2023-06-13T20:48:27Z
|
2021-08-25T20:48:07Z
| null |
['CVE-2020-35882']
|
Data races in rocket
|
The affected version of rocket contains a Clone trait implementation of LocalRequest that reuses the pointer to inner Request object. This causes data race in rare combinations of APIs if the original and the cloned objects are modified at the same time.
|
[{'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': 'rocket'}, 'ecosystem_specific': {'affected_functions': ['rocket::local::LocalRequest::clone']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.4.0'}, {'fixed': '0.4.5'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35882'}, {'type': 'WEB', 'url': 'https://github.com/SergioBenitez/Rocket/issues/1312'}, {'type': 'PACKAGE', 'url': 'https://github.com/SergioBenitez/Rocket'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0028.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:07:49Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-jqfh-8hw5-fqjr
|
2021-10-21T14:15:03Z
|
2021-08-25T14:44:48Z
| null |
['CVE-2021-39157']
|
Improper Handling of Exceptional Conditions in detect-character-encoding
|
### Impact
In detect-character-encoding v0.6.0 and earlier, data matching no charset causes the Node.js process to crash.
### Patches
The problem has been patched in [detect-character-encoding v0.7.0](https://github.com/sonicdoe/detect-character-encoding/releases/tag/v0.7.0).
### CVSS score
[CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/RL:O/RC:C](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/RL:O/RC:C)
Base Score: 7.5 (High)
Temporal Score: 7.2 (High)
Since detect-character-encoding is a library, the scoring is based on the “[reasonable worst-case implementation scenario](https://www.first.org/cvss/v3.1/user-guide#3-7-Scoring-Vulnerabilities-in-Software-Libraries-and-Similar)”, namely, accepting data from untrusted sources over a network and passing it directly to detect-character-encoding. Depending on your specific implementation, the vulnerability’s severity in your program may be different.
### Proof of concept
```js
const express = require("express");
const bodyParser = require("body-parser");
const detectCharacterEncoding = require("detect-character-encoding");
const app = express();
app.use(bodyParser.raw());
app.post("/", (req, res) => {
const charsetMatch = detectCharacterEncoding(req.body);
res.end(charsetMatch.encoding);
});
app.listen(3000);
```
`printf "\xAA" | curl --request POST --header "Content-Type: application/octet-stream" --data-binary @- http://localhost:3000` crashes the server.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'detect-character-encoding'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.7.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/sonicdoe/detect-character-encoding/security/advisories/GHSA-jqfh-8hw5-fqjr'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39157'}, {'type': 'WEB', 'url': 'https://github.com/sonicdoe/detect-character-encoding/issues/15'}, {'type': 'WEB', 'url': 'https://github.com/sonicdoe/detect-character-encoding/commit/992a11007fff6cfd40b952150ab8d30410c4a20a'}, {'type': 'PACKAGE', 'url': 'https://github.com/sonicdoe/detect-character-encoding'}, {'type': 'WEB', 'url': 'https://github.com/sonicdoe/detect-character-encoding/releases/tag/v0.7.0'}]
|
{'cwe_ids': ['CWE-755'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T19:11:52Z', 'nvd_published_at': '2021-08-24T19:15:00Z'}
|
1.4.0
|
GHSA-62jx-8vmh-4mcw
|
2023-06-13T22:04:07Z
|
2021-08-25T20:58:23Z
| null |
['CVE-2021-38511']
|
Links in archive can create arbitrary directories
|
When unpacking a tarball that contains a symlink the tar crate may create directories outside of the directory it's supposed to unpack into. The function errors when it's trying to create a file, but the folders are already created at this point.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'tar'}, 'ecosystem_specific': {'affected_functions': ['tar::Archive::unpack']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.36'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-38511'}, {'type': 'WEB', 'url': 'https://github.com/alexcrichton/tar-rs/issues/238'}, {'type': 'WEB', 'url': 'https://github.com/alexcrichton/tar-rs/pull/259'}, {'type': 'PACKAGE', 'url': 'https://github.com/alexcrichton/tar-rs'}, {'type': 'WEB', 'url': 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/tar/RUSTSEC-2021-0080.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0080.html'}]
|
{'cwe_ids': ['CWE-22'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T20:08:23Z', 'nvd_published_at': '2021-08-10T23:15:00Z'}
|
1.4.0
|
GHSA-w7j2-35mf-95p7
|
2022-07-13T20:03:17Z
|
2021-08-25T20:52:16Z
| null |
['CVE-2021-27378']
|
Incorrect check on buffer length in rand_core
|
An issue was discovered in the rand_core crate before 0.6.2 for Rust. Because `read_u32_into` and `read_u64_into` mishandle certain buffer-length checks, a random number generator may be seeded with too little data. The vulnerability was introduced in v0.6.0. The advisory doesn't apply to earlier minor version numbers.
Because read_u32_into and read_u64_into mishandle certain buffer-length checks, a random number generator may be seeded with too little data.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'rand_core'}, 'ecosystem_specific': {'affected_functions': ['rand_core::le::read_u32_into', 'rand_core::le::read_u64_into']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.6.0'}, {'fixed': '0.6.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-27378'}, {'type': 'WEB', 'url': 'https://github.com/rust-random/rand/pull/1096'}, {'type': 'PACKAGE', 'url': 'https://github.com/rust-random/rand'}, {'type': 'WEB', 'url': 'https://github.com/rust-random/rand/compare/0.6.0...rand_core-0.6.2#diff-f41b3dfa5ce28f3bee390d327c50621e141cf3569921f8e9ca15ccfcf25263a9R19'}, {'type': 'WEB', 'url': 'https://github.com/rust-random/rand/compare/0.6.0...rand_core-0.6.2#diff-f41b3dfa5ce28f3bee390d327c50621e141cf3569921f8e9ca15ccfcf25263a9R28'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0023.html'}]
|
{'cwe_ids': ['CWE-330'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:35:01Z', 'nvd_published_at': '2021-02-18T04:15:00Z'}
|
1.4.0
|
GHSA-rpcm-whqc-jfw8
|
2021-08-19T21:22:31Z
|
2021-08-25T20:44:53Z
| null |
['CVE-2019-15552']
|
Use after free in libflate
|
An issue was discovered in the libflate crate before 0.1.25 for Rust. MultiDecoder::read has a use-after-free, leading to arbitrary 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': 'libflate'}, 'ecosystem_specific': {'affected_functions': ['libflate::gzip::MultiDecoder::read']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.1.14'}, {'fixed': '0.1.25'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-15552'}, {'type': 'WEB', 'url': 'https://github.com/sile/libflate/issues/35'}, {'type': 'WEB', 'url': 'https://github.com/sile/libflate/pull/37'}, {'type': 'WEB', 'url': 'https://github.com/sile/libflate/commit/ffeff7c65deac5a6f886db2a59bcae4e420e4706'}, {'type': 'PACKAGE', 'url': 'https://github.com/sile/libflate'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0010.html'}]
|
{'cwe_ids': ['CWE-416'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:22:31Z', 'nvd_published_at': '2019-08-26T15:15:00Z'}
|
1.4.0
|
GHSA-q39c-5vh5-vw2p
|
2021-07-26T18:43:04Z
|
2021-08-02T16:47:10Z
| null |
['CVE-2020-27178']
|
Improper Authentication in Apereo CAS
|
Apereo CAS 5.3.x before 5.3.16, 6.x before 6.1.7.2, 6.2.x before 6.2.4, and 6.3.x before 6.3.0-RC4 mishandles secret keys with Google Authenticator for multifactor authentication.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.apereo.cas:cas-server-webapp'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '5.3.0'}, {'fixed': '5.3.16'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.apereo.cas:cas-server-webapp'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '6.0.0'}, {'fixed': '6.1.7.2'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.1.7.1'}}, {'package': {'ecosystem': 'Maven', 'name': 'org.apereo.cas:cas-server-webapp'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '6.2.0'}, {'fixed': '6.2.4'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.apereo.cas:cas-server-support-otp-mfa-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '5.3.0'}, {'fixed': '5.3.16'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.apereo.cas:cas-server-support-otp-mfa-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '6.0.0'}, {'fixed': '6.1.7.2'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.1.7.1'}}, {'package': {'ecosystem': 'Maven', 'name': 'org.apereo.cas:cas-server-support-otp-mfa-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '6.2.0'}, {'fixed': '6.2.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-27178'}, {'type': 'WEB', 'url': 'https://apereo.github.io/2020/10/14/gauthvuln/'}]
|
{'cwe_ids': ['CWE-287'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-07-26T18:43:04Z', 'nvd_published_at': '2020-10-16T16:15:00Z'}
|
1.4.0
|
GHSA-5hj3-vjjf-f5m7
|
2021-08-24T14:35:33Z
|
2021-08-25T14:41:39Z
| null |
['CVE-2021-37672']
|
Heap OOB in `SdcaOptimizerV2`
|
### Impact
An attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to `tf.raw_ops.SdcaOptimizerV2`:
```python
import tensorflow as tf
tf.raw_ops.SdcaOptimizerV2(
sparse_example_indices=[[1]],
sparse_feature_indices=[[1]],
sparse_feature_values=[[1.0,2.0]],
dense_features=[[1.0]],
example_weights=[1.0],
example_labels=[],
sparse_indices=[1],
sparse_weights=[1.0],
dense_weights=[[1.0]],
example_state_data=[[100.0,100.0,100.0,100.0]],
loss_type='logistic_loss',
l1=100.0,
l2=100.0,
num_loss_partitions=1,
num_inner_iterations=1,
adaptive=True)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/sdca_internal.cc#L320-L353) does not check that the length of `example_labels` is the same as the number of examples.
### Patches
We have patched the issue in GitHub commit [a4e138660270e7599793fa438cd7b2fc2ce215a6](https://github.com/tensorflow/tensorflow/commit/a4e138660270e7599793fa438cd7b2fc2ce215a6).
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-5hj3-vjjf-f5m7'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37672'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/a4e138660270e7599793fa438cd7b2fc2ce215a6'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T14:35:33Z', 'nvd_published_at': '2021-08-12T23:15:00Z'}
|
1.4.0
|
GHSA-4xfp-4pfp-89wg
|
2021-08-24T13:07:20Z
|
2021-08-25T14:42:55Z
| null |
['CVE-2021-37656']
|
Reference binding to nullptr in `RaggedTensorToSparse`
|
### Impact
An attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.RaggedTensorToSparse`:
```python
import tensorflow as tf
tf.raw_ops.RaggedTensorToSparse(
rt_nested_splits=[[0, 38, 0]],
rt_dense_values=[])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/ragged_tensor_to_sparse_kernel.cc#L30) has an incomplete validation of the splits values: it does not check that they are in increasing order.
### Patches
We have patched the issue in GitHub commit [1071f554dbd09f7e101324d366eec5f4fe5a3ece](https://github.com/tensorflow/tensorflow/commit/1071f554dbd09f7e101324d366eec5f4fe5a3ece).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.4'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.1'}]}], 'versions': ['2.5.0']}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-4xfp-4pfp-89wg'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37656'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/1071f554dbd09f7e101324d366eec5f4fe5a3ece'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-824'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T13:07:20Z', 'nvd_published_at': '2021-08-12T21:15:00Z'}
|
1.4.0
|
GHSA-jg8v-48h5-wgxg
|
2023-09-12T19:23:56Z
|
2021-08-10T16:02:18Z
| null |
['CVE-2021-23413']
|
jszip Vulnerable to Prototype Pollution
|
This affects the package jszip before 3.7.0. Crafting a new zip file with filenames set to Object prototype values (e.g `__proto__`, `toString`, etc) results in a returned object with a modified prototype instance.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'jszip'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.0.0'}, {'fixed': '3.7.0'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'jszip'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.7.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-23413'}, {'type': 'WEB', 'url': 'https://github.com/Stuk/jszip/pull/766'}, {'type': 'WEB', 'url': 'https://github.com/Stuk/jszip/commit/22357494f424178cb416cdb7d93b26dd4f824b36'}, {'type': 'PACKAGE', 'url': 'https://github.com/Stuk/jszip'}, {'type': 'WEB', 'url': 'https://github.com/Stuk/jszip/blob/master/lib/object.js%23L88'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARS-1251499'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1251498'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JS-JSZIP-1251497'}]
|
{'cwe_ids': ['CWE-1321'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-02T22:15:49Z', 'nvd_published_at': '2021-07-25T13:15:00Z'}
|
1.4.0
|
GHSA-8892-84wf-cg8f
|
2023-06-13T21:01:55Z
|
2021-08-25T21:00:16Z
| null |
[]
|
SyncChannel<T> can move 'T: !Send' to other threads
|
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': 'WEB', 'url': 'https://github.com/kitsuneninetails/signal-rust/issues/2'}, {'type': 'PACKAGE', 'url': 'https://github.com/kitsuneninetails/signal-rust/'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0126.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-06T18:04:55Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-hqxw-mm44-gc4r
|
2022-08-15T20:04:30Z
|
2021-08-30T16:16:14Z
| null |
['CVE-2021-39156']
|
Istio Fragments in Path May Lead to Authorization Policy Bypass
|
### Impact
Istio 1.11.0, 1.10.3 and below, and 1.9.7 and below contain a remotely exploitable vulnerability where an HTTP request with `#fragment` in the path may bypass Istio’s URI path based authorization policies.
### Patches
* Istio 1.11.1 and above
* Istio 1.10.4 and above
* Istio 1.9.8 and above
### Workarounds
A Lua filter may be written to normalize the path. This is similar to the Path normalization presented in the [Security Best Practices](https://istio.io/latest/docs/ops/best-practices/security/#case-normalization) guide.
### References
More details can be found in the [Istio Security Bulletin](https://istio.io/latest/news/security/istio-security-2021-008)
### For more information
If you have any questions or comments about this advisory, please email us at istio-security-vulnerability-reports@googlegroups.com
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'istio.io/istio'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.9.8'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'istio.io/istio'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.10.0'}, {'fixed': '1.10.4'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'istio.io/istio'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.11.0'}, {'fixed': '1.11.1'}]}], 'versions': ['1.11.0']}]
|
[{'type': 'WEB', 'url': 'https://github.com/istio/istio/security/advisories/GHSA-hqxw-mm44-gc4r'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39156'}, {'type': 'PACKAGE', 'url': 'https://github.com/istio/istio'}, {'type': 'WEB', 'url': 'https://istio.io/latest/news/security/istio-security-2021-008'}]
|
{'cwe_ids': ['CWE-706', 'CWE-863'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-25T22:28:17Z', 'nvd_published_at': '2021-08-24T23:15:00Z'}
|
1.4.0
|
GHSA-77m6-x95j-75r5
|
2023-06-13T22:07:15Z
|
2021-08-25T20:58:58Z
| null |
['CVE-2020-36439']
|
Data races in ticketed_lock
|
Affected versions of this crate unconditionally implemented Send for ReadTicket<T> & WriteTicket<T>. This allows to send non-Send T to other threads. This can allows creating data races by cloning types with internal mutability and sending them to other threads (as T of ReadTicket<T>/WriteTicket<T>). Such data races can cause memory corruption or other undefined behavior. The flaw was corrected in commit `a986a93` by adding T: Send bounds to Send impls of ReadTicket<T>/WriteTicket<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': 'ticketed_lock'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.3.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36439'}, {'type': 'WEB', 'url': 'https://github.com/kvark/ticketed_lock/issues/7'}, {'type': 'WEB', 'url': 'https://github.com/kvark/ticketed_lock/commit/a986a9335d591fa5c826157d1674d47aa525357f'}, {'type': 'PACKAGE', 'url': 'https://github.com/kvark/ticketed_lock/'}, {'type': 'WEB', 'url': 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/ticketed_lock/RUSTSEC-2020-0119.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0119.html'}]
|
{'cwe_ids': ['CWE-119', 'CWE-362'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-09T22:40:34Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-x7vr-c387-8w57
|
2023-06-13T18:21:10Z
|
2021-08-25T21:01:31Z
| null |
['CVE-2020-25574']
|
Integer Overflow/Infinite Loop in the http crate
|
HeaderMap::reserve() used usize::next_power_of_two() to calculate the increased capacity. However, next_power_of_two() silently overflows to 0 if given a sufficiently large number in release mode.
If the map was not empty when the overflow happens, the library will invoke self.grow(0) and start infinite probing. This allows an attacker who controls the argument to reserve() to cause a potential denial of service (DoS).
The flaw was corrected in 0.1.20 release of http crate.
|
[{'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': 'http'}, 'ecosystem_specific': {'affected_functions': ['http::header::HeaderMap::reserve']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.1.20'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-25574'}, {'type': 'WEB', 'url': 'https://github.com/hyperium/http/issues/352'}, {'type': 'PACKAGE', 'url': 'https://github.com/hyperium/http'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0033.html'}]
|
{'cwe_ids': ['CWE-190', 'CWE-835'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-07-26T18:47:31Z', 'nvd_published_at': '2020-09-14T19:15:00Z'}
|
1.4.0
|
GHSA-g4gq-j4p2-j8fr
|
2021-08-30T23:21:29Z
|
2021-08-05T17:00:37Z
| null |
['CVE-2021-32811']
|
Remote Code Execution via Script (Python) objects under Python 3
|
### Impact
Background: The optional add-on package `Products.PythonScripts` adds `Script (Python)` to the list of content items a user can add to the Zope object database. Inside these scripts users can write Python code that is executed when rendered through the web. The code environment in these script objects is limited, it relies on the `RestrictedPython` package to provide a "safe" subset of Python instructions as well as the `AccessControl` package that defines security policies for execution in the context of a Zope application.
Recently the `AccessControl` package was updated to fix a remote code execution security issue. A link to the security advisory is provided in the References section below. The bug tightens the `AccessControl` security policies for Zope by blocking access to unsafe classes inside the Python `string` module.
You are only affected if the following are true:
- You use Python 3 for your Zope deployment (Zope 4 on Python 2 is not affected)
- You run Zope 4 below version 4.6.3 or Zope 5 below version 5.3
- You have installed the optional `Products.PythonScripts` add-on package
By default, you need to have the admin-level Zope "Manager" role to add or edit Script (Python) objects through the web. Only sites that allow untrusted users to add/edit these scripts through the web - which would be a very unusual configuration to begin with - are at risk.
### Patches
The problem has been fixed in `AccessControl` versions 4.3 and 5.2. Zope releases 4.6.3 and 5.3 now require these new `AccessControl` releases.
### Workarounds
A site administrator can restrict adding/editing Script (Python) objects through the web using the standard Zope user/role permission mechanisms. Untrusted users should not be assigned the Zope Manager role and adding/editing these scripts through the web should be restricted to trusted users only. This is the default configuration in Zope.
### References
* [AccessControl security advisory GHSA-qcx9-j53g-ccgf](https://github.com/zopefoundation/AccessControl/security/advisories/GHSA-qcx9-j53g-ccgf)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [Zope issue tracker](https://github.com/zopefoundation/Zope/issues)
* Email us at [security@plone.org](mailto:security@plone.org)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'Zope'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.0'}, {'fixed': '4.6.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'Zope'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '5.0'}, {'fixed': '5.3'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/zopefoundation/AccessControl/security/advisories/GHSA-qcx9-j53g-ccgf'}, {'type': 'WEB', 'url': 'https://github.com/zopefoundation/Zope/security/advisories/GHSA-g4gq-j4p2-j8fr'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-32811'}, {'type': 'WEB', 'url': 'https://github.com/zopefoundation/Zope/commit/f72a18dda8e9bf2aedb46168761668464a4be988'}, {'type': 'PACKAGE', 'url': 'https://github.com/zopefoundation/Zope'}]
|
{'cwe_ids': ['CWE-1321', 'CWE-915'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-02T22:57:25Z', 'nvd_published_at': '2021-08-02T22:15:00Z'}
|
1.4.0
|
GHSA-g4xg-fxmg-vcg5
|
2021-09-07T21:16:08Z
|
2021-08-05T19:31:55Z
| null |
['CVE-2021-3013']
|
OS command injection in ripgrep
|
ripgrep before 13 on Windows allows attackers to trigger execution of arbitrary programs from the current working directory via the -z/--search-zip or --pre flag.
|
[{'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': 'ripgrep'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '13.0.0'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'grep-cli'}, 'ecosystem_specific': {'affected_functions': ['grep_cli::DecompressionReader::new']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.1.6'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3013'}, {'type': 'WEB', 'url': 'https://github.com/BurntSushi/ripgrep/issues/1773'}, {'type': 'PACKAGE', 'url': 'https://github.com/BurntSushi/ripgrep'}, {'type': 'WEB', 'url': 'https://github.com/BurntSushi/ripgrep/blob/e48a17e1891e1ea9dd06ba0e48d5fb140ca7c0c4/CHANGELOG.md'}, {'type': 'WEB', 'url': 'https://github.com/BurntSushi/ripgrep/blob/master/CHANGELOG.md'}, {'type': 'WEB', 'url': 'https://github.com/BurntSushi/ripgrep/blob/master/CHANGELOG.md#1300-2021-06-12'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0071.html'}]
|
{'cwe_ids': ['CWE-78'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-06-14T19:32:57Z', 'nvd_published_at': '2021-06-11T12:15:00Z'}
|
1.4.0
|
GHSA-c9rv-3jmq-527w
|
2023-06-13T17:09:32Z
|
2021-08-25T20:49:50Z
| null |
['CVE-2020-35918']
|
Unexpected panic when decoding tokens in branca
|
Prior to 0.10.0 it was possible to have both decoding functions panic unexpectedly, by supplying tokens with an incorrect base62 encoding.
The documentation stated that an error should have been reported instead.
|
[{'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': 'branca'}, 'ecosystem_specific': {'affected_functions': ['branca::Branca::decode', 'branca::decode']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.10.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35918'}, {'type': 'WEB', 'url': 'https://github.com/return/branca/issues/24'}, {'type': 'WEB', 'url': 'https://github.com/tuupola/branca-spec/issues/22'}, {'type': 'WEB', 'url': 'https://github.com/return/branca/commit/7da3274bd99b05dce9c3f9b4b129d0145c71820b'}, {'type': 'PACKAGE', 'url': 'https://github.com/return/branca'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0075.html'}]
|
{'cwe_ids': ['CWE-20'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T20:50:27Z', 'nvd_published_at': '2020-12-31T09:15:00Z'}
|
1.4.0
|
GHSA-m72m-mhq2-9p6c
|
2022-02-08T20:59:16Z
|
2021-08-23T19:42:38Z
| null |
['CVE-2021-37714']
|
Uncaught Exception in jsoup
|
### Impact
_What kind of vulnerability is it? Who is impacted?_
Those using jsoup to parse untrusted HTML or XML may be vulnerable to DOS attacks. If the parser is run on user supplied input, an attacker may supply content that causes the parser to get stuck (loop indefinitely until cancelled), to complete more slowly than usual, or to throw an unexpected exception. This effect may support a denial of service attack.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
Users should upgrade to jsoup 1.14.2
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
Users may rate limit input parsing. Users should limit the size of inputs based on system resources. Users should implement thread watchdogs to cap and timeout parse runtimes.
|
[{'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.jsoup:jsoup'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.14.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/jhy/jsoup/security/advisories/GHSA-m72m-mhq2-9p6c'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37714'}, {'type': 'PACKAGE', 'url': 'https://github.com/jhy/jsoup'}, {'type': 'WEB', 'url': 'https://jsoup.org/news/release-1.14.1'}, {'type': 'WEB', 'url': 'https://jsoup.org/news/release-1.14.2'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r215009dbf7467a9f6506d0c0024cb36cad30071010e62c9352cfaaf0@%3Cissues.maven.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r377b93d79817ce649e9e68b3456e6f499747ef1643fa987b342e082e@%3Cissues.maven.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r3d71f18adb78e50f626dde689161ca63d3b7491bd9718fcddfaecba7@%3Cissues.maven.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r50e9c9466c592ca9d707a5dea549524d19e3287da08d8392f643960e@%3Cissues.maven.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r685c5235235ad0c26e86d0ee987fb802c9675de6081dbf0516464e0b@%3Cnotifications.james.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r97404676a5cf591988faedb887d64e278f522adcaa823d89ca69defe@%3Cnotifications.james.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rc3354080fc67fb50b45b3c2d12dc4ca2a3c1c78dad3d3ba012c038aa@%3Cnotifications.james.apache.org%3E'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20220210-0022/'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuapr2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujan2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujul2022.html'}]
|
{'cwe_ids': ['CWE-248', 'CWE-835'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T17:20:30Z', 'nvd_published_at': '2021-08-18T15:15:00Z'}
|
1.4.0
|
GHSA-29hg-r7c7-54fr
|
2021-08-19T17:05:09Z
|
2021-08-25T20:55:06Z
| null |
['CVE-2021-29933']
|
Double free in insert_many
|
An issue was discovered in the insert_many crate through 2021-01-26 for Rust. Elements may be dropped twice if a .next() method 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': 'insert_many'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.1.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-29933'}, {'type': 'WEB', 'url': 'https://github.com/rphmeier/insert_many/issues/1'}, {'type': 'PACKAGE', 'url': 'https://github.com/rphmeier/insert_many'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0042.html'}]
|
{'cwe_ids': ['CWE-415'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:05:09Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-m57c-4vvx-gjgq
|
2021-08-18T17:45:17Z
|
2021-08-25T20:58:27Z
| null |
['CVE-2019-15546']
|
Format string vulnerabilities in pancurses
|
An issue was discovered in the pancurses crate through 0.16.1 for Rust. printw and mvprintw have format string vulnerabilities.
|
[{'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': 'pancurses'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.16.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-15546'}, {'type': 'WEB', 'url': 'https://github.com/RustSec/advisory-db/issues/106'}, {'type': 'WEB', 'url': 'https://github.com/ihalila/pancurses/issues/66'}, {'type': 'PACKAGE', 'url': 'https://github.com/ihalila/pancurses'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0005.html'}]
|
{'cwe_ids': ['CWE-134'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T17:45:17Z', 'nvd_published_at': '2019-08-26T18:15:00Z'}
|
1.4.0
|
GHSA-8r7q-r9mx-35rh
|
2021-08-19T21:18:40Z
|
2021-08-25T20:47:18Z
| null |
['CVE-2020-35869']
|
Mishandling of format strings in rusqlite
|
An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated because rusqlite::trace::log mishandles format strings.
|
[{'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-35869'}, {'type': 'WEB', 'url': 'https://github.com/rusqlite/rusqlite/commit/2327d3b774927fdf48903c0bdc1ca7ec93c7c8d0'}, {'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-134'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:18:40Z', 'nvd_published_at': '2020-12-31T10:15:00Z'}
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.