ecosystem
stringclasses 11
values | vuln_id
stringlengths 10
19
| summary
stringlengths 4
220
⌀ | details
stringlengths 34
13.5k
| aliases
stringlengths 17
87
⌀ | modified_date
stringdate 2019-03-26 14:13:00
2022-05-10 08:46:52
| published_date
stringdate 2012-06-17 03:41:00
2022-05-10 08:46:50
| severity
stringclasses 5
values | score
float64 0
10
⌀ | cwe_id
stringclasses 581
values | refs
stringlengths 82
11.6k
| introduced
stringclasses 843
values | code_refs
stringlengths 46
940
| commits
stringlengths 46
940
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
GHSA | GHSA-qc9x-gjcv-465w | Pipenv's requirements.txt parsing allows malicious index url in comments | ## Issue Summary
Due to a flaw in pipenv's parsing of requirements files, an attacker can insert a specially crafted string inside a comment anywhere within a requirements.txt file, which will cause victims who use pipenv to install the requirements file (e.g. with "`pipenv install -r requirements.txt`") to download dependencies from a package index server controlled by the attacker. By embedding malicious code in packages served from their malicious index server, the attacker can trigger arbitrary remote code execution (RCE) on the victims' systems.
### Impact
The impact of successful exploitation is **severe/critical**.
If an attacker is able to hide a malicious `--index-url` option in a requirements file that a victim installs with pipenv, the attacker can embed arbitrary malicious code in packages served from their malicious index server that will be executed on the victim's host during installation (remote code execution/RCE). Exploitation using this technique would be relatively simple to achieve for an attacker with basic knowledge of Python, as the attacker can simply build a source distribution for any of the packages specified in the requirements file, and embed arbitrary malicious code in the setup.py file. When pip installs from a source distribution, any code in the setup.py is executed by the install process.
Basic attacks might use the initial RCE triggered when a victim installs the attacker's malicious package to steal credentials from the victim's host, leach the host's resources to mine cryptocurrency, or install exploit kits or other malware. More sophisticated attackers may use more advanced techniques to persist access to the victim's host, hide or remove evidence of their attack by deleting references to the malicious index server in the Pipfile and Pipfile.lock generated by pipenv or other potential indicators of compromise. Highly sophisticated attackers could attempt to pivot to additional targets from the initial compromised host, and might leverage any exposed credentials in the compromised host environment or implicit authorization granted to the host to gain privileged access to other systems or resources, such as source repositories or package registries.
### Likelihood
The overall likelihood of exploitation is **low to moderate** depending on a range of factors.
The primary hurdle to successful exploitation of this vulnerability depends on an attacker's ability to surreptitiously insert a specially crafted string into a requirements.txt file which will be installed by a victim (or victims). Unfortunately, because the attacker can insert this string into a comment, the attacker's ability to evade suspicion is greatly increased, and they may even be able to hide the initial payload in plain sight if a victim assumes that comments will be ignored by pipenv as expected.
In many common usage contexts — for example in environments where a requirements file is used to lock or "freeze" dependency versions for reproducible builds — requirements files can often become quite large, particularly when leveraging pip's integrity checking, which requires every dependency specified in the requirements file to includes hashes for all of its distribution files. In such cases, a malicious actor might mask an exploitation attempt by opening a pull request ostensibly to update or "bump" the project's dependencies to their latest versions, but surreptitiously insert a malicious `—index-url` option amidst the many other changes associated with updating the dependencies in a lock file. As these dependency updates often result in hundreds or even thousands of changes spread across the requirements file and are not easy to review manually, such an attack could be difficult to identify or prevent without tools or other mitigating controls.
Moreover, because the `argparse` module is used to parse the `--index-url`, `--extra-index-url`, and `--trusted-host` options, an attacker's ability to obfuscate their payload and hide their malicious intent is even more greatly enhanced, as the attacker may use abbreviated option names, which are supported by default with `argparse`. For example, an attacker can insert the string, "`--t pypi.org`" into a comment anywhere in the requirements file, which will automatically be expanded to "`--trusted-host pypi.org`" during processing by pipenv. This "`--trusted-host pypi.org`" option will disable SSL/TLS validation when pipenv attempts to connect to the default/official package index server (https://pypi.org/simple), and could allow a malicious index server to pose as the pipi.org index server in a man-in-the-middle attack.
Setting up the malicious index server to serve compromised package versions is relatively simple, even for a non-sophisticated attacker. As `pip` uses a simple directory format for serving packages, the malicious packages simply need to be placed in the correct folder structure and served using an HTTP server with autoindex enabled (e.g. `python3 -m http.server`).
Packaging up the exploit code into the malicious package versions would also be trivial for an attacker with basic knowledge of Python development, as the attacker can simply clone the source code for any of the packages specified in the requirements file, embed their malicious exploit code in the cloned package's setup.py file, and then build a source distribution of the package. When pip installs a package from a source distribution, any code in the setup.py is executed by the install process.
### Additional Context & Details
According to the requirements file format specification (https://pip.pypa.io/en/stable/reference/requirements-file-format/#comments), any lines which begin with a "#" character, and/or any text in a line following a whitespace and a "#" character, should be interpreted as a comment which will be removed/ignored during processing of the requirements file.
However, due to a flaw in pipenv's parsing of requirements files, an attacker can insert a specially crafted string inside a comment anywhere within a requirements.txt file, which will cause victims who use pipenv to install the requirements file (e.g. with "`pipenv install -r requirements.txt`") to download dependencies from a package index server controlled by the attacker. By embedding malicious code in packages served from their malicious index server, the attacker is then able to gain arbitrary remote code execution on the victims' systems.
The vulnerable requirements file parsing code is in the parse_indexes(str: line) function of the pipenv.utils module:
https://github.com/pypa/pipenv/blob/cdde3f7bcee6bacba89538f73aba9401337be10c/pipenv/utils.py#L2061-L2078
This function is called iteratively on each line of a requirements file, and uses the argparse module to find and process `--index-url`, `--extra-index-url`, and `--trusted-host` options (and variations thereof). However, it does not ignore these options when they appear in comments, or validate that these options appear on their own lines as required by the requirements file specification (see: https://pip.pypa.io/en/stable/reference/requirements-file-format/#global-options). The options can also be abbreviated due to default behavior provided by the `argparse.ArgumentParser` object used to parse these options in the requirements file, so that `--trusted-host` and `--t` will be treated as equivalent by pipenv, for example.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [https://github.com/pypa/pipenv/](https://github.com/pypa/pipenv/)
* Contact the pipenv maintainers:
* [Dan Ryan](https://github.com/techalchemy)
* [Tzu-ping Chung](https://github.com/uranusjr)
* [Nate Prewitt](https://github.com/nateprewitt)
* Contact the contributor who discovered the issue and authored this report:
* [Chris Passarello](https://github.com/milo-minderbinder) | {'CVE-2022-21668'} | 2022-03-30T16:44:16Z | 2022-01-12T22:29:41Z | HIGH | 8 | {'CWE-20', 'CWE-77'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QHQRIWKDP3SVJABAPEXBIQPKDI6UP7G4/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/56HBA3EOSLEDNCCBJVHE6DO34P56EOUM/', 'https://github.com/pypa/pipenv/security/advisories/GHSA-qc9x-gjcv-465w', 'https://github.com/pypa/pipenv/commit/439782a8ae36c4762c88e43d5f0d8e563371b46f', 'https://github.com/advisories/GHSA-qc9x-gjcv-465w', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KCROBYHUS6DKQPCXBRPCZ5CDBNQTYAWT/', 'https://github.com/pypa/pipenv/releases/tag/v2022.1.8', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21668'} | null | {'https://github.com/pypa/pipenv/commit/439782a8ae36c4762c88e43d5f0d8e563371b46f'} | {'https://github.com/pypa/pipenv/commit/439782a8ae36c4762c88e43d5f0d8e563371b46f'} |
GHSA | GHSA-c56f-grv3-gpfr | Regular expression denial of service in forms | The package forms before 1.3.2 are vulnerable to Regular Expression Denial of Service (ReDoS) via email validation. | {'CVE-2021-23388'} | 2021-06-07T22:10:13Z | 2021-06-07T22:10:13Z | MODERATE | 5.3 | {'CWE-400'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-23388', 'https://github.com/advisories/GHSA-c56f-grv3-gpfr', 'https://github.com/caolan/forms/pull/214/commits/d4bd5b5febfe49c1f585f162e04ec810f8dc47a0', 'https://github.com/caolan/forms/pull/214', 'https://snyk.io/vuln/SNYK-JS-FORMS-1296389'} | null | {'https://github.com/caolan/forms/pull/214/commits/d4bd5b5febfe49c1f585f162e04ec810f8dc47a0'} | {'https://github.com/caolan/forms/pull/214/commits/d4bd5b5febfe49c1f585f162e04ec810f8dc47a0'} |
GHSA | GHSA-7qw8-847f-pggm | Improper Locking in github.com/containers/storage | A deadlock vulnerability was found in 'github.com/containers/storage' in versions before 1.28.1. When a container image is processed, each layer is unpacked using `tar`. If one of those layers is not a valid `tar` archive this causes an error leading to an unexpected situation where the code indefinitely waits for the tar unpacked stream, which never finishes. An attacker could use this vulnerability to craft a malicious image, which when downloaded and stored by an application using containers/storage, would then cause a deadlock leading to a Denial of Service (DoS). | {'CVE-2021-20291'} | 2021-05-25T21:58:26Z | 2021-05-10T19:35:07Z | HIGH | 6.5 | {'CWE-667', 'CWE-400'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WX24EITRXVHDM5M223BVTJA2ODF2FSHI/', 'https://bugzilla.redhat.com/show_bug.cgi?id=1939485', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/R5D7XL7FL24TWFMGQ3K2S72EOUSLZMKL/', 'https://github.com/containers/storage/commit/306fcabc964470e4b3b87a43a8f6b7d698209ee1', 'https://github.com/advisories/GHSA-7qw8-847f-pggm', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SPYOHNG2Q7DCAQZMGYLMENLKALGDLG3X/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-20291', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZNMB7O2UIXE34PGSCSOULGHPX5LIJBMM/', 'https://unit42.paloaltonetworks.com/cve-2021-20291/'} | null | {'https://github.com/containers/storage/commit/306fcabc964470e4b3b87a43a8f6b7d698209ee1'} | {'https://github.com/containers/storage/commit/306fcabc964470e4b3b87a43a8f6b7d698209ee1'} |
GHSA | GHSA-hvmf-r92r-27hr | Django allows unintended model editing | Django 2.1 before 2.1.15 and 2.2 before 2.2.8 allows unintended model editing. A Django model admin displaying inline related models, where the user has view-only permissions to a parent model but edit permissions to the inline model, would be presented with an editing UI, allowing POST requests, for updating the inline model. Directly editing the view-only parent model was not possible, but the parent model's save() method was called, triggering potential side effects, and causing pre and post-save signal handlers to be invoked. (To resolve this, the Django admin is adjusted to require edit permissions on the parent model in order for inline models to be editable.) | {'CVE-2019-19118'} | 2021-08-19T16:04:59Z | 2019-12-04T21:26:28Z | MODERATE | 6.5 | {'CWE-276'} | {'https://github.com/django/django/commit/36f580a17f0b3cb087deadf3b65eea024f479c21', 'https://github.com/django/django/commit/103ebe2b5ff1b2614b85a52c239f471904d26244', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6R4HD22PVEVQ45H2JA2NXH443AYJOPL5/', 'https://nvd.nist.gov/vuln/detail/CVE-2019-19118', 'https://security.netapp.com/advisory/ntap-20191217-0003/', 'https://docs.djangoproject.com/en/dev/releases/security/', 'https://www.djangoproject.com/weblog/2019/dec/02/security-releases/', 'http://www.openwall.com/lists/oss-security/2019/12/02/1', 'https://github.com/advisories/GHSA-hvmf-r92r-27hr', 'https://security.gentoo.org/glsa/202004-17', 'https://groups.google.com/forum/#!topic/django-announce/GjGqDvtNmWQ'} | null | {'https://github.com/django/django/commit/103ebe2b5ff1b2614b85a52c239f471904d26244', 'https://github.com/django/django/commit/36f580a17f0b3cb087deadf3b65eea024f479c21'} | {'https://github.com/django/django/commit/103ebe2b5ff1b2614b85a52c239f471904d26244', 'https://github.com/django/django/commit/36f580a17f0b3cb087deadf3b65eea024f479c21'} |
GHSA | GHSA-c7vg-w8q8-c3wf | Session Fixation | Shopware is an open source eCommerce platform. Potential session hijacking of store customers in versions below 6.3.5.2. We recommend to update to the current version 6.3.5.2. You can get the update to 6.3.5.2 regularly via the Auto-Updater or directly via the download overview. 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. | {'CVE-2021-32710'} | 2021-09-08T18:00:20Z | 2021-09-08T18:00:20Z | MODERATE | 5.9 | {'CWE-384'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-32710', 'https://github.com/shopware/platform/security/advisories/GHSA-h9q8-5gv2-v6mg', 'https://github.com/shopware/platform/commit/010c0154bea57c1fca73277c7431d029db7a972e', 'https://github.com/advisories/GHSA-c7vg-w8q8-c3wf'} | null | {'https://github.com/shopware/platform/commit/010c0154bea57c1fca73277c7431d029db7a972e'} | {'https://github.com/shopware/platform/commit/010c0154bea57c1fca73277c7431d029db7a972e'} |
GHSA | GHSA-5w74-jx7m-x6hv | XSS vulnerability in theme config file in Mautic | ### Impact
Mautic before v2.13.0 has stored XSS via a theme config file.
### Patches
Update to 2.13.0 or later.
### Workarounds
None.
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@mautic.org](mailto:security@mautic.org) | {'CVE-2018-8071'} | 2021-01-19T21:16:17Z | 2021-01-19T21:16:17Z | LOW | 6.1 | {'CWE-79'} | {'https://github.com/mautic/mautic/releases/tag/2.13.0', 'https://github.com/advisories/GHSA-5w74-jx7m-x6hv', 'https://github.com/mautic/mautic/security/advisories/GHSA-5w74-jx7m-x6hv', 'https://nvd.nist.gov/vuln/detail/CVE-2018-8071', 'https://github.com/mautic/mautic/commit/3add236e9cc00ea9b211b52cccc4660379b2ee8b'} | null | {'https://github.com/mautic/mautic/commit/3add236e9cc00ea9b211b52cccc4660379b2ee8b'} | {'https://github.com/mautic/mautic/commit/3add236e9cc00ea9b211b52cccc4660379b2ee8b'} |
GHSA | GHSA-ccmq-qvcp-5mrm | Critical severity vulnerability that affects owlmixin | An exploitable vulnerability exists in the YAML loading functionality of util.py in OwlMixin before 2.0.0a12. A "Load YAML" string or file (aka load_yaml or load_yamlf) can execute arbitrary Python commands resulting in command execution because load is used where safe_load should have been used. An attacker can insert Python into loaded YAML to trigger this vulnerability. | {'CVE-2017-16618'} | 2022-03-22T21:47:59Z | 2018-07-13T16:01:12Z | CRITICAL | 9.8 | null | {'https://joel-malwarebenchmark.github.io/blog/2017/11/08/cve-2017-16618-convert-through-owlmixin/', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16618', 'https://github.com/advisories/GHSA-ccmq-qvcp-5mrm', 'https://github.com/tadashi-aikawa/owlmixin/commit/5d0575303f6df869a515ced4285f24ba721e0d4e', 'https://github.com/tadashi-aikawa/owlmixin/issues/12'} | null | {'https://github.com/tadashi-aikawa/owlmixin/commit/5d0575303f6df869a515ced4285f24ba721e0d4e'} | {'https://github.com/tadashi-aikawa/owlmixin/commit/5d0575303f6df869a515ced4285f24ba721e0d4e'} |
GHSA | GHSA-jgrh-5m3h-9c5f | Web Cache Poisoning in find-my-way | This affects the package find-my-way before 2.2.5, from 3.0.0 and before 3.0.5. It accepts the Accept-Version' header by default, and if versioned routes are not being used, this could lead to a denial of service. Accept-Version can be used as an unkeyed header in a cache poisoning attack. | {'CVE-2020-7764'} | 2020-11-10T20:19:43Z | 2020-11-09T22:17:13Z | MODERATE | 5.9 | {'CWE-444'} | {'https://snyk.io/vuln/SNYK-JS-FINDMYWAY-1038269', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7764', 'https://github.com/advisories/GHSA-jgrh-5m3h-9c5f', 'https://github.com/delvedor/find-my-way/commit/ab408354690e6b9cf3c4724befb3b3fa4bb90aac', 'https://www.npmjs.com/package/find-my-way'} | null | {'https://github.com/delvedor/find-my-way/commit/ab408354690e6b9cf3c4724befb3b3fa4bb90aac'} | {'https://github.com/delvedor/find-my-way/commit/ab408354690e6b9cf3c4724befb3b3fa4bb90aac'} |
GHSA | GHSA-44gg-pmqr-4669 | Access Restriction Bypass in Docker | Docker 1.3.0 through 1.3.1 allows remote attackers to modify the default run profile of image containers and possibly bypass the container by applying unspecified security options to an image. | {'CVE-2014-6408'} | 2022-04-12T22:38:18Z | 2022-02-15T01:57:18Z | MODERATE | 0 | {'CWE-285'} | {'https://secunia.com/advisories/60241', 'https://secunia.com/advisories/60171', 'https://github.com/docker/docker/commit/c9379eb3fbbc484c056f5a5e49d8d0b755a29c45', 'https://lists.opensuse.org/opensuse-security-announce/2014-12/msg00009.html', 'https://github.com/advisories/GHSA-44gg-pmqr-4669', 'https://docs.docker.com/v1.3/release-notes/', 'https://www.openwall.com/lists/oss-security/2014/11/24/5', 'https://nvd.nist.gov/vuln/detail/CVE-2014-6408', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-6408', 'https://lists.fedoraproject.org/pipermail/package-announce/2014-December/145154.html'} | null | {'https://github.com/docker/docker/commit/c9379eb3fbbc484c056f5a5e49d8d0b755a29c45'} | {'https://github.com/docker/docker/commit/c9379eb3fbbc484c056f5a5e49d8d0b755a29c45'} |
GHSA | GHSA-hrjm-c879-pp86 | Side-channel timing attack in libsecp256k1 | An issue was discovered in the libsecp256k1 crate before 0.3.1 for Rust. Scalar::check_overflow allows a timing side-channel attack; consequently, attackers can obtain sensitive information. | {'CVE-2019-25003'} | 2021-08-25T20:46:46Z | 2021-08-25T20:46:46Z | HIGH | 7.5 | {'CWE-208'} | {'https://github.com/paritytech/libsecp256k1/commit/11ba23a9766a5079918cd9f515bc100bc8164b50', 'https://rustsec.org/advisories/RUSTSEC-2019-0027.html', 'https://github.com/advisories/GHSA-hrjm-c879-pp86', 'https://nvd.nist.gov/vuln/detail/CVE-2019-25003'} | null | {'https://github.com/paritytech/libsecp256k1/commit/11ba23a9766a5079918cd9f515bc100bc8164b50'} | {'https://github.com/paritytech/libsecp256k1/commit/11ba23a9766a5079918cd9f515bc100bc8164b50'} |
GHSA | GHSA-m3f9-w3p3-p669 | Heap buffer overflow in `QuantizedMul` | ### Impact
An attacker can cause a heap buffer overflow in `QuantizedMul` by passing in invalid thresholds for the quantization:
```python
import tensorflow as tf
x = tf.constant([256, 328], shape=[1, 2], dtype=tf.quint8)
y = tf.constant([256, 328], shape=[1, 2], dtype=tf.quint8)
min_x = tf.constant([], dtype=tf.float32)
max_x = tf.constant([], dtype=tf.float32)
min_y = tf.constant([], dtype=tf.float32)
max_y = tf.constant([], dtype=tf.float32)
tf.raw_ops.QuantizedMul(x=x, y=y, min_x=min_x, max_x=max_x, min_y=min_y, max_y=max_y)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/87cf4d3ea9949051e50ca3f071fc909538a51cd0/tensorflow/core/kernels/quantized_mul_op.cc#L287-L290) assumes that the 4 arguments are always valid scalars and tries to access the numeric value directly:
```cc
const float min_x = context->input(2).flat<float>()(0);
const float max_x = context->input(3).flat<float>()(0);
const float min_y = context->input(4).flat<float>()(0);
const float max_y = context->input(5).flat<float>()(0);
```
However, if any of these tensors is empty, then `.flat<T>()` is an empty buffer and accessing the element at position 0 results in overflow.
### Patches
We have patched the issue in GitHub commit [efea03b38fb8d3b81762237dc85e579cc5fc6e87](https://github.com/tensorflow/tensorflow/commit/efea03b38fb8d3b81762237dc85e579cc5fc6e87).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team. | {'CVE-2021-29535'} | 2021-05-21T14:22:28Z | 2021-05-21T14:22:28Z | LOW | 2.5 | {'CWE-131', 'CWE-787'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-m3f9-w3p3-p669', 'https://github.com/advisories/GHSA-m3f9-w3p3-p669', 'https://github.com/tensorflow/tensorflow/commit/efea03b38fb8d3b81762237dc85e579cc5fc6e87', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29535'} | null | {'https://github.com/tensorflow/tensorflow/commit/efea03b38fb8d3b81762237dc85e579cc5fc6e87'} | {'https://github.com/tensorflow/tensorflow/commit/efea03b38fb8d3b81762237dc85e579cc5fc6e87'} |
GHSA | GHSA-8j36-q8x7-pm6q | OS Command Injection in systeminformation | This affects the package systeminformation before 4.30.2. The attacker can overwrite the properties and functions of an object, which can lead to executing OS commands. | {'CVE-2020-7778'} | 2022-02-09T23:14:11Z | 2022-02-09T23:14:11Z | HIGH | 7.3 | {'CWE-78'} | {'https://gist.github.com/EffectRenan/b434438938eed0b21b376cedf5c81e80', 'https://snyk.io/vuln/SNYK-JS-SYSTEMINFORMATION-1043753', 'https://github.com/advisories/GHSA-8j36-q8x7-pm6q', 'https://github.com/sebhildebrandt/systeminformation/commit/73dce8d717ca9c3b7b0d0688254b8213b957f0fa%23diff-970ae648187190f86bafc8f193b7538200eba164fad0674428b6487582c089cc', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7778', 'https://github.com/sebhildebrandt/systeminformation/commit/11103a447ab9550c25f1fbec7e6d903720b3fea8%23diff-970ae648187190f86bafc8f193b7538200eba164fad0674428b6487582c089cc', 'https://github.com/sebhildebrandt/systeminformation/blob/master/lib/internet.js'} | null | {'https://github.com/sebhildebrandt/systeminformation/commit/11103a447ab9550c25f1fbec7e6d903720b3fea8#diff-970ae648187190f86bafc8f193b7538200eba164fad0674428b6487582c089cc', 'https://github.com/sebhildebrandt/systeminformation/commit/73dce8d717ca9c3b7b0d0688254b8213b957f0fa#diff-970ae648187190f86bafc8f193b7538200eba164fad0674428b6487582c089cc'} | {'https://github.com/sebhildebrandt/systeminformation/commit/11103a447ab9550c25f1fbec7e6d903720b3fea8#diff-970ae648187190f86bafc8f193b7538200eba164fad0674428b6487582c089cc', 'https://github.com/sebhildebrandt/systeminformation/commit/73dce8d717ca9c3b7b0d0688254b8213b957f0fa#diff-970ae648187190f86bafc8f193b7538200eba164fad0674428b6487582c089cc'} |
GHSA | GHSA-rjh8-p66p-jrh5 | Data races in rusqlite | An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via an Auxdata API data race. | {'CVE-2020-35871'} | 2021-08-25T20:46:59Z | 2021-08-25T20:46:59Z | HIGH | 8.1 | {'CWE-362'} | {'https://github.com/rusqlite/rusqlite/commit/2ef3628dac35aeba0a97d5fb3a57746b4e1d62b3', 'https://github.com/rusqlite/rusqlite/releases/tag/0.23.0', 'https://github.com/advisories/GHSA-rjh8-p66p-jrh5', 'https://rustsec.org/advisories/RUSTSEC-2020-0014.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35871'} | null | {'https://github.com/rusqlite/rusqlite/commit/2ef3628dac35aeba0a97d5fb3a57746b4e1d62b3'} | {'https://github.com/rusqlite/rusqlite/commit/2ef3628dac35aeba0a97d5fb3a57746b4e1d62b3'} |
GHSA | GHSA-484f-743f-6jx2 | Object injection in cookie driver in phpfastcache | ## Object injection in cookie driver
### Impact
An possible object injection has been discovered in cookie driver prior 5.0.13 versions (of 5.x releases).
### Patches
The issue has been addressed by enforcing JSON conversion when deserializing
### Workarounds
If you can't fix it, use another driver such as "Files" (Filesystem)
### References
Fixing release: https://github.com/PHPSocialNetwork/phpfastcache/releases/tag/5.0.13
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the issue tracker](https://github.com/PHPSocialNetwork/phpfastcache/issues)
* Email us at [security@geolim4.com](mailto:security@geolim4.com) | {'CVE-2019-16774'} | 2021-01-08T21:28:17Z | 2019-12-12T22:50:20Z | HIGH | 4.4 | {'CWE-94'} | {'https://github.com/PHPSocialNetwork/phpfastcache/releases/tag/5.0.13', 'https://github.com/advisories/GHSA-484f-743f-6jx2', 'https://github.com/PHPSocialNetwork/phpfastcache/commit/c4527205cb7a402b595790c74310791f5b04a1a4', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16774', 'https://github.com/PHPSocialNetwork/phpfastcache/security/advisories/GHSA-484f-743f-6jx2'} | null | {'https://github.com/PHPSocialNetwork/phpfastcache/commit/c4527205cb7a402b595790c74310791f5b04a1a4'} | {'https://github.com/PHPSocialNetwork/phpfastcache/commit/c4527205cb7a402b595790c74310791f5b04a1a4'} |
GHSA | GHSA-9cx9-x2gp-9qvh | CRLF vulnerability in Fiber | ### Impact
The filename that is given in [c.Attachment()](https://docs.gofiber.io/ctx#attachment) is not escaped, and therefore vulnerable for a CRLF injection attack. I.e. an attacker could upload a custom filename and then give the link to the victim. With this filename, the attacker can change the name of the downloaded file, redirect to another site, change the authorization header, etc.
### Steps to reproduce
```go
package main
import "github.com/gofiber/fiber"
const badFileName = "another secret document.pdf\"\r\nLocation: google.com\r\nAuthorization: \"example_of_session_fixation"
func splitTheResponse(c *fiber.Ctx) {
c.Attachment(badFileName)
}
func main() {
app := fiber.New()
app.Get("/attack", splitTheResponse)
app.Listen("127.0.0.1:8080")
}
```
```
HTTP/1.1 200 OK
Date: Fri, 10 Jul 2020 19:47:04 GMT
Content-Type: application/octet-stream
Content-Length: 0
Content-Disposition: attachment; filename="another secret document.pdf"
Location: google.com
Authorization: "example_of_session_fixation"
```
### Patches
This issue has been patched in `v1.12.6` with commit [579](https://github.com/gofiber/fiber/pull/579/commits/f698b5d5066cfe594102ae252cd58a1fe57cf56f) escaping the filename by default.
### Workarounds
You could of course serialize the input yourself before passing it to `ctx.Attachment()`, this is actually a good practice by default. But in case you forget, we got you covered 👍
### References
A CRLF injection attack is one of several types of injection attacks. It can be used to escalate to more malicious attacks such as Cross-site Scripting (XSS), page injection, web cache poisoning, cache-based defacement, and more. A CRLF injection vulnerability exists if an attacker can inject the CRLF characters into a web application, for example using a user input form or an HTTP request, [see acunetix](https://www.acunetix.com/websitesecurity/crlf-injection/)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [gofiber/fiber](https://github.com/gofiber/fiber)
* Join us on [Discord](https://gofiber.io/discord) | {'CVE-2020-15111'} | 2022-04-19T19:02:30Z | 2021-06-29T21:24:28Z | MODERATE | 4.2 | {'CWE-93', 'CWE-74'} | {'https://github.com/gofiber/fiber/pull/579/commits/f698b5d5066cfe594102ae252cd58a1fe57cf56f', 'https://github.com/advisories/GHSA-9cx9-x2gp-9qvh', 'https://github.com/gofiber/fiber/security/advisories/GHSA-9cx9-x2gp-9qvh', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15111'} | null | {'https://github.com/gofiber/fiber/pull/579/commits/f698b5d5066cfe594102ae252cd58a1fe57cf56f'} | {'https://github.com/gofiber/fiber/pull/579/commits/f698b5d5066cfe594102ae252cd58a1fe57cf56f'} |
GHSA | GHSA-j3rh-8vwq-wh84 | Use of Cryptographically Weak Pseudo-Random Number Generator in JHipster Kotlin | JHipster Kotlin is using an insecure source of randomness to generate all of it's random values. JHipster Kotlin relies upon apache commons lang3 `RandomStringUtils`.
From the documentation:
> Caveat: Instances of Random, upon which the implementation of this class relies, are not cryptographically secure.
> \- https://commons.apache.org/proper/commons-lang/javadocs/api-3.9/org/apache/commons/lang3/RandomStringUtils.html
Here are the examples of JHipster Kotlin'ss use of an insecure PRNG:
https://github.com/jhipster/jhipster-kotlin/blob/193ae8f13c0be686f9687e78bacfedb144c47d8c/generators/server/templates/src/main/kotlin/package/service/util/RandomUtil.kt.ejs#L32
## Proof Of Concepts Already Exist
There has been a POC of taking one RNG value generated `RandomStringUtils` and reversing it to generate all of the past/future RNG values public since March 3rd, 2018.
https://medium.com/@alex91ar/the-java-soothsayer-a-practical-application-for-insecure-randomness-c67b0cd148cd
POC Repository: https://github.com/alex91ar/randomstringutils
## Potential Impact Technical
All that is required is to get one password reset token from a JHipster Kotlin generated service and using the POC above, you can reverse what all future password reset tokens to be generated by this server. This allows an attacker to pick and choose what account they would like to takeover by sending account password reset requests for targeted accounts.
## Potential Impact Scale
Not as large as for the original jhipster project as the kotlin blueprint is not that widely used.
### Patches
Update your generated applications to > 1.2.0
### Workarounds
Change the content of `RandomUtil.kt` like this:
```kotlin
import java.security.SecureRandom
import org.apache.commons.lang3.RandomStringUtils
private const val DEF_COUNT = 20
object RandomUtil {
private val secureRandom: SecureRandom = SecureRandom()
init {
secureRandom.nextBytes(byteArrayOf(64.toByte()))
}
private fun generateRandomAlphanumericString(): String {
return RandomStringUtils.random(DEF_COUNT, 0, 0, true, true, null, secureRandom)
}
/**
* Generate a password.
*
* @return the generated password.
*/
fun generatePassword(): String = generateRandomAlphanumericString()
}
```
Important is to exchange **every** call of `RandomStringUtils.randomAlphaNumeric`.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [JHipster Kotlin](https://github.com/jhipster/jhipster-kotlin) | {'CVE-2019-16303'} | 2022-04-19T19:02:30Z | 2020-06-26T16:48:13Z | CRITICAL | 9.8 | {'CWE-338'} | {'https://github.com/jhipster/jhipster-kotlin/issues/183', 'https://github.com/jhipster/generator-jhipster/security/advisories/GHSA-mwp6-j9wf-968c', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16303', 'https://github.com/jhipster/jhipster-kotlin/security/advisories/GHSA-j3rh-8vwq-wh84', 'https://www.jhipster.tech/2019/09/13/jhipster-release-6.3.0.html', 'https://github.com/jhipster/generator-jhipster/issues/10401', 'https://www.npmjs.com/advisories/1187', 'https://github.com/advisories/GHSA-j3rh-8vwq-wh84', 'https://lists.apache.org/thread.html/r6d243e7e3f25daeb242dacf3def411fba32a9388d3ff84918cb28ddd@%3Cissues.commons.apache.org%3E', 'https://www.npmjs.com/advisories/1188', 'https://github.com/jhipster/generator-jhipster/commit/88448b85fd3e8e49df103f0061359037c2c68ea7', 'https://lists.apache.org/thread.html/rc87fa35a48b5d70b06af6fb81785ed82e82686eb83307aae6d250dc9@%3Cissues.commons.apache.org%3E', 'https://lists.apache.org/thread.html/rc3f00f5d3d2ec0e2381a3b9096d5f5b4d46ec1587ee7e251a3dbb897@%3Cissues.commons.apache.org%3E', 'https://snyk.io/vuln/SNYK-JS-GENERATORJHIPSTER-466980'} | null | {'https://github.com/jhipster/generator-jhipster/commit/88448b85fd3e8e49df103f0061359037c2c68ea7'} | {'https://github.com/jhipster/generator-jhipster/commit/88448b85fd3e8e49df103f0061359037c2c68ea7'} |
GHSA | GHSA-wvjw-p9f5-vq28 | Segfault in `tf.raw_ops.SparseCountSparseOutput` | ### Impact
Passing invalid arguments (e.g., discovered via fuzzing) to `tf.raw_ops.SparseCountSparseOutput` results in segfault.
### Patches
We have patched the issue in GitHub commit [82e6203221865de4008445b13c69b6826d2b28d9](https://github.com/tensorflow/tensorflow/commit/82e6203221865de4008445b13c69b6826d2b28d9).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.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. | {'CVE-2021-29619'} | 2021-05-21T14:29:02Z | 2021-05-21T14:29:02Z | LOW | 2.5 | {'CWE-755'} | {'https://github.com/advisories/GHSA-wvjw-p9f5-vq28', 'https://github.com/tensorflow/tensorflow/commit/82e6203221865de4008445b13c69b6826d2b28d9', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29619', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-wvjw-p9f5-vq28'} | null | {'https://github.com/tensorflow/tensorflow/commit/82e6203221865de4008445b13c69b6826d2b28d9'} | {'https://github.com/tensorflow/tensorflow/commit/82e6203221865de4008445b13c69b6826d2b28d9'} |
GHSA | GHSA-ggmv-6q9p-9gm6 | Cross-site Scripting in django-unicorn | The Unicorn framework before 0.36.1 for Django allows XSS via a component. NOTE: this issue exists because of an incomplete fix for CVE-2021-42053. | {'CVE-2021-42134'} | 2021-10-19T14:51:12Z | 2021-10-12T17:51:04Z | MODERATE | 6.1 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-42134', 'https://github.com/adamghill/django-unicorn/commit/3a832a9e3f6455ddd3b87f646247269918ad10c6', 'https://github.com/adamghill/django-unicorn/compare/0.36.0...0.36.1', 'https://github.com/advisories/GHSA-ggmv-6q9p-9gm6'} | null | {'https://github.com/adamghill/django-unicorn/commit/3a832a9e3f6455ddd3b87f646247269918ad10c6'} | {'https://github.com/adamghill/django-unicorn/commit/3a832a9e3f6455ddd3b87f646247269918ad10c6'} |
GHSA | GHSA-j88m-953w-8r2c | Moderate severity vulnerability that affects rendertron | Error reporting within Rendertron 1.0.0 allows reflected Cross Site Scripting (XSS) from invalid URLs. | {'CVE-2017-18352'} | 2021-09-14T19:19:43Z | 2019-01-07T19:14:21Z | MODERATE | 6.1 | {'CWE-79'} | {'https://github.com/GoogleChrome/rendertron/pull/88', 'https://github.com/GoogleChrome/rendertron/commit/8d70628c96ae72eff6eebb451d26fc9ed6b58b0e', 'https://nvd.nist.gov/vuln/detail/CVE-2017-18352', 'https://bugs.chromium.org/p/chromium/issues/detail?id=759111', 'https://github.com/advisories/GHSA-j88m-953w-8r2c'} | null | {'https://github.com/GoogleChrome/rendertron/commit/8d70628c96ae72eff6eebb451d26fc9ed6b58b0e'} | {'https://github.com/GoogleChrome/rendertron/commit/8d70628c96ae72eff6eebb451d26fc9ed6b58b0e'} |
GHSA | GHSA-cg3h-rc9q-g8v9 | Cross-site Scripting in pimcore | pimcore version 10.3.0 and prior is vulnerable to cross-site scripting. | {'CVE-2022-0509'} | 2022-02-14T22:35:25Z | 2022-02-09T00:00:30Z | MODERATE | 5.4 | {'CWE-79'} | {'https://huntr.dev/bounties/26cdf86c-8edc-4af6-8411-d569699ecd1b', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0509', 'https://github.com/advisories/GHSA-cg3h-rc9q-g8v9', 'https://github.com/pimcore/pimcore/commit/6ccb5c12fc1be065ebce9c89c4677ee939b88597'} | null | {'https://github.com/pimcore/pimcore/commit/6ccb5c12fc1be065ebce9c89c4677ee939b88597'} | {'https://github.com/pimcore/pimcore/commit/6ccb5c12fc1be065ebce9c89c4677ee939b88597'} |
GHSA | GHSA-2575-pghm-6qqx | Incorrect Permission Assignment for Critical Resource and Use of Cache Containing Sensitive Information in Kubernetes | In Kubernetes v1.8.x-v1.14.x, schema info is cached by kubectl in the location specified by --cache-dir (defaulting to $HOME/.kube/http-cache), written with world-writeable permissions (rw-rw-rw-). If --cache-dir is specified and pointed at a different location accessible to other users/groups, the written files may be modified by other users/groups and disrupt the kubectl invocation. | {'CVE-2019-11244'} | 2022-04-12T22:00:59Z | 2022-02-15T01:57:18Z | MODERATE | 2.8 | {'CWE-524', 'CWE-732'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-11244', 'https://github.com/kubernetes/client-go/commit/790a4f63632139cf6731014d00a9a8338f1fbd7d', 'https://security.netapp.com/advisory/ntap-20190509-0002/', 'http://www.securityfocus.com/bid/108064', 'https://github.com/kubernetes/kubernetes/issues/76676', 'https://github.com/kubernetes/kubernetes/pull/77874', 'https://access.redhat.com/errata/RHSA-2020:0020', 'https://github.com/advisories/GHSA-2575-pghm-6qqx', 'https://access.redhat.com/errata/RHSA-2020:0074', 'https://github.com/kubernetes/kubernetes/pull/77874/commits/f228ae3364729caed59087e23c42868454bc3ff4', 'https://access.redhat.com/errata/RHSA-2019:3942'} | null | {'https://github.com/kubernetes/kubernetes/pull/77874/commits/f228ae3364729caed59087e23c42868454bc3ff4', 'https://github.com/kubernetes/client-go/commit/790a4f63632139cf6731014d00a9a8338f1fbd7d'} | {'https://github.com/kubernetes/kubernetes/pull/77874/commits/f228ae3364729caed59087e23c42868454bc3ff4', 'https://github.com/kubernetes/client-go/commit/790a4f63632139cf6731014d00a9a8338f1fbd7d'} |
GHSA | GHSA-6r7x-hc8m-985r | Cross-site Scripting in Joplin | Joplin through 1.0.184 allows Arbitrary File Read via Cross-site Scripting (XSS). | {'CVE-2020-9038'} | 2022-01-04T19:44:56Z | 2020-10-13T17:29:25Z | MODERATE | 5.4 | {'CWE-79'} | {'http://packetstormsecurity.com/files/156582/Joplin-Desktop-1.0.184-Cross-Site-Scripting.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-9038', 'https://github.com/advisories/GHSA-6r7x-hc8m-985r', 'https://github.com/laurent22/joplin/compare/clipper-1.0.19...clipper-1.0.20', 'https://github.com/laurent22/joplin/commit/3db47b575b9cb0a765da3d283baa2c065df0d0bc'} | null | {'https://github.com/laurent22/joplin/commit/3db47b575b9cb0a765da3d283baa2c065df0d0bc'} | {'https://github.com/laurent22/joplin/commit/3db47b575b9cb0a765da3d283baa2c065df0d0bc'} |
GHSA | GHSA-p2cq-cprg-frvm | Out of bounds write in tensorflow-lite | ### Impact
In TensorFlow Lite models using segment sum can trigger a write out bounds / segmentation fault if the segment ids are not sorted. Code assumes that the segment ids are in increasing order, using the last element of the tensor holding them to determine the dimensionality of output tensor:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/segment_sum.cc#L39-L44
This results in allocating insufficient memory for the output tensor and in a write outside the bounds of the output array:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/internal/reference/reference_ops.h#L2625-L2631
This usually results in a segmentation fault, but depending on runtime conditions it can provide for a write gadget to be used in future memory corruption-based exploits.
### Patches
We have patched the issue in 204945b and will release patch releases for all affected versions.
We recommend users to upgrade to TensorFlow 2.2.1, or 2.3.1.
### Workarounds
A potential workaround would be to add a custom `Verifier` to the model loading code to ensure that the segment ids are sorted, although this only handles the case when the segment ids are stored statically in the model.
A similar validation could be done if the segment ids are generated at runtime between inference steps.
If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code.
### 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. | {'CVE-2020-15214'} | 2021-08-26T15:20:07Z | 2020-09-25T18:28:56Z | HIGH | 8.1 | {'CWE-787'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15214', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p2cq-cprg-frvm', 'https://github.com/tensorflow/tensorflow/commit/204945b19e44b57906c9344c0d00120eeeae178a', 'https://github.com/advisories/GHSA-p2cq-cprg-frvm', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1'} | null | {'https://github.com/tensorflow/tensorflow/commit/204945b19e44b57906c9344c0d00120eeeae178a'} | {'https://github.com/tensorflow/tensorflow/commit/204945b19e44b57906c9344c0d00120eeeae178a'} |
GHSA | GHSA-9f66-54xg-pc2c | Open redirect vulnerability | ### Impact
_What kind of vulnerability is it? Who is impacted?_
Open redirect vulnerability - a maliciously crafted link to a jupyter server could redirect the browser to a different website.
All jupyter servers running without a base_url prefix are technically affected, however, these maliciously crafted links can only be reasonably made for known jupyter server hosts. A link to your jupyter server may *appear* safe, but ultimately redirect to a spoofed server on the public internet. This same vulnerability was patched in upstream notebook v5.7.8.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
Patched in jupyter_server 1.1.1. If upgrade is not available, a workaround can be to run your server on a url prefix:
```
jupyter server --ServerApp.base_url=/jupyter/
```
### References
[OWASP page on open redirects](https://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html)
### For more information
If you have any questions or comments about this advisory, or vulnerabilities to report, please email our security list [security@ipython.org](mailto:security@ipython.org).
Credit: Yaniv Nizry from CxSCA group at Checkmarx | {'CVE-2020-26275'} | 2022-04-19T19:02:42Z | 2020-12-21T18:01:41Z | LOW | 6.1 | {'CWE-601'} | {'https://github.com/advisories/GHSA-9f66-54xg-pc2c', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26275', 'https://github.com/jupyter-server/jupyter_server/commit/85e4abccf6ea9321d29153f73b0bd72ccb3a6bca', 'https://advisory.checkmarx.net/advisory/CX-2020-4291', 'https://pypi.org/project/jupyter-server/', 'https://github.com/jupyter-server/jupyter_server/security/advisories/GHSA-9f66-54xg-pc2c'} | null | {'https://github.com/jupyter-server/jupyter_server/commit/85e4abccf6ea9321d29153f73b0bd72ccb3a6bca'} | {'https://github.com/jupyter-server/jupyter_server/commit/85e4abccf6ea9321d29153f73b0bd72ccb3a6bca'} |
GHSA | GHSA-56wv-2wr9-3h9r | Improper Verification of Cryptographic Signature in fastecdsa | An issue was discovered in fastecdsa before 2.1.2. When using the NIST P-256 curve in the ECDSA implementation, the point at infinity is mishandled. This means that for an extreme value in k and s^-1, the signature verification fails even if the signature is correct. This behavior is not solely a usability problem. There are some threat models where an attacker can benefit by successfully guessing users for whom signature verification will fail. | {'CVE-2020-12607'} | 2021-10-12T16:30:37Z | 2021-10-12T16:30:37Z | HIGH | 7.5 | {'CWE-347'} | {'https://github.com/advisories/GHSA-56wv-2wr9-3h9r', 'https://github.com/AntonKueltz/fastecdsa/commit/e592f106edd5acf6dacedfab2ad16fe6c735c9d1', 'https://nvd.nist.gov/vuln/detail/CVE-2020-12607', 'https://github.com/AntonKueltz/fastecdsa/issues/52', 'https://github.com/AntonKueltz/fastecdsa/commit/4a16daeaf139be20654ef58a9fe4c79dc030458c', 'https://github.com/AntonKueltz/fastecdsa/commit/7b64e3efaa806b4daaf73bb5172af3581812f8de'} | null | {'https://github.com/AntonKueltz/fastecdsa/commit/7b64e3efaa806b4daaf73bb5172af3581812f8de', 'https://github.com/AntonKueltz/fastecdsa/commit/4a16daeaf139be20654ef58a9fe4c79dc030458c', 'https://github.com/AntonKueltz/fastecdsa/commit/e592f106edd5acf6dacedfab2ad16fe6c735c9d1'} | {'https://github.com/AntonKueltz/fastecdsa/commit/e592f106edd5acf6dacedfab2ad16fe6c735c9d1', 'https://github.com/AntonKueltz/fastecdsa/commit/7b64e3efaa806b4daaf73bb5172af3581812f8de', 'https://github.com/AntonKueltz/fastecdsa/commit/4a16daeaf139be20654ef58a9fe4c79dc030458c'} |
GHSA | GHSA-5fh3-25xr-g85h | snipe-it is vulnerable to Cross-site Scripting | snipe-it is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). | {'CVE-2021-4018'} | 2021-12-03T20:40:50Z | 2021-12-03T20:40:50Z | MODERATE | 5.4 | {'CWE-79'} | {'https://huntr.dev/bounties/c14395f6-bf0d-4b06-b4d1-b509d8a99b54', 'https://github.com/snipe/snipe-it/releases/tag/v5.3.3', 'https://github.com/advisories/GHSA-5fh3-25xr-g85h', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4018', 'https://github.com/snipe/snipe-it/commit/ff81e6d5366c2cfb15618793ad919ae4cbb3ac57'} | null | {'https://github.com/snipe/snipe-it/commit/ff81e6d5366c2cfb15618793ad919ae4cbb3ac57'} | {'https://github.com/snipe/snipe-it/commit/ff81e6d5366c2cfb15618793ad919ae4cbb3ac57'} |
GHSA | GHSA-6r97-cj55-9hrq | SQL Injection in Django | An issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4. Due to an error in shallow key transformation, key and index lookups for django.contrib.postgres.fields.JSONField, and key lookups for django.contrib.postgres.fields.HStoreField, were subject to SQL injection. This could, for example, be exploited via crafted use of "OR 1=1" in a key or index name to return all records, using a suitably crafted dictionary, with dictionary expansion, as the **kwargs passed to the QuerySet.filter() function. | {'CVE-2019-14234'} | 2022-03-21T21:11:02Z | 2019-08-16T14:00:34Z | CRITICAL | 9.8 | {'CWE-89'} | {'https://www.djangoproject.com/weblog/2019/aug/01/security-releases/', 'https://groups.google.com/forum/#!topic/django-announce/jIoju2-KLDs', 'https://nvd.nist.gov/vuln/detail/CVE-2019-14234', 'https://github.com/django/django/commit/4f5b58f5cd3c57fee9972ab074f8dc6895d8f387', 'https://github.com/advisories/GHSA-6r97-cj55-9hrq'} | null | {'https://github.com/django/django/commit/4f5b58f5cd3c57fee9972ab074f8dc6895d8f387'} | {'https://github.com/django/django/commit/4f5b58f5cd3c57fee9972ab074f8dc6895d8f387'} |
GHSA | GHSA-wcxc-jf6c-8rx9 | Uncaught Exception in libpulse-binding | Affected versions of this crate failed to catch panics crossing FFI boundaries via callbacks, which
is a form of UB. This flaw was corrected by [this commit][1] which was included in version 2.6.0. | null | 2021-08-25T20:57:21Z | 2021-08-25T20:57:21Z | MODERATE | 0 | {'CWE-248'} | {'https://github.com/advisories/GHSA-wcxc-jf6c-8rx9', 'https://rustsec.org/advisories/RUSTSEC-2019-0038.html', 'https://github.com/jnqnfe/pulse-binding-rust/commit/7fd282aef7787577c385aed88cb25d004b85f494'} | null | {'https://github.com/jnqnfe/pulse-binding-rust/commit/7fd282aef7787577c385aed88cb25d004b85f494'} | {'https://github.com/jnqnfe/pulse-binding-rust/commit/7fd282aef7787577c385aed88cb25d004b85f494'} |
GHSA | GHSA-h4j5-c7cj-74xg | Arbitrary Code Injection | This affects the package xmlhttprequest before 1.7.0; all versions of package xmlhttprequest-ssl. Provided requests are sent synchronously (async=False on xhr.open), malicious user input flowing into xhr.send could result in arbitrary code being injected and run. | {'CVE-2020-28502'} | 2021-05-04T18:02:34Z | 2021-05-04T18:02:34Z | HIGH | 9.8 | {'CWE-94'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-28502', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1082938', 'https://snyk.io/vuln/SNYK-JS-XMLHTTPREQUEST-1082935', 'https://github.com/driverdan/node-XMLHttpRequest/blob/1.6.0/lib/XMLHttpRequest.js%23L480', 'https://github.com/driverdan/node-XMLHttpRequest/commit/983cfc244c7567ad6a59e366e55a8037e0497fe6', 'https://github.com/driverdan/node-XMLHttpRequest/blob/1.6.0/lib/XMLHttpRequest.js#L480', 'https://snyk.io/vuln/SNYK-JS-XMLHTTPREQUESTSSL-1082936', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1082937', 'https://github.com/mjwwit/node-XMLHttpRequest/blob/ae38832a0f1347c5e96dda665402509a3458e302/lib/XMLHttpRequest.js#L531', 'https://github.com/advisories/GHSA-h4j5-c7cj-74xg', 'https://github.com/mjwwit/node-XMLHttpRequest/commit/ee1e81fc67729c7c0eba5537ed7fe1e30a6b3291'} | null | {'https://github.com/mjwwit/node-XMLHttpRequest/commit/ee1e81fc67729c7c0eba5537ed7fe1e30a6b3291', 'https://github.com/driverdan/node-XMLHttpRequest/commit/983cfc244c7567ad6a59e366e55a8037e0497fe6'} | {'https://github.com/mjwwit/node-XMLHttpRequest/commit/ee1e81fc67729c7c0eba5537ed7fe1e30a6b3291', 'https://github.com/driverdan/node-XMLHttpRequest/commit/983cfc244c7567ad6a59e366e55a8037e0497fe6'} |
GHSA | GHSA-8jj7-5vxc-pg2q | Integer overflow in TensorFlow | ### Impact
Under certain scenarios, Grappler component of TensorFlow is vulnerable to an integer overflow during [cost estimation for crop and resize](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/grappler/costs/op_level_cost_estimator.cc#L2621-L2689). Since the cropping parameters are user controlled, a malicious person can trigger undefined behavior.
### Patches
We have patched the issue in GitHub commit [0aaaae6eca5a7175a193696383f582f53adab23f](https://github.com/tensorflow/tensorflow/commit/0aaaae6eca5a7175a193696383f582f53adab23f).
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.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. | {'CVE-2022-23587'} | 2022-02-11T20:31:18Z | 2022-02-09T23:27:49Z | HIGH | 8.8 | {'CWE-190'} | {'https://github.com/tensorflow/tensorflow/commit/0aaaae6eca5a7175a193696383f582f53adab23f', 'https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/grappler/costs/op_level_cost_estimator.cc#L2621-L2689', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23587', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-8jj7-5vxc-pg2q', 'https://github.com/advisories/GHSA-8jj7-5vxc-pg2q'} | null | {'https://github.com/tensorflow/tensorflow/commit/0aaaae6eca5a7175a193696383f582f53adab23f'} | {'https://github.com/tensorflow/tensorflow/commit/0aaaae6eca5a7175a193696383f582f53adab23f'} |
GHSA | GHSA-r87w-47m8-22w3 | Template Injection in jsrender | Affected versions of `jsrender` are susceptible to a remote code execution vulnerability when used with server delivered client-side tempates which dynamically embed user input.
## Proof of Concept
```
<POC-REQUEST>
{{for ~x!=1?(constructor.constructor("return arguments.callee.caller")()):~y(10)}}
{{:#data}}
{{/for}}
</POC-REQUEST>
```
```
<POC-RESPONSE>
function anonymous(data,view,j,u) { // template var v,t=j._tag,ret="" +t("for",view,this,[ {view:view,tmpl:1, params:{args:['~x!=1?(constructor.constructor(\"return arguments.callee.caller\")()):~y(10)']}, args:[view.hlp("x")!=1?(data.constructor.constructor("return arguments.callee.caller")()):view.hlp("y")(10)], props:{}}]); return ret; }
<POC-RESPONSE>
```
## Recommendation
Update to version 0.9.74 or later. | {'CVE-2016-3942'} | 2021-09-23T21:26:40Z | 2020-09-01T15:24:24Z | MODERATE | 6.3 | {'CWE-94'} | {'https://github.com/advisories/GHSA-r87w-47m8-22w3', 'https://github.com/BorisMoore/jsrender/commit/f984e139deb0a7648d5b543860ec652c21f6dcf6', 'https://nvd.nist.gov/vuln/detail/CVE-2016-3942', 'https://snyk.io/vuln/SNYK-DOTNET-JSRENDER-60173', 'https://www.npmjs.com/advisories/97'} | null | {'https://github.com/BorisMoore/jsrender/commit/f984e139deb0a7648d5b543860ec652c21f6dcf6'} | {'https://github.com/BorisMoore/jsrender/commit/f984e139deb0a7648d5b543860ec652c21f6dcf6'} |
GHSA | GHSA-6346-5r4h-ff5x | Microweber vulnerable to cross-site scripting (XSS) | Microweber is a drag and drop website builder and a powerful next generation CMS. Microweber versions 1.2.15 and prior are vulnerable to cross-site scripting. This could lead to injection of arbitrary JaveScript code, defacement of a page, or stealing cookies. A patch is available on the `master` branch of Microweber's GitHub repository. | {'CVE-2022-1555'} | 2022-05-05T21:08:08Z | 2022-05-05T00:00:26Z | HIGH | 0 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-1555', 'https://github.com/microweber/microweber/commit/724e2d186a33c0c27273107dc4f160a09384877f', 'https://github.com/advisories/GHSA-6346-5r4h-ff5x', 'https://huntr.dev/bounties/d9f9b5bd-16f3-4eaa-9e36-d4958b557687'} | null | {'https://github.com/microweber/microweber/commit/724e2d186a33c0c27273107dc4f160a09384877f'} | {'https://github.com/microweber/microweber/commit/724e2d186a33c0c27273107dc4f160a09384877f'} |
GHSA | GHSA-wc9w-wvq2-ffm9 | Server Side Request Forgery in Grafana | The avatar feature in Grafana 3.0.1 through 7.0.1 has an SSRF Incorrect Access Control issue that allows remote code execution. This vulnerability allows any unauthenticated user/client to make Grafana send HTTP requests to any URL and return its result to the user/client. This can be used to gain information about the network that Grafana is running on. | {'CVE-2020-13379'} | 2022-04-12T22:53:25Z | 2022-02-15T01:57:18Z | MODERATE | 5.4 | {'CWE-918'} | {'http://www.openwall.com/lists/oss-security/2020/06/03/4', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00017.html', 'https://grafana.com/blog/2020/06/03/grafana-6.7.4-and-7.0.2-released-with-important-security-fix/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EEKSZ6GE4EDOFZ23NGYWOCMD6O4JF5SO/', 'http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00083.html', 'https://lists.apache.org/thread.html/rba0247a27be78bd14046724098462d058a9969400a82344b3007cf90@%3Cdev.ambari.apache.org%3E', 'https://lists.apache.org/thread.html/r40f0a97b6765de6b8938bc212ee9dfb5101e9efa48bcbbdec02b2a60@%3Cissues.ambari.apache.org%3E', 'https://community.grafana.com/t/release-notes-v6-7-x/27119', 'https://community.grafana.com/t/release-notes-v7-0-x/29381', 'https://lists.apache.org/thread.html/re75f59639f3bc1d14c7ab362bc4485ade84f3c6a3c1a03200c20fe13@%3Cissues.ambari.apache.org%3E', 'https://lists.apache.org/thread.html/r984c3b42a500f5a6a89fbee436b9432fada5dc27ebab04910aafe4da@%3Cissues.ambari.apache.org%3E', 'https://lists.apache.org/thread.html/r0928ee574281f8b6156e0a6d0291bfc27100a9dd3f9b0177ece24ae4@%3Cdev.ambari.apache.org%3E', 'https://lists.apache.org/thread.html/r6bb57124a21bb638f552d81650c66684e70fc1ff9f40b6a8840171cd@%3Cissues.ambari.apache.org%3E', 'https://mostwanted002.cf/post/grafanados/', 'https://lists.apache.org/thread.html/r093b405a49fd31efa0d949ac1a887101af1ca95652a66094194ed933@%3Cdev.ambari.apache.org%3E', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00009.html', 'https://rhynorater.github.io/CVE-2020-13379-Write-Up', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/O2KSCCGKNEENZN3DW7TSPFBBUZH3YZXZ/', 'https://security.netapp.com/advisory/ntap-20200608-0006/', 'https://lists.apache.org/thread.html/re7c4b251b52f49ba6ef752b829bca9565faaf93d03206b1db6644d31@%3Cdev.ambari.apache.org%3E', 'https://lists.apache.org/thread.html/r6670a6c29044bcb77d4e5d165b5bd13fffe37b84caa5d6471b13b3a2@%3Cdev.ambari.apache.org%3E', 'https://www.exploit-db.com/exploits/48638', 'https://nvd.nist.gov/vuln/detail/CVE-2020-13379', 'https://lists.apache.org/thread.html/rad99b06d7360a5cf6e394afb313f8901dcd4cb777aee9c9197b3b23d@%3Cdev.ambari.apache.org%3E', 'https://lists.apache.org/thread.html/rff71126fa7d9f572baafb9be44078ad409c85d2c0f3e26664f1ef5a2@%3Cdev.ambari.apache.org%3E', 'https://github.com/advisories/GHSA-wc9w-wvq2-ffm9', 'https://lists.apache.org/thread.html/rd0fd283e3844b9c54cd5ecc92d966f96d3f4318815bbf3ac41f9c820@%3Ccommits.ambari.apache.org%3E', 'http://lists.opensuse.org/opensuse-security-announce/2020-06/msg00060.html', 'https://community.grafana.com/t/grafana-7-0-2-and-6-7-4-security-update/31408', 'https://github.com/grafana/grafana/commit/ba953be95f0302c2ea80d23f1e5f2c1847365192', 'http://www.openwall.com/lists/oss-security/2020/06/09/2', 'http://packetstormsecurity.com/files/158320/Grafana-7.0.1-Denial-Of-Service.html'} | null | {'https://github.com/grafana/grafana/commit/ba953be95f0302c2ea80d23f1e5f2c1847365192'} | {'https://github.com/grafana/grafana/commit/ba953be95f0302c2ea80d23f1e5f2c1847365192'} |
GHSA | GHSA-wm93-f238-7v37 | Integer overflow in Tensorflow | ### Impact
The [implementation of `OpLevelCostEstimator::CalculateOutputSize`](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/grappler/costs/op_level_cost_estimator.cc#L1598-L1617) is vulnerable to an integer overflow if an attacker can create an operation which would involve tensors with large enough number of elements:
```cc
for (const auto& dim : output_shape.dim()) {
output_size *= dim.size();
}
```
Here, we can have a large enough number of dimensions in `output_shape.dim()` or just a small number of dimensions being large enough to cause an overflow in the multiplication.
### Patches
We have patched the issue in GitHub commit [b9bd6cfd1c50e6807846af9a86f9b83cafc9c8ae](https://github.com/tensorflow/tensorflow/commit/b9bd6cfd1c50e6807846af9a86f9b83cafc9c8ae).
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.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.
| {'CVE-2022-23576'} | 2022-02-11T20:46:11Z | 2022-02-10T00:32:44Z | MODERATE | 6.5 | {'CWE-190'} | {'https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/grappler/costs/op_level_cost_estimator.cc#L1598-L1617', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23576', 'https://github.com/advisories/GHSA-wm93-f238-7v37', 'https://github.com/tensorflow/tensorflow/commit/b9bd6cfd1c50e6807846af9a86f9b83cafc9c8ae', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-wm93-f238-7v37'} | null | {'https://github.com/tensorflow/tensorflow/commit/b9bd6cfd1c50e6807846af9a86f9b83cafc9c8ae'} | {'https://github.com/tensorflow/tensorflow/commit/b9bd6cfd1c50e6807846af9a86f9b83cafc9c8ae'} |
GHSA | GHSA-pqcf-v8v5-jmcg | Zip slip in Microweber | A directory traversal issue in the Utils/Unzip module in Microweber through 1.1.20 allows an authenticated attacker to gain remote code execution via the backup restore feature. To exploit the vulnerability, an attacker must have the credentials of an administrative user, upload a maliciously constructed ZIP file with file paths including relative paths (i.e., ../../), move this file into the backup directory, and execute a restore on this file. | {'CVE-2020-28337'} | 2022-02-10T22:23:18Z | 2022-02-10T22:23:18Z | HIGH | 7.2 | {'CWE-22'} | {'http://packetstormsecurity.com/files/162514/Microweber-CMS-1.1.20-Remote-Code-Execution.html', 'https://sl1nki.page/blog/2021/02/01/microweber-zip-slip', 'https://github.com/microweber/microweber/commit/777ee9c3e7519eb3672c79ac41066175b2001b50', 'https://github.com/advisories/GHSA-pqcf-v8v5-jmcg', 'https://sl1nki.page/advisories/CVE-2020-28337', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28337'} | null | {'https://github.com/microweber/microweber/commit/777ee9c3e7519eb3672c79ac41066175b2001b50'} | {'https://github.com/microweber/microweber/commit/777ee9c3e7519eb3672c79ac41066175b2001b50'} |
GHSA | GHSA-gj4p-3wh3-2rmf | High severity vulnerability that affects yard | lib/yard/core_ext/file.rb in the server in YARD before 0.9.11 does not block relative paths with an initial ../ sequence, which allows attackers to conduct directory traversal attacks and read arbitrary files. | {'CVE-2017-17042'} | 2021-09-10T21:52:35Z | 2017-12-21T00:47:25Z | HIGH | 7.5 | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2017-17042', 'https://github.com/lsegal/yard/commit/b0217b3e30dc53d057b1682506333335975e62b4', 'https://github.com/advisories/GHSA-gj4p-3wh3-2rmf'} | null | {'https://github.com/lsegal/yard/commit/b0217b3e30dc53d057b1682506333335975e62b4'} | {'https://github.com/lsegal/yard/commit/b0217b3e30dc53d057b1682506333335975e62b4'} |
GHSA | GHSA-84cm-v6jp-gjmr | OS command injection in git-diff-apply | In "index.js" file line 240, the run command executes the git command with a user controlled variable called remoteUrl. This affects git-diff-apply all versions prior to 0.22.2. | {'CVE-2019-10776'} | 2021-08-19T17:14:36Z | 2020-02-14T23:09:24Z | CRITICAL | 9.8 | {'CWE-78'} | {'https://github.com/kellyselden/git-diff-apply/commit/106d61d3ae723b4257c2a13e67b95eb40a27e0b5', 'https://github.com/advisories/GHSA-84cm-v6jp-gjmr', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10776', 'https://snyk.io/vuln/SNYK-JS-GITDIFFAPPLY-540774,', 'https://snyk.io/vuln/SNYK-JS-GITDIFFAPPLY-540774'} | null | {'https://github.com/kellyselden/git-diff-apply/commit/106d61d3ae723b4257c2a13e67b95eb40a27e0b5'} | {'https://github.com/kellyselden/git-diff-apply/commit/106d61d3ae723b4257c2a13e67b95eb40a27e0b5'} |
GHSA | GHSA-72p5-2r6g-fm6v | Moderate severity vulnerability that affects total.js | Total.js CMS 12.0.0 has XSS related to themes/admin/views/index.html (item.message) and themes/admin/public/ui.js (column.format). | {'CVE-2019-10260'} | 2021-06-11T14:17:28Z | 2019-04-02T15:46:52Z | MODERATE | 6.1 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-10260', 'https://github.com/advisories/GHSA-72p5-2r6g-fm6v', 'https://github.com/totaljs/cms/commit/8b9d7dada998c08d172481d9f0fc0397c4b3c78d', 'https://github.com/totaljs/cms/commit/75205f93009db3cf8c0b0f4f1fc8ab82d70da8ad'} | null | {'https://github.com/totaljs/cms/commit/75205f93009db3cf8c0b0f4f1fc8ab82d70da8ad', 'https://github.com/totaljs/cms/commit/8b9d7dada998c08d172481d9f0fc0397c4b3c78d'} | {'https://github.com/totaljs/cms/commit/8b9d7dada998c08d172481d9f0fc0397c4b3c78d', 'https://github.com/totaljs/cms/commit/75205f93009db3cf8c0b0f4f1fc8ab82d70da8ad'} |
GHSA | GHSA-g7p5-5759-qv46 | Data leak in Tensorflow | ### Impact
The `data_splits` argument of [`tf.raw_ops.StringNGrams`](https://www.tensorflow.org/api_docs/python/tf/raw_ops/StringNGrams) lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory
```python
>>> tf.raw_ops.StringNGrams(data=["aa", "bb", "cc", "dd", "ee", "ff"], data_splits=[0,8], separator=" ", ngram_widths=[3], left_pad="", right_pad="", pad_width=0, preserve_short_sequences=False)
StringNGrams(ngrams=<tf.Tensor: shape=(6,), dtype=string, numpy=
array([b'aa bb cc', b'bb cc dd', b'cc dd ee', b'dd ee ff',
b'ee ff \xf4j\xa7q\x7f\x00\x00q\x00\x00\x00\x00\x00\x00\x00\xd8\x9b~\xa8q\x7f\x00',
b'ff \xf4j\xa7q\x7f\x00\x00q\x00\x00\x00\x00\x00\x00\x00\xd8\x9b~\xa8q\x7f\x00 \x9b~\xa8q\x7f\x00\x00p\xf5j\xa7q\x7f\x00\x00H\xf8j\xa7q\x7f\x00\x00\xf0\xf3\xf7\x85q\x7f\x00\x00`}\xa6\x00\x00\x00\x00\x00`~\xa6\x00\x00\x00\x00\x00\xb0~\xeb\x9bq\x7f\x00'],...
```
All the binary strings after `ee ff` are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR.
### Patches
We have patched the issue in 0462de5b544ed4731aa2fb23946ac22c01856b80 and will release patch releases for all versions between 1.15 and 2.3.
We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
### 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. | {'CVE-2020-15205'} | 2021-11-19T15:18:06Z | 2020-09-25T18:28:38Z | CRITICAL | 9 | {'CWE-119', 'CWE-122', 'CWE-787'} | {'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15205', 'https://github.com/advisories/GHSA-g7p5-5759-qv46', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-g7p5-5759-qv46', 'https://github.com/tensorflow/tensorflow/commit/0462de5b544ed4731aa2fb23946ac22c01856b80', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1'} | null | {'https://github.com/tensorflow/tensorflow/commit/0462de5b544ed4731aa2fb23946ac22c01856b80'} | {'https://github.com/tensorflow/tensorflow/commit/0462de5b544ed4731aa2fb23946ac22c01856b80'} |
GHSA | GHSA-hpjm-3ww5-6cpf | Cross-Site Scripting through Fluid view helper arguments | > ### Meta
> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC:C` (5.7)
> * CWE-79
### Problem
Three XSS vulnerabilities have been detected in Fluid:
1. TagBasedViewHelper allowed XSS throug maliciously crafted `additionalAttributes` arrays by creating keys with attribute-closing quotes followed by HTML. When rendering such attributes, TagBuilder would not escape the keys.
2. ViewHelpers which used the `CompileWithContentArgumentAndRenderStatic` trait, and which declared `escapeOutput = false`, would receive the content argument in unescaped format.
3. Subclasses of AbstractConditionViewHelper would receive the `then` and `else` arguments in unescaped format.
### Solution
Update to versions 2.0.8, 2.1.7, 2.2.4, 2.3.7, 2.4.4, 2.5.11 or 2.6.10 of this `typo3fluid/fluid` package that fix the problem described.
Updated versions of this package are bundled in following TYPO3 (`typo3/cms-core`) releases:
* TYPO3 v9.5.23 (using typo3fluid/fluid v2.6.10)
* TYPO3 v10.4.10 (using typo3fluid/fluid v2.6.10)
The specific vulnerabilities are prevented by:
1. Explicitly escaping keys found in the `additionalAttributes` array passed to a TagBasedViewHelper before using them as attribute names.
2. Detecting "content argument" on ViewHelpers using the trait CompileWithContentArgumentAndRenderStatic and escaping it based on the state of `escapeChildren` when `escapeOutput` is toggled off. Escaping still will not occur if explicitly disabled by an enclosing ViewHelper. This homogenises escaping behavior of "content arguments" so the same strategy is used whether the "content" argument is passed as argument or child content.
3. Explicitly defining the `then` and `else` arguments on AbstractConditionViewHelper subclasses as escaped and applying escaping in all cases where escaping is not explicitly disabled by an enclosing ViewHelper.
### Affected cases
1. The fix for TagBasedViewHelper does not affect any valid use cases; it only prevents use of maliciously crafted attribute/value arrays passed as `additionalAttributes`.
2. Any case where a ViewHelper with a "content argument" and which defines `escapeOutput = false` is used with the content argument instead of passing variables as child node - e.g. `<v:h content="{variable}" />` instead of `<v:h>{variable}</v:h>` to intentionally circumvent escaping of any HTML in `{variable}`.
3. Any case where a condition ViewHelper is used with `then` or `else` arguments to render a variable containing HTML, excluding cases where the variable is intentionally unescaped - e.g. `<f:if condition="1" then="{variable -> f:format.raw()}" />`, and excluding any cases where a ViewHelper is used as argument value and the ViewHelper intentionally disables escaping - e.g. `<f:if condition="1" then="{f:render(section: 'MySection')}" />` does not escape the `then` argument because `f:render` disables output escaping.
Cases 2 and 3 can be mitigated to allow variables with HTML to not be escaped, by intentionally disabling escaping by chaining the variable used in the argument with `f:format.raw` as described in case 3. Note that this constitutes a potential security issue, for which the template author is solely responsible. Example: `<f:if condition="1" then="{intentionalHtmlVariable}" />` can allow HTML in `{intentionalHtmlVariable}` by adding `-> f:format.raw()` - to become `<f:if condition="1" then="{intentionalHtmlVariable -> f:format.raw()}" />`.
Custom ViewHelpers which use `CompileWithContentArgumentAndRenderStatic` can alternatively pass a 6th argument with value `false` to the call to `registerArgument` which registers the "content argument", which explicitly disables escaping of the argument value: `$this->registerArgument('arg', 'string', 'My argument', false, null, false);`. Note that this constitutes a potential security issue for which the ViewHelper author is solely responsible. **Variables containing HTML should only be allowed after taking great care to prevent XSS through other means, e.g. sanitising the variable before it is assigned to Fluid or only allowing such variables to come from trusted sources.**
### Credits
Thanks to Jonas Eberle and Sinan Sekerci (Dreamlab Technologies) who reported this issue and to TYPO3 core merger Claus Due who fixed the issue.
### References
* [TYPO3-CORE-SA-2020-009](https://typo3.org/security/advisory/typo3-core-sa-2020-009) | {'CVE-2020-26216'} | 2022-04-19T19:02:41Z | 2020-11-18T21:06:07Z | MODERATE | 8 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-26216', 'https://github.com/TYPO3/Fluid/commit/f20db4e74cf9803c6cffca2ed2f03e1b0b89d0dc', 'https://github.com/advisories/GHSA-hpjm-3ww5-6cpf', 'https://github.com/TYPO3/Fluid/security/advisories/GHSA-hpjm-3ww5-6cpf', 'https://typo3.org/security/advisory/typo3-core-sa-2020-009'} | null | {'https://github.com/TYPO3/Fluid/commit/f20db4e74cf9803c6cffca2ed2f03e1b0b89d0dc'} | {'https://github.com/TYPO3/Fluid/commit/f20db4e74cf9803c6cffca2ed2f03e1b0b89d0dc'} |
GHSA | GHSA-vcwc-6mr9-8m7c | Cross-site Scripting in phpmyadmin | An issue was discovered in phpMyAdmin 5.1 before 5.1.2. An attacker can inject malicious code into aspects of the setup script, which can allow XSS or HTML injection. | {'CVE-2022-23808'} | 2022-01-28T22:36:28Z | 2022-01-28T22:36:28Z | MODERATE | 6.1 | {'CWE-79'} | {'https://github.com/advisories/GHSA-vcwc-6mr9-8m7c', 'https://www.phpmyadmin.net/security/PMASA-2022-2/', 'https://github.com/phpmyadmin/phpmyadmin/commit/5118acce1dfcdb09cbc0f73927bf51c46feeaf38', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23808', 'https://github.com/phpmyadmin/phpmyadmin/commit/44eb12f15a562718bbe54c9a16af91ceea335d59'} | null | {'https://github.com/phpmyadmin/phpmyadmin/commit/44eb12f15a562718bbe54c9a16af91ceea335d59', 'https://github.com/phpmyadmin/phpmyadmin/commit/5118acce1dfcdb09cbc0f73927bf51c46feeaf38'} | {'https://github.com/phpmyadmin/phpmyadmin/commit/5118acce1dfcdb09cbc0f73927bf51c46feeaf38', 'https://github.com/phpmyadmin/phpmyadmin/commit/44eb12f15a562718bbe54c9a16af91ceea335d59'} |
GHSA | GHSA-34f9-hjfq-rr8j | Overflow and uncaught divide by zero in Tensorflow | ### Impact
The [implementation of `UnravelIndex`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/unravel_index_op.cc#L36-L135) is vulnerable to a division by zero caused by an integer overflow bug:
```python
import tensorflow as tf
tf.raw_ops.UnravelIndex(indices=-0x100000,dims=[0x100000,0x100000])
```
### Patches
We have patched the issue in GitHub commit [58b34c6c8250983948b5a781b426f6aa01fd47af](https://github.com/tensorflow/tensorflow/commit/58b34c6c8250983948b5a781b426f6aa01fd47af).
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.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 Yu Tian of Qihoo 360 AIVul Team. | {'CVE-2022-21729'} | 2022-02-11T17:04:54Z | 2022-02-10T00:18:53Z | MODERATE | 6.5 | {'CWE-190'} | {'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/unravel_index_op.cc#L36-L135', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-34f9-hjfq-rr8j', 'https://github.com/tensorflow/tensorflow/commit/58b34c6c8250983948b5a781b426f6aa01fd47af', 'https://github.com/advisories/GHSA-34f9-hjfq-rr8j', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21729'} | null | {'https://github.com/tensorflow/tensorflow/commit/58b34c6c8250983948b5a781b426f6aa01fd47af'} | {'https://github.com/tensorflow/tensorflow/commit/58b34c6c8250983948b5a781b426f6aa01fd47af'} |
GHSA | GHSA-h99w-9q5r-gjq9 | HTTP Request Smuggling in puma | When using Puma behind a proxy that does not properly validate that the incoming HTTP request matches the RFC7230 standard, Puma and the frontend proxy may disagree on where a request starts and ends. This would allow requests to be smuggled via the front-end proxy to Puma.
The following vulnerabilities are addressed by this advisory:
- Lenient parsing of `Transfer-Encoding` headers, when unsupported encodings should be rejected and the final encoding must be `chunked`.
- Lenient parsing of malformed `Content-Length` headers and chunk sizes, when only digits and hex digits should be allowed.
- Lenient parsing of duplicate `Content-Length` headers, when they should be rejected.
- Lenient parsing of the ending of chunked segments, when they should end with `\r\n`.
The vulnerability has been fixed in 5.6.4 and 4.3.12. When deploying a proxy in front of Puma, turning on any and all functionality to make sure that the request matches the RFC7230 standard.
These proxy servers are known to have "good" behavior re: this standard and upgrading Puma may not be necessary. Users are encouraged to validate for themselves.
- Nginx (latest)
- Apache (latest)
- Haproxy 2.5+
- Caddy (latest)
- Traefik (latest) | {'CVE-2022-24790'} | 2022-04-12T16:42:35Z | 2022-03-30T21:48:50Z | CRITICAL | 9.1 | {'CWE-444'} | {'https://github.com/puma/puma/security/advisories/GHSA-h99w-9q5r-gjq9', 'https://github.com/advisories/GHSA-h99w-9q5r-gjq9', 'https://github.com/puma/puma/commit/5bb7d202e24dec00a898dca4aa11db391d7787a5', 'https://portswigger.net/web-security/request-smuggling', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24790'} | null | {'https://github.com/puma/puma/commit/5bb7d202e24dec00a898dca4aa11db391d7787a5'} | {'https://github.com/puma/puma/commit/5bb7d202e24dec00a898dca4aa11db391d7787a5'} |
GHSA | GHSA-x2jc-pwfj-h9p3 | SQL Injection in sequelize | Affected versions of `sequelize` use MySQL's backslash-based escape syntax when connecting to SQLite, despite the fact that SQLite uses PostgreSQL's escape syntax, which can result in a SQL Injection vulnerability.
## Recommendation
Update to version 1.7.0-alpha3 or later. | {'CVE-2016-10554'} | 2021-01-08T00:47:49Z | 2019-02-18T23:54:28Z | MODERATE | 0 | {'CWE-89'} | {'https://github.com/sequelize/sequelize/commit/c876192aa6ce1f67e22b26a4d175b8478615f42d', 'https://nodesecurity.io/advisories/113', 'https://github.com/advisories/GHSA-x2jc-pwfj-h9p3', 'https://www.npmjs.com/advisories/113', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10554'} | null | {'https://github.com/sequelize/sequelize/commit/c876192aa6ce1f67e22b26a4d175b8478615f42d'} | {'https://github.com/sequelize/sequelize/commit/c876192aa6ce1f67e22b26a4d175b8478615f42d'} |
GHSA | GHSA-8928-2fgm-6x9x | HTTP Request Smuggling in actix-http | Affected versions of this crate did not properly detect invalid requests that could allow HTTP/1 request smuggling (HRS) attacks when running alongside a vulnerable front-end proxy server. This can result in leaked internal and/or user data, including credentials, when the front-end proxy is also vulnerable.
Popular front-end proxies and load balancers already mitigate HRS attacks so it is recommended that they are also kept up to date; check your specific set up. You should upgrade even if the front-end proxy receives exclusively HTTP/2 traffic and connects to the back-end using HTTP/1; several downgrade attacks are known that can also expose HRS vulnerabilities. | {'CVE-2021-38512'} | 2021-08-25T20:58:21Z | 2021-08-25T20:58:21Z | HIGH | 7.5 | {'CWE-444'} | {'https://github.com/advisories/GHSA-8928-2fgm-6x9x', 'https://rustsec.org/advisories/RUSTSEC-2021-0081.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/67URRW4K47SR6LNQB4YALPLGGQMQK7HO/', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/actix-http/RUSTSEC-2021-0081.md', 'https://github.com/actix/actix-web/pull/2363', 'https://nvd.nist.gov/vuln/detail/CVE-2021-38512', 'https://github.com/actix/actix-web/commit/e965d8298f421e9c89fe98b1300b8361e948c324'} | null | {'https://github.com/actix/actix-web/commit/e965d8298f421e9c89fe98b1300b8361e948c324'} | {'https://github.com/actix/actix-web/commit/e965d8298f421e9c89fe98b1300b8361e948c324'} |
GHSA | GHSA-9wvh-ff5f-xjpj | Missing Authorization in Harbor | core/api/user.go in Harbor 1.7.0 through 1.8.2 allows non-admin users to create admin accounts via the POST /api/users API. This is fixed in 1.9.0-rc1. | {'CVE-2019-16097'} | 2022-04-12T22:49:27Z | 2022-02-15T01:57:18Z | MODERATE | 6.5 | {'CWE-862'} | {'https://github.com/ianxtianxt/CVE-2019-16097', 'https://github.com/goharbor/harbor/compare/v1.8.2...v1.9.0-rc1', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16097', 'http://www.vmware.com/security/advisories/VMSA-2019-0015.html', 'https://unit42.paloaltonetworks.com/critical-vulnerability-in-harbor-enables-privilege-escalation-from-zero-to-admin-cve-2019-16097/', 'https://github.com/goharbor/harbor/commit/b6db8a8a106259ec9a2c48be8a380cb3b37cf517', 'https://github.com/goharbor/harbor/releases/tag/v1.8.3', 'https://github.com/goharbor/harbor/releases/tag/v1.7.6', 'https://github.com/advisories/GHSA-9wvh-ff5f-xjpj'} | null | {'https://github.com/goharbor/harbor/commit/b6db8a8a106259ec9a2c48be8a380cb3b37cf517'} | {'https://github.com/goharbor/harbor/commit/b6db8a8a106259ec9a2c48be8a380cb3b37cf517'} |
GHSA | GHSA-3jmw-c69h-426c | Cross-Site Request Forgery (CSRF) can run untrusted code on Rundeck server | ### Impact
A user with `admin` access to the `system` resource type is potentially vulnerable to a CSRF attack that could cause the server to run untrusted code on all Rundeck editions.
### Patches
Available in Rundeck 3.4.3 and 3.3.14
### Workarounds
Please visit [https://rundeck.com/security](https://rundeck.com/security) for information about specific workarounds.
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@rundeck.com](mailto:security@rundeck.com)
To report security issues to Rundeck please use the form at [https://rundeck.com/security](https://rundeck.com/security) | {'CVE-2021-39133'} | 2021-09-01T18:26:48Z | 2021-09-01T18:26:48Z | HIGH | 7.2 | {'CWE-352'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-39133', 'https://github.com/rundeck/rundeck/commit/67c4eedeaf9509fc0b255aff15977a5229ef13b9', 'https://github.com/rundeck/rundeck/security/advisories/GHSA-3jmw-c69h-426c', 'https://github.com/advisories/GHSA-3jmw-c69h-426c'} | null | {'https://github.com/rundeck/rundeck/commit/67c4eedeaf9509fc0b255aff15977a5229ef13b9'} | {'https://github.com/rundeck/rundeck/commit/67c4eedeaf9509fc0b255aff15977a5229ef13b9'} |
GHSA | GHSA-g6vq-wc8w-4g69 | firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF) | firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF). | {'CVE-2021-4015'} | 2021-12-06T17:19:18Z | 2021-12-06T17:19:18Z | MODERATE | 4.3 | {'CWE-352'} | {'https://github.com/firefly-iii/firefly-iii/commit/518b4ba5a7a56760902758ae0a2c6a392c2f4d37', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4015', 'https://huntr.dev/bounties/b698d445-602d-4701-961c-dffe6d3009b1', 'https://github.com/advisories/GHSA-g6vq-wc8w-4g69', 'https://github.com/firefly-iii/firefly-iii/releases/tag/5.6.5'} | null | {'https://github.com/firefly-iii/firefly-iii/commit/518b4ba5a7a56760902758ae0a2c6a392c2f4d37'} | {'https://github.com/firefly-iii/firefly-iii/commit/518b4ba5a7a56760902758ae0a2c6a392c2f4d37'} |
GHSA | GHSA-6g33-f262-xjp4 | Cryptographically Weak PRNG in randomatic | Affected versions of `randomatic` generate random values using a cryptographically weak psuedo-random number generator. This may result in predictable values instead of random values as intended.
## Recommendation
Update to version 3.0.0 or later. | {'CVE-2017-16028'} | 2021-01-08T20:58:34Z | 2018-10-09T00:57:21Z | LOW | 0 | {'CWE-330'} | {'https://nvd.nist.gov/vuln/detail/CVE-2017-16028', 'https://github.com/advisories/GHSA-6g33-f262-xjp4', 'https://github.com/tableflip/react-native-meteor-oauth/blob/a7eb738b74c469f5db20296b44b7cae4e2337435/src/meteor-oauth.js#L66', 'https://github.com/jonschlinkert/randomatic/commit/4a526959b3a246ae8e4a82f9c182180907227fe1#diff-b9cfc7f2cdf78a7f4b91a753d10865a2', 'https://nodesecurity.io/advisories/157', 'https://www.npmjs.com/advisories/157'} | null | {'https://github.com/jonschlinkert/randomatic/commit/4a526959b3a246ae8e4a82f9c182180907227fe1#diff-b9cfc7f2cdf78a7f4b91a753d10865a2'} | {'https://github.com/jonschlinkert/randomatic/commit/4a526959b3a246ae8e4a82f9c182180907227fe1#diff-b9cfc7f2cdf78a7f4b91a753d10865a2'} |
GHSA | GHSA-r5jw-62xg-j433 | Cross-Site Scripting in Kaminari | ### Impact
In Kaminari before 1.2.1, there is a vulnerability that would allow an attacker to inject arbitrary code into pages with pagination links. This has been fixed in 1.2.1.
### Releases
The 1.2.1 gem including the patch has already been released.
All past released versions are affected by this vulnerability.
### Workarounds
Application developers who can't update the gem can workaround by overriding the `PARAM_KEY_EXCEPT_LIST` constant.
```ruby
module Kaminari::Helpers
PARAM_KEY_EXCEPT_LIST = [:authenticity_token, :commit, :utf8, :_method, :script_name, :original_script_name].freeze
end
```
### Credits
Thanks to Daniel Mircea for finding the issue and sending a patch via GitHub. Also thanks to Aditya Prakash for reporting the vulnerability. | {'CVE-2020-11082'} | 2022-04-19T19:02:27Z | 2020-05-28T21:10:11Z | MODERATE | 6.4 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-11082', 'https://github.com/github/advisory-review/pull/1020', 'https://github.com/advisories/GHSA-r5jw-62xg-j433', 'https://github.com/kaminari/kaminari/security/advisories/GHSA-r5jw-62xg-j433', 'https://www.debian.org/security/2021/dsa-5005', 'https://github.com/kaminari/kaminari/commit/8dd52a1aed3d2fa2835d836de23fc0d8c4ff5db8', 'https://lists.debian.org/debian-lts-announce/2021/09/msg00011.html'} | null | {'https://github.com/kaminari/kaminari/commit/8dd52a1aed3d2fa2835d836de23fc0d8c4ff5db8'} | {'https://github.com/kaminari/kaminari/commit/8dd52a1aed3d2fa2835d836de23fc0d8c4ff5db8'} |
GHSA | GHSA-hw4v-5x4h-c3xm | Transaction validity oversight in pallet-ethereum | ### Impact
A bug in `pallet-ethereum` can cause invalid transactions to be included in the Ethereum block state in `pallet-ethereum` due to not validating the input data size. Any invalid transactions included this way have no possibility to alter the internal Ethereum or Substrate state. The transaction will appear to have be included, but is of no effect as it is rejected by the EVM engine. The impact is further limited by Substrate extrinsic size constraints.
### Patches
Patches are applied in PR #465.
### Workarounds
None.
### References
Patch PR: https://github.com/paritytech/frontier/pull/465
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [Frontier repo](https://github.com/paritytech/frontier)
| {'CVE-2021-39193'} | 2021-09-07T14:25:43Z | 2021-09-01T18:22:48Z | MODERATE | 5.3 | {'CWE-20'} | {'https://github.com/advisories/GHSA-hw4v-5x4h-c3xm', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39193', 'https://github.com/paritytech/frontier/pull/465', 'https://github.com/paritytech/frontier/security/advisories/GHSA-hw4v-5x4h-c3xm', 'https://github.com/paritytech/frontier/commit/dd112e', 'https://github.com/paritytech/frontier/commit/0b962f218f0cdd796dadfe26c3f09e68f7861b26', 'https://github.com/paritytech/frontier/pull/465/commits/8a2b890a2fb477d5fedd0e4335b00623832849ae'} | null | {'https://github.com/paritytech/frontier/pull/465/commits/8a2b890a2fb477d5fedd0e4335b00623832849ae', 'https://github.com/paritytech/frontier/commit/0b962f218f0cdd796dadfe26c3f09e68f7861b26', 'https://github.com/paritytech/frontier/commit/dd112e'} | {'https://github.com/paritytech/frontier/commit/dd112e', 'https://github.com/paritytech/frontier/pull/465/commits/8a2b890a2fb477d5fedd0e4335b00623832849ae', 'https://github.com/paritytech/frontier/commit/0b962f218f0cdd796dadfe26c3f09e68f7861b26'} |
GHSA | GHSA-mqgv-67vx-g4m5 | Prototype Pollution in js-data | All versions of package js-data prior to 3.0.10 are vulnerable to Prototype Pollution via the deepFillIn function. | {'CVE-2020-28442'} | 2022-02-09T22:46:05Z | 2022-02-09T22:45:52Z | HIGH | 9.8 | {'CWE-1321'} | {'https://github.com/advisories/GHSA-mqgv-67vx-g4m5', 'https://github.com/js-data/js-data/commit/2d9eed5d3e9710d7e7fecc6f6437c39fe73a4097', 'https://github.com/js-data/js-data/pull/574', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28442', 'https://snyk.io/vuln/SNYK-JS-JSDATA-1023655'} | null | {'https://github.com/js-data/js-data/commit/2d9eed5d3e9710d7e7fecc6f6437c39fe73a4097'} | {'https://github.com/js-data/js-data/commit/2d9eed5d3e9710d7e7fecc6f6437c39fe73a4097'} |
GHSA | GHSA-x2w5-5m2g-7h5m | High severity vulnerability that affects com.fasterxml.jackson.core:jackson-databind | FasterXML jackson-databind 2.x before 2.9.7 might allow attackers to conduct external XML entity (XXE) attacks by leveraging failure to block unspecified JDK classes from polymorphic deserialization. | {'CVE-2018-14720'} | 2021-06-10T19:39:26Z | 2019-01-04T19:09:46Z | CRITICAL | 9.8 | {'CWE-502', 'CWE-611'} | {'https://access.redhat.com/errata/RHSA-2019:1108', 'https://github.com/FasterXML/jackson-databind/commit/87d29af25e82a249ea15858e2d4ecbf64091db44', 'https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html', 'https://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html', 'https://lists.apache.org/thread.html/ff8dcfe29377088ab655fda9d585dccd5b1f07fabd94ae84fd60a7f8@%3Ccommits.pulsar.apache.org%3E', 'https://github.com/advisories/GHSA-x2w5-5m2g-7h5m', 'https://lists.apache.org/thread.html/rf1bbc0ea4a9f014cf94df9a12a6477d24a27f52741dbc87f2fd52ff2@%3Cissues.geode.apache.org%3E', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2019/03/msg00005.html', 'https://access.redhat.com/errata/RHBA-2019:0959', 'https://seclists.org/bugtraq/2019/May/68', 'https://access.redhat.com/errata/RHSA-2019:1140', 'https://access.redhat.com/errata/RHSA-2019:4037', 'https://www.debian.org/security/2019/dsa-4452', 'https://security.netapp.com/advisory/ntap-20190530-0003/', 'https://access.redhat.com/errata/RHSA-2019:2858', 'https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html', 'https://lists.apache.org/thread.html/ba973114605d936be276ee6ce09dfbdbf78aa56f6cdc6e79bfa7b8df@%3Cdev.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2018-14720', 'https://access.redhat.com/errata/RHSA-2019:1822', 'https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html', 'https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.9.7', 'https://access.redhat.com/errata/RHSA-2019:0782', 'https://access.redhat.com/errata/RHSA-2019:3149', 'https://access.redhat.com/errata/RHSA-2019:1106', 'https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/82b01bfb6787097427ce97cec6a7127e93718bc05d1efd5eaffc228f@%3Cdev.lucene.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2019:1107', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'https://github.com/FasterXML/jackson-databind/issues/2097', 'https://access.redhat.com/errata/RHSA-2019:3892', 'https://access.redhat.com/errata/RHSA-2019:1823', 'https://lists.apache.org/thread.html/6a78f88716c3c57aa74ec05764a37ab3874769a347805903b393b286@%3Cdev.lucene.apache.org%3E'} | null | {'https://github.com/FasterXML/jackson-databind/commit/87d29af25e82a249ea15858e2d4ecbf64091db44'} | {'https://github.com/FasterXML/jackson-databind/commit/87d29af25e82a249ea15858e2d4ecbf64091db44'} |
GHSA | GHSA-g42g-737j-qx6j | Access Restriction Bypass in kube-apiserver | A vulnerability in Kubernetes `kube-apiserver` could allow node updates to bypass a _Validating Admission Webhook_ and allow unauthorized node updates. The information that is provided to the admission controller could contain old configurations that overwrite values used for validation. Since the overwriting takes place before the validation, this could lead the admission controller to accept requests that should be blocked. The vulnerability can be exploited when an update action on node resources is performed and an admission controller is in place and configured to validate the action.
Users are only affected by this vulnerability if they are running a _Validating Admission Webhook_ for Nodes that denies admission based partially on the old state of the Node object. It only impacts validating admission plugins that rely on old values in certain fields and does not impact calls from kubelets that go through the built-in NodeRestriction admission plugin. | {'CVE-2021-25735'} | 2022-04-12T22:19:17Z | 2021-12-16T19:55:25Z | MODERATE | 6.5 | {'CWE-863', 'CWE-284'} | {'https://github.com/kubernetes/kubernetes/pull/99946', 'https://groups.google.com/g/kubernetes-security-announce/c/FKAGqT4jx9Y', 'https://pkg.go.dev/k8s.io/kubernetes@v1.23.5/cmd/kube-apiserver', 'https://github.com/advisories/GHSA-g42g-737j-qx6j', 'https://sysdig.com/blog/cve-2021-25735-kubernetes-admission-bypass/', 'https://github.com/kubernetes/kubernetes/commit/00e81db174ef7aca497be5f42d87e46d14df2a90', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25735', 'https://github.com/kubernetes/kubernetes/issues/100096', 'https://bugzilla.redhat.com/show_bug.cgi?id=1937562'} | null | {'https://github.com/kubernetes/kubernetes/commit/00e81db174ef7aca497be5f42d87e46d14df2a90'} | {'https://github.com/kubernetes/kubernetes/commit/00e81db174ef7aca497be5f42d87e46d14df2a90'} |
GHSA | GHSA-99wh-973f-779p | XML External Entity Reference in Hazelcast | The AbstractXmlConfigRootTagRecognizer() function makes use of SAXParser generated from a SAXParserFactory with no FEATURE_SECURE_PROCESSING set, allowing for XXE attacks. | {'CVE-2022-0265'} | 2022-04-01T19:47:36Z | 2022-03-04T00:00:15Z | CRITICAL | 9.8 | {'CWE-611'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0265', 'https://github.com/advisories/GHSA-99wh-973f-779p', 'https://huntr.dev/bounties/d63972a2-b910-480a-a86b-d1f75d24d563', 'https://github.com/hazelcast/hazelcast/pull/20407', 'https://github.com/hazelcast/hazelcast/commit/4d6b666cd0291abd618c3b95cdbb51aa4208e748'} | null | {'https://github.com/hazelcast/hazelcast/commit/4d6b666cd0291abd618c3b95cdbb51aa4208e748'} | {'https://github.com/hazelcast/hazelcast/commit/4d6b666cd0291abd618c3b95cdbb51aa4208e748'} |
GHSA | GHSA-r6pg-pjwc-j585 | Null pointer dereference in `SparseFillEmptyRows` | ### Impact
An attacker can trigger a null pointer dereference in the implementation of `tf.raw_ops.SparseFillEmptyRows`:
```python
import tensorflow as tf
indices = tf.constant([], shape=[0, 0], dtype=tf.int64)
values = tf.constant([], shape=[0], dtype=tf.int64)
dense_shape = tf.constant([], shape=[0], dtype=tf.int64)
default_value = 0
tf.raw_ops.SparseFillEmptyRows(
indices=indices, values=values, dense_shape=dense_shape,
default_value=default_value)
```
This is because of missing [validation](https://github.com/tensorflow/tensorflow/blob/fdc82089d206e281c628a93771336bf87863d5e8/tensorflow/core/kernels/sparse_fill_empty_rows_op.cc#L230-L231) that was covered under a `TODO`. If the `dense_shape` tensor is empty, then `dense_shape_t.vec<>()` would cause a null pointer dereference in the implementation of the op:
```cc
template <typename T, typename Tindex>
struct SparseFillEmptyRows<CPUDevice, T, Tindex> {
Status operator()(OpKernelContext* context, const Tensor& default_value_t,
const Tensor& indices_t, const Tensor& values_t,
const Tensor& dense_shape_t,
typename AsyncOpKernel::DoneCallback done) {
...
const auto dense_shape = dense_shape_t.vec<Tindex>();
...
}
}
```
### Patches
We have patched the issue in GitHub commit [faa76f39014ed3b5e2c158593b1335522e573c7f](https://github.com/tensorflow/tensorflow/commit/faa76f39014ed3b5e2c158593b1335522e573c7f).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team. | {'CVE-2021-29565'} | 2021-05-21T14:25:11Z | 2021-05-21T14:25:11Z | LOW | 2.5 | {'CWE-476'} | {'https://github.com/advisories/GHSA-r6pg-pjwc-j585', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-r6pg-pjwc-j585', 'https://github.com/tensorflow/tensorflow/commit/faa76f39014ed3b5e2c158593b1335522e573c7f', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29565'} | null | {'https://github.com/tensorflow/tensorflow/commit/faa76f39014ed3b5e2c158593b1335522e573c7f'} | {'https://github.com/tensorflow/tensorflow/commit/faa76f39014ed3b5e2c158593b1335522e573c7f'} |
GHSA | GHSA-pwpr-vp2v-99xw | Out-of-bounds write | A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1217, CVE-2019-1237, CVE-2019-1298, CVE-2019-1300. | {'CVE-2019-1138'} | 2021-03-29T20:56:11Z | 2021-03-29T20:56:11Z | HIGH | 7.5 | {'CWE-787'} | {'https://github.com/chakra-core/ChakraCore/commit/7e9a2ee60baa95ceb4f48f522f823c812ca90c80', 'https://nvd.nist.gov/vuln/detail/CVE-2019-1138', 'https://github.com/chakra-core/ChakraCore/commit/1e5d3f5e4f4feb37a6844f654d351ddcc53e2046', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1138', 'https://github.com/advisories/GHSA-pwpr-vp2v-99xw'} | null | {'https://github.com/chakra-core/ChakraCore/commit/1e5d3f5e4f4feb37a6844f654d351ddcc53e2046', 'https://github.com/chakra-core/ChakraCore/commit/7e9a2ee60baa95ceb4f48f522f823c812ca90c80'} | {'https://github.com/chakra-core/ChakraCore/commit/7e9a2ee60baa95ceb4f48f522f823c812ca90c80', 'https://github.com/chakra-core/ChakraCore/commit/1e5d3f5e4f4feb37a6844f654d351ddcc53e2046'} |
GHSA | GHSA-px9f-597f-wmcf | Uncontrolled Resource Consumption in Apache OpenMeetings server | If was found that the NetTest web service can be used to overload the bandwidth of a Apache OpenMeetings server. This issue was addressed in Apache OpenMeetings 6.0.0 | {'CVE-2021-27576'} | 2021-06-16T17:43:36Z | 2021-06-16T17:43:36Z | HIGH | 7.5 | {'CWE-400'} | {'https://github.com/advisories/GHSA-px9f-597f-wmcf', 'https://github.com/apache/openmeetings/commit/060a3114ad759931aeb42cd9afa9d1ebb39d3075', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27576', 'https://lists.apache.org/thread.html/r9bb615bd70a0197368f5f3ffc887162686caeb0b5fc30592a7a871e9%40%3Cuser.openmeetings.apache.org%3E', 'https://github.com/apache/openmeetings/commit/afe26c950b127776f2dfe920abff41a584874de8', 'https://issues.apache.org/jira/browse/OPENMEETINGS-2551', 'https://openmeetings.apache.org/security.html#cve-2021-27576---apache-openmeetings-bandwidth-can', 'https://github.com/apache/openmeetings/commit/cbdfd2f9731a8fe3daa9b4adf5da4a063fde161d'} | null | {'https://github.com/apache/openmeetings/commit/cbdfd2f9731a8fe3daa9b4adf5da4a063fde161d', 'https://github.com/apache/openmeetings/commit/060a3114ad759931aeb42cd9afa9d1ebb39d3075', 'https://github.com/apache/openmeetings/commit/afe26c950b127776f2dfe920abff41a584874de8'} | {'https://github.com/apache/openmeetings/commit/060a3114ad759931aeb42cd9afa9d1ebb39d3075', 'https://github.com/apache/openmeetings/commit/afe26c950b127776f2dfe920abff41a584874de8', 'https://github.com/apache/openmeetings/commit/cbdfd2f9731a8fe3daa9b4adf5da4a063fde161d'} |
GHSA | GHSA-7pxj-m4jf-r6h2 | Missing validation during checkpoint loading | ### Impact
An attacker can trigger undefined behavior, integer overflows, segfaults and `CHECK`-fail crashes if they can change saved checkpoints from outside of TensorFlow.
This is because the checkpoints loading infrastructure is missing validation for invalid file formats.
### Patches
We have patched the issue in GitHub commits [b619c6f865715ca3b15ef1842b5b95edbaa710ad](https://github.com/tensorflow/tensorflow/commit/b619c6f865715ca3b15ef1842b5b95edbaa710ad), [e8dc63704c88007ee4713076605c90188d66f3d2](https://github.com/tensorflow/tensorflow/commit/e8dc63704c88007ee4713076605c90188d66f3d2), [368af875869a204b4ac552b9ddda59f6a46a56ec](https://github.com/tensorflow/tensorflow/commit/368af875869a204b4ac552b9ddda59f6a46a56ec), and [abcced051cb1bd8fb05046ac3b6023a7ebcc4578](https://github.com/tensorflow/tensorflow/commit/abcced051cb1bd8fb05046ac3b6023a7ebcc4578).
These fixes will be included in TensorFlow 2.7.0. We will also cherrypick these commits on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. | {'CVE-2021-41203'} | 2021-11-10T19:12:46Z | 2021-11-10T19:12:46Z | HIGH | 7.8 | {'CWE-345'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-41203', 'https://github.com/tensorflow/tensorflow/commit/e8dc63704c88007ee4713076605c90188d66f3d2', 'https://github.com/tensorflow/tensorflow/commit/b619c6f865715ca3b15ef1842b5b95edbaa710ad', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-7pxj-m4jf-r6h2', 'https://github.com/advisories/GHSA-7pxj-m4jf-r6h2', 'https://github.com/tensorflow/tensorflow/commit/368af875869a204b4ac552b9ddda59f6a46a56ec', 'https://github.com/tensorflow/tensorflow/commit/abcced051cb1bd8fb05046ac3b6023a7ebcc4578'} | null | {'https://github.com/tensorflow/tensorflow/commit/e8dc63704c88007ee4713076605c90188d66f3d2', 'https://github.com/tensorflow/tensorflow/commit/abcced051cb1bd8fb05046ac3b6023a7ebcc4578', 'https://github.com/tensorflow/tensorflow/commit/b619c6f865715ca3b15ef1842b5b95edbaa710ad', 'https://github.com/tensorflow/tensorflow/commit/368af875869a204b4ac552b9ddda59f6a46a56ec'} | {'https://github.com/tensorflow/tensorflow/commit/e8dc63704c88007ee4713076605c90188d66f3d2', 'https://github.com/tensorflow/tensorflow/commit/abcced051cb1bd8fb05046ac3b6023a7ebcc4578', 'https://github.com/tensorflow/tensorflow/commit/b619c6f865715ca3b15ef1842b5b95edbaa710ad', 'https://github.com/tensorflow/tensorflow/commit/368af875869a204b4ac552b9ddda59f6a46a56ec'} |
GHSA | GHSA-747p-jfqv-f43r | Downloads Resources over HTTP in mystem3 | Affected versions of `mystem3` insecurely download an executable over an unencrypted HTTP connection.
In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running `mystem3`.
## Recommendation
Update to version 1.0.8 or later. | {'CVE-2016-10626'} | 2021-06-11T14:04:49Z | 2019-02-18T23:47:26Z | HIGH | 8.1 | {'CWE-311'} | {'https://github.com/koorchik/node-mystem3/commit/4bd31c0e0110afc327c414d7ebfc2ffe738cbad2', 'https://nodesecurity.io/advisories/229', 'https://github.com/advisories/GHSA-747p-jfqv-f43r', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10626', 'https://www.npmjs.com/advisories/229'} | null | {'https://github.com/koorchik/node-mystem3/commit/4bd31c0e0110afc327c414d7ebfc2ffe738cbad2'} | {'https://github.com/koorchik/node-mystem3/commit/4bd31c0e0110afc327c414d7ebfc2ffe738cbad2'} |
GHSA | GHSA-f5c9-x9j6-87qp | Prototype pollution in dotty | Prototype pollution vulnerability in 'dotty' before version 0.1.1 allows attackers to cause a denial of service and may lead to remote code execution. | {'CVE-2021-25912'} | 2021-02-05T20:43:08Z | 2021-02-05T20:43:08Z | MODERATE | 0 | {'CWE-400'} | {'https://github.com/deoxxa/dotty/commit/cd997d37917186c131be71501a698803f2b7ebdb', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25912', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25912', 'https://github.com/advisories/GHSA-f5c9-x9j6-87qp', 'https://www.npmjs.com/package/dotty'} | null | {'https://github.com/deoxxa/dotty/commit/cd997d37917186c131be71501a698803f2b7ebdb'} | {'https://github.com/deoxxa/dotty/commit/cd997d37917186c131be71501a698803f2b7ebdb'} |
GHSA | GHSA-9p3v-wf2w-v29c | Moderate severity vulnerability that affects rails | Cross-site scripting (XSS) vulnerability in the strip_tags function in Ruby on Rails before 2.2.s, and 2.3.x before 2.3.5, allows remote attackers to inject arbitrary web script or HTML via vectors involving non-printing ASCII characters, related to HTML::Tokenizer and actionpack/lib/action_controller/vendor/html-scanner/html/node.rb. | {'CVE-2009-4214'} | 2021-09-08T20:12:32Z | 2017-10-24T18:33:38Z | MODERATE | 0 | {'CWE-79'} | {'http://github.com/rails/rails/commit/bfe032858077bb2946abe25e95e485ba6da86bd5', 'https://nvd.nist.gov/vuln/detail/CVE-2009-4214', 'http://www.openwall.com/lists/oss-security/2009/12/08/3', 'http://www.debian.org/security/2011/dsa-2301', 'http://www.debian.org/security/2011/dsa-2260', 'http://secunia.com/advisories/38915', 'http://www.openwall.com/lists/oss-security/2009/11/27/2', 'http://groups.google.com/group/rubyonrails-security/browse_thread/thread/4d4f71f2aef4c0ab?pli=1', 'http://www.securityfocus.com/bid/37142', 'http://lists.opensuse.org/opensuse-security-announce/2010-03/msg00004.html', 'http://secunia.com/advisories/37446', 'http://support.apple.com/kb/HT4077', 'http://www.securitytracker.com/id?1023245', 'http://lists.apple.com/archives/security-announce/2010//Mar/msg00001.html', 'http://www.vupen.com/english/advisories/2009/3352', 'https://github.com/advisories/GHSA-9p3v-wf2w-v29c', 'http://weblog.rubyonrails.org/2009/11/30/ruby-on-rails-2-3-5-released'} | null | {'http://github.com/rails/rails/commit/bfe032858077bb2946abe25e95e485ba6da86bd5'} | {'http://github.com/rails/rails/commit/bfe032858077bb2946abe25e95e485ba6da86bd5'} |
GHSA | GHSA-49wp-qq6x-g2rf | Cross-site Request Forgery in fastify-csrf | The package fastify-csrf before 3.0.0 has a set of issues that affect its ability to do CSRF protection.
1. The generated cookie used insecure defaults, and did not have the httpOnly flag on: `cookieOpts: { path: '/', sameSite: true }`
2. The CSRF token was available in the GET query parameter | {'CVE-2020-28482'} | 2021-01-20T21:30:34Z | 2021-01-20T21:30:34Z | MODERATE | 0 | {'CWE-352'} | {'https://github.com/advisories/GHSA-49wp-qq6x-g2rf', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28482', 'https://github.com/fastify/fastify-csrf/pull/26', 'https://www.npmjs.com/package/fastify-csrf', 'https://github.com/fastify/fastify-csrf/commit/3c9de36e9e73ce0eda9207f84f2ac0243e1f5253', 'https://snyk.io/vuln/SNYK-JS-FASTIFYCSRF-1062044'} | null | {'https://github.com/fastify/fastify-csrf/commit/3c9de36e9e73ce0eda9207f84f2ac0243e1f5253'} | {'https://github.com/fastify/fastify-csrf/commit/3c9de36e9e73ce0eda9207f84f2ac0243e1f5253'} |
GHSA | GHSA-p75f-g7gx-2r7p | Exposure of Sensitive Information to an Unauthorized Actor in Products.PluggableAuthService ZODBRoleManager | ### Impact
_What kind of vulnerability is it? Who is impacted?_
Information disclosure vulnerability - everyone can list the names of roles defined in the ZODB Role Manager plugin if the site uses this plugin.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
The problem has been fixed in version 2.6.0. Depending on how you have installed Products.PluggableAuthService, you should change the buildout version pin to 2.6.0 and re-run the buildout, or if you used pip simply do `pip install "Products.PluggableAuthService>=2.6.0"`
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
There is no workaround. Users are encouraged to upgrade.
### References
_Are there any links users can visit to find out more?_
- [GHSA-p75f-g7gx-2r7p](https://github.com/zopefoundation/Products.PluggableAuthService/security/advisories/GHSA-p75f-g7gx-2r7p)
- [Products.PluggableAuthService on PyPI](https://github.com/zopefoundation/Products.PluggableAuthService)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [Products.PluggableAuthService issue tracker](https://github.com/zopefoundation/Products.PluggableAuthService/issues)
* Email us at [security@plone.org](mailto:security@plone.org) | {'CVE-2021-21336'} | 2022-04-19T19:02:49Z | 2021-03-08T20:38:35Z | LOW | 0 | {'CWE-200'} | {'https://github.com/zopefoundation/Products.PluggableAuthService/security/advisories/GHSA-p75f-g7gx-2r7p', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21336', 'http://www.openwall.com/lists/oss-security/2021/05/22/1', 'http://www.openwall.com/lists/oss-security/2021/05/21/1', 'https://pypi.org/project/Products.PluggableAuthService/', 'https://github.com/zopefoundation/Products.PluggableAuthService/commit/2dad81128250cb2e5d950cddc9d3c0314a80b4bb', 'https://github.com/advisories/GHSA-p75f-g7gx-2r7p'} | null | {'https://github.com/zopefoundation/Products.PluggableAuthService/commit/2dad81128250cb2e5d950cddc9d3c0314a80b4bb'} | {'https://github.com/zopefoundation/Products.PluggableAuthService/commit/2dad81128250cb2e5d950cddc9d3c0314a80b4bb'} |
GHSA | GHSA-xp63-6vf5-xf3v | Command injection in codecov (npm package) | ### Impact
The `upload` method has a command injection vulnerability. Clients of the `codecov-node` library are unlikely to be aware of this, so they might unwittingly write code that contains a vulnerability.
A similar CVE was issued: [CVE-2020-7597](https://github.com/advisories/GHSA-5q88-cjfq-g2mh), but the fix was incomplete. It only blocked `&`, and command injection is still possible using backticks instead to bypass the sanitizer.
We have written a [CodeQL](https://codeql.com) query, which automatically detects this vulnerability. You can see the results of the query on the `codecov-node` project [here](https://lgtm.com/query/7714424068617023832/).
### Patches
This has been patched in version 3.7.1
### Workarounds
None, however, the attack surface is low in this case. Particularly in the standard use of codecov, where the module is used directly in a build pipeline, not built against as a library in another application that may supply malicious input and perform command injection.
### References
* [CVE-2020-7597](https://github.com/advisories/GHSA-5q88-cjfq-g2mh)
### For more information
If you have any questions or comments about this advisory:
* Contact us via our [Security Email](mailto:security@codecov.io) | {'CVE-2020-15123'} | 2021-01-07T23:47:14Z | 2020-07-20T17:20:20Z | MODERATE | 9.3 | {'CWE-78'} | {'https://lgtm.com/query/7714424068617023832', 'https://github.com/codecov/codecov-node/pull/180', 'https://github.com/codecov/codecov-node/commit/c0711c656686e902af2cd92d6aecc8074de4d83d', 'https://github.com/advisories/GHSA-5q88-cjfq-g2mh', 'https://github.com/codecov/codecov-node/security/advisories/GHSA-xp63-6vf5-xf3v', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15123', 'https://github.com/advisories/GHSA-xp63-6vf5-xf3v'} | null | {'https://github.com/codecov/codecov-node/commit/c0711c656686e902af2cd92d6aecc8074de4d83d'} | {'https://github.com/codecov/codecov-node/commit/c0711c656686e902af2cd92d6aecc8074de4d83d'} |
GHSA | GHSA-qhv9-728r-6jqg | ReDoS via long string of semicolons in tough-cookie | Affected versions of `tough-cookie` may be vulnerable to regular expression denial of service when long strings of semicolons exist in the `Set-Cookie` header.
## Recommendation
Update to version 2.3.0 or later. | {'CVE-2016-1000232'} | 2021-09-16T19:58:55Z | 2018-10-10T18:57:02Z | MODERATE | 5.3 | {'CWE-20'} | {'https://github.com/salesforce/tough-cookie/commit/615627206357d997d5e6ff9da158997de05235ae', 'https://www.npmjs.com/advisories/130', 'https://access.redhat.com/errata/RHSA-2017:2912', 'https://nvd.nist.gov/vuln/detail/CVE-2016-1000232', 'https://access.redhat.com/security/cve/cve-2016-1000232', 'https://www.ibm.com/blogs/psirt/ibm-security-bulletin-ibm-api-connect-is-affected-by-node-js-tough-cookie-module-vulnerability-to-a-denial-of-service-cve-2016-1000232/', 'https://github.com/advisories/GHSA-qhv9-728r-6jqg', 'https://access.redhat.com/errata/RHSA-2016:2101', 'https://github.com/salesforce/tough-cookie/commit/e4fc2e0f9ee1b7a818d68f0ac7ea696f377b1534'} | null | {'https://github.com/salesforce/tough-cookie/commit/e4fc2e0f9ee1b7a818d68f0ac7ea696f377b1534', 'https://github.com/salesforce/tough-cookie/commit/615627206357d997d5e6ff9da158997de05235ae'} | {'https://github.com/salesforce/tough-cookie/commit/615627206357d997d5e6ff9da158997de05235ae', 'https://github.com/salesforce/tough-cookie/commit/e4fc2e0f9ee1b7a818d68f0ac7ea696f377b1534'} |
GHSA | GHSA-6q4w-3wp4-q5wf | Denial of Service in get-ip-range | The get-ip-range package before 4.0.0 for Node.js is vulnerable to denial of service (DoS) if the range is untrusted input. An attacker could send a large range (such as 128.0.0.0/1) that causes resource exhaustion. Update get-ip-range dependency to 4.0.0 or above.
| {'CVE-2021-27191'} | 2022-05-03T02:57:48Z | 2021-04-13T15:15:57Z | HIGH | 7.5 | {'CWE-400'} | {'https://security.netapp.com/advisory/ntap-20210319-0002/', 'https://github.com/advisories/GHSA-6q4w-3wp4-q5wf', 'https://www.npmjs.com/package/get-ip-range', 'https://advisory.checkmarx.net/advisory/CX-2021-4304', 'https://github.com/JoeScho/get-ip-range/commit/98ca22b815c77273cbab259811ab0976118e13b6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27191'} | null | {'https://github.com/JoeScho/get-ip-range/commit/98ca22b815c77273cbab259811ab0976118e13b6'} | {'https://github.com/JoeScho/get-ip-range/commit/98ca22b815c77273cbab259811ab0976118e13b6'} |
GHSA | GHSA-q3vw-4jx3-rrr2 | Validation bypass vulnerability | Back in min June a security vulnerability was reported to the team, the reason for the slow response was due to ownership of some packages
was locked and we wanted to be sure to update all packages before any disclosure was released.
The issue is deemed being a Low severity vulnerability.
### Impact
This vulnerability impacts users who rely on the for last digits of personnummer to be a _real_ personnummer.
### Patches
The issue have been patched in all repositories. The following versions should be updated to as soon as possible:
C# 3.0.2
D 3.0.1
Dart 3.0.3
Elixir 3.0.0
Go 3.0.1
Java 3.3.0
JavaScript 3.1.0
Kotlin 1.1.0
Lua 3.0.1
PHP 3.0.2
Perl 3.0.0
Python 3.0.2
Ruby 3.0.1
Rust 3.0.0
Scala 3.0.1
Swift 1.0.1
If you are using any of the earlier packages, please update to latest.
### Workarounds
The issue arrieses from the regular expression allowing the first three digits in the last four digits of the personnummer to be
000, which is invalid. To mitigate this without upgrading, a check on the last four digits can be made to make sure it's not
000x.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Personnummer Meta](https://github.com/personnummer/meta/issues)
* Email us at [Personnummer Email](mailto:security@personnummer.dev)
### Credits
Niklas Sköldmark (Medborgarskolan) | null | 2020-09-23T17:20:09Z | 2020-09-23T17:20:09Z | LOW | 0 | null | {'https://github.com/advisories/GHSA-q3vw-4jx3-rrr2', 'https://github.com/personnummer/java/security/advisories/GHSA-q3vw-4jx3-rrr2', 'https://github.com/personnummer/java/commit/3bad4e3354503d7cfd443257c94c41f57b3d1621'} | null | {'https://github.com/personnummer/java/commit/3bad4e3354503d7cfd443257c94c41f57b3d1621'} | {'https://github.com/personnummer/java/commit/3bad4e3354503d7cfd443257c94c41f57b3d1621'} |
GHSA | GHSA-p44j-xrqg-4xrr | URL Redirection to Untrusted Site ('Open Redirect') in Products.PluggableAuthService | ### Impact
_What kind of vulnerability is it? Who is impacted?_
Open redirect vulnerability - a maliciously crafted link to the login form and login functionality could redirect the browser to a different website.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
The problem has been fixed in version 2.6.1. Depending on how you have installed Products.PluggableAuthService, you should change the buildout version pin to `2.6.1` and re-run the buildout, or if you used `pip` simply do `pip install "Products.PluggableAuthService>=2.6.1"`
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
There is no workaround. Users are encouraged to upgrade.
### References
_Are there any links users can visit to find out more?_
- [GHSA-p44j-xrqg-4xrr](https://github.com/zopefoundation/Products.PluggableAuthService/security/advisories/GHSA-p44j-xrqg-4xrr)
- [Products.PluggableAuthService on PyPI](https://pypi.org/project/Products.PluggableAuthService/)
- [OWASP page on open redirects](https://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [Products.PluggableAuthService issue tracker](https://github.com/zopefoundation/Products.PluggableAuthService/issues)
* Email us at [security@plone.org](mailto:security@plone.org) | {'CVE-2021-21337'} | 2022-04-19T19:02:49Z | 2021-03-08T21:06:23Z | LOW | 0 | {'CWE-601'} | {'https://github.com/zopefoundation/Products.PluggableAuthService/commit/7eead067898852ebd3e0f143bc51295928528dfa', 'https://github.com/advisories/GHSA-p44j-xrqg-4xrr', 'https://github.com/zopefoundation/Products.PluggableAuthService/security/advisories/GHSA-p44j-xrqg-4xrr', 'https://pypi.org/project/Products.PluggableAuthService/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21337', 'http://packetstormsecurity.com/files/162911/Products.PluggableAuthService-2.6.0-Open-Redirect.html'} | null | {'https://github.com/zopefoundation/Products.PluggableAuthService/commit/7eead067898852ebd3e0f143bc51295928528dfa'} | {'https://github.com/zopefoundation/Products.PluggableAuthService/commit/7eead067898852ebd3e0f143bc51295928528dfa'} |
GHSA | GHSA-75pc-qvwc-jf3g | Improper Input Validation in HashiCorp Vault | HashiCorp Vault and Vault Enterprise 1.4.x before 1.4.2 has Incorrect Access Control. | {'CVE-2020-12757'} | 2021-05-18T18:20:48Z | 2021-05-18T18:20:48Z | HIGH | 4 | {'CWE-20'} | {'https://www.hashicorp.com/blog/category/vault/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-12757', 'https://github.com/hashicorp/vault-plugin-secrets-gcp/commit/e43d20870c50f7428dead1411debcec075b35fb4', 'https://github.com/hashicorp/vault-plugin-secrets-gcp/pull/85', 'https://github.com/hashicorp/vault/blob/master/CHANGELOG.md', 'https://github.com/advisories/GHSA-75pc-qvwc-jf3g', 'https://github.com/hashicorp/vault/blob/master/CHANGELOG.md#142-may-21st-2020'} | null | {'https://github.com/hashicorp/vault-plugin-secrets-gcp/commit/e43d20870c50f7428dead1411debcec075b35fb4'} | {'https://github.com/hashicorp/vault-plugin-secrets-gcp/commit/e43d20870c50f7428dead1411debcec075b35fb4'} |
GHSA | GHSA-q99r-j969-6jwr | Out-of-bounds write | A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1138, CVE-2019-1217, CVE-2019-1298, CVE-2019-1300. | {'CVE-2019-1237'} | 2021-03-29T20:56:04Z | 2021-03-29T20:56:04Z | HIGH | 7.5 | {'CWE-787'} | {'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1237', 'https://github.com/chakra-core/ChakraCore/commit/7e9a2ee60baa95ceb4f48f522f823c812ca90c80', 'https://github.com/advisories/GHSA-q99r-j969-6jwr', 'https://github.com/chakra-core/ChakraCore/commit/31f2588c7ba5b446bccf2769e9ecf4d444b73045', 'https://nvd.nist.gov/vuln/detail/CVE-2019-1237'} | null | {'https://github.com/chakra-core/ChakraCore/commit/31f2588c7ba5b446bccf2769e9ecf4d444b73045', 'https://github.com/chakra-core/ChakraCore/commit/7e9a2ee60baa95ceb4f48f522f823c812ca90c80'} | {'https://github.com/chakra-core/ChakraCore/commit/7e9a2ee60baa95ceb4f48f522f823c812ca90c80', 'https://github.com/chakra-core/ChakraCore/commit/31f2588c7ba5b446bccf2769e9ecf4d444b73045'} |
GHSA | GHSA-77mr-wc79-m8j3 | A validation function with the same name as a built-in validator can be called | If a function is defined that has the same name as the default built-in email address validation scheme (`php`), it will be called in default configuration as when no validation scheme is provided, the default scheme's callable `php` was being called. If an attacker is able to inject such a function into the application (a much bigger issue), it will be called whenever an email address is validated, such as when calling `validateAddress()`.
### Impact
Low impact – exploitation requires that an attacker can already inject code into an application, but it provides a trigger pathway.
### Patches
This is patched in PHPMailer 6.5.0 by denying the use of simple strings as validator function names, which is a very minor BC break.
### Workarounds
Inject your own email validator function.
### References
Reported by [Vikrant Singh Chauhan](mailto:vi@hackberry.xyz) via [huntr.dev](https://www.huntr.dev/).
[CVE-2021-3603](https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3603)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the PHPMailer project](https://github.com/PHPMailer/PHPMailer)
* [Email us](mailto:phpmailer@synchromedia.co.uk).
| {'CVE-2021-3603'} | 2022-04-19T19:03:00Z | 2021-06-22T15:18:02Z | LOW | 0 | {'CWE-74'} | {'https://github.com/PHPMailer/PHPMailer/commit/45f3c18dc6a2de1cb1bf49b9b249a9ee36a5f7f3', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3603', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3603', 'https://github.com/PHPMailer/PHPMailer/security/advisories/GHSA-77mr-wc79-m8j3', 'https://github.com/advisories/GHSA-77mr-wc79-m8j3', 'https://www.huntr.dev/bounties/1-PHPMailer/PHPMailer/'} | null | {'https://github.com/PHPMailer/PHPMailer/commit/45f3c18dc6a2de1cb1bf49b9b249a9ee36a5f7f3'} | {'https://github.com/PHPMailer/PHPMailer/commit/45f3c18dc6a2de1cb1bf49b9b249a9ee36a5f7f3'} |
GHSA | GHSA-q4qv-fmwc-qxpx | SQL Injection in NukeViet | modules/banners/funcs/click.php in NukeViet before 4.3.04 has a SQL INSERT statement with raw header data from an HTTP request (e.g., Referer and User-Agent). | {'CVE-2019-7726'} | 2021-06-22T15:24:55Z | 2021-06-22T15:24:55Z | CRITICAL | 9.8 | {'CWE-89'} | {'https://github.com/nukeviet/nukeviet/compare/4.3.03...4.3.04', 'https://github.com/nukeviet/nukeviet/blob/4.3.04/CHANGELOG.txt', 'https://github.com/nukeviet/nukeviet/blob/nukeviet4.3/CHANGELOG.txt', 'https://nvd.nist.gov/vuln/detail/CVE-2019-7726', 'https://github.com/nukeviet/nukeviet/pull/2740/commits/05dfb9b4531f12944fe39556f58449b9a56241be', 'https://github.com/advisories/GHSA-q4qv-fmwc-qxpx'} | null | {'https://github.com/nukeviet/nukeviet/pull/2740/commits/05dfb9b4531f12944fe39556f58449b9a56241be'} | {'https://github.com/nukeviet/nukeviet/pull/2740/commits/05dfb9b4531f12944fe39556f58449b9a56241be'} |
GHSA | GHSA-78hj-86cr-6j2v | Improper Access Control in Lightning Network Daemon | Lightning Network Daemon (lnd) before 0.7 allows attackers to trigger loss of funds because of Incorrect Access Control. | {'CVE-2019-12999'} | 2021-05-18T15:30:22Z | 2021-05-18T15:30:22Z | HIGH | 7.5 | {'CWE-284'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-12999', 'https://lists.linuxfoundation.org/pipermail/lightning-dev/2019-September/002174.html', 'https://github.com/lightninglabs/chanleakcheck', 'https://github.com/advisories/GHSA-78hj-86cr-6j2v', 'https://github.com/lightningnetwork/lnd/commits/master', 'https://github.com/lightningnetwork/lnd/releases/tag/v0.7.0-beta'} | null | {'https://github.com/lightningnetwork/lnd/commits/master'} | {'https://github.com/lightningnetwork/lnd/commits/master'} |
GHSA | GHSA-jggw-2q6g-c3m6 | Out-of-bounds Read in OpenCV | An out-of-bounds read was discovered in OpenCV before 4.1.1 (OpenCV-Python before 4.1.0.25). Specifically, variable coarsest_scale is assumed to be greater than or equal to finest_scale within the calc()/ocl_calc() functions in dis_flow.cpp. However, this is not true when dealing with small images, leading to an out-of-bounds read of the heap-allocated arrays Ux and Uy. | {'CVE-2019-19624'} | 2021-10-12T22:22:58Z | 2021-10-12T22:22:58Z | MODERATE | 6.5 | {'CWE-125'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-19624', 'https://github.com/opencv/opencv-python/releases/tag/25', 'https://github.com/opencv/opencv/commit/d1615ba11a93062b1429fce9f0f638d1572d3418', 'https://github.com/opencv/opencv/issues/14554', 'https://access.redhat.com/security/cve/cve-2019-19624', 'https://github.com/advisories/GHSA-jggw-2q6g-c3m6'} | null | {'https://github.com/opencv/opencv/commit/d1615ba11a93062b1429fce9f0f638d1572d3418'} | {'https://github.com/opencv/opencv/commit/d1615ba11a93062b1429fce9f0f638d1572d3418'} |
GHSA | GHSA-wp3c-xw9g-gpcg | Lack of validation in `SparseDenseCwiseMul` | ### Impact
Due to lack of validation in `tf.raw_ops.SparseDenseCwiseMul`, an attacker can trigger denial of service via `CHECK`-fails or accesses to outside the bounds of heap allocated data:
```python
import tensorflow as tf
indices = tf.constant([], shape=[10, 0], dtype=tf.int64)
values = tf.constant([], shape=[0], dtype=tf.int64)
shape = tf.constant([0, 0], shape=[2], dtype=tf.int64)
dense = tf.constant([], shape=[0], dtype=tf.int64)
tf.raw_ops.SparseDenseCwiseMul(
sp_indices=indices, sp_values=values, sp_shape=shape, dense=dense)
```
Since the [implementation](https://github.com/tensorflow/tensorflow/blob/38178a2f7a681a7835bb0912702a134bfe3b4d84/tensorflow/core/kernels/sparse_dense_binary_op_shared.cc#L68-L80) only validates the rank of the input arguments but no [constraints between dimensions](https://www.tensorflow.org/api_docs/python/tf/raw_ops/SparseDenseCwiseMul), an attacker can abuse them to trigger internal `CHECK` assertions (and cause program termination, denial of service) or to write to memory outside of bounds of heap allocated tensor buffers.
### Patches
We have patched the issue in GitHub commit [7ae2af34087fb4b5c8915279efd03da3b81028bc](https://github.com/tensorflow/tensorflow/commit/7ae2af34087fb4b5c8915279efd03da3b81028bc).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team. | {'CVE-2021-29567'} | 2021-05-21T14:25:16Z | 2021-05-21T14:25:16Z | LOW | 2.5 | {'CWE-617'} | {'https://github.com/tensorflow/tensorflow/commit/7ae2af34087fb4b5c8915279efd03da3b81028bc', 'https://github.com/advisories/GHSA-wp3c-xw9g-gpcg', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-wp3c-xw9g-gpcg', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29567'} | null | {'https://github.com/tensorflow/tensorflow/commit/7ae2af34087fb4b5c8915279efd03da3b81028bc'} | {'https://github.com/tensorflow/tensorflow/commit/7ae2af34087fb4b5c8915279efd03da3b81028bc'} |
GHSA | GHSA-9pr6-grf4-x2fr | Omniauth allows POST parameters to be stored in session | In strategy.rb in OmniAuth before 1.3.2, the authenticity_token value is improperly protected because POST (in addition to GET) parameters are stored in the session and become available in the environment of the callback phase. | {'CVE-2017-18076'} | 2022-04-25T22:27:19Z | 2018-01-29T15:45:28Z | HIGH | 7.5 | null | {'https://bugs.debian.org/888523', 'https://github.com/omniauth/omniauth/pull/867', 'https://nvd.nist.gov/vuln/detail/CVE-2017-18076', 'https://github.com/omniauth/omniauth/pull/867/commits/71866c5264122e196847a3980c43051446a03e9b', 'https://www.debian.org/security/2018/dsa-4109', 'https://github.com/advisories/GHSA-9pr6-grf4-x2fr'} | null | {'https://github.com/omniauth/omniauth/pull/867/commits/71866c5264122e196847a3980c43051446a03e9b'} | {'https://github.com/omniauth/omniauth/pull/867/commits/71866c5264122e196847a3980c43051446a03e9b'} |
GHSA | GHSA-m4jx-6526-vvhm | Denial of service in github.com/nats-io/nats-server/server | This affects all versions of package github.com/nats-io/nats-server/server. Untrusted accounts are able to crash the server using configs that represent a service export/import cycles. Disclaimer from the maintainers - Running a NATS service which is exposed to untrusted users presents a heightened risk. Any remote execution flaw or equivalent seriousness, or denial-of-service by unauthenticated users, will lead to prompt releases by the NATS maintainers. Fixes for denial of service issues with no threat of remote execution, when limited to account holders, are likely to just be committed to the main development branch with no special attention. Those who are running such services are encouraged to build regularly from git. | {'CVE-2020-28466'} | 2022-04-12T22:56:52Z | 2022-02-15T01:57:18Z | HIGH | 7.5 | {'CWE-400'} | {'https://github.com/advisories/GHSA-m4jx-6526-vvhm', 'https://github.com/nats-io/nats-server/pull/1731', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMNATSIONATSSERVERSERVER-1042967', 'http://www.openwall.com/lists/oss-security/2021/03/16/1', 'http://www.openwall.com/lists/oss-security/2021/03/16/2', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28466', 'https://github.com/nats-io/nats-server/pull/1731/commits/2e3c22672936f4980d343fb1d328b38919e74796'} | null | {'https://github.com/nats-io/nats-server/pull/1731/commits/2e3c22672936f4980d343fb1d328b38919e74796'} | {'https://github.com/nats-io/nats-server/pull/1731/commits/2e3c22672936f4980d343fb1d328b38919e74796'} |
GHSA | GHSA-c84h-w6cr-5v8q | Markdown-supplied Shell Command Execution | ### Impact
lookatme versions prior to 2.3.0 automatically loaded the built-in "terminal" and "file_loader" extensions. Users that use lookatme to render untrusted markdown may have malicious shell commands automatically run on their system.
### Patches
Users should upgrade to lookatme versions 2.3.0 or above.
### Workarounds
The `lookatme/contrib/terminal.py` and `lookatme/contrib/file_loader.py` files may be manually deleted. Additionally, it is always recommended to be aware of what is being rendered with lookatme.
### References
* https://github.com/d0c-s4vage/lookatme/pull/110
* https://github.com/d0c-s4vage/lookatme/releases/tag/v2.3.0
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [d0c-s4vage/lookatme](https://github.com/d0c-s4vage/lookatme) | {'CVE-2020-15271'} | 2022-03-22T20:38:43Z | 2020-10-27T17:59:54Z | CRITICAL | 9.3 | {'CWE-78'} | {'https://github.com/d0c-s4vage/lookatme/commit/72fe36b784b234548d49dae60b840c37f0eb8d84', 'https://pypi.org/project/lookatme/#history', 'https://github.com/advisories/GHSA-c84h-w6cr-5v8q', 'https://github.com/d0c-s4vage/lookatme/releases/tag/v2.3.0', 'https://github.com/d0c-s4vage/lookatme/pull/110', 'https://github.com/d0c-s4vage/lookatme/security/advisories/GHSA-c84h-w6cr-5v8q', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15271'} | null | {'https://github.com/d0c-s4vage/lookatme/commit/72fe36b784b234548d49dae60b840c37f0eb8d84'} | {'https://github.com/d0c-s4vage/lookatme/commit/72fe36b784b234548d49dae60b840c37f0eb8d84'} |
GHSA | GHSA-5gwh-g79j-vh4q | Command Injection in pdf-image | Versions of `pdf-image` before 2.0.0 are vulnerable to command injection. This vulnerability is exploitable if the attacker has control over the `pdfFilePath` variable passed into `pdf-image`.
## Recommendation
Update to version 2.0.0 or later. | {'CVE-2018-3757'} | 2021-09-24T20:36:09Z | 2020-09-01T20:44:52Z | CRITICAL | 9.8 | {'CWE-78'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-3757', 'https://hackerone.com/reports/340208', 'https://github.com/advisories/GHSA-5gwh-g79j-vh4q', 'https://www.npmjs.com/advisories/670', 'https://github.com/roest01/node-pdf-image/commit/54679496a89738443917608c2bbe2f6e5dd20e83'} | null | {'https://github.com/roest01/node-pdf-image/commit/54679496a89738443917608c2bbe2f6e5dd20e83'} | {'https://github.com/roest01/node-pdf-image/commit/54679496a89738443917608c2bbe2f6e5dd20e83'} |
GHSA | GHSA-x5rq-j2xg-h7qm | Regular Expression Denial of Service (ReDoS) in lodash | lodash prior to 4.7.11 is affected by: CWE-400: Uncontrolled Resource Consumption. The impact is: Denial of service. The component is: Date handler. The attack vector is: Attacker provides very long strings, which the library attempts to match using a regular expression. The fixed version is: 4.7.11. | {'CVE-2019-1010266'} | 2022-04-19T19:03:26Z | 2019-07-19T16:13:07Z | MODERATE | 0 | {'CWE-400'} | {'https://github.com/lodash/lodash/commit/5c08f18d365b64063bfbfa686cbb97cdd6267347', 'https://github.com/lodash/lodash/wiki/Changelog', 'https://security.netapp.com/advisory/ntap-20190919-0004/', 'https://nvd.nist.gov/vuln/detail/CVE-2019-1010266', 'https://github.com/lodash/lodash/issues/3359', 'https://snyk.io/vuln/SNYK-JS-LODASH-73639', 'https://github.com/advisories/GHSA-x5rq-j2xg-h7qm'} | null | {'https://github.com/lodash/lodash/commit/5c08f18d365b64063bfbfa686cbb97cdd6267347'} | {'https://github.com/lodash/lodash/commit/5c08f18d365b64063bfbfa686cbb97cdd6267347'} |
GHSA | GHSA-r5hc-wm3g-hjw6 | Server-Side Request Forgery (SSRF) in rudloff/alltube | ### Impact
Releases prior to 3.0.2 are vulnerable to a Server-Side Request Forgery vulnerability that allows an attacker to send a request to an internal hostname.
### Patches
3.0.2 contains a fix for this vulnerability.
(The 1.x and 2.x releases are not maintained anymore.)
Part of the fix requires applying [a patch](https://github.com/Rudloff/alltube/blob/148a171b240e7ceb076b9e198bef412de14ac55d/patches/youtube-dl-redirect.diff) to youtube-dl to prevent it from following HTTP redirects. If you are using the version of youtube-dl bundled with 3.0.2, it is already patched.
However, if you are using your own unpatched version of youtube-dl **you might still be vulnerable**.
### References
* https://github.com/Rudloff/alltube/commit/3a4f09dda0a466662a4e52cde674749e0c668e8d
* https://github.com/Rudloff/alltube/commit/1b099bb9836a3ce7c427a41722a7ab5a3d1c1b2d
* https://huntr.dev/bounties/9b14cc46-ec08-4940-83cc-9f986b2a5903/
* https://nvd.nist.gov/vuln/detail/CVE-2022-0768
* https://github.com/ytdl-org/youtube-dl/issues/30691 | {'CVE-2022-0768'} | 2022-03-18T20:42:55Z | 2022-03-01T22:01:30Z | CRITICAL | 9.1 | {'CWE-918'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0768', 'https://huntr.dev/bounties/9b14cc46-ec08-4940-83cc-9f986b2a5903', 'https://github.com/Rudloff/alltube/security/advisories/GHSA-r5hc-wm3g-hjw6', 'https://github.com/Rudloff/alltube/commit/3a4f09dda0a466662a4e52cde674749e0c668e8d', 'https://github.com/rudloff/alltube/commit/148a171b240e7ceb076b9e198bef412de14ac55d', 'https://github.com/advisories/GHSA-r5hc-wm3g-hjw6'} | null | {'https://github.com/Rudloff/alltube/commit/3a4f09dda0a466662a4e52cde674749e0c668e8d', 'https://github.com/rudloff/alltube/commit/148a171b240e7ceb076b9e198bef412de14ac55d'} | {'https://github.com/rudloff/alltube/commit/148a171b240e7ceb076b9e198bef412de14ac55d', 'https://github.com/Rudloff/alltube/commit/3a4f09dda0a466662a4e52cde674749e0c668e8d'} |
GHSA | GHSA-qjg4-w4c6-f6c6 | Command injection in mversion | ### Impact
This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input.
### Patches
Patched by version 2.0.0. Previous releases are deprecated in npm.
### Workarounds
Make sure to escape git commit messages when using the commitMessage option for the update function. | {'CVE-2020-4059'} | 2021-01-08T21:00:25Z | 2020-06-18T19:23:17Z | HIGH | 7.3 | {'CWE-77'} | {'https://github.com/advisories/GHSA-qjg4-w4c6-f6c6', 'https://github.com/mikaelbr/mversion/commit/6c76c9efd27c7ff5a5c6f187e8b7a435c4722338', 'https://nvd.nist.gov/vuln/detail/CVE-2020-4059', 'https://github.com/mikaelbr/mversion/security/advisories/GHSA-qjg4-w4c6-f6c6'} | null | {'https://github.com/mikaelbr/mversion/commit/6c76c9efd27c7ff5a5c6f187e8b7a435c4722338'} | {'https://github.com/mikaelbr/mversion/commit/6c76c9efd27c7ff5a5c6f187e8b7a435c4722338'} |
GHSA | GHSA-5hx2-qx8j-qjqm | Overflow/crash in `tf.image.resize` when size is large | ### Impact
If `tf.image.resize` is called with a large input argument then the TensorFlow process will crash due to a `CHECK`-failure caused by an overflow.
```python
import tensorflow as tf
import numpy as np
tf.keras.layers.UpSampling2D(
size=1610637938,
data_format='channels_first',
interpolation='bilinear')(np.ones((5,1,1,1)))
```
The number of elements in the output tensor is too much for the `int64_t` type and the overflow is detected via a `CHECK` statement. This aborts the process.
### Patches
We have patched the issue in GitHub commit [e5272d4204ff5b46136a1ef1204fc00597e21837](https://github.com/tensorflow/tensorflow/commit/e5272d4204ff5b46136a1ef1204fc00597e21837) (merging [#51497](https://github.com/tensorflow/tensorflow/pull/51497)).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46914). | {'CVE-2021-41199'} | 2021-11-10T19:33:24Z | 2021-11-10T19:33:24Z | MODERATE | 5.5 | {'CWE-190'} | {'https://github.com/tensorflow/tensorflow/commit/e5272d4204ff5b46136a1ef1204fc00597e21837', 'https://github.com/tensorflow/tensorflow/issues/46914', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41199', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-5hx2-qx8j-qjqm', 'https://github.com/advisories/GHSA-5hx2-qx8j-qjqm'} | null | {'https://github.com/tensorflow/tensorflow/commit/e5272d4204ff5b46136a1ef1204fc00597e21837'} | {'https://github.com/tensorflow/tensorflow/commit/e5272d4204ff5b46136a1ef1204fc00597e21837'} |
GHSA | GHSA-254q-rqmw-vx45 | Exposure of Sensitive Information to an Unauthorized Actor in librenms | Exposure of Sensitive Information to an Unauthorized Actor in Packagist librenms/librenms prior to 22.2.0. | {'CVE-2022-0588'} | 2022-02-24T13:05:39Z | 2022-02-16T00:01:52Z | MODERATE | 6.5 | {'CWE-200'} | {'https://github.com/advisories/GHSA-254q-rqmw-vx45', 'https://github.com/librenms/librenms/commit/95970af78e4c899744a715766d744deef8c505f7', 'https://huntr.dev/bounties/caab3310-0d70-4c8a-8768-956f8dd3326d', 'https://notes.netbytesec.com/2022/02/multiple-vulnerabilities-in-librenms.html', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0588'} | null | {'https://github.com/librenms/librenms/commit/95970af78e4c899744a715766d744deef8c505f7'} | {'https://github.com/librenms/librenms/commit/95970af78e4c899744a715766d744deef8c505f7'} |
GHSA | GHSA-j85f-xw9x-ffwp | yetiforcecrm is vulnerable to Cross-site Scripting | yetiforcecrm is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). | {'CVE-2021-4121'} | 2022-01-04T18:52:13Z | 2021-12-17T20:00:12Z | MODERATE | 6.4 | {'CWE-79'} | {'https://github.com/advisories/GHSA-j85f-xw9x-ffwp', 'https://github.com/yetiforcecompany/yetiforcecrm/commit/6b5967198e43b6fbb3b2715b49c6cd5b12ce08c3', 'https://huntr.dev/bounties/6da878de-acdb-4b97-b9ff-9674c3f0881d', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4121'} | null | {'https://github.com/yetiforcecompany/yetiforcecrm/commit/6b5967198e43b6fbb3b2715b49c6cd5b12ce08c3'} | {'https://github.com/yetiforcecompany/yetiforcecrm/commit/6b5967198e43b6fbb3b2715b49c6cd5b12ce08c3'} |
GHSA | GHSA-m6gj-h9gm-gw44 | Incorrect Default Permissions | An issue was discovered in Django 2.2 before 2.2.16, 3.0 before 3.0.10, and 3.1 before 3.1.1 (when Python 3.7+ is used). FILE_UPLOAD_DIRECTORY_PERMISSIONS mode was not applied to intermediate-level directories created in the process of uploading files. It was also not applied to intermediate-level collected static directories when using the collectstatic management command. | {'CVE-2020-24583'} | 2021-03-18T20:30:13Z | 2021-03-18T20:30:13Z | HIGH | 7.5 | {'CWE-276'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-24583', 'https://github.com/django/django/commit/8d7271578d7b153435b40fe40236ebec43cbf1b9', 'https://www.openwall.com/lists/oss-security/2020/09/01/2', 'https://usn.ubuntu.com/4479-1/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OLGFFLMF3X6USMJD7V5F5P4K2WVUTO3T/', 'https://www.djangoproject.com/weblog/2020/sep/01/security-releases/', 'https://docs.djangoproject.com/en/dev/releases/security/', 'https://groups.google.com/forum/#!topic/django-announce/zFCMdgUnutU', 'https://groups.google.com/forum/#!topic/django-announce/Gdqn58RqIDM', 'https://github.com/advisories/GHSA-m6gj-h9gm-gw44', 'https://security.netapp.com/advisory/ntap-20200918-0004/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/F2ZHO3GZCJMP3DDTXCNVFV6ED3W64NAU/', 'https://www.oracle.com/security-alerts/cpujan2021.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZCRPQCBTV3RZHKVZ6K6QOAANPRZQD3GI/'} | null | {'https://github.com/django/django/commit/8d7271578d7b153435b40fe40236ebec43cbf1b9'} | {'https://github.com/django/django/commit/8d7271578d7b153435b40fe40236ebec43cbf1b9'} |
GHSA | GHSA-gwc9-348x-qwv2 | Use after free in Wasmtime | There is a use after free vulnerability in Wasmtime when both running Wasm that uses `externref`s and enabling [epoch interruption](https://docs.rs/wasmtime/latest/wasmtime/struct.Config.html#method.epoch_interruption) in Wasmtime. If you are not explicitly enabling epoch interruption (it is disabled by default) then you are not affected. If you are explicitly disabling the Wasm reference types proposal (it is enabled by default) then you are also not affected.
The use after free is caused by Cranelift failing to emit stack maps when there are safepoints inside cold blocks. Cold blocks occur when epoch interruption is enabled. Cold blocks are emitted at the end of compiled functions, and change the order blocks are emitted versus defined. This reordering accidentally caused Cranelift to skip emitting some stack maps because it expected to emit the stack maps in block definition order, rather than block emission order. When Wasmtime would eventually collect garbage, it would fail to find live references on the stack because of the missing stack maps, think that they were unreferenced garbage, and therefore reclaim them. Then after the collection ended, the Wasm code could use the reclaimed-too-early references, which is a use after free.
This bug was discovered while extending our fuzz targets for `externref`s and GC in Wasmtime. The updated fuzz target thoroughly exercises these code paths and feature combinations now. We have also added a regression test for this bug. Released versions 0.34.2 and 0.35.2, which fix the vulnerability. We recommend all Wasmtime users upgrade to these patched versions. If upgrading is not an option for you at this time, you can avoid the vulnerability by either disabling the Wasm reference types proposal or by disabling epoch interruption if you were previously enabling it. | {'CVE-2022-24791'} | 2022-04-12T23:16:18Z | 2022-04-01T13:36:12Z | HIGH | 8.1 | {'CWE-416'} | {'https://github.com/WebAssembly/reference-types', 'https://github.com/bytecodealliance/wasmtime/commit/666c2554ea0e1728c35aa41178cf235920db888a', 'https://docs.rs/wasmtime/latest/wasmtime/struct.Config.html#method.epoch_interruption', 'https://github.com/advisories/GHSA-gwc9-348x-qwv2', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24791', 'https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-gwc9-348x-qwv2'} | null | {'https://github.com/bytecodealliance/wasmtime/commit/666c2554ea0e1728c35aa41178cf235920db888a'} | {'https://github.com/bytecodealliance/wasmtime/commit/666c2554ea0e1728c35aa41178cf235920db888a'} |
GHSA | GHSA-29v9-2fpx-j5g9 | CSV Injection vulnerability with exported contact lists in Mautic | ### Impact
Mautic versions before 2.13.0 had a vulnerability that allowed a CSV injection with exported contact lists - https://www.owasp.org/index.php/CSV_Injection.
### Patches
Update to 2.13.0 or later.
### Workarounds
None.
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@mautic.org](mailto:security@mautic.org) | {'CVE-2018-8092'} | 2021-01-19T21:16:29Z | 2021-01-19T21:16:29Z | MODERATE | 9.8 | {'CWE-1236'} | {'https://github.com/mautic/mautic/releases/tag/2.13.0', 'https://github.com/mautic/mautic/commit/cbc49f0ac4cc7e3acc07f2a85c079b2f85225a6b', 'https://github.com/mautic/mautic/security/advisories/GHSA-29v9-2fpx-j5g9', 'https://nvd.nist.gov/vuln/detail/CVE-2018-8092', 'https://github.com/advisories/GHSA-29v9-2fpx-j5g9'} | null | {'https://github.com/mautic/mautic/commit/cbc49f0ac4cc7e3acc07f2a85c079b2f85225a6b'} | {'https://github.com/mautic/mautic/commit/cbc49f0ac4cc7e3acc07f2a85c079b2f85225a6b'} |
GHSA | GHSA-3v56-q6r6-4gcw | Insecure Inherited Permissions in neoan3-apps/template | ### Impact
Versions prior 1.1.1 have allowed for passing in closures directly into the template engine. As a result values that are callable are executed by the template engine. The issue arises if a value has the same name as a method or function in scope and can therefore be executed either by mistake or maliciously.
In theory all users of the package are affected as long as they either deal with direct user input or database values. A multi-step attack on is therefore plausible.
### Patches
Version 1.1.1 has addressed this vulnerability.
```php
$params = [
'reverse' => fn($input) => strrev($input), // <-- no longer possible with version ~1.1.1
'value' => 'My website'
]
TemplateFunctions::registerClosure('reverse', fn($input) => strrev($input)); // <-- still possible (and nicely isolated)
Template::embrace('<h1>{{reverse(value)}}</h1>', $params);
```
### Workarounds
Unfortunately only working with hardcoded values is safe in prior versions. As this likely defeats the purpose of a template engine, please upgrade.
### References
As a possible exploit is relatively easy to achieve, I will not share steps to reproduce the issue for now.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [our repo](https://github.com/sroehrl/neoan3-template)
| {'CVE-2021-41170'} | 2021-11-17T21:25:14Z | 2021-11-10T16:41:08Z | HIGH | 7.5 | {'CWE-732', 'CWE-74', 'CWE-277'} | {'https://github.com/sroehrl/neoan3-template/commit/4a2c9570f071d3c8f4ac790007599cba20e16934', 'https://github.com/advisories/GHSA-3v56-q6r6-4gcw', 'https://github.com/sroehrl/neoan3-template/issues/8', 'https://github.com/sroehrl/neoan3-template/security/advisories/GHSA-3v56-q6r6-4gcw', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41170'} | null | {'https://github.com/sroehrl/neoan3-template/commit/4a2c9570f071d3c8f4ac790007599cba20e16934'} | {'https://github.com/sroehrl/neoan3-template/commit/4a2c9570f071d3c8f4ac790007599cba20e16934'} |
GHSA | GHSA-hwj9-h5mp-3pm3 | Regular Expression Denial of Service in postcss | The npm package `postcss` from 7.0.0 and before versions 7.0.36 and 8.2.10 is vulnerable to Regular Expression Denial of Service (ReDoS) during source map parsing. | {'CVE-2021-23368'} | 2021-06-15T15:12:14Z | 2021-05-10T15:29:24Z | MODERATE | 5.3 | {'CWE-400'} | {'https://lists.apache.org/thread.html/r49afb49b38748897211b1f89c3a64dc27f9049474322b05715695aab@%3Cdev.myfaces.apache.org%3E', 'https://github.com/advisories/GHSA-hwj9-h5mp-3pm3', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1244795', 'https://lists.apache.org/thread.html/r00158f5d770d75d0655c5eef1bdbc6150531606c8f8bcb778f0627be@%3Cdev.myfaces.apache.org%3E', 'https://lists.apache.org/thread.html/r5acd89f3827ad9a9cad6d24ed93e377f7114867cd98cfba616c6e013@%3Ccommits.myfaces.apache.org%3E', 'https://lists.apache.org/thread.html/rad5af2044afb51668b1008b389ac815a28ecea9eb75ae2cab5a00ebb@%3Ccommits.myfaces.apache.org%3E', 'https://github.com/postcss/postcss/commit/b6f3e4d5a8d7504d553267f80384373af3a3dec5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23368', 'https://github.com/postcss/postcss/commit/54cbf3c4847eb0fb1501b9d2337465439e849734', 'https://lists.apache.org/thread.html/r16e295b4f02d81b79981237d602cb0b9e59709bafaa73ac98be7cef1@%3Cdev.myfaces.apache.org%3E', 'https://lists.apache.org/thread.html/r8def971a66cf3e375178fbee752e1b04a812a047cc478ad292007e33@%3Cdev.myfaces.apache.org%3E', 'https://snyk.io/vuln/SNYK-JS-POSTCSS-1090595', 'https://github.com/postcss/postcss/commit/8682b1e4e328432ba692bed52326e84439cec9e4'} | null | {'https://github.com/postcss/postcss/commit/b6f3e4d5a8d7504d553267f80384373af3a3dec5', 'https://github.com/postcss/postcss/commit/8682b1e4e328432ba692bed52326e84439cec9e4', 'https://github.com/postcss/postcss/commit/54cbf3c4847eb0fb1501b9d2337465439e849734'} | {'https://github.com/postcss/postcss/commit/8682b1e4e328432ba692bed52326e84439cec9e4', 'https://github.com/postcss/postcss/commit/b6f3e4d5a8d7504d553267f80384373af3a3dec5', 'https://github.com/postcss/postcss/commit/54cbf3c4847eb0fb1501b9d2337465439e849734'} |
GHSA | GHSA-3j58-p785-f27x | Cross-site Scripting in microweber | There is a reflected cross sitem scripting attack in microweber via url parameters. | {'CVE-2022-0378'} | 2022-02-03T20:34:29Z | 2022-01-28T22:15:24Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/advisories/GHSA-3j58-p785-f27x', 'https://github.com/microweber/microweber/commit/fc7e1a026735b93f0e0047700d08c44954fce9ce', 'https://huntr.dev/bounties/529b65c0-5be7-49d4-9419-f905b8153d31', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0378'} | null | {'https://github.com/microweber/microweber/commit/fc7e1a026735b93f0e0047700d08c44954fce9ce'} | {'https://github.com/microweber/microweber/commit/fc7e1a026735b93f0e0047700d08c44954fce9ce'} |
GHSA | GHSA-85cp-p426-42f5 | Prototype Pollution in deep-get-set | All versions of package deep-get-set prior to version 1.1.1 are vulnerable to Prototype Pollution via the main function. | {'CVE-2020-7715'} | 2021-07-29T22:06:52Z | 2021-05-06T18:12:59Z | HIGH | 9.8 | {'CWE-1321'} | {'https://github.com/advisories/GHSA-85cp-p426-42f5', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7715', 'https://github.com/acstll/deep-get-set/commit/a127e65bc77ff5707a6a103819e140d11475c5f4', 'https://snyk.io/vuln/SNYK-JS-DEEPGETSET-598666'} | null | {'https://github.com/acstll/deep-get-set/commit/a127e65bc77ff5707a6a103819e140d11475c5f4'} | {'https://github.com/acstll/deep-get-set/commit/a127e65bc77ff5707a6a103819e140d11475c5f4'} |
GHSA | GHSA-45w7-7g63-2m5w | Drop of uninitialized memory in stack_dst | Affected versions of stack_dst used a push_inner function that increased the internal length of the array and then called val.clone(). If the val.clone() call panics, the stack could drop an already dropped element or drop uninitialized memory. This issue was fixed in 2a4d538 by increasing the length of the array after elements are cloned.
| {'CVE-2021-28035'} | 2021-09-01T18:30:55Z | 2021-09-01T18:30:55Z | CRITICAL | 9.8 | {'CWE-908'} | {'https://github.com/thepowersgang/stack_dst-rs/issues/5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28035', 'https://github.com/thepowersgang/stack_dst-rs/commit/2a4d538', 'https://rustsec.org/advisories/RUSTSEC-2021-0033.html', 'https://github.com/advisories/GHSA-45w7-7g63-2m5w'} | null | {'https://github.com/thepowersgang/stack_dst-rs/commit/2a4d538'} | {'https://github.com/thepowersgang/stack_dst-rs/commit/2a4d538'} |
GHSA | GHSA-38r5-34mr-mvm7 | "catalog's registry v2 api exposed on unauthenticated path in Harbor" | ### **Impact**
Javier Provecho, member of the TCCT (Telefonica Cloud & Cybersecurity Tech better known as ElevenPaths) SRE team discovered a vulnerability regarding Harbor’s v2 API.
The catalog’s registry v2 api is exposed on an unauthenticated path. The current catalog API path is served at the following path and it requires to be authenticated as an admin.
"GET /v2/_catalog"
However, the authorization can be bypassed by using the following path
"GET /v2/_catalog/"
### **Patches**
If your product uses the affected releases of Harbor, update to either version v2.1.2 or v2.0.5 to fix this issue immediately
https://github.com/goharbor/harbor/releases/tag/v2.1.2
https://github.com/goharbor/harbor/releases/tag/v2.0.5
### **Workarounds**
If you cannot access a patched release, it can be mitigated by disabling that API. For example, redirecting it to a 404 sink hole in the ingress.
### **For more information**
If you have any questions or comments about this advisory, contact cncf-harbor-security@lists.cncf.io
View our security policy at https://github.com/goharbor/harbor/security/policy
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29662 | {'CVE-2020-29662'} | 2022-02-12T00:01:58Z | 2022-02-12T00:01:51Z | MODERATE | 5.3 | {'CWE-287', 'CWE-319'} | {'https://github.com/goharbor/harbor/releases/tag/v2.0.5', 'https://github.com/advisories/GHSA-38r5-34mr-mvm7', 'https://github.com/goharbor/harbor/commit/3481722f140e1fdf6e6d290b0cd5c86e509feed4', 'https://github.com/goharbor/harbor/commit/c7c409a8e5a8b3fd42841dda84759c9d77977853', 'https://nvd.nist.gov/vuln/detail/CVE-2020-29662', 'https://github.com/goharbor/harbor/security/advisories/GHSA-38r5-34mr-mvm7', 'https://github.com/goharbor/harbor/pull/13676', 'https://github.com/goharbor/harbor/releases/tag/v2.1.2'} | null | {'https://github.com/goharbor/harbor/commit/3481722f140e1fdf6e6d290b0cd5c86e509feed4', 'https://github.com/goharbor/harbor/commit/c7c409a8e5a8b3fd42841dda84759c9d77977853'} | {'https://github.com/goharbor/harbor/commit/3481722f140e1fdf6e6d290b0cd5c86e509feed4', 'https://github.com/goharbor/harbor/commit/c7c409a8e5a8b3fd42841dda84759c9d77977853'} |
GHSA | GHSA-vfj6-275q-4pvm | graphite.composer.views.send_email vulnerable to SSRF | ### Impact
send_email in graphite-web/webapp/graphite/composer/views.py in Graphite through 1.1.5 is vulnerable to SSRF. The vulnerable SSRF endpoint can be used by an attacker to have the Graphite web server request any resource. The response to this SSRF request is encoded into an image file and then sent to an e-mail address that can be supplied by the attacker. Thus, an attacker can exfiltrate any information. Email will be send through SMTP server configured in Graphite, by default it's 'localhost'
### Patches
Problem was patched in Graphite-web 1.1.6. Also patches was released for graphite-web [1.0.x](https://github.com/graphite-project/graphite-web/pull/2501) and [0.9.x](https://github.com/graphite-project/graphite-web/pull/2500), and we'll discuss releases of non-supported branches later.
### Workarounds
You can manually remove function `send_email` from file `webapp/graphite/composer/views.py`. This function are not in use and will not affect your Graphite installation.
### References
For more information check this graphite-web Github issue #2008
### For more information
If you have any questions or comments about this advisory:
* Add comment in [issue #2008](https://github.com/graphite-project/graphite-web/issues/2008) | {'CVE-2017-18638'} | 2022-04-19T19:02:27Z | 2019-10-25T13:55:20Z | HIGH | 7.5 | {'CWE-918'} | {'https://github.com/graphite-project/graphite-web/pull/2499', 'https://www.youtube.com/watch?v=ds4Gp4xoaeA', 'https://github.com/graphite-project/graphite-web/security/advisories/GHSA-vfj6-275q-4pvm', 'https://lists.debian.org/debian-lts-announce/2019/10/msg00030.html', 'https://github.com/advisories/GHSA-vfj6-275q-4pvm', 'https://nvd.nist.gov/vuln/detail/CVE-2017-18638', 'https://blog.orange.tw/2017/07/how-i-chained-4-vulnerabilities-on.html#second-bug-internal-graphite-ssrf', 'https://github.com/graphite-project/graphite-web/commit/71726a0e41a5263f49b973a7b856505a5b931c1f', 'https://github.com/graphite-project/graphite-web/issues/2008'} | null | {'https://github.com/graphite-project/graphite-web/commit/71726a0e41a5263f49b973a7b856505a5b931c1f'} | {'https://github.com/graphite-project/graphite-web/commit/71726a0e41a5263f49b973a7b856505a5b931c1f'} |
GHSA | GHSA-xm3x-787m-p66r | Cross-site Scripting in ShowDoc | ShowDoc prior to 2.10.4 is vulnerable to stored cross-site scripting via `.webmv` file upload. | {'CVE-2022-0964'} | 2022-03-29T21:23:07Z | 2022-03-16T00:00:46Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/advisories/GHSA-xm3x-787m-p66r', 'https://huntr.dev/bounties/dbe39998-8eb7-46ea-997f-7b27f6f16ea0', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0964', 'https://github.com/star7th/showdoc/commit/3caa32334db0c277b84e993eaca2036f5d1dbef8'} | null | {'https://github.com/star7th/showdoc/commit/3caa32334db0c277b84e993eaca2036f5d1dbef8'} | {'https://github.com/star7th/showdoc/commit/3caa32334db0c277b84e993eaca2036f5d1dbef8'} |
GHSA | GHSA-vxh4-x6gv-mphf | Cross-Site Request Forgery (CSRF) in livehelperchat/livehelperchat | Cross-Site Request Forgery (CSRF) in GitHub repository livehelperchat/livehelperchat. | {'CVE-2022-0245'} | 2022-01-25T20:48:53Z | 2022-01-21T23:25:45Z | MODERATE | 4.3 | {'CWE-352'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0245', 'https://huntr.dev/bounties/6a6aca72-32b7-45b3-a8ba-9b400b2d669c', 'https://github.com/advisories/GHSA-vxh4-x6gv-mphf', 'https://github.com/livehelperchat/livehelperchat/commit/c2fa19afeb8b1ea927fea3fd452515c95f289fb9'} | null | {'https://github.com/livehelperchat/livehelperchat/commit/c2fa19afeb8b1ea927fea3fd452515c95f289fb9'} | {'https://github.com/livehelperchat/livehelperchat/commit/c2fa19afeb8b1ea927fea3fd452515c95f289fb9'} |
GHSA | GHSA-fr76-2wp8-fp92 | Insecure template handling in Express-handlebars | Express-handlebars is a Handlebars view engine for Express. Express-handlebars mixes pure template data with engine configuration options through the Express render API. More specifically, the layout parameter may trigger file disclosure vulnerabilities in downstream applications. This potential vulnerability is somewhat restricted in that only files with existing extentions (i.e. file.extension) can be included, files that lack an extension will have .handlebars appended to them. For complete details refer to the referenced GHSL-2021-018 report. Notes in documentation have been added to help users avoid this potential information exposure vulnerability.
A fix is discussed in https://github.com/express-handlebars/express-handlebars/pull/163 | {'CVE-2021-32820'} | 2022-02-10T23:35:42Z | 2022-02-10T23:35:21Z | HIGH | 8.6 | {'CWE-200'} | {'https://github.com/express-handlebars/express-handlebars#danger-', 'https://github.com/express-handlebars/express-handlebars/commit/78c47a235c4ad7bc2674bddd8ec2721567ed8c72', 'https://github.com/express-handlebars/express-handlebars/pull/163', 'https://github.com/advisories/GHSA-fr76-2wp8-fp92', 'https://securitylab.github.com/advisories/GHSL-2021-018-express-handlebars/', 'https://www.npmjs.com/package/express-handlebars', 'https://github.com/express-handlebars/express-handlebars/blob/78c47a235c4ad7bc2674bddd8ec2721567ed8c72/README.md#danger-', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32820'} | null | {'https://github.com/express-handlebars/express-handlebars/commit/78c47a235c4ad7bc2674bddd8ec2721567ed8c72'} | {'https://github.com/express-handlebars/express-handlebars/commit/78c47a235c4ad7bc2674bddd8ec2721567ed8c72'} |
GHSA | GHSA-jphm-g89m-v42p | Path traversal in Grafana Cortex | An issue was discovered in Grafana Cortex through 1.9.0. The header value X-Scope-OrgID is used to construct file paths for rules files, and if crafted to conduct directory traversal such as ae ../../sensitive/path/in/deployment pathname, then Cortex will attempt to parse a rules file at that location and include some of the contents in the error message. (Other Cortex API requests can also be sent a malicious OrgID header, e.g., tricking the ingester into writing metrics to a different location, but the effect is nuisance rather than information disclosure.) | {'CVE-2021-36157'} | 2021-09-02T21:59:50Z | 2021-09-02T21:59:50Z | MODERATE | 0 | {'CWE-22'} | {'https://grafana.com/docs/grafana/latest/release-notes/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-36157', 'https://github.com/advisories/GHSA-jphm-g89m-v42p', 'https://github.com/cortexproject/cortex/pull/4375', 'https://github.com/cortexproject/cortex/commit/d9e1f81f40c607b9e97c2fc6db70ae54679917c4'} | null | {'https://github.com/cortexproject/cortex/commit/d9e1f81f40c607b9e97c2fc6db70ae54679917c4'} | {'https://github.com/cortexproject/cortex/commit/d9e1f81f40c607b9e97c2fc6db70ae54679917c4'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.