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-rc7p-gmvh-xfx2
|
2021-08-02T17:18:32Z
|
2021-08-02T17:19:52Z
| null |
[]
|
Attack on Kubernetes via Misconfigured Argo Workflows
|
### Impact
Users running using the Argo Server with `--auth-mode=server` (which is the default < v3.0.0) AND have exposed their UI to the Internet may allow remote users to execute arbitrary code on their cluster, e.g. crypto-mining.
### Resolution
* Do not expose your user interface to the Internet.
* Change configuration. `--auth-mode=client`.
For users using an older 2.x version of Argo Server, consider upgrading to Argo Server version 3.x or later.
|
[]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/argoproj/argo-workflows'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}]}], 'database_specific': {'last_known_affected_version_range': '< 3.0.0'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/argoproj/argo-workflows/security/advisories/GHSA-rc7p-gmvh-xfx2'}, {'type': 'WEB', 'url': 'https://www.intezer.com/blog/container-security/new-attacks-on-kubernetes-via-misconfigured-argo-workflows/'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-07-22T20:25:42Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-83mx-573x-5rw9
|
2023-09-05T14:49:32Z
|
2021-08-25T20:54:02Z
| null |
['CVE-2021-3449']
|
openssl-src NULL pointer Dereference in signature_algorithms processing
|
An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits the signature_algorithms extension (where it was present in the initial ClientHello), but includes a signature_algorithms_cert extension then a NULL pointer dereference will result, leading to a crash and a denial of service attack. A server is only vulnerable if it has TLSv1.2 and renegotiation enabled (which is the default configuration). OpenSSL TLS clients are not impacted by this issue. All OpenSSL 1.1.1 versions are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1-1.1.1j).
|
[{'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': 'openssl-src'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '111.15.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3449'}, {'type': 'WEB', 'url': 'https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf'}, {'type': 'WEB', 'url': 'https://cert-portal.siemens.com/productcert/pdf/ssa-772220.pdf'}, {'type': 'WEB', 'url': 'https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=fb9fa6b51defd48157eeb207f52181f735d96148'}, {'type': 'PACKAGE', 'url': 'https://github.com/alexcrichton/openssl-src-rs'}, {'type': 'WEB', 'url': 'https://kb.pulsesecure.net/articles/Pulse_Security_Advisories/SA44845'}, {'type': 'WEB', 'url': 'https://kc.mcafee.com/corporate/index?page=content&id=SB10356'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2021/08/msg00029.html'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CCBFLLVQVILIVGZMBJL3IXZGKWQISYNP/'}, {'type': 'WEB', 'url': 'https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2021-0013'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0055'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0055.html'}, {'type': 'WEB', 'url': 'https://security.FreeBSD.org/advisories/FreeBSD-SA-21:07.openssl.asc'}, {'type': 'WEB', 'url': 'https://security.gentoo.org/glsa/202103-03'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20210326-0006/'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20210513-0002/'}, {'type': 'WEB', 'url': 'https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-openssl-2021-GHY28dJd'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2021/dsa-4875'}, {'type': 'WEB', 'url': 'https://www.openssl.org/news/secadv/20210325.txt'}, {'type': 'WEB', 'url': 'https://www.oracle.com//security-alerts/cpujul2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuApr2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuapr2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujul2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2021.html'}, {'type': 'WEB', 'url': 'https://www.tenable.com/security/tns-2021-05'}, {'type': 'WEB', 'url': 'https://www.tenable.com/security/tns-2021-06'}, {'type': 'WEB', 'url': 'https://www.tenable.com/security/tns-2021-09'}, {'type': 'WEB', 'url': 'https://www.tenable.com/security/tns-2021-10'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/03/27/1'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/03/27/2'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/03/28/3'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/03/28/4'}]
|
{'cwe_ids': ['CWE-476'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:21:40Z', 'nvd_published_at': '2021-03-25T15:15:00Z'}
|
1.4.0
|
GHSA-fhvj-7f9p-w788
|
2023-06-13T16:51:18Z
|
2021-08-25T20:48:54Z
| null |
['CVE-2020-35887']
|
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-35887'}, {'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-120'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T20:56:25Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-5v34-g2px-j4fw
|
2022-02-08T21:08:25Z
|
2021-08-02T16:56:31Z
| null |
['CVE-2021-36374']
|
Improper Handling of Length Parameter Inconsistency in Apache Ant
|
When reading a specially crafted ZIP archive, or a derived formats, an Apache Ant build can be made to allocate large amounts of memory that leads to an out of memory error, even for small inputs. This can be used to disrupt builds using Apache Ant. Commonly used derived formats from ZIP archives are for instance JAR files and many office files. Apache Ant prior to 1.9.16 and 1.10.11 were affected.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.apache.ant:ant'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.9.16'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.apache.ant:ant'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.10.0'}, {'fixed': '1.10.11'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-36374'}, {'type': 'WEB', 'url': 'https://ant.apache.org/security.html'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r27919fd4db07c487239c1d9771f480d89ce5ee2750aa9447309b709a@%3Ccommits.groovy.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r544c9e8487431768465b8b2d13982c75123109bd816acf839d46010d@%3Ccommits.groovy.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rad36f470647c5a7c02dd78c9973356d2840766d132b597b6444e373a@%3Cnotifications.groovy.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rdd5412a5b9a25aed2a02c3317052d38a97128314d50bc1ed36e81d38%40%3Cuser.ant.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rf4bb79751a02889623195715925e4fd8932dd3c97e0ade91395a96c6@%3Cdev.myfaces.apache.org%3E'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20210819-0007/'}, {'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-130'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-07-15T19:18:28Z', 'nvd_published_at': '2021-07-14T07:15:00Z'}
|
1.4.0
|
GHSA-mcrf-7hf9-f6q5
|
2023-06-13T20:48:55Z
|
2021-08-25T21:00:09Z
| null |
[]
|
Unchecked vector pre-allocation
|
Affected versions of this crate pre-allocate memory on deserializing raw buffers without checking whether there is sufficient data available. This allows an attacker to do denial-of-service attacks by sending small msgpack messages that allocate gigabytes of memory.
|
[]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'rmpv'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/3Hren/msgpack-rust/issues/151'}, {'type': 'PACKAGE', 'url': 'https://github.com/3Hren/msgpack-rust'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2017-0006.html'}]
|
{'cwe_ids': ['CWE-400'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-06T19:28:40Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-v7q4-97x4-4qw2
|
2021-08-19T17:22:46Z
|
2021-08-25T20:51:58Z
| null |
['CVE-2021-28030']
|
Use of Uninitialized Resource in truetype
|
An issue was discovered in the truetype crate before 0.30.1 for Rust. Attackers can read the contents of uninitialized memory locations via a user-provided Read operation within Tape::take_bytes.
|
[{'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': 'truetype'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.30.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-28030'}, {'type': 'WEB', 'url': 'https://github.com/bodoni/truetype/issues/11'}, {'type': 'PACKAGE', 'url': 'https://github.com/bodoni/truetype'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0029.html'}]
|
{'cwe_ids': ['CWE-908'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:22:46Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-h6jh-7gv5-28vg
|
2021-08-23T19:25:38Z
|
2021-08-25T14:43:34Z
| null |
['CVE-2021-37646']
|
Bad alloc in `StringNGrams` caused by integer conversion
|
### Impact
The implementation of `tf.raw_ops.StringNGrams` is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value.
```python
import tensorflow as tf
tf.raw_ops.StringNGrams(
data=['',''],
data_splits=[0,2],
separator=' '*100,
ngram_widths=[-80,0,0,-60],
left_pad=' ',
right_pad=' ',
pad_width=100,
preserve_short_sequences=False)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/string_ngrams_op.cc#L184) calls `reserve` on a `tstring` with a value that sometimes can be negative if user supplies negative `ngram_widths`. The `reserve` method calls `TF_TString_Reserve` which has an `unsigned long` argument for the size of the buffer. Hence, the implicit conversion transforms the negative value to a large integer.
### Patches
We have patched the issue in GitHub commit [c283e542a3f422420cfdb332414543b62fc4e4a5](https://github.com/tensorflow/tensorflow/commit/c283e542a3f422420cfdb332414543b62fc4e4a5).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### 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-h6jh-7gv5-28vg'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37646'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/c283e542a3f422420cfdb332414543b62fc4e4a5'}]
|
{'cwe_ids': ['CWE-681'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T19:25:38Z', 'nvd_published_at': '2021-08-12T21:15:00Z'}
|
1.4.0
|
GHSA-mgg8-9pvp-6qcw
|
2021-08-24T18:01:27Z
|
2021-08-25T20:59:59Z
|
2021-08-24T18:01:27Z
|
[]
|
MvccRwLock allows data races & aliasing violations
|
Affected versions of the `noise_search` crate unconditionally implement Send/Sync for `MvccRwLock`.
This can lead to data races when types that are either `!Send` or `!Sync` (e.g. `Rc<T>`, `Arc<Cell<_>>`) are contained inside `MvccRwLock` and sent across thread boundaries. The data races can potentially lead to memory corruption (as demonstrated in the PoC from the original report issue).
Also, safe APIs of `MvccRwLock` allow aliasing violations by allowing `&T` and `LockResult<MutexGuard<Box<T>>>` to co-exist in conflicting lifetime regions. The APIs of `MvccRwLock` should either be marked as `unsafe` or `MbccRwLock` should be changed to private or pub(crate).
|
[]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'noise_search'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.7.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/pipedown/noise/issues/72'}, {'type': 'PACKAGE', 'url': 'https://github.com/pipedown/noise'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0141.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-09T17:16:18Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-qcx9-j53g-ccgf
|
2021-08-30T23:27:55Z
|
2021-08-05T17:01:30Z
| null |
['CVE-2021-32807']
|
Remote Code Execution via unsafe classes in otherwise permitted modules
|
### Impact
The module `AccessControl` defines security policies for Python code used in restricted code within Zope applications. Restricted code is any code that resides in Zope's object database, such as the contents of `Script (Python)` objects.
The policies defined in `AccessControl` severely restrict access to Python modules and only exempt a few that are deemed safe, such as Python's `string` module. However, full access to the `string` module also allows access to the class `Formatter`, which can be overridden and extended within `Script (Python)` in a way that provides access to other unsafe Python libraries. Those unsafe Python libraries can be used for remote code execution.
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 4.3 and 5.2.
Only AccessControl versions 4 and 5 are vulnerable, and only on Python 3, not Python 2.7.
### 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.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [AccessControl issue tracker](https://github.com/zopefoundation/AccessControl/issues)
* Email us at [security@plone.org](mailto:security@plone.org)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'AccessControl'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.0'}, {'fixed': '4.3'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'AccessControl'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '5.0'}, {'fixed': '5.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/zopefoundation/AccessControl/security/advisories/GHSA-qcx9-j53g-ccgf'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-32807'}, {'type': 'WEB', 'url': 'https://github.com/zopefoundation/AccessControl/commit/b42dd4badf803bb9fb71ac34cd9cb0c249262f2c'}, {'type': 'PACKAGE', 'url': 'https://github.com/zopefoundation/AccessControl'}, {'type': 'WEB', 'url': 'https://github.com/zopefoundation/AccessControl/blob/master/CHANGES.rst#51-2021-07-30'}]
|
{'cwe_ids': ['CWE-1321', 'CWE-915'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-02T23:00:00Z', 'nvd_published_at': '2021-07-30T22:15:00Z'}
|
1.4.0
|
GHSA-p8q8-jfcv-g2h2
|
2021-09-20T20:26:41Z
|
2021-08-09T20:40:06Z
| null |
['CVE-2021-32610']
|
Directory Traversal in Archive_Tar
|
In Archive_Tar before 1.4.14, symlinks can refer to targets outside of the extracted archive, a different vulnerability than CVE-2020-36193.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'pear/archive_tar'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.4.14'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-32610'}, {'type': 'WEB', 'url': 'https://github.com/pear/Archive_Tar/commit/7789ebb2f34f9e4adb3a4152ad0d1548930a9755'}, {'type': 'WEB', 'url': 'https://github.com/pear/Archive_Tar/commit/b5832439b1f37331fb4f87e67fe4f'}, {'type': 'PACKAGE', 'url': 'https://github.com/pear/Archive_Tar'}, {'type': 'WEB', 'url': 'https://github.com/pear/Archive_Tar/releases/tag/1.4.14'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2021/07/msg00023.html'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/42GPGVVFTLJYAKRI75IVB5R45NYQGEUR/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CAODVMHGL5MHQWQAQTXQ7G7OE3VQZ7LS/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/G5LTY6COQYNMMHQJ3QIOJHEWCKD4XDFH/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VJQQYDAOWHD6RDITDRPHFW7WY6BS3V5N/'}, {'type': 'WEB', 'url': 'https://www.drupal.org/sa-core-2021-004'}]
|
{'cwe_ids': ['CWE-59'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-02T18:04:45Z', 'nvd_published_at': '2021-07-30T14:15:00Z'}
|
1.4.0
|
GHSA-9w2p-5mgw-p94c
|
2021-08-23T19:20:13Z
|
2021-08-25T14:43:37Z
| null |
['CVE-2021-37645']
|
Integer overflow due to conversion to unsigned
|
### Impact
The implementation of `tf.raw_ops.QuantizeAndDequantizeV4Grad` is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value.
```python
import tensorflow as tf
tf.raw_ops.QuantizeAndDequantizeV4Grad(
gradients=[1.0,2.0],
input=[1.0,1.0],
input_min=[0.0],
input_max=[10.0],
axis=-100)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L126) uses the `axis` value as the size argument to `absl::InlinedVector` constructor. But, the constructor uses an unsigned type for the argument, so the implicit conversion transforms the negative value to a large integer.
### Patches
We have patched the issue in GitHub commit [96f364a1ca3009f98980021c4b32be5fdcca33a1](https://github.com/tensorflow/tensorflow/commit/96f364a1ca3009f98980021c4b32be5fdcca33a1).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, and TensorFlow 2.4.3, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by 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.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.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.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-9w2p-5mgw-p94c'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37645'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/96f364a1ca3009f98980021c4b32be5fdcca33a1'}]
|
{'cwe_ids': ['CWE-681'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T19:20:13Z', 'nvd_published_at': '2021-08-12T21:15:00Z'}
|
1.4.0
|
GHSA-7j36-gc4r-9x3r
|
2023-06-13T16:57:55Z
|
2021-08-25T20:44:48Z
| null |
['CVE-2019-16139']
|
Out of bounds access in compact_arena
|
Affected versions of this crate did not properly implement the generativity, because the invariant lifetimes were not necessarily dropped.
This allows an attacker to mix up two arenas, using indices created from one arena with another one. This might lead to an out-of-bounds read or write access into the memory reserved for the arena.
The flaw was corrected by implementing generativity correctly in version 0.4.0.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'compact_arena'}, 'ecosystem_specific': {'affected_functions': ['compact_arena::SmallArena::new']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-16139'}, {'type': 'WEB', 'url': 'https://github.com/llogiq/compact_arena/issues/22'}, {'type': 'PACKAGE', 'url': 'https://github.com/llogiq/compact_arena'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0015.html'}]
|
{'cwe_ids': ['CWE-125', 'CWE-787'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:22:37Z', 'nvd_published_at': '2019-09-09T12:15:00Z'}
|
1.4.0
|
GHSA-34p9-f4q3-c4r7
|
2023-06-13T20:14:09Z
|
2021-08-25T20:43:11Z
| null |
['CVE-2016-10931']
|
Improper Certificate Validation in openssl
|
All versions of rust-openssl prior to 0.9.0 contained numerous insecure defaults including off-by-default certificate verification and no API to perform hostname verification. Unless configured correctly by a developer, these defaults could allow an attacker to perform man-in-the-middle attacks. The problem was addressed in newer versions by enabling certificate verification by default and exposing APIs to perform hostname verification. Use the SslConnector and SslAcceptor types to take advantage of these new features (as opposed to the lower-level SslContext type).
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'openssl'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.9.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2016-10931'}, {'type': 'PACKAGE', 'url': 'https://github.com/sfackler/rust-openssl'}, {'type': 'WEB', 'url': 'https://github.com/sfackler/rust-openssl/releases/tag/v0.9.0'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2016-0001.html'}]
|
{'cwe_ids': ['CWE-295'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:25:06Z', 'nvd_published_at': '2019-08-26T12:15:00Z'}
|
1.4.0
|
GHSA-r4c4-5fpq-56wg
|
2021-08-24T13:46:31Z
|
2021-08-25T14:42:20Z
| null |
['CVE-2021-37664']
|
Heap OOB in boosted trees
|
### Impact
An attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to `BoostedTreesSparseCalculateBestFeatureSplit`:
```python
import tensorflow as tf
tf.raw_ops.BoostedTreesSparseCalculateBestFeatureSplit(
node_id_range=[0,10],
stats_summary_indices=[[1, 2, 3, 0x1000000]],
stats_summary_values=[1.0],
stats_summary_shape=[1,1,1,1],
l1=l2=[1.0],
tree_complexity=[0.5],
min_node_weight=[1.0],
logits_dimension=3,
split_type='inequality')
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) needs to validate that each value in `stats_summary_indices` is in range.
### Patches
We have patched the issue in GitHub commit [e84c975313e8e8e38bb2ea118196369c45c51378](https://github.com/tensorflow/tensorflow/commit/e84c975313e8e8e38bb2ea118196369c45c51378).
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-r4c4-5fpq-56wg'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37664'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/e84c975313e8e8e38bb2ea118196369c45c51378'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T13:46:31Z', 'nvd_published_at': '2021-08-12T21:15:00Z'}
|
1.4.0
|
GHSA-39xg-8p43-h76x
|
2023-06-13T20:28:35Z
|
2021-08-25T20:51:40Z
| null |
['CVE-2020-36203']
|
Data races in reffers
|
ARefss<'a, V> is a type that is assumed to contain objects that are Send + Sync.
In the affected versions of this crate, Send/Sync traits are unconditionally implemented for ARefss<'a, V>.
By using the ARefss::map() API, we can insert a !Send or !Sync object into ARefss<'a, V>. After that, it is possible to create a data race to the inner object of ARefss<'a, V>, which can lead to undefined behavior & memory corruption.
The flaw was corrected in commit `6dd7ca0` by adding trait bound V: Send + Sync to ARefss::map() API.
|
[{'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': 'reffers'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.6.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36203'}, {'type': 'WEB', 'url': 'https://github.com/diwic/reffers-rs/issues/7'}, {'type': 'WEB', 'url': 'https://github.com/diwic/reffers-rs/commit/6dd7ca0d50f2464df708975cdafcfaeeb6d41c66'}, {'type': 'PACKAGE', 'url': 'https://github.com/diwic/reffers-rs'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0094.html'}]
|
{'cwe_ids': ['CWE-362', 'CWE-787'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:49:46Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-gmv4-vmx3-x9f3
|
2021-08-19T20:52:14Z
|
2021-08-25T20:49:37Z
| null |
['CVE-2020-35914']
|
Data races in lock_api
|
An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockWriteGuard unsoundness.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'lock_api'}, 'ecosystem_specific': {'affected_functions': ['lock_api::RwLockWriteGuard']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35914'}, {'type': 'WEB', 'url': 'https://github.com/Amanieu/parking_lot/pull/262'}, {'type': 'PACKAGE', 'url': 'https://github.com/Amanieu/parking_lot'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0070.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T20:52:14Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-pjxv-w3qj-j8m3
|
2021-08-31T21:00:58Z
|
2021-08-09T20:42:13Z
| null |
['CVE-2021-23415']
|
Directory Traversal in elFinder.AspNet
|
This affects the package elFinder.AspNet before 1.1.1.
The user-controlled file name is not properly sanitized before it is used to create a file system path.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'NuGet', 'name': 'elFinder.AspNet'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.1.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-23415'}, {'type': 'WEB', 'url': 'https://github.com/mguinness/elFinder.AspNet/commit/675049b39284a9e84f0915c71d688da8ebc7d720'}, {'type': 'PACKAGE', 'url': 'https://github.com/mguinness/elFinder.AspNet'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-DOTNET-ELFINDERASPNET-1315153'}]
|
{'cwe_ids': ['CWE-22'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-02T18:41:18Z', 'nvd_published_at': '2021-07-28T16:15:00Z'}
|
1.4.0
|
GHSA-p2q9-9cq6-h3jw
|
2023-06-13T20:11:33Z
|
2021-08-25T20:47:46Z
| null |
['CVE-2020-35877']
|
Out of bounds read in Ozone
|
An issue was discovered in the ozone crate through version 0.1.0 for Rust. Memory safety is violated because of out-of-bounds access.
|
[{'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-35877'}, {'type': 'PACKAGE', 'url': 'https://github.com/bqv/ozone'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0022.html'}]
|
{'cwe_ids': ['CWE-119'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:08:51Z', 'nvd_published_at': '2020-12-31T10:15:00Z'}
|
1.4.0
|
GHSA-h7qh-3h6f-w79p
|
2023-06-13T20:05:17Z
|
2021-08-25T20:49:41Z
| null |
['CVE-2020-35909']
|
Unexpected panic in multihash
|
In versions prior 0.11.3 it's possible to make from_slice panic by feeding it certain malformed input. It's never documented that from_slice (and from_bytes which wraps it) can panic, and its' return type (Result<Self, DecodeError>) suggests otherwise. In practice, from_slice/from_bytes is frequently used in networking code and is being called with unsanitized data from untrusted sources. This can allow attackers to cause DoS by causing an unexpected panic in the network client's code..
|
[{'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': 'multihash'}, 'ecosystem_specific': {'affected_functions': ['multihash::digests::MultihashGeneric::from_bytes', 'multihash::digests::MultihashRefGeneric::from_slice']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.11.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35909'}, {'type': 'WEB', 'url': 'https://github.com/multiformats/rust-multihash/pull/72'}, {'type': 'PACKAGE', 'url': 'https://github.com/multiformats/rust-multihash'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0068.html'}]
|
{'cwe_ids': ['CWE-20'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T20:51:29Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-23fq-q7hc-993r
|
2022-08-11T21:57:44Z
|
2021-08-30T17:22:53Z
| null |
['CVE-2021-38553']
|
HashiCorp Vault underlying database had excessively broad filesystem permissions from v1.4.0 until v1.8.0
|
HashiCorp Vault and Vault Enterprise 1.4.0 through 1.7.3 initialized an underlying database file associated with the Integrated Storage feature with excessively broad filesystem permissions. Fixed in Vault and Vault Enterprise 1.8.0.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/hashicorp/vault'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.4.0'}, {'fixed': '1.8.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-38553'}, {'type': 'WEB', 'url': 'https://discuss.hashicorp.com/t/hcsec-2021-20-vault-s-integrated-storage-backend-database-file-may-have-excessively-broad-permissions/28168'}, {'type': 'PACKAGE', 'url': 'https://github.com/hashicorp/vault/'}, {'type': 'WEB', 'url': 'https://security.gentoo.org/glsa/202207-01'}]
|
{'cwe_ids': ['CWE-281'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-30T17:16:42Z', 'nvd_published_at': '2021-08-13T16:15:00Z'}
|
1.4.0
|
GHSA-85j6-f8j6-q26x
|
2023-06-13T19:59:50Z
|
2021-08-25T20:48:12Z
| null |
['CVE-2020-35894']
|
Unaligned references in Obstack
|
Obstack generates unaligned references for types that require a large alignment.
|
[{'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': 'obstack'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.1.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35894'}, {'type': 'WEB', 'url': 'https://github.com/petertodd/rust-obstack/issues/4'}, {'type': 'PACKAGE', 'url': 'https://github.com/petertodd/rust-obstack'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0040.html'}]
|
{'cwe_ids': ['CWE-706'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:06:51Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-hpcx-3pw8-g3j2
|
2022-06-14T20:23:55Z
|
2021-08-25T20:54:22Z
| null |
['CVE-2021-29937']
|
Free of uninitialized memory in telemetry
|
An issue was discovered in the telemetry crate through 0.1.2 for Rust. There is a drop of uninitialized memory if a value.clone() call panics within misc::vec_with_size()
|
[{'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': 'telemetry'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.1.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-29937'}, {'type': 'WEB', 'url': 'https://github.com/Yoric/telemetry.rs/issues/45'}, {'type': 'WEB', 'url': 'https://github.com/Yoric/telemetry.rs/commit/2820cf12f2e08645fd6d1f15b4a90a54d6082a81'}, {'type': 'PACKAGE', 'url': 'https://github.com/Yoric/telemetry.rs'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0046.html'}]
|
{'cwe_ids': ['CWE-908'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:09:26Z', 'nvd_published_at': '2021-04-01T05:15:00Z'}
|
1.4.0
|
GHSA-69gw-hgj3-45m7
|
2023-06-13T21:37:37Z
|
2021-08-25T20:43:58Z
| null |
['CVE-2019-15554']
|
Memory corruption in smallvec
|
Attempting to call grow on a spilled SmallVec with a value less than the current capacity causes corruption of memory allocator data structures. An attacker that controls the value passed to grow may exploit this flaw to obtain memory contents or gain remote code execution.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'smallvec'}, 'ecosystem_specific': {'affected_functions': ['smallvec::SmallVec::grow']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.6.3'}, {'fixed': '0.6.10'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-15554'}, {'type': 'WEB', 'url': 'https://github.com/servo/rust-smallvec/issues/149'}, {'type': 'PACKAGE', 'url': 'https://github.com/servo/rust-smallvec'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0012.html'}]
|
{'cwe_ids': ['CWE-787'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:23:44Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-8hfj-xrj2-pm22
|
2023-08-04T18:38:54Z
|
2021-08-25T20:54:00Z
| null |
['CVE-2021-3450']
|
Certificate check bypass in openssl-src
|
The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a "purpose" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named "purpose" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'openssl-src'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '111.11.0'}, {'fixed': '111.15.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3450'}, {'type': 'WEB', 'url': 'https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf'}, {'type': 'WEB', 'url': 'https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=2a40b7bc7b94dd7de897a74571e7024f0cf0d63b'}, {'type': 'PACKAGE', 'url': 'https://github.com/alexcrichton/openssl-src-rs'}, {'type': 'WEB', 'url': 'https://kb.pulsesecure.net/articles/Pulse_Security_Advisories/SA44845'}, {'type': 'WEB', 'url': 'https://kc.mcafee.com/corporate/index?page=content&id=SB10356'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CCBFLLVQVILIVGZMBJL3IXZGKWQISYNP/'}, {'type': 'WEB', 'url': 'https://mta.openssl.org/pipermail/openssl-announce/2021-March/000198.html'}, {'type': 'WEB', 'url': 'https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2021-0013'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0056.html'}, {'type': 'WEB', 'url': 'https://security.FreeBSD.org/advisories/FreeBSD-SA-21:07.openssl.asc'}, {'type': 'WEB', 'url': 'https://security.gentoo.org/glsa/202103-03'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20210326-0006/'}, {'type': 'WEB', 'url': 'https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-openssl-2021-GHY28dJd'}, {'type': 'WEB', 'url': 'https://www.openssl.org/news/secadv/20210325.txt'}, {'type': 'WEB', 'url': 'https://www.oracle.com//security-alerts/cpujul2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuApr2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuapr2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujul2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2021.html'}, {'type': 'WEB', 'url': 'https://www.tenable.com/security/tns-2021-05'}, {'type': 'WEB', 'url': 'https://www.tenable.com/security/tns-2021-08'}, {'type': 'WEB', 'url': 'https://www.tenable.com/security/tns-2021-09'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/03/27/1'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/03/27/2'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/03/28/3'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2021/03/28/4'}]
|
{'cwe_ids': ['CWE-295'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:22:00Z', 'nvd_published_at': '2021-03-25T15:15:00Z'}
|
1.4.0
|
GHSA-rg4m-gww5-7p47
|
2021-08-19T17:14:41Z
|
2021-08-25T20:54:18Z
| null |
['CVE-2021-29936']
|
Free of uninitialized memory in adtensor
|
An issue was discovered in the adtensor crate through 0.0.3 for Rust. There is a drop of uninitialized memory via the FromIterator implementation for Vector and Matrix.
|
[{'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': 'adtensor'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.0.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-29936'}, {'type': 'WEB', 'url': 'https://github.com/charles-r-earp/adtensor/issues/4'}, {'type': 'PACKAGE', 'url': 'https://github.com/charles-r-earp/adtensor'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0045.html'}]
|
{'cwe_ids': ['CWE-908'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:14:41Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-qjj8-32p7-h289
|
2021-08-24T12:42:21Z
|
2021-08-25T14:43:04Z
| null |
['CVE-2021-37653']
|
Division by 0 in `ResourceGather`
|
### Impact
An attacker can trigger a crash via a floating point exception in `tf.raw_ops.ResourceGather`:
```python
import tensorflow as tf
tensor = tf.constant(value=[[]],shape=(0,1),dtype=tf.uint32)
v = tf.Variable(tensor)
tf.raw_ops.ResourceGather(
resource=v.handle,
indices=[0],
dtype=tf.uint32,
batch_dims=1,
validate_indices=False)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L725-L731) computes the value of a value, `batch_size`, and then divides by it without checking that this value is not 0.
### Patches
We have patched the issue in GitHub commit [ac117ee8a8ea57b73d34665cdf00ef3303bc0b11](https://github.com/tensorflow/tensorflow/commit/ac117ee8a8ea57b73d34665cdf00ef3303bc0b11).
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-qjj8-32p7-h289'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37653'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/ac117ee8a8ea57b73d34665cdf00ef3303bc0b11'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow/'}]
|
{'cwe_ids': ['CWE-369'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T12:41:26Z', 'nvd_published_at': '2021-08-12T18:15:00Z'}
|
1.4.0
|
GHSA-r67m-m8c7-jp83
|
2022-08-16T18:40:56Z
|
2021-08-30T16:11:33Z
| null |
['CVE-2021-39173']
|
Cachet vulnerable to forced reinstall
|
### Impact
Authenticated users, regardless of their privileges (_User_ or _Admin_), can trick Cachet and install the instance again, leading to arbitrary code execution on the server.
### Patches
This issue was addressed by improving the middleware `ReadyForUse`, which now performs a stricter validation of the instance name.
### Workarounds
Only allow trusted source IP addresses to access to the administration dashboard.
### References
- https://blog.sonarsource.com/cachet-code-execution-via-laravel-configuration-injection
### For more information
If you have any questions or comments about this advisory, you can contact:
- The original reporters, by sending an email to vulnerability.research [at] sonarsource.com;
- The maintainers, by opening an issue on this repository.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'cachethq/cachet'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.5.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/fiveai/Cachet/security/advisories/GHSA-r67m-m8c7-jp83'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39173'}, {'type': 'WEB', 'url': 'https://blog.sonarsource.com/cachet-code-execution-via-laravel-configuration-injection/'}, {'type': 'PACKAGE', 'url': 'https://github.com/fiveai/Cachet'}, {'type': 'WEB', 'url': 'https://github.com/fiveai/Cachet/releases/tag/v2.5.1'}]
|
{'cwe_ids': ['CWE-704'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-27T23:34:37Z', 'nvd_published_at': '2021-08-27T23:15:00Z'}
|
1.4.0
|
GHSA-vq23-5h4f-vwpv
|
2022-06-15T19:41:47Z
|
2021-08-25T21:01:35Z
| null |
['CVE-2020-36212']
|
Update unsound DrainFilter and RString::retain
|
An issue was discovered in the abi_stable crate before 0.9.1 for Rust. DrainFilter lacks soundness because of a double drop.
|
[{'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': 'abi_stable'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.9.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36212'}, {'type': 'WEB', 'url': 'https://github.com/rodrimati1992/abi_stable_crates/issues/44'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0105.html'}]
|
{'cwe_ids': ['CWE-672'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-07-26T17:17:19Z', 'nvd_published_at': '2021-01-26T18:15:00Z'}
|
1.4.0
|
GHSA-39vw-qp34-rmwf
|
2023-06-13T21:03:35Z
|
2021-08-25T21:00:18Z
| null |
[]
|
Uncontrolled recursion leads to abort in deserialization
|
Affected versions of this crate did not properly check for recursion while deserializing aliases. This allows an attacker to make a YAML file with an alias referring to itself causing an abort. The flaw was corrected by checking the recursion depth.
|
[]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'serde_yaml'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.6.0-rc1'}, {'fixed': '0.8.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/dtolnay/serde-yaml/pull/105'}, {'type': 'WEB', 'url': 'https://github.com/dtolnay/serde-yaml/commit/b93aff6e904cffbbfd1f421b82f6dcc5ca19a4fd'}, {'type': 'PACKAGE', 'url': 'https://github.com/dtolnay/serde-yaml'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2018-0005.html'}]
|
{'cwe_ids': ['CWE-674'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-06T17:45:03Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-566x-hhrf-qf8m
|
2023-06-13T19:51:43Z
|
2021-08-25T20:50:30Z
| null |
['CVE-2020-35923']
|
ordered_float:NotNan may contain NaN after panic in assignment operators
|
After using an assignment operators such as NotNan::add_assign, NotNan::mul_assign, etc., it was possible for the resulting NotNan value to contain a NaN. This could cause undefined behavior in safe code, because the safe NotNan::cmp method contains internal unsafe code that assumes the value is never NaN. (It could also cause undefined behavior in third-party unsafe code that makes the same assumption, as well as logic errors in safe code.)
This was mitigated starting in version 0.4.0, by panicking if the assigned value is NaN. However, in affected versions from 0.4.0 onward, code that uses the NotNan value during unwinding, or that continues after catching the panic, could still observe the invalid value and trigger undefined behavior.
The flaw is fully corrected in versions 1.1.1 and 2.0.1, by ensuring that the assignment operators panic without modifying the operand, if the result would be NaN.
|
[{'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': 'ordered-float'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.0.0'}, {'fixed': '2.0.1'}]}], 'versions': ['2.0.0']}, {'package': {'ecosystem': 'crates.io', 'name': 'ordered-float'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.2.2'}, {'fixed': '1.1.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35923'}, {'type': 'WEB', 'url': 'https://github.com/reem/rust-ordered-float/pull/71'}, {'type': 'WEB', 'url': 'https://github.com/reem/rust-ordered-float/commit/c55cda301c943270b7eb2b4765bedbcce56edb90'}, {'type': 'WEB', 'url': 'https://github.com/reem/rust-ordered-float/commit/da4a8dd49300740a434c095a9c4b408d2415cc08'}, {'type': 'PACKAGE', 'url': 'https://github.com/reem/rust-ordered-float'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0082.html'}]
|
{'cwe_ids': ['CWE-460'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:54:34Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-j8qq-58cr-8cc7
|
2022-05-05T00:44:22Z
|
2021-08-25T20:52:53Z
| null |
['CVE-2021-25905']
|
Out of bounds read in bra
|
Buffered Random Access (BRA) provides easy random memory access to a sequential source of data in Rust. This is achieved by greedily retaining all memory read from a given source. Buffered Random Access (BRA) provides easy random memory access to a sequential source of data in Rust. An issue was discovered in the bra crate before 0.1.1 for Rust. It lacks soundness because it can read uninitialized memory.
|
[{'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': 'bra'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.1.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-25905'}, {'type': 'WEB', 'url': 'https://github.com/Enet4/bra-rs/issues/1'}, {'type': 'WEB', 'url': 'https://github.com/Enet4/bra-rs/commit/aabf5562f8c6374ab30f615b28e0cff9b5c79e5f'}, {'type': 'PACKAGE', 'url': 'https://github.com/Enet4/bra-rs'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0008.html'}]
|
{'cwe_ids': ['CWE-125', 'CWE-908'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:46:05Z', 'nvd_published_at': '2021-01-26T18:16:00Z'}
|
1.4.0
|
GHSA-w3g5-2848-2v8r
|
2021-08-24T18:04:25Z
|
2021-08-25T20:57:05Z
| null |
['CVE-2020-36471']
|
Data races in generator
|
The `Generator` type is an iterable which uses a generator function that yields
values. In affected versions of the crate, the provided function yielding values
had no `Send` bounds despite the `Generator` itself implementing `Send`.
The generator function lacking a `Send` bound means that types that are
dangerous to send across threads such as `Rc` could be sent as part of a
generator, potentially leading to data races.
This flaw was fixed in commit [`f7d120a3b`](https://github.com/Xudong-Huang/generator-rs/commit/f7d120a3b724d06a7b623d0a4306acf8f78cb4f0)
by enforcing that the generator function be bound by `Send`.
|
[{'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': 'generator'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.7.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36471'}, {'type': 'WEB', 'url': 'https://github.com/Xudong-Huang/generator-rs/issues/27'}, {'type': 'WEB', 'url': 'https://github.com/Xudong-Huang/generator-rs/commit/f7d120a3b724d06a7b623d0a4306acf8f78cb4f0'}, {'type': 'PACKAGE', 'url': 'https://github.com/Xudong-Huang/generator-rs'}, {'type': 'WEB', 'url': 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/generator/RUSTSEC-2020-0151.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0151.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T20:33:21Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-3gp6-hhfw-4gqx
|
2021-06-28T19:05:25Z
|
2021-08-13T15:22:24Z
| null |
['CVE-2010-3300']
|
Padding oracle attacks
|
It was found that all OWASP ESAPI for Java up to version 2.0 RC2 are vulnerable to padding oracle attacks.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.owasp.esapi:esapi'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.0GA'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2010-3300'}, {'type': 'WEB', 'url': 'https://seclists.org/oss-sec/2010/q3/357'}, {'type': 'WEB', 'url': 'https://www.usenix.org/legacy/events/woot10/tech/full_papers/Rizzo.pdf'}]
|
{'cwe_ids': ['CWE-649'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-06-24T20:07:33Z', 'nvd_published_at': '2021-06-22T12:15:00Z'}
|
1.4.0
|
GHSA-vhfr-v4w9-45v8
|
2023-06-13T20:28:01Z
|
2021-08-25T20:44:51Z
| null |
['CVE-2019-16142']
|
Improper Input Validation in renderdoc
|
Affected versions of this crate exposed several methods which took self by immutable reference, despite the requesting the RenderDoc API to set a mutable value internally. This is technically unsound and calling these methods from multiple threads without synchronization could lead to unexpected and unpredictable behavior. The flaw was corrected in release 0.5.0.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'renderdoc'}, 'ecosystem_specific': {'affected_functions': ['renderdoc::api::RenderDocV110::trigger_multi_frame_capture', 'renderdoc::api::RenderDocV120::set_capture_file_comments']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.5.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-16142'}, {'type': 'WEB', 'url': 'https://github.com/ebkalderon/renderdoc-rs/pull/32'}, {'type': 'PACKAGE', 'url': 'https://github.com/ebkalderon/renderdoc-rs'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0018.html'}]
|
{'cwe_ids': ['CWE-20'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:22:34Z', 'nvd_published_at': '2019-09-09T12:15:00Z'}
|
1.4.0
|
GHSA-8gmx-cpcg-f8h5
|
2023-06-13T17:37:47Z
|
2021-08-25T20:55:11Z
| null |
['CVE-2021-30455']
|
Double-free in id-map
|
The clone_from implementation for IdMap drops the values present in the map and then begins cloning values from the other map. If a .clone() call pancics, then the afformentioned dropped elements can be freed again.
get_or_insert
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.
remove_set
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-30455'}, {'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:17Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-f2rp-j8hv-g5gx
|
2021-08-26T16:24:16Z
|
2021-08-30T16:25:26Z
| null |
['CVE-2021-38713']
|
Cross-site scripting in imgURL
|
imgURL 2.31 allows XSS via an X-Forwarded-For HTTP header.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'helloxz/imgurl'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '2.31'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-38713'}, {'type': 'WEB', 'url': 'https://github.com/helloxz/imgurl/issues/72'}, {'type': 'PACKAGE', 'url': 'https://github.com/helloxz/imgurl'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-26T16:24:16Z', 'nvd_published_at': '2021-08-16T04:15:00Z'}
|
1.4.0
|
GHSA-j2r6-2m5c-vgh5
|
2021-08-19T21:20:52Z
|
2021-08-25T20:45:20Z
| null |
['CVE-2019-25005']
|
Counter overflow in chacha20
|
An issue was discovered in the chacha20 crate before 0.2.3 for Rust. A ChaCha20 counter overflow makes it easier for attackers to determine plaintext.
|
[{'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': 'chacha20'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.2.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-25005'}, {'type': 'WEB', 'url': 'https://github.com/RustCrypto/stream-ciphers/pull/64'}, {'type': 'PACKAGE', 'url': 'https://github.com/RustCrypto/stream-ciphers/tree/master/chacha20'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0029.html'}]
|
{'cwe_ids': ['CWE-190'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:20:52Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-5955-9wpr-37jh
|
2021-08-31T16:02:32Z
|
2021-08-31T16:05:05Z
| null |
['CVE-2021-37713']
|
Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization
|
### Impact
Arbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution
node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory.
This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\path`. If the drive letter does not match the extraction target, for example `D:\extraction\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory.
Additionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path.
This only affects users of `node-tar` on Windows systems.
### Patches
4.4.18 || 5.0.10 || 6.1.9
### Workarounds
There is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does.
Users are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.
### Fix
The fixed versions strip path roots from all paths prior to being resolved against the extraction target folder, even if such paths are not "absolute".
Additionally, a path starting with a drive letter and then two dots, like `c:../`, would bypass the check for `..` path portions. This is checked properly in the patched versions.
Finally, a defense in depth check is added, such that if the `entry.absolute` is outside of the extraction taret, and we are not in preservePaths:true mode, a warning is raised on that entry, and it is skipped. Currently, it is believed that this check is redundant, but it did catch some oversights in development.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'tar'}, 'ecosystem_specific': {'affected_functions': ['tar.Unpack']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.4.18'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'tar'}, 'ecosystem_specific': {'affected_functions': ['tar.Unpack']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '5.0.0'}, {'fixed': '5.0.10'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'tar'}, 'ecosystem_specific': {'affected_functions': ['tar.Unpack']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '6.0.0'}, {'fixed': '6.1.9'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/npm/node-tar/security/advisories/GHSA-5955-9wpr-37jh'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37713'}, {'type': 'WEB', 'url': 'https://github.com/isaacs/node-tar/commit/52b09e309bcae0c741a7eb79a17ef36e7828b946'}, {'type': 'WEB', 'url': 'https://github.com/isaacs/node-tar/commit/82eac952f7c10765969ed464e549375854b26edc'}, {'type': 'WEB', 'url': 'https://github.com/isaacs/node-tar/commit/875a37e3ec031186fc6599f6807341f56c584598'}, {'type': 'WEB', 'url': 'https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf'}, {'type': 'PACKAGE', 'url': 'https://github.com/npm/node-tar'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/package/tar'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2021.html'}]
|
{'cwe_ids': ['CWE-22'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-31T16:02:32Z', 'nvd_published_at': '2021-08-31T17:15:00Z'}
|
1.4.0
|
GHSA-6vmq-jh76-hq43
|
2022-06-14T22:22:47Z
|
2021-08-25T20:55:25Z
| null |
['CVE-2021-30454']
|
Uninitialized memory access in outer_cgi
|
An issue was discovered in the outer_cgi crate before 0.2.1 for Rust. A user-provided Read instance receives an uninitialized memory buffer from KeyValueReader.
|
[{'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': 'outer_cgi'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.2.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-30454'}, {'type': 'WEB', 'url': 'https://github.com/SolraBizna/outer_cgi/issues/1'}, {'type': 'WEB', 'url': 'https://github.com/SolraBizna/outer_cgi/commit/dd59b3066e616a08e756f72de8dc3ab11b7036c4'}, {'type': 'PACKAGE', 'url': 'https://github.com/SolraBizna/outer_cgi'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0051.html'}]
|
{'cwe_ids': ['CWE-119'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:03:35Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-c7fw-cr3w-wvfc
|
2023-06-13T16:51:44Z
|
2021-08-25T20:49:04Z
| null |
['CVE-2020-35886']
|
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:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/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-35886'}, {'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-362'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T20:56:00Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-q2gj-9r85-p832
|
2023-06-13T20:47:12Z
|
2021-08-25T20:48:09Z
| null |
['CVE-2020-35879']
|
Data races in rulinalg
|
The affected version of rulinalg has incorrect lifetime boundary definitions for RowMut::raw_slice and RowMut::raw_slice_mut. They do not conform with Rust's borrowing rule and allows the user to create multiple mutable references to the same location. This may result in unexpected calculation result and data race if both references are used at the same time.
|
[{'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': 'rulinalg'}, 'ecosystem_specific': {'affected_functions': ['rulinalg::matrix::RowMut::raw_slice', 'rulinalg::matrix::RowMut::raw_slice_mut']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.4.0'}, {'last_affected': '0.4.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35879'}, {'type': 'WEB', 'url': 'https://github.com/AtheMathmo/rulinalg/issues/201'}, {'type': 'PACKAGE', 'url': 'https://github.com/AtheMathmo/rulinalg'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0023.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:06:56Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-2c25-xfpq-8w9r
|
2021-07-01T21:48:01Z
|
2021-08-13T15:22:14Z
| null |
['CVE-2021-33348']
|
Cross-site scripting in jfinal
|
An issue was discovered in JFinal framework v4.9.10 and below. The "set" method of the "Controller" class of jfinal framework is not strictly filtered, which will lead to XSS vulnerabilities in some cases.
|
[{'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': 'com.jfinal:jfinal'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.9.11'}]}], 'database_specific': {'last_known_affected_version_range': '<= 4.9.10'}}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-33348'}, {'type': 'WEB', 'url': 'https://github.com/jfinal/jfinal/issues/188'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-06-25T15:28:12Z', 'nvd_published_at': '2021-06-24T15:15:00Z'}
|
1.4.0
|
GHSA-pfrg-w49c-8432
|
2021-07-27T15:01:39Z
|
2021-08-02T17:26:23Z
| null |
['CVE-2020-0768']
|
Out-of-bounds write in ChakraCore
|
A remote code execution vulnerability exists in the way the scripting engine handles objects in memory in Microsoft browsers, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0823, CVE-2020-0825, CVE-2020-0826, CVE-2020-0827, CVE-2020-0828, CVE-2020-0829, CVE-2020-0830, CVE-2020-0831, CVE-2020-0832, CVE-2020-0833, CVE-2020-0848.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'NuGet', 'name': 'Microsoft.ChakraCore'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.11.17'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-0768'}, {'type': 'WEB', 'url': 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0768'}]
|
{'cwe_ids': ['CWE-787'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-07-27T15:01:39Z', 'nvd_published_at': '2020-03-12T16:15:00Z'}
|
1.4.0
|
GHSA-vrw4-w73r-6mm8
|
2021-09-13T20:30:25Z
|
2021-08-30T16:12:49Z
| null |
['CVE-2021-39168']
|
TimelockController vulnerability in OpenZeppelin Contracts
|
### Impact
A vulnerability in `TimelockController` allowed an actor with the executor role to take immediate control of the timelock, by resetting the delay to 0 and escalating privileges, thus gaining unrestricted access to assets held in the contract. Instances with the executor role set to "open" allow anyone to use the executor role, thus leaving the timelock at risk of being taken over by an attacker.
### Patches
A fix is included in the following releases of `@openzeppelin/contracts` and `@openzeppelin/contracts-upgradeable`:
- 4.3.1
- 3.4.2
- 3.4.2-solc-0.7
Deployed instances of `TimelockController` should be replaced with a fixed version by migrating all assets, ownership, and roles.
### Workarounds
Revoke the executor role from accounts not strictly under the team's control. We recommend revoking all executors that are not also proposers. When applying this mitigation, ensure there is at least one proposer and executor remaining.
### References
[Post-mortem](https://forum.openzeppelin.com/t/timelockcontroller-vulnerability-postmortem/14958).
### Credits
The issue was identified by an anonymous white hat hacker through [Immunefi](https://immunefi.com/).
### For more information
If you have any questions or comments about this advisory, or need assistance executing the mitigation, email us at security@openzeppelin.com.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'npm', 'name': '@openzeppelin/contracts-upgradeable'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.0.0'}, {'fixed': '4.3.1'}]}]}, {'package': {'ecosystem': 'npm', 'name': '@openzeppelin/contracts-upgradeable'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.3.0'}, {'fixed': '3.4.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/OpenZeppelin/openzeppelin-contracts-upgradeable/security/advisories/GHSA-vrw4-w73r-6mm8'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39168'}, {'type': 'WEB', 'url': 'https://github.com/OpenZeppelin/openzeppelin-contracts/commit/cec4f2ef57495d8b1742d62846da212515d99dd5'}, {'type': 'PACKAGE', 'url': 'https://github.com/OpenZeppelin/openzeppelin-contracts-upgradeabl'}, {'type': 'WEB', 'url': 'https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/CHANGELOG.md#431'}]
|
{'cwe_ids': ['CWE-269'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-27T12:57:31Z', 'nvd_published_at': '2021-08-27T00:15:00Z'}
|
1.4.0
|
GHSA-6cj2-92m5-7mvp
|
2021-10-08T21:20:09Z
|
2021-08-03T16:48:46Z
| null |
[]
|
Improperly Controlled Modification of Object Prototype Attributes
|
### Impact
The software receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.
### Patches
`think-config@1.1.3` patched it, anyone used `think-config` should upgrade to `>=1.1.3` version.
### References
https://cwe.mitre.org/data/definitions/1321.html
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [thinkjs/thinkjs](https://github.com/thinkjs/thinkjs)
* Email us at [i@imnerd.org](mailto:i@imnerd.org)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'think-config'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.1.3'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/thinkjs/think-config/security/advisories/GHSA-6cj2-92m5-7mvp'}, {'type': 'PACKAGE', 'url': 'https://github.com/thinkjs/think-config/'}]
|
{'cwe_ids': ['CWE-1321'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-02T23:23:16Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-r628-mhmh-qjhw
|
2023-03-09T16:44:57Z
|
2021-08-03T19:00:40Z
| null |
['CVE-2021-32803']
|
Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning
|
### Impact
Arbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution
`node-tar` aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary `stat` calls to determine whether a given path is a directory, paths are cached when directories are created.
This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory. This order of operations resulted in the directory being created and added to the `node-tar` directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where `node-tar` checks for symlinks occur.
By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass `node-tar` symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite.
This issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.
### Patches
3.2.3 || 4.4.15 || 5.0.7 || 6.1.2
### Workarounds
Users may work around this vulnerability without upgrading by creating a custom `filter` method which prevents the extraction of symbolic links.
```js
const tar = require('tar')
tar.x({
file: 'archive.tgz',
filter: (file, entry) => {
if (entry.type === 'SymbolicLink') {
return false
} else {
return true
}
}
})
```
Users are encouraged to upgrade to the latest patch versions, rather than attempt to sanitize tar input themselves.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'tar'}, 'ecosystem_specific': {'affected_functions': ['tar.Unpack']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.2.3'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'tar'}, 'ecosystem_specific': {'affected_functions': ['tar.Unpack']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.0.0'}, {'fixed': '4.4.15'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'tar'}, 'ecosystem_specific': {'affected_functions': ['tar.Unpack']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '5.0.0'}, {'fixed': '5.0.7'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'tar'}, 'ecosystem_specific': {'affected_functions': ['tar.Unpack']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '6.0.0'}, {'fixed': '6.1.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/npm/node-tar/security/advisories/GHSA-r628-mhmh-qjhw'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-32803'}, {'type': 'WEB', 'url': 'https://github.com/isaacs/node-tar/commit/46fe35083e2676e31c4e0a81639dce6da7aaa356'}, {'type': 'WEB', 'url': 'https://github.com/isaacs/node-tar/commit/5987d9a41f6bfbf1ddab1098e1fdcf1a5618f571'}, {'type': 'WEB', 'url': 'https://github.com/isaacs/node-tar/commit/85d3a942b4064e4ff171f91696fced7975167349'}, {'type': 'WEB', 'url': 'https://github.com/isaacs/node-tar/commit/9dbdeb6df8e9dbd96fa9e84341b9d74734be6c20'}, {'type': 'WEB', 'url': 'https://github.com/npm/node-tar/commit/9dbdeb6df8e9dbd96fa9e84341b9d74734be6c20'}, {'type': 'WEB', 'url': 'https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf'}, {'type': 'PACKAGE', 'url': 'https://github.com/isaacs/node-tar'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/advisories/1771'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/package/tar'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2021.html'}]
|
{'cwe_ids': ['CWE-22', 'CWE-23', 'CWE-59'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-03T18:59:57Z', 'nvd_published_at': '2021-08-03T19:15:00Z'}
|
1.4.0
|
GHSA-h6gg-fvf5-qgwf
|
2021-08-24T18:04:01Z
|
2021-08-25T20:55:41Z
|
2021-08-24T18:04:01Z
|
[]
|
Data races in generator
|
The `Generator` type is an iterable which uses a generator function that yields
values. In affected versions of the crate, the provided function yielding values
had no `Send` bounds despite the `Generator` itself implementing `Send`.
The generator function lacking a `Send` bound means that types that are
dangerous to send across threads such as `Rc` could be sent as part of a
generator, potentially leading to data races.
This flaw was fixed in commit [`f7d120a3b`](https://github.com/Xudong-Huang/generator-rs/commit/f7d120a3b724d06a7b623d0a4306acf8f78cb4f0)
by enforcing that the generator function be bound by `Send`.
|
[]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'generator'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.7.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/Xudong-Huang/generator-rs/issues/27'}, {'type': 'WEB', 'url': 'https://github.com/Xudong-Huang/generator-rs/commit/f7d120a3b724d06a7b623d0a4306acf8f78cb4f0'}, {'type': 'PACKAGE', 'url': 'https://github.com/Xudong-Huang/generator-rs'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0151.html'}]
|
{'cwe_ids': ['CWE-362'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T21:35:57Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-64gv-qg2v-vxv6
|
2021-08-19T21:21:48Z
|
2021-08-25T20:45:04Z
| null |
['CVE-2020-25793']
|
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 From<InlineArray<A, 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': 'sized-chunks'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.6.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-25793'}, {'type': 'WEB', 'url': 'https://github.com/bodil/sized-chunks/issues/11'}, {'type': 'PACKAGE', 'url': 'https://github.com/bodil/sized-chunks'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0041.html'}]
|
{'cwe_ids': ['CWE-129'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:21:48Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-fc38-mxwr-pfhx
|
2021-08-23T17:24:12Z
|
2021-08-23T19:43:00Z
| null |
['CVE-2021-37710']
|
Cross-Site Scripting via SVG media files
|
### Impact
Cross-Site Scripting via SVG media files
### Patches
We recommend updating to the current version 6.4.3.1. You can get the update to 6.4.3.1 regularly via the Auto-Updater or directly via the download overview.
https://www.shopware.com/en/download/#shopware-6
### Workarounds
For older versions of 6.1, 6.2, and 6.3, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'shopware/core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.4.3.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.4.3.0'}}, {'package': {'ecosystem': 'Packagist', 'name': 'shopware/platform'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.4.3.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.4.3.0'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/shopware/platform/security/advisories/GHSA-fc38-mxwr-pfhx'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37710'}, {'type': 'WEB', 'url': 'https://github.com/shopware/platform/commit/abe9f69e1f667800f974acccd3047b4930e4b423'}, {'type': 'PACKAGE', 'url': 'https://github.com/shopware/platform'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T17:24:12Z', 'nvd_published_at': '2021-08-16T23:15:00Z'}
|
1.4.0
|
GHSA-m2pf-hprp-3vqm
|
2023-06-13T18:18:15Z
|
2021-08-25T20:44:43Z
| null |
['CVE-2019-16138']
|
Use after free in image
|
Affected versions of this crate would call Vec::set_len on an uninitialized vector with user-provided type parameter, in an interface of the HDR image format decoder. They would then also call other code that could panic before initializing all instances.
This could run Drop implementations on uninitialized types, equivalent to use-after-free, and allow an attacker arbitrary code execution.
Two different fixes were applied. It is possible to conserve the interface by ensuring proper initialization before calling Vec::set_len. Drop is no longer called in case of panic, though.
Starting from version 0.22, a breaking change to the interface requires callers to pre-allocate the output buffer and pass a mutable slice instead, avoiding all unsafe code.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'image'}, 'ecosystem_specific': {'affected_functions': ['image::hdr::HDRDecoder::read_image_transform']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.10.2'}, {'fixed': '0.21.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2019-16138'}, {'type': 'WEB', 'url': 'https://github.com/image-rs/image/pull/985'}, {'type': 'PACKAGE', 'url': 'https://github.com/image-rs/image'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2019-0014.html'}]
|
{'cwe_ids': ['CWE-416'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:22:44Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-8h4j-vm3r-vcq3
|
2021-08-19T21:08:47Z
|
2021-08-25T20:47:48Z
| null |
['CVE-2020-35870']
|
Use after free in rusqlite
|
An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via an Auxdata API 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-35870'}, {'type': 'WEB', 'url': 'https://github.com/rusqlite/rusqlite/commit/2ef3628dac35aeba0a97d5fb3a57746b4e1d62b3'}, {'type': 'PACKAGE', 'url': 'https://github.com/rusqlite/rusqlite'}, {'type': 'WEB', 'url': 'https://github.com/rusqlite/rusqlite/releases/tag/0.23.0'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0014.html'}]
|
{'cwe_ids': ['CWE-416'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:08:47Z', 'nvd_published_at': '2020-12-31T10:15:00Z'}
|
1.4.0
|
GHSA-3hj2-hh36-hv9v
|
2023-06-13T22:11:43Z
|
2021-08-25T20:51:56Z
| null |
['CVE-2020-36220']
|
Data race in va-ts
|
In the affected versions of this crate, Demuxer<T> unconditionally implemented Send with no trait bounds on T. This allows sending a non-Send type T across thread boundaries, which can cause undefined behavior like unlocking a mutex from a thread that didn't lock the mutex, or memory corruption from data race. The flaw was corrected in commit `0562cbf` by adding a T: Send bound to the Send impl for Demuxer<T>.
|
[{'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': 'va-ts'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.0.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36220'}, {'type': 'WEB', 'url': 'https://github.com/video-audio/va-ts/issues/4'}, {'type': 'PACKAGE', 'url': 'https://github.com/video-audio/va-ts'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0114.html'}]
|
{'cwe_ids': ['CWE-662', 'CWE-667', 'CWE-787'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:47:06Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-9r2w-394v-53qc
|
2021-08-31T16:01:50Z
|
2021-08-31T16:05:27Z
| null |
['CVE-2021-37701']
|
Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links
|
### Impact
Arbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution
`node-tar` aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created.
This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory, where the symlink and directory names in the archive entry used backslashes as a path separator on posix systems. The cache checking logic used both `\` and `/` characters as path separators, however `\` is a valid filename character on posix systems.
By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite.
Additionally, a similar confusion could arise on case-insensitive filesystems. If a tar archive contained a directory at `FOO`, followed by a symbolic link named `foo`, then on case-insensitive file systems, the creation of the symbolic link would remove the directory from the filesystem, but _not_ from the internal directory cache, as it would not be treated as a cache hit. A subsequent file entry within the `FOO` directory would then be placed in the target of the symbolic link, thinking that the directory had already been created.
These issues were addressed in releases 4.4.16, 5.0.8 and 6.1.7.
The v3 branch of `node-tar` has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of `node-tar`. If this is not possible, a workaround is available below.
### Patches
4.4.16 || 5.0.8 || 6.1.7
### Workarounds
Users may work around this vulnerability without upgrading by creating a custom filter method which prevents the extraction of symbolic links.
```js
const tar = require('tar')
tar.x({
file: 'archive.tgz',
filter: (file, entry) => {
if (entry.type === 'SymbolicLink') {
return false
} else {
return true
}
}
})
```
Users are encouraged to upgrade to the latest patched versions, rather than attempt to sanitize tar input themselves.
### Fix
The problem is addressed in the following ways:
1. All paths are normalized to use `/` as a path separator, replacing `\` with `/` on Windows systems, and leaving `\` intact in the path on posix systems. This is performed in depth, at every level of the program where paths are consumed.
2. Directory cache pruning is performed case-insensitively. This _may_ result in undue cache misses on case-sensitive file systems, but the performance impact is negligible.
#### Caveat
Note that this means that the `entry` objects exposed in various parts of tar's API will now always use `/` as a path separator, even on Windows systems. This is not expected to cause problems, as `/` is a valid path separator on Windows systems, but _may_ result in issues if `entry.path` is compared against a path string coming from some other API such as `fs.realpath()` or `path.resolve()`.
Users are encouraged to always normalize paths using a well-tested method such as `path.resolve()` before comparing paths to one another.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'tar'}, 'ecosystem_specific': {'affected_functions': ['tar.Unpack']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.4.16'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'tar'}, 'ecosystem_specific': {'affected_functions': ['tar.Unpack']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '5.0.0'}, {'fixed': '5.0.8'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'tar'}, 'ecosystem_specific': {'affected_functions': ['tar.Unpack']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '6.0.0'}, {'fixed': '6.1.7'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/npm/node-tar/security/advisories/GHSA-9r2w-394v-53qc'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37701'}, {'type': 'WEB', 'url': 'https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf'}, {'type': 'PACKAGE', 'url': 'https://github.com/npm/node-tar'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2022/12/msg00023.html'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2021/dsa-5008'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/package/tar'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2021.html'}]
|
{'cwe_ids': ['CWE-22', 'CWE-59'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-31T16:01:50Z', 'nvd_published_at': '2021-08-31T17:15:00Z'}
|
1.4.0
|
GHSA-p8pq-r894-fm8f
|
2022-02-08T21:00:18Z
|
2021-08-25T14:47:57Z
| null |
['CVE-2021-39146']
|
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-39146](https://x-stream.github.io/CVE-2021-39146.html).
### Credits
Ceclin and YXXX from the Tencent Security Response Center found and reported the issue to XStream and provided the required information to reproduce it.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)
* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'com.thoughtworks.xstream:xstream'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.4.18'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/x-stream/xstream/security/advisories/GHSA-p8pq-r894-fm8f'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39146'}, {'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-39146.html'}]
|
{'cwe_ids': ['CWE-502'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T18:22:13Z', 'nvd_published_at': '2021-08-23T18:15:00Z'}
|
1.4.0
|
GHSA-3ccq-5vw3-2p6x
|
2022-02-08T20:44:12Z
|
2021-08-25T14:47:28Z
| null |
['CVE-2021-39149']
|
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-39149](https://x-stream.github.io/CVE-2021-39149.html).
### Credits
Lai Han of NSFOCUS security team 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-3ccq-5vw3-2p6x'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39149'}, {'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-39149.html'}]
|
{'cwe_ids': ['CWE-434', 'CWE-502'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T18:22:21Z', 'nvd_published_at': '2021-08-23T18:15:00Z'}
|
1.4.0
|
GHSA-j42v-6wpm-r847
|
2021-08-19T18:55:21Z
|
2021-08-25T20:50:26Z
| null |
['CVE-2020-35927']
|
Data races in thex
|
An issue was discovered in the thex crate through 2020-12-08 for Rust. Thex<T> allows cross-thread data races of non-Send 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': 'thex'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.1.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35927'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0090.html'}]
|
{'cwe_ids': ['CWE-662'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:55:21Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-88f9-7xxh-c688
|
2022-08-16T18:38:53Z
|
2021-08-30T16:11:43Z
| null |
['CVE-2021-39174']
|
Cachet configuration leak
|
### Impact
Authenticated users, regardless of their privileges (_User_ or _Admin_), can leak the value of any configuration entry of the dotenv file, e.g. the application secret (`APP_KEY`) and various passwords (email, database, etc).
### Patches
This issue was addressed by improving `UpdateConfigCommandHandler` and preventing the use of nested variables in the resulting dotenv configuration file.
### Workarounds
Only allow trusted source IP addresses to access to the administration dashboard.
### References
Further technical details are available at [https://blog.sonarsource.com/cachet-code-execution-via-laravel-configuration-injection](https://blog.sonarsource.com/cachet-code-execution-via-laravel-configuration-injection).
### For more information
If you have any questions or comments about this advisory, you can contact:
- The original reporters, by sending an email to vulnerability.research [at] sonarsource.com;
- The maintainers, by opening an issue on this repository.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'cachethq/cachet'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.5.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 2.5.0'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/fiveai/Cachet/security/advisories/GHSA-88f9-7xxh-c688'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39174'}, {'type': 'WEB', 'url': 'https://blog.sonarsource.com/cachet-code-execution-via-laravel-configuration-injection'}, {'type': 'PACKAGE', 'url': 'https://github.com/cachethq/Cachet'}, {'type': 'WEB', 'url': 'https://github.com/fiveai/Cachet/releases/tag/v2.5.1'}]
|
{'cwe_ids': ['CWE-75'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-27T23:34:07Z', 'nvd_published_at': '2021-08-28T00:15:00Z'}
|
1.4.0
|
GHSA-3jfq-g458-7qm9
|
2021-08-30T23:14:50Z
|
2021-08-03T19:06:36Z
| null |
['CVE-2021-32804']
|
Arbitrary File Creation/Overwrite due to insufficient absolute path sanitization
|
### Impact
Arbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution
`node-tar` aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`.
This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite.
### Patches
3.2.2 || 4.4.14 || 5.0.6 || 6.1.1
NOTE: an adjacent issue [CVE-2021-32803](https://github.com/npm/node-tar/security/advisories/GHSA-r628-mhmh-qjhw) affects this release level. Please ensure you update to the latest patch levels that address CVE-2021-32803 as well if this adjacent issue affects your `node-tar` use case.
### Workarounds
Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths.
```js
const path = require('path')
const tar = require('tar')
tar.x({
file: 'archive.tgz',
// either add this function...
onentry: (entry) => {
if (path.isAbsolute(entry.path)) {
entry.path = sanitizeAbsolutePathSomehow(entry.path)
entry.absolute = path.resolve(entry.path)
}
},
// or this one
filter: (file, entry) => {
if (path.isAbsolute(entry.path)) {
return false
} else {
return true
}
}
})
```
Users are encouraged to upgrade to the latest patch versions, rather than attempt to sanitize tar input themselves.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'tar'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.2.2'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'tar'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.0.0'}, {'fixed': '4.4.14'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'tar'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '5.0.0'}, {'fixed': '5.0.6'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'tar'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '6.0.0'}, {'fixed': '6.1.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-32804'}, {'type': 'WEB', 'url': 'https://github.com/npm/node-tar/commit/1f036ca23f64a547bdd6c79c1a44bc62e8115da4'}, {'type': 'WEB', 'url': 'https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf'}, {'type': 'PACKAGE', 'url': 'https://github.com/npm/node-tar'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/advisories/1770'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/package/tar'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2021.html'}]
|
{'cwe_ids': ['CWE-22'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-03T19:06:15Z', 'nvd_published_at': '2021-08-03T19:15:00Z'}
|
1.4.0
|
GHSA-6w62-hx7r-mw68
|
2022-02-08T20:43:47Z
|
2021-08-25T14:46:38Z
| null |
['CVE-2021-39154']
|
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-39154](https://x-stream.github.io/CVE-2021-39154.html).
### Credits
ka1n4t 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-6w62-hx7r-mw68'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39154'}, {'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-39154.html'}]
|
{'cwe_ids': ['CWE-434', 'CWE-502'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T18:22:35Z', 'nvd_published_at': '2021-08-23T18:15:00Z'}
|
1.4.0
|
GHSA-6wp2-fw3v-mfmc
|
2021-08-24T18:54:26Z
|
2021-08-25T20:57:19Z
| null |
['CVE-2020-36452']
|
Memory corruption in array-tools
|
An issue was discovered in the array-tools crate before 0.3.2 for Rust. Affected versions of this crate don't guard against panics, so that partially uninitialized buffer is dropped when user-provided `T::clone()` panics in `FixedCapacityDequeLike<T, A>::clone()`. This causes memory corruption.
|
[{'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': 'array-tools'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.3.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36452'}, {'type': 'WEB', 'url': 'https://github.com/L117/array-tools/issues/2'}, {'type': 'PACKAGE', 'url': 'https://github.com/L117/array-tools'}, {'type': 'WEB', 'url': 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/array-tools/RUSTSEC-2020-0132.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0132.html'}]
|
{'cwe_ids': ['CWE-908', 'CWE-909'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T20:24:55Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-r6g8-jmj9-g945
|
2021-08-27T12:54:01Z
|
2021-08-30T16:22:16Z
| null |
['CVE-2021-3734']
|
Improper Restriction of Rendered UI Layers or Frames in yourls
|
yourls is vulnerable to Improper Restriction of Rendered UI Layers or Frames
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'yourls/yourls'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.8.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3734'}, {'type': 'WEB', 'url': 'https://github.com/yourls/yourls/commit/0a70acdcfb5fcbc63dbc5750018d608288eba3fe'}, {'type': 'PACKAGE', 'url': 'https://github.com/yourls/yourls'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/dd2e2dbe-efe5-49ec-be11-7a7e7c41debd'}]
|
{'cwe_ids': ['CWE-1021', 'CWE-352'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-27T12:54:01Z', 'nvd_published_at': '2021-08-26T13:15:00Z'}
|
1.4.0
|
GHSA-r6mv-ppjc-4hgr
|
2023-04-25T16:37:22Z
|
2021-08-23T19:41:04Z
| null |
['CVE-2021-37626']
|
PHP file inclusion via insert tags
|
### Impact
It is possible for untrusted users to load arbitrary PHP files via insert tags.
Installations are only affected if there are untrusted back end users.
### Patches
Update to Contao 4.4.56, 4.9.18 or 4.11.7.
### Workarounds
Disable the login for untrusted back end users.
### References
https://contao.org/en/security-advisories/php-file-inclusion-via-insert-tags
### For more information
If you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'contao/core-bundle'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.0.0'}, {'fixed': '4.4.56'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'contao/core-bundle'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.5.0'}, {'fixed': '4.9.18'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'contao/core-bundle'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.10.0'}, {'fixed': '4.11.7'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/contao/contao/security/advisories/GHSA-r6mv-ppjc-4hgr'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37626'}, {'type': 'WEB', 'url': 'https://contao.org/en/security-advisories/php-file-inclusion-via-insert-tags.html'}, {'type': 'PACKAGE', 'url': 'https://github.com/contao/contao'}]
|
{'cwe_ids': ['CWE-94'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T16:51:34Z', 'nvd_published_at': '2021-08-11T23:15:00Z'}
|
1.4.0
|
GHSA-x54v-qxxr-93qc
|
2023-06-13T20:38:08Z
|
2021-08-25T20:45:01Z
| null |
['CVE-2020-25795']
|
Missing release of memory in sized-chunks
|
Chunk:
* Array size is not checked when constructed with unit() and pair().
* Array size is not checked when constructed with From<InlineArray<A, T>>.
* Clone and insert_from are not panic-safe; A panicking iterator causes memory safety issues with them.
InlineArray:
* Generates unaligned references for types with 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-25795'}, {'type': 'WEB', 'url': 'https://github.com/bodil/sized-chunks/issues/11'}, {'type': 'PACKAGE', 'url': 'https://github.com/bodil/sized-chunks'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0041.html'}]
|
{'cwe_ids': ['CWE-401'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:21:52Z', 'nvd_published_at': '2020-09-19T21:15:00Z'}
|
1.4.0
|
GHSA-2wmv-37vq-52g5
|
2021-08-24T14:19:36Z
|
2021-08-25T14:42:06Z
| null |
['CVE-2021-37668']
|
FPE in `tf.raw_ops.UnravelIndex`
|
### Impact
An attacker can cause denial of service in applications serving models using `tf.raw_ops.UnravelIndex` by triggering a division by 0:
```python
import tensorflow as tf
tf.raw_ops.UnravelIndex(indices=-1, dims=[1,0,2])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unravel_index_op.cc#L36) does not check that the tensor subsumed by `dims` is not empty. Hence, if one element of `dims` is 0, the implementation does a division by 0.
### Patches
We have patched the issue in GitHub commit [a776040a5e7ebf76eeb7eb923bf1ae417dd4d233](https://github.com/tensorflow/tensorflow/commit/a776040a5e7ebf76eeb7eb923bf1ae417dd4d233).
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-2wmv-37vq-52g5'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37668'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/a776040a5e7ebf76eeb7eb923bf1ae417dd4d233'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-369'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T14:19:36Z', 'nvd_published_at': '2021-08-12T23:15:00Z'}
|
1.4.0
|
GHSA-5ph6-qq5x-7jwc
|
2021-08-30T16:53:38Z
|
2021-08-30T17:22:10Z
| null |
['CVE-2021-32783']
|
ExternalName Services can be used to gain access to Envoy's admin interface
|
### Impact
Josh Ferrell (@josh-ferrell) from VMware has reported that a specially crafted ExternalName type Service may be used to access Envoy's admin interface, which Contour normally prevents from access outside the Envoy container. This can be used to shut down Envoy remotely (a denial of service), or to expose the existence of any Secret that Envoy is using for its configuration, including most notably TLS Keypairs. However, it *cannot* be used to get the *content* of those secrets.
Since this attack allows access to the administration interface, a variety of administration options are available, such as shutting down the Envoy or draining traffic. In general, the Envoy admin interface cannot easily be used for making changes to the cluster, in-flight requests, or backend services, but it could be used to shut down or drain Envoy, change traffic routing, or to retrieve secret metadata, as mentioned above.
### Patches
The issue will be addressed in the forthcoming Contour v1.18.0 and a patch release, v1.17.1, has been released in the meantime.
It is addressed in two ways:
- disabling ExternalName type Services by default
- When ExternalName Services are enabled, block obvious "localhost" entries.
#### Disable ExternalName type Services by default
This change prohibits processing of ExternalName services unless the cluster operator specifically allows them using the new `--enable-externalname` flag or equivalent configuration file setting. This is a breaking change for previous versions of Contour, which is unfortunate, but necessary because of the severity of the information exposed in this advisory.
#### Block obvious `localhost` entries for enabled ExternalName Services
As part of this change set, we have added a filter in the event that operators *do* enable ExternalName Services, such that obvious `localhost` entries are rejected by Contour.
There are a number of problems with this method, however:
- This is a porous control. As long as you control a domain name, it's trivially easy to add a DNS entry for any name you like that redirects to `127.0.0.1` or `::1`. Contour even provides `local.projectcontour.io` ourselves for testing and example purposes. (This name is, of course, included in the "obvious localhost entries" list.) So we can never totally stop this exploit as long as the admin interface is accessible on localhost, which, according to envoyproxy/envoy#2763, will be for some time if not forever. The best we can do is block some obvious elements, but this is always a risk for a motivated attacker.
- We've actually suggested using `localhost` ExternalName Services in the past, to allow people to connect to sidecar External Authentication services in their cluster. Both of these changes break this use-case, but given that it's about something that has security requirements high enough to require authentication, it's important to ensure that people are opting in. For the External Auth sidecar case, we are investigating an update to ExtensionService that will help with the sidecar use case.
### Workarounds
Not easily. It's not possible to control the creation of ExternalName Services with RBAC without the use of Gatekeeper or other form of admission control, and the creation of services is required for Contour to actually work for application developer personas.
### For more information
Exploit code will be published at a later date for this vulnerability, once our users have had a chance to upgrade.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:H'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/projectcontour/contour'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.14.2'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/projectcontour/contour'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.15.0'}, {'fixed': '1.15.2'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/projectcontour/contour'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.16.0'}, {'fixed': '1.16.1'}]}], 'versions': ['1.16.0']}, {'package': {'ecosystem': 'Go', 'name': 'github.com/projectcontour/contour'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.17.0'}, {'fixed': '1.17.1'}]}], 'versions': ['1.17.0']}]
|
[{'type': 'WEB', 'url': 'https://github.com/projectcontour/contour/security/advisories/GHSA-5ph6-qq5x-7jwc'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-32783'}, {'type': 'WEB', 'url': 'https://github.com/projectcontour/contour/commit/5f3e6d0ab1d48e64bae46400c85c490b200393a3'}, {'type': 'WEB', 'url': 'https://github.com/projectcontour/contour/commit/b53a5c4fd927f4ea2c6cf02f1359d8e28bef852e'}, {'type': 'WEB', 'url': 'https://github.com/projectcontour/contour/releases/tag/v1.14.2'}, {'type': 'WEB', 'url': 'https://github.com/projectcontour/contour/releases/tag/v1.15.2'}, {'type': 'WEB', 'url': 'https://github.com/projectcontour/contour/releases/tag/v1.16.1'}, {'type': 'WEB', 'url': 'https://github.com/projectcontour/contour/releases/tag/v1.17.1'}]
|
{'cwe_ids': ['CWE-610'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-30T16:53:38Z', 'nvd_published_at': '2021-07-23T22:15:00Z'}
|
1.4.0
|
GHSA-jphw-p3m6-pj3c
|
2023-06-13T20:04:07Z
|
2021-08-25T20:51:54Z
| null |
['CVE-2020-36214']
|
Data races in multiqueue2
|
Affected versions of this crate unconditionally implemented Send for types used in queue implementations (InnerSend<RW, T>, InnerRecv<RW, T>, FutInnerSend<RW, T>, FutInnerRecv<RW, T>).
This allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior.
The flaw was corrected in v0.1.7 by adding T: Send bound to to the Send impl of four data types explained above.
|
[{'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': 'multiqueue2'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.1.7'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36214'}, {'type': 'WEB', 'url': 'https://github.com/abbychau/multiqueue2/issues/10'}, {'type': 'PACKAGE', 'url': 'https://github.com/abbychau/multiqueue2'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0106.html'}]
|
{'cwe_ids': ['CWE-662'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T18:47:21Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-mhhc-q96p-mfm9
|
2021-08-24T17:54:33Z
|
2021-08-25T14:39:58Z
| null |
['CVE-2021-37686']
|
Infinite loop in TFLite
|
### Impact
The strided slice implementation in TFLite has a logic bug which can allow an attacker to trigger an infinite loop. This arises from newly introduced support for [ellipsis in axis definition](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/strided_slice.cc#L103-L122):
```cc
for (int i = 0; i < effective_dims;) {
if ((1 << i) & op_context->params->ellipsis_mask) {
// ...
int ellipsis_end_idx =
std::min(i + 1 + num_add_axis + op_context->input_dims - begin_count,
effective_dims);
// ...
for (; i < ellipsis_end_idx; ++i) {
// ...
}
continue;
}
// ...
++i;
}
```
An attacker can craft a model such that `ellipsis_end_idx` is smaller than `i` (e.g., always negative). In this case, the inner loop does not increase `i` and the `continue` statement causes execution to skip over the preincrement at the end of the outer loop.
### Patches
We have patched the issue in GitHub commit [dfa22b348b70bb89d6d6ec0ff53973bacb4f4695](https://github.com/tensorflow/tensorflow/commit/dfa22b348b70bb89d6d6ec0ff53973bacb4f4695).
The fix will be included in TensorFlow 2.6.0. This is the only 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-cpu'}, '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-mhhc-q96p-mfm9'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-37686'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/dfa22b348b70bb89d6d6ec0ff53973bacb4f4695'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.4'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/releases/tag/v2.4.3'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/releases/tag/v2.5.1'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/releases/tag/v2.6.0'}]
|
{'cwe_ids': ['CWE-835'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-24T17:54:33Z', 'nvd_published_at': '2021-08-12T22:15:00Z'}
|
1.4.0
|
GHSA-955p-rc5h-hg6h
|
2023-06-13T16:52:27Z
|
2021-08-25T20:55:04Z
| null |
['CVE-2021-29931']
|
Double free in arenavec
|
Affected versions of this crate did not guard against potential panics that may happen from user-provided functions T::default() and T::drop().
Panic within T::default() leads to dropping uninitialized T, when it is invoked from common::Slice::<T, H>::new(). Panic within T::drop() leads to double drop of T, when it is invoked either from common::SliceVec::<T, H>::resize_with() or common::SliceVec::<T, H>::resize()
Either case causes memory corruption in the heap memory.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'arenavec'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.1.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-29931'}, {'type': 'WEB', 'url': 'https://github.com/ibabushkin/arenavec/issues/1'}, {'type': 'PACKAGE', 'url': 'https://github.com/ibabushkin/arenavec'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0040.html'}]
|
{'cwe_ids': ['CWE-415'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:08:56Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-64xx-cq4q-mf44
|
2022-02-08T21:01:27Z
|
2021-08-25T14:48:47Z
| null |
['CVE-2021-39139']
|
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. A user is only affected if using the version out of the box with JDK 1.7u21 or below. However, this scenario can be adjusted easily to an external Xalan that works regardless of the version of the Java runtime. 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-39139](https://x-stream.github.io/CVE-2021-39139.html).
### Credits
Lai Han of nsfocus security team 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-64xx-cq4q-mf44'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-39139'}, {'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-39139.html'}]
|
{'cwe_ids': ['CWE-502'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-23T18:21:57Z', 'nvd_published_at': '2021-08-23T18:15:00Z'}
|
1.4.0
|
GHSA-7f92-rr6w-cq64
|
2021-08-02T19:12:30Z
|
2021-08-05T16:57:42Z
| null |
[]
|
Storage corruption due to variables overwritten by re-entrancy locks
|
### Background
When attempting to use the v0.2.14 release, @pandadefi discovered an issue using the `@nonreentrant` decorator.
### Impact
Reentrancy protection storage slots get allocated to the same slots as storage variables, leading to the corruption of storage variables when using the `@nonreentrant` decorator.
### Patches
This issue was fixed in v0.2.15 in #2391, #2379
### Workarounds
Don't use the `@nonreentrant` decorator in these versions.
|
[]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'vyper'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.2.13'}, {'fixed': '0.2.15'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/vyperlang/vyper/security/advisories/GHSA-7f92-rr6w-cq64'}, {'type': 'WEB', 'url': 'https://github.com/vyperlang/vyper/pull/2379'}, {'type': 'WEB', 'url': 'https://github.com/vyperlang/vyper/pull/2391'}]
|
{'cwe_ids': [], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-02T19:12:30Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-qj3v-q2vj-4c8h
|
2021-08-18T21:27:27Z
|
2021-08-25T20:55:58Z
| null |
['CVE-2021-38194']
|
Calculation error in ark-r1cs-std
|
An issue was discovered in the ark-r1cs-std crate before 0.3.1 for Rust. It does not enforce any constraints in the FieldVar::mul_by_inverse method. Thus, a prover can produce a proof that is unsound but is nonetheless verified.
|
[{'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': 'ark-r1cs-std'}, 'ecosystem_specific': {'affected_functions': ['ark_r1cs_std::FieldVar::mul_by_inverse']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.2.0'}, {'fixed': '0.3.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-38194'}, {'type': 'WEB', 'url': 'https://github.com/arkworks-rs/r1cs-std/pull/70'}, {'type': 'WEB', 'url': 'https://github.com/arkworks-rs/r1cs-std/commit/47ddbaa411afe7c499311a248a38135e5a192b67'}, {'type': 'PACKAGE', 'url': 'https://github.com/arkworks-rs/r1cs-std'}, {'type': 'WEB', 'url': 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/ark-r1cs-std/RUSTSEC-2021-0075.md'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0075.html'}]
|
{'cwe_ids': ['CWE-682'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T21:27:27Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-82hm-vh7g-hrh9
|
2021-09-09T17:55:10Z
|
2021-08-25T21:01:25Z
| null |
[]
|
Partial read is incorrect in molecule
|
### Impact
Anyone who uses `total_size(..)` function to partial read the length of any `FixVec` will get an incorrect result, due to an incorrect implementation. This has been resolved in the 0.7.2 release.
### Workarounds
If you already have the whole `FixVec` `A`, you can use `A.as_slice().len()` to get the total size of the `FixVec`.
### For more information
If you have any questions or comments about this advisory:
- [Open an issue to ask use directly](https://github.com/nervosnetwork/molecule/issues/new).
|
[]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'molecule'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.7.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/nervosnetwork/molecule/security/advisories/GHSA-82hm-vh7g-hrh9'}, {'type': 'WEB', 'url': 'https://github.com/nervosnetwork/molecule/pull/49'}, {'type': 'PACKAGE', 'url': 'https://github.com/nervosnetwork/molecule'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0103.html'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-02T18:10:49Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-3h87-v52r-p9rg
|
2023-06-13T20:27:27Z
|
2021-08-25T20:54:08Z
| null |
['CVE-2021-29941']
|
Out of bounds write in reorder
|
swap_index takes an iterator and swaps the items with their corresponding indexes. It reserves capacity and sets the length of the vector based on the .len() method of the iterator.
If the len() returned by the iterator is larger than the actual number of elements yielded, then swap_index creates a vector containing uninitialized members. If the len() returned by the iterator is smaller than the actual number of members yielded, then swap_index can write out of bounds past its allocated vector.
As noted by the Rust documentation, len() and size_hint() are primarily meant for optimization and incorrect values from their implementations should not lead to memory safety violations.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'reorder'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.1.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-29941'}, {'type': 'WEB', 'url': 'https://github.com/tiby312/reorder/issues/1'}, {'type': 'PACKAGE', 'url': 'https://github.com/tiby312/reorder'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0050.html'}]
|
{'cwe_ids': ['CWE-787'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T17:17:20Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-6hfq-h8hq-87mf
|
2021-08-18T21:07:17Z
|
2021-08-25T20:56:18Z
| null |
['CVE-2021-21299']
|
HTTP Request Smuggling in hyper
|
### Summary
hyper's HTTP server code had a flaw that incorrectly understands some requests with multiple transfer-encoding headers to have a chunked payload, when it should have been rejected as illegal. This combined with an upstream HTTP proxy that understands the request payload boundary differently can result in "request smuggling" or "desync attacks".
### Vulnerability
The flaw was introduced in https://github.com/hyperium/hyper/commit/26417fc24a7d05df538e0f39239b373c5c3d61f6, released in v0.12.0.
Consider this example request:
```
POST /yolo HTTP/1.1
Transfer-Encoding: chunked
Transfer-Encoding: cow
```
This request *should* be rejected, according to RFC 7230, since it has a `Transfer-Encoding` header, but after folding, it does not end in `chunked`. hyper would notice the `chunked` in the first line, and then check the second line, and thanks to a missing boolean assignment, *not* set the error condition. hyper would treat the payload as being `chunked`. By differing from the spec, it is possible to send requests like these to endpoints that have different HTTP implementations, with different interpretations of the payload semantics, and cause "desync attacks".
There are several parts of the spec that must also be checked, and hyper correctly handles all of those. Additionally, hyper's *client* does not allow sending requests with improper headers, so the misunderstanding cannot be propagated further.
Read more about desync attacks: https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn
### Impact
To determine if vulnerable, all these things must be true:
- **Using hyper as an HTTP *server*.** The client is not affected.
- **Using HTTP/1.1.** HTTP/2 does not use `transfer-encoding`.
- **Using a vulnerable HTTP proxy upstream to hyper.** If an upstream proxy correctly rejects the illegal transfer-encoding headers, the desync attack cannot succeed. If there is *no* proxy upstream of hyper, hyper cannot *start* the desync attack, as the client will repair the headers before forwarding.
### Patches
We have released and backported the following patch versions:
- v0.14.3
- v0.13.10
### Workarounds
Besides upgrading hyper, you can take the following options:
- Reject requests that contain a `transfer-encoding` header.
- Ensure any upstream proxy handles `transfer-encoding` correctly.
### Credits
This issue was initially reported by ZeddYu Lu From Qi An Xin Technology Research Institute.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'hyper'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.14.0'}, {'fixed': '0.14.3'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'hyper'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.13.0'}, {'fixed': '0.13.10'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'hyper'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.12.0'}, {'fixed': '0.12.36'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/hyperium/hyper/security/advisories/GHSA-6hfq-h8hq-87mf'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-21299'}, {'type': 'WEB', 'url': 'https://github.com/hyperium/hyper/commit/8f93123efef5c1361086688fe4f34c83c89cec02'}, {'type': 'PACKAGE', 'url': 'https://github.com/hyperium/hyper'}, {'type': 'WEB', 'url': 'https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2021-0020.html'}]
|
{'cwe_ids': ['CWE-444'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T21:07:17Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-9pp4-8p8v-g78w
|
2021-08-18T20:22:32Z
|
2021-08-25T20:57:26Z
| null |
['CVE-2020-36457']
|
Data races in lever
|
An issue was discovered in the lever crate before 0.1.1 for Rust. AtomicBox<T> implements the Send and Sync traits for all types T. This allows non-Send types such as Rc and non-Sync types such as Cell to be used across thread boundaries which can trigger undefined behavior and memory corruption.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'lever'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.1.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36457'}, {'type': 'WEB', 'url': 'https://github.com/vertexclique/lever/issues/15'}, {'type': 'WEB', 'url': 'https://github.com/vertexclique/lever/pull/17'}, {'type': 'WEB', 'url': 'https://github.com/vertexclique/lever/commit/4a4cca61cdb25061967d58522229e147483007b1'}, {'type': 'PACKAGE', 'url': 'https://github.com/vertexclique/lever'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0137.html'}]
|
{'cwe_ids': ['CWE-362', 'CWE-77'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-08-18T20:22:32Z', 'nvd_published_at': '2021-08-08T06:15:00Z'}
|
1.4.0
|
GHSA-gv73-9mwv-fwgq
|
2023-06-13T20:33:10Z
|
2021-08-25T20:46:11Z
| null |
['CVE-2020-35858']
|
Out of bounds write in prost
|
Affected versions of this crate contained a bug in which decoding untrusted input could overflow the stack. On architectures with stack probes (like x86), this can be used for denial of service attacks, while on architectures without stack probes (like ARM) overflowing the stack is unsound and can result in potential memory corruption (or even RCE).
|
[{'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': 'prost'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.6.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-35858'}, {'type': 'WEB', 'url': 'https://github.com/danburkert/prost/issues/267'}, {'type': 'WEB', 'url': 'https://github.com/danburkert/prost/commit/04091d3e745c27590a5f1b7f581793e4159486b5'}, {'type': 'PACKAGE', 'url': 'https://github.com/danburkert/prost'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2020-0002.html'}]
|
{'cwe_ids': ['CWE-787'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:20:08Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-jqqr-c2r2-9cvr
|
2023-06-13T20:37:16Z
|
2021-08-25T20:42:59Z
| null |
['CVE-2017-18588']
|
Improper Certificate Validation in security-framework
|
If custom root certificates were registered with a ClientBuilder, the hostname of the target server would not be validated against its presented leaf certificate. This issue was fixed by properly configuring the trust evaluation logic to perform that check.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'security-framework'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.1.12'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2017-18588'}, {'type': 'WEB', 'url': 'https://github.com/sfackler/rust-security-framework/pull/27'}, {'type': 'PACKAGE', 'url': 'https://github.com/sfackler/rust-security-framework'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2017-0003.html'}]
|
{'cwe_ids': ['CWE-295'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-08-19T21:25:26Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-7m7q-q53v-j47v
|
2021-02-25T02:01:47Z
|
2021-02-25T02:01:47Z
|
2021-02-25T02:01:47Z
|
[]
|
Regular Expression Denial of Service
|
A flaw was found in nodejs-marked versions from 0.5.0 to before 0.6.1. Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). Input to the host variable is vulnerable when input contains parenthesis in link URIs, coupled with a high number of link tokens in a single line.
|
[]
|
[{'package': {'ecosystem': 'npm', 'name': 'marked'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.5.0'}, {'fixed': '0.6.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/Feder1co5oave/marktex/commit/cc8a45288b59ca10a8fedaed9028072021be9999'}, {'type': 'WEB', 'url': 'https://bugzilla.redhat.com/show_bug.cgi?id=1679550'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2019-06-04T19:45:00Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-pmw4-jgxx-pcq9
|
2021-02-11T17:04:52Z
|
2021-02-10T18:11:34Z
| null |
['CVE-2020-26299']
|
File System Bounds Escape
|
### Impact
Clients of FTP servers utilizing `ftp-srv` hosted on Windows machines can escape the FTP user's defined root folder using the expected FTP commands, for example, `CWD` and `UPDR`.
### Background
When windows separators exist within the path (`\`), `path.resolve` leaves the upper pointers intact and allows the user to move beyond the root folder defined for that user. We did not take that into account when creating the path resolve function.
### Patches
None at the moment.
### Workarounds
There are no workarounds for windows servers. Hosting the server on a different OS mitigates the issue.
### References
Issues:
https://github.com/autovance/ftp-srv/issues/167
https://github.com/autovance/ftp-srv/issues/225
### For more information
If you have any questions or comments about this advisory:
Open an issue at https://github.com/autovance/ftp-srv.
Please email us directly; security@autovance.com.
|
[]
|
[{'package': {'ecosystem': 'npm', 'name': 'ftp-srv'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.4.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/autovance/ftp-srv/security/advisories/GHSA-pmw4-jgxx-pcq9'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-26299'}, {'type': 'WEB', 'url': 'https://github.com/autovance/ftp-srv/issues/167'}, {'type': 'WEB', 'url': 'https://github.com/autovance/ftp-srv/issues/225'}, {'type': 'WEB', 'url': 'https://github.com/autovance/ftp-srv/pull/224'}, {'type': 'WEB', 'url': 'https://github.com/autovance/ftp-srv/commit/457b859450a37cba10ff3c431eb4aa67771122e3'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/package/ftp-srv'}]
|
{'cwe_ids': ['CWE-22'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-02-10T18:11:21Z', 'nvd_published_at': '2021-02-10T18:15:00Z'}
|
1.4.0
|
GHSA-6cf8-qhqj-vjqm
|
2023-09-13T20:22:24Z
|
2021-02-05T20:43:19Z
| null |
['CVE-2020-28495']
|
Prototype pollution in total.js
|
There is a prototype pollution vulnerability in the package total.js before version 3.4.7. The set function can be used to set a value into the object according to the path. However the keys of the path being set are not properly sanitized, leading to a prototype pollution vulnerability. The impact depends on the application. In some cases it is possible to achieve Denial of service (DoS), Remote Code Execution or Property Injection.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'total.js'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.4.7'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-28495'}, {'type': 'WEB', 'url': 'https://github.com/totaljs/framework/commit/b3f901561d66ab799a4a99279893b94cad7ae4ff'}, {'type': 'WEB', 'url': 'https://docs.totaljs.com/latest/en.html%23api~FrameworkUtils~U.set'}, {'type': 'WEB', 'url': 'https://github.com/totaljs/framework/blob/master/utils.js%23L6606'}, {'type': 'WEB', 'url': 'https://github.com/totaljs/framework/blob/master/utils.js%23L6617'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JS-TOTALJS-1046671'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/package/total.js'}]
|
{'cwe_ids': ['CWE-1321', 'CWE-400'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-02-03T07:46:44Z', 'nvd_published_at': '2021-02-02T11:15:00Z'}
|
1.4.0
|
GHSA-5mcr-gq6c-3hq2
|
2022-04-19T15:19:08Z
|
2021-02-08T21:17:48Z
| null |
['CVE-2021-21290']
|
Local Information Disclosure Vulnerability in Netty on Unix-Like systems
|
### Impact
When netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled.
The CVSSv3.1 score of this vulnerability is calculated to be a [6.2/10](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N&version=3.1)
### Vulnerability Details
On unix-like systems, the temporary directory is shared between all user. As such, writing to this directory using APIs that do not explicitly set the file/directory permissions can lead to information disclosure. Of note, this does not impact modern MacOS Operating Systems.
The method `File.createTempFile` on unix-like systems creates a random file, but, by default will create this file with the permissions `-rw-r--r--`. Thus, if sensitive information is written to this file, other local users can read this information.
This is the case in netty's `AbstractDiskHttpData` is vulnerable.
https://github.com/netty/netty/blob/e5951d46fc89db507ba7d2968d2ede26378f0b04/codec-http/src/main/java/io/netty/handler/codec/http/multipart/AbstractDiskHttpData.java#L80-L101
`AbstractDiskHttpData` is used as a part of the `DefaultHttpDataFactory` class which is used by `HttpPostRequestDecoder` / `HttpPostMultiPartRequestDecoder`.
You may be affected by this vulnerability your project contains the following code patterns:
```java
channelPipeline.addLast(new HttpPostRequestDecoder(...));
```
```java
channelPipeline.addLast(new HttpPostMultiPartRequestDecoder(...));
```
### Patches
This has been patched in version `4.1.59.Final`.
### Workarounds
Specify your own `java.io.tmpdir` when you start the JVM or use `DefaultHttpDataFactory.setBaseDir(...)` to set the directory to something that is only readable by the current user.
### References
- [CWE-378: Creation of Temporary File With Insecure Permissions](https://cwe.mitre.org/data/definitions/378.html)
- [CWE-379: Creation of Temporary File in Directory with Insecure Permissions](https://cwe.mitre.org/data/definitions/379.html)
### Similar Vulnerabilities
Similar, but not the same.
- JUnit 4 - https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp
- Google Guava - https://github.com/google/guava/issues/4011
- Apache Ant - https://nvd.nist.gov/vuln/detail/CVE-2020-1945
- JetBrains Kotlin Compiler - https://nvd.nist.gov/vuln/detail/CVE-2020-15824
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [netty](https://github.com/netty/netty)
* Email us [here](mailto:netty-security@googlegroups.com)
### Original Report
> Hi Netty Security Team,
>
> I've been working on some security research leveraging custom CodeQL queries to detect local information disclosure vulnerabilities in java applications. This was the result from running this query against the netty project:
> https://lgtm.com/query/7723301787255288599/
>
> Netty contains three local information disclosure vulnerabilities, so far as I can tell.
>
> One is here, where the private key for the certificate is written to a temporary file.
>
> https://github.com/netty/netty/blob/e5951d46fc89db507ba7d2968d2ede26378f0b04/handler/src/main/java/io/netty/handler/ssl/util/SelfSignedCertificate.java#L316-L346
>
> One is here, where the certificate is written to a temporary file.
>
> https://github.com/netty/netty/blob/e5951d46fc89db507ba7d2968d2ede26378f0b04/handler/src/main/java/io/netty/handler/ssl/util/SelfSignedCertificate.java#L348-L371
>
> The final one is here, where the 'AbstractDiskHttpData' creates a temporary file if the getBaseDirectory() method returns null. I believe that 'AbstractDiskHttpData' is used as a part of the file upload support? If this is the case, any files uploaded would be similarly vulnerable.
>
> https://github.com/netty/netty/blob/e5951d46fc89db507ba7d2968d2ede26378f0b04/codec-http/src/main/java/io/netty/handler/codec/http/multipart/AbstractDiskHttpData.java#L91
>
> All of these vulnerabilities exist because `File.createTempFile(String, String)` will create a temporary file in the system temporary directory if the 'java.io.tmpdir' system property is not explicitly set. It is my understanding that when java creates a file, by default, and using this method, the permissions on that file utilize the umask. In a majority of cases, this means that the file that java creates has the permissions: `-rw-r--r--`, thus, any other local user on that system can read the contents of that file.
>
> Impacted OS:
> - Any OS where the system temporary directory is shared between multiple users. This is not the case for MacOS or Windows.
>
> Mitigation.
>
> Moving to the `Files` API instead will fix this vulnerability.
> https://docs.oracle.com/javase/8/docs/api/java/nio/file/Files.html#createTempFile-java.nio.file.Path-java.lang.String-java.lang.String-java.nio.file.attribute.FileAttribute...-
>
> This API will explicitly set the posix file permissions to something safe, by default.
>
> I recently disclosed a similar vulnerability in JUnit 4:
> https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp
>
> If you're also curious, this vulnerability in Jetty was also mine, also involving temporary directories, but is not the same vulnerability as in this case.
> https://github.com/eclipse/jetty.project/security/advisories/GHSA-g3wg-6mcf-8jj6
>
> I would appreciate it if we could perform disclosure of this vulnerability leveraging the GitHub security advisories feature here. GitHub has a nice credit system that I appreciate, plus the disclosures, as you can see from the sampling above, end up looking very nice.
> https://github.com/netty/netty/security/advisories
>
> This vulnerability disclosure follows Google's [90-day vulnerability disclosure policy](https://www.google.com/about/appsecurity/) (I'm not an employee of Google, I just like their policy). Full disclosure will occur either at the end of the 90-day deadline or whenever a patch is made widely available, whichever occurs first.
>
> Cheers,
> Jonathan Leitschuh
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'io.netty:netty-codec-http'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.0.0'}, {'fixed': '4.1.59.Final'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.jboss.netty:netty'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}]}], 'database_specific': {'last_known_affected_version_range': '< 4.0.0'}}, {'package': {'ecosystem': 'Maven', 'name': 'io.netty:netty'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}]}], 'database_specific': {'last_known_affected_version_range': '< 4.0.0'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/netty/netty/security/advisories/GHSA-5mcr-gq6c-3hq2'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-21290'}, {'type': 'WEB', 'url': 'https://github.com/netty/netty/commit/c735357bf29d07856ad171c6611a2e1a0e0000ec'}, {'type': 'PACKAGE', 'url': 'https://github.com/netty/netty'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r0053443ce19ff125981559f8c51cf66e3ab4350f47812b8cf0733a05@%3Cdev.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r02e467123d45006a1dda20a38349e9c74c3a4b53e2e07be0939ecb3f@%3Cdev.ranger.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r0857b613604c696bf9743f0af047360baaded48b1c75cf6945a083c5@%3Cjira.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r10308b625e49d4e9491d7e079606ca0df2f0a4d828f1ad1da64ba47b@%3Cjira.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r1908a34b9cc7120e5c19968a116ddbcffea5e9deb76c2be4fa461904@%3Cdev.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r2748097ea4b774292539cf3de6e3b267fc7a88d6c8ec40f4e2e87bd4@%3Cdev.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r2936730ef0a06e724b96539bc7eacfcd3628987c16b1b99c790e7b87@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r2fda4dab73097051977f2ab818f75e04fbcb15bb1003c8530eac1059@%3Cjira.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r326ec431f06eab7cb7113a7a338e59731b8d556d05258457f12bac1b@%3Cdev.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r4efed2c501681cb2e8d629da16e48d9eac429624fd4c9a8c6b8e7020@%3Cdev.tinkerpop.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r584cf871f188c406d8bd447ff4e2fd9817fca862436c064d0951a071@%3Ccommits.pulsar.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r59bac5c09f7a4179b9e2460e8f41c278aaf3b9a21cc23678eb893e41@%3Cjira.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r5bf303d7c04da78f276765da08559fdc62420f1df539b277ca31f63b@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r5c701840aa2845191721e39821445e1e8c59711e71942b7796a6ec29@%3Cusers.activemq.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r5e4a540089760c8ecc2c411309d74264f1dad634ad93ad583ca16214@%3Ccommits.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r5e66e286afb5506cdfe9bbf68a323e8d09614f6d1ddc806ed0224700@%3Cjira.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r71dbb66747ff537640bb91eb0b2b24edef21ac07728097016f58b01f@%3Ccommits.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r743149dcc8db1de473e6bff0b3ddf10140a7357bc2add75f7d1fbb12@%3Cdev.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r790c2926efcd062067eb18fde2486527596d7275381cfaff2f7b3890@%3Cissues.bookkeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r7bb3cdc192e9a6f863d3ea05422f09fa1ae2b88d4663e63696ee7ef5@%3Cdev.ranger.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r9924ef9357537722b28d04c98a189750b80694a19754e5057c34ca48@%3Ccommits.pulsar.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/ra0fc2b4553dd7aaf75febb61052b7f1243ac3a180a71c01f29093013@%3Cjira.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/ra503756ced78fdc2136bd33e87cb7553028645b261b1f5c6186a121e@%3Cjira.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rb06c1e766aa45ee422e8261a8249b561784186483e8f742ea627bda4@%3Cdev.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rb51d6202ff1a773f96eaa694b7da4ad3f44922c40b3d4e1a19c2f325@%3Ccommits.pulsar.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rb592033a2462548d061a83ac9449c5ff66098751748fcd1e2d008233@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rc0087125cb15b4b78e44000f841cd37fefedfda942fd7ddf3ad1b528@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rc488f80094872ad925f0c73d283d4c00d32def81977438e27a3dc2bb@%3Cjira.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rcd163e421273e8dca1c71ea298dce3dd11b41d51c3a812e0394e6a5d@%3Ccommits.pulsar.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rdba4f78ac55f803893a1a2265181595e79e3aa027e2e651dfba98c18@%3Cjira.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2021/02/msg00016.html'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20220210-0011/'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2021/dsa-4885'}, {'type': 'WEB', 'url': 'https://www.oracle.com//security-alerts/cpujul2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuApr2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuapr2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2021.html'}]
|
{'cwe_ids': ['CWE-378', 'CWE-379', 'CWE-668'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-02-08T20:07:45Z', 'nvd_published_at': '2021-02-08T20:15:00Z'}
|
1.4.0
|
GHSA-qfmr-6qvh-49gm
|
2021-02-25T01:44:38Z
|
2021-02-25T01:44:38Z
|
2021-02-25T01:44:38Z
|
[]
|
XSS
|
**Withdrawn:** Duplicate of GHSA-vcjj-xf2r-mwvc.
Knockout, before 3.5.0-beta, has an XSS injection point in attr name binding for browser IE7 and older.
|
[]
|
[{'package': {'ecosystem': 'npm', 'name': 'knockout'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.5.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/knockout/knockout/issues/1244'}, {'type': 'WEB', 'url': 'https://github.com/knockout/knockout/commit/86b06aa8633f9f72b953f512df7471a22689ea14'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2019-05-22T15:03:20Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-93xj-8mrv-444m
|
2021-02-08T19:41:34Z
|
2021-02-08T19:41:59Z
| null |
['CVE-2021-21240']
|
Regular Expression Denial of Service (REDoS) in httplib2
|
### Impact
A malicious server which responds with long series of `\xa0` characters in the `www-authenticate` header may cause Denial of Service (CPU burn while parsing header) of the httplib2 client accessing said server.
### Patches
Version 0.19.0 contains new implementation of auth headers parsing, using pyparsing library.
https://github.com/httplib2/httplib2/pull/182
### Workarounds
```py
import httplib2
httplib2.USE_WWW_AUTH_STRICT_PARSING = True
```
### Technical Details
The vulnerable regular expression is https://github.com/httplib2/httplib2/blob/595e248d0958c00e83cb28f136a2a54772772b50/python3/httplib2/__init__.py#L336-L338
The section before the equals sign contains multiple overlapping groups. Ignoring the optional part containing a comma, we have:
\s*[^ \t\r\n=]+\s*=
Since all three infinitely repeating groups accept the non-breaking space character `\xa0`, a long string of `\xa0` causes catastrophic backtracking.
The complexity is cubic, so doubling the length of the malicious string of `\xa0` makes processing take 8 times as long.
### Reproduction Steps
Run a malicious server which responds with
www-authenticate: x \xa0\xa0\xa0\xa0x
but with many more `\xa0` characters.
An example malicious python server is below:
```py
from http.server import BaseHTTPRequestHandler, HTTPServer
def make_header_value(n_spaces):
repeat = "\xa0" * n_spaces
return f"x {repeat}x"
class Handler(BaseHTTPRequestHandler):
def do_GET(self):
self.log_request(401)
self.send_response_only(401) # Don't bother sending Server and Date
n_spaces = (
int(self.path[1:]) # Can GET e.g. /100 to test shorter sequences
if len(self.path) > 1 else
65512 # Max header line length 65536
)
value = make_header_value(n_spaces)
self.send_header("www-authenticate", value) # This header can actually be sent multiple times
self.end_headers()
if __name__ == "__main__":
HTTPServer(("", 1337), Handler).serve_forever()
```
Connect to the server with httplib2:
```py
import httplib2
httplib2.Http(".cache").request("http://localhost:1337", "GET")
```
To benchmark performance with shorter strings, you can set the path to a number e.g. http://localhost:1337/1000
### References
Thanks to [Ben Caller](https://github.com/b-c-ds) ([Doyensec](https://doyensec.com)) for finding vulnerability and discrete notification.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [httplib2](https://github.com/httplib2/httplib2/issues/new)
* Email [current maintainer at 2021-01](mailto:temotor@gmail.com)
|
[]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'httplib2'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.19.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/httplib2/httplib2/security/advisories/GHSA-93xj-8mrv-444m'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-21240'}, {'type': 'WEB', 'url': 'https://github.com/httplib2/httplib2/pull/182'}, {'type': 'WEB', 'url': 'https://github.com/httplib2/httplib2/commit/bd9ee252c8f099608019709e22c0d705e98d26bc'}, {'type': 'WEB', 'url': 'https://pypi.org/project/httplib2'}]
|
{'cwe_ids': ['CWE-400'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2021-02-08T19:41:34Z', 'nvd_published_at': '2021-02-08T20:15:00Z'}
|
1.4.0
|
GHSA-xmw9-q7x9-j5qc
|
2022-10-25T20:21:46Z
|
2021-02-02T21:42:49Z
| null |
['CVE-2021-21293']
|
Unbounded connection acceptance leads to file handle exhaustion
|
### Impact
All servers running blaze-core <= 0.14.14, including blaze-http and http4s-blaze-server users, are affected.
Blaze, accepts connections unconditionally on a dedicated thread pool. This has the net effect of amplifying degradation in services that are unable to handle their current request load, since incoming connections are still accepted and added to an unbounded queue. Each connection allocates a socket handle, which drains a scarce OS resource. This can also confound higher level circuit breakers which work based on detecting failed connections.
The vast majority of affected users are using it as part of http4s-blaze-server <= 0.21.16. http4s provides a mechanism for limiting open connections, but is enforced inside the Blaze accept loop, after the connection is accepted and the socket opened. Thus, the limit only prevents the number of connections which can be simultaneously processed, not the number of connections which can be held open.
### Patches
The issue is fixed in version 0.14.15 for `NIO1SocketServerGroup`. A `maxConnections` parameter is added, with a default value of 512. Concurrent connections beyond this limit are rejected. To run unbounded, which is not recommended, set a negative number.
The `NIO2SocketServerGroup` has no such setting and is now deprecated.
### Workarounds
* An Nginx side-car acting as a reverse proxy for the local http4s-blaze-server instance would be able to apply a connection limiting semantic before the sockets reach blaze-core. Nginx’s connection bounding is both asynchronous and properly respects backpressure.
* A similar sidecar strategy is viable for other non-HTTP services running on blaze-core.
* http4s-ember-server is an alternative to http4s-blaze-server, but does not yet have HTTP/2 or web socket support. Its performance in terms of RPS is appreciably behind Blaze’s, and as the newest backend, has substantially less industrial uptake.
* http4s-jetty is an alternative to http4s-blaze-server, but does not yet have web socket support. Its performance in terms of requests per second is somewhat behind Blaze’s, and despite Jetty's industrial adoption, the http4s integration has substantially less industrial uptake.
* http4s-tomcat is an alternative to http4s-blaze-server, but does not yet have HTTP/2 web socket support. Its performance in terms of requests per second is somewhat behind Blaze’s, and despite Jetty's industrial adoption, the http4s integration has substantially less industrial uptake.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [http4s/blaze](http://github.com/http4s/blaze)
* Contact us according to the [http4s security policy](https://github.com/http4s/http4s/security/policy)
|
[{'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.http4s:blaze-core_2.11'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.14.15'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.http4s:blaze-core_2.12'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.14.15'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.http4s:blaze-core_2.13'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.14.15'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/http4s/blaze/security/advisories/GHSA-xmw9-q7x9-j5qc'}, {'type': 'WEB', 'url': 'https://github.com/http4s/http4s/security/advisories/GHSA-xhv5-w9c5-2r2w'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-21293'}, {'type': 'WEB', 'url': 'https://github.com/http4s/blaze/commit/4f786177f9fb71ab272f3a5f6c80bca3e5662aa1'}]
|
{'cwe_ids': ['CWE-400', 'CWE-770'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-02-02T21:40:18Z', 'nvd_published_at': '2021-02-02T22:15:00Z'}
|
1.4.0
|
GHSA-wjmf-58vc-xqjr
|
2021-02-25T02:01:56Z
|
2021-02-25T02:01:56Z
|
2021-02-25T02:01:56Z
|
[]
|
Content injection in marked
|
Versions 0.3.7 and earlier of marked When mangling is disabled via option mangle don't escape target href. This allow attacker to inject arbitrary html-event into resulting a tag.
|
[]
|
[{'package': {'ecosystem': 'npm', 'name': 'marked'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.3.9'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/markedjs/marked/issues/926'}, {'type': 'WEB', 'url': 'https://github.com/markedjs/marked/commit/cb72584c5d9d32ebfdbb99e35fb9b81af2b79686'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2019-06-05T20:56:48Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-w736-hf9p-qqh3
|
2021-02-05T21:21:40Z
|
2021-02-08T17:43:36Z
| null |
[]
|
Key Caching behavior in the DynamoDB Encryption Client.
|
### Impact
This advisory concerns users of MostRecentProvider in the DynamoDB Encryption Client with a key provider like AWS Key Management Service that allows for permissions on keys to be modified.
When key usage permissions were changed at the key provider, time-based key reauthorization logic in MostRecentProvider did not reauthorize the use of the key. This created the potential for keys to be used in the DynamoDB Encryption Client after permissions to do so were revoked at the key provider.
### Patches
Fixed as of 1.15.0. We recommend users to modify their code and adopt `CachingMostRecentProvider`.
### Workarounds
Users who cannot upgrade to use the `CachingMostRecentProvider` can call `clear()` on the cache to manually flush all of its contents. Next use of the key will force a re-validation to occur with the key provider.
|
[]
|
[{'package': {'ecosystem': 'Maven', 'name': 'com.amazonaws:aws-dynamodb-encryption-java'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.15.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/aws/aws-dynamodb-encryption-java/security/advisories/GHSA-w736-hf9p-qqh3'}, {'type': 'WEB', 'url': 'https://github.com/aws/aws-dynamodb-encryption-java/commit/7de5f5a5929271ab25bce685089eb7ec564dac4b'}, {'type': 'WEB', 'url': 'https://github.com/aws/aws-dynamodb-encryption-java/blob/master/CHANGELOG.md#1150----2021-02-04'}]
|
{'cwe_ids': ['CWE-862'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2021-02-05T21:21:40Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-x7p5-p2c9-phvg
|
2021-02-02T15:46:07Z
|
2021-02-02T15:47:08Z
| null |
[]
|
Unexpected database bindings
|
This is a follow-up to the previous security advisory (GHSA-3p32-j457-pg5x) which addresses a few additional edge cases.
If a request is crafted where a field that is normally a non-array value is an array, and that input is not validated or cast to its expected type before being passed to the query builder, an unexpected number of query bindings can be added to the query. In some situations, this will simply lead to no results being returned by the query builder; however, it is possible certain queries could be affected in a way that causes the query to return unexpected results.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'laravel/framework'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.20.14'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'laravel/framework'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '7.0.0'}, {'fixed': '7.30.4'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'laravel/framework'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '8.0.0'}, {'fixed': '8.24.0'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'illuminate/database'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.20.14'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'illuminate/database'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '7.0.0'}, {'fixed': '7.30.4'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'illuminate/database'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '8.0.0'}, {'fixed': '8.24.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/laravel/framework/security/advisories/GHSA-x7p5-p2c9-phvg'}, {'type': 'ADVISORY', 'url': 'https://github.com/advisories/GHSA-3p32-j457-pg5x'}, {'type': 'WEB', 'url': 'https://packagist.org/packages/illuminate/database'}, {'type': 'WEB', 'url': 'https://packagist.org/packages/laravel/framework'}]
|
{'cwe_ids': ['CWE-74'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-02-02T15:46:07Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-5hx7-77g4-wqx3
|
2021-02-23T21:30:56Z
|
2021-02-23T21:30:56Z
|
2021-02-23T21:30:56Z
|
[]
|
Incorrect Authorization
|
Versions of aedes before 0.35.1 does not respect its own authorization rules when a client sets a Last Will.
|
[]
|
[{'package': {'ecosystem': 'npm', 'name': 'aedes'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.1.0'}, {'fixed': '0.35.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/mcollina/aedes/issues/211'}, {'type': 'WEB', 'url': 'https://github.com/mcollina/aedes/commit/ffbc1702bb24b596afbb96407cc6db234a4044a8'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2019-05-29T19:18:50Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-288c-cq4h-88gq
|
2022-02-08T22:02:19Z
|
2021-02-18T20:51:54Z
| null |
['CVE-2020-25649']
|
XML External Entity (XXE) Injection in Jackson Databind
|
A flaw was found in FasterXML Jackson Databind, where it did not have entity expansion secured properly. This flaw allows vulnerability to XML external entity (XXE) attacks. The highest threat from this vulnerability is data integrity.
|
[{'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': 'com.fasterxml.jackson.core:jackson-databind'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.7.4'}]}], 'database_specific': {'last_known_affected_version_range': '<= 2.6.7.3'}}, {'package': {'ecosystem': 'Maven', 'name': 'com.fasterxml.jackson.core:jackson-databind'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.7.0.0'}, {'fixed': '2.9.10.7'}]}], 'database_specific': {'last_known_affected_version_range': '<= 2.9.10.6'}}, {'package': {'ecosystem': 'Maven', 'name': 'com.fasterxml.jackson.core:jackson-databind'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.10.0.0'}, {'fixed': '2.10.5.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 2.10.5.0'}}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-25649'}, {'type': 'WEB', 'url': 'https://github.com/FasterXML/jackson-databind/issues/2589'}, {'type': 'WEB', 'url': 'https://bugzilla.redhat.com/show_bug.cgi?id=1887664'}, {'type': 'PACKAGE', 'url': 'https://github.com/FasterXML/jackson-databind'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r011d1430e8f40dff9550c3bc5d0f48b14c01ba8aecabd91d5e495386@%3Ccommits.turbine.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r024b7bda9c43c5560d81238748775c5ecfe01b57280f90df1f773949@%3Cissues.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r04529cedaca40c2ff90af4880493f9c88a8ebf4d1d6c861d23108a5a@%3Cnotifications.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r0881e23bd9034c8f51fdccdc8f4d085ba985dcd738f8520569ca5c3d@%3Cissues.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r0b8dc3acd4503e4ecb6fbd6ea7d95f59941168d8452ac0ab1d1d96bb@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r1b7ed0c4b6c4301d4dfd6fdbc5581b0a789d3240cab55d766f33c6c6@%3Cjira.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r2882fc1f3032cd7be66e28787f04ec6f1874ac68d47e310e30ff7eb1@%3Cjira.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r2b6ddb3a4f4cd11d8f6305011e1b7438ba813511f2e3ab3180c7ffda@%3Ccommits.druid.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r2eb66c182853c69ecfb52f63d3dec09495e9b65be829fd889a081ae1@%3Cdev.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r2f5c5479f99398ef344b7ebd4d90bc3316236c45d0f3bc42090efcd7@%3Cissues.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r31f4ee7d561d56a0c2c2c6eb1d6ce3e05917ff9654fdbfec05dc2b83@%3Ccommits.servicecomb.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r3e6ae311842de4e64c5d560a475b7f9cc7e0a9a8649363c6cf7537eb@%3Ccommits.karaf.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r407538adec3185dd35a05c9a26ae2f74425b15132470cf540f41d85b@%3Cissues.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r45e7350dfc92bb192f3f88e9971c11ab2be0953cc375be3dda5170bd@%3Cissues.flink.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r5b130fe668503c4b7e2caf1b16f86b7f2070fd1b7ef8f26195a2ffbd@%3Cissues.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r5f8a1608d758936bd6bbc5eed980777437b611537bf6fff40663fc71@%3Cjira.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r605764e05e201db33b3e9c2e66ff620658f07ad74f296abe483f7042@%3Creviews.iotdb.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r61db8e7dcb56dc000a5387a88f7a473bacec5ee01b9ff3f55308aacc@%3Cdev.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r61db8e7dcb56dc000a5387a88f7a473bacec5ee01b9ff3f55308aacc@%3Cusers.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r63c87aab97155f3f3cbe11d030c4a184ea0de440ee714977db02e956@%3Cjira.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r68d029ee74ab0f3b0569d0c05f5688cb45dd3abe96a6534735252805@%3Cnotifications.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r6a4f3ef6edfed2e0884269d84798f766779bbbc1005f7884e0800d61@%3Cdev.knox.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r6a6df5647583541e3cb71c75141008802f7025cee1c430d4ed78f4cc@%3Cissues.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r6b11eca1d646f45eb0d35d174e6b1e47cfae5295b92000856bfb6304@%3Cdev.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r6b11eca1d646f45eb0d35d174e6b1e47cfae5295b92000856bfb6304@%3Cusers.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r6cbd599b80e787f02ff7a1391d9278a03f37d6a6f4f943f0f01a62fb@%3Creviews.iotdb.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r6e3d4f7991542119a4ca6330271d7fbf7b9fb3abab24ada82ddf1ee4@%3Cnotifications.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r73bef1bb601a9f093f915f8075eb49fcca51efade57b817afd5def07@%3Ccommits.iotdb.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r765283e145049df9b8998f14dcd444345555aae02b1610cfb3188bf8@%3Cnotifications.iotdb.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r78d53a0a269c18394daf5940105dc8c7f9a2399503c2e78be20abe7e@%3Cjira.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r7cb5b4b3e4bd41a8042e5725b7285877a17bcbf07f4eb3f7b316af60@%3Creviews.iotdb.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r86c78bf7656fdb2dab69cbf17f3d7492300f771025f1a3a65d5e5ce5@%3Ccommits.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r8764bb835bcb8e311c882ff91dd3949c9824e905e880930be56f6ba3@%3Cuser.spark.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r8937a7160717fe8b2221767163c4de4f65bc5466405cb1c5310f9080@%3Cdev.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r8937a7160717fe8b2221767163c4de4f65bc5466405cb1c5310f9080@%3Cusers.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r8ae961c80930e2717c75025414ce48a432cea1137c02f648b1fb9524@%3Cissues.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r900d4408c4189b376d1ec580ea7740ea6f8710dc2f0b7e9c9eeb5ae0@%3Cdev.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r90d1e97b0a743cf697d89a792a9b669909cc5a1692d1e0083a22e66c@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r91722ecfba688b0c565675f8bf380269fde8ec62b54d6161db544c22@%3Ccommits.karaf.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r94c7e86e546120f157264ba5ba61fd29b3a8d530ed325a9b4fa334d7@%3Ccommits.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r95a297eb5fd1f2d3a2281f15340e2413f952e9d5503296c3adc7201a@%3Ccommits.tomee.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/r98bfe3b90ea9408f12c4b447edcb5638703d80bc782430aa0c210a54@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/ra1157e57a01d25e36b0dc17959ace758fc21ba36746de29ba1d8b130@%3Cjira.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/ra409f798a1e5a6652b7097429b388650ccd65fd958cee0b6f69bba00@%3Cissues.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/ra95faf968f3463acb3f31a6fbec31453fc5045325f99f396961886d3@%3Cissues.flink.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/raf13235de6df1d47a717199e1ecd700dff3236632f5c9a1488d9845b@%3Cjira.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rb674520b9f6c808c1bf263b1369e14048ec3243615f35cfd24e33604@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rbf4ce74b0d1fa9810dec50ba3ace0caeea677af7c27a97111c06ccb7@%3Cdev.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rbf4ce74b0d1fa9810dec50ba3ace0caeea677af7c27a97111c06ccb7@%3Cusers.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rc15e90bbef196a5c6c01659e015249d6c9a73581ca9afb8aeecf00d2@%3Cjira.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rc82ff47853289e9cd17f5cfbb053c04cafc75ee32e3d7223963f83bb@%3Cdev.knox.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rc88f2fa2b7bd6443921727aeee7704a1fb02433e722e2abf677e0d3d@%3Ccommits.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rc959cdb57c4fe198316130ff4a5ecbf9d680e356032ff2e9f4f05d54@%3Cjira.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rd317f15a675d114dbf5b488d27eeb2467b4424356b16116eb18a652d@%3Cjira.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rd57c7582adc90e233f23f3727db3df9115b27a823b92374f11453f34@%3Cissues.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rd6f6bf848c2d47fa4a85c27d011d948778b8f7e58ba495968435a0b3@%3Cissues.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rdca8711bb7aa5d47a44682606cd0ea3497e2e922f22b7ee83e81e6c1@%3Cissues.hive.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rdf9a34726482222c90d50ae1b9847881de67dde8cfde4999633d2cdc@%3Ccommits.zookeeper.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/re16f81d3ad49a93dd2f0cba9f8fc88e5fb89f30bf9a2ad7b6f3e69c1@%3Ccommits.karaf.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/re96dc7a13e13e56190a5d80f9e5440a0d0c83aeec6467b562fbf2dca@%3Cjira.kafka.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread.html/rf1809a1374041a969d77afab21fc38925de066bc97e86157d3ac3402@%3Ccommits.karaf.apache.org%3E'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6X2UT4X6M7DLQYBOOHMXBWGYJ65RL2CT/'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20210108-0007/'}, {'type': 'WEB', 'url': 'https://www.oracle.com//security-alerts/cpujul2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuApr2021.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuapr2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujan2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujul2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuoct2021.html'}]
|
{'cwe_ids': ['CWE-611'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-02-18T20:41:26Z', 'nvd_published_at': '2020-12-03T17:15:00Z'}
|
1.4.0
|
GHSA-7ggw-h8pp-r95r
|
2023-09-07T17:47:26Z
|
2021-02-10T02:32:35Z
| null |
['CVE-2021-3311']
|
October CMS Session ID not invalidated after logout
|
### Impact
When logging out, the session ID was not invalidated. This is not a problem while the user is logged out, but as soon as the user logs back in the old session ID would be valid again; which means that anyone that gained access to the old session cookie would be able to act as the logged in user. This is not a major concern for the majority of cases, since it requires a malicious party gaining access to the session cookie in the first place, but nevertheless has been fixed.
### Patches
Issue has been patched in Build 472 (v1.0.472) and v1.1.2.
### Workarounds
Apply https://github.com/octobercms/library/commit/642f597489e6f644d4bd9a0c267e864cabead024 to your installation manually if unable to upgrade to Build 472 or v1.1.2.
### References
- Reported by Anisio (Brazilian Information Security Analyst)
- http://cve.circl.lu/cve/CVE-2021-3311
### For more information
If you have any questions or comments about this advisory:
* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)
### Threat assessment:
<img width="699" alt="Screen Shot 2021-02-07 at 11 50 35 PM" src="https://user-images.githubusercontent.com/7253840/107180881-51eaf000-699f-11eb-8828-333128faf2a6.png">
|
[{'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': 'october/rain'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.0.472'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'october/rain'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.1.0'}, {'fixed': '1.1.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/octobercms/october/security/advisories/GHSA-7ggw-h8pp-r95r'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3311'}, {'type': 'WEB', 'url': 'https://github.com/octobercms/library/commit/642f597489e6f644d4bd9a0c267e864cabead024'}, {'type': 'WEB', 'url': 'https://anisiosantos.me/october-cms-token-reactivation'}, {'type': 'WEB', 'url': 'https://octobercms.com/forum/chan/announcements'}, {'type': 'WEB', 'url': 'https://packagist.org/packages/october/rain'}, {'type': 'WEB', 'url': 'http://cve.circl.lu/cve/CVE-2021-3311'}]
|
{'cwe_ids': ['CWE-613'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-02-10T02:30:45Z', 'nvd_published_at': '2021-02-05T14:15:00Z'}
|
1.4.0
|
GHSA-26hg-crh6-mjrw
|
2021-02-23T21:28:28Z
|
2021-02-23T21:28:28Z
|
2021-02-23T21:28:28Z
|
[]
|
Directory Traversal
|
Affected versions of list-n-stream package (0.0.10 and before), are vulnerable to a directory traversal issue.
|
[]
|
[{'package': {'ecosystem': 'npm', 'name': 'list-n-stream'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.0.11'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/KoryNunn/list-n-stream/commit/99b0b40b34aaedfcdf25da46bef0a06b9c47fb59#diff-78c12f5adc1848d13b1c6f07055d996e'}]
|
{'cwe_ids': [], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2019-05-29T20:01:50Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-c497-v8pv-ch6x
|
2023-08-08T19:28:27Z
|
2021-02-01T15:01:14Z
| null |
['CVE-2021-23329']
|
Prototype pollution in nested-object-assign
|
The package nested-object-assign before 1.0.4 is vulnerable to Prototype Pollution via the default 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': 'npm', 'name': 'nested-object-assign'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.0.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-23329'}, {'type': 'WEB', 'url': 'https://github.com/Geta/NestedObjectAssign/pull/11'}, {'type': 'WEB', 'url': 'https://snyk.io/vuln/SNYK-JS-NESTEDOBJECTASSIGN-1065977'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/package/nested-object-assign'}]
|
{'cwe_ids': ['CWE-400'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2021-02-01T06:29:54Z', 'nvd_published_at': '2021-01-31T16:15:00Z'}
|
1.4.0
|
GHSA-jvg4-9rc2-wvcr
|
2021-02-10T02:17:07Z
|
2021-02-10T02:32:07Z
| null |
[]
|
Generation of fake documents via public GET-call
|
### Impact
Generation of fake documents via public GET-call
### Patches
We recommend to update to the current version 6.3.5.1. You can get the update to 6.3.5.1 regularly via the Auto-Updater or directly via the download overview.
https://www.shopware.com/en/download/#shopware-6
### Workarounds
For older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.
https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659
### For more information
https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-02-2021
|
[]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'shopware/platform'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.3.5.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.3.5.0'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/shopware/platform/security/advisories/GHSA-jvg4-9rc2-wvcr'}, {'type': 'WEB', 'url': 'https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-02-2021'}, {'type': 'WEB', 'url': 'https://github.com/shopware/platform/blob/v6.3.5.1/UPGRADE-6.3.md#6351'}, {'type': 'WEB', 'url': 'https://packagist.org/packages/shopware/platform'}]
|
{'cwe_ids': ['CWE-862'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2021-02-10T02:17:07Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-rhm9-p9w5-fwm7
|
2023-08-30T22:06:59Z
|
2021-02-10T01:32:27Z
| null |
['CVE-2020-36242']
|
PyCA Cryptography symmetrically encrypting large values can lead to integer overflow
|
cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. When certain sequences of `update()` calls with large values (multiple GBs) for symetric encryption or decryption occur, it's possible for an integer overflow to happen, leading to mishandling of buffers. This is patched in version 3.3.2 and newer.
|
[{'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': 'PyPI', 'name': 'cryptography'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.1'}, {'fixed': '3.3.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/pyca/cryptography/security/advisories/GHSA-rhm9-p9w5-fwm7'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36242'}, {'type': 'WEB', 'url': 'https://github.com/pyca/cryptography/issues/5615'}, {'type': 'WEB', 'url': 'https://github.com/pyca/cryptography/commit/82b6ce28389f0a317bc55ba2091a74b346db7cae'}, {'type': 'PACKAGE', 'url': 'https://github.com/pyca/cryptography'}, {'type': 'WEB', 'url': 'https://github.com/pyca/cryptography/blob/master/CHANGELOG.rst'}, {'type': 'WEB', 'url': 'https://github.com/pyca/cryptography/compare/3.3.1...3.3.2'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/L7RGQLK4J5ZQFRLKCHVVG6BKZTUQMG7E/'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpuapr2022.html'}, {'type': 'WEB', 'url': 'https://www.oracle.com/security-alerts/cpujul2022.html'}]
|
{'cwe_ids': ['CWE-190', 'CWE-787'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-02-10T01:31:02Z', 'nvd_published_at': '2021-02-07T20:15:00Z'}
|
1.4.0
|
GHSA-xm8r-5wh6-f46f
|
2021-02-24T19:45:15Z
|
2021-02-24T19:45:15Z
|
2021-02-24T19:45:15Z
|
[]
|
Timing attack
|
While each ID is used for only one authentication attempt, a timing attack is possible to figure out in Autobahn.
|
[]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'autobahn'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.6.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/crossbario/autobahn-python/issues/157'}, {'type': 'WEB', 'url': 'https://www.whitesourcesoftware.com/vulnerability-database/WS-2013-0019'}]
|
{'cwe_ids': [], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2019-06-20T14:32:05Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-94ww-22rx-493x
|
2021-02-24T19:46:35Z
|
2021-02-24T19:46:35Z
|
2021-02-24T19:46:35Z
|
[]
|
Cross-Site Scripting
|
Flower, before 0.9.2, has a XSS on tasks page because data is not properly escaped.
|
[]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'flower'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.9.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/mher/flower/issues/650'}, {'type': 'WEB', 'url': 'https://github.com/mher/flower/commit/0f2eab324f65823340a0146f7a2b44804e4725ee'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2019-06-05T13:52:45Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-f6gj-7592-5jxm
|
2021-02-23T21:33:53Z
|
2021-02-23T21:33:53Z
|
2021-02-23T21:33:53Z
|
[]
|
Directory Traversal
|
Affected versions of node-simple-router package (0.10.0 and before), are vulnerable to a directory traversal issue.
|
[]
|
[{'package': {'ecosystem': 'npm', 'name': 'node-simple-router'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.10.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/sandy98/node-simple-router/commit/dfdd52e2e80607af433097d940b3834fd96df488#diff-b9cfc7f2cdf78a7f4b91a753d10865a2'}]
|
{'cwe_ids': [], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2019-05-29T20:20:42Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-f4hq-453j-p95f
|
2022-05-26T20:40:57Z
|
2021-02-05T20:43:34Z
| null |
['CVE-2021-3189']
|
Open redirect in Slashify
|
The package is an Express middleware that normalises routes by stripping any final slash, redirecting, for example, `bookings/latest/` to `bookings/latest`. However, it does not validate the path it redirects to in any way. In particular, if the path starts with two slashes (or two backslashes, or a slash and a backslash, etc.) it may redirect to a different domain.
Consider the [example from the docs](https://www.npmjs.com/package/slashify#usage). Assume we have run it and started a server on `localhost:3000`, then visiting `localhost:3000///github.com/` redirects you to https://github.com.
## Recommendation
This vulnerability is currently un-patched in the `slashify` package so there is no known safe version of this package. Discontinuing use of `slashify` is recommended.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'slashify'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.0.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-3189'}, {'type': 'WEB', 'url': 'https://github.com/divshot/slashify'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20210401-0004/'}, {'type': 'ADVISORY', 'url': 'https://securitylab.github.com/advisories/GHSL-2020-199-open-redirect-slashify'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/package/slashify'}]
|
{'cwe_ids': ['CWE-601'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2021-02-05T20:42:47Z', 'nvd_published_at': '2021-02-19T23:15:00Z'}
|
1.4.0
|
GHSA-pg53-56cg-4m8q
|
2021-02-22T20:43:03Z
|
2021-02-11T21:36:24Z
| null |
['CVE-2021-21310']
|
Token verification bug in next-auth
|
### Impact
Implementations using the **Prisma database adapter** with the **Email provider** **are impacted**.
Implementations using the Prisma database adapter that are not using the Email provider are not impacted.
Implementations using the default database adapter (TypeORM) with the Email provider are not impacted.
Implementations not using a database are not impacted.
### Patches
This issue is fixed in 3.3.0 and newer versions.
### Workarounds
Those not able to upgrade can alternatively disable the Email provider as a workaround.
### Description
The Prisma database adapter was checking the verification token but not the identifier (the email address associated with the token). This made it possible to use a valid token assigned to one user, to sign in as another user when using the Prima adapter in conjunction with the Email provider. The defect is specific to the community-supported Prisma database adapter in versions <3.3.0 and is not present in the default database adapter (TypeORM).
*Note: The current community-supported adapter was not developed by Prisma.*
The defect was a problem in the implementation of verification function the adapter and is not directly related to Prisma.
The flaw may exist in other third party database adapters that do not check both the identifier and token values.
The design of the database adapter API may be revised in future to help reduce the likelyhood of similar defects.
### Timeline
On Monday (2021-02-08) we were notified via responsible disclosure by Alessandro Angelino (@AlessandroA) of a flaw in the implementation of the Prisma database adapter included with NextAuth.js. A detailed write up and proof of concept were provided.
The following day (2021-02-09) we published a fix in v3.3.0 and confirmed through internal testing, and with Alessandro, that the issue was resolved in the new release and prompted users to upgrade.
On 2021-02-10 we received a CVE ID and published this advisory within a few hours of notification.
We would like to thank Alessandro for using responsible disclose to allow us to address the issue promptly and publish this advisory once an update was available that resolved the issue and Balázs Orbán (@balazsorban44) for facilitating a timely release of the fix.
|
[]
|
[{'package': {'ecosystem': 'npm', 'name': 'next-auth'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.3.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/nextauthjs/next-auth/security/advisories/GHSA-pg53-56cg-4m8q'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-21310'}, {'type': 'WEB', 'url': 'https://github.com/nextauthjs/next-auth/releases/tag/v3.3.0'}, {'type': 'WEB', 'url': 'https://www.npmjs.com/package/next-auth'}]
|
{'cwe_ids': ['CWE-290'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2021-02-11T21:36:12Z', 'nvd_published_at': '2021-02-11T22:15:00Z'}
|
1.4.0
|
GHSA-3rpf-5rqv-689q
|
2022-05-03T03:01:58Z
|
2021-02-26T19:53:24Z
| null |
['CVE-2021-26120']
|
PHP Code Injection by malicious function name in smarty
|
Template authors could inject php code by choosing a malicous {function} name. Sites that cannot fully trust template authors should update as soon as possible. Please upgrade to 3.1.39 or higher.
|
[{'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': 'smarty/smarty'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.1.39'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/smarty-php/smarty/security/advisories/GHSA-3rpf-5rqv-689q'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-26120'}, {'type': 'WEB', 'url': 'https://github.com/smarty-php/smarty/commit/165f1bd4d2eec328cfeaca517a725b46001de838'}, {'type': 'PACKAGE', 'url': 'https://github.com/smarty-php/smarty'}, {'type': 'WEB', 'url': 'https://github.com/smarty-php/smarty/blob/master/CHANGELOG.md'}, {'type': 'WEB', 'url': 'https://github.com/smarty-php/smarty/blob/master/CHANGELOG.md#3139---2021-02-17'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2021/04/msg00004.html'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2021/04/msg00014.html'}, {'type': 'WEB', 'url': 'https://security.gentoo.org/glsa/202105-06'}, {'type': 'WEB', 'url': 'https://srcincite.io/blog/2021/02/18/smarty-template-engine-multiple-sandbox-escape-vulnerabilities.html'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2022/dsa-5151'}]
|
{'cwe_ids': ['CWE-94'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2021-02-26T19:52:58Z', 'nvd_published_at': '2021-02-22T02:15:00Z'}
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.