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-f8m6-h2c7-8h9x | Inefficient Regular Expression Complexity in nltk (word_tokenize, sent_tokenize) | ### Impact
The vulnerability is present in [`PunktSentenceTokenizer`](https://www.nltk.org/api/nltk.tokenize.punkt.html#nltk.tokenize.punkt.PunktSentenceTokenizer), [`sent_tokenize`](https://www.nltk.org/api/nltk.tokenize.html#nltk.tokenize.sent_tokenize) and [`word_tokenize`](https://www.nltk.org/api/nltk.tokenize.html#nltk.tokenize.word_tokenize). Any users of this class, or these two functions, are vulnerable to a Regular Expression Denial of Service (ReDoS) attack.
In short, a specifically crafted long input to any of these vulnerable functions will cause them to take a significant amount of execution time. The effect of this vulnerability is noticeable with the following example:
```python
from nltk.tokenize import word_tokenize
n = 8
for length in [10**i for i in range(2, n)]:
# Prepare a malicious input
text = "a" * length
start_t = time.time()
# Call `word_tokenize` and naively measure the execution time
word_tokenize(text)
print(f"A length of {length:<{n}} takes {time.time() - start_t:.4f}s")
```
Which gave the following output during testing:
```python
A length of 100 takes 0.0060s
A length of 1000 takes 0.0060s
A length of 10000 takes 0.6320s
A length of 100000 takes 56.3322s
...
```
I canceled the execution of the program after running it for several hours.
If your program relies on any of the vulnerable functions for tokenizing unpredictable user input, then we would strongly recommend upgrading to a version of NLTK without the vulnerability, or applying the workaround described below.
### Patches
The problem has been patched in NLTK 3.6.6. After the fix, running the above program gives the following result:
```python
A length of 100 takes 0.0070s
A length of 1000 takes 0.0010s
A length of 10000 takes 0.0060s
A length of 100000 takes 0.0400s
A length of 1000000 takes 0.3520s
A length of 10000000 takes 3.4641s
```
This output shows a linear relationship in execution time versus input length, which is desirable for regular expressions.
We recommend updating to NLTK 3.6.6+ if possible.
### Workarounds
The execution time of the vulnerable functions is exponential to the length of a malicious input. With other words, the execution time can be bounded by limiting the maximum length of an input to any of the vulnerable functions. Our recommendation is to implement such a limit.
### References
* The issue showcasing the vulnerability: https://github.com/nltk/nltk/issues/2866
* The pull request containing considerably more information on the vulnerability, and the fix: https://github.com/nltk/nltk/pull/2869
* The commit containing the fix: 1405aad979c6b8080dbbc8e0858f89b2e3690341
* Information on CWE-1333: Inefficient Regular Expression Complexity: https://cwe.mitre.org/data/definitions/1333.html
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [github.com/nltk/nltk](https://github.com/nltk/nltk)
* Email us at [nltk.team@gmail.com](mailto:nltk.team@gmail.com)
| {'CVE-2021-43854'} | 2022-04-19T19:03:16Z | 2022-01-06T17:38:45Z | HIGH | 7.5 | {'CWE-400'} | {'https://github.com/nltk/nltk/commit/1405aad979c6b8080dbbc8e0858f89b2e3690341', 'https://github.com/nltk/nltk/issues/2866', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43854', 'https://github.com/advisories/GHSA-f8m6-h2c7-8h9x', 'https://github.com/nltk/nltk/security/advisories/GHSA-f8m6-h2c7-8h9x', 'https://github.com/nltk/nltk/pull/2869'} | null | {'https://github.com/nltk/nltk/commit/1405aad979c6b8080dbbc8e0858f89b2e3690341'} | {'https://github.com/nltk/nltk/commit/1405aad979c6b8080dbbc8e0858f89b2e3690341'} |
GHSA | GHSA-jf7h-7m85-w2v2 | Integer overflow in TFLite memory allocation | ### Impact
The TFLite code for allocating `TFLiteIntArray`s is [vulnerable to an integer overflow issue](https://github.com/tensorflow/tensorflow/blob/4ceffae632721e52bf3501b736e4fe9d1221cdfa/tensorflow/lite/c/common.c#L24-L27):
```cc
int TfLiteIntArrayGetSizeInBytes(int size) {
static TfLiteIntArray dummy;
return sizeof(dummy) + sizeof(dummy.data[0]) * size;
}
```
An attacker can craft a model such that the `size` multiplier is so large that the return value overflows the `int` datatype and becomes negative. In turn, this results in [invalid value being given to `malloc`](https://github.com/tensorflow/tensorflow/blob/4ceffae632721e52bf3501b736e4fe9d1221cdfa/tensorflow/lite/c/common.c#L47-L52):
```cc
TfLiteIntArray* TfLiteIntArrayCreate(int size) {
TfLiteIntArray* ret = (TfLiteIntArray*)malloc(TfLiteIntArrayGetSizeInBytes(size));
ret->size = size;
return ret;
}
```
In this case, `ret->size` would dereference an invalid pointer.
### Patches
We have patched the issue in GitHub commit [7c8cc4ec69cd348e44ad6a2699057ca88faad3e5](https://github.com/tensorflow/tensorflow/commit/7c8cc4ec69cd348e44ad6a2699057ca88faad3e5).
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 members of the Aivul Team from Qihoo 360. | {'CVE-2021-29605'} | 2021-05-21T14:28:22Z | 2021-05-21T14:28:22Z | HIGH | 7.1 | {'CWE-190'} | {'https://github.com/tensorflow/tensorflow/commit/7c8cc4ec69cd348e44ad6a2699057ca88faad3e5', 'https://github.com/advisories/GHSA-jf7h-7m85-w2v2', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-jf7h-7m85-w2v2', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29605'} | null | {'https://github.com/tensorflow/tensorflow/commit/7c8cc4ec69cd348e44ad6a2699057ca88faad3e5'} | {'https://github.com/tensorflow/tensorflow/commit/7c8cc4ec69cd348e44ad6a2699057ca88faad3e5'} |
GHSA | GHSA-gf8j-v8x5-h9qp | XSS in enshrined/svg-sanitize due to mishandled script and data values in attributes | enshrined/svg-sanitize before 0.12.0 mishandles script and data values in attributes, as demonstrated by unexpected whitespace such as in the javascript	:alert substring. | {'CVE-2019-18857'} | 2022-04-19T19:03:23Z | 2020-01-08T17:15:37Z | HIGH | 7.5 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-18857', 'https://github.com/darylldoyle/svg-sanitizer/compare/0.11.0...0.12.0', 'https://github.com/darylldoyle/svg-sanitizer/commit/51ca4b713f3706d6b27769c6296bbc0c28a5bbd0', 'https://github.com/advisories/GHSA-gf8j-v8x5-h9qp'} | null | {'https://github.com/darylldoyle/svg-sanitizer/commit/51ca4b713f3706d6b27769c6296bbc0c28a5bbd0'} | {'https://github.com/darylldoyle/svg-sanitizer/commit/51ca4b713f3706d6b27769c6296bbc0c28a5bbd0'} |
GHSA | GHSA-mf79-f657-47ww | Insufficient Session Expiration in Admidio | Admidio prior to version 4.1.9 is vulnerable to insufficient session expiration. In vulnerable versions, changing the password in one session does not terminate sessions logged in with the old password, which could lead to unauthorized actors maintaining access to an account. | {'CVE-2022-0991'} | 2022-03-29T21:39:04Z | 2022-03-20T00:00:29Z | HIGH | 8.2 | {'CWE-613'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0991', 'https://github.com/Admidio/admidio/issues/1238', 'https://huntr.dev/bounties/1c406a4e-15d0-4920-8495-731c48473ba4', 'https://github.com/admidio/admidio/commit/e84e472ebe517e2ff5795c46dc10b5f49dc4d46a', 'https://github.com/Admidio/admidio/releases/tag/v4.1.9', 'https://github.com/advisories/GHSA-mf79-f657-47ww'} | null | {'https://github.com/admidio/admidio/commit/e84e472ebe517e2ff5795c46dc10b5f49dc4d46a'} | {'https://github.com/admidio/admidio/commit/e84e472ebe517e2ff5795c46dc10b5f49dc4d46a'} |
GHSA | GHSA-vrgh-5w3c-ggf8 | showdoc is vulnerable to Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) | showdoc is vulnerable to Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG). | {'CVE-2021-3990'} | 2021-12-03T20:38:50Z | 2021-12-03T20:38:50Z | MODERATE | 6.5 | {'CWE-338'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-3990', 'https://github.com/star7th/showdoc/commit/a9886f26c08225e0adca75c67dfca3f7c42b87d0', 'https://github.com/advisories/GHSA-vrgh-5w3c-ggf8', 'https://huntr.dev/bounties/0680067d-56a7-4412-b06e-a267e850ae9f'} | null | {'https://github.com/star7th/showdoc/commit/a9886f26c08225e0adca75c67dfca3f7c42b87d0'} | {'https://github.com/star7th/showdoc/commit/a9886f26c08225e0adca75c67dfca3f7c42b87d0'} |
GHSA | GHSA-vhm6-gw82-6f8j | Cross site scripting in LibreNMS | LibreNMS prior to version 22.2.2 is vulnerable to cross-site scripting. | {'CVE-2022-0772'} | 2022-03-08T18:06:06Z | 2022-02-28T00:00:34Z | MODERATE | 4.8 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0772', 'https://github.com/advisories/GHSA-vhm6-gw82-6f8j', 'https://github.com/librenms/librenms/commit/703745d0ed3948623153117d761ce48514e2f281', 'https://huntr.dev/bounties/faae29bd-c43a-468d-8af6-2b6aa4d40f09'} | null | {'https://github.com/librenms/librenms/commit/703745d0ed3948623153117d761ce48514e2f281'} | {'https://github.com/librenms/librenms/commit/703745d0ed3948623153117d761ce48514e2f281'} |
GHSA | GHSA-89gv-h8wf-cg8r | Hostname spoofing via backslashes in URL | ### Impact
If using affected versions to determine a URL's hostname, the hostname can be spoofed by using a combination of backslash (`\`) and slash (`/`) characters as part of the scheme delimiter, e.g. `scheme:/\/\/\hostname`. If the hostname is used in security decisions, the decision may be incorrect.
Depending on library usage and attacker intent, impacts may include allow/block list bypasses, SSRF attacks, open redirects, or other undesired behavior.
Example URL: `https:/\/\/\expected-example.com/path`
Escaped string: `https:/\\/\\/\\expected-example.com/path` (JavaScript strings must escape backslash)
Affected versions incorrectly return no hostname. Patched versions correctly return `expected-example.com`. Patched versions match the behavior of other parsers which implement the [WHATWG URL specification](https://url.spec.whatwg.org/), including web browsers and [Node's built-in URL class](https://nodejs.org/api/url.html).
### Patches
Version 1.19.7 is patched against all known payload variants.
### References
https://github.com/medialize/URI.js/releases/tag/v1.19.7 (fix for this particular bypass)
https://github.com/medialize/URI.js/releases/tag/v1.19.6 (fix for related bypass)
https://github.com/medialize/URI.js/releases/tag/v1.19.4 (fix for related bypass)
https://github.com/medialize/URI.js/releases/tag/v1.19.3 (fix for related bypass)
[PR #233](https://github.com/medialize/URI.js/pull/233) (initial fix for backslash handling)
### For more information
If you have any questions or comments about this advisory, open an issue in https://github.com/medialize/URI.js
### Reporter credit
[ready-research](https://github.com/ready-research) via https://huntr.dev/ | {'CVE-2021-3647'} | 2022-04-19T19:03:03Z | 2021-07-19T21:22:36Z | MODERATE | 5.3 | {'CWE-601'} | {'https://github.com/medialize/URI.js/pull/233', 'https://github.com/medialize/URI.js/releases/tag/v1.19.4', 'https://github.com/medialize/URI.js/commit/ac43ca8f80c042f0256fb551ea5203863dec4481', 'https://github.com/medialize/URI.js/releases/tag/v1.19.7', 'https://github.com/medialize/URI.js/releases/tag/v1.19.3', 'https://huntr.dev/bounties/1625558772840-medialize/URI.js', 'https://github.com/advisories/GHSA-89gv-h8wf-cg8r', 'https://github.com/medialize/URI.js/security/advisories/GHSA-89gv-h8wf-cg8r', 'https://github.com/medialize/URI.js/releases/tag/v1.19.6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3647'} | null | {'https://github.com/medialize/URI.js/commit/ac43ca8f80c042f0256fb551ea5203863dec4481'} | {'https://github.com/medialize/URI.js/commit/ac43ca8f80c042f0256fb551ea5203863dec4481'} |
GHSA | GHSA-qq3j-xp49-j73f | Plugin archive directory traversal in Helm | The Helm core maintainers have identified an information disclosure
vulnerability in Helm 3.0.0-3.2.3.
### Impact
A traversal attack is possible when installing Helm plugins from a tar
archive over HTTP. It is possible for a malicious plugin author to inject a relative
path into a plugin archive, and copy a file outside of the intended directory.
Traversal Attacks are a form of a Directory Traversal that can be exploited by
extracting files from an archive. The premise of the Directory Traversal
vulnerability is that an attacker can gain access to parts of the file system
outside of the target folder in which they should reside. The attacker can
then overwrite executable files and either invoke them remotely or wait for
the system or user to call them, thus achieving Remote Command Execution on
the victim's machine. The vulnerability can also cause damage by overwriting
configuration files or other sensitive resources, and can be exploited on both
client (user) machines and servers.
https://snyk.io/research/zip-slip-vulnerability
### Patches
This issue has been fixed in Helm 3.2.4
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the Helm repository](https://github.com/helm/helm/issues)
* For security-specific issues, email us at [cncf-helm-security@lists.cncf.io](mailto:cncf-helm-security@lists.cncf.io) | {'CVE-2020-4053'} | 2022-04-19T19:02:28Z | 2021-06-23T18:14:36Z | LOW | 3.7 | {'CWE-22'} | {'https://github.com/helm/helm/releases/tag/v3.2.4', 'https://github.com/helm/helm/pull/8317', 'https://github.com/advisories/GHSA-qq3j-xp49-j73f', 'https://nvd.nist.gov/vuln/detail/CVE-2020-4053', 'https://github.com/helm/helm/commit/b6bbe4f08bbb98eadd6c9cd726b08a5c639908b3', 'https://github.com/helm/helm/security/advisories/GHSA-qq3j-xp49-j73f', 'https://github.com/helm/helm/commit/0ad800ef43d3b826f31a5ad8dfbb4fe05d143688'} | null | {'https://github.com/helm/helm/commit/b6bbe4f08bbb98eadd6c9cd726b08a5c639908b3', 'https://github.com/helm/helm/commit/0ad800ef43d3b826f31a5ad8dfbb4fe05d143688'} | {'https://github.com/helm/helm/commit/b6bbe4f08bbb98eadd6c9cd726b08a5c639908b3', 'https://github.com/helm/helm/commit/0ad800ef43d3b826f31a5ad8dfbb4fe05d143688'} |
GHSA | GHSA-r578-pj6f-r4ff | Auto-merging Person Records Compromised | ### Impact
New user registrations are able to access anyone's account by only knowing their basic profile information (name, birthday, gender, etc). This includes all app functionality within the app, as well as any authenticated links to Rock-based webpages (such as giving and events).
### Patches
We have released a security patch on v2.20.0. The solution was to create a duplicate person and then patch the new person with their profile details.
### Workarounds
If you do not wish to upgrade your app to the new version, you can patch your server by overriding the `create` data source method on the `People` class.
```js
create = async (profile) => {
const rockUpdateFields = this.mapApollosFieldsToRock(profile);
// auto-merge functionality is compromised
// we are creating a new user and patching them with profile details
const id = await this.post('/People', {
Gender: 0, // required by Rock. Listed first so it can be overridden.
IsSystem: false, // required by rock
});
await this.patch(`/People/${id}`, {
...rockUpdateFields,
});
return id;
};
```
### For more information
If you have any questions or comments about this advisory:
* Email us at [support@apollos.app](mailto:support@apollos.app)
| {'CVE-2021-32691'} | 2021-06-25T13:13:03Z | 2021-06-21T17:07:47Z | HIGH | 8.8 | {'CWE-287', 'CWE-303'} | {'https://github.com/ApollosProject/apollos-apps/security/advisories/GHSA-r578-pj6f-r4ff', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32691', 'https://github.com/ApollosProject/apollos-apps/releases/tag/v2.20.0', 'https://github.com/advisories/GHSA-r578-pj6f-r4ff', 'https://github.com/ApollosProject/apollos-apps/commit/cb5f8f1c0b24f1b215b2bb5eb6f9a8e16d728ce2'} | null | {'https://github.com/ApollosProject/apollos-apps/commit/cb5f8f1c0b24f1b215b2bb5eb6f9a8e16d728ce2'} | {'https://github.com/ApollosProject/apollos-apps/commit/cb5f8f1c0b24f1b215b2bb5eb6f9a8e16d728ce2'} |
GHSA | GHSA-xh55-2fqp-p775 | Command injection in mail agent settings | ### Impact
Command injection in mail agent settings
### Patches
We recommend updating to the current version 6.4.3.1. You can get the update to 6.4.3.1 regularly via the Auto-Updater or directly via the download overview.
https://www.shopware.com/en/download/#shopware-6
### Workarounds
For older versions of 6.1, 6.2, and 6.3, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.
https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659 | {'CVE-2021-37708'} | 2021-08-30T16:14:09Z | 2021-08-30T16:14:09Z | HIGH | 8.8 | {'CWE-77'} | {'https://github.com/advisories/GHSA-xh55-2fqp-p775', 'https://github.com/shopware/platform/commit/82d8d1995f6ce9054323b2c3522b1b3cf04853aa', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37708', 'https://github.com/shopware/platform/security/advisories/GHSA-xh55-2fqp-p775'} | null | {'https://github.com/shopware/platform/commit/82d8d1995f6ce9054323b2c3522b1b3cf04853aa'} | {'https://github.com/shopware/platform/commit/82d8d1995f6ce9054323b2c3522b1b3cf04853aa'} |
GHSA | GHSA-w2pm-r78h-4m7v | OS Command Injection in Laravel Framework | OS Command injection vulnerability in function link in Filesystem.php in Laravel Framework before 5.8.17. | {'CVE-2020-19316'} | 2022-01-06T23:13:42Z | 2022-01-06T23:13:42Z | HIGH | 8.8 | {'CWE-78'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-19316', 'http://www.netbytesec.com/advisories/OSCommandInjectionInLaravelFramework/', 'https://github.com/advisories/GHSA-w2pm-r78h-4m7v', 'https://github.com/laravel/framework/commit/44c3feb604944599ad1c782a9942981c3991fa31'} | null | {'https://github.com/laravel/framework/commit/44c3feb604944599ad1c782a9942981c3991fa31'} | {'https://github.com/laravel/framework/commit/44c3feb604944599ad1c782a9942981c3991fa31'} |
GHSA | GHSA-9gwq-6cwj-47h3 | Integer overflow in TFLite array creation | ### Impact
An attacker can craft a TFLite model that would cause an integer overflow [in `TfLiteIntArrayCreate`](https://github.com/tensorflow/tensorflow/blob/ca6f96b62ad84207fbec580404eaa7dd7403a550/tensorflow/lite/c/common.c#L53-L60):
```cc
TfLiteIntArray* TfLiteIntArrayCreate(int size) {
int alloc_size = TfLiteIntArrayGetSizeInBytes(size);
// ...
TfLiteIntArray* ret = (TfLiteIntArray*)malloc(alloc_size);
// ...
}
```
The [`TfLiteIntArrayGetSizeInBytes`](https://github.com/tensorflow/tensorflow/blob/ca6f96b62ad84207fbec580404eaa7dd7403a550/tensorflow/lite/c/common.c#L24-L33) returns an `int` instead of a `size_t`:
```cc
int TfLiteIntArrayGetSizeInBytes(int size) {
static TfLiteIntArray dummy;
int computed_size = sizeof(dummy) + sizeof(dummy.data[0]) * size;
#if defined(_MSC_VER)
// Context for why this is needed is in http://b/189926408#comment21
computed_size -= sizeof(dummy.data[0]);
#endif
return computed_size;
}
```
An attacker can control model inputs such that `computed_size` overflows the size of `int` datatype.
### Patches
We have patched the issue in GitHub commit [a1e1511dde36b3f8aa27a6ec630838e7ea40e091](https://github.com/tensorflow/tensorflow/commit/a1e1511dde36b3f8aa27a6ec630838e7ea40e091).
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 Wang Xuan of Qihoo 360 AIVul Team. | {'CVE-2022-23558'} | 2022-02-11T15:08:44Z | 2022-02-09T23:52:24Z | HIGH | 7.6 | {'CWE-190'} | {'https://github.com/tensorflow/tensorflow/blob/ca6f96b62ad84207fbec580404eaa7dd7403a550/tensorflow/lite/c/common.c#L53-L60', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23558', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9gwq-6cwj-47h3', 'https://github.com/tensorflow/tensorflow/commit/a1e1511dde36b3f8aa27a6ec630838e7ea40e091', 'https://github.com/tensorflow/tensorflow/blob/ca6f96b62ad84207fbec580404eaa7dd7403a550/tensorflow/lite/c/common.c#L24-L33', 'https://github.com/advisories/GHSA-9gwq-6cwj-47h3'} | null | {'https://github.com/tensorflow/tensorflow/commit/a1e1511dde36b3f8aa27a6ec630838e7ea40e091'} | {'https://github.com/tensorflow/tensorflow/commit/a1e1511dde36b3f8aa27a6ec630838e7ea40e091'} |
GHSA | GHSA-pq7m-3gw7-gq5x | Execution with Unnecessary Privileges in ipython | We’d like to disclose an arbitrary code execution vulnerability in IPython that stems from IPython executing untrusted files in CWD. This vulnerability allows one user to run code as another.
Proof of concept
User1:
```
mkdir -m 777 /tmp/profile_default
mkdir -m 777 /tmp/profile_default/startup
echo 'print("stealing your private secrets")' > /tmp/profile_default/startup/foo.py
```
User2:
```
cd /tmp
ipython
```
User2 will see:
```
Python 3.9.7 (default, Oct 25 2021, 01:04:21)
Type 'copyright', 'credits' or 'license' for more information
IPython 7.29.0 -- An enhanced Interactive Python. Type '?' for help.
stealing your private secrets
```
## Patched release and documentation
See https://ipython.readthedocs.io/en/stable/whatsnew/version8.html#ipython-8-0-1-cve-2022-21699,
Version 8.0.1, 7.31.1 for current Python version are recommended.
Version 7.16.3 has also been published for Python 3.6 users,
Version 5.11 (source only, 5.x branch on github) for older Python versions. | {'CVE-2022-21699'} | 2022-02-16T22:13:05Z | 2022-01-21T18:55:30Z | HIGH | 8.2 | {'CWE-279', 'CWE-269', 'CWE-250'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-21699', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CRQRTWHYXMLDJ572VGVUZMUPEOTPM3KB/', 'https://github.com/advisories/GHSA-pq7m-3gw7-gq5x', 'https://lists.debian.org/debian-lts-announce/2022/01/msg00021.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DZ7LVZBB4D7KVSFNEQUBEHFO3JW6D2ZK/', 'https://github.com/ipython/ipython/security/advisories/GHSA-pq7m-3gw7-gq5x', 'https://ipython.readthedocs.io/en/stable/whatsnew/version8.html#ipython-8-0-1-cve-2022-21699', 'https://github.com/ipython/ipython/commit/46a51ed69cdf41b4333943d9ceeb945c4ede5668'} | null | {'https://github.com/ipython/ipython/commit/46a51ed69cdf41b4333943d9ceeb945c4ede5668'} | {'https://github.com/ipython/ipython/commit/46a51ed69cdf41b4333943d9ceeb945c4ede5668'} |
GHSA | GHSA-mqm2-cgpr-p4m6 | Unintended read access in kramdown gem | The kramdown gem before 2.3.0 for Ruby processes the template option inside Kramdown documents by default, which allows unintended read access (such as template="/etc/passwd") or unintended embedded Ruby code execution (such as a string that begins with template="string://<%= `). NOTE: kramdown is used in Jekyll, GitLab Pages, GitHub Pages, and Thredded Forum. | {'CVE-2020-14001'} | 2022-04-29T20:26:20Z | 2020-08-07T22:27:41Z | CRITICAL | 9.8 | {'CWE-862'} | {'https://kramdown.gettalong.org/news.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-14001', 'https://github.com/advisories/GHSA-mqm2-cgpr-p4m6', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ENMMGKHRQIZ3QKGOMBBBGB6B4LB5I7NQ/', 'https://security.netapp.com/advisory/ntap-20200731-0004/', 'https://usn.ubuntu.com/4562-1/', 'https://kramdown.gettalong.org', 'https://lists.apache.org/thread.html/r96df7899fbb456fe2705882f710a0c8e8614b573fbffd8d12e3f54d2@%3Cnotifications.fluo.apache.org%3E', 'https://rubygems.org/gems/kramdown', 'https://lists.debian.org/debian-lts-announce/2020/08/msg00014.html', 'https://www.debian.org/security/2020/dsa-4743', 'https://github.com/gettalong/kramdown/compare/REL_2_2_1...REL_2_3_0', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KBLTGBYU7NKOUOHDKVCU4GFZMGA6BP4L/', 'https://github.com/gettalong/kramdown/commit/1b8fd33c3120bfc6e5164b449e2c2fc9c9306fde'} | null | {'https://github.com/gettalong/kramdown/commit/1b8fd33c3120bfc6e5164b449e2c2fc9c9306fde'} | {'https://github.com/gettalong/kramdown/commit/1b8fd33c3120bfc6e5164b449e2c2fc9c9306fde'} |
GHSA | GHSA-6g3c-2mh5-7q6x | Missing validation of JWT signature in `ManyDesigns/Portofino` | ### Impact
https://github.com/ManyDesigns/Portofino before version 5.2.1 did not properly verify the signature of JSON Web Tokens.
This allows forging a valid JWT.
### Patches
The issue will be patched in the upcoming 5.2.1 release.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [https://github.com/ManyDesigns/Portofino](https://github.com/ManyDesigns/Portofino) | {'CVE-2021-29451'} | 2022-04-19T19:02:53Z | 2021-04-19T14:56:33Z | CRITICAL | 9.1 | {'CWE-347'} | {'https://github.com/advisories/GHSA-6g3c-2mh5-7q6x', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29451', 'https://github.com/ManyDesigns/Portofino/commit/8c754a0ad234555e813dcbf9e57d637f9f23d8fb', 'https://github.com/ManyDesigns/Portofino/security/advisories/GHSA-6g3c-2mh5-7q6x', 'https://mvnrepository.com/artifact/com.manydesigns/portofino'} | null | {'https://github.com/ManyDesigns/Portofino/commit/8c754a0ad234555e813dcbf9e57d637f9f23d8fb'} | {'https://github.com/ManyDesigns/Portofino/commit/8c754a0ad234555e813dcbf9e57d637f9f23d8fb'} |
GHSA | GHSA-v3f7-j968-4h5f | Division by zero in Tensorflow | ### Impact
The [estimator for the cost of some convolution operations](https://github.com/tensorflow/tensorflow/blob/ffa202a17ab7a4a10182b746d230ea66f021fe16/tensorflow/core/grappler/costs/op_level_cost_estimator.cc#L189-L198) can be made to execute a division by 0:
```python
import tensorflow as tf
@tf.function
def test():
y=tf.raw_ops.AvgPoolGrad(
orig_input_shape=[1,1,1,1],
grad=[[[[1.0],[1.0],[1.0]]],[[[2.0],[2.0],[2.0]]],[[[3.0],[3.0],[3.0]]]],
ksize=[1,1,1,1],
strides=[1,1,1,0],
padding='VALID',
data_format='NCHW')
return y
test()
```
The function fails to check that the stride argument is stricly positive:
```cc
int64_t GetOutputSize(const int64_t input, const int64_t filter,
const int64_t stride, const Padding& padding) {
// Logic for calculating output shape is from GetWindowedOutputSizeVerbose()
// function in third_party/tensorflow/core/framework/common_shape_fns.cc.
if (padding == Padding::VALID) {
return (input - filter + stride) / stride;
} else { // SAME.
return (input + stride - 1) / stride;
}
}
```
Hence, the fix is to add a check for the stride argument to ensure it is valid.
### Patches
We have patched the issue in GitHub commit [3218043d6d3a019756607643cf65574fbfef5d7a](https://github.com/tensorflow/tensorflow/commit/3218043d6d3a019756607643cf65574fbfef5d7a).
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-21725'} | 2022-02-11T17:05:09Z | 2022-02-10T00:15:07Z | MODERATE | 6.5 | {'CWE-369'} | {'https://github.com/tensorflow/tensorflow/blob/ffa202a17ab7a4a10182b746d230ea66f021fe16/tensorflow/core/grappler/costs/op_level_cost_estimator.cc#L189-L198', 'https://github.com/advisories/GHSA-v3f7-j968-4h5f', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-v3f7-j968-4h5f', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21725', 'https://github.com/tensorflow/tensorflow/commit/3218043d6d3a019756607643cf65574fbfef5d7a'} | null | {'https://github.com/tensorflow/tensorflow/commit/3218043d6d3a019756607643cf65574fbfef5d7a'} | {'https://github.com/tensorflow/tensorflow/commit/3218043d6d3a019756607643cf65574fbfef5d7a'} |
GHSA | GHSA-w534-q4xf-h5v2 | XSS in Mapfish Print relating to JSONP support | ### Impact
A user can use the JSONP support to do a Cross-site scripting.
### Patches
Use version >= 3.24
### Workarounds
No
### References
* https://github.com/mapfish/mapfish-print/pull/1397/commits/89155f2506b9cee822e15ce60ccae390a1419d5e
* https://cwe.mitre.org/data/definitions/79.html
### For more information
If you have any questions or comments about this advisory Comment the pull request: https://github.com/mapfish/mapfish-print/pull/1397 | {'CVE-2020-15231'} | 2021-01-07T23:47:27Z | 2020-07-07T16:32:49Z | LOW | 9.3 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15231', 'https://github.com/mapfish/mapfish-print/pull/1397/commits/89155f2506b9cee822e15ce60ccae390a1419d5e', 'https://github.com/mapfish/mapfish-print/security/advisories/GHSA-w534-q4xf-h5v2', 'https://github.com/advisories/GHSA-w534-q4xf-h5v2'} | null | {'https://github.com/mapfish/mapfish-print/pull/1397/commits/89155f2506b9cee822e15ce60ccae390a1419d5e'} | {'https://github.com/mapfish/mapfish-print/pull/1397/commits/89155f2506b9cee822e15ce60ccae390a1419d5e'} |
GHSA | GHSA-wgmx-52ph-qqcw | High severity vulnerability that affects qutebrowser | qutebrowser before version 1.4.1 is vulnerable to a cross-site request forgery flaw that allows websites to access 'qute://*' URLs. A malicious website could exploit this to load a 'qute://settings/set' URL, which then sets 'editor.command' to a bash script, resulting in arbitrary code execution. | {'CVE-2018-10895'} | 2021-09-21T20:42:18Z | 2018-10-10T16:05:23Z | HIGH | 8.8 | {'CWE-352'} | {'https://github.com/qutebrowser/qutebrowser/commit/43e58ac865ff862c2008c510fc5f7627e10b4660', 'https://github.com/advisories/GHSA-wgmx-52ph-qqcw', 'https://nvd.nist.gov/vuln/detail/CVE-2018-10895'} | null | {'https://github.com/qutebrowser/qutebrowser/commit/43e58ac865ff862c2008c510fc5f7627e10b4660'} | {'https://github.com/qutebrowser/qutebrowser/commit/43e58ac865ff862c2008c510fc5f7627e10b4660'} |
GHSA | GHSA-87cj-px37-rc3x | OS Command Injection in bikeshed | This affects the package bikeshed before 3.0.0. This can occur when an untrusted source file containing Inline Tag Command metadata is processed. When an arbitrary OS command is executed, the command output would be included in the HTML output. | {'CVE-2021-23422'} | 2021-08-30T16:25:35Z | 2021-08-30T16:25:35Z | HIGH | 7.8 | {'CWE-78'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-23422', 'https://snyk.io/vuln/SNYK-PYTHON-BIKESHED-1537646', 'https://github.com/tabatkins/bikeshed/commit/b2f668fca204260b1cad28d5078e93471cb6b2dd', 'https://github.com/advisories/GHSA-87cj-px37-rc3x'} | null | {'https://github.com/tabatkins/bikeshed/commit/b2f668fca204260b1cad28d5078e93471cb6b2dd'} | {'https://github.com/tabatkins/bikeshed/commit/b2f668fca204260b1cad28d5078e93471cb6b2dd'} |
GHSA | GHSA-f9wg-5f46-cjmw | NextAuth.js default redirect callback vulnerable to open redirects | `next-auth` v3 users before version 3.29.2 are impacted. (We recommend upgrading to v4 in most cases. See our [migration guide](https://next-auth.js.org/getting-started/upgrade-v4)).`next-auth` v4 users before version 4.3.2 are impacted. Upgrading to 3.29.2 or 4.3.2 will patch this vulnerability. If you are not able to upgrade for any reason, you can add a configuration to your `callbacks` option:
```js
// async redirect(url, baseUrl) { // v3
async redirect({ url, baseUrl }) { // v4
// Allows relative callback URLs
if (url.startsWith("/")) return new URL(url, baseUrl).toString()
// Allows callback URLs on the same origin
else if (new URL(url).origin === baseUrl) return url
return baseUrl
}
```
If you already have a `redirect` callback, make sure that you match the incoming `url` origin against the `baseUrl`. | {'CVE-2022-24858'} | 2022-05-03T02:26:17Z | 2022-04-22T20:49:09Z | MODERATE | 6.1 | {'CWE-290', 'CWE-601'} | {'https://next-auth.js.org/getting-started/upgrade-v4', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24858', 'https://github.com/advisories/GHSA-f9wg-5f46-cjmw', 'https://github.com/nextauthjs/next-auth/commit/6e15bdcb2d93c1ad5ee3889f702607637e79db50', 'https://github.com/nextauthjs/next-auth/security/advisories/GHSA-f9wg-5f46-cjmw', 'https://next-auth.js.org/configuration/callbacks#redirect-callback', 'https://github.com/nextauthjs/next-auth/releases/tag/next-auth%40v4.3.2'} | null | {'https://github.com/nextauthjs/next-auth/commit/6e15bdcb2d93c1ad5ee3889f702607637e79db50'} | {'https://github.com/nextauthjs/next-auth/commit/6e15bdcb2d93c1ad5ee3889f702607637e79db50'} |
GHSA | GHSA-8m5h-hrqm-pxm2 | Path traversal in the OWASP Enterprise Security API | ### Impact
The default implementation of `Validator.getValidDirectoryPath(String, String, File, boolean)` may incorrectly treat the tested input string as a child of the specified parent directory. This potentially could allow control-flow bypass checks to be defeated if an attack can specify the entire string representing the 'input' path.
### Patches
This vulnerability is patched in release 2.3.0.0 of ESAPI. See https://github.com/ESAPI/esapi-java-legacy/releases/tag/esapi-2.3.0.0 for details.
### Workarounds
Yes; in theory, one _could_ write the own implementation of the Validator interface. This would most easily be done by sub-classing a version of the affected `DefaultValidator` class and then overriding the affected `getValidDirectoryPath()` to correct the issue. However, this is not recommended.
### For more information
If you have any questions or comments about this advisory:
* Email one of the project co-leaders. See email addresses listed on the [OWASP ESAPI wiki](https://owasp.org/www-project-enterprise-security-api/) page, under "Leaders".
* Send email to one of the two ESAPI related Google Groups listed under [Where to Find More Information on ESAPI](https://github.com/ESAPI/esapi-java-legacy#where-to-find-more-information-on-esapi) on our [README.md](https://github.com/ESAPI/esapi-java-legacy#readme) page.
| {'CVE-2022-23457'} | 2022-04-27T21:09:46Z | 2022-04-27T21:09:43Z | HIGH | 7.5 | {'CWE-22'} | {'https://github.com/ESAPI/esapi-java-legacy/blob/develop/documentation/GHSL-2022-008_The_OWASP_Enterprise_Security_API.md', 'https://github.com/advisories/GHSA-8m5h-hrqm-pxm2', 'https://github.com/ESAPI/esapi-java-legacy/blob/develop/documentation/esapi4java-core-2.3.0.0-release-notes.txt', 'https://github.com/ESAPI/esapi-java-legacy/commit/a0d67b75593878b1b6e39e2acc1773b3effedb2a', 'https://securitylab.github.com/advisories/GHSL-2022-008_The_OWASP_Enterprise_Security_API/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23457', 'https://github.com/ESAPI/esapi-java-legacy/security/advisories/GHSA-8m5h-hrqm-pxm2'} | null | {'https://github.com/ESAPI/esapi-java-legacy/commit/a0d67b75593878b1b6e39e2acc1773b3effedb2a'} | {'https://github.com/ESAPI/esapi-java-legacy/commit/a0d67b75593878b1b6e39e2acc1773b3effedb2a'} |
GHSA | GHSA-8x44-pwr2-rgc6 | Cross-site Scripting in pimcore | Pimcore settings module is vulnerable to stored cross site scripting | {'CVE-2022-0348'} | 2022-02-03T19:56:46Z | 2022-01-28T23:05:03Z | MODERATE | 5.4 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0348', 'https://github.com/advisories/GHSA-8x44-pwr2-rgc6', 'https://github.com/pimcore/pimcore/commit/832c34aeb9f21f213295a0c28377132df996352a', 'https://huntr.dev/bounties/250e79be-7e5d-4ba3-9c34-655e39ade2f4'} | null | {'https://github.com/pimcore/pimcore/commit/832c34aeb9f21f213295a0c28377132df996352a'} | {'https://github.com/pimcore/pimcore/commit/832c34aeb9f21f213295a0c28377132df996352a'} |
GHSA | GHSA-f54p-f6jp-4rhr | Heap OOB in `FusedBatchNorm` kernels | ### Impact
The [implementation](https://github.com/tensorflow/tensorflow/blob/e71b86d47f8bc1816bf54d7bddc4170e47670b97/tensorflow/core/kernels/fused_batch_norm_op.cc#L1292) of `FusedBatchNorm` kernels is vulnerable to a heap OOB:
```python
import tensorflow as tf
tf.raw_ops.FusedBatchNormGrad(
y_backprop=tf.constant([i for i in range(9)],shape=(1,1,3,3),dtype=tf.float32)
x=tf.constant([i for i in range(2)],shape=(1,1,1,2),dtype=tf.float32)
scale=[1,1],
reserve_space_1=[1,1],
reserve_space_2=[1,1,1],
epsilon=1.0,
data_format='NCHW',
is_training=True)
```
### Patches
We have patched the issue in GitHub commit [aab9998916c2ffbd8f0592059fad352622f89cda](https://github.com/tensorflow/tensorflow/commit/aab9998916c2ffbd8f0592059fad352622f89cda).
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 by members of the Aivul Team from Qihoo 360. | {'CVE-2021-41223'} | 2021-11-10T18:46:52Z | 2021-11-10T18:46:52Z | HIGH | 7.1 | {'CWE-125'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-41223', 'https://github.com/advisories/GHSA-f54p-f6jp-4rhr', 'https://github.com/tensorflow/tensorflow/commit/aab9998916c2ffbd8f0592059fad352622f89cda', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-f54p-f6jp-4rhr'} | null | {'https://github.com/tensorflow/tensorflow/commit/aab9998916c2ffbd8f0592059fad352622f89cda'} | {'https://github.com/tensorflow/tensorflow/commit/aab9998916c2ffbd8f0592059fad352622f89cda'} |
GHSA | GHSA-23hm-7w47-xw72 | Out of bounds read in Tensorflow | ### Impact
The [implementation of `Dequantize`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/dequantize_op.cc#L92-L153) does not fully validate the value of `axis` and can result in heap OOB accesses:
```python
import tensorflow as tf
@tf.function
def test():
y = tf.raw_ops.Dequantize(
input=tf.constant([1,1],dtype=tf.qint32),
min_range=[1.0],
max_range=[10.0],
mode='MIN_COMBINED',
narrow_range=False,
axis=2**31-1,
dtype=tf.bfloat16)
return y
test()
```
The `axis` argument can be `-1` (the default value for the optional argument) or any other positive value at most the number of dimensions of the input. Unfortunately, the upper bound is not checked and this results in reading past the end of the array containing the dimensions of the input tensor:
```cc
if (axis_ > -1) {
num_slices = input.dim_size(axis_);
}
// ...
int64_t pre_dim = 1, post_dim = 1;
for (int i = 0; i < axis_; ++i) {
pre_dim *= float_output.dim_size(i);
}
for (int i = axis_ + 1; i < float_output.dims(); ++i) {
post_dim *= float_output.dim_size(i);
}
```
### Patches
We have patched the issue in GitHub commit [23968a8bf65b009120c43b5ebcceaf52dbc9e943](https://github.com/tensorflow/tensorflow/commit/23968a8bf65b009120c43b5ebcceaf52dbc9e943).
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-21726'} | 2022-02-10T00:15:47Z | 2022-02-09T18:28:54Z | HIGH | 8.1 | {'CWE-125'} | {'https://github.com/advisories/GHSA-23hm-7w47-xw72', 'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/dequantize_op.cc#L92-L153', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21726', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-23hm-7w47-xw72', 'https://github.com/tensorflow/tensorflow/commit/23968a8bf65b009120c43b5ebcceaf52dbc9e943'} | null | {'https://github.com/tensorflow/tensorflow/commit/23968a8bf65b009120c43b5ebcceaf52dbc9e943'} | {'https://github.com/tensorflow/tensorflow/commit/23968a8bf65b009120c43b5ebcceaf52dbc9e943'} |
GHSA | GHSA-fpm5-vv97-jfwg | Uncontrolled Resource Consumption in firebase | This affects the package @firebase/util before 0.3.4. This vulnerability relates to the deepExtend function within the DeepCopy.ts file. Depending on if user input is provided, an attacker can overwrite and pollute the object prototype of a program. | {'CVE-2020-7765'} | 2021-05-18T01:57:24Z | 2021-05-18T01:57:24Z | MODERATE | 5.3 | {'CWE-400'} | {'https://snyk.io/vuln/SNYK-JS-FIREBASEUTIL-1038324', 'https://github.com/advisories/GHSA-fpm5-vv97-jfwg', 'https://github.com/firebase/firebase-js-sdk/pull/4001', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7765', 'https://github.com/firebase/firebase-js-sdk/commit/9cf727fcc3d049551b16ae0698ac33dc2fe45ada'} | null | {'https://github.com/firebase/firebase-js-sdk/commit/9cf727fcc3d049551b16ae0698ac33dc2fe45ada'} | {'https://github.com/firebase/firebase-js-sdk/commit/9cf727fcc3d049551b16ae0698ac33dc2fe45ada'} |
GHSA | GHSA-3xh2-74w9-5vxm | Integer overflow in github.com/gorilla/websocket | An integer overflow vulnerability exists with the length of websocket frames received via a websocket connection. An attacker would use this flaw to cause a denial of service attack on an HTTP Server allowing websocket connections. | {'CVE-2020-27813'} | 2021-05-18T21:08:02Z | 2021-05-18T21:08:02Z | HIGH | 7.5 | {'CWE-400', 'CWE-190'} | {'https://github.com/gorilla/websocket/pull/537', 'https://github.com/gorilla/websocket/security/advisories/GHSA-jf24-p9p9-4rjh', 'https://github.com/gorilla/websocket/commit/5b740c29263eb386f33f265561c8262522f19d37', 'https://lists.debian.org/debian-lts-announce/2021/01/msg00008.html', 'https://github.com/advisories/GHSA-3xh2-74w9-5vxm', 'https://bugzilla.redhat.com/show_bug.cgi?id=1902111', 'https://nvd.nist.gov/vuln/detail/CVE-2020-27813'} | null | {'https://github.com/gorilla/websocket/commit/5b740c29263eb386f33f265561c8262522f19d37'} | {'https://github.com/gorilla/websocket/commit/5b740c29263eb386f33f265561c8262522f19d37'} |
GHSA | GHSA-73rg-x683-m3qw | Buffer overflow in canvas | A buffer overflow is present in canvas versions before 1.6.11, which could lead to a Denial of Service or execution of arbitrary code when it processes a user-provided image. | {'CVE-2020-8215'} | 2021-05-07T16:05:16Z | 2021-05-07T16:05:16Z | HIGH | 8.8 | {'CWE-120'} | {'https://hackerone.com/reports/315037', 'https://www.npmjs.com/package/canvas', 'https://github.com/Automattic/node-canvas/commit/c3e4ccb1c404da01e83fe5eb3626bf55f7f55957', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8215', 'https://github.com/advisories/GHSA-73rg-x683-m3qw'} | null | {'https://github.com/Automattic/node-canvas/commit/c3e4ccb1c404da01e83fe5eb3626bf55f7f55957'} | {'https://github.com/Automattic/node-canvas/commit/c3e4ccb1c404da01e83fe5eb3626bf55f7f55957'} |
GHSA | GHSA-p23j-g745-8449 | 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-1307, CVE-2019-1308, CVE-2019-1366. | {'CVE-2019-1335'} | 2021-03-29T20:55:40Z | 2021-03-29T20:55:40Z | HIGH | 7.5 | {'CWE-787'} | {'https://github.com/chakra-core/ChakraCore/commit/a4e56547fb8b7450656bfd26dfc52b8477c8ef27', 'https://github.com/chakra-core/ChakraCore/commit/cc871514deeaeaedb5b757c2ca8cd4ab9abccb5d', 'https://github.com/advisories/GHSA-p23j-g745-8449', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1335', 'https://nvd.nist.gov/vuln/detail/CVE-2019-1335'} | null | {'https://github.com/chakra-core/ChakraCore/commit/cc871514deeaeaedb5b757c2ca8cd4ab9abccb5d', 'https://github.com/chakra-core/ChakraCore/commit/a4e56547fb8b7450656bfd26dfc52b8477c8ef27'} | {'https://github.com/chakra-core/ChakraCore/commit/a4e56547fb8b7450656bfd26dfc52b8477c8ef27', 'https://github.com/chakra-core/ChakraCore/commit/cc871514deeaeaedb5b757c2ca8cd4ab9abccb5d'} |
GHSA | GHSA-q85f-69q7-55h2 | Uninitialized variable access in Tensorflow | ### Impact
The [implementation of `AssignOp`](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/kernels/assign_op.h#L30-L143) can result in copying unitialized data to a new tensor. This later results in undefined behavior.
The implementation has a check that the left hand side of the assignment is initialized (to minimize number of allocations), but does not check that the right hand side is also initialized.
### Patches
We have patched the issue in GitHub commit [ef1d027be116f25e25bb94a60da491c2cf55bd0b](https://github.com/tensorflow/tensorflow/commit/ef1d027be116f25e25bb94a60da491c2cf55bd0b).
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-23573'} | 2022-02-11T20:47:00Z | 2022-02-09T23:26:50Z | HIGH | 7.6 | {'CWE-908'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q85f-69q7-55h2', 'https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/kernels/assign_op.h#L30-L143', 'https://github.com/advisories/GHSA-q85f-69q7-55h2', 'https://github.com/tensorflow/tensorflow/commit/ef1d027be116f25e25bb94a60da491c2cf55bd0b', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23573'} | null | {'https://github.com/tensorflow/tensorflow/commit/ef1d027be116f25e25bb94a60da491c2cf55bd0b'} | {'https://github.com/tensorflow/tensorflow/commit/ef1d027be116f25e25bb94a60da491c2cf55bd0b'} |
GHSA | GHSA-7h8v-2v8x-h264 | SQL Injection in moodle | In moodle, some database module web services allowed students to add entries within groups they did not belong to. Versions affected: 3.9 to 3.9.2, 3.8 to 3.8.5, 3.7 to 3.7.8, 3.5 to 3.5.14 and earlier unsupported versions. This is fixed in moodle 3.8.6, 3.7.9, 3.5.15, and 3.10. | {'CVE-2020-25700'} | 2021-03-29T20:42:19Z | 2021-03-29T20:42:19Z | MODERATE | 6.5 | {'CWE-89'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=1895427', 'https://github.com/moodle/moodle/commit/8169aeff59d8ed910ca3545413561005282bbd32', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4NNFCHPPHRJNJROIX6SYMHOC6HMKP3GU/', 'https://moodle.org/mod/forum/discuss.php?d=413938', 'https://nvd.nist.gov/vuln/detail/CVE-2020-25700', 'https://github.com/advisories/GHSA-7h8v-2v8x-h264', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/B55KXBVAT45MDASJ3EK6VIGQOYGJ4NH6/'} | null | {'https://github.com/moodle/moodle/commit/8169aeff59d8ed910ca3545413561005282bbd32'} | {'https://github.com/moodle/moodle/commit/8169aeff59d8ed910ca3545413561005282bbd32'} |
GHSA | GHSA-6xxj-gcjq-wgf4 | SQL injection in prestashop/prestashop | ### Impact
Blind SQLi using Search filters with `orderBy` and `sortOrder` parameters
### Patches
The problem is fixed in 1.7.8.2 | {'CVE-2021-43789'} | 2022-04-19T19:03:16Z | 2021-12-07T21:23:17Z | HIGH | 7.5 | {'CWE-89'} | {'https://github.com/advisories/GHSA-6xxj-gcjq-wgf4', 'https://github.com/PrestaShop/PrestaShop/issues/26623', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43789', 'https://github.com/PrestaShop/PrestaShop/releases/tag/1.7.8.2', 'https://github.com/PrestaShop/PrestaShop/security/advisories/GHSA-6xxj-gcjq-wgf4', 'https://github.com/PrestaShop/PrestaShop/commit/6482b9ddc9dcebf7588dbfd616d2d635218408d6', 'https://cwe.mitre.org/data/definitions/89.html'} | null | {'https://github.com/PrestaShop/PrestaShop/commit/6482b9ddc9dcebf7588dbfd616d2d635218408d6'} | {'https://github.com/PrestaShop/PrestaShop/commit/6482b9ddc9dcebf7588dbfd616d2d635218408d6'} |
GHSA | GHSA-w8cj-mvf9-mpc9 | OS Command injection in Bolt | Bolt before 3.7.2 does not restrict filter options in a Request in the Twig context, and is therefore inconsistent with the "How to Harden Your PHP for Better Security" guidance. | {'CVE-2020-28925'} | 2021-05-06T18:53:29Z | 2021-05-06T18:53:29Z | MODERATE | 5.3 | {'CWE-78'} | {'https://github.com/bolt/bolt/compare/3.7.1...3.7.2', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28925', 'https://github.com/bolt/bolt/commit/c0cd530e78c2a8c6d71ceb75b10c251b39fb923a', 'https://github.com/advisories/GHSA-w8cj-mvf9-mpc9'} | null | {'https://github.com/bolt/bolt/commit/c0cd530e78c2a8c6d71ceb75b10c251b39fb923a'} | {'https://github.com/bolt/bolt/commit/c0cd530e78c2a8c6d71ceb75b10c251b39fb923a'} |
GHSA | GHSA-3q6g-vf58-7m4g | Regular Expression Denial of Service in flask-restx | Flask RESTX contains a regular expression that is vulnerable to [ReDoS](https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS) (Regular Expression Denial of Service) in `email_regex`.
| {'CVE-2021-32838'} | 2022-04-19T19:03:07Z | 2021-09-08T15:41:15Z | HIGH | 7.5 | {'CWE-400'} | {'https://github.com/advisories/GHSA-3q6g-vf58-7m4g', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32838', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5UCTFVDU3677B5OBGK4EF5NMUPJLL6SQ/', 'https://github.com/python-restx/flask-restx/commit/bab31e085f355dd73858fd3715f7ed71849656da', 'https://github.com/python-restx/flask-restx/security/advisories/GHSA-3q6g-vf58-7m4g', 'https://github.com/python-restx/flask-restx/blob/fd99fe11a88531f5f3441a278f7020589f9d2cc0/flask_restx/inputs.py#L51', 'https://pypi.org/project/flask-restx/', 'https://github.com/python-restx/flask-restx/issues/372', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QUD6SWZLX52AAZUHDETJ2CDMQGEPGFL3/'} | null | {'https://github.com/python-restx/flask-restx/commit/bab31e085f355dd73858fd3715f7ed71849656da'} | {'https://github.com/python-restx/flask-restx/commit/bab31e085f355dd73858fd3715f7ed71849656da'} |
GHSA | GHSA-32wx-4gxx-h48f | Users can edit the tags of any discussion | This advisory concerns a vulnerability which was patched and publicly released on October 5, 2020.
### Impact
This vulnerability allowed any registered user to edit the tags of any discussion for which they have READ access using the REST API.
Users were able to remove any existing tag, and add any tag in which they are allowed to create discussions. The chosen tags still had to match the configured Tags minimums and maximums.
By moving the discussion to new tags, users were able to go around permissions applied to restricted tags. Depending on the setup, this can include publicly exposing content that was only visible to certain groups, or gain the ability to interact with content where such interaction was limited.
The full impact varies depending on the configuration of permissions and restricted tags, and which community extensions are being used. All tag-scoped permissions offered by extensions are impacted by this ability to go around them.
Forums that don't use restricted tags and don't use any extension that relies on tags for access control should not see any security impact. An update is still required to stop users from being able to change any discussion's tags.
Forums that don't use the Tags extension are unaffected.
### Patches
The fix will be available in version v0.1.0-beta.14 with Flarum beta 14. The fix has already been back-ported to Flarum beta 13 as version v0.1.0-beta.13.2 of the Tags extension.
### Workarounds
Version v0.1.0-beta.13.2 of the Tags extension allows existing Flarum beta 13 forums to fix the issue without the need to update to beta 14.
Forums that have not yet updated to Flarum beta 13 are encouraged to update as soon as possible.
### References
- [Release announcement](https://discuss.flarum.org/d/25059-security-update-to-flarum-tags-010-beta132)
- [GitHub issue](https://github.com/flarum/core/issues/2355)
### For more information
If you have any questions or comments about this advisory, please start a new discussion on our [support forum](https://discuss.flarum.org/t/support).
If you discover a security vulnerability within Flarum, please send an e-mail to [security@flarum.org](mailto:security@flarum.org). All security vulnerabilities will be promptly addressed. More details can be found in our [security policy](https://github.com/flarum/core/security/policy). | null | 2022-04-19T19:02:36Z | 2021-01-29T18:13:32Z | MODERATE | 0 | {'CWE-639'} | {'https://github.com/flarum/core/issues/2355', 'https://discuss.flarum.org/d/25059-security-update-to-flarum-tags-010-beta132', 'https://github.com/flarum/tags/security/advisories/GHSA-32wx-4gxx-h48f', 'https://github.com/advisories/GHSA-32wx-4gxx-h48f', 'https://packagist.org/packages/flarum/tags', 'https://github.com/flarum/tags/commit/c8fcd000857493f1e4cc00b6f2771ce388b93e9d'} | null | {'https://github.com/flarum/tags/commit/c8fcd000857493f1e4cc00b6f2771ce388b93e9d'} | {'https://github.com/flarum/tags/commit/c8fcd000857493f1e4cc00b6f2771ce388b93e9d'} |
GHSA | GHSA-f545-vpwp-r9j7 | showdoc is vulnerable to URL Redirection to Untrusted Site | showdoc is vulnerable to URL Redirection to Untrusted Site. | {'CVE-2021-3989'} | 2021-12-03T20:41:35Z | 2021-12-03T20:41:35Z | MODERATE | 6.1 | {'CWE-601'} | {'https://huntr.dev/bounties/ffc61eff-efea-42c5-92c2-e043fdf904d5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3989', 'https://github.com/advisories/GHSA-f545-vpwp-r9j7', 'https://github.com/star7th/showdoc/commit/335afc7ed6d6627c3d0434aa9acc168c77117614'} | null | {'https://github.com/star7th/showdoc/commit/335afc7ed6d6627c3d0434aa9acc168c77117614'} | {'https://github.com/star7th/showdoc/commit/335afc7ed6d6627c3d0434aa9acc168c77117614'} |
GHSA | GHSA-gcj7-j438-hjj2 | Smokescreen SSRF via deny list bypass | The primary use case for Smokescreen is to prevent server-side request forgery (SSRF) attacks in which external attackers leverage the behavior of applications to connect to or scan internal infrastructure.
Smokescreen also offers an option to deny access to additional (e.g., external) URLs by way of a deny list. There was an issue in Smokescreen that made it possible to bypass the deny list feature by appending a dot to the end of user-supplied URLs, or by providing input in a different letter case.
### Recommendation
Upgrade Smokescreen to version 0.0.3 or later.
### Acknowledgements
Thanks to [Grzegorz Niedziela](https://twitter.com/gregxsunday) for reporting the issue.
### For more information
Email us at security@stripe.com | {'CVE-2022-24825'} | 2022-04-28T19:13:16Z | 2022-04-07T22:10:22Z | MODERATE | 5.8 | {'CWE-918'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-24825', 'https://github.com/stripe/smokescreen/security/advisories/GHSA-gcj7-j438-hjj2', 'https://github.com/stripe/smokescreen/commit/fafb6ae48c6c40aa011d87b61306abc48db8797b', 'https://github.com/advisories/GHSA-gcj7-j438-hjj2'} | null | {'https://github.com/stripe/smokescreen/commit/fafb6ae48c6c40aa011d87b61306abc48db8797b'} | {'https://github.com/stripe/smokescreen/commit/fafb6ae48c6c40aa011d87b61306abc48db8797b'} |
GHSA | GHSA-8c89-2vwr-chcq | Heap buffer overflow in `QuantizedResizeBilinear` | ### Impact
An attacker can cause a heap buffer overflow in `QuantizedResizeBilinear` by passing in invalid thresholds for the quantization:
```python
import tensorflow as tf
images = tf.constant([], shape=[0], dtype=tf.qint32)
size = tf.constant([], shape=[0], dtype=tf.int32)
min = tf.constant([], dtype=tf.float32)
max = tf.constant([], dtype=tf.float32)
tf.raw_ops.QuantizedResizeBilinear(images=images, size=size, min=min, max=max, align_corners=False, half_pixel_centers=False)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/50711818d2e61ccce012591eeb4fdf93a8496726/tensorflow/core/kernels/quantized_resize_bilinear_op.cc#L705-L706) assumes that the 2 arguments are always valid scalars and tries to access the numeric value directly:
```cc
const float in_min = context->input(2).flat<float>()(0);
const float in_max = context->input(3).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 [f6c40f0c6cbf00d46c7717a26419f2062f2f8694](https://github.com/tensorflow/tensorflow/commit/f6c40f0c6cbf00d46c7717a26419f2062f2f8694).
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-29537'} | 2021-05-21T14:22:35Z | 2021-05-21T14:22:35Z | LOW | 2.5 | {'CWE-131', 'CWE-787'} | {'https://github.com/advisories/GHSA-8c89-2vwr-chcq', 'https://github.com/tensorflow/tensorflow/commit/f6c40f0c6cbf00d46c7717a26419f2062f2f8694', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-8c89-2vwr-chcq', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29537'} | null | {'https://github.com/tensorflow/tensorflow/commit/f6c40f0c6cbf00d46c7717a26419f2062f2f8694'} | {'https://github.com/tensorflow/tensorflow/commit/f6c40f0c6cbf00d46c7717a26419f2062f2f8694'} |
GHSA | GHSA-7638-r9r3-rmjj | chroot isolation: environment value leakage to intermediate processes | ### Impact
When running processes using "chroot" isolation, the process being run can examine the environment variables of its immediate parent and grandparent processes (CVE-2021-3602). This isolation type is often used when running `buildah` in unprivileged containers, and it is often used to do so in CI/CD environments. If sensitive information is exposed to the original `buildah` process through its environment, that information will unintentionally be shared with child processes which it starts as part of handling RUN instructions or during `buildah run`. The commands that `buildah` is instructed to run can read that information if they choose to.
### Patches
Users should upgrade packages, or images which contain packages, to include version 1.21.3 or later.
### Workarounds
As a workaround, invoking `buildah` in a container under `env -i` to have it started with a reinitialized environment should prevent the leakage.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [buildah](https://github.com/containers/buildah/issues)
* Email us at [the buildah general mailing list](mailto:buildah@lists.buildah.io), or [the podman security mailing list](mailto:security@lists.podman.io) if it's sensitive. | {'CVE-2021-3602'} | 2022-03-18T21:03:35Z | 2021-07-19T15:19:09Z | MODERATE | 5.5 | {'CWE-200'} | {'https://github.com/advisories/GHSA-7638-r9r3-rmjj', 'https://bugzilla.redhat.com/show_bug.cgi?id=1969264', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3602', 'https://ubuntu.com/security/CVE-2021-3602', 'https://github.com/containers/buildah/security/advisories/GHSA-7638-r9r3-rmjj', 'https://github.com/containers/buildah/commit/a468ce0ffd347035d53ee0e26c205ef604097fb0'} | null | {'https://github.com/containers/buildah/commit/a468ce0ffd347035d53ee0e26c205ef604097fb0'} | {'https://github.com/containers/buildah/commit/a468ce0ffd347035d53ee0e26c205ef604097fb0'} |
GHSA | GHSA-4pwq-fj89-6rjc | Cross-site Scripting in Apache Airflow | In Apache Airflow < 1.10.12, the "origin" parameter passed to some of the endpoints like '/trigger' was vulnerable to XSS exploit. | {'CVE-2020-13944'} | 2021-06-18T18:29:54Z | 2021-06-18T18:29:54Z | MODERATE | 6.1 | {'CWE-79'} | {'https://lists.apache.org/thread.html/r97e1b60ca508a86be58c43f405c0c8ff00ba467ba0bee68704ae7e3e%40%3Cdev.airflow.apache.org%3E', 'https://lists.apache.org/thread.html/r2892ef594dbbf54d0939b808626f52f7c2d1584f8aa1d81570847d2a@%3Cannounce.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-13944', 'http://www.openwall.com/lists/oss-security/2021/05/01/2', 'https://lists.apache.org/thread.html/ra8ce70088ba291f358e077cafdb14d174b7a1ce9a9d86d1b332d6367@%3Cusers.airflow.apache.org%3E', 'https://lists.apache.org/thread.html/r4656959c8ed06c1f6202d89aa4e67b35ad7bdba5a666caff3fea888e@%3Cusers.airflow.apache.org%3E', 'http://www.openwall.com/lists/oss-security/2020/12/11/2', 'https://lists.apache.org/thread.html/rc005f4de9d9b0ba943ceb8ff5a21a5c6ff8a9df52632476698d99432@%3Cannounce.apache.org%3E', 'https://lists.apache.org/thread.html/r2892ef594dbbf54d0939b808626f52f7c2d1584f8aa1d81570847d2a@%3Cdev.airflow.apache.org%3E', 'https://lists.apache.org/thread.html/r2892ef594dbbf54d0939b808626f52f7c2d1584f8aa1d81570847d2a@%3Cusers.airflow.apache.org%3E', 'https://github.com/apache/airflow/commit/5c2bb7b0b0e717b11f093910b443243330ad93ca', 'https://github.com/advisories/GHSA-4pwq-fj89-6rjc'} | null | {'https://github.com/apache/airflow/commit/5c2bb7b0b0e717b11f093910b443243330ad93ca'} | {'https://github.com/apache/airflow/commit/5c2bb7b0b0e717b11f093910b443243330ad93ca'} |
GHSA | GHSA-f8h4-7rgh-q2gm | Segfault and heap buffer overflow in `{Experimental,}DatasetToTFRecord` | ### Impact
The implementation for `tf.raw_ops.ExperimentalDatasetToTFRecord` and `tf.raw_ops.DatasetToTFRecord` can trigger heap buffer overflow and segmentation fault:
```python
import tensorflow as tf
dataset = tf.data.Dataset.range(3)
dataset = tf.data.experimental.to_variant(dataset)
tf.raw_ops.ExperimentalDatasetToTFRecord(
input_dataset=dataset,
filename='/tmp/output',
compression_type='')
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/data/experimental/to_tf_record_op.cc#L93-L102) assumes that all records in the dataset are of string type. However, there is no check for that, and the example given above uses numeric types.
### Patches
We have patched the issue in GitHub commit [e0b6e58c328059829c3eb968136f17aa72b6c876](https://github.com/tensorflow/tensorflow/commit/e0b6e58c328059829c3eb968136f17aa72b6c876).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-37650'} | 2021-08-25T14:43:24Z | 2021-08-25T14:43:24Z | HIGH | 7.8 | {'CWE-787', 'CWE-120'} | {'https://github.com/advisories/GHSA-f8h4-7rgh-q2gm', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-f8h4-7rgh-q2gm', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37650', 'https://github.com/tensorflow/tensorflow/commit/e0b6e58c328059829c3eb968136f17aa72b6c876'} | null | {'https://github.com/tensorflow/tensorflow/commit/e0b6e58c328059829c3eb968136f17aa72b6c876'} | {'https://github.com/tensorflow/tensorflow/commit/e0b6e58c328059829c3eb968136f17aa72b6c876'} |
GHSA | GHSA-pmcr-2rhp-36hr | SQL injection in github.com/navidrome/navidrome | model/criteria/criteria.go in Navidrome before 0.47.5 is vulnerable to SQL injection attacks when processing crafted Smart Playlists. An authenticated user could abuse this to extract arbitrary data from the database, including the user table (which contains sensitive information such as the users' encrypted passwords). | {'CVE-2022-23857'} | 2022-01-27T16:23:02Z | 2022-01-27T16:23:02Z | MODERATE | 0 | {'CWE-89'} | {'https://github.com/navidrome/navidrome/commit/9e79b5cbf2a48c1e4344df00fea4ed3844ea965d', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23857', 'https://github.com/advisories/GHSA-pmcr-2rhp-36hr', 'https://github.com/navidrome/navidrome/releases/tag/v0.47.5'} | null | {'https://github.com/navidrome/navidrome/commit/9e79b5cbf2a48c1e4344df00fea4ed3844ea965d'} | {'https://github.com/navidrome/navidrome/commit/9e79b5cbf2a48c1e4344df00fea4ed3844ea965d'} |
GHSA | GHSA-8fvr-5rqf-3wwh | Information Exposure in Docker Engine | Docker Engine before 1.6.1 uses weak permissions for (1) /proc/asound, (2) /proc/timer_stats, (3) /proc/latency_stats, and (4) /proc/fs, which allows local users to modify the host, obtain sensitive information, and perform protocol downgrade attacks via a crafted image. | {'CVE-2015-3630'} | 2022-04-12T22:39:05Z | 2022-02-15T01:57:18Z | HIGH | 8.4 | {'CWE-285'} | {'https://github.com/advisories/GHSA-8fvr-5rqf-3wwh', 'https://groups.google.com/forum/#%21searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-3630', 'https://lists.opensuse.org/opensuse-updates/2015-05/msg00023.html', 'https://groups.google.com/forum/#!searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ', 'https://nvd.nist.gov/vuln/detail/CVE-2015-3630', 'https://seclists.org/fulldisclosure/2015/May/28', 'https://packetstormsecurity.com/files/131835/Docker-Privilege-Escalation-Information-Disclosure.html', 'https://github.com/moby/moby/commit/545b440a80f676a506e5837678dd4c4f65e78660', 'https://www.securityfocus.com/bid/74566'} | null | {'https://github.com/moby/moby/commit/545b440a80f676a506e5837678dd4c4f65e78660'} | {'https://github.com/moby/moby/commit/545b440a80f676a506e5837678dd4c4f65e78660'} |
GHSA | GHSA-jqfh-8hw5-fqjr | Improper Handling of Exceptional Conditions in detect-character-encoding | ### Impact
In detect-character-encoding v0.6.0 and earlier, data matching no charset causes the Node.js process to crash.
### Patches
The problem has been patched in [detect-character-encoding v0.7.0](https://github.com/sonicdoe/detect-character-encoding/releases/tag/v0.7.0).
### CVSS score
[CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/RL:O/RC:C](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/RL:O/RC:C)
Base Score: 7.5 (High)
Temporal Score: 7.2 (High)
Since detect-character-encoding is a library, the scoring is based on the “[reasonable worst-case implementation scenario](https://www.first.org/cvss/v3.1/user-guide#3-7-Scoring-Vulnerabilities-in-Software-Libraries-and-Similar)”, namely, accepting data from untrusted sources over a network and passing it directly to detect-character-encoding. Depending on your specific implementation, the vulnerability’s severity in your program may be different.
### Proof of concept
```js
const express = require("express");
const bodyParser = require("body-parser");
const detectCharacterEncoding = require("detect-character-encoding");
const app = express();
app.use(bodyParser.raw());
app.post("/", (req, res) => {
const charsetMatch = detectCharacterEncoding(req.body);
res.end(charsetMatch.encoding);
});
app.listen(3000);
```
`printf "\xAA" | curl --request POST --header "Content-Type: application/octet-stream" --data-binary @- http://localhost:3000` crashes the server. | {'CVE-2021-39157'} | 2022-04-19T19:03:06Z | 2021-08-25T14:44:48Z | HIGH | 7.5 | {'CWE-755'} | {'https://github.com/sonicdoe/detect-character-encoding/commit/992a11007fff6cfd40b952150ab8d30410c4a20a', 'https://github.com/advisories/GHSA-jqfh-8hw5-fqjr', 'https://github.com/sonicdoe/detect-character-encoding/releases/tag/v0.7.0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39157', 'https://github.com/sonicdoe/detect-character-encoding/issues/15', 'https://github.com/sonicdoe/detect-character-encoding/security/advisories/GHSA-jqfh-8hw5-fqjr'} | null | {'https://github.com/sonicdoe/detect-character-encoding/commit/992a11007fff6cfd40b952150ab8d30410c4a20a'} | {'https://github.com/sonicdoe/detect-character-encoding/commit/992a11007fff6cfd40b952150ab8d30410c4a20a'} |
GHSA | GHSA-5fvx-5p2r-4mvp | Open Redirect in firefly-iii | firefly-iii is vulnerable to URL Redirection to Untrusted Site | {'CVE-2021-3851'} | 2021-10-25T20:08:27Z | 2021-10-21T17:48:41Z | MODERATE | 5 | {'CWE-601'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-3851', 'https://huntr.dev/bounties/549a1040-9b5e-420b-9b80-20700dd9d592', 'https://github.com/advisories/GHSA-5fvx-5p2r-4mvp', 'https://github.com/firefly-iii/firefly-iii/commit/8662dfa4c0f71efef61c31dc015c6f723db8318d'} | null | {'https://github.com/firefly-iii/firefly-iii/commit/8662dfa4c0f71efef61c31dc015c6f723db8318d'} | {'https://github.com/firefly-iii/firefly-iii/commit/8662dfa4c0f71efef61c31dc015c6f723db8318d'} |
GHSA | GHSA-qgmg-gppg-76g5 | Inefficient Regular Expression Complexity in validator.js | validator.js prior to 13.7.0 is vulnerable to Inefficient Regular Expression Complexity | {'CVE-2021-3765'} | 2021-11-03T17:34:45Z | 2021-11-03T17:34:45Z | MODERATE | 5.3 | {'CWE-1333'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-3765', 'https://github.com/validatorjs/validator.js/commit/496fc8b2a7f5997acaaec33cc44d0b8dba5fb5e1', 'https://huntr.dev/bounties/c37e975c-21a3-4c5f-9b57-04d63b28cfc9', 'https://github.com/advisories/GHSA-qgmg-gppg-76g5'} | null | {'https://github.com/validatorjs/validator.js/commit/496fc8b2a7f5997acaaec33cc44d0b8dba5fb5e1'} | {'https://github.com/validatorjs/validator.js/commit/496fc8b2a7f5997acaaec33cc44d0b8dba5fb5e1'} |
GHSA | GHSA-5f2r-qp73-37mr | `CHECK`-failures during Grappler's `SafeToRemoveIdentity` in Tensorflow | ### Impact
The Grappler optimizer in TensorFlow can be used to cause a denial of service by altering a `SavedModel` such that [`SafeToRemoveIdentity`](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/grappler/optimizers/dependency_optimizer.cc#L59-L98) would trigger `CHECK` failures.
### Patches
We have patched the issue in GitHub commit [92dba16749fae36c246bec3f9ba474d9ddeb7662](https://github.com/tensorflow/tensorflow/commit/92dba16749fae36c246bec3f9ba474d9ddeb7662).
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-23579'} | 2022-02-11T20:39:08Z | 2022-02-10T00:33:29Z | MODERATE | 6.5 | {'CWE-617'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-23579', 'https://github.com/advisories/GHSA-5f2r-qp73-37mr', 'https://github.com/tensorflow/tensorflow/commit/92dba16749fae36c246bec3f9ba474d9ddeb7662', 'https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/grappler/optimizers/dependency_optimizer.cc#L59-L98', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-5f2r-qp73-37mr'} | null | {'https://github.com/tensorflow/tensorflow/commit/92dba16749fae36c246bec3f9ba474d9ddeb7662'} | {'https://github.com/tensorflow/tensorflow/commit/92dba16749fae36c246bec3f9ba474d9ddeb7662'} |
GHSA | GHSA-mvg9-xffr-p774 | Out of bounds read in Pillow | An issue was discovered in Pillow before 8.1.1. In TiffDecode.c, there is an out-of-bounds read in TiffreadRGBATile via invalid tile boundaries. | {'CVE-2021-25291'} | 2021-12-02T15:31:14Z | 2021-03-29T16:35:57Z | HIGH | 7.5 | {'CWE-125'} | {'https://pillow.readthedocs.io/en/stable/releasenotes/8.1.1.html', 'https://github.com/advisories/GHSA-mvg9-xffr-p774', 'https://github.com/python-pillow/Pillow/commit/cbdce6c5d054fccaf4af34b47f212355c64ace7a', 'https://security.gentoo.org/glsa/202107-33', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25291'} | null | {'https://github.com/python-pillow/Pillow/commit/cbdce6c5d054fccaf4af34b47f212355c64ace7a'} | {'https://github.com/python-pillow/Pillow/commit/cbdce6c5d054fccaf4af34b47f212355c64ace7a'} |
GHSA | GHSA-5gqf-456p-4836 | Reference binding to nullptr in `SdcaOptimizer` | ### Impact
The implementation of `tf.raw_ops.SdcaOptimizer` triggers undefined behavior due to dereferencing a null pointer:
```python
import tensorflow as tf
sparse_example_indices = [tf.constant((0), dtype=tf.int64), tf.constant((0), dtype=tf.int64)]
sparse_feature_indices = [tf.constant([], shape=[0, 0, 0, 0], dtype=tf.int64), tf.constant((0), dtype=tf.int64)]
sparse_feature_values = []
dense_features = []
dense_weights = []
example_weights = tf.constant((0.0), dtype=tf.float32)
example_labels = tf.constant((0.0), dtype=tf.float32)
sparse_indices = [tf.constant((0), dtype=tf.int64), tf.constant((0), dtype=tf.int64)]
sparse_weights = [tf.constant((0.0), dtype=tf.float32), tf.constant((0.0), dtype=tf.float32)]
example_state_data = tf.constant([0.0, 0.0, 0.0, 0.0], shape=[1, 4], dtype=tf.float32)
tf.raw_ops.SdcaOptimizer(
sparse_example_indices=sparse_example_indices,
sparse_feature_indices=sparse_feature_indices,
sparse_feature_values=sparse_feature_values, dense_features=dense_features,
example_weights=example_weights, example_labels=example_labels,
sparse_indices=sparse_indices, sparse_weights=sparse_weights,
dense_weights=dense_weights, example_state_data=example_state_data,
loss_type="logistic_loss", l1=0.0, l2=0.0, num_loss_partitions=1,
num_inner_iterations=1, adaptative=False)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/60a45c8b6192a4699f2e2709a2645a751d435cc3/tensorflow/core/kernels/sdca_internal.cc) does not validate that the user supplied arguments satisfy all [constraints expected by the op](https://www.tensorflow.org/api_docs/python/tf/raw_ops/SdcaOptimizer).
### Patches
We have patched the issue in GitHub commit [f7cc8755ac6683131fdfa7a8a121f9d7a9dec6fb](https://github.com/tensorflow/tensorflow/commit/f7cc8755ac6683131fdfa7a8a121f9d7a9dec6fb).
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-29572'} | 2021-05-21T14:25:31Z | 2021-05-21T14:25:31Z | LOW | 2.5 | {'CWE-476'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-5gqf-456p-4836', 'https://github.com/tensorflow/tensorflow/commit/f7cc8755ac6683131fdfa7a8a121f9d7a9dec6fb', 'https://github.com/advisories/GHSA-5gqf-456p-4836', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29572'} | null | {'https://github.com/tensorflow/tensorflow/commit/f7cc8755ac6683131fdfa7a8a121f9d7a9dec6fb'} | {'https://github.com/tensorflow/tensorflow/commit/f7cc8755ac6683131fdfa7a8a121f9d7a9dec6fb'} |
GHSA | GHSA-34hv-f45p-4qfq | Open redirect in wwbn/avideo | Open redirect vulnerability in objects/login.json.php in WWBN AVideo through 11.6, allows attackers to arbitrarily redirect users from a crafted url to the login page. A patch is available on the `master` branch of the repository. | {'CVE-2022-27463'} | 2022-04-19T14:13:44Z | 2022-04-06T00:01:29Z | MODERATE | 6.1 | {'CWE-601'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-27463', 'https://avideo.tube/', 'https://github.com/WWBN/AVideo/commit/77e9aa6411ff4b97571eb82e587139ec05ff894c', 'https://github.com/advisories/GHSA-34hv-f45p-4qfq'} | null | {'https://github.com/WWBN/AVideo/commit/77e9aa6411ff4b97571eb82e587139ec05ff894c'} | {'https://github.com/WWBN/AVideo/commit/77e9aa6411ff4b97571eb82e587139ec05ff894c'} |
GHSA | GHSA-7p8f-8hjm-wm92 | Lookup operations do not take into account wildcards in SpiceDB | ### Impact
Any user making use of a wildcard relationship under the right hand branch of an `exclusion` or within an `intersection` operation will see `Lookup`/`LookupResources` return a resource as "accessible" if it is *not* accessible by virtue of the inclusion of the wildcard in the intersection or the right side of the exclusion.
For example, given schema:
```zed
definition user {}
definition resource {
relation viewer: user
relation banned: user | user:*
permission view = viewer - banned
}
```
If `user:*` is placed into the `banned` relation for a particular resource, `view` should return false for *all* resources. in `v1.3.0`, the wildcard is ignored entirely in lookup's dispatch, resulting in the `banned` wildcard being ignored in the exclusion.
### Workarounds
Don't make use of wildcards on the right side of intersections or within exclusions.
### References
https://github.com/authzed/spicedb/issues/358
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [SpiceDB](https://github.com/authzed/spicedb)
* Ask a question in the [SpiceDB Discord](https://authzed.com/discord)
| {'CVE-2022-21646'} | 2022-04-19T19:03:19Z | 2022-01-13T15:05:41Z | HIGH | 8.1 | {'CWE-155', 'CWE-20'} | {'https://github.com/authzed/spicedb/commit/15bba2e2d2a4bda336a37a7fe8ef8a35028cd970', 'https://github.com/advisories/GHSA-7p8f-8hjm-wm92', 'https://github.com/authzed/spicedb/issues/358', 'https://github.com/authzed/spicedb/releases/tag/v1.4.0', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21646', 'https://github.com/authzed/spicedb/security/advisories/GHSA-7p8f-8hjm-wm92'} | null | {'https://github.com/authzed/spicedb/commit/15bba2e2d2a4bda336a37a7fe8ef8a35028cd970'} | {'https://github.com/authzed/spicedb/commit/15bba2e2d2a4bda336a37a7fe8ef8a35028cd970'} |
GHSA | GHSA-gx5w-rrhp-f436 | XSS in mdBook | > This is a cross-post of [the official security advisory][ml]. The official post contains a signed version with our PGP key, as well.
[ml]: https://groups.google.com/g/rustlang-security-announcements/c/3-sO6of29O0
The Rust Security Response Working Group was recently notified of a security issue affecting the search feature of mdBook, which could allow an attacker to execute arbitrary JavaScript code on the page.
The CVE for this vulnerability is [CVE-2020-26297](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26297).
## Overview
The search feature of mdBook (introduced in version 0.1.4) was affected by a cross site scripting vulnerability that allowed an attacker to execute arbitrary JavaScript code on an user's browser by tricking the user into typing a malicious search query, or tricking the user into clicking a link to the search page with the malicious search query prefilled.
mdBook 0.4.5 fixes the vulnerability by properly escaping the search query.
## Mitigations
Owners of websites built with mdBook have to upgrade to mdBook 0.4.5 or greater and rebuild their website contents with it. It's possible to install mdBook 0.4.5 on the local system with:
```
cargo install mdbook --version 0.4.5 --force
```
## Acknowledgements
Thanks to Kamil Vavra for responsibly disclosing the vulnerability to us according to [our security policy](https://www.rust-lang.org/policies/security).
## Timeline of events
All times are listed in UTC.
- 2020-12-30 20:14 - The issue is reported to the Rust Security Response WG
- 2020-12-30 20:32 - The issue is acknowledged and the investigation began
- 2020-12-30 21:21 - Found the cause of the vulnerability and prepared the patch
- 2021-01-04 15:00 - Patched version released and vulnerability disclosed | {'CVE-2020-26297'} | 2022-04-19T19:02:44Z | 2021-08-25T20:56:20Z | HIGH | 8.2 | {'CWE-79'} | {'https://github.com/rust-lang/mdBook/blob/master/CHANGELOG.md#mdbook-045', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26297', 'https://groups.google.com/g/rustlang-security-announcements/c/3-sO6of29O0', 'https://rustsec.org/advisories/RUSTSEC-2021-0001.html', 'https://github.com/advisories/GHSA-gx5w-rrhp-f436', 'https://github.com/rust-lang/mdBook/commit/32abeef088e98327ca0dfccdad92e84afa9d2e9b', 'https://github.com/rust-lang/mdBook/security/advisories/GHSA-gx5w-rrhp-f436'} | null | {'https://github.com/rust-lang/mdBook/commit/32abeef088e98327ca0dfccdad92e84afa9d2e9b'} | {'https://github.com/rust-lang/mdBook/commit/32abeef088e98327ca0dfccdad92e84afa9d2e9b'} |
GHSA | GHSA-pqm6-cgwr-x6pf | Signature validation bypass in XmlSecLibs | Rob Richards XmlSecLibs, all versions prior to v3.0.3, as used for example by SimpleSAMLphp, performed incorrect validation of cryptographic signatures in XML messages, allowing an authenticated attacker to impersonate others or elevate privileges by creating a crafted XML message. | {'CVE-2019-3465'} | 2021-08-18T22:14:39Z | 2019-11-08T20:06:46Z | HIGH | 8.8 | {'CWE-347'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OCSR3V6LNWJAD37VQB6M2K7P4RQSCVFG/', 'https://github.com/robrichards/xmlseclibs/commit/0a53d3c3aa87564910cae4ed01416441d3ae0db5', 'https://lists.debian.org/debian-lts-announce/2019/11/msg00003.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HBE2SJSXG7J4XYLJ2H6HC2VPPOG2OMUN/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AB34ILMJ67CUROBOR6YPKB46VHXLOAJ4/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BBKVDUZ7G5ZOUO4BFJWLNJ6VOKBQJX5U/', 'https://nvd.nist.gov/vuln/detail/CVE-2019-3465', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BNFMY5RRLU63P25HEBVDO5KAVI7TX7JV/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MAWOVYLZKYDCQBLQEJCFAAD3KQTBPHXE/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XBSSRV5Q7JFCYO46A3EN624UZ4KXFQ2M/', 'https://simplesamlphp.org/security/201911-01', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7KID7C4AZPYYIZQIPSLANP4R2RQR6YK3/', 'https://seclists.org/bugtraq/2019/Nov/8', 'https://github.com/advisories/GHSA-pqm6-cgwr-x6pf', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ESKJTWLE7QZBQ3EKMYXKMBQG3JDEJWM6/', 'https://www.debian.org/security/2019/dsa-4560', 'https://www.tenable.com/security/tns-2019-09'} | null | {'https://github.com/robrichards/xmlseclibs/commit/0a53d3c3aa87564910cae4ed01416441d3ae0db5'} | {'https://github.com/robrichards/xmlseclibs/commit/0a53d3c3aa87564910cae4ed01416441d3ae0db5'} |
GHSA | GHSA-4hq8-gmxx-h6w9 | XML Processing error in github.com/crewjam/saml | ### Impact
There are three vulnerabilities in the go `encoding/xml` package that can allow an attacker to forge part of a signed XML document. For details on this vulnerability see [xml-roundtrip-validator](https://github.com/mattermost/xml-roundtrip-validator)
### Patches
In version 0.4.3, all XML input is validated prior to being parsed. | {'CVE-2020-27846'} | 2021-06-23T17:29:42Z | 2021-06-23T17:29:42Z | HIGH | 9.8 | {'CWE-287', 'CWE-115'} | {'https://github.com/advisories/GHSA-4hq8-gmxx-h6w9', 'https://security.netapp.com/advisory/ntap-20210205-0002/', 'https://github.com/crewjam/saml/security/advisories/GHSA-4hq8-gmxx-h6w9', 'https://nvd.nist.gov/vuln/detail/CVE-2020-27846', 'https://github.com/crewjam/saml/commit/da4f1a0612c0a8dd0452cf8b3c7a6518f6b4d053', 'https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3YUTKIRWT6TWU7DS6GF3EOANVQBFQZYI/', 'https://grafana.com/blog/2020/12/17/grafana-6.7.5-7.2.3-and-7.3.6-released-with-important-security-fix-for-grafana-enterprise/', 'https://bugzilla.redhat.com/show_bug.cgi?id=1907670', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ICP3YRY2VUCNCF2VFUSK77ZMRIC77FEM/'} | null | {'https://github.com/crewjam/saml/commit/da4f1a0612c0a8dd0452cf8b3c7a6518f6b4d053'} | {'https://github.com/crewjam/saml/commit/da4f1a0612c0a8dd0452cf8b3c7a6518f6b4d053'} |
GHSA | GHSA-6h88-qjpv-p32m | OpenSSL gem for Ruby using inadequate encryption strength | The OpenSSL gem for Ruby uses the same initialization vector (IV) in GCM Mode (aes-*-gcm) when the IV is set before the key, which makes it easier for context-dependent attackers to bypass the encryption protection mechanism. | {'CVE-2016-7798'} | 2022-04-25T16:33:58Z | 2017-10-24T18:33:35Z | HIGH | 7.5 | {'CWE-326'} | {'https://github.com/advisories/GHSA-6h88-qjpv-p32m', 'https://www.debian.org/security/2017/dsa-3966', 'https://lists.debian.org/debian-lts-announce/2018/07/msg00012.html', 'https://github.com/ruby/openssl/issues/49', 'http://www.openwall.com/lists/oss-security/2016/09/30/6', 'https://nvd.nist.gov/vuln/detail/CVE-2016-7798', 'http://www.securityfocus.com/bid/93031', 'https://github.com/ruby/openssl/commit/8108e0a6db133f3375608303fdd2083eb5115062', 'http://www.openwall.com/lists/oss-security/2016/09/19/9', 'http://www.openwall.com/lists/oss-security/2016/10/01/2'} | null | {'https://github.com/ruby/openssl/commit/8108e0a6db133f3375608303fdd2083eb5115062'} | {'https://github.com/ruby/openssl/commit/8108e0a6db133f3375608303fdd2083eb5115062'} |
GHSA | GHSA-4gw3-8f77-f72c | Regular expression denial of service in codemirror | This affects the package codemirror before 5.58.2; the package org.apache.marmotta.webjars:codemirror before 5.58.2.
The vulnerable regular expression is located in https://github.com/codemirror/CodeMirror/blob/cdb228ac736369c685865b122b736cd0d397836c/mode/javascript/javascript.jsL129. The ReDOS vulnerability of the regex is mainly due to the sub-pattern (s|/*.*?*/)* | {'CVE-2020-7760'} | 2022-04-22T17:20:51Z | 2021-05-10T18:46:27Z | MODERATE | 5.3 | {'CWE-400'} | {'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-1024445', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBCOMPONENTS-1024446', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARS-1024449', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7760', 'https://www.npmjs.com/package/codemirror', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEMARMOTTAWEBJARS-1024450', 'https://snyk.io/vuln/SNYK-JS-CODEMIRROR-1016937', 'https://github.com/codemirror/CodeMirror/commit/55d0333907117c9231ffdf555ae8824705993bbb', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBCODEMIRROR-1024448', 'https://www.debian.org/security/2020/dsa-4789', 'https://github.com/advisories/GHSA-4gw3-8f77-f72c', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1024447', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/codemirror/CodeMirror/commit/55d0333907117c9231ffdf555ae8824705993bbb'} | {'https://github.com/codemirror/CodeMirror/commit/55d0333907117c9231ffdf555ae8824705993bbb'} |
GHSA | GHSA-vmjw-c2vp-p33c | Crash in NMS ops caused by integer conversion to unsigned | ### Impact
An attacker can cause denial of service in applications serving models using `tf.raw_ops.NonMaxSuppressionV5` by triggering a division by 0:
```python
import tensorflow as tf
tf.raw_ops.NonMaxSuppressionV5(
boxes=[[0.1,0.1,0.1,0.1],[0.2,0.2,0.2,0.2],[0.3,0.3,0.3,0.3]],
scores=[1.0,2.0,3.0],
max_output_size=-1,
iou_threshold=0.5,
score_threshold=0.5,
soft_nms_sigma=1.0,
pad_to_max_output_size=True)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/image/non_max_suppression_op.cc#L170-L271) uses a user controlled argument to resize a `std::vector`:
```cc
const int output_size = max_output_size.scalar<int>()();
// ...
std::vector<int> selected;
// ...
if (pad_to_max_output_size) {
selected.resize(output_size, 0);
// ...
}
```
However, as `std::vector::resize` takes the size argument as a `size_t` and `output_size` is an `int`, there is an implicit conversion to usigned. If the attacker supplies a negative value, this conversion results in a crash.
A similar issue occurs in `CombinedNonMaxSuppression`:
```python
import tensorflow as tf
tf.raw_ops.NonMaxSuppressionV5(
boxes=[[[[0.1,0.1,0.1,0.1],[0.2,0.2,0.2,0.2],[0.3,0.3,0.3,0.3]],[[0.1,0.1,0.1,0.1],[0.2,0.2,0.2,0.2],[0.3,0.3,0.3,0.3]],[[0.1,0.1,0.1,0.1],[0.2,0.2,0.2,0.2],[0.3,0.3,0.3,0.3]]]],
scores=[[[1.0,2.0,3.0],[1.0,2.0,3.0],[1.0,2.0,3.0]]],
max_output_size_per_class=-1,
max_total_size=10,
iou_threshold=score_threshold=0.5,
pad_per_class=True,
clip_boxes=True)
```
### Patches
We have patched the issue in GitHub commit [3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d](https://github.com/tensorflow/tensorflow/commit/3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d) and commit [b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58](https://github.com/tensorflow/tensorflow/commit/b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-37669'} | 2021-08-25T14:42:03Z | 2021-08-25T14:42:03Z | MODERATE | 5.5 | {'CWE-681'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-vmjw-c2vp-p33c', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37669', 'https://github.com/tensorflow/tensorflow/commit/3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d', 'https://github.com/advisories/GHSA-vmjw-c2vp-p33c', 'https://github.com/tensorflow/tensorflow/commit/b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58'} | null | {'https://github.com/tensorflow/tensorflow/commit/3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d', 'https://github.com/tensorflow/tensorflow/commit/b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58'} | {'https://github.com/tensorflow/tensorflow/commit/b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58', 'https://github.com/tensorflow/tensorflow/commit/3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d'} |
GHSA | GHSA-hg2p-2cvq-4ppv | Cross-site scripting in lazysizes | lazysizes through 5.2.0 allows execution of malicious JavaScript. The following attributes are not sanitized by the video-embed plugin: data-vimeo, data-vimeoparams, data-youtube and data-ytparams which can be abused to inject malicious JavaScript. | {'CVE-2020-7642'} | 2021-12-10T20:06:23Z | 2021-12-10T20:06:23Z | LOW | 5.4 | {'CWE-79'} | {'https://snyk.io/vuln/SNYK-JS-LAZYSIZES-567144', 'https://github.com/advisories/GHSA-hg2p-2cvq-4ppv', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7642', 'https://github.com/aFarkas/lazysizes/commit/3720ab8262552d4e063a38d8492f9490a231fd48'} | null | {'https://github.com/aFarkas/lazysizes/commit/3720ab8262552d4e063a38d8492f9490a231fd48'} | {'https://github.com/aFarkas/lazysizes/commit/3720ab8262552d4e063a38d8492f9490a231fd48'} |
GHSA | GHSA-w749-p3v6-hccq | Possible code injection vulnerability in Rails / Active Storage | The Active Storage module of Rails starting with version 5.2.0 are possibly vulnerable to code injection. This issue was patched in versions 5.2.6.3, 6.0.4.7, 6.1.4.7, and 7.0.2.3. To work around this issue, applications should implement a strict allow-list on accepted transformation methods or arguments. Additionally, a strict ImageMagick security policy will help mitigate this issue. | {'CVE-2022-21831'} | 2022-04-19T19:03:27Z | 2022-03-08T21:25:54Z | HIGH | 0 | {'CWE-94'} | {'https://github.com/advisories/GHSA-w749-p3v6-hccq', 'https://github.com/rails/rails/commit/0a72f7d670e9aa77a0bb8584cb1411ddabb7546e', 'https://rubysec.com/advisories/CVE-2022-21831/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21831', 'https://groups.google.com/g/rubyonrails-security/c/n-p-W1yxatI'} | null | {'https://github.com/rails/rails/commit/0a72f7d670e9aa77a0bb8584cb1411ddabb7546e'} | {'https://github.com/rails/rails/commit/0a72f7d670e9aa77a0bb8584cb1411ddabb7546e'} |
GHSA | GHSA-3fw8-66wf-pr7m | methodOverride Middleware Reflected Cross-Site Scripting in connect | Connect is a stack of middleware that is executed in order in each request.
The "methodOverride" middleware allows the http post to override the method of the request with the value of the "_method" post key or with the header "x-http-method-override".
Because the user post input was not checked, req.method could contain any kind of value. Because the req.method did not match any common method VERB, connect answered with a 404 page containing the "Cannot `[method]` `[url]`" content. The method was not properly encoded for output in the browser.
###Example:
```
~ curl "localhost:3000" -d "_method=<script src=http://nodesecurity.io/xss.js></script>"
Cannot <SCRIPT SRC=HTTP://NODESECURITY.IO/XSS.JS></SCRIPT> /
```
## Recommendation
Update to the newest version of Connect or disable methodOverride. It is not possible to avoid the vulnerability if you have enabled this middleware in the top of your stack. | {'CVE-2013-7370'} | 2021-04-07T19:56:51Z | 2020-08-31T22:41:27Z | LOW | 0 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2013-7370', 'https://github.com/senchalabs/connect/commit/277e5aad6a95d00f55571a9a0e11f2fa190d8135', 'https://nodesecurity.io/advisories/methodOverride_Middleware_Reflected_Cross-Site_Scripting', 'http://www.openwall.com/lists/oss-security/2014/05/13/1', 'https://github.com/senchalabs/connect/issues/831', 'https://access.redhat.com/security/cve/cve-2013-7370', 'https://security-tracker.debian.org/tracker/CVE-2013-7370', 'http://www.openwall.com/lists/oss-security/2014/04/21/2', 'https://bugzilla.suse.com/show_bug.cgi?id=CVE-2013-7370', 'https://github.com/senchalabs/connect/commit/126187c4e12162e231b87350740045e5bb06e93a', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-7370', 'https://www.npmjs.com/advisories/3', 'https://github.com/advisories/GHSA-3fw8-66wf-pr7m'} | null | {'https://github.com/senchalabs/connect/commit/126187c4e12162e231b87350740045e5bb06e93a', 'https://github.com/senchalabs/connect/commit/277e5aad6a95d00f55571a9a0e11f2fa190d8135'} | {'https://github.com/senchalabs/connect/commit/126187c4e12162e231b87350740045e5bb06e93a', 'https://github.com/senchalabs/connect/commit/277e5aad6a95d00f55571a9a0e11f2fa190d8135'} |
GHSA | GHSA-7c82-mp33-r854 | Cross-site scripting in bootstrap-select | bootstrap-select before 1.13.6 allows Cross-Site Scripting (XSS). It does not escape title values in OPTION elements. This may allow attackers to execute arbitrary JavaScript in a victim's browser. | {'CVE-2019-20921'} | 2021-05-07T16:47:54Z | 2021-05-07T16:47:54Z | MODERATE | 6.1 | {'CWE-79'} | {'https://www.npmjs.com/advisories/1522', 'https://github.com/advisories/GHSA-7c82-mp33-r854', 'https://nvd.nist.gov/vuln/detail/CVE-2019-20921', 'https://github.com/advisories/GHSA-9r7h-6639-v5mw', 'https://github.com/snapappointments/bootstrap-select/issues/2199', 'https://github.com/snapappointments/bootstrap-select/commit/ab6e068748040cf3cda5859f6349b382402b8767', 'https://snyk.io/vuln/SNYK-JS-BOOTSTRAPSELECT-570457'} | null | {'https://github.com/snapappointments/bootstrap-select/commit/ab6e068748040cf3cda5859f6349b382402b8767'} | {'https://github.com/snapappointments/bootstrap-select/commit/ab6e068748040cf3cda5859f6349b382402b8767'} |
GHSA | GHSA-4mv4-gmmf-q382 | Cross-Site Scripting in datatables | Cross-site scripting (XSS) vulnerability in the DataTables plugin 1.10.8 and earlier for jQuery allows remote attackers to inject arbitrary web script or HTML via the scripts parameter to media/unit_testing/templates/6776.php.
## Recommendation
Update to a version greater than 1.10.8. | {'CVE-2015-6584'} | 2021-09-23T19:26:59Z | 2020-08-31T22:42:29Z | HIGH | 0 | {'CWE-79'} | {'https://www.netsparker.com/cve-2015-6384-xss-vulnerability-identified-in-datatables/', 'http://www.securityfocus.com/archive/1/536437/100/0/threaded', 'https://www.npmjs.com/advisories/5', 'http://seclists.org/fulldisclosure/2015/Sep/37', 'https://github.com/advisories/GHSA-4mv4-gmmf-q382', 'https://github.com/DataTables/DataTables/issues/602', 'http://packetstormsecurity.com/files/133555/DataTables-1.10.8-Cross-Site-Scripting.html', 'https://github.com/DataTables/DataTablesSrc/commit/ccf86dc5982bd8e16d', 'http://www.securityfocus.com/archive/1/archive/1/536437/100/0/threaded', 'https://nvd.nist.gov/vuln/detail/CVE-2015-6584'} | null | {'https://github.com/DataTables/DataTablesSrc/commit/ccf86dc5982bd8e16d'} | {'https://github.com/DataTables/DataTablesSrc/commit/ccf86dc5982bd8e16d'} |
GHSA | GHSA-68v9-3jjq-rvp4 | Exposure of Sensitive Information to an Unauthorized Actor | Shopware is an open source eCommerce platform. In versions prior to 6.4.1.1 the admin api has exposed some internal hidden fields when an association has been loaded with a to many reference. Users are recommend to update to version 6.4.1.1. You can get the update to 6.4.1.1 regularly via the Auto-Updater or directly via the download overview. For older versions of 6.1, 6.2, and 6.3, corresponding security measures are also available via a plugin. | {'CVE-2021-32716'} | 2021-09-08T18:00:40Z | 2021-09-08T18:00:40Z | MODERATE | 4.4 | {'CWE-200'} | {'https://github.com/shopware/platform/security/advisories/GHSA-gpmh-g94g-qrhr', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32716', 'https://github.com/shopware/platform/commit/b5c3ce3e93bd121324d72aa9d367cb636ff1c0eb', 'https://github.com/advisories/GHSA-68v9-3jjq-rvp4', 'https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-06-2021'} | null | {'https://github.com/shopware/platform/commit/b5c3ce3e93bd121324d72aa9d367cb636ff1c0eb'} | {'https://github.com/shopware/platform/commit/b5c3ce3e93bd121324d72aa9d367cb636ff1c0eb'} |
GHSA | GHSA-3f99-hvg4-qjwj | Insecure random number generation in keypair | ## Description and Impact
A bug in the pseudo-random number generator used by [keypair](https://github.com/juliangruber/keypair) versions up to and including 1.0.3 could allow for weak RSA key generation. This could enable an attacker to decrypt confidential messages or gain authorized access to an account belonging to the victim. We recommend replacing any RSA keys that were generated using keypair version 1.0.3 or earlier.
## Fix
* The [bug](https://github.com/juliangruber/keypair/blob/87c62f255baa12c1ec4f98a91600f82af80be6db/index.js#L1008) in the pseudo-random number generator is fixed in commit [`9596418`](https://github.com/juliangruber/keypair/commit/9596418d3363d3e757676c0b6a8f2d35a9d1cb18).
* If the crypto module is available, it is used instead of the pseudo-random number generator. Also fixed in [`9596418`](https://github.com/juliangruber/keypair/commit/9596418d3363d3e757676c0b6a8f2d35a9d1cb18)
## Additional Details
The specific [line](https://github.com/juliangruber/keypair/blob/87c62f255baa12c1ec4f98a91600f82af80be6db/index.js#L1008) with the flaw is:
```javascript
b.putByte(String.fromCharCode(next & 0xFF))
```
The [definition](https://github.com/juliangruber/keypair/blob/87c62f255baa12c1ec4f98a91600f82af80be6db/index.js#L350-L352) of `putByte` is
```javascript
util.ByteBuffer.prototype.putByte = function(b) {
this.data += String.fromCharCode(b);
};
```
Simplified, this is `String.fromCharCode(String.fromCharCode(next & 0xFF))`. This results in most of the buffer containing zeros. An example generated buffer:
(Note: truncated for brevity)
```
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
\x00\x00\x00\x00\x04\x00\x00\x00....\x00\x00\x00\x00\x00\x00\x00\x00\x00
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
```
Since it is masking with 0xFF, approximately 97% of the bytes are converted to zeros. The impact is that each byte in the RNG seed has a 97% chance of being 0 due to incorrect conversion.
## Credit
This issue was reported to GitHub Security Lab by Ross Wheeler of Axosoft. It was discovered by Axosoft engineer Dan Suceava, who noticed that [keypair](https://github.com/juliangruber/keypair) was regularly generating duplicate RSA keys. GitHub security engineer [@vcsjones (Kevin Jones)](https://github.com/vcsjones) independently investigated the problem and identified the cause and source code location of the bug. | {'CVE-2021-41117'} | 2022-04-19T19:03:11Z | 2021-10-11T17:09:05Z | HIGH | 8.7 | {'CWE-335'} | {'https://github.com/juliangruber/keypair/releases/tag/v1.0.4', 'https://github.com/juliangruber/keypair/security/advisories/GHSA-3f99-hvg4-qjwj', 'https://securitylab.github.com/advisories/GHSL-2021-1012-keypair/', 'https://github.com/juliangruber/keypair/commit/9596418d3363d3e757676c0b6a8f2d35a9d1cb18', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41117', 'https://github.com/advisories/GHSA-3f99-hvg4-qjwj'} | null | {'https://github.com/juliangruber/keypair/commit/9596418d3363d3e757676c0b6a8f2d35a9d1cb18'} | {'https://github.com/juliangruber/keypair/commit/9596418d3363d3e757676c0b6a8f2d35a9d1cb18'} |
GHSA | GHSA-ch4f-829c-v5pw | Division by 0 in `ResourceScatterDiv` | ### Impact
The implementation of `tf.raw_ops.ResourceScatterDiv` is vulnerable to a division by 0 error:
```python
import tensorflow as tf
v= tf.Variable([1,2,3])
tf.raw_ops.ResourceScatterDiv(
resource=v.handle,
indices=[1],
updates=[0])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/resource_variable_ops.cc#L865) uses a common class for all binary operations but fails to treat the division by 0 case separately.
### Patches
We have patched the issue in GitHub commit [4aacb30888638da75023e6601149415b39763d76](https://github.com/tensorflow/tensorflow/commit/4aacb30888638da75023e6601149415b39763d76).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-37642'} | 2021-08-25T14:43:56Z | 2021-08-25T14:43:56Z | MODERATE | 5.5 | {'CWE-369'} | {'https://github.com/tensorflow/tensorflow/commit/4aacb30888638da75023e6601149415b39763d76', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37642', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-ch4f-829c-v5pw', 'https://github.com/advisories/GHSA-ch4f-829c-v5pw'} | null | {'https://github.com/tensorflow/tensorflow/commit/4aacb30888638da75023e6601149415b39763d76'} | {'https://github.com/tensorflow/tensorflow/commit/4aacb30888638da75023e6601149415b39763d76'} |
GHSA | GHSA-hxcc-f52p-wc94 | Insecure serialization leading to RCE in serialize-javascript | serialize-javascript prior to 3.1.0 allows remote attackers to inject arbitrary code via the function "deleteFunctions" within "index.js".
An object such as `{"foo": /1"/, "bar": "a\"@__R-<UID>-0__@"}` was serialized as `{"foo": /1"/, "bar": "a\/1"/}`, which allows an attacker to escape the `bar` key. This requires the attacker to control the values of both `foo` and `bar` and guess the value of `<UID>`. The UID has a keyspace of approximately 4 billion making it a realistic network attack. | {'CVE-2020-7660'} | 2021-09-23T18:51:00Z | 2020-08-11T17:21:13Z | HIGH | 8.1 | {'CWE-502'} | {'https://github.com/advisories/GHSA-hxcc-f52p-wc94', 'https://github.com/yahoo/serialize-javascript/commit/f21a6fb3ace2353413761e79717b2d210ba6ccbd', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7660'} | null | {'https://github.com/yahoo/serialize-javascript/commit/f21a6fb3ace2353413761e79717b2d210ba6ccbd'} | {'https://github.com/yahoo/serialize-javascript/commit/f21a6fb3ace2353413761e79717b2d210ba6ccbd'} |
GHSA | GHSA-6wrh-279j-6hvw | HTTP caching is marking private HTTP headers as public in Shopware | ### Impact
HTTP caching is marking private HTTP headers as public
## Patches
Fixed in recommend updating to the current version 6.4.8.2. You can get the update to 6.4.8.2 regularly via the Auto-Updater or directly via the download overview.
https://www.shopware.com/en/download/#shopware-6
## Workarounds
For older versions of 6.1, 6.2, and 6.3, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version. | {'CVE-2022-24747'} | 2022-03-18T20:15:07Z | 2022-03-10T17:55:21Z | MODERATE | 6.3 | {'CWE-200'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-24747', 'https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-03-2022', 'https://github.com/shopware/platform/commit/d51863148f32306aafdbc7f9f48887c69fce206f', 'https://github.com/shopware/platform/security/advisories/GHSA-6wrh-279j-6hvw', 'https://github.com/advisories/GHSA-6wrh-279j-6hvw'} | null | {'https://github.com/shopware/platform/commit/d51863148f32306aafdbc7f9f48887c69fce206f'} | {'https://github.com/shopware/platform/commit/d51863148f32306aafdbc7f9f48887c69fce206f'} |
GHSA | GHSA-9hx8-2mrv-r674 | Deserialization of Untrusted Data in Apache jUDDI | Apache jUDDI uses several classes related to Java's Remote Method Invocation (RMI) which (as an extension to UDDI) provides an alternate transport for accessing UDDI services.
RMI uses the default Java serialization mechanism to pass parameters in RMI invocations. A remote attacker can send a malicious serialized object to the above RMI entries. The objects get deserialized without any check on the incoming data. In the worst case, it may let the attacker run arbitrary code remotely.
For both jUDDI web service applications and jUDDI clients, the usage of RMI is disabled by default. Since this is an optional feature and an extension to the UDDI protocol, the likelihood of impact is low. Starting with 3.3.10, all RMI related code was removed. | {'CVE-2021-37578'} | 2021-08-31T21:02:02Z | 2021-08-09T20:41:37Z | CRITICAL | 9.8 | {'CWE-502'} | {'https://github.com/advisories/GHSA-9hx8-2mrv-r674', 'https://lists.apache.org/thread.html/r82047b3ba774cf870ea8e1e9ec51c6107f6cd056d4e36608148c6e71%40%3Cprivate.juddi.apache.org%3E', 'https://github.com/apache/juddi/commit/dd880ffe7694a70cee75efeee79c9197d261866f', 'http://www.openwall.com/lists/oss-security/2021/07/29/1', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37578'} | null | {'https://github.com/apache/juddi/commit/dd880ffe7694a70cee75efeee79c9197d261866f'} | {'https://github.com/apache/juddi/commit/dd880ffe7694a70cee75efeee79c9197d261866f'} |
GHSA | GHSA-hgpf-97c5-74fc | Regular expression denial of service in @absolunet/kafe | This affects the package @absolunet/kafe before 3.2.10. It allows cause a denial of service when validating crafted invalid emails. | {'CVE-2020-7761'} | 2021-05-10T19:08:29Z | 2021-05-10T19:08:29Z | MODERATE | 5.3 | {'CWE-400'} | {'https://www.npmjs.com/package/@absolunet/kafe', 'https://github.com/absolunet/kafe/commit/c644c798bfcdc1b0bbb1f0ca59e2e2664ff3fdd0%23diff-f0f4b5b19ad46588ae9d7dc1889f681252b0698a4ead3a77b7c7d127ee657857', 'https://snyk.io/vuln/SNYK-JS-ABSOLUNETKAFE-1017403', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7761', 'https://github.com/advisories/GHSA-hgpf-97c5-74fc'} | null | {'https://github.com/absolunet/kafe/commit/c644c798bfcdc1b0bbb1f0ca59e2e2664ff3fdd0#diff-f0f4b5b19ad46588ae9d7dc1889f681252b0698a4ead3a77b7c7d127ee657857'} | {'https://github.com/absolunet/kafe/commit/c644c798bfcdc1b0bbb1f0ca59e2e2664ff3fdd0#diff-f0f4b5b19ad46588ae9d7dc1889f681252b0698a4ead3a77b7c7d127ee657857'} |
GHSA | GHSA-fqq2-xp7m-xvm8 | Data race in ruspiro-singleton | `Singleton<T>` is meant to be a static object that can be initialized lazily. In
order to satisfy the requirement that `static` items must implement `Sync`,
`Singleton` implemented both `Sync` and `Send` unconditionally.
This allows for a bug where non-`Sync` types such as `Cell` can be used in
singletons and cause data races in concurrent programs.
The flaw was corrected in commit `b0d2bd20e` by adding trait bounds, requiring
the contaiend type to implement `Sync`.
| {'CVE-2020-36435'} | 2021-08-25T20:58:19Z | 2021-08-25T20:58:19Z | HIGH | 8.1 | {'CWE-119', 'CWE-362'} | {'https://rustsec.org/advisories/RUSTSEC-2020-0115.html', 'https://github.com/RusPiRo/ruspiro-singleton/pull/11', 'https://github.com/RusPiRo/ruspiro-singleton/commit/b0d2bd20eb40b9cbc2958b981ba2dcd9e6f9396e', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36435', 'https://github.com/RusPiRo/ruspiro-singleton/issues/10', 'https://github.com/advisories/GHSA-fqq2-xp7m-xvm8'} | null | {'https://github.com/RusPiRo/ruspiro-singleton/commit/b0d2bd20eb40b9cbc2958b981ba2dcd9e6f9396e'} | {'https://github.com/RusPiRo/ruspiro-singleton/commit/b0d2bd20eb40b9cbc2958b981ba2dcd9e6f9396e'} |
GHSA | GHSA-q6w2-89hq-hq27 | Cross-site scripting in keycloak | A flaw was found in keycloak in versions before 13.0.0. A Self Stored XSS attack vector escalating to a complete account takeover is possible due to user-supplied data fields not being properly encoded and Javascript code being used to process the data. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. | {'CVE-2021-20195'} | 2021-06-08T23:02:43Z | 2021-06-08T23:02:43Z | CRITICAL | 9.6 | {'CWE-20', 'CWE-79'} | {'https://github.com/advisories/GHSA-q6w2-89hq-hq27', 'https://nvd.nist.gov/vuln/detail/CVE-2021-20195', 'https://github.com/keycloak/keycloak/commit/717d9515fa131e3d8c8936e41b2e52270fdec976', 'https://bugzilla.redhat.com/show_bug.cgi?id=1919143'} | null | {'https://github.com/keycloak/keycloak/commit/717d9515fa131e3d8c8936e41b2e52270fdec976'} | {'https://github.com/keycloak/keycloak/commit/717d9515fa131e3d8c8936e41b2e52270fdec976'} |
GHSA | GHSA-9pq7-rcxv-47vq | Incorrect Regular Expression in RestSharp | RestSharp < 106.11.8-alpha.0.13 uses a regular expression which is vulnerable to Regular Expression Denial of Service (ReDoS) when converting strings into DateTimes. If a server responds with a malicious string, the client using RestSharp will be stuck processing it for an exceedingly long time. Thus the remote server can trigger Denial of Service. | {'CVE-2021-27293'} | 2021-07-15T20:24:44Z | 2021-07-14T19:10:01Z | HIGH | 7.5 | {'CWE-697', 'CWE-185'} | {'https://restsharp.dev/', 'https://github.com/advisories/GHSA-9pq7-rcxv-47vq', 'https://github.com/restsharp/RestSharp/issues/1556', 'https://github.com/restsharp/RestSharp/commit/be39346784b68048b230790d15333574341143bc', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27293'} | null | {'https://github.com/restsharp/RestSharp/commit/be39346784b68048b230790d15333574341143bc'} | {'https://github.com/restsharp/RestSharp/commit/be39346784b68048b230790d15333574341143bc'} |
GHSA | GHSA-h6rj-8r3c-9gpj | bson is vulnerable to denial of service due to incorrect regex validation | BSON injection vulnerability in the legal? function in BSON (bson-ruby) gem before 3.0.4 for Ruby allows remote attackers to cause a denial of service (resource consumption) or inject arbitrary data via a crafted string. | {'CVE-2015-4412'} | 2022-04-25T22:35:30Z | 2018-03-05T19:43:21Z | CRITICAL | 9.8 | {'CWE-400'} | {'https://github.com/mongodb/bson-ruby/compare/7446d7c6764dfda8dc4480ce16d5c023e74be5ca...28f34978a85b689a4480b4d343389bf4886522e7', 'https://nvd.nist.gov/vuln/detail/CVE-2015-4412', 'https://sakurity.com/blog/2015/06/04/mongo_ruby_regexp.html', 'http://www.securityfocus.com/bid/75045', 'https://github.com/mongodb/bson-ruby/commit/976da329ff03ecdfca3030eb6efe3c85e6db9999', 'https://bugzilla.redhat.com/show_bug.cgi?id=1229750', 'http://www.openwall.com/lists/oss-security/2015/06/06/3', 'https://github.com/advisories/GHSA-h6rj-8r3c-9gpj'} | null | {'https://github.com/mongodb/bson-ruby/commit/976da329ff03ecdfca3030eb6efe3c85e6db9999'} | {'https://github.com/mongodb/bson-ruby/commit/976da329ff03ecdfca3030eb6efe3c85e6db9999'} |
GHSA | GHSA-3fc5-9x9m-vqc4 | Privilege Escalation in express-cart | Versions of `express-cart` before 1.1.6 are vulnerable to privilege escalation. This vulnerability can be exploited so that normal users can escalate their privilege and add new administrator users.
## Recommendation
Update to version 1.1.6 or later. | null | 2021-08-04T21:25:59Z | 2019-06-03T17:31:32Z | CRITICAL | 9.8 | null | {'https://github.com/mrvautin/expressCart/commit/baccaae9b0b72f00b10c5453ca00231340ad3e3b', 'https://hackerone.com/reports/343626', 'https://github.com/nodejs/security-wg/blob/master/vuln/npm/469.json', 'https://snyk.io/vuln/npm:express-cart:20180712', 'https://github.com/advisories/GHSA-3fc5-9x9m-vqc4', 'https://www.npmjs.com/advisories/730'} | null | {'https://github.com/mrvautin/expressCart/commit/baccaae9b0b72f00b10c5453ca00231340ad3e3b'} | {'https://github.com/mrvautin/expressCart/commit/baccaae9b0b72f00b10c5453ca00231340ad3e3b'} |
GHSA | GHSA-h8hx-2c5r-32cf | Cross-Site Request Forgery (CSRF) in trestle-auth | ### Impact
A vulnerability in trestle-auth versions 0.4.0 and 0.4.1 allows an attacker to create a form that will bypass Rails' built-in CSRF protection when submitted by a victim with a trestle-auth admin session. This potentially allows an attacker to alter protected data, including admin account credentials.
### Patches
The vulnerability has been fixed in trestle-auth 0.4.2 released to RubyGems.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [trestle-auth](https://github.com/TrestleAdmin/trestle-auth/issues)
* Email the maintainer at [sam@sampohlenz.com](mailto:sam@sampohlenz.com) | {'CVE-2021-29435'} | 2022-04-19T19:02:54Z | 2021-04-13T17:01:50Z | HIGH | 8.1 | {'CWE-352'} | {'https://rubygems.org/gems/trestle-auth', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29435', 'https://github.com/advisories/GHSA-h8hx-2c5r-32cf', 'https://github.com/TrestleAdmin/trestle-auth/security/advisories/GHSA-h8hx-2c5r-32cf', 'https://github.com/TrestleAdmin/trestle-auth/commit/cb95b05cdb2609052207af07b4b8dfe3a23c11dc'} | null | {'https://github.com/TrestleAdmin/trestle-auth/commit/cb95b05cdb2609052207af07b4b8dfe3a23c11dc'} | {'https://github.com/TrestleAdmin/trestle-auth/commit/cb95b05cdb2609052207af07b4b8dfe3a23c11dc'} |
GHSA | GHSA-6g6m-m6h5-w9gf | Authorization bypass in express-jwt | ### Overview
Versions before and including 5.3.3, we are not enforcing the **algorithms** entry to be specified in the configuration.
When **algorithms** is not specified in the configuration, with the combination of jwks-rsa, it may lead to authorization bypass.
### Am I affected?
You are affected by this vulnerability if all of the following conditions apply:
You are using express-jwt
AND
You do not have **algorithms** configured in your express-jwt configuration.
AND
You are using libraries such as jwks-rsa as the **secret**.
### How to fix that?
Specify **algorithms** in the express-jwt configuration. The following is an example of a proper configuration
```
const checkJwt = jwt({
secret: jwksRsa.expressJwtSecret({
rateLimit: true,
jwksRequestsPerMinute: 5,
jwksUri: `https://${DOMAIN}/.well-known/jwks.json`
}),
// Validate the audience and the issuer.
audience: process.env.AUDIENCE,
issuer: `https://${DOMAIN}/`,
// restrict allowed algorithms
algorithms: ['RS256']
});
```
### Will this update impact my users?
The fix provided in patch will not affect your users if you specified the algorithms allowed. The patch now makes **algorithms** a required configuration.
### Credit
IST Group | {'CVE-2020-15084'} | 2021-01-07T23:49:23Z | 2020-06-30T16:05:24Z | HIGH | 7.7 | {'CWE-285'} | {'https://github.com/auth0/express-jwt/commit/7ecab5f8f0cab5297c2b863596566eb0c019cdef', 'https://github.com/auth0/express-jwt/security/advisories/GHSA-6g6m-m6h5-w9gf', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15084', 'https://github.com/advisories/GHSA-6g6m-m6h5-w9gf'} | null | {'https://github.com/auth0/express-jwt/commit/7ecab5f8f0cab5297c2b863596566eb0c019cdef'} | {'https://github.com/auth0/express-jwt/commit/7ecab5f8f0cab5297c2b863596566eb0c019cdef'} |
GHSA | GHSA-742w-89gc-8m9c | containerd v1.2.x can be coerced into leaking credentials during image pull | ## Impact
If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format includes a URL for the location of a specific image layer (otherwise known as a “foreign layer”), the default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or later, the default containerd resolver will provide its authentication credentials if the server where the URL is located presents an HTTP 401 status code along with registry-specific HTTP headers.
If an attacker publishes a public image with a manifest that directs one of the layers to be fetched from a web server they control and they trick a user or system into pulling the image, they can obtain the credentials used for pulling that image. In some cases, this may be the user's username and password for the registry. In other cases, this may be the credentials attached to the cloud virtual instance which can grant access to other cloud resources in the account.
The default containerd resolver is used by the cri-containerd plugin (which can be used by Kubernetes), the ctr development tool, and other client programs that have explicitly linked against it.
This vulnerability has been rated by the containerd maintainers as medium, with a CVSS score of 6.1 and a vector string of CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N.
## Patches
This vulnerability has been fixed in containerd 1.2.14. containerd 1.3 and later are not affected.
## Workarounds
If you are using containerd 1.3 or later, you are not affected. If you are using cri-containerd in the 1.2 series or prior, you should ensure you only pull images from trusted sources. Other container runtimes built on top of containerd but not using the default resolver (such as Docker) are not affected.
## Credits
The containerd maintainers would like to thank Brad Geesaman, Josh Larsen, Ian Coldwater, Duffie Cooley, and Rory McCune for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/master/SECURITY.md). | {'CVE-2020-15157'} | 2022-04-19T19:02:37Z | 2022-02-11T23:27:39Z | MODERATE | 6.1 | {'CWE-522'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15157', 'https://github.com/advisories/GHSA-742w-89gc-8m9c', 'https://github.com/containerd/containerd/commit/1ead8d9deb3b175bf40413b8c47b3d19c2262726', 'https://www.debian.org/security/2021/dsa-4865', 'https://usn.ubuntu.com/4589-1/', 'https://github.com/containerd/containerd/security/advisories/GHSA-742w-89gc-8m9c', 'https://usn.ubuntu.com/4589-2/', 'https://github.com/containerd/containerd/releases/tag/v1.2.14', 'https://darkbit.io/blog/cve-2020-15157-containerdrip'} | null | {'https://github.com/containerd/containerd/commit/1ead8d9deb3b175bf40413b8c47b3d19c2262726'} | {'https://github.com/containerd/containerd/commit/1ead8d9deb3b175bf40413b8c47b3d19c2262726'} |
GHSA | GHSA-gm9x-q798-hmr4 | Command Injection in git-tags-remote | All versions of `git-tags-remote ` are vulnerable to Command Injection. The package fails to sanitize the repository input and passes it directly to an `exec` call on the `get` function . This may allow attackers to execute arbitrary code in the system if the `repo` value passed to the function is user-controlled.
The following proof-of-concept creates a file in `/tmp`:
```
const gitTagsRemote = require('git-tags-remote');
gitTagsRemote.get('https://github.com/sh0ji/git-tags-remote.git; echo "Injection Success" > /tmp/command-injection.test')
.then(tags => console.log(tags));
``` | null | 2021-09-23T17:26:33Z | 2020-07-29T14:53:40Z | HIGH | 7.2 | {'CWE-78'} | {'https://github.com/advisories/GHSA-gm9x-q798-hmr4', 'https://github.com/sh0ji/git-tags-remote/issues/58', 'https://github.com/sh0ji/git-tags-remote/commit/a20488960cbd2c98455386108253094897ebfc1c', 'https://www.npmjs.com/advisories/1517'} | null | {'https://github.com/sh0ji/git-tags-remote/commit/a20488960cbd2c98455386108253094897ebfc1c'} | {'https://github.com/sh0ji/git-tags-remote/commit/a20488960cbd2c98455386108253094897ebfc1c'} |
GHSA | GHSA-pmw4-jgxx-pcq9 | File System Bounds Escape | ### Impact
Clients of FTP servers utilizing `ftp-srv` hosted on Windows machines can escape the FTP user's defined root folder using the expected FTP commands, for example, `CWD` and `UPDR`.
### Background
When windows separators exist within the path (`\`), `path.resolve` leaves the upper pointers intact and allows the user to move beyond the root folder defined for that user. We did not take that into account when creating the path resolve function.
### Patches
None at the moment.
### Workarounds
There are no workarounds for windows servers. Hosting the server on a different OS mitigates the issue.
### References
Issues:
https://github.com/autovance/ftp-srv/issues/167
https://github.com/autovance/ftp-srv/issues/225
### For more information
If you have any questions or comments about this advisory:
Open an issue at https://github.com/autovance/ftp-srv.
Please email us directly; security@autovance.com. | {'CVE-2020-26299'} | 2022-04-19T19:02:43Z | 2021-02-10T18:11:34Z | MODERATE | 0 | {'CWE-22'} | {'https://github.com/autovance/ftp-srv/security/advisories/GHSA-pmw4-jgxx-pcq9', 'https://github.com/autovance/ftp-srv/issues/225', 'https://github.com/autovance/ftp-srv/commit/457b859450a37cba10ff3c431eb4aa67771122e3', 'https://github.com/advisories/GHSA-pmw4-jgxx-pcq9', 'https://github.com/autovance/ftp-srv/pull/224', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26299', 'https://www.npmjs.com/package/ftp-srv', 'https://github.com/autovance/ftp-srv/issues/167'} | null | {'https://github.com/autovance/ftp-srv/commit/457b859450a37cba10ff3c431eb4aa67771122e3'} | {'https://github.com/autovance/ftp-srv/commit/457b859450a37cba10ff3c431eb4aa67771122e3'} |
GHSA | GHSA-rfcf-m67m-jcrq | Authentication granted to all firewalls instead of just one | Description
-----------
When an application defines multiple firewalls, the authenticated token delivered by one of the firewalls is available to all other firewalls. This can be abused when the application defines different providers for different parts of an application. In such a situation, a user authenticated on one part of the application is considered authenticated on the whole application.
Resolution
----------
We now ensure that the authenticated token is only available for the firewall that generates it.
The patch for this issue is available [here](https://github.com/symfony/symfony/commit/3084764ad82f29dbb025df19978b9cbc3ab34728) for branch 5.3.
Credits
-------
I would like to thank Bogdan, gndk, Paweł Warchoł, Warxcell, and Adrien Lamotte for reporting the issue and Wouter J for fixing the issue.
| {'CVE-2021-32693'} | 2022-04-19T19:03:00Z | 2021-06-21T17:03:44Z | HIGH | 6.8 | {'CWE-287'} | {'https://github.com/symfony/symfony/security/advisories/GHSA-rfcf-m67m-jcrq', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32693', 'https://symfony.com/blog/cve-2021-32693-authentication-granted-to-all-firewalls-instead-of-just-one', 'https://github.com/advisories/GHSA-rfcf-m67m-jcrq', 'https://github.com/symfony/symfony/commit/3084764ad82f29dbb025df19978b9cbc3ab34728', 'https://github.com/symfony/security-http/commit/6bf4c31219773a558b019ee12e54572174ff8129'} | null | {'https://github.com/symfony/symfony/commit/3084764ad82f29dbb025df19978b9cbc3ab34728', 'https://github.com/symfony/security-http/commit/6bf4c31219773a558b019ee12e54572174ff8129'} | {'https://github.com/symfony/symfony/commit/3084764ad82f29dbb025df19978b9cbc3ab34728', 'https://github.com/symfony/security-http/commit/6bf4c31219773a558b019ee12e54572174ff8129'} |
GHSA | GHSA-qv8q-v995-72gr | 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-09T17:29:38Z | 2020-09-09T17:29:38Z | LOW | 0 | null | {'https://github.com/personnummer/csharp/commit/d7ac9b60a3677cd841a488b4f82ac6930f168699', 'https://www.nuget.org/packages/Personnummer/', 'https://github.com/advisories/GHSA-qv8q-v995-72gr', 'https://github.com/personnummer/csharp/security/advisories/GHSA-qv8q-v995-72gr'} | null | {'https://github.com/personnummer/csharp/commit/d7ac9b60a3677cd841a488b4f82ac6930f168699'} | {'https://github.com/personnummer/csharp/commit/d7ac9b60a3677cd841a488b4f82ac6930f168699'} |
GHSA | GHSA-hcxx-mp6g-6gr9 | Opencast publishes global system account credentials | The issue was mostly mitigated before, drastically reducing the risk. See references below for more information.
### Impact
Opencast before version 10.6 will try to authenticate against any external services listed in a media package when it is trying to access the files, sending the global system user's credentials, regardless of the target being part of the Opencast cluster or not.
Previous mitigations already prevented clear text authentications for such requests (e.g. HTTP Basic authentication), but with enough malicious intent, even hashed credentials can be broken.
### Patches
Opencast 10.6 will now send authentication requests only against servers which are part of the Opencast cluster, preventing external services from getting any form of authentication attempt in the first place.
### Workarounds
No workaround available.
### References
- [Patch fixing the issue](https://github.com/opencast/opencast/commit/776d5588f39c61eb04c03bb955416c4f77629d51)
- [Original security notice](https://groups.google.com/a/opencast.org/g/security-notices/c/XRZzRiqp-NE)
- [Original security mitigation](https://github.com/opencast/opencast/commit/fe8c3d3a60dc5869b468957270dbad5f8c30ead6)
### For more information
If you have any questions or comments about this advisory:
- Open an issue in [our issue tracker](https://github.com/opencast/opencast/issues)
- Email us at [security@opencast.org](mailto:security@opencast.org)
| {'CVE-2018-16153'} | 2022-04-19T19:03:17Z | 2021-12-14T21:43:48Z | LOW | 0 | {'CWE-200', 'CWE-522'} | {'https://github.com/opencast/opencast/security/advisories/GHSA-hcxx-mp6g-6gr9', 'https://github.com/opencast/opencast/commit/776d5588f39c61eb04c03bb955416c4f77629d51', 'https://docs.opencast.org/r/10.x/admin/#changelog/#opencast-106', 'https://github.com/advisories/GHSA-hcxx-mp6g-6gr9'} | null | {'https://github.com/opencast/opencast/commit/776d5588f39c61eb04c03bb955416c4f77629d51'} | {'https://github.com/opencast/opencast/commit/776d5588f39c61eb04c03bb955416c4f77629d51'} |
GHSA | GHSA-gg2g-m5wc-vccq | Rebuild-bot workflow may allow unauthorised repository modifications | ### Impact
`projen` is a project generation tool that synthesizes project configuration files such as `package.json`, `tsconfig.json`, `.gitignore`, GitHub Workflows, `eslint`, `jest`, and more, from a well-typed definition written in JavaScript. Users of projen's `NodeProject` project type (including any project type derived from it) include a `.github/workflows/rebuild-bot.yml` workflow that may allow any GitHub user to trigger execution of un-trusted code in the context of the "main" repository (as opposed to that of a fork). In some situations, such untrusted code may potentially be able to commit to the "main" repository.
The rebuild-bot workflow is triggered by comments including `@projen rebuild` on pull-request to trigger a re-build of the projen project, and updating the pull request with the updated files. This workflow is triggered by an `issue_comment` event, and thus always executes with a `GITHUB_TOKEN` belonging to the repository into which the pull-request is made (this is in contrast with workflows triggered by `pull_request` events, which always execute with a `GITHUB_TOKEN` belonging to the repository from which the pull-request is made).
Repositories that do not have branch protection configured on their default branch (typically `main` or `master`) could possibly allow an untrusted user to gain access to secrets configured on the repository (such as NPM tokens, etc). Branch protection prohibits this escalation, as the managed `GITHUB_TOKEN` would not be able to modify the contents of a protected branch and affected workflows must be defined on the default branch.
### Patches
The issue was mitigated in version `0.16.41` of the `projen` tool, which removes the `issue_comment` trigger from this workflow. Version `0.17.0` of projen completely removes the `rebuild-bot.yml` workflow.
### Workarounds
The recommended way to address the vulnerability is to upgrade `projen`. Users who cannot upgrade `projen` may also remove the `.github/workflows/rebuild-bot.yml` file and add it to their `.gitignore` file (via `projenrc.js`) to mitigate the issue.
### References
The `rebuild-bot.yml` workflow managed by `projen` is only one occurrence of a GitHub Workflows mis-configuration, but it may also be present in other workflows not managed by `projen` (either hand-written, or managed by other tools). For more information on this class of issues, the [Keeping your GitHub Actions and workflows secure: Preventing pwn requests][1] article provides a great overview of the problem.
[1]: https://securitylab.github.com/research/github-actions-preventing-pwn-requests | {'CVE-2021-21423'} | 2021-04-16T22:53:31Z | 2021-04-06T18:36:40Z | HIGH | 9.4 | {'CWE-527'} | {'https://github.com/advisories/GHSA-gg2g-m5wc-vccq', 'https://www.npmjs.com/package/projen', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21423', 'https://github.com/projen/projen/commit/36030c6a4b1acd0054673322612e7c70e9446643', 'https://github.com/projen/projen/security/advisories/GHSA-gg2g-m5wc-vccq'} | null | {'https://github.com/projen/projen/commit/36030c6a4b1acd0054673322612e7c70e9446643'} | {'https://github.com/projen/projen/commit/36030c6a4b1acd0054673322612e7c70e9446643'} |
GHSA | GHSA-j77r-2fxf-5jrw | Improper path handling in kustomization files allows path traversal | The kustomize-controller enables the use of Kustomize’s functionality when applying Kubernetes declarative state onto a cluster. A malicious user can use built-in features and a specially crafted `kustomization.yaml` to expose sensitive data from the controller’s pod filesystem. In multi-tenancy deployments this can lead to privilege escalation if the controller's service account has elevated permissions.
Within the affected versions, users with write access to a Flux source are able to use built-in features to expose sensitive data from the controller’s pod filesystem using a malicious `kustomization.yaml` file.
This vulnerability was fixed in kustomize-controller v0.24.0 and included in flux2 v0.29.0 released on 2022-04-20. The changes introduce a new Kustomize file system implementation which ensures that all files being handled are contained within the Kustomization working directory, blocking references to any files that do not meet that requirement.
Automated tooling (e.g. conftest) could be employed as a workaround, as part of a user's CI/CD pipeline to ensure that their `kustomization.yaml` files conform with specific policies, blocking access to sensitive path locations. | {'CVE-2022-24877'} | 2022-05-05T21:49:52Z | 2022-05-04T18:04:07Z | CRITICAL | 9.9 | {'CWE-22'} | {'https://github.com/fluxcd/kustomize-controller/commit/f4528fb25d611da94e491346bea056d5c5c3611f', 'https://github.com/fluxcd/pkg/commit/0ec014baf417fd3879d366a45503a548b9267d2a', 'https://github.com/fluxcd/flux2/security/advisories/GHSA-j77r-2fxf-5jrw', 'https://github.com/advisories/GHSA-j77r-2fxf-5jrw'} | null | {'https://github.com/fluxcd/kustomize-controller/commit/f4528fb25d611da94e491346bea056d5c5c3611f', 'https://github.com/fluxcd/pkg/commit/0ec014baf417fd3879d366a45503a548b9267d2a'} | {'https://github.com/fluxcd/kustomize-controller/commit/f4528fb25d611da94e491346bea056d5c5c3611f', 'https://github.com/fluxcd/pkg/commit/0ec014baf417fd3879d366a45503a548b9267d2a'} |
GHSA | GHSA-c4w7-xm78-47vh | Prototype Pollution in y18n | ### Overview
The npm package `y18n` before versions 3.2.2, 4.0.1, and 5.0.5 is vulnerable to Prototype Pollution.
### POC
```
const y18n = require('y18n')();
y18n.setLocale('__proto__');
y18n.updateLocale({polluted: true});
console.log(polluted); // true
```
### Recommendation
Upgrade to version 3.2.2, 4.0.1, 5.0.5 or later. | {'CVE-2020-7774'} | 2022-04-20T19:14:19Z | 2021-03-29T16:05:12Z | HIGH | 7.3 | {'CWE-20', 'CWE-915'} | {'https://github.com/advisories/GHSA-c4w7-xm78-47vh', 'https://github.com/yargs/y18n/pull/108', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1038306', 'https://github.com/yargs/y18n/commit/a9ac604abf756dec9687be3843e2c93bfe581f25', 'https://snyk.io/vuln/SNYK-JS-Y18N-1021887', 'https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7774', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://github.com/yargs/y18n/issues/96'} | null | {'https://github.com/yargs/y18n/commit/a9ac604abf756dec9687be3843e2c93bfe581f25'} | {'https://github.com/yargs/y18n/commit/a9ac604abf756dec9687be3843e2c93bfe581f25'} |
GHSA | GHSA-jff3-mwp3-f8cw | Exposure of Sensitive Information to an Unauthorized Actor in Products.GenericSetup | ### Impact
_What kind of vulnerability is it? Who is impacted?_
Information disclosure vulnerability - anonymous visitors may view log and snapshot files generated by the Generic Setup Tool.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
The problem has been fixed in version 2.1.1. Depending on how you have installed Products.GenericSetup, you should change the buildout version pin to 2.1.1 and re-run the buildout, or if you used pip simply do pip install `"Products.GenericSetup>=2.1.1"`
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
Visit the ZMI Security tab at `portal_setup/manage_access` and click on the link _Access contents information_. On the next page, uncheck the box _Also use roles acquired from folders containing this objects_ at the bottom and check the boxes for _Manager_ and _Owner_. Then click on _Save Changes_. Return to the ZMI Security tab at `portal_setup/manage_access` and scroll down to the link _View_. Click on _View_, uncheck the box _Also use roles acquired from folders containing this objects_ at the bottom and check the boxes for _Manager_ and _Owner_. Then click on _Save Changes_.
### References
_Are there any links users can visit to find out more?_
- [GHSA-jff3-mwp3-f8cw](https://github.com/zopefoundation/Products.GenericSetup/security/advisories/GHSA-jff3-mwp3-f8cw)
- [Products.GenericSetup on PyPI](https://pypi.org/project/Products.GenericSetup/)
- [Definition of information disclosure at MITRE](https://cwe.mitre.org/data/definitions/200.html)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [Products.GenericSetup issue tracker](https://github.com/zopefoundation/Products.GenericSetup/issues)
* Email us at [security@plone.org](mailto:security@plone.org) | {'CVE-2021-21360'} | 2022-04-19T19:02:49Z | 2021-03-09T00:38:31Z | LOW | 0 | {'CWE-200'} | {'http://www.openwall.com/lists/oss-security/2021/05/22/1', 'https://pypi.org/project/Products.GenericSetup/', 'https://github.com/zopefoundation/Products.GenericSetup/security/advisories/GHSA-jff3-mwp3-f8cw', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21360', 'https://github.com/zopefoundation/Products.GenericSetup/commit/700319512b3615b3871a1f24e096cf66dc488c57', 'https://github.com/advisories/GHSA-jff3-mwp3-f8cw', 'http://www.openwall.com/lists/oss-security/2021/05/21/1'} | null | {'https://github.com/zopefoundation/Products.GenericSetup/commit/700319512b3615b3871a1f24e096cf66dc488c57'} | {'https://github.com/zopefoundation/Products.GenericSetup/commit/700319512b3615b3871a1f24e096cf66dc488c57'} |
GHSA | GHSA-79qm-h35f-hr77 | OS Command Injection in compile-sass | compile-sass prior to 1.0.5 allows execution of arbritary commands. The function "setupCleanupOnExit(cssPath)" within "dist/index.js" is executed as part of the "rm" command without any sanitization. | {'CVE-2019-10799'} | 2022-01-04T19:50:38Z | 2021-04-13T15:23:13Z | HIGH | 9.8 | {'CWE-78'} | {'https://github.com/advisories/GHSA-79qm-h35f-hr77', 'https://github.com/eiskalteschatten/compile-sass/commit/d9ada7797ff93875b6466dea7a78768e90a0f8d2', 'https://snyk.io/vuln/SNYK-JS-COMPILESASS-551804', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10799', 'https://snyk.io/vuln/SNYK-JS-RPI-548942'} | null | {'https://github.com/eiskalteschatten/compile-sass/commit/d9ada7797ff93875b6466dea7a78768e90a0f8d2'} | {'https://github.com/eiskalteschatten/compile-sass/commit/d9ada7797ff93875b6466dea7a78768e90a0f8d2'} |
GHSA | GHSA-r64m-qchj-hrjp | Webcache Poisoning in shopware/platform and shopware/core | ### Impact
Webcache Poisoning via X-Forwarded-Prefix and sub-request
### Patches
We recommend updating to the current version 6.4.6.1. You can get the update to 6.4.6.1 regularly via the Auto-Updater or directly via the download overview.
https://www.shopware.com/en/download/#shopware-6
Workarounds
For older versions of 6.1, 6.2, and 6.3, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.
https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659
| null | 2021-11-24T20:05:19Z | 2021-11-24T20:05:19Z | CRITICAL | 0 | {'CWE-444'} | {'https://github.com/shopware/platform/commit/9062f15450d183f2c666664841efd4f5ef25e0f3', 'https://github.com/shopware/platform/security/advisories/GHSA-r64m-qchj-hrjp', 'https://github.com/advisories/GHSA-r64m-qchj-hrjp'} | null | {'https://github.com/shopware/platform/commit/9062f15450d183f2c666664841efd4f5ef25e0f3'} | {'https://github.com/shopware/platform/commit/9062f15450d183f2c666664841efd4f5ef25e0f3'} |
GHSA | GHSA-fxp8-7h5w-h235 | XSS in search engine | In the Alkacon OpenCms Apollo Template 10.5.4 and 10.5.5, there is XSS in the search engine. | {'CVE-2019-13234'} | 2021-08-18T22:27:15Z | 2019-11-12T22:58:11Z | MODERATE | 6.1 | {'CWE-79'} | {'https://aetsu.github.io/OpenCms', 'https://github.com/advisories/GHSA-fxp8-7h5w-h235', 'https://github.com/alkacon/apollo-template/commits/branch_10_5_x', 'https://nvd.nist.gov/vuln/detail/CVE-2019-13234', 'http://packetstormsecurity.com/files/154298/Alkacon-OpenCMS-10.5.x-Cross-Site-Scripting.html'} | null | {'https://github.com/alkacon/apollo-template/commits/branch_10_5_x'} | {'https://github.com/alkacon/apollo-template/commits/branch_10_5_x'} |
GHSA | GHSA-crp2-qrr5-8pq7 | containerd CRI plugin: Insecure handling of image volumes | ### Impact
A bug was found in containerd where containers launched through containerd’s CRI implementation with a specially-crafted image configuration could gain access to read-only copies of arbitrary files and directories on the host. This may bypass any policy-based enforcement on container setup (including a Kubernetes Pod Security Policy) and expose potentially sensitive information. Kubernetes and crictl can both be configured to use containerd’s CRI implementation.
### Patches
This bug has been fixed in containerd 1.6.1, 1.5.10 and 1.4.13. Users should update to these versions to resolve the issue.
### Workarounds
Ensure that only trusted images are used.
### Credits
The containerd project would like to thank Felix Wilhelm of Google Project Zero for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/main/SECURITY.md).
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [containerd](https://github.com/containerd/containerd/issues/new/choose)
* Email us at [security@containerd.io](mailto:security@containerd.io) | {'CVE-2022-23648'} | 2022-03-29T19:11:09Z | 2022-03-02T21:33:17Z | HIGH | 7.5 | {'CWE-200'} | {'https://github.com/containerd/containerd/releases/tag/v1.4.13', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AUDQUQBZJGBWJPMRVB6QCCCRF7O3O4PA/', 'https://github.com/containerd/containerd/commit/10f428dac7cec44c864e1b830a4623af27a9fc70', 'https://github.com/advisories/GHSA-crp2-qrr5-8pq7', 'https://github.com/containerd/containerd/releases/tag/v1.5.10', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HFTS2EF3S7HNYSNZSEJZIJHPRU7OPUV3/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23648', 'https://github.com/containerd/containerd/security/advisories/GHSA-crp2-qrr5-8pq7', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OCCARJ6FU4MWBTXHZNMS7NELPDBIX2VO/', 'https://www.debian.org/security/2022/dsa-5091', 'http://packetstormsecurity.com/files/166421/containerd-Image-Volume-Insecure-Handling.html', 'https://github.com/containerd/containerd/releases/tag/v1.6.1'} | null | {'https://github.com/containerd/containerd/commit/10f428dac7cec44c864e1b830a4623af27a9fc70'} | {'https://github.com/containerd/containerd/commit/10f428dac7cec44c864e1b830a4623af27a9fc70'} |
GHSA | GHSA-m57p-p67h-mq74 | Command Injection Vulnerability in systeminformation | ### Impact
command injection vulnerability
### Patches
Problem was fixed with a shell string sanitation fix. Please upgrade to version >= 4.31.1
### Workarounds
If you cannot upgrade, be sure to check or sanitize service parameter strings that are passed to si.inetLatency()
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [systeminformation](https://github.com/sebhildebrandt/systeminformation/issues/new?template=bug_report.md) | {'CVE-2020-26274'} | 2020-12-17T01:41:17Z | 2020-12-16T19:25:00Z | MODERATE | 6.4 | {'CWE-78'} | {'https://www.npmjs.com/advisories/1590', 'https://www.npmjs.com/package/systeminformation', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26274', 'https://github.com/sebhildebrandt/systeminformation/commit/1faadcbf68f1b1fdd5eb2054f68fc932be32ac99', 'https://github.com/advisories/GHSA-m57p-p67h-mq74', 'https://github.com/sebhildebrandt/systeminformation/security/advisories/GHSA-m57p-p67h-mq74'} | null | {'https://github.com/sebhildebrandt/systeminformation/commit/1faadcbf68f1b1fdd5eb2054f68fc932be32ac99'} | {'https://github.com/sebhildebrandt/systeminformation/commit/1faadcbf68f1b1fdd5eb2054f68fc932be32ac99'} |
GHSA | GHSA-rp65-9cf3-cjxr | Inefficient Regular Expression Complexity in nth-check | nth-check is vulnerable to Inefficient Regular Expression Complexity | {'CVE-2021-3803'} | 2021-09-20T20:47:31Z | 2021-09-20T20:47:31Z | MODERATE | 7.5 | {'CWE-1333'} | {'https://github.com/advisories/GHSA-rp65-9cf3-cjxr', 'https://github.com/fb55/nth-check/commit/9894c1d2010870c351f66c6f6efcf656e26bb726', 'https://huntr.dev/bounties/8cf8cc06-d2cf-4b4e-b42c-99fafb0b04d0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3803'} | null | {'https://github.com/fb55/nth-check/commit/9894c1d2010870c351f66c6f6efcf656e26bb726'} | {'https://github.com/fb55/nth-check/commit/9894c1d2010870c351f66c6f6efcf656e26bb726'} |
GHSA | GHSA-c4rh-4376-gff4 | Improper certificate management in AWS IoT Device SDK v2 | The AWS IoT Device SDK v2 for Java, Python, C++ and Node.js appends a user supplied Certificate Authority (CA) to the root CAs instead of overriding it on Unix systems. TLS handshakes will thus succeed if the peer can be verified either from the user-supplied CA or the system’s default trust-store. Attackers with access to a host’s trust stores or are able to compromise a certificate authority already in the host's trust store (note: the attacker must also be able to spoof DNS in this case) may be able to use this issue to bypass CA pinning. An attacker could then spoof the MQTT broker, and either drop traffic and/or respond with the attacker's data, but they would not be able to forward this data on to the MQTT broker because the attacker would still need the user's private keys to authenticate against the MQTT broker. The 'aws_tls_ctx_options_override_default_trust_store_*' function within the aws-c-io submodule has been updated to override the default trust store. This corrects this issue. This issue affects: Amazon Web Services AWS IoT Device SDK v2 for Java versions prior to 1.5.0 on Linux/Unix. Amazon Web Services AWS IoT Device SDK v2 for Python versions prior to 1.6.1 on Linux/Unix. Amazon Web Services AWS IoT Device SDK v2 for C++ versions prior to 1.12.7 on Linux/Unix. Amazon Web Services AWS IoT Device SDK v2 for Node.js versions prior to 1.5.3 on Linux/Unix. Amazon Web Services AWS-C-IO 0.10.4 on Linux/Unix. | {'CVE-2021-40830'} | 2021-12-03T15:22:05Z | 2021-11-24T21:12:04Z | MODERATE | 6.3 | {'CWE-295'} | {'https://github.com/aws/aws-iot-device-sdk-python-v2/commit/0450ce68add7e3d05c6d781ecdac953c299c053a', 'https://nvd.nist.gov/vuln/detail/CVE-2021-40830', 'https://github.com/advisories/GHSA-c4rh-4376-gff4', 'https://github.com/aws/aws-iot-device-sdk-java-v2/commit/67950ad2a02f2f9355c310b69dc9226b017f32f2', 'https://github.com/awslabs/aws-c-io/', 'https://github.com/aws/aws-iot-device-sdk-cpp-v2', 'https://github.com/aws/aws-iot-device-sdk-js-v2/commit/53a36e3ac203291494120604d416b6de59177cac', 'https://github.com/aws/aws-iot-device-sdk-java-v2', 'https://github.com/aws/aws-iot-device-sdk-js-v2', 'https://github.com/aws/aws-iot-device-sdk-python-v2'} | null | {'https://github.com/aws/aws-iot-device-sdk-java-v2/commit/67950ad2a02f2f9355c310b69dc9226b017f32f2', 'https://github.com/aws/aws-iot-device-sdk-js-v2/commit/53a36e3ac203291494120604d416b6de59177cac', 'https://github.com/aws/aws-iot-device-sdk-python-v2/commit/0450ce68add7e3d05c6d781ecdac953c299c053a'} | {'https://github.com/aws/aws-iot-device-sdk-java-v2/commit/67950ad2a02f2f9355c310b69dc9226b017f32f2', 'https://github.com/aws/aws-iot-device-sdk-python-v2/commit/0450ce68add7e3d05c6d781ecdac953c299c053a', 'https://github.com/aws/aws-iot-device-sdk-js-v2/commit/53a36e3ac203291494120604d416b6de59177cac'} |
GHSA | GHSA-w542-cpp9-r3g7 | CSRF in Field Test | The Field Test dashboard is vulnerable to cross-site request forgery (CSRF) with non-session based authentication methods in versions v0.2.0 through v0.3.2.
## Impact
The Field Test dashboard is vulnerable to CSRF with non-session based authentication methods, like basic authentication. Session-based authentication methods (like Devise's default authentication) are not affected.
A CSRF attack works by getting an authorized user to visit a malicious website and then performing requests on behalf of the user. In this instance, a single endpoint is affected, which allows for changing the variant assigned to a user.
All users running an affected release should upgrade immediately.
## Technical Details
Field Test uses the `protect_from_forgery` method from Rails to prevent CSRF. However, this defaults to `:null_session`, which has no effect on non-session based authentication methods. This has been changed to `protect_from_forgery with: :exception`. | {'CVE-2020-16252'} | 2022-04-19T19:03:24Z | 2020-08-05T14:53:34Z | MODERATE | 4.3 | {'CWE-352'} | {'https://github.com/advisories/GHSA-w542-cpp9-r3g7', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/field_test/CVE-2020-16252.yml', 'https://nvd.nist.gov/vuln/detail/CVE-2020-16252', 'https://github.com/ankane/field_test/issues/28', 'https://github.com/ankane/field_test/commit/defd3fdf457c22d7dc5b3be7048481947bd5f0d0', 'https://rubygems.org/gems/field_test'} | null | {'https://github.com/ankane/field_test/commit/defd3fdf457c22d7dc5b3be7048481947bd5f0d0'} | {'https://github.com/ankane/field_test/commit/defd3fdf457c22d7dc5b3be7048481947bd5f0d0'} |
GHSA | GHSA-5mcr-gq6c-3hq2 | Local Information Disclosure Vulnerability in Netty on Unix-Like systems | ### Impact
When netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled.
The CVSSv3.1 score of this vulnerability is calculated to be a [6.2/10](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N&version=3.1)
### Vulnerability Details
On unix-like systems, the temporary directory is shared between all user. As such, writing to this directory using APIs that do not explicitly set the file/directory permissions can lead to information disclosure. Of note, this does not impact modern MacOS Operating Systems.
The method `File.createTempFile` on unix-like systems creates a random file, but, by default will create this file with the permissions `-rw-r--r--`. Thus, if sensitive information is written to this file, other local users can read this information.
This is the case in netty's `AbstractDiskHttpData` is vulnerable.
https://github.com/netty/netty/blob/e5951d46fc89db507ba7d2968d2ede26378f0b04/codec-http/src/main/java/io/netty/handler/codec/http/multipart/AbstractDiskHttpData.java#L80-L101
`AbstractDiskHttpData` is used as a part of the `DefaultHttpDataFactory` class which is used by `HttpPostRequestDecoder` / `HttpPostMultiPartRequestDecoder`.
You may be affected by this vulnerability your project contains the following code patterns:
```java
channelPipeline.addLast(new HttpPostRequestDecoder(...));
```
```java
channelPipeline.addLast(new HttpPostMultiPartRequestDecoder(...));
```
### Patches
This has been patched in version `4.1.59.Final`.
### Workarounds
Specify your own `java.io.tmpdir` when you start the JVM or use `DefaultHttpDataFactory.setBaseDir(...)` to set the directory to something that is only readable by the current user.
### References
- [CWE-378: Creation of Temporary File With Insecure Permissions](https://cwe.mitre.org/data/definitions/378.html)
- [CWE-379: Creation of Temporary File in Directory with Insecure Permissions](https://cwe.mitre.org/data/definitions/379.html)
### Similar Vulnerabilities
Similar, but not the same.
- JUnit 4 - https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp
- Google Guava - https://github.com/google/guava/issues/4011
- Apache Ant - https://nvd.nist.gov/vuln/detail/CVE-2020-1945
- JetBrains Kotlin Compiler - https://nvd.nist.gov/vuln/detail/CVE-2020-15824
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [netty](https://github.com/netty/netty)
* Email us [here](mailto:netty-security@googlegroups.com)
### Original Report
> Hi Netty Security Team,
>
> I've been working on some security research leveraging custom CodeQL queries to detect local information disclosure vulnerabilities in java applications. This was the result from running this query against the netty project:
> https://lgtm.com/query/7723301787255288599/
>
> Netty contains three local information disclosure vulnerabilities, so far as I can tell.
>
> One is here, where the private key for the certificate is written to a temporary file.
>
> https://github.com/netty/netty/blob/e5951d46fc89db507ba7d2968d2ede26378f0b04/handler/src/main/java/io/netty/handler/ssl/util/SelfSignedCertificate.java#L316-L346
>
> One is here, where the certificate is written to a temporary file.
>
> https://github.com/netty/netty/blob/e5951d46fc89db507ba7d2968d2ede26378f0b04/handler/src/main/java/io/netty/handler/ssl/util/SelfSignedCertificate.java#L348-L371
>
> The final one is here, where the 'AbstractDiskHttpData' creates a temporary file if the getBaseDirectory() method returns null. I believe that 'AbstractDiskHttpData' is used as a part of the file upload support? If this is the case, any files uploaded would be similarly vulnerable.
>
> https://github.com/netty/netty/blob/e5951d46fc89db507ba7d2968d2ede26378f0b04/codec-http/src/main/java/io/netty/handler/codec/http/multipart/AbstractDiskHttpData.java#L91
>
> All of these vulnerabilities exist because `File.createTempFile(String, String)` will create a temporary file in the system temporary directory if the 'java.io.tmpdir' system property is not explicitly set. It is my understanding that when java creates a file, by default, and using this method, the permissions on that file utilize the umask. In a majority of cases, this means that the file that java creates has the permissions: `-rw-r--r--`, thus, any other local user on that system can read the contents of that file.
>
> Impacted OS:
> - Any OS where the system temporary directory is shared between multiple users. This is not the case for MacOS or Windows.
>
> Mitigation.
>
> Moving to the `Files` API instead will fix this vulnerability.
> https://docs.oracle.com/javase/8/docs/api/java/nio/file/Files.html#createTempFile-java.nio.file.Path-java.lang.String-java.lang.String-java.nio.file.attribute.FileAttribute...-
>
> This API will explicitly set the posix file permissions to something safe, by default.
>
> I recently disclosed a similar vulnerability in JUnit 4:
> https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp
>
> If you're also curious, this vulnerability in Jetty was also mine, also involving temporary directories, but is not the same vulnerability as in this case.
> https://github.com/eclipse/jetty.project/security/advisories/GHSA-g3wg-6mcf-8jj6
>
> I would appreciate it if we could perform disclosure of this vulnerability leveraging the GitHub security advisories feature here. GitHub has a nice credit system that I appreciate, plus the disclosures, as you can see from the sampling above, end up looking very nice.
> https://github.com/netty/netty/security/advisories
>
> This vulnerability disclosure follows Google's [90-day vulnerability disclosure policy](https://www.google.com/about/appsecurity/) (I'm not an employee of Google, I just like their policy). Full disclosure will occur either at the end of the 90-day deadline or whenever a patch is made widely available, whichever occurs first.
>
> Cheers,
> Jonathan Leitschuh | {'CVE-2021-21290'} | 2022-04-22T18:18:15Z | 2021-02-08T21:17:48Z | MODERATE | 6.2 | {'CWE-379', 'CWE-668', 'CWE-378'} | {'https://github.com/netty/netty/security/advisories/GHSA-5mcr-gq6c-3hq2', 'https://lists.apache.org/thread.html/r4efed2c501681cb2e8d629da16e48d9eac429624fd4c9a8c6b8e7020@%3Cdev.tinkerpop.apache.org%3E', 'https://lists.apache.org/thread.html/ra0fc2b4553dd7aaf75febb61052b7f1243ac3a180a71c01f29093013@%3Cjira.kafka.apache.org%3E', 'https://lists.apache.org/thread.html/r2936730ef0a06e724b96539bc7eacfcd3628987c16b1b99c790e7b87@%3Cissues.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/r2fda4dab73097051977f2ab818f75e04fbcb15bb1003c8530eac1059@%3Cjira.kafka.apache.org%3E', 'https://lists.apache.org/thread.html/r5e66e286afb5506cdfe9bbf68a323e8d09614f6d1ddc806ed0224700@%3Cjira.kafka.apache.org%3E', 'https://lists.apache.org/thread.html/r02e467123d45006a1dda20a38349e9c74c3a4b53e2e07be0939ecb3f@%3Cdev.ranger.apache.org%3E', 'https://lists.apache.org/thread.html/r9924ef9357537722b28d04c98a189750b80694a19754e5057c34ca48@%3Ccommits.pulsar.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://lists.apache.org/thread.html/rdba4f78ac55f803893a1a2265181595e79e3aa027e2e651dfba98c18@%3Cjira.kafka.apache.org%3E', 'https://lists.apache.org/thread.html/rc0087125cb15b4b78e44000f841cd37fefedfda942fd7ddf3ad1b528@%3Cissues.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/rc488f80094872ad925f0c73d283d4c00d32def81977438e27a3dc2bb@%3Cjira.kafka.apache.org%3E', 'https://lists.apache.org/thread.html/r59bac5c09f7a4179b9e2460e8f41c278aaf3b9a21cc23678eb893e41@%3Cjira.kafka.apache.org%3E', 'https://lists.apache.org/thread.html/r5e4a540089760c8ecc2c411309d74264f1dad634ad93ad583ca16214@%3Ccommits.kafka.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://lists.apache.org/thread.html/r5c701840aa2845191721e39821445e1e8c59711e71942b7796a6ec29@%3Cusers.activemq.apache.org%3E', 'https://www.debian.org/security/2021/dsa-4885', 'https://lists.apache.org/thread.html/ra503756ced78fdc2136bd33e87cb7553028645b261b1f5c6186a121e@%3Cjira.kafka.apache.org%3E', 'https://lists.apache.org/thread.html/rcd163e421273e8dca1c71ea298dce3dd11b41d51c3a812e0394e6a5d@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/r5bf303d7c04da78f276765da08559fdc62420f1df539b277ca31f63b@%3Cissues.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/r1908a34b9cc7120e5c19968a116ddbcffea5e9deb76c2be4fa461904@%3Cdev.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/r10308b625e49d4e9491d7e079606ca0df2f0a4d828f1ad1da64ba47b@%3Cjira.kafka.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2021/02/msg00016.html', 'https://lists.apache.org/thread.html/r0857b613604c696bf9743f0af047360baaded48b1c75cf6945a083c5@%3Cjira.kafka.apache.org%3E', 'https://lists.apache.org/thread.html/rb06c1e766aa45ee422e8261a8249b561784186483e8f742ea627bda4@%3Cdev.kafka.apache.org%3E', 'https://lists.apache.org/thread.html/r7bb3cdc192e9a6f863d3ea05422f09fa1ae2b88d4663e63696ee7ef5@%3Cdev.ranger.apache.org%3E', 'https://lists.apache.org/thread.html/r584cf871f188c406d8bd447ff4e2fd9817fca862436c064d0951a071@%3Ccommits.pulsar.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://lists.apache.org/thread.html/rb592033a2462548d061a83ac9449c5ff66098751748fcd1e2d008233@%3Cissues.zookeeper.apache.org%3E', 'https://lists.apache.org/thread.html/r0053443ce19ff125981559f8c51cf66e3ab4350f47812b8cf0733a05@%3Cdev.kafka.apache.org%3E', 'https://github.com/netty/netty/commit/c735357bf29d07856ad171c6611a2e1a0e0000ec', 'https://lists.apache.org/thread.html/r790c2926efcd062067eb18fde2486527596d7275381cfaff2f7b3890@%3Cissues.bookkeeper.apache.org%3E', 'https://lists.apache.org/thread.html/rb51d6202ff1a773f96eaa694b7da4ad3f44922c40b3d4e1a19c2f325@%3Ccommits.pulsar.apache.org%3E', 'https://github.com/advisories/GHSA-5mcr-gq6c-3hq2', 'https://lists.apache.org/thread.html/r326ec431f06eab7cb7113a7a338e59731b8d556d05258457f12bac1b@%3Cdev.kafka.apache.org%3E', 'https://lists.apache.org/thread.html/r2748097ea4b774292539cf3de6e3b267fc7a88d6c8ec40f4e2e87bd4@%3Cdev.kafka.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21290', 'https://lists.apache.org/thread.html/r743149dcc8db1de473e6bff0b3ddf10140a7357bc2add75f7d1fbb12@%3Cdev.zookeeper.apache.org%3E', 'https://security.netapp.com/advisory/ntap-20220210-0011/', 'https://lists.apache.org/thread.html/r71dbb66747ff537640bb91eb0b2b24edef21ac07728097016f58b01f@%3Ccommits.kafka.apache.org%3E', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/netty/netty/commit/c735357bf29d07856ad171c6611a2e1a0e0000ec'} | {'https://github.com/netty/netty/commit/c735357bf29d07856ad171c6611a2e1a0e0000ec'} |
GHSA | GHSA-ccgm-3xw4-h5p8 | Improper Restriction of XML External Entity Reference in pikepdf | models/metadata.py in the pikepdf package 1.3.0 through 2.9.2 for Python allows XXE when parsing XMP metadata entries. | {'CVE-2021-29421'} | 2021-09-29T18:44:06Z | 2021-04-20T16:30:03Z | HIGH | 7.5 | {'CWE-611'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3QFLBBYGEDNXJ7FS6PIWTVI4T4BUPGEQ/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29421', 'https://github.com/advisories/GHSA-ccgm-3xw4-h5p8', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/36P4HTLBJPO524WMQWW57N3QRF4RFSJG/', 'https://github.com/pikepdf/pikepdf/commit/3f38f73218e5e782fe411ccbb3b44a793c0b343a'} | null | {'https://github.com/pikepdf/pikepdf/commit/3f38f73218e5e782fe411ccbb3b44a793c0b343a'} | {'https://github.com/pikepdf/pikepdf/commit/3f38f73218e5e782fe411ccbb3b44a793c0b343a'} |
GHSA | GHSA-95hx-62rh-gg96 | Potential XSS injection In PrestaShop contactform | ### Impact
An attacker is able to inject javascript while using the contact form.
### Patches
The problem is fixed in v4.3.0
### References
[Cross-site Scripting (XSS) - Stored (CWE-79)](https://cwe.mitre.org/data/definitions/79.html) | {'CVE-2020-15178'} | 2021-01-07T22:56:43Z | 2020-09-15T17:34:17Z | HIGH | 8 | {'CWE-79'} | {'https://github.com/PrestaShop/contactform/security/advisories/GHSA-95hx-62rh-gg96', 'https://packagist.org/packages/prestashop/contactform', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15178', 'https://github.com/advisories/GHSA-95hx-62rh-gg96', 'https://github.com/PrestaShop/contactform/commit/ecd9f5d14920ec00885766a7cb41bcc5ed8bfa09'} | null | {'https://github.com/PrestaShop/contactform/commit/ecd9f5d14920ec00885766a7cb41bcc5ed8bfa09'} | {'https://github.com/PrestaShop/contactform/commit/ecd9f5d14920ec00885766a7cb41bcc5ed8bfa09'} |
GHSA | GHSA-4rhm-m2fp-hx7q | Potential CSV Injection vector in OctoberCMS | ### Impact
Any users with the ability to modify any data that could eventually be exported as a CSV file from the `ImportExportController` could potentially introduce a CSV injection into the data to cause the generated CSV export file to be malicious. This requires attackers to achieve the following before a successful attack can be completed:
1. Have found a vulnerability in the victim's spreadsheet software of choice.
2. Control data that would potentially be exported through the `ImportExportController` by a theoretical victim.
3. Convince the victim to export above data as a CSV and run it in vulnerable spreadsheet software while also bypassing any sanity checks by said software.
### Patches
Issue has been patched in Build 466 (v1.0.466).
### Workarounds
Apply https://github.com/octobercms/library/commit/c84bf03f506052c848f2fddc05f24be631427a1a & https://github.com/octobercms/october/commit/802d8c8e09a2b342649393edb6d3ceb958851484 to your installation manually if unable to upgrade to Build 466.
### References
Reported by @chrisvidal initially & [Sivanesh Ashok](https://stazot.com/) later.
### For more information
If you have any questions or comments about this advisory:
* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)
### Threat assessment:
Given the number of hoops that a potential attacker would have to jump through, this vulnerability really boils down to the possibility of abusing the trust that a user may have in the export functionality of the project. Thus, this has been rated low severity as it requires vulnerabilities to also exist in other software used by any potential victims as well as successful social engineering attacks. | {'CVE-2020-5299'} | 2022-04-19T19:02:26Z | 2020-06-03T21:58:35Z | MODERATE | 4 | {'CWE-77'} | {'https://github.com/octobercms/library/commit/c84bf03f506052c848f2fddc05f24be631427a1a', 'https://github.com/octobercms/october/commit/802d8c8e09a2b342649393edb6d3ceb958851484', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5299', 'https://github.com/advisories/GHSA-4rhm-m2fp-hx7q', 'http://packetstormsecurity.com/files/158730/October-CMS-Build-465-XSS-File-Read-File-Deletion-CSV-Injection.html', 'https://github.com/octobercms/october/security/advisories/GHSA-4rhm-m2fp-hx7q', 'http://seclists.org/fulldisclosure/2020/Aug/2'} | null | {'https://github.com/octobercms/october/commit/802d8c8e09a2b342649393edb6d3ceb958851484', 'https://github.com/octobercms/library/commit/c84bf03f506052c848f2fddc05f24be631427a1a'} | {'https://github.com/octobercms/library/commit/c84bf03f506052c848f2fddc05f24be631427a1a', 'https://github.com/octobercms/october/commit/802d8c8e09a2b342649393edb6d3ceb958851484'} |
GHSA | GHSA-2j6v-xpf3-xvrv | Use of Externally-Controlled Format String in wire-avs | ### Impact
A remote format string vulnerability allowed an attacker to cause a denial of service or possibly execute arbitrary code.
### Patches
* The issue has been fixed in wire-avs 7.1.12 and is already included on all Wire products (currently used version is 8.0.x)
### Workarounds
* No workaround known
### References
* Fixed in commit https://github.com/wireapp/wire-avs/commit/40d373ede795443ae6f2f756e9fb1f4f4ae90bbe
### For more information
If you have any questions or comments about this advisory feel free to email us at [vulnerability-report@wire.com](mailto:vulnerability-report@wire.com)
| {'CVE-2021-41193'} | 2022-03-10T15:59:42Z | 2022-03-01T18:58:23Z | HIGH | 9.8 | {'CWE-134'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-41193', 'https://github.com/wireapp/wire-avs/commit/40d373ede795443ae6f2f756e9fb1f4f4ae90bbe', 'https://github.com/advisories/GHSA-2j6v-xpf3-xvrv', 'https://github.com/wireapp/wire-avs/security/advisories/GHSA-2j6v-xpf3-xvrv'} | null | {'https://github.com/wireapp/wire-avs/commit/40d373ede795443ae6f2f756e9fb1f4f4ae90bbe'} | {'https://github.com/wireapp/wire-avs/commit/40d373ede795443ae6f2f756e9fb1f4f4ae90bbe'} |
GHSA | GHSA-q3gh-5r98-j4h3 | RSA-PSS signature validation vulnerability by prepending zeros in jsrsasign | ### Impact
Jsrsasign can verify RSA-PSS signature which value can expressed as BigInteger. When there is a valid RSA-PSS signature value, this vulnerability is also accept value with prepending zeros as a valid signature.
- If you are not use RSA-PSS signature validation, this vulnerability is not affected.
- Risk to accept a forged or crafted message to be signed is low.
- Risk to raise memory corruption is low since jsrsasign uses BigInteger class.
### Patches
Users using RSA-PSS signature validation should upgrade to 8.0.17.
### Workarounds
Reject RSA-PSS signatures with unnecessary prepending zeros.
### References
https://github.com/kjur/jsrsasign/security/advisories/GHSA-q3gh-5r98-j4h3
[https://github.com/kjur/jsrsasign/issues/438](https://github.com/kjur/jsrsasign/issues/438)
https://nvd.nist.gov/vuln/detail/CVE-2020-14968
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14968
https://vuldb.com/?id.157125
https://kjur.github.io/jsrsasign/api/symbols/RSAKey.html#.verifyWithMessageHashPSS
| {'CVE-2020-14968'} | 2021-10-06T21:44:42Z | 2020-06-26T16:26:50Z | CRITICAL | 9.8 | {'CWE-119'} | {'https://github.com/kjur/jsrsasign/releases/tag/8.0.17', 'https://nvd.nist.gov/vuln/detail/CVE-2020-14968', 'https://github.com/advisories/GHSA-q3gh-5r98-j4h3', 'https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14968', 'https://security.netapp.com/advisory/ntap-20200724-0001/', 'https://www.npmjs.com/package/jsrsasign', 'https://github.com/kjur/jsrsasign/commit/3bcc088c727658d7235854cd2a409a904cc2ce99', 'https://vuldb.com/?id.157125', 'https://github.com/kjur/jsrsasign/releases/tag/8.0.18', 'https://kjur.github.io/jsrsasign/api/symbols/RSAKey.html#.verifyWithMessageHashPSS', 'https://github.com/kjur/jsrsasign/security/advisories/GHSA-q3gh-5r98-j4h3', 'https://github.com/kjur/jsrsasign/issues/438', 'https://www.npmjs.com/advisories/1541', 'https://kjur.github.io/jsrsasign/'} | null | {'https://github.com/kjur/jsrsasign/commit/3bcc088c727658d7235854cd2a409a904cc2ce99'} | {'https://github.com/kjur/jsrsasign/commit/3bcc088c727658d7235854cd2a409a904cc2ce99'} |
GHSA | GHSA-42qm-c3cf-9wv2 | Code injection in dolibarr/dolibarr | Improper php function sanitization, lead to an ability to inject arbitrary PHP code and run arbitrary commands on file system. In the function "dol_eval" in file "dolibarr/htdocs/core/lib/functions.lib.php" dangerous PHP functions are sanitized using "str_replace" and can be bypassed using following code in $s parameter | {'CVE-2022-0819'} | 2022-03-10T15:55:04Z | 2022-03-03T00:00:49Z | HIGH | 8.8 | {'CWE-94'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0819', 'https://huntr.dev/bounties/b03d4415-d4f9-48c8-9ae2-d3aa248027b5', 'https://github.com/advisories/GHSA-42qm-c3cf-9wv2', 'https://github.com/dolibarr/dolibarr/commit/2a48dd349e7de0d4a38e448b0d2ecbe25e968075'} | null | {'https://github.com/dolibarr/dolibarr/commit/2a48dd349e7de0d4a38e448b0d2ecbe25e968075'} | {'https://github.com/dolibarr/dolibarr/commit/2a48dd349e7de0d4a38e448b0d2ecbe25e968075'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.