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-8r7q-r9mx-35rh | Mishandling of format strings in rusqlite | An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated because rusqlite::trace::log mishandles format strings. | {'CVE-2020-35869'} | 2021-08-25T20:47:18Z | 2021-08-25T20:47:18Z | CRITICAL | 9.8 | {'CWE-134'} | {'https://github.com/rusqlite/rusqlite/releases/tag/0.23.0', 'https://github.com/rusqlite/rusqlite/commit/2327d3b774927fdf48903c0bdc1ca7ec93c7c8d0', 'https://rustsec.org/advisories/RUSTSEC-2020-0014.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35869', 'https://github.com/advisories/GHSA-8r7q-r9mx-35rh'} | null | {'https://github.com/rusqlite/rusqlite/commit/2327d3b774927fdf48903c0bdc1ca7ec93c7c8d0'} | {'https://github.com/rusqlite/rusqlite/commit/2327d3b774927fdf48903c0bdc1ca7ec93c7c8d0'} |
GHSA | GHSA-cqcc-mm6x-vmvw | Persistent Cross-site Scripting vulnerability in PrivateBin | In PrivateBin < v1.4.0 a cross-site scripting (XSS) vulnerability was found. The vulnerability is present since attachments with image preview got introduced in v0.21 of the project, which was at the time still called ZeroBin. The issue is caused by the fact that SVGs can contain JavaScript. This can allow an attacker to execute code, if the user opens a paste with a specifically crafted SVG attachment, and interacts with the preview image and the instance isn't protected by an appropriate content security policy.
As a consequence, we have mitigated the vulnerability in the preview and urge server administrators to either **upgrade** to a version with the fix or to ensure the content security policy of their instance is set correctly, ideally both. Additionally, we expanded our [directory listing tool with a checking mechanism](https://privatebin.info/directory/check) and **highly suggest server administrators to check their instance there** and, should there be a warning regarding the content security policy **adjust the CSP to our suggested one**, as it is shown in the configuration preset.
## Proof of concept
The vulnerability can be triggered as following:
1. Create the following SVG as a file:
```svg
<?xml version="1.0" standalone="no"?>
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg version="1.1" baseProfile="full" xmlns="http://www.w3.org/2000/svg">
<polygon id="triangle" points="0,0 0,50 50,0" fill="#009900" stroke="#004400"/>
<script type="text/javascript">
alert(document.domain);
</script>
</svg>
```
2. Upload it as an attachment to a PrivateBin instance that has attachments enabled and hasn't set the recommended content security policy (in particular, one that has either no content security policy set or that allows `*` or `blob:` as a `script-src`).
3. Open the paste. (In a real attack scenario this would be done by the victim.)
4. The SVG is rendered safely as a preview, and script isn't yet executed.
5. Now (depending on your device) right-click or long tap on the image and open it in a new tab.
6. Now a `blob:` URI opens in a new tab with the image and the modal is shown, therefore the script got executed.
## Impact
We tried to reproduce the vulnerability and in our assessment, we found out the following:
1. Any users who use our recommended _Content Security Policy_ (CSP), even older, less strict ones, are **not affected** by this vulnerability, if a [CSP compatible browser](https://caniuse.com/contentsecuritypolicy) is used. All the browsers we tested with did pass on the CSP to the new tab that is opened when viewing the SVG by itself.
As PrivateBin ships with a [built-in CSP](https://github.com/PrivateBin/PrivateBin/wiki/Configuration#cspheader), we consider this a strong defence in depth against these and related issues. That said, we think the CSP should only be the last layer of defence and as such, we decided to still apply further mitigations for this security issue.
2. Instances that do not have attachments enabled, are not affected. Even when attachments are uploaded using a third-party client, they can't be rendered when the administrator disables them (the HTML element that they would render in isn't present and before 1.4 this caused an error, we now catch the error and only display the paste text) and thus potential exploits in the attachment file do not apply.
3. The inline preview (step 4 above) does _not_ execute the script, because [browsers explicitly restrict SVGs if the they are is embedded in an `img` tag](https://developer.mozilla.org/en-US/docs/Web/SVG/SVG_as_an_Image#restrictions) to prevent such security issues in images. Thus, [SVGs in `img` tags itself can be considered safe](https://www.w3.org/TR/CSP2/#which-policy-applies).
However, when the user opens the SVG in a new tab, this browser security feature is circumvented. That's why the exploit steps above explain to open the SVG in a new tab. That being said, the impact of the vulnerability is reduced by two factors:
1. The attack explicitly requires **user-interaction**, i.e. the user has to be tricked into opening the preview in a new tab for some reason. This could realistically be achieved with some social engineering: The markdown formatted text part of the paste could include such an instruction as a big, bold title, or the SVG could be very large and have very small text, which the user might want to zoom into, in order to read.
2. Potential exploit code can only run in a new tab. It still has the same origin (as can be seen in the PoC above, because the domain/origin the script is running on, is shown). However, though, sensitive information like the paste content, potential comments or encryption key (in the URL) is not accessible to the attacker as the context is now a blob-URL – and would anyway consist mostly of things the attacker initially created itself.
That said, [the same origin policy applies](https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy) and thus, what an attacker could do is read e.g. cookies and local storage data saved in the same origin. As PrivateBin itself does not use any of that, the impact of this vulnerability is limited. However, as PrivateBin is a software for self-hosting, it cannot be excluded that other services run in the same origin (e.g. on the same domain). That's why server administrators may need to evaluate the impact of running arbitrary JavaScript code on their domain/origin where PrivateBin is hosted by themselves.
To summarize, this shows a fairly limited impact, given even if the CSP had not caught the issue, the user still needs to interact with the page and the exploit code cannot access or exfiltrate any data of the PrivateBin instance.
**Note:** However, take our assessment only as a basis for your own assessment. As explained, depending on your environment, the actual risk may vary if you are hosting other services on the same domain as PrivateBin.
As for the metrics, the impact assessment we have done with [CVSS v3.1](https://nvd.nist.gov/vuln-metrics/cvss) results in this:
[AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N/E:F/RL:U/RC:C/CR:X/IR:X/AR:X/MAV:N/MAC:L/MPR:N/MUI:R/MS:U/MC:X/MI:X/MA:X](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N/E:F/RL:U/RC:C/CR:X/IR:X/AR:X/MAV:N/MAC:L/MPR:N/MUI:R/MS:U/MC:X/MI:X/MA:X&version=3.1)
### Real-life impact
We found two affected instances in our instance lists (wiki, directory) that did not serve a correct Content Security Policy header, had attachments enabled and thus are vulnerable to this attack. We didn't manage to get into contact with the administrators of these sites, though.
In addition to that, we found that multiple instances do seem to either strip our CSP or have it changed to an unsafe setting and have thus expanded our directory service to verify whether our recommend CSP is used or not. (see below)
We have no reports that indicate this vulnerability was or is being actively exploited at the time of this report.
## Patches
To fix the problem, we took the following measures (in no particular order):
* We apply [DOMpurify](https://github.com/cure53/DOMPurify/) (a library we already use to sanitize user-submitted HTML via the Markdown format) to the SVG preview, too. It strips script tags and other uncommon security-relevant and potentially malicious tags/properties from the SVG file.
So whether you open the SVG in a new tab or not and whether CSP is present and enabled or not does not matter any more, as the displayed SVG is sanitized.
* As a further defence in depth mechanism we now send the CSP both as an HTTP header, as well as a meta tag. This protects instance with mis-configured web servers, CDNs, proxy or similar, from stripping or breaking the CSP headers, as they still get the CSP inside of the HTML content itself. Please note though, that the [meta tag approach is not as strong as the HTTP header approach](https://content-security-policy.com/examples/meta/) and should thus only be considered as a fallback.
* The [PrivateBin Directory](https://privatebin.info/) now also scans whether the recommend Content-Security-Policy header is used on a given instance. If you do not want to have your website appear in the list, but check it manually [you can use a separate check page](https://privatebin.info/directory/check) there.
The code-changes in PrivateBin can be found in https://github.com/PrivateBin/PrivateBin/pull/906.
**Note:** Please note that we explicitly chose to _not_ apply _DOMPurify_ if you download the (SVG) attachment with the download button. Subsequently, if a user would manually opens the downloaded SVG in the browser, it will be opened from the `file://` protocol and thus from a [different origin](https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy), so all reference to the download location is lost and no more security risk is associated with that, than opening any website or local HTML file. Thus, the SVG file with stay intact in it's original form, if you download the attachment.
We consider the execution of code from attachments outside of the PrivateBin instance's context to be out of scope to mitigate (i.e. malware in executables, office documents macros, PDF scripts), as all of these require client side mitigations to be applied to all such downloaded file types, independent on where they get downloaded from.
## Workarounds
We strongly recommend you to upgrade to our latest release, especially as we also upgraded outdated and potential vulnerable libraries (see below). However, here are two workarounds that may help you to mitigate this vulnerability:
* Update the [CSP in your configuration file](https://github.com/PrivateBin/PrivateBin/wiki/Configuration#cspheader) to the latest recommended settings and check that it isn't getting reverted or overwritten by your web server, reverse proxy or CDN, i.e. using [our offered check service](https://privatebin.info/directory/check).
* Deploying PrivateBin on a separate domain may limit the scope of the vulnerability to PrivateBin itself and thus, as described in the “Impact” section, effectively prevent any damage by the vulnerability to other resources you are hosting.
* As explained in the impact assessment, disabling attachments also prevents this issue.
## References
We highly encourage server administrators and others involved with the PrivateBin project to read-up on how Content-Security-Policies work, especially should you consider to manually adjust it:
* https://content-security-policy.com/
* https://developer.mozilla.org/docs/Web/HTTP/CSP
* https://developers.google.com/web/fundamentals/security/csp/
Also please note that if multiple headers are set (as e.g. done via our now introduced meta tag) [browsers should apply the most restrictive set of the policies](https://stackoverflow.com/a/51153816/5008962), [as per the CSP specification](https://www.w3.org/TR/CSP2/#enforcing-multiple-policies).
## For more information
Please notice we also upgraded [jQuery](https://github.com/PrivateBin/PrivateBin/pull/880) that was reported to us as being vulnerable both by [our automated container security scanning](https://github.com/PrivateBin/docker-nginx-fpm-alpine/issues/69#issue-1006943396) as well as [by users](https://github.com/PrivateBin/PrivateBin/issues/864).
By doing so, we also updated all [other dependencies we use](https://github.com/PrivateBin/PrivateBin/pull/888). Our tooling identified the following vulnerabilities in jQuery:
* CVE-2020-11023
* CVE-2020-11022
In [a limited assessment about these when we were made aware of them](https://github.com/PrivateBin/docker-nginx-fpm-alpine/issues/69#issuecomment-928261418) we could not find any immediate risk, but nevertheless, we encourage users to upgrade to be on the safe side.
Finally, we also [upgraded zlib](https://github.com/PrivateBin/PrivateBin/pull/909) to address CVE-2018-25032.
## Timeline
* 2022-02-22 – Initial contact by reporter.
* 2022-02-25 – Reporter sends in a detailed report.
* 2022-02-26 – Report gets reviewed, initial findings around the content security get shared and reporter withdraws report.
* 2022-04-09 – Vulnerability details published.
## Credits
This vulnerability was reported by Ian Budd, [Nethemba s.r.o](https://www.nethemba.com/), which we'd like to thank for that.
In general, we'd like to thank everyone reporting issues and potential vulnerabilities to us.
If you think you have found a vulnerability or potential security risk, [we'd kindly ask you to follow our security policy](https://github.com/PrivateBin/PrivateBin/blob/master/SECURITY.md) and report it to us. We then assess the report and will take the actions we deem necessary to address it. | {'CVE-2022-24833'} | 2022-04-12T21:33:22Z | 2022-04-12T20:45:22Z | HIGH | 8.2 | {'CWE-79'} | {'https://github.com/advisories/GHSA-cqcc-mm6x-vmvw', 'https://github.com/PrivateBin/PrivateBin/security/advisories/GHSA-cqcc-mm6x-vmvw', 'https://github.com/PrivateBin/PrivateBin/commit/2a4d572c1e9eb9b608d32b0cc0cb3b6c3b684eab', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24833'} | null | {'https://github.com/PrivateBin/PrivateBin/commit/2a4d572c1e9eb9b608d32b0cc0cb3b6c3b684eab'} | {'https://github.com/PrivateBin/PrivateBin/commit/2a4d572c1e9eb9b608d32b0cc0cb3b6c3b684eab'} |
GHSA | GHSA-hpv8-9rq5-hq7w | Generated Code Contains Local Information Disclosure Vulnerability | ### Impact
**This vulnerability impacts generated code.** If this code was generated as a one-off occasion, not as a part of an automated CI/CD process, this code will remain vulnerable until fixed manually!
On Unix-Like systems, the system temporary directory is shared between all local users. When files/directories are created, the default `umask` settings for the process are respected. As a result, by default, most processes/apis will create files/directories with the permissions `-rw-r--r--` and `drwxr-xr-x` respectively, unless an API that explicitly sets safe file permissions is used.
#### Java Code
The method `File.createTempFile` from the JDK is vulnerable to this local information disclosure vulnerability.
- https://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-codegen/src/main/resources/kotlin-client/infrastructure/ApiClient.kt.mustache#L209
- https://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-codegen/src/main/resources/finch/api.mustache#L84
- https://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-codegen/src/main/resources/Java/libraries/okhttp-gson/ApiClient.mustache#L831-L834
- https://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-codegen/src/main/resources/Java/libraries/jersey2/ApiClient.mustache#L630-L633
### Patches
Fix has been applied to the master branch with:
* https://github.com/swagger-api/swagger-codegen/commit/35adbd552d5f99b3ff1e0e59da228becc85190f2
included in release: 2.4.19
### Workarounds
Users can remediate the vulnerability in non patched version by manually (or programmatically e.g. in CI) updating the generated source code to use `java.nio.files.Files` temporary file creation instead of `java.io.File`, e.g. by changing
```java
if (tempFolderPath == null)
return File.createTempFile(prefix, suffix);
else
return File.createTempFile(prefix, suffix, new File(tempFolderPath));
```
to
```java
if (tempFolderPath == null)
return Files.createTempFile(prefix, suffix).toFile();
else
return Files.createTempFile(Paths.get(tempFolderPath), prefix, suffix).toFile();
```
or generally changing:
```java
File.createTempFile(prefix, suffix);
```
to
```java
Files.createTempFile(prefix, suffix).toFile();
```
### References
* [CWE-378: Creation of Temporary File With Insecure Permissions](https://cwe.mitre.org/data/definitions/378.html)
* [CWE-200: Exposure of Sensitive Information to an Unauthorized Actor](https://cwe.mitre.org/data/definitions/200.html)
* [CWE-732: Incorrect Permission Assignment for Critical Resource](https://cwe.mitre.org/data/definitions/732.html)
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@swagger.io](mailto:security@swagger.io)
#### Original vulnerability report
> I'm performing OSS security research under the GitHub Security Lab Bug Bounty program.
> I've been using a custom CodeQL query to find local temporary directory vulnerabilities in OSS with three custom CodeQL queries.
>
> - https://github.com/github/codeql/pull/4388/files#diff-71d36c0f2bd0b08e32866f873f1c906cdc17277e0ad327c0c6cd2c882f30de4f
> - https://github.com/github/codeql/pull/4388/files#diff-1893a18a8bf43c011d61a7889d0139b998a5a78701a30fe7722eddd4c506aaac
> - https://github.com/github/codeql/pull/4473
>
> The code generated by the Swagger Generator contains a local information disclosure vulnerability. The system temporary directory, on unix-like systems is shared between multiple users. Information written to this directory, or directories created under this directory that do not correctly set the posix standard permissions can have these directories read/modified by other users.
>
> ---
>
> This code exists in the code generator, in the generated code.
>
> In this case, I believe this is only a local information disclosure. IE. another user can read the information, not replace it.
>
> In particular, the method `File.createTempFile` from the JDK is vulnerable to this local information disclosure vulnerability.
>
> This is because `File.createTempFile` creates a file inside of the system temporary directory with the permissions: `-rw-r--r--`. Thus the contents of this file are viewable by all other users locally on the system.
>
> - https://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-codegen/src/main/resources/kotlin-client/infrastructure/ApiClient.kt.mustache#L209
> - https://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-codegen/src/main/resources/finch/api.mustache#L84
> - https://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-codegen/src/main/resources/Java/libraries/okhttp-gson/ApiClient.mustache#L831-L834
> - https://github.com/swagger-api/swagger-codegen/blob/068b1ebcb7b04a48ad38f1cadd24bb3810c9f1ab/modules/swagger-codegen/src/main/resources/Java/libraries/jersey2/ApiClient.mustache#L630-L633
>
> The fix here is to switch to the `Files` API, instead of `File` as that appropriately sets the file permissions.
> | {'CVE-2021-21364'} | 2022-04-19T19:02:48Z | 2021-03-11T03:09:18Z | LOW | 6.2 | {'CWE-200', 'CWE-732', 'CWE-378'} | {'https://github.com/swagger-api/swagger-codegen/security/advisories/GHSA-hpv8-9rq5-hq7w', 'https://github.com/advisories/GHSA-hpv8-9rq5-hq7w', 'https://github.com/swagger-api/swagger-codegen/commit/35adbd552d5f99b3ff1e0e59da228becc85190f2', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21364'} | null | {'https://github.com/swagger-api/swagger-codegen/commit/35adbd552d5f99b3ff1e0e59da228becc85190f2'} | {'https://github.com/swagger-api/swagger-codegen/commit/35adbd552d5f99b3ff1e0e59da228becc85190f2'} |
GHSA | GHSA-jg4f-jqm5-4mgq | Ansible fails to properly sanitize fact variables sent from the Ansible controller | Ansible before version 2.2.0 fails to properly sanitize fact variables sent from the Ansible controller. An attacker with the ability to create special variables on the controller could execute arbitrary commands on Ansible clients as the user Ansible runs as. | {'CVE-2016-8628'} | 2022-04-26T18:42:21Z | 2018-10-10T17:23:14Z | CRITICAL | 9.1 | {'CWE-77'} | {'https://github.com/ansible/ansible/commit/35938b907dfcd1106ca40b794f0db446bdb8cf09', 'https://access.redhat.com/errata/RHSA-2016:2778', 'https://nvd.nist.gov/vuln/detail/CVE-2016-8628', 'http://www.securityfocus.com/bid/94109', 'https://github.com/advisories/GHSA-jg4f-jqm5-4mgq', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-8628'} | null | {'https://github.com/ansible/ansible/commit/35938b907dfcd1106ca40b794f0db446bdb8cf09'} | {'https://github.com/ansible/ansible/commit/35938b907dfcd1106ca40b794f0db446bdb8cf09'} |
GHSA | GHSA-f2vv-v9cg-qhh7 | Assertion failure based denial of service in Tensorflow | ### Impact
The [implementation of `*Bincount` operations](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/bincount_op.cc) allows malicious users to cause denial of service by passing in arguments which would trigger a `CHECK`-fail:
```python
import tensorflow as tf
tf.raw_ops.DenseBincount(
input=[[0], [1], [2]],
size=[1],
weights=[3,2,1],
binary_output=False)
```
There are several conditions that the input arguments must satisfy. Some are not caught during shape inference and others are not caught during kernel implementation. This results in `CHECK` failures later when the output tensors get allocated.
### Patches
We have patched the issue in GitHub commit [7019ce4f68925fd01cdafde26f8d8c938f47e6f9](https://github.com/tensorflow/tensorflow/commit/7019ce4f68925fd01cdafde26f8d8c938f47e6f9).
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 Faysal Hossain Shezan from University of Virginia. | {'CVE-2022-21737'} | 2022-02-11T16:23:03Z | 2022-02-09T23:43:48Z | MODERATE | 6.5 | {'CWE-754', 'CWE-617'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-21737', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-f2vv-v9cg-qhh7', 'https://github.com/advisories/GHSA-f2vv-v9cg-qhh7', 'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/bincount_op.cc', 'https://github.com/tensorflow/tensorflow/commit/7019ce4f68925fd01cdafde26f8d8c938f47e6f9'} | null | {'https://github.com/tensorflow/tensorflow/commit/7019ce4f68925fd01cdafde26f8d8c938f47e6f9'} | {'https://github.com/tensorflow/tensorflow/commit/7019ce4f68925fd01cdafde26f8d8c938f47e6f9'} |
GHSA | GHSA-hqhp-5p83-hx96 | Regular Expression Denial of Service in prismjs | Prism is a lightweight, robust, and elegant syntax highlighting library. The prismjs package is vulnerable to ReDoS (regular expression denial of service). An attacker that is able to provide a crafted HTML comment as input may cause an application to consume an excessive amount of CPU. | {'CVE-2021-3801'} | 2022-05-04T03:23:17Z | 2021-09-20T20:44:48Z | MODERATE | 6.5 | {'CWE-400'} | {'https://huntr.dev/bounties/8c16ab31-6eb6-46d1-b9a4-387222fe1b8a', 'https://github.com/advisories/GHSA-hqhp-5p83-hx96', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3801', 'https://github.com/prismjs/prism/commit/0ff371bb4775a131634f47d0fe85794c547232f9'} | null | {'https://github.com/prismjs/prism/commit/0ff371bb4775a131634f47d0fe85794c547232f9'} | {'https://github.com/prismjs/prism/commit/0ff371bb4775a131634f47d0fe85794c547232f9'} |
GHSA | GHSA-hf4q-52x6-4p57 | Unrestricted file upload leads to stored cross-site scripting in Microweber | Microweber prior to version 1.2.12 allows unrestricted file upload, which could lead to stored cross-site scripting. | {'CVE-2022-0906'} | 2022-03-29T21:07:51Z | 2022-03-11T00:02:36Z | MODERATE | 4.8 | {'CWE-79'} | {'https://github.com/advisories/GHSA-hf4q-52x6-4p57', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0906', 'https://github.com/microweber/microweber/commit/d9bae9df873c2d2a13a2eb08d512019d49ebca68', 'https://huntr.dev/bounties/87ed3b42-9824-49b0-91a5-fd908a0601e8'} | null | {'https://github.com/microweber/microweber/commit/d9bae9df873c2d2a13a2eb08d512019d49ebca68'} | {'https://github.com/microweber/microweber/commit/d9bae9df873c2d2a13a2eb08d512019d49ebca68'} |
GHSA | GHSA-v567-q267-phpg | pimcore is vulnerable to Cross-site Scripting | pimcore is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') | {'CVE-2022-0257'} | 2022-01-25T20:49:26Z | 2022-01-21T23:50:11Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/advisories/GHSA-v567-q267-phpg', 'https://github.com/pimcore/pimcore/commit/dfaf78b26fb77990267c0cc05b9fcb9f8de7b66d', 'https://huntr.dev/bounties/bad2073c-bbd5-4425-b3e9-c336b73ddda6', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0257'} | null | {'https://github.com/pimcore/pimcore/commit/dfaf78b26fb77990267c0cc05b9fcb9f8de7b66d'} | {'https://github.com/pimcore/pimcore/commit/dfaf78b26fb77990267c0cc05b9fcb9f8de7b66d'} |
GHSA | GHSA-67mm-m3wx-j7fr | Command injection in gitlog | The gitlog function in src/index.ts in gitlog before 4.0.4 has a command injection vulnerability. | {'CVE-2021-26541'} | 2022-04-27T19:13:34Z | 2021-04-13T15:15:29Z | CRITICAL | 9.8 | {'CWE-77'} | {'https://github.com/domharrington/node-gitlog/pull/65/commits/bb22ffb2c907e0284f887ab625e12b88c31f4bf4', 'https://www.npmjs.com/package/gitlog', 'https://github.com/domharrington/node-gitlog/pull/65', 'https://nvd.nist.gov/vuln/detail/CVE-2021-26541', 'https://advisory.checkmarx.net/advisory/CX-2020-4301', 'https://github.com/advisories/GHSA-67mm-m3wx-j7fr'} | null | {'https://github.com/domharrington/node-gitlog/pull/65/commits/bb22ffb2c907e0284f887ab625e12b88c31f4bf4'} | {'https://github.com/domharrington/node-gitlog/pull/65/commits/bb22ffb2c907e0284f887ab625e12b88c31f4bf4'} |
GHSA | GHSA-9c8h-2mv3-49ww | Division by 0 in most convolution operators | ### Impact
Most implementations of convolution operators in TensorFlow are affected by a division by 0 vulnerability where an attacker can trigger a denial of service via a crash:
```python
import tensorflow as tf
tf.compat.v1.disable_v2_behavior()
tf.raw_ops.Conv2D(
input = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32),
filter = tf.constant([], shape=[0, 0, 0, 0], dtype=tf.float32),
strides = [1, 1, 1, 1],
padding = "SAME")
```
The shape inference [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/framework/common_shape_fns.cc#L577) is missing several validations before doing divisions and modulo operations.
### Patches
We have patched the issue in GitHub commit [8a793b5d7f59e37ac7f3cd0954a750a2fe76bad4](https://github.com/tensorflow/tensorflow/commit/8a793b5d7f59e37ac7f3cd0954a750a2fe76bad4).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Yakun Zhang of Baidu Security. | {'CVE-2021-37675'} | 2021-08-25T14:41:29Z | 2021-08-25T14:41:29Z | MODERATE | 5.5 | {'CWE-369'} | {'https://github.com/tensorflow/tensorflow/commit/8a793b5d7f59e37ac7f3cd0954a750a2fe76bad4', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9c8h-2mv3-49ww', 'https://github.com/advisories/GHSA-9c8h-2mv3-49ww', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37675'} | null | {'https://github.com/tensorflow/tensorflow/commit/8a793b5d7f59e37ac7f3cd0954a750a2fe76bad4'} | {'https://github.com/tensorflow/tensorflow/commit/8a793b5d7f59e37ac7f3cd0954a750a2fe76bad4'} |
GHSA | GHSA-6hfq-h8hq-87mf | HTTP Request Smuggling in hyper | ### Summary
hyper's HTTP server code had a flaw that incorrectly understands some requests with multiple transfer-encoding headers to have a chunked payload, when it should have been rejected as illegal. This combined with an upstream HTTP proxy that understands the request payload boundary differently can result in "request smuggling" or "desync attacks".
### Vulnerability
The flaw was introduced in https://github.com/hyperium/hyper/commit/26417fc24a7d05df538e0f39239b373c5c3d61f6, released in v0.12.0.
Consider this example request:
```
POST /yolo HTTP/1.1
Transfer-Encoding: chunked
Transfer-Encoding: cow
```
This request *should* be rejected, according to RFC 7230, since it has a `Transfer-Encoding` header, but after folding, it does not end in `chunked`. hyper would notice the `chunked` in the first line, and then check the second line, and thanks to a missing boolean assignment, *not* set the error condition. hyper would treat the payload as being `chunked`. By differing from the spec, it is possible to send requests like these to endpoints that have different HTTP implementations, with different interpretations of the payload semantics, and cause "desync attacks".
There are several parts of the spec that must also be checked, and hyper correctly handles all of those. Additionally, hyper's *client* does not allow sending requests with improper headers, so the misunderstanding cannot be propagated further.
Read more about desync attacks: https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn
### Impact
To determine if vulnerable, all these things must be true:
- **Using hyper as an HTTP *server*.** The client is not affected.
- **Using HTTP/1.1.** HTTP/2 does not use `transfer-encoding`.
- **Using a vulnerable HTTP proxy upstream to hyper.** If an upstream proxy correctly rejects the illegal transfer-encoding headers, the desync attack cannot succeed. If there is *no* proxy upstream of hyper, hyper cannot *start* the desync attack, as the client will repair the headers before forwarding.
### Patches
We have released and backported the following patch versions:
- v0.14.3
- v0.13.10
### Workarounds
Besides upgrading hyper, you can take the following options:
- Reject requests that contain a `transfer-encoding` header.
- Ensure any upstream proxy handles `transfer-encoding` correctly.
### Credits
This issue was initially reported by ZeddYu Lu From Qi An Xin Technology Research Institute. | {'CVE-2021-21299'} | 2022-04-19T19:02:46Z | 2021-08-25T20:56:18Z | MODERATE | 4.8 | {'CWE-444'} | {'https://rustsec.org/advisories/RUSTSEC-2021-0020.html', 'https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn', 'https://github.com/hyperium/hyper/commit/8f93123efef5c1361086688fe4f34c83c89cec02', 'https://github.com/hyperium/hyper/security/advisories/GHSA-6hfq-h8hq-87mf', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21299', 'https://github.com/advisories/GHSA-6hfq-h8hq-87mf'} | null | {'https://github.com/hyperium/hyper/commit/8f93123efef5c1361086688fe4f34c83c89cec02'} | {'https://github.com/hyperium/hyper/commit/8f93123efef5c1361086688fe4f34c83c89cec02'} |
GHSA | GHSA-cgjv-rghq-qhgp | Path Traversal in algo-httpserv | Versions of `algo-httpserv` prior to 1.1.2 are vulnerable to Path Traversal. Due to insufficient input sanitization, attackers can access server files by using relative paths.
## Recommendation
Upgrade to version 1.1.2 or later. | null | 2021-08-17T22:22:49Z | 2019-09-11T23:00:57Z | HIGH | 8.6 | {'CWE-22'} | {'https://github.com/AlgoRythm-Dylan/httpserv/commit/bcfe9d4316c2b59aab3a64a38905376026888735', 'https://snyk.io/vuln/SNYK-JS-ALGOHTTPSERV-174741', 'https://www.npmjs.com/advisories/889', 'https://github.com/advisories/GHSA-cgjv-rghq-qhgp'} | null | {'https://github.com/AlgoRythm-Dylan/httpserv/commit/bcfe9d4316c2b59aab3a64a38905376026888735'} | {'https://github.com/AlgoRythm-Dylan/httpserv/commit/bcfe9d4316c2b59aab3a64a38905376026888735'} |
GHSA | GHSA-vfvf-mqq8-rwqc | Sanitization bypass using HTML Entities in marked | Affected versions of `marked` are susceptible to a cross-site scripting vulnerability in link components when `sanitize:true` is configured.
## Proof of Concept
This flaw exists because link URIs containing HTML entities get processed in an abnormal manner. Any HTML Entities get parsed on a best-effort basis and included in the resulting link, while if that parsing fails that character is omitted.
For example:
A link URI such as
```
javascript֍ocument;alert(1)
```
Renders a valid link that when clicked will execute `alert(1)`.
## Recommendation
Update to version 0.3.6 or later. | {'CVE-2016-10531'} | 2021-01-08T01:57:26Z | 2019-02-18T23:58:20Z | HIGH | 0 | {'CWE-79'} | {'https://nodesecurity.io/advisories/101', 'https://github.com/chjj/marked/pull/592', 'https://www.npmjs.com/advisories/101', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10531', 'https://github.com/chjj/marked/pull/592/commits/2cff85979be8e7a026a9aca35542c470cf5da523', 'https://github.com/advisories/GHSA-vfvf-mqq8-rwqc'} | null | {'https://github.com/chjj/marked/pull/592/commits/2cff85979be8e7a026a9aca35542c470cf5da523'} | {'https://github.com/chjj/marked/pull/592/commits/2cff85979be8e7a026a9aca35542c470cf5da523'} |
GHSA | GHSA-m3jw-62m7-jjcm | Out-of-bounds read in typed-ast and cpython may allow an attacker to crash the interpreter process (handle_keywordonly_args case). | typed_ast 1.3.0 and 1.3.1 has a handle_keywordonly_args out-of-bounds read. An attacker with the ability to cause a Python interpreter to parse Python source (but not necessarily execute it) may be able to crash the interpreter process. This could be a concern, for example, in a web-based service that parses (but does not execute) Python code. (This issue also affected certain Python 3.8.0-alpha prereleases.) | {'CVE-2019-19274'} | 2021-08-18T22:47:51Z | 2019-12-02T18:02:02Z | HIGH | 7.5 | {'CWE-125'} | {'https://github.com/python/cpython/commit/a4d78362397fc3bced6ea80fbc7b5f4827aec55e', 'https://nvd.nist.gov/vuln/detail/CVE-2019-19274', 'https://github.com/python/cpython/commit/dcfcd146f8e6fc5c2fc16a4c192a0c5f5ca8c53c', 'https://github.com/advisories/GHSA-m3jw-62m7-jjcm', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LG5H4Q6LFVRX7SFXLBEJMNQFI4T5SCEA/', 'https://bugs.python.org/issue36495', 'https://github.com/python/typed_ast/commit/156afcb26c198e162504a57caddfe0acd9ed7dce', 'https://github.com/python/typed_ast/commit/dc317ac9cff859aa84eeabe03fb5004982545b3b'} | null | {'https://github.com/python/cpython/commit/dcfcd146f8e6fc5c2fc16a4c192a0c5f5ca8c53c', 'https://github.com/python/cpython/commit/a4d78362397fc3bced6ea80fbc7b5f4827aec55e', 'https://github.com/python/typed_ast/commit/dc317ac9cff859aa84eeabe03fb5004982545b3b', 'https://github.com/python/typed_ast/commit/156afcb26c198e162504a57caddfe0acd9ed7dce'} | {'https://github.com/python/cpython/commit/a4d78362397fc3bced6ea80fbc7b5f4827aec55e', 'https://github.com/python/typed_ast/commit/dc317ac9cff859aa84eeabe03fb5004982545b3b', 'https://github.com/python/cpython/commit/dcfcd146f8e6fc5c2fc16a4c192a0c5f5ca8c53c', 'https://github.com/python/typed_ast/commit/156afcb26c198e162504a57caddfe0acd9ed7dce'} |
GHSA | GHSA-q3g3-h9r4-prrc | Reference binding to nullptr and heap OOB in binary cwise ops | ### Impact
An attacker can cause undefined behavior via binding a reference to null pointer in all binary cwise operations that don't require broadcasting (e.g., gradients of binary cwise operations):
```python
import tensorflow as tf
tf.raw_ops.SqrtGrad(y=[4, 16],dy=[])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/cwise_ops_common.h#L264) assumes that the two inputs have exactly the same number of elements but does not check that. Hence, when the eigen functor executes it triggers heap OOB reads and undefined behavior due to binding to nullptr.
### Patches
We have patched the issue in GitHub commit [93f428fd1768df147171ed674fee1fc5ab8309ec](https://github.com/tensorflow/tensorflow/commit/93f428fd1768df147171ed674fee1fc5ab8309ec).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-37659'} | 2021-08-25T14:42:47Z | 2021-08-25T14:42:47Z | HIGH | 7.3 | {'CWE-125'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q3g3-h9r4-prrc', 'https://github.com/advisories/GHSA-q3g3-h9r4-prrc', 'https://github.com/tensorflow/tensorflow/commit/93f428fd1768df147171ed674fee1fc5ab8309ec', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37659'} | null | {'https://github.com/tensorflow/tensorflow/commit/93f428fd1768df147171ed674fee1fc5ab8309ec'} | {'https://github.com/tensorflow/tensorflow/commit/93f428fd1768df147171ed674fee1fc5ab8309ec'} |
GHSA | GHSA-3j78-7m59-r7gv | Private data exposure via REST API in BuddyPress | In BuddyPress before 5.1.2, requests to a certain REST API endpoint can result in private user data getting exposed. Authentication is not needed.
This has been patched in version 5.1.2. | {'CVE-2020-5244'} | 2021-01-08T20:29:12Z | 2020-02-24T17:18:26Z | HIGH | 8 | {'CWE-284'} | {'https://github.com/advisories/GHSA-3j78-7m59-r7gv', 'https://github.com/buddypress/BuddyPress/commit/39294680369a0c992290577a9d740f4a2f2c2ca3', 'https://buddypress.org/2020/01/buddypress-5-1-2/', 'https://github.com/buddypress/BuddyPress/security/advisories/GHSA-3j78-7m59-r7gv', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5244'} | null | {'https://github.com/buddypress/BuddyPress/commit/39294680369a0c992290577a9d740f4a2f2c2ca3'} | {'https://github.com/buddypress/BuddyPress/commit/39294680369a0c992290577a9d740f4a2f2c2ca3'} |
GHSA | GHSA-q73m-3q7r-fpf7 | Cross-site Scripting in ShowDoc | ShowDoc prior to 2.10.4 is vulnerable to stored cross-site scripting via file upload. | {'CVE-2022-0957'} | 2022-03-29T21:27:35Z | 2022-03-16T00:00:48Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/advisories/GHSA-q73m-3q7r-fpf7', 'https://github.com/star7th/showdoc/pull/1632', 'https://github.com/star7th/showdoc/commit/d1c9ed0d77ea5d56f09be0c492361dca8af745bb', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0957', 'https://huntr.dev/bounties/b4918d45-b635-40db-bb4b-34035e1aca21'} | null | {'https://github.com/star7th/showdoc/commit/d1c9ed0d77ea5d56f09be0c492361dca8af745bb'} | {'https://github.com/star7th/showdoc/commit/d1c9ed0d77ea5d56f09be0c492361dca8af745bb'} |
GHSA | GHSA-h65g-jfqg-2w6m | Server-Side Request Forgery in calibreweb | calibreweb prior to version 0.6.17 is vulnerable to server-side request forgery (SSRF). This is a result of incomplete SSRF protection that can be bypassed via an HTTP redirect. An HTTP server set up to respond with a 302 redirect may redirect a request to `localhost`. | {'CVE-2022-0767'} | 2022-03-15T21:52:59Z | 2022-03-08T00:00:31Z | CRITICAL | 9.9 | {'CWE-918'} | {'https://github.com/advisories/GHSA-h65g-jfqg-2w6m', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0767', 'https://github.com/janeczku/calibre-web/commit/965352c8d96c9eae7a6867ff76b0db137d04b0b8', 'https://huntr.dev/bounties/b26fc127-9b6a-4be7-a455-58aefbb62d9e'} | null | {'https://github.com/janeczku/calibre-web/commit/965352c8d96c9eae7a6867ff76b0db137d04b0b8'} | {'https://github.com/janeczku/calibre-web/commit/965352c8d96c9eae7a6867ff76b0db137d04b0b8'} |
GHSA | GHSA-g6rj-rv7j-xwp4 | Denial of service | An issue was discovered in Pillow before 8.2.0. PSDImagePlugin.PsdImageFile lacked a sanity check on the number of input layers relative to the size of the data block. This could lead to a DoS on Image.open prior to Image.load. | {'CVE-2021-28675'} | 2021-07-16T14:33:38Z | 2021-06-08T18:49:11Z | MODERATE | 5.5 | {'CWE-233', 'CWE-252'} | {'https://github.com/advisories/GHSA-g6rj-rv7j-xwp4', 'https://pillow.readthedocs.io/en/stable/releasenotes/8.2.0.html#cve-2021-28675-fix-dos-in-psdimageplugin', 'https://github.com/python-pillow/Pillow/pull/5377/commits/22e9bee4ef225c0edbb9323f94c26cee0c623497', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28675', 'https://security.gentoo.org/glsa/202107-33', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MQHA5HAIBOYI3R6HDWCLAGFTIQP767FL/'} | null | {'https://github.com/python-pillow/Pillow/pull/5377/commits/22e9bee4ef225c0edbb9323f94c26cee0c623497'} | {'https://github.com/python-pillow/Pillow/pull/5377/commits/22e9bee4ef225c0edbb9323f94c26cee0c623497'} |
GHSA | GHSA-r854-96gq-rfg3 | Python Image Library (PIL) allows symlink attacks | The (1) JpegImagePlugin.py and (2) EpsImagePlugin.py scripts in Python Image Library (PIL) 1.1.7 and earlier and Pillow before 2.3.1 uses the names of temporary files on the command line, which makes it easier for local users to conduct symlink attacks by listing the processes. | {'CVE-2014-1933'} | 2021-08-25T21:10:34Z | 2020-05-18T17:41:19Z | MODERATE | 0 | null | {'http://www.openwall.com/lists/oss-security/2014/02/11/1', 'http://www.openwall.com/lists/oss-security/2014/02/10/15', 'https://nvd.nist.gov/vuln/detail/CVE-2014-1933', 'https://github.com/advisories/GHSA-r854-96gq-rfg3', 'https://github.com/python-imaging/Pillow/commit/4e9f367dfd3f04c8f5d23f7f759ec12782e10ee7', 'https://security.gentoo.org/glsa/201612-52', 'http://www.ubuntu.com/usn/USN-2168-1', 'http://www.securityfocus.com/bid/65513', 'http://lists.opensuse.org/opensuse-updates/2014-05/msg00002.html'} | null | {'https://github.com/python-imaging/Pillow/commit/4e9f367dfd3f04c8f5d23f7f759ec12782e10ee7'} | {'https://github.com/python-imaging/Pillow/commit/4e9f367dfd3f04c8f5d23f7f759ec12782e10ee7'} |
GHSA | GHSA-9mx2-prfp-8hqp | Prototype Pollution in simpl-schema | This affects the package simpl-schema before 1.10.2. Attacker controlled input into a schema could result in remote code execution within the scope of the surrounding application. | {'CVE-2020-7742'} | 2021-05-10T18:38:47Z | 2021-05-10T18:38:47Z | HIGH | 7.5 | {'CWE-1321'} | {'https://github.com/longshotlabs/simpl-schema/releases/tag/1.10.2', 'https://snyk.io/vuln/SNYK-JS-SIMPLSCHEMA-1016157', 'https://github.com/advisories/GHSA-9mx2-prfp-8hqp', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7742', 'https://github.com/longshotlabs/simpl-schema/commit/50128841fa7fc2d137c36a397054279144caea3d'} | null | {'https://github.com/longshotlabs/simpl-schema/commit/50128841fa7fc2d137c36a397054279144caea3d'} | {'https://github.com/longshotlabs/simpl-schema/commit/50128841fa7fc2d137c36a397054279144caea3d'} |
GHSA | GHSA-49rx-x2rw-pc6f | Heap OOB read in all `tf.raw_ops.QuantizeAndDequantizeV*` ops | ### Impact
The [shape inference functions for the `QuantizeAndDequantizeV*` operations](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/array_ops.cc) can trigger a read outside of bounds of heap allocated array as illustrated in the following sets of PoCs:
```python
import tensorflow as tf
@tf.function
def test():
data=tf.raw_ops.QuantizeAndDequantizeV4Grad(
gradients=[1.0,1.0],
input=[1.0,1.0],
input_min=[1.0,10.0],
input_max=[1.0,10.0],
axis=-100)
return data
test()
```
```python
import tensorflow as tf
@tf.function
def test():
data=tf.raw_ops.QuantizeAndDequantizeV4(
input=[1.0,1.0],
input_min=[1.0,10.0],
input_max=[1.0,10.0],
signed_input=False,
num_bits=10,
range_given=False,
round_mode='HALF_TO_EVEN',
narrow_range=False,
axis=-100)
return data
test()
```
```python
import tensorflow as tf
@tf.function
def test():
data=tf.raw_ops.QuantizeAndDequantizeV3(
input=[1.0,1.0],
input_min=[1.0,10.0],
input_max=[1.0,10.0],
signed_input=False,
num_bits=10,
range_given=False,
narrow_range=False,
axis=-100)
return data
test()
```
```python
import tensorflow as tf
@tf.function
def test():
data=tf.raw_ops.QuantizeAndDequantizeV2(
input=[1.0,1.0],
input_min=[1.0,10.0],
input_max=[1.0,10.0],
signed_input=False,
num_bits=10,
range_given=False,
round_mode='HALF_TO_EVEN',
narrow_range=False,
axis=-100)
return data
test()
```
In all of these cases, `axis` is a negative value different than the special value used for optional/unknown dimensions (i.e., -1). However, the code ignores the occurences of these values:
```cc
...
if (axis != -1) {
...
c->Dim(input, axis);
...
}
```
### Patches
We have patched the issue in GitHub commit [7cf73a2274732c9d82af51c2bc2cf90d13cd7e6d](https://github.com/tensorflow/tensorflow/commit/7cf73a2274732c9d82af51c2bc2cf90d13cd7e6d).
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-41205'} | 2021-11-10T19:04:25Z | 2021-11-10T19:04:25Z | HIGH | 7.1 | {'CWE-125'} | {'https://github.com/advisories/GHSA-49rx-x2rw-pc6f', 'https://github.com/tensorflow/tensorflow/commit/7cf73a2274732c9d82af51c2bc2cf90d13cd7e6d', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41205', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-49rx-x2rw-pc6f'} | null | {'https://github.com/tensorflow/tensorflow/commit/7cf73a2274732c9d82af51c2bc2cf90d13cd7e6d'} | {'https://github.com/tensorflow/tensorflow/commit/7cf73a2274732c9d82af51c2bc2cf90d13cd7e6d'} |
GHSA | GHSA-5xwc-mrhx-5g3m | Reference binding to nullptr in `MatrixDiagV*` ops | ### Impact
An attacker can cause undefined behavior via binding a reference to null pointer in all operations of type `tf.raw_ops.MatrixDiagV*`:
```python
import tensorflow as tf
tf.raw_ops.MatrixDiagV3(
diagonal=[1,0],
k=[],
num_rows=[1,2,3],
num_cols=[4,5],
padding_value=[],
align='RIGHT_RIGHT')
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/linalg/matrix_diag_op.cc) has incomplete validation that the value of `k` is a valid tensor. We have check that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong:
```cc
auto& diag_index = context->input(1);
...
lower_diag_index = diag_index.flat<int32>()(0);
```
### Patches
We have patched the issue in GitHub commit [f2a673bd34f0d64b8e40a551ac78989d16daad09](https://github.com/tensorflow/tensorflow/commit/f2a673bd34f0d64b8e40a551ac78989d16daad09).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-37657'} | 2021-08-25T14:42:52Z | 2021-08-25T14:42:52Z | HIGH | 7.1 | {'CWE-824'} | {'https://github.com/advisories/GHSA-5xwc-mrhx-5g3m', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37657', 'https://github.com/tensorflow/tensorflow/commit/f2a673bd34f0d64b8e40a551ac78989d16daad09', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-5xwc-mrhx-5g3m'} | null | {'https://github.com/tensorflow/tensorflow/commit/f2a673bd34f0d64b8e40a551ac78989d16daad09'} | {'https://github.com/tensorflow/tensorflow/commit/f2a673bd34f0d64b8e40a551ac78989d16daad09'} |
GHSA | GHSA-hrf4-hcpc-3345 | Denial of service in microweber | Microweber is drag and drop website builder and CMS with E-commerce. The microweber prior 1.2.12 application allows large characters to insert in the input field "post title" which can allow attackers to cause a Denial of Service (DoS) via a crafted HTTP request. The post title input can be limited to 500 characters or max 1000 characters as a workaround. | {'CVE-2022-0961'} | 2022-03-25T17:09:25Z | 2022-03-16T00:00:48Z | HIGH | 7.1 | {'CWE-190'} | {'https://github.com/microweber/microweber/commit/f7acbd075dff4825b35b597b74958de9edce67fc', 'https://github.com/advisories/GHSA-hrf4-hcpc-3345', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0961', 'https://huntr.dev/bounties/cdf00e14-38a7-4b6b-9bb4-3a71bf24e436'} | null | {'https://github.com/microweber/microweber/commit/f7acbd075dff4825b35b597b74958de9edce67fc'} | {'https://github.com/microweber/microweber/commit/f7acbd075dff4825b35b597b74958de9edce67fc'} |
GHSA | GHSA-84px-q68r-2fc9 | Privilege escalation in the Sulu Admin panel | ### Impact
Impacted are only users which already have access to the admin UI. Over the API it was possible for them to give themselves permissions to areas which they did not already had. This issue was introduced in 2.0.0-RC1 with the new ProfileController putAction.
### Patches
The versions have been patched in 2.2.18, 2.3.8 and 2.4.0.
### Workarounds
Patching the ProfileController of affected sulu versions yourself by overwriting it.
### References
_Are there any links users can visit to find out more?_
Currently not.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [sulu/sulu repo](https://github.com/sulu/sulu/issues)
* Email us at [security@sulu.io](mailto:security@sulu.io)
| {'CVE-2021-43835'} | 2021-12-16T14:08:57Z | 2021-12-15T22:55:16Z | HIGH | 7.2 | {'CWE-269'} | {'https://github.com/sulu/sulu/security/advisories/GHSA-84px-q68r-2fc9', 'https://github.com/sulu/sulu/commit/30bf8b5a4f83b6f2171a696011757d095edaa28a', 'https://github.com/advisories/GHSA-84px-q68r-2fc9', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43835'} | null | {'https://github.com/sulu/sulu/commit/30bf8b5a4f83b6f2171a696011757d095edaa28a'} | {'https://github.com/sulu/sulu/commit/30bf8b5a4f83b6f2171a696011757d095edaa28a'} |
GHSA | GHSA-vw2g-5827-m9fp | 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-1335, CVE-2019-1366. | {'CVE-2019-1308'} | 2021-03-29T20:55:52Z | 2021-03-29T20:55:52Z | HIGH | 7.5 | {'CWE-787'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-1308', 'https://github.com/advisories/GHSA-vw2g-5827-m9fp', 'https://github.com/chakra-core/ChakraCore/commit/64376deca69126c2bb05cd87bd5c073aedaf5f9c', 'https://github.com/chakra-core/ChakraCore/commit/cc871514deeaeaedb5b757c2ca8cd4ab9abccb5d', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1308'} | null | {'https://github.com/chakra-core/ChakraCore/commit/cc871514deeaeaedb5b757c2ca8cd4ab9abccb5d', 'https://github.com/chakra-core/ChakraCore/commit/64376deca69126c2bb05cd87bd5c073aedaf5f9c'} | {'https://github.com/chakra-core/ChakraCore/commit/64376deca69126c2bb05cd87bd5c073aedaf5f9c', 'https://github.com/chakra-core/ChakraCore/commit/cc871514deeaeaedb5b757c2ca8cd4ab9abccb5d'} |
GHSA | GHSA-5q88-cjfq-g2mh | codecov NPM module allows remote attackers to execute arbitrary commands | codecov-node npm module before 3.6.5 allows remote attackers to execute arbitrary commands.The value provided as part of the gcov-root argument is executed by the exec function within lib/codecov.js. This vulnerability exists due to an incomplete fix of CVE-2020-7596. | {'CVE-2020-7597'} | 2021-08-19T17:22:07Z | 2020-02-19T17:29:39Z | HIGH | 8.8 | {'CWE-78'} | {'https://github.com/advisories/GHSA-5q88-cjfq-g2mh', 'https://github.com/codecov/codecov-node/commit/02cf13d8b93ac547b5b4c2cfe186b7d874fd234f', 'https://snyk.io/vuln/SNYK-JS-CODECOV-548879', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7597'} | null | {'https://github.com/codecov/codecov-node/commit/02cf13d8b93ac547b5b4c2cfe186b7d874fd234f'} | {'https://github.com/codecov/codecov-node/commit/02cf13d8b93ac547b5b4c2cfe186b7d874fd234f'} |
GHSA | GHSA-75c5-f4gw-38r9 | Multiple vulnerabilities through filename manipulation in Archive_Tar | Archive_Tar through 1.4.10 has :// filename sanitization only to address phar attacks, and thus any other stream-wrapper attack (such as file:// to overwrite files) can still succeed. See: https://github.com/pear/Archive_Tar/issues/33 | {'CVE-2020-28949'} | 2021-09-27T18:45:51Z | 2021-04-22T16:20:59Z | HIGH | 7.8 | {'CWE-74'} | {'http://packetstormsecurity.com/files/161095/PEAR-Archive_Tar-Arbitrary-File-Write.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28949', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VJQQYDAOWHD6RDITDRPHFW7WY6BS3V5N/', 'https://github.com/pear/Archive_Tar/issues/33', 'https://www.drupal.org/sa-core-2020-013', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/42GPGVVFTLJYAKRI75IVB5R45NYQGEUR/', 'https://github.com/advisories/GHSA-75c5-f4gw-38r9', 'https://github.com/pear/Archive_Tar/commit/0670a05fdab997036a3fc3ef113b8f5922e574da', 'https://github.com/FriendsOfPHP/security-advisories/blob/master/pear/archive_tar/CVE-2020-28949.yaml', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NBYZSHYTIOBK6V7C4N7TP6KIKCRKLVWP/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5KSFM672XW3X6BR7TVKRD63SLZGKK437/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4V35LBRM6HBCXBVCITKQ4UEBTXO2EG7B/', 'https://www.debian.org/security/2020/dsa-4817', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KWM4CTMEGAC4I2CHYNJVSROY4CVXVEUT/', 'https://lists.debian.org/debian-lts-announce/2020/11/msg00045.html', 'https://security.gentoo.org/glsa/202101-23'} | null | {'https://github.com/pear/Archive_Tar/commit/0670a05fdab997036a3fc3ef113b8f5922e574da'} | {'https://github.com/pear/Archive_Tar/commit/0670a05fdab997036a3fc3ef113b8f5922e574da'} |
GHSA | GHSA-vcgf-vmpc-ph79 | Improper Access Control in microweber | Improper Access Control in Packagist microweber/microweber prior to 1.2.11. | {'CVE-2022-0277'} | 2022-01-27T18:30:42Z | 2022-01-21T18:06:16Z | MODERATE | 6.5 | {'CWE-284', 'CWE-269'} | {'https://github.com/advisories/GHSA-vcgf-vmpc-ph79', 'https://github.com/microweber/microweber/commit/e680e134a4215c979bfd2eaf58336be34c8fc6e6', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0277', 'https://huntr.dev/bounties/0e776f3d-35b1-4a9e-8fe8-91e46c0d6316'} | null | {'https://github.com/microweber/microweber/commit/e680e134a4215c979bfd2eaf58336be34c8fc6e6'} | {'https://github.com/microweber/microweber/commit/e680e134a4215c979bfd2eaf58336be34c8fc6e6'} |
GHSA | GHSA-2cjf-w7c4-fhf6 | Cross-site Scripting in Beanstalk console | Beanstalk console (ptrofimov/beanstalk_console) prior to 1.7.14 is vulnerable to cross-site scripting. | {'CVE-2022-0539'} | 2022-02-11T21:08:35Z | 2022-02-10T00:00:30Z | MODERATE | 6.3 | {'CWE-79'} | {'https://github.com/advisories/GHSA-2cjf-w7c4-fhf6', 'https://github.com/ptrofimov/beanstalk_console/commit/5aea5f912f6e6d19dedb1fdfc25a29a2e1fc1694', 'https://huntr.dev/bounties/5f41b182-dda2-4c6f-9668-2a9afaed53af', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0539'} | null | {'https://github.com/ptrofimov/beanstalk_console/commit/5aea5f912f6e6d19dedb1fdfc25a29a2e1fc1694'} | {'https://github.com/ptrofimov/beanstalk_console/commit/5aea5f912f6e6d19dedb1fdfc25a29a2e1fc1694'} |
GHSA | GHSA-gh8h-7j2j-qv4f | Incomplete validation in `tf.summary.create_file_writer` | ### Impact
If `tf.summary.create_file_writer` is called with non-scalar arguments code crashes due to a `CHECK`-fail.
```python
import tensorflow as tf
import numpy as np
tf.summary.create_file_writer(logdir='', flush_millis=np.ones((1,2)))
```
### Patches
We have patched the issue in GitHub commit [874bda09e6702cd50bac90b453b50bcc65b2769e](https://github.com/tensorflow/tensorflow/commit/874bda09e6702cd50bac90b453b50bcc65b2769e) (merging [#51715](https://github.com/tensorflow/tensorflow/pull/51715)).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46909). | {'CVE-2021-41200'} | 2021-11-10T19:31:16Z | 2021-11-10T19:31:16Z | MODERATE | 5.5 | {'CWE-617'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-41200', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-gh8h-7j2j-qv4f', 'https://github.com/tensorflow/tensorflow/commit/874bda09e6702cd50bac90b453b50bcc65b2769e', 'https://github.com/advisories/GHSA-gh8h-7j2j-qv4f', 'https://github.com/tensorflow/tensorflow/issues/46909'} | null | {'https://github.com/tensorflow/tensorflow/commit/874bda09e6702cd50bac90b453b50bcc65b2769e'} | {'https://github.com/tensorflow/tensorflow/commit/874bda09e6702cd50bac90b453b50bcc65b2769e'} |
GHSA | GHSA-g753-jx37-7xwh | ECDSA signature vulnerability of Minerva timing attack in jsrsasign | ### Impact
ECDSA side-channel attack named [Minerava](https://minerva.crocs.fi.muni.cz/) have been found and it was found that it affects to jsrsasign.
Execution time of thousands signature generation have been observed then EC private key which is scalar value may be recovered since point and scalar multiplication time depends on bits of scalar. In jsrsasign 8.0.13 or later, execution time of EC point and scalar multiplication is almost constant and fixed for the issue.
- Minerva is one of timing attack or side channel attack for EC.
- If you don't use ECDSA class, you are not affected the vulnerability.
- The vulnerability is that attacker may guess private key by checking processing time of EC key generation or ECDSA signing.
- The cause issue is that point multiplication processing time in ECDSA signing is depends on private key value.
- After 8.0.13, processing time of point multiplication in ECDSA signing have become constant for key value in theory.
### Patches
Users using ECDSA signature generation should upgrade to 8.0.13 or later.
### Workarounds
There is no workarounds in jsrsasign. Update jsrsasign or use other ECDSA library.
### ACKNOWLEDGEMENT
Thanks to Jan Jancar @J08nY, Petr Svenda and Vladimir Sedlacek of Masaryk University in Czech Republic to find and report this vulnerability.
### References
https://minerva.crocs.fi.muni.cz/
https://www.npmjs.com/advisories/1505
https://github.com/kjur/jsrsasign/issues/411 | null | 2021-09-22T18:43:42Z | 2020-06-30T16:05:08Z | MODERATE | 5.9 | {'CWE-362'} | {'https://github.com/kjur/jsrsasign/security/advisories/GHSA-g753-jx37-7xwh', 'https://www.npmjs.com/advisories/1505', 'https://snyk.io/vuln/SNYK-JS-JSRSASIGN-561755', 'https://github.com/advisories/GHSA-g753-jx37-7xwh', 'https://github.com/kjur/jsrsasign/commit/9dcb89c57408a3d4b5b66aa9138426bd92819e73', 'https://github.com/kjur/jsrsasign/issues/411', 'https://minerva.crocs.fi.muni.cz/', 'https://github.com/kjur/jsrsasign/releases/tag/8.0.13'} | null | {'https://github.com/kjur/jsrsasign/commit/9dcb89c57408a3d4b5b66aa9138426bd92819e73'} | {'https://github.com/kjur/jsrsasign/commit/9dcb89c57408a3d4b5b66aa9138426bd92819e73'} |
GHSA | GHSA-x3rq-r3cm-5vc4 | Business Logic Errors in Publify | Publify (formerly known as Typo) prior to version 9.2.7 is vulnerable to business logic errors. | {'CVE-2022-0524'} | 2022-02-14T22:34:47Z | 2022-02-09T00:00:27Z | HIGH | 7.5 | null | {'https://huntr.dev/bounties/bfffae58-b3cd-4e0e-b1f2-3db387a22c3d', 'https://github.com/publify/publify/releases/tag/v9.2.7', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0524', 'https://github.com/advisories/GHSA-x3rq-r3cm-5vc4', 'https://github.com/publify/publify/commit/16fceecadbe80ab0ef846b62a12dc7bfff10b8c5'} | null | {'https://github.com/publify/publify/commit/16fceecadbe80ab0ef846b62a12dc7bfff10b8c5'} | {'https://github.com/publify/publify/commit/16fceecadbe80ab0ef846b62a12dc7bfff10b8c5'} |
GHSA | GHSA-2m8v-572m-ff2v | Command Injection Vulnerability | ### Impact
command injection vulnerability
### Patches
Problem was fixed with a parameter check. Please upgrade to version >= 5.3.1
### Workarounds
If you cannot upgrade, be sure to check or sanitize service parameters that are passed to si.inetLatency(), si.inetChecksite(), si.services(), si.processLoad() ... do only allow strings, reject any arrays. String sanitation works as expected. | {'CVE-2021-21315'} | 2021-03-19T17:54:20Z | 2021-02-16T16:51:04Z | MODERATE | 0 | {'CWE-78'} | {'https://security.netapp.com/advisory/ntap-20210312-0007/', 'https://www.npmjs.com/package/systeminformation', 'https://lists.apache.org/thread.html/r8afea9a83ed568f2647cccc6d8d06126f9815715ddf9a4d479b26b05@%3Cissues.cordova.apache.org%3E', 'https://github.com/advisories/GHSA-2m8v-572m-ff2v', 'https://github.com/sebhildebrandt/systeminformation/commit/07daa05fb06f24f96297abaa30c2ace8bfd8b525', 'https://github.com/sebhildebrandt/systeminformation/security/advisories/GHSA-2m8v-572m-ff2v', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21315'} | null | {'https://github.com/sebhildebrandt/systeminformation/commit/07daa05fb06f24f96297abaa30c2ace8bfd8b525'} | {'https://github.com/sebhildebrandt/systeminformation/commit/07daa05fb06f24f96297abaa30c2ace8bfd8b525'} |
GHSA | GHSA-7mg7-m5c3-3hqj | Data races in unicycle | Affected versions of this crate unconditionally implemented `Send` & `Sync` for types `PinSlab<T>` & `Unordered<T, S>`. This allows sending non-Send types to other threads and concurrently accessing non-Sync types from multiple threads.
This can result in a data race & memory corruption when types that provide internal mutability without synchronization are contained within `PinSlab<T>` or `Unordered<T, S>` and accessed concurrently from multiple threads.
The flaw was corrected in commits 92f40b4 & 6a6c367 by adding trait bound `T: Send` to `Send` impls for `PinSlab<T>` & `Unordered<T, S>` and adding `T: Sync` to `Sync` impls for `PinSlab<T>` & `Unordered<T, S>`.
| null | 2021-08-25T21:00:39Z | 2021-08-25T21:00:39Z | MODERATE | 0 | {'CWE-362'} | {'https://github.com/udoprog/unicycle/commit/6a6c367a0c25f86f998fa315ea90c328f685b194', 'https://github.com/udoprog/unicycle/commit/92f40b4a2c671553dfa96feacff0265206c44ce5', 'https://rustsec.org/advisories/RUSTSEC-2020-0116.html', 'https://github.com/udoprog/unicycle/issues/8', 'https://github.com/advisories/GHSA-7mg7-m5c3-3hqj'} | null | {'https://github.com/udoprog/unicycle/commit/6a6c367a0c25f86f998fa315ea90c328f685b194', 'https://github.com/udoprog/unicycle/commit/92f40b4a2c671553dfa96feacff0265206c44ce5'} | {'https://github.com/udoprog/unicycle/commit/6a6c367a0c25f86f998fa315ea90c328f685b194', 'https://github.com/udoprog/unicycle/commit/92f40b4a2c671553dfa96feacff0265206c44ce5'} |
GHSA | GHSA-vfrc-ggmc-5jwv | Cross-site Scripting in django-helpdesk | django-helpdesk is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') | {'CVE-2021-3950'} | 2021-11-24T19:43:03Z | 2021-11-23T17:55:46Z | HIGH | 8.8 | {'CWE-79'} | {'https://github.com/advisories/GHSA-vfrc-ggmc-5jwv', 'https://huntr.dev/bounties/4d7a5fdd-b2de-467a-ade0-3f2fb386638e', 'https://github.com/django-helpdesk/django-helpdesk/commit/04483bdac3b5196737516398b5ce0383875a5c60', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3950', 'https://github.com/django-helpdesk/django-helpdesk/releases/tag/0.3.2'} | null | {'https://github.com/django-helpdesk/django-helpdesk/commit/04483bdac3b5196737516398b5ce0383875a5c60'} | {'https://github.com/django-helpdesk/django-helpdesk/commit/04483bdac3b5196737516398b5ce0383875a5c60'} |
GHSA | GHSA-xwhf-g6j5-j5gc | Float cast overflow undefined behavior | ### Impact
When the `boxes` argument of `tf.image.crop_and_resize` has a very large value, the CPU kernel implementation receives it as a C++ `nan` floating point value. Attempting to operate on this is undefined behavior which later produces a segmentation fault.
### Patches
We have patched the issue in c0319231333f0f16e1cc75ec83660b01fedd4182 and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.
### 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 in #42129 | {'CVE-2020-15266'} | 2021-08-26T15:20:48Z | 2020-11-13T17:18:29Z | LOW | 3.7 | {'CWE-119'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15266', 'https://github.com/advisories/GHSA-xwhf-g6j5-j5gc', 'https://github.com/tensorflow/tensorflow/pull/42143/commits/3ade2efec2e90c6237de32a19680caaa3ebc2845', 'https://github.com/tensorflow/tensorflow/issues/42129', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-xwhf-g6j5-j5gc'} | null | {'https://github.com/tensorflow/tensorflow/pull/42143/commits/3ade2efec2e90c6237de32a19680caaa3ebc2845'} | {'https://github.com/tensorflow/tensorflow/pull/42143/commits/3ade2efec2e90c6237de32a19680caaa3ebc2845'} |
GHSA | GHSA-cwv3-863g-39vx | Stack overflow due to looping TFLite subgraph | ### Impact
TFlite graphs must not have loops between nodes. However, this condition was not checked and an attacker could craft models that would result in infinite loop during evaluation. In certain cases, the infinite loop would be replaced by stack overflow due to too many recursive calls.
For example, the [`While` implementation](https://github.com/tensorflow/tensorflow/blob/106d8f4fb89335a2c52d7c895b7a7485465ca8d9/tensorflow/lite/kernels/while.cc) could be tricked into a scneario where both the body and the loop subgraphs are the same. Evaluating one of the subgraphs means calling the `Eval` function for the other and this quickly exhaust all stack space.
### Patches
We have patched the issue in GitHub commit [9c1dc920d8ffb4893d6c9d27d1f039607b326743](https://github.com/tensorflow/tensorflow/commit/9c1dc920d8ffb4893d6c9d27d1f039607b326743) (for the `While` operator) and in GitHub commit [c6173f5fe66cdbab74f4f869311fe6aae2ba35f4](https://github.com/tensorflow/tensorflow/commit/c6173f5fe66cdbab74f4f869311fe6aae2ba35f4) (in general).
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-29591'} | 2022-04-26T18:09:15Z | 2021-05-21T14:26:56Z | HIGH | 7.3 | {'CWE-835', 'CWE-674'} | {'https://github.com/tensorflow/tensorflow/commit/c6173f5fe66cdbab74f4f869311fe6aae2ba35f4', 'https://github.com/tensorflow/tensorflow/commit/9c1dc920d8ffb4893d6c9d27d1f039607b326743', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29591', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cwv3-863g-39vx', 'https://github.com/advisories/GHSA-cwv3-863g-39vx'} | null | {'https://github.com/tensorflow/tensorflow/commit/c6173f5fe66cdbab74f4f869311fe6aae2ba35f4', 'https://github.com/tensorflow/tensorflow/commit/9c1dc920d8ffb4893d6c9d27d1f039607b326743'} | {'https://github.com/tensorflow/tensorflow/commit/c6173f5fe66cdbab74f4f869311fe6aae2ba35f4', 'https://github.com/tensorflow/tensorflow/commit/9c1dc920d8ffb4893d6c9d27d1f039607b326743'} |
GHSA | GHSA-4hvv-7x94-7vq8 | Null dereference in Grappler's `TrySimplify` | ### Impact
The implementation of [`TrySimplify`](https://github.com/tensorflow/tensorflow/blob/c22d88d6ff33031aa113e48aa3fc9aa74ed79595/tensorflow/core/grappler/optimizers/arithmetic_optimizer.cc#L390-L401) has undefined behavior due to dereferencing a null pointer in corner cases that
result in optimizing a node with no inputs.
### Patches
We have patched the issue in GitHub commit [e6340f0665d53716ef3197ada88936c2a5f7a2d3](https://github.com/tensorflow/tensorflow/commit/e6340f0665d53716ef3197ada88936c2a5f7a2d3).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. | {'CVE-2021-29616'} | 2021-05-21T14:28:47Z | 2021-05-21T14:28:47Z | LOW | 2.5 | {'CWE-476'} | {'https://github.com/tensorflow/tensorflow/commit/e6340f0665d53716ef3197ada88936c2a5f7a2d3', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-4hvv-7x94-7vq8', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29616', 'https://github.com/advisories/GHSA-4hvv-7x94-7vq8'} | null | {'https://github.com/tensorflow/tensorflow/commit/e6340f0665d53716ef3197ada88936c2a5f7a2d3'} | {'https://github.com/tensorflow/tensorflow/commit/e6340f0665d53716ef3197ada88936c2a5f7a2d3'} |
GHSA | GHSA-rpq8-mmwh-q9hm | Directory traversal in Eclipse Mojarra | Directory traversal in Eclipse Mojarra before 2.3.14 allows attackers to read arbitrary files via the loc parameter or con parameter. | {'CVE-2020-6950'} | 2022-04-22T15:47:12Z | 2021-09-01T18:23:58Z | HIGH | 7.5 | {'CWE-22'} | {'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://github.com/eclipse-ee4j/mojarra/issues/4571', 'https://bugs.eclipse.org/bugs/show_bug.cgi?id=550943', 'https://nvd.nist.gov/vuln/detail/CVE-2020-6950', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://github.com/advisories/GHSA-rpq8-mmwh-q9hm', 'https://github.com/eclipse-ee4j/mojarra/commit/cefbb9447e7be560e59da2da6bd7cb93776f7741'} | null | {'https://github.com/eclipse-ee4j/mojarra/commit/cefbb9447e7be560e59da2da6bd7cb93776f7741'} | {'https://github.com/eclipse-ee4j/mojarra/commit/cefbb9447e7be560e59da2da6bd7cb93776f7741'} |
GHSA | GHSA-g89m-3wjw-h857 | Low severity vulnerability that affects puppet | Directory traversal vulnerability in lib/puppet/reports/store.rb in Puppet before 2.6.17 and 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, when Delete is enabled in auth.conf, allows remote authenticated users to delete arbitrary files on the puppet master server via a .. (dot dot) in a node name. | {'CVE-2012-3865'} | 2021-09-10T20:29:08Z | 2017-10-24T18:33:37Z | LOW | 0 | {'CWE-22'} | {'http://lists.opensuse.org/opensuse-updates/2012-07/msg00036.html', 'https://github.com/puppetlabs/puppet/commit/554eefc55f57ed2b76e5ee04d8f194d36f6ee67f', 'https://bugzilla.redhat.com/show_bug.cgi?id=839131', 'http://www.debian.org/security/2012/dsa-2511', 'http://www.ubuntu.com/usn/USN-1506-1', 'http://lists.opensuse.org/opensuse-security-announce/2012-08/msg00006.html', 'http://puppetlabs.com/security/cve/cve-2012-3865/', 'https://nvd.nist.gov/vuln/detail/CVE-2012-3865', 'https://github.com/advisories/GHSA-g89m-3wjw-h857', 'http://secunia.com/advisories/50014', 'https://github.com/puppetlabs/puppet/commit/d80478208d79a3e6d6cb1fbc525e24817fe8c4c6'} | null | {'https://github.com/puppetlabs/puppet/commit/d80478208d79a3e6d6cb1fbc525e24817fe8c4c6', 'https://github.com/puppetlabs/puppet/commit/554eefc55f57ed2b76e5ee04d8f194d36f6ee67f'} | {'https://github.com/puppetlabs/puppet/commit/554eefc55f57ed2b76e5ee04d8f194d36f6ee67f', 'https://github.com/puppetlabs/puppet/commit/d80478208d79a3e6d6cb1fbc525e24817fe8c4c6'} |
GHSA | GHSA-35m5-8cvj-8783 | Improper hashing in enrocrypt | ### Impact
The vulnerability is we used MD5 hashing Algorithm In our hashing file. If anyone who is a beginner(and doesn't know about hashes) can face problems as MD5 is considered a Insecure Hashing Algorithm.
### Patches
The vulnerability is patched in v1.1.4 of the product, the users can upgrade to version 1.1.4.
### Workarounds
If u specifically want a version and don't want to upgrade, you can remove the `MD5` hashing function from the file `hashing.py` and this vulnerability will be gone
### References
https://www.cybersecurity-help.cz/vdb/cwe/916/
https://www.cybersecurity-help.cz/vdb/cwe/327/
https://www.cybersecurity-help.cz/vdb/cwe/328/
https://www.section.io/engineering-education/what-is-md5/
https://www.johndcook.com/blog/2019/01/24/reversing-an-md5-hash/
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [**Enrocrypt's Official Repo**](http://www.github.com/Morgan-Phoenix/EnroCrypt)
* Create a Discussion in [**Enrocrypt's Official Repo**](http://www.github.com/Morgan-Phoenix/EnroCrypt)
| {'CVE-2021-39182'} | 2021-11-10T16:28:46Z | 2021-11-10T16:28:46Z | HIGH | 7.5 | {'CWE-327', 'CWE-916', 'CWE-328'} | {'https://github.com/advisories/GHSA-35m5-8cvj-8783', 'https://github.com/Morgan-Phoenix/EnroCrypt/security/advisories/GHSA-35m5-8cvj-8783', 'https://github.com/Morgan-Phoenix/EnroCrypt/commit/e652d56ac60eadfc26489ab83927af13a9b9d8ce', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39182'} | null | {'https://github.com/Morgan-Phoenix/EnroCrypt/commit/e652d56ac60eadfc26489ab83927af13a9b9d8ce'} | {'https://github.com/Morgan-Phoenix/EnroCrypt/commit/e652d56ac60eadfc26489ab83927af13a9b9d8ce'} |
GHSA | GHSA-fxqh-cfjm-fp93 | Division by 0 in `Reverse` | ### Impact
An attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.Reverse`:
```python
import tensorflow as tf
tensor_input = tf.constant([], shape=[0, 1, 1], dtype=tf.int32)
dims = tf.constant([False, True, False], shape=[3], dtype=tf.bool)
tf.raw_ops.Reverse(tensor=tensor_input, dims=dims)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/36229ea9e9451dac14a8b1f4711c435a1d84a594/tensorflow/core/kernels/reverse_op.cc#L75-L76) performs a division based on the first dimension of the tensor argument:
```cc
const int64 N = input.dim_size(0);
const int64 cost_per_unit = input.NumElements() / N;
```
Since this is controlled by the user, an attacker can trigger a denial of service.
### Patches
We have patched the issue in GitHub commit [4071d8e2f6c45c1955a811fee757ca2adbe462c1](https://github.com/tensorflow/tensorflow/commit/4071d8e2f6c45c1955a811fee757ca2adbe462c1).
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-29556'} | 2021-05-21T14:24:39Z | 2021-05-21T14:24:39Z | LOW | 2.5 | {'CWE-369'} | {'https://github.com/tensorflow/tensorflow/commit/4071d8e2f6c45c1955a811fee757ca2adbe462c1', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29556', 'https://github.com/advisories/GHSA-fxqh-cfjm-fp93', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-fxqh-cfjm-fp93'} | null | {'https://github.com/tensorflow/tensorflow/commit/4071d8e2f6c45c1955a811fee757ca2adbe462c1'} | {'https://github.com/tensorflow/tensorflow/commit/4071d8e2f6c45c1955a811fee757ca2adbe462c1'} |
GHSA | GHSA-xc3p-ff3m-f46v | Insecure input handling in Flask-Cors | An issue was discovered in Flask-CORS (aka CORS Middleware for Flask) before 3.0.9. It allows ../ directory traversal to access private resources because resource matching does not ensure that pathnames are in a canonical format. | {'CVE-2020-25032'} | 2022-04-29T20:27:29Z | 2021-05-06T18:51:48Z | HIGH | 7.5 | {'CWE-22'} | {'https://github.com/corydolphin/flask-cors/commit/67c4b2cc98ae87cf1fa7df4f97fd81b40c79b895', 'http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00048.html', 'http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00032.html', 'https://www.debian.org/security/2020/dsa-4775', 'https://github.com/advisories/GHSA-xc3p-ff3m-f46v', 'https://nvd.nist.gov/vuln/detail/CVE-2020-25032', 'http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00039.html', 'https://github.com/corydolphin/flask-cors/releases/tag/3.0.9', 'http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00028.html'} | null | {'https://github.com/corydolphin/flask-cors/commit/67c4b2cc98ae87cf1fa7df4f97fd81b40c79b895'} | {'https://github.com/corydolphin/flask-cors/commit/67c4b2cc98ae87cf1fa7df4f97fd81b40c79b895'} |
GHSA | GHSA-f599-5m7p-hcpf | Moderate severity vulnerability that affects grape | The grape rubygem suffers from a cross-site scripting (XSS) vulnerability via "format" parameter. | {'CVE-2018-3769'} | 2021-01-08T18:54:26Z | 2018-08-13T20:45:32Z | MODERATE | 0 | {'CWE-79'} | {'https://github.com/ruby-grape/grape/pull/1763', 'https://github.com/advisories/GHSA-f599-5m7p-hcpf', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3769', 'https://github.com/ruby-grape/grape/issues/1762', 'https://github.com/ruby-grape/grape/commit/6876b71efc7b03f7ce1be3f075eaa4e7e6de19af'} | null | {'https://github.com/ruby-grape/grape/commit/6876b71efc7b03f7ce1be3f075eaa4e7e6de19af'} | {'https://github.com/ruby-grape/grape/commit/6876b71efc7b03f7ce1be3f075eaa4e7e6de19af'} |
GHSA | GHSA-wqvq-5m8c-6g24 | CRLF injection | urllib3 before 1.25.9 allows CRLF injection if the attacker controls the HTTP request method, as demonstrated by inserting CR and LF control characters in the first argument of putrequest(). NOTE: this is similar to CVE-2020-26116. | {'CVE-2020-26137'} | 2021-10-21T20:49:58Z | 2021-06-18T18:46:43Z | MODERATE | 6.5 | {'CWE-74'} | {'https://bugs.python.org/issue39603', 'https://github.com/urllib3/urllib3/commit/1dd69c5c5982fae7c87a620d487c2ebf7a6b436b', 'https://github.com/urllib3/urllib3/pull/1800', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26137', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://lists.debian.org/debian-lts-announce/2021/06/msg00015.html', 'https://github.com/advisories/GHSA-wqvq-5m8c-6g24', 'https://usn.ubuntu.com/4570-1/'} | null | {'https://github.com/urllib3/urllib3/commit/1dd69c5c5982fae7c87a620d487c2ebf7a6b436b'} | {'https://github.com/urllib3/urllib3/commit/1dd69c5c5982fae7c87a620d487c2ebf7a6b436b'} |
GHSA | GHSA-f865-m6cq-j9vx | ReDOS in Mpmath | A Regular Expression Denial of Service (ReDOS) vulnerability was discovered in Mpmath v1.0.0 when the mpmathify function is called. | {'CVE-2021-29063'} | 2021-11-18T15:17:54Z | 2021-08-09T20:44:51Z | HIGH | 7.5 | {'CWE-770'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29063', 'https://github.com/fredrik-johansson/mpmath/issues/548', 'https://github.com/fredrik-johansson/mpmath/commit/c811b37c65a4372a7ce613111d2a508c204f9833', 'https://github.com/yetingli/PoCs/blob/main/CVE-2021-29063/Mpmath.md', 'https://www.npmjs.com/package/hosted-git-info', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MS2U6GLXQSRZJE2HVUAUMVFR2DWQLCZG/', 'https://github.com/npm/hosted-git-info/pull/76', 'https://github.com/yetingli/SaveResults/blob/main/js/hosted-git-info.js', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3M5O55E7VUDMXCPQR6MQTOIFDKHP36AA/', 'https://github.com/advisories/GHSA-f865-m6cq-j9vx', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EIUX3XWY2K3MSO7QXMZXQQYAURARSPC5/'} | null | {'https://github.com/fredrik-johansson/mpmath/commit/c811b37c65a4372a7ce613111d2a508c204f9833'} | {'https://github.com/fredrik-johansson/mpmath/commit/c811b37c65a4372a7ce613111d2a508c204f9833'} |
GHSA | GHSA-f768-8pvq-mm6r | Business Logic Errors in dolibarr/dolibarr | Dolibarr 14.0.5 and prior versions are vulnerable to Business Logic Errors. | {'CVE-2022-0414'} | 2022-02-07T21:10:24Z | 2022-02-01T22:01:47Z | MODERATE | 4.3 | null | {'https://github.com/dolibarr/dolibarr/commit/37fb02ee760cfff18c795ba468da1ba1c53f4684', 'https://huntr.dev/bounties/76f3b405-9f5d-44b1-8434-b52b56ee395f', 'https://github.com/advisories/GHSA-f768-8pvq-mm6r', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0414'} | null | {'https://github.com/dolibarr/dolibarr/commit/37fb02ee760cfff18c795ba468da1ba1c53f4684'} | {'https://github.com/dolibarr/dolibarr/commit/37fb02ee760cfff18c795ba468da1ba1c53f4684'} |
GHSA | GHSA-hgjr-632x-qpp3 | Cross-site scripting vulnerability in file upload | There is a cross-site scripting vulnerability in file upload on the management system of baserCMS.
This is a vulnerability that needs to be addressed when the management system is used by an unspecified number of users.
If you are eligible, please update to the new version as soon as possible.
### Target
baserCMS 4.5.1 and earlier versions
### Vulnerability
Execution of malicious JavaScript code may alter the display of the page or leak cookie information.
### Countermeasures
Update to the latest version of baserCMS
Please refer to the next page for details.
https://basercms.net/security/JVN_14134801 | {'CVE-2021-39136'} | 2021-08-30T16:18:59Z | 2021-08-30T16:18:59Z | HIGH | 8.7 | {'CWE-79'} | {'http://jvn.jp/en/jp/JVN14134801/index.html', 'https://github.com/baserproject/basercms/commit/568d4cab5ba1cdee7bbf0133c676d02a98f6d7bc', 'https://github.com/baserproject/basercms/security/advisories/GHSA-hgjr-632x-qpp3', 'https://github.com/advisories/GHSA-hgjr-632x-qpp3', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39136', 'https://basercms.net/security/JVN_14134801'} | null | {'https://github.com/baserproject/basercms/commit/568d4cab5ba1cdee7bbf0133c676d02a98f6d7bc'} | {'https://github.com/baserproject/basercms/commit/568d4cab5ba1cdee7bbf0133c676d02a98f6d7bc'} |
GHSA | GHSA-2473-9hgq-j7xw | Cross-Site Scripting in Wagtail | ### Impact
When a form page type is made available to Wagtail editors through the `wagtail.contrib.forms` app, and the page template is built using Django's standard form rendering helpers such as `form.as_p` ([as directed in the documentation](https://docs.wagtail.io/en/stable/reference/contrib/forms/index.html#usage)), any HTML tags used within a form field's help text will be rendered unescaped in the page. Allowing HTML within help text is [an intentional design decision](https://docs.djangoproject.com/en/3.0/ref/models/fields/#django.db.models.Field.help_text) by Django; however, as a matter of policy Wagtail does not allow editors to insert arbitrary HTML by default, as this could potentially be used to carry out cross-site scripting attacks, including privilege escalation. This functionality should therefore not have been made available to editor-level users.
The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.
### Patches
Patched versions have been released as Wagtail 2.7.4 (for the LTS 2.7 branch) and Wagtail 2.9.3 (for the current 2.9 branch). In these versions, help text will be escaped to prevent the inclusion of HTML tags. Site owners who wish to re-enable the use of HTML within help text (and are willing to accept the risk of this being exploited by editors) may set `WAGTAILFORMS_HELP_TEXT_ALLOW_HTML = True` in their configuration settings.
### Workarounds
Site owners who are unable to upgrade to the new versions can secure their form page templates by [rendering forms field-by-field as per Django's documentation](https://docs.djangoproject.com/en/3.0/topics/forms/#looping-over-the-form-s-fields), but omitting the `|safe` filter when outputting the help text.
### Acknowledgements
Many thanks to Timothy Bautista for reporting this issue.
### For more information
If you have any questions or comments about this advisory:
* Visit Wagtail's [support channels](https://docs.wagtail.io/en/stable/support.html)
* Email us at [security@wagtail.io](mailto:security@wagtail.io) (if you wish to send encrypted email, the public key ID is `0x6ba1e1a86e0f8ce8`) | {'CVE-2020-15118'} | 2022-04-19T19:02:30Z | 2020-07-20T17:50:30Z | MODERATE | 5.7 | {'CWE-79'} | {'https://github.com/advisories/GHSA-2473-9hgq-j7xw', 'https://github.com/wagtail/wagtail/blob/master/docs/releases/2.9.3.rst', 'https://docs.djangoproject.com/en/3.0/ref/models/fields/#django.db.models.Field.help_text', 'https://github.com/wagtail/wagtail/security/advisories/GHSA-2473-9hgq-j7xw', 'https://docs.wagtail.io/en/stable/reference/contrib/forms/index.html#usage', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15118', 'https://github.com/wagtail/wagtail/commit/d9a41e7f24d08c024acc9a3094940199df94db34'} | null | {'https://github.com/wagtail/wagtail/commit/d9a41e7f24d08c024acc9a3094940199df94db34'} | {'https://github.com/wagtail/wagtail/commit/d9a41e7f24d08c024acc9a3094940199df94db34'} |
GHSA | GHSA-9j9m-8wjc-ff96 | Insufficient Session Expiration in apostrophe | Apostrophe CMS versions between 2.63.0 to 3.3.1 affected by an insufficient session expiration vulnerability, which allows unauthenticated remote attackers to hijack recently logged-in users' sessions. | {'CVE-2021-25979'} | 2021-11-19T13:29:28Z | 2021-11-10T17:02:44Z | CRITICAL | 9.8 | {'CWE-613'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-25979', 'https://github.com/advisories/GHSA-9j9m-8wjc-ff96', 'https://github.com/apostrophecms/apostrophe/commit/c211b211f9f4303a77a307cf41aac9b4ef8d2c7c'} | null | {'https://github.com/apostrophecms/apostrophe/commit/c211b211f9f4303a77a307cf41aac9b4ef8d2c7c'} | {'https://github.com/apostrophecms/apostrophe/commit/c211b211f9f4303a77a307cf41aac9b4ef8d2c7c'} |
GHSA | GHSA-x9j7-x98r-r4w2 | Segmentation fault in tensorflow-lite | ### Impact
If a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption.
### Patches
We have patched the issue in d58c96946b and will release patch releases for all versions between 1.15 and 2.3.
We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
### Workarounds
A potential workaround would be to add a custom `Verifier` to the model loading code to ensure that no operator reuses tensors as both inputs and outputs. Care should be taken to check all types of inputs (i.e., constant or variable tensors as well as optional tensors).
### 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 discovered from a variant analysis of [GHSA-cvpc-8phh-8f45](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cvpc-8phh-8f45). | {'CVE-2020-15210'} | 2021-11-19T15:11:28Z | 2020-09-25T18:28:51Z | MODERATE | 6.5 | {'CWE-20', 'CWE-787'} | {'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html', 'https://github.com/tensorflow/tensorflow/commit/d58c96946b2880991d63d1dacacb32f0a4dfa453', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-x9j7-x98r-r4w2', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15210', 'https://github.com/advisories/GHSA-x9j7-x98r-r4w2', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1'} | null | {'https://github.com/tensorflow/tensorflow/commit/d58c96946b2880991d63d1dacacb32f0a4dfa453'} | {'https://github.com/tensorflow/tensorflow/commit/d58c96946b2880991d63d1dacacb32f0a4dfa453'} |
GHSA | GHSA-4pm3-f52j-8ggh | Improper Input Validation in GeoServer | ### Impact
The GeoServer security mechanism can perform an unchecked JNDI lookup, which in turn can be used to perform class deserialization and result in arbitrary code execution. The same can happen while configuring data stores with data sources located in JNDI, or while setting up the disk quota mechanism.
In order to perform any of the above changes, the attack needs to have obtained admin rights and use either the GeoServer GUI, or its REST API.
### Patches
The lookups are going to be restricted in GeoServer 2.21.0, 2.20.4, 2.19.6.
### Workarounds
Protection can be achieved by making the GUI (``geoserver/web``), the REST configuration (``geoserver/rest``) and the embedded GeoWebCache configuration (``geoserver/gwc/rest``) unreachable from remote hosts, in addition to protecting access to the file system where the GeoServer configuration is stored.
| {'CVE-2022-24847'} | 2022-04-28T20:51:26Z | 2022-04-22T20:39:10Z | HIGH | 7.2 | {'CWE-20'} | {'https://github.com/geoserver/geoserver/commit/b94a69943992df999d627b21a4ed056fad4569f8', 'https://github.com/geoserver/geoserver/security/advisories/GHSA-4pm3-f52j-8ggh', 'https://github.com/advisories/GHSA-4pm3-f52j-8ggh', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24847'} | null | {'https://github.com/geoserver/geoserver/commit/b94a69943992df999d627b21a4ed056fad4569f8'} | {'https://github.com/geoserver/geoserver/commit/b94a69943992df999d627b21a4ed056fad4569f8'} |
GHSA | GHSA-hfmf-q43v-2ffj | Improper Key Verification in openpgp | Versions of `openpgp` prior to 4.2.0 are vulnerable to Improper Key Verification. The OpenPGP standard allows signature packets to have subpackets which may be hashed or unhashed. Unhashed subpackets are not cryptographically protected and cannot be trusted. The `openpgp` package does not verify whether a subpacket is hashed. Furthermore, due to the order of parsing a signature packet information from unhashed subpackets overwrites information from hashed subpackets. This may allow an attacker to modify the contents of a key certification signature or revocation signature. Doing so could convince a victim to use an obsolete key for encryption. An attack require a victim to import a manipulated key or update an existing key with a manipulated version.
## Recommendation
Upgrade to version 4.2.0 or later.
If you are upgrading from a version <4.0.0 it is highly recommended to read the `High-Level API Changes` section of the `openpgp` 4.0.0 release: https://github.com/openpgpjs/openpgpjs/releases/tag/v4.0.0 | {'CVE-2019-9154'} | 2021-08-17T22:08:26Z | 2019-08-23T21:42:18Z | HIGH | 7.5 | {'CWE-347'} | {'https://snyk.io/vuln/SNYK-JS-OPENPGP-460247', 'http://packetstormsecurity.com/files/154191/OpenPGP.js-4.2.0-Signature-Bypass-Invalid-Curve-Attack.html', 'https://github.com/openpgpjs/openpgpjs/pull/797', 'https://sec-consult.com/en/blog/advisories/multiple-vulnerabilities-in-openpgp-js/', 'https://nvd.nist.gov/vuln/detail/CVE-2019-9154', 'https://github.com/advisories/GHSA-hfmf-q43v-2ffj', 'https://www.npmjs.com/advisories/1161', 'https://github.com/openpgpjs/openpgpjs/pull/797/commits/47138eed61473e13ee8f05931119d3e10542c5e1', 'https://github.com/openpgpjs/openpgpjs/releases/tag/v4.2.0', 'https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/Studies/Mailvelope_Extensions/Mailvelope_Extensions_pdf.html#download=1'} | null | {'https://github.com/openpgpjs/openpgpjs/pull/797/commits/47138eed61473e13ee8f05931119d3e10542c5e1'} | {'https://github.com/openpgpjs/openpgpjs/pull/797/commits/47138eed61473e13ee8f05931119d3e10542c5e1'} |
GHSA | GHSA-3j7m-hmh3-9jmp | Cross-Site Scripting in sanitize-html | Affected versions of `sanitize-html` do not sanitize input recursively, which may allow an attacker to execute arbitrary Javascript.
## Recommendation
Update to version 1.4.3 or later. | {'CVE-2016-1000237'} | 2021-08-23T15:18:04Z | 2020-04-16T03:14:47Z | MODERATE | 6.1 | {'CWE-79'} | {'https://www.npmjs.com/advisories/135', 'https://github.com/apostrophecms/sanitize-html/issues/29', 'https://nvd.nist.gov/vuln/detail/CVE-2016-1000237', 'https://nodesecurity.io/advisories/135', 'https://github.com/punkave/sanitize-html/issues/29', 'https://raw.githubusercontent.com/distributedweaknessfiling/cvelist/master/2016/1000xxx/CVE-2016-1000237.json', 'https://github.com/apostrophecms/sanitize-html/commit/762fbc7bba389f3f789cc291c1eb2b64f60f2caf', 'https://github.com/advisories/GHSA-3j7m-hmh3-9jmp'} | null | {'https://github.com/apostrophecms/sanitize-html/commit/762fbc7bba389f3f789cc291c1eb2b64f60f2caf'} | {'https://github.com/apostrophecms/sanitize-html/commit/762fbc7bba389f3f789cc291c1eb2b64f60f2caf'} |
GHSA | GHSA-9cq5-xgg4-x477 | SQL Injection in showdoc | Showdoc verions 2.10.2 and prior is vulnerable to SQL injection. A patch is available in the `master` branch of the repository. | {'CVE-2022-0362'} | 2022-02-10T22:30:55Z | 2022-01-27T00:01:15Z | MODERATE | 6.7 | {'CWE-89'} | {'https://github.com/star7th/showdoc/commit/2b34e267e4186125f99bfa420140634ad45801fb', 'https://huntr.dev/bounties/e7c72417-eb8f-416c-8480-be76ac0a9091', 'https://github.com/advisories/GHSA-9cq5-xgg4-x477', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0362'} | null | {'https://github.com/star7th/showdoc/commit/2b34e267e4186125f99bfa420140634ad45801fb'} | {'https://github.com/star7th/showdoc/commit/2b34e267e4186125f99bfa420140634ad45801fb'} |
GHSA | GHSA-29mw-wpgm-hmr9 | Regular Expression Denial of Service (ReDoS) in lodash | All versions of package lodash prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions. Steps to reproduce (provided by reporter Liyuan Chen): var lo = require('lodash'); function build_blank (n) { var ret = "1" for (var i = 0; i < n; i++) { ret += " " } return ret + "1"; } var s = build_blank(50000) var time0 = Date.now(); lo.trim(s) var time_cost0 = Date.now() - time0; console.log("time_cost0: " + time_cost0) var time1 = Date.now(); lo.toNumber(s) var time_cost1 = Date.now() - time1; console.log("time_cost1: " + time_cost1) var time2 = Date.now(); lo.trimEnd(s) var time_cost2 = Date.now() - time2; console.log("time_cost2: " + time_cost2) | {'CVE-2020-28500'} | 2022-04-19T19:03:27Z | 2022-01-06T20:30:46Z | MODERATE | 5.3 | {'CWE-400'} | {'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-1074892', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://snyk.io/vuln/SNYK-JAVA-ORGFUJIONWEBJARS-1074896', 'https://snyk.io/vuln/SNYK-JS-LODASH-1018905', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1074893', 'https://security.netapp.com/advisory/ntap-20210312-0006/', 'https://github.com/lodash/lodash/blob/npm/trimEnd.js%23L8', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://github.com/advisories/GHSA-29mw-wpgm-hmr9', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28500', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBLODASH-1074895', 'https://github.com/lodash/lodash/pull/5065/commits/02906b8191d3c100c193fe6f7b27d1c40f200bb7', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARS-1074894', 'https://github.com/lodash/lodash/pull/5065', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/lodash/lodash/pull/5065/commits/02906b8191d3c100c193fe6f7b27d1c40f200bb7'} | {'https://github.com/lodash/lodash/pull/5065/commits/02906b8191d3c100c193fe6f7b27d1c40f200bb7'} |
GHSA | GHSA-25mp-g6fv-mqxx | Unexpected server crash in Next.js. | Next.js is a React framework. In versions of Next.js prior to 12.0.5 or 11.1.3, invalid or malformed URLs could lead to a server crash. In order to be affected by this issue, the deployment must use Next.js versions above 11.1.0 and below 12.0.5, Node.js above 15.0.0, and next start or a custom server. Deployments on Vercel are not affected, along with similar environments where invalid requests are filtered before reaching Next.js. Versions 12.0.5 and 11.1.3 contain patches for this issue. Note that prior version 0.9.9 package `next` hosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions. | {'CVE-2021-43803'} | 2022-04-07T16:06:55Z | 2021-12-07T21:12:09Z | HIGH | 7.5 | {'CWE-20'} | {'https://github.com/advisories/GHSA-25mp-g6fv-mqxx', 'https://github.com/vercel/next.js/security/advisories/GHSA-25mp-g6fv-mqxx', 'https://github.com/vercel/next.js/releases/v12.0.5', 'https://github.com/vercel/next.js/releases/tag/v11.1.3', 'https://github.com/vercel/next.js/commit/6d98b4fb4315dec1badecf0e9bdc212a4272b264', 'https://github.com/vercel/next.js/pull/32080', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43803'} | null | {'https://github.com/vercel/next.js/commit/6d98b4fb4315dec1badecf0e9bdc212a4272b264'} | {'https://github.com/vercel/next.js/commit/6d98b4fb4315dec1badecf0e9bdc212a4272b264'} |
GHSA | GHSA-jvfv-hrrc-6q72 | Improper Restriction of XML External Entity Reference in Liquibase | The XMLChangeLogSAXParser() function in Liquibase prior to version 4.8.0 contains an issue that may lead to to Improper Restriction of XML External Entity Reference. | {'CVE-2022-0839'} | 2022-03-18T21:12:36Z | 2022-03-05T00:00:45Z | CRITICAL | 9.8 | {'CWE-611'} | {'https://github.com/advisories/GHSA-jvfv-hrrc-6q72', 'https://github.com/liquibase/liquibase/commit/33d9d925082097fb1a3d2fc8e44423d964cd9381', 'https://huntr.dev/bounties/f1ae5779-b406-4594-a8a3-d089c68d6e70', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0839'} | null | {'https://github.com/liquibase/liquibase/commit/33d9d925082097fb1a3d2fc8e44423d964cd9381'} | {'https://github.com/liquibase/liquibase/commit/33d9d925082097fb1a3d2fc8e44423d964cd9381'} |
GHSA | GHSA-m54r-vrmv-hw33 | Improper Sanitizing of plugin names in helm | ### Impact
Security researchers at Trail of Bits discovered that plugin names are not sanitized properly. As a result, a malicious plugin author could use characters in a plugin name that would result in unexpected behavior, such as duplicating the name of another plugin or spoofing the output to `helm --help`.
### Patches
This issue has been patched in Helm 3.3.2.
### Workarounds
Do not install untrusted Helm plugins. Examine the `name` field in the `plugin.yaml` file for a plugin, looking for characters outside of the [a-zA-Z0-9._-] range. | {'CVE-2020-15186'} | 2021-11-19T15:28:38Z | 2021-05-24T16:57:12Z | LOW | 3.4 | {'CWE-74', 'CWE-20'} | {'https://github.com/helm/helm/security/advisories/GHSA-m54r-vrmv-hw33', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15186', 'https://github.com/helm/helm/commit/c8d6b01d72c9604e43ee70d0d78fadd54c2d8499', 'https://github.com/advisories/GHSA-m54r-vrmv-hw33', 'https://github.com/helm/helm/commit/809e2d999e2c33e20e77f6bff30652d79c287542'} | null | {'https://github.com/helm/helm/commit/c8d6b01d72c9604e43ee70d0d78fadd54c2d8499', 'https://github.com/helm/helm/commit/809e2d999e2c33e20e77f6bff30652d79c287542'} | {'https://github.com/helm/helm/commit/809e2d999e2c33e20e77f6bff30652d79c287542', 'https://github.com/helm/helm/commit/c8d6b01d72c9604e43ee70d0d78fadd54c2d8499'} |
GHSA | GHSA-g585-j55v-38h7 | Cross-site Scripting in ShowDoc | ShowDoc prior to 2.10.4 is vulnerable to stored cross-site scripting via file upload. | {'CVE-2022-0966'} | 2022-03-29T21:27:49Z | 2022-03-16T00:00:45Z | MODERATE | 5.4 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0966', 'https://github.com/advisories/GHSA-g585-j55v-38h7', 'https://huntr.dev/bounties/e06c0d55-00a3-4f82-a009-0310b2e402fe', 'https://github.com/star7th/showdoc/commit/3caa32334db0c277b84e993eaca2036f5d1dbef8'} | null | {'https://github.com/star7th/showdoc/commit/3caa32334db0c277b84e993eaca2036f5d1dbef8'} | {'https://github.com/star7th/showdoc/commit/3caa32334db0c277b84e993eaca2036f5d1dbef8'} |
GHSA | GHSA-2r8p-fg3c-wcj4 | Heap OOB and CHECK fail in `ResourceGather` | ### Impact
An attacker can trigger a crash via a `CHECK`-fail in debug builds of TensorFlow using `tf.raw_ops.ResourceGather` or a read from outside the bounds of heap allocated data in the same API in a release build:
```python
import tensorflow as tf
tensor = tf.constant(value=[[1,2],[3,4],[5,6]],shape=(3,2),dtype=tf.uint32)
v = tf.Variable(tensor)
tf.raw_ops.ResourceGather(
resource=v.handle,
indices=[0],
dtype=tf.uint32,
batch_dims=10,
validate_indices=False)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L660-L668) does not check that the `batch_dims` value that the user supplies is less than the rank of the input tensor.
Since the implementation uses several for loops over the dimensions of `tensor`, this results in reading data from outside the bounds of heap allocated buffer backing the tensor:
```cc
// batch_dims_ = > params.dims() (10 > 2)
for (int i = 0; i < batch_dims_; ++i) {
result_shape.AddDim(params.dim_size(i));
}
for (int i = batch_dims_; i < indices.dims(); ++i) {
result_shape.AddDim(indices.dim_size(i));
}
for (int i = batch_dims_ + 1; i < params.dims(); ++i) {
result_shape.AddDim(params.dim_size(i));
}
```
In debug mode, `.dim_size(i)` validates that the argument is less than `.dims()` using a `DCHECK`. But the `DCHECK` is a no-op in release builds.
### Patches
We have patched the issue in GitHub commit [bc9c546ce7015c57c2f15c168b3d9201de679a1d](https://github.com/tensorflow/tensorflow/commit/bc9c546ce7015c57c2f15c168b3d9201de679a1d).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-37654'} | 2021-08-25T14:43:01Z | 2021-08-25T14:43:01Z | HIGH | 7.3 | {'CWE-125'} | {'https://github.com/advisories/GHSA-2r8p-fg3c-wcj4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37654', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-2r8p-fg3c-wcj4', 'https://github.com/tensorflow/tensorflow/commit/bc9c546ce7015c57c2f15c168b3d9201de679a1d'} | null | {'https://github.com/tensorflow/tensorflow/commit/bc9c546ce7015c57c2f15c168b3d9201de679a1d'} | {'https://github.com/tensorflow/tensorflow/commit/bc9c546ce7015c57c2f15c168b3d9201de679a1d'} |
GHSA | GHSA-38m9-3vg4-rwvp | Cross-site Scripting in microweber | microweber prior to version 1.2.11 is vulnerable to cross-site scripting. | {'CVE-2022-0678'} | 2022-02-26T01:15:19Z | 2022-02-20T00:00:32Z | MODERATE | 6.5 | {'CWE-79'} | {'https://github.com/microweber/microweber/commit/2b8fa5aac31e51e2aca83c7ef5d1281ba2e755f8', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0678', 'https://huntr.dev/bounties/d707137a-aace-44c5-b15c-1807035716c0', 'https://github.com/advisories/GHSA-38m9-3vg4-rwvp'} | null | {'https://github.com/microweber/microweber/commit/2b8fa5aac31e51e2aca83c7ef5d1281ba2e755f8'} | {'https://github.com/microweber/microweber/commit/2b8fa5aac31e51e2aca83c7ef5d1281ba2e755f8'} |
GHSA | GHSA-fx3v-553x-3c4q | Stored XSS by authenticated backend user with access to upload files | ### Impact
Backend users with access to upload files were permitted to upload SVG files without any sanitization applied to the uploaded files. Since SVG files support being parsed as HTML by browsers, this means that they could theoretically upload Javascript that would be executed on a path under the website's domain (i.e. /storage/app/media/evil.svg), but they would have to convince their target to visit that location directly in the target's browser as the backend does not display SVGs inline anywhere, SVGs are only displayed as image resources in the backend and are thus unable to be executed.
### Patches
Issue has been patched in Build 469 (v1.0.469) & v1.1.0.
### Workarounds
Apply https://github.com/octobercms/library/commit/80aab47f044a2660aa352450f55137598f362aa4 to your installation manually if unable to upgrade to Build 469 or v1.1.0.
### References
Reported by [Hoan Hoang](https://github.com/hoanhp)
### For more information
If you have any questions or comments about this advisory:
* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)
### Threat assessment:
<img width="1107" alt="Screen Shot 2020-10-10 at 1 47 49 PM" src="https://user-images.githubusercontent.com/7253840/95663787-378f2b80-0aff-11eb-8dfc-b97d162939da.png"> | {'CVE-2020-15249'} | 2022-04-19T19:02:38Z | 2020-11-23T19:47:59Z | LOW | 2.8 | {'CWE-79'} | {'https://github.com/octobercms/library/commit/80aab47f044a2660aa352450f55137598f362aa4', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15249', 'https://github.com/advisories/GHSA-fx3v-553x-3c4q', 'https://github.com/octobercms/october/security/advisories/GHSA-fx3v-553x-3c4q'} | null | {'https://github.com/octobercms/library/commit/80aab47f044a2660aa352450f55137598f362aa4'} | {'https://github.com/octobercms/library/commit/80aab47f044a2660aa352450f55137598f362aa4'} |
GHSA | GHSA-7qqr-3pj3-q2f5 | XSS issues in the management interface | In system/workplace/ in Alkacon OpenCms 10.5.4 and 10.5.5, there are multiple Reflected and Stored XSS issues in the management interface. | {'CVE-2019-13236'} | 2021-08-18T22:25:16Z | 2019-11-12T22:58:21Z | MODERATE | 6.1 | {'CWE-79'} | {'https://twitter.com/aetsu/status/1152096227938459648', 'https://nvd.nist.gov/vuln/detail/CVE-2019-13236', 'https://github.com/alkacon/opencms-core/commits/branch_10_5_x', 'https://aetsu.github.io/OpenCms', 'https://github.com/advisories/GHSA-7qqr-3pj3-q2f5', 'http://packetstormsecurity.com/files/154283/Alkacon-OpenCMS-10.5.x-Cross-Site-Scripting.html'} | null | {'https://github.com/alkacon/opencms-core/commits/branch_10_5_x'} | {'https://github.com/alkacon/opencms-core/commits/branch_10_5_x'} |
GHSA | GHSA-xmc8-cjfr-phx3 | Regular Expression Denial of Service in highcharts | Versions of `highcharts` prior to 6.1.0 are vulnerable to Regular Expression Denial of Service (ReDoS). Untrusted input may cause catastrophic backtracking while matching regular expressions. This can cause the application to be unresponsive leading to Denial of Service.
## Recommendation
Upgrade to version 6.1.0 or higher. | {'CVE-2018-20801'} | 2021-09-21T22:36:58Z | 2019-03-18T15:59:32Z | HIGH | 7.5 | {'CWE-185'} | {'https://github.com/advisories/GHSA-xmc8-cjfr-phx3', 'https://security.netapp.com/advisory/ntap-20190715-0001/', 'https://nvd.nist.gov/vuln/detail/CVE-2018-20801', 'https://snyk.io/vuln/npm:highcharts:20180225', 'https://github.com/highcharts/highcharts/commit/7c547e1e0f5e4379f94396efd559a566668c0dfa', 'https://www.npmjs.com/advisories/793'} | null | {'https://github.com/highcharts/highcharts/commit/7c547e1e0f5e4379f94396efd559a566668c0dfa'} | {'https://github.com/highcharts/highcharts/commit/7c547e1e0f5e4379f94396efd559a566668c0dfa'} |
GHSA | GHSA-c442-3278-rhrg | Unrestricted File Upload in ShowDoc v2.9.5 | Unrestricted File Upload in ShowDoc v2.9.5 allows remote attackers to execute arbitrary code via the 'file_url' parameter in the component AdminUpdateController.class.php'. | {'CVE-2021-36440'} | 2021-09-16T19:26:05Z | 2021-09-09T17:08:46Z | CRITICAL | 9.8 | {'CWE-434'} | {'https://github.com/star7th/showdoc/commit/49b992d4c548c8c615a92b6efe8a50c8f1083abf', 'https://github.com/advisories/GHSA-c442-3278-rhrg', 'https://nvd.nist.gov/vuln/detail/CVE-2021-36440', 'https://github.com/star7th/showdoc/issues/1406'} | null | {'https://github.com/star7th/showdoc/commit/49b992d4c548c8c615a92b6efe8a50c8f1083abf'} | {'https://github.com/star7th/showdoc/commit/49b992d4c548c8c615a92b6efe8a50c8f1083abf'} |
GHSA | GHSA-5xp3-jfq3-5q8x | Improper Input Validation in pip | A flaw was found in python-pip in the way it handled Unicode separators in git references. A remote attacker could possibly use this issue to install a different revision on a repository. The highest threat from this vulnerability is to data integrity. This is fixed in python-pip version 21.1. | {'CVE-2021-3572'} | 2022-04-22T15:40:09Z | 2021-11-15T17:45:01Z | MODERATE | 5.7 | {'CWE-20'} | {'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://github.com/advisories/GHSA-5xp3-jfq3-5q8x', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3572', 'https://access.redhat.com/errata/RHSA-2021:3254', 'https://bugzilla.redhat.com/show_bug.cgi?id=1962856', 'https://github.com/pypa/pip/commit/e46bdda9711392fec0c45c1175bae6db847cb30b', 'https://packetstormsecurity.com/files/162712/USN-4961-1.txt', 'https://github.com/pypa/pip/pull/9827'} | null | {'https://github.com/pypa/pip/commit/e46bdda9711392fec0c45c1175bae6db847cb30b'} | {'https://github.com/pypa/pip/commit/e46bdda9711392fec0c45c1175bae6db847cb30b'} |
GHSA | GHSA-m342-ff57-4jcc | Heap OOB read in `tf.raw_ops.SparseCountSparseOutput` | ### Impact
The [shape inference functions for `SparseCountSparseOutput`](https://github.com/tensorflow/tensorflow/blob/e0b6e58c328059829c3eb968136f17aa72b6c876/tensorflow/core/ops/count_ops.cc#L43-L50) can trigger a read outside of bounds of heap allocated array:
```python
import tensorflow as tf
@tf.function
def func():
return tf.raw_ops.SparseCountSparseOutput(
indices=[1],
values=[[1]],
dense_shape=[10],
weights=[],
binary_output= True)
func()
```
The function fails to check that the first input (i.e., `indices`) has rank 2:
```cc
auto rank = c->Dim(c->input(0), 1);
```
### Patches
We have patched the issue in GitHub commit [701cfaca222a82afbeeb17496bd718baa65a67d2](https://github.com/tensorflow/tensorflow/commit/701cfaca222a82afbeeb17496bd718baa65a67d2).
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-41210'} | 2021-11-10T19:01:44Z | 2021-11-10T19:01:44Z | HIGH | 7.1 | {'CWE-125'} | {'https://github.com/advisories/GHSA-m342-ff57-4jcc', 'https://github.com/tensorflow/tensorflow/commit/701cfaca222a82afbeeb17496bd718baa65a67d2', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-m342-ff57-4jcc', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41210'} | null | {'https://github.com/tensorflow/tensorflow/commit/701cfaca222a82afbeeb17496bd718baa65a67d2'} | {'https://github.com/tensorflow/tensorflow/commit/701cfaca222a82afbeeb17496bd718baa65a67d2'} |
GHSA | GHSA-rwh9-8xx8-4wfm | Cross-site Scripting in OpenCRX | In OpenCRX, versions v4.0.0 through v5.1.0 are vulnerable to reflected Cross-site Scripting (XSS), due to unsanitized parameters in the password reset functionality. This allows execution of external javascript files on any user of the openCRX instance. | {'CVE-2021-25959'} | 2021-10-08T21:28:56Z | 2021-09-30T20:50:21Z | MODERATE | 6.1 | {'CWE-79'} | {'https://github.com/advisories/GHSA-rwh9-8xx8-4wfm', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25959', 'https://github.com/opencrx/opencrx/commit/14e75f95e5f56fbe7ee897bdf5d858788072e818'} | null | {'https://github.com/opencrx/opencrx/commit/14e75f95e5f56fbe7ee897bdf5d858788072e818'} | {'https://github.com/opencrx/opencrx/commit/14e75f95e5f56fbe7ee897bdf5d858788072e818'} |
GHSA | GHSA-68gr-cmcp-g3mj | Directory Traversal in lactate | A crafted `GET` request can be leveraged to traverse the directory structure of a host using the lactate web server package, and request arbitrary files outside of the specified web root. This allows for a remote attacker to gain access to arbitrary files on the filesystem that the process has access to read.
Mitigating factors:
Only files that the user running `lactate` has permission to read will be accessible via this vulnerability.
[Proof of concept](https://hackerone.com/reports/296645):
Please globally install the `lactate` package and `cd` to a directory you wish to serve assets from. Next, run `lactate -p 8081` to start serving files from this location.
The following cURL request can be used to demonstrate this vulnerability by requesting the target `/etc/passwd` file:
```
curl "http://127.0.0.1:8081/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/etc/passwd"
```
```
root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
bin:x:2:2:bin:/bin:/usr/sbin/nologin
sys:x:3:3:sys:/dev:/usr/sbin/nologin
[...]
```
## Recommendation
As there is currently no fix for this issue selecting an alternative static web server would be the best choice. | null | 2021-08-16T23:34:11Z | 2019-06-14T16:39:31Z | HIGH | 7.5 | {'CWE-22'} | {'https://hackerone.com/reports/296645', 'https://www.npmjs.com/advisories/560', 'https://github.com/advisories/GHSA-68gr-cmcp-g3mj', 'https://github.com/RetireJS/retire.js/commit/800c8140884eaa5753a49308f560c925fe97b9a5', 'https://snyk.io/vuln/npm:lactate:20180123'} | null | {'https://github.com/RetireJS/retire.js/commit/800c8140884eaa5753a49308f560c925fe97b9a5'} | {'https://github.com/RetireJS/retire.js/commit/800c8140884eaa5753a49308f560c925fe97b9a5'} |
GHSA | GHSA-8h46-5m9h-7553 | Heap out of bounds write in `RaggedBinCount` | ### Impact
If the `splits` argument of `RaggedBincount` does not specify a valid [`SparseTensor`](https://www.tensorflow.org/api_docs/python/tf/sparse/SparseTensor), then an attacker can trigger a heap buffer overflow:
```python
import tensorflow as tf
tf.raw_ops.RaggedBincount(splits=[7,8], values= [5, 16, 51, 76, 29, 27, 54, 95],\
size= 59, weights= [0, 0, 0, 0, 0, 0, 0, 0],\
binary_output=False)
```
This will cause a read from outside the bounds of the `splits` tensor buffer in the [implementation of the `RaggedBincount` op](https://github.com/tensorflow/tensorflow/blob/8b677d79167799f71c42fd3fa074476e0295413a/tensorflow/core/kernels/bincount_op.cc#L430-L446):
```cc
for (int idx = 0; idx < num_values; ++idx) {
while (idx >= splits(batch_idx)) {
batch_idx++;
}
...
if (bin < size) {
if (binary_output_) {
out(batch_idx - 1, bin) = T(1);
} else {
T value = (weights_size > 0) ? weights(idx) : T(1);
out(batch_idx - 1, bin) += value;
}
}
}
```
Before the `for` loop, `batch_idx` is set to 0. The attacker sets `splits(0)` to be 7, hence the `while` loop does not execute and `batch_idx` remains 0. This then results in writing to `out(-1, bin)`, which is before the heap allocated buffer for the output tensor.
### Patches
We have patched the issue in GitHub commit [eebb96c2830d48597d055d247c0e9aebaea94cd5](https://github.com/tensorflow/tensorflow/commit/eebb96c2830d48597d055d247c0e9aebaea94cd5).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 and TensorFlow 2.3.3, as these are also affected.
### 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-29514'} | 2021-05-21T14:20:51Z | 2021-05-21T14:20:51Z | LOW | 2.5 | {'CWE-787'} | {'https://github.com/advisories/GHSA-8h46-5m9h-7553', 'https://github.com/tensorflow/tensorflow/commit/eebb96c2830d48597d055d247c0e9aebaea94cd5', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-8h46-5m9h-7553', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29514'} | null | {'https://github.com/tensorflow/tensorflow/commit/eebb96c2830d48597d055d247c0e9aebaea94cd5'} | {'https://github.com/tensorflow/tensorflow/commit/eebb96c2830d48597d055d247c0e9aebaea94cd5'} |
GHSA | GHSA-w6rp-4vj7-v2m8 | Missing Authorization in DayByDay CRM | In DayByDay CRM, version 2.2.0 is vulnerable to missing authorization. Any application user in the application who has update user permission enabled is able to change the password of other users, including the administrator’s. This allows the attacker to gain access to the highest privileged user in the application. | {'CVE-2022-22111'} | 2022-01-10T21:46:06Z | 2022-01-08T00:31:49Z | HIGH | 8.8 | {'CWE-862'} | {'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2022-22111', 'https://github.com/Bottelet/DaybydayCRM/commit/fe842ea5ede237443f1f45a99aeb839133115d8b', 'https://github.com/advisories/GHSA-w6rp-4vj7-v2m8', 'https://nvd.nist.gov/vuln/detail/CVE-2022-22111'} | null | {'https://github.com/Bottelet/DaybydayCRM/commit/fe842ea5ede237443f1f45a99aeb839133115d8b'} | {'https://github.com/Bottelet/DaybydayCRM/commit/fe842ea5ede237443f1f45a99aeb839133115d8b'} |
GHSA | GHSA-2cf2-2383-h4jv | Improperly Controlled Modification of Dynamically-Determined Object Attributes in querymen | querymen prior to 2.1.4 allows modification of object properties. The parameters of exported function handler(type, name, fn) can be controlled by users without any sanitization. This could be abused for Prototype Pollution attacks. | {'CVE-2020-7600'} | 2021-07-28T18:46:08Z | 2021-05-07T16:16:43Z | MODERATE | 5.3 | {'CWE-915'} | {'https://snyk.io/vuln/SNYK-JS-QUERYMEN-559867', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7600', 'https://github.com/diegohaz/querymen/commit/1987fefcb3b7508253a29502a008d5063a873cef', 'https://github.com/advisories/GHSA-2cf2-2383-h4jv'} | null | {'https://github.com/diegohaz/querymen/commit/1987fefcb3b7508253a29502a008d5063a873cef'} | {'https://github.com/diegohaz/querymen/commit/1987fefcb3b7508253a29502a008d5063a873cef'} |
GHSA | GHSA-xfhp-gmh8-r8v2 | Regular Expression Denial of Service (ReDoS) | The package printf before 0.6.1 are vulnerable to Regular Expression Denial of Service (ReDoS) via the regex string /\%(?:\(([\w_.]+)\)|([1-9]\d*)\$)?([0 +\-\]*)(\*|\d+)?(\.)?(\*|\d+)?[hlL]?([\%bscdeEfFgGioOuxX])/g in lib/printf.js. The vulnerable regular expression has cubic worst-case time complexity. | {'CVE-2021-23354'} | 2021-03-25T00:18:25Z | 2021-03-19T21:22:10Z | HIGH | 7.5 | {'CWE-400'} | {'https://github.com/adaltas/node-printf/commit/a8502e7c9b0b22555696a2d8ef67722086413a68', 'https://snyk.io/vuln/SNYK-JS-PRINTF-1072096', 'https://github.com/adaltas/node-printf/pull/32', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23354', 'https://github.com/advisories/GHSA-xfhp-gmh8-r8v2', 'https://github.com/adaltas/node-printf/issues/31'} | null | {'https://github.com/adaltas/node-printf/commit/a8502e7c9b0b22555696a2d8ef67722086413a68'} | {'https://github.com/adaltas/node-printf/commit/a8502e7c9b0b22555696a2d8ef67722086413a68'} |
GHSA | GHSA-w6jr-wj64-mc9x | Deserialization of Untrusted Data in Codeigniter4 | ### Impact
Deserialization of Untrusted Data was found in the `old()` function in CodeIgniter4.
Remote attackers may inject auto-loadable arbitrary objects with this vulnerability,
and possibly execute existing PHP code on the server.
We are aware of a working exploit, which can lead to SQL injection.
### Patches
Upgrade to v4.1.6 or later.
### Workarounds
Do not use:
- `old()` and form_helper
- `RedirectResponse::withInput()` and `redirect()->withInput()`
### References
- [PHP Object Injection | OWASP](https://owasp.org/www-community/vulnerabilities/PHP_Object_Injection)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [codeigniter4/CodeIgniter4](https://github.com/codeigniter4/CodeIgniter4/issues)
* Email us at [SECURITY.md](https://github.com/codeigniter4/CodeIgniter4/blob/develop/SECURITY.md)
| {'CVE-2022-21647'} | 2022-01-06T22:52:41Z | 2022-01-06T22:52:41Z | HIGH | 7.7 | {'CWE-502'} | {'https://github.com/advisories/GHSA-w6jr-wj64-mc9x', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21647', 'https://github.com/codeigniter4/CodeIgniter4/security/advisories/GHSA-w6jr-wj64-mc9x', 'https://github.com/codeigniter4/CodeIgniter4/commit/ce95ed5765256e2f09f3513e7d42790e0d6948f5'} | null | {'https://github.com/codeigniter4/CodeIgniter4/commit/ce95ed5765256e2f09f3513e7d42790e0d6948f5'} | {'https://github.com/codeigniter4/CodeIgniter4/commit/ce95ed5765256e2f09f3513e7d42790e0d6948f5'} |
GHSA | GHSA-q4xf-3pmq-3hw8 | Improper Restriction of XML External Entity Reference in Apache NiFi | In Apache NiFi 1.0.0 to 1.11.4, the notification service manager and various policy authorizer and user group provider objects allowed trusted administrators to inadvertently configure a potentially malicious XML file. The XML file has the ability to make external calls to services (via XXE). | {'CVE-2020-13940'} | 2022-01-06T20:41:00Z | 2022-01-06T20:41:00Z | MODERATE | 5.5 | {'CWE-611'} | {'https://nifi.apache.org/security#CVE-2020-13940', 'https://github.com/advisories/GHSA-q4xf-3pmq-3hw8', 'https://github.com/apache/nifi/commit/7f0416ee8bdcee95e28409cc6fae9c1394c2a798', 'https://nvd.nist.gov/vuln/detail/CVE-2020-13940'} | null | {'https://github.com/apache/nifi/commit/7f0416ee8bdcee95e28409cc6fae9c1394c2a798'} | {'https://github.com/apache/nifi/commit/7f0416ee8bdcee95e28409cc6fae9c1394c2a798'} |
GHSA | GHSA-x9r5-jxvq-4387 | Self XSS on user input in jquery.terminal | ### Impact
This is low impact and limited XSS, because code for XSS payload is always visible, but attacker can use other techniques to hide the code the victim sees.
Also if the application use execHash option and execute code from URL the attacker can use this URL to execute his code. The scope is limited because the javascript code inside html attribute used is added to span tag, so no automatic execution like with `onerror` on images is possible.
### Patches
Fixed version 2.31.1
### Workarounds
The user can use formatting that wrap whole user input and it's no op.
```javascript
$.terminal.new_formatter([/([\s\S]+)/g, '[[;;]$1]']);
```
The fix will only work when user of the library is not using different formatters (e.g. to highlight code in different way).
### References
The issue was reported here [jcubic/jquery.terminal#727](https://github.com/jcubic/jquery.terminal/issues/727)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [jcubic/jquery.terminal](https://github.com/jcubic/jquery.terminal)
* Email us at [jcubic@onet.pl](mailto:jcubic@onet.pl)
| {'CVE-2021-43862'} | 2022-04-19T19:03:19Z | 2022-01-06T22:48:56Z | LOW | 3.7 | {'CWE-80'} | {'https://github.com/advisories/GHSA-x9r5-jxvq-4387', 'https://github.com/jcubic/jquery.terminal/security/advisories/GHSA-x9r5-jxvq-4387', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43862', 'https://github.com/jcubic/jquery.terminal/releases/tag/2.31.1', 'https://github.com/jcubic/jquery.terminal/commit/77eb044d0896e990d48a9157f0bc6648f81a84b5', 'https://github.com/jcubic/jquery.terminal/issues/727'} | null | {'https://github.com/jcubic/jquery.terminal/commit/77eb044d0896e990d48a9157f0bc6648f81a84b5'} | {'https://github.com/jcubic/jquery.terminal/commit/77eb044d0896e990d48a9157f0bc6648f81a84b5'} |
GHSA | GHSA-rv49-54qp-fw42 | Path Traversal in servey | Versions of `servey` prior to 3.x are vulnerable to Path Traversal. Due to insufficient input sanitization, attackers can access server files by using relative paths.
## Recommendation
Upgrade to the latest version | null | 2021-08-04T20:56:42Z | 2019-06-06T15:30:20Z | MODERATE | 0 | {'CWE-22'} | {'https://github.com/typeorm/typeorm/commit/d46c8b0e6c0db56bb5976a4917e9f67a43715111', 'https://github.com/advisories/GHSA-rv49-54qp-fw42', 'https://www.npmjs.com/advisories/802', 'https://hackerone.com/reports/355501'} | null | {'https://github.com/typeorm/typeorm/commit/d46c8b0e6c0db56bb5976a4917e9f67a43715111'} | {'https://github.com/typeorm/typeorm/commit/d46c8b0e6c0db56bb5976a4917e9f67a43715111'} |
GHSA | GHSA-6vmq-jh76-hq43 | Uninitialized memory access in outer_cgi | An issue was discovered in the outer_cgi crate before 0.2.1 for Rust. A user-provided Read instance receives an uninitialized memory buffer from KeyValueReader. | {'CVE-2021-30454'} | 2021-08-25T20:55:25Z | 2021-08-25T20:55:25Z | CRITICAL | 0 | {'CWE-119'} | {'https://github.com/advisories/GHSA-6vmq-jh76-hq43', 'https://rustsec.org/advisories/RUSTSEC-2021-0051.html', 'https://github.com/SolraBizna/outer_cgi/commit/dd59b3066e616a08e756f72de8dc3ab11b7036c4', 'https://github.com/SolraBizna/outer_cgi/issues/1', 'https://nvd.nist.gov/vuln/detail/CVE-2021-30454'} | null | {'https://github.com/SolraBizna/outer_cgi/commit/dd59b3066e616a08e756f72de8dc3ab11b7036c4'} | {'https://github.com/SolraBizna/outer_cgi/commit/dd59b3066e616a08e756f72de8dc3ab11b7036c4'} |
GHSA | GHSA-wgx2-6432-j3fw | Unsoundness in bigint | An issue was discovered in the bigint crate through 2020-05-07 for Rust. It allows a soundness violation. | {'CVE-2020-35880'} | 2021-08-25T20:48:04Z | 2021-08-25T20:48:04Z | CRITICAL | 9.8 | {'CWE-704'} | {'https://github.com/rustsec/advisory-db/pull/290', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35880', 'https://github.com/advisories/GHSA-wgx2-6432-j3fw', 'https://github.com/paritytech/bigint/commit/7e71521a61b009afc94c91135353102658550d42', 'https://rustsec.org/advisories/RUSTSEC-2020-0025.html'} | null | {'https://github.com/paritytech/bigint/commit/7e71521a61b009afc94c91135353102658550d42'} | {'https://github.com/paritytech/bigint/commit/7e71521a61b009afc94c91135353102658550d42'} |
GHSA | GHSA-9824-rp6m-xx9w | 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-0991, CVE-2019-0992, CVE-2019-0993, CVE-2019-1002, CVE-2019-1003, CVE-2019-1024, CVE-2019-1051, CVE-2019-1052. | {'CVE-2019-0989'} | 2021-03-29T20:59:04Z | 2021-03-29T20:59:04Z | HIGH | 7.5 | {'CWE-787'} | {'https://github.com/advisories/GHSA-9824-rp6m-xx9w', 'https://nvd.nist.gov/vuln/detail/CVE-2019-0989', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0989', 'https://github.com/chakra-core/ChakraCore/commit/3d6226cc2d1077537220361c82e34a362c6c76ee', 'https://github.com/chakra-core/ChakraCore/commit/e0ce3f01c83c53f93e7299d7c8b389b17084aa1f'} | null | {'https://github.com/chakra-core/ChakraCore/commit/3d6226cc2d1077537220361c82e34a362c6c76ee', 'https://github.com/chakra-core/ChakraCore/commit/e0ce3f01c83c53f93e7299d7c8b389b17084aa1f'} | {'https://github.com/chakra-core/ChakraCore/commit/3d6226cc2d1077537220361c82e34a362c6c76ee', 'https://github.com/chakra-core/ChakraCore/commit/e0ce3f01c83c53f93e7299d7c8b389b17084aa1f'} |
GHSA | GHSA-xq52-rv6w-397c | Directive injection when using dynamic overrides with user input | ### Impact
If user-supplied input was passed into `append/override_content_security_policy_directives`, a semicolon could be injected leading to directive injection.
This could be used to e.g. override a `script-src` directive. Duplicate directives are ignored and the first one wins. The directives in `secure_headers` are sorted alphabetically so they pretty much all come before `script-src`. A previously undefined directive would receive a value even if `SecureHeaders::OPT_OUT` was supplied.
The fixed versions will silently convert the semicolons to spaces and emit a deprecation warning when this happens. This will result in innocuous browser console messages if being exploited/accidentally used. In future releases, we will raise application errors resulting in 500s.
> Duplicate script-src directives detected. All but the first instance will be ignored.
See https://www.w3.org/TR/CSP3/#parse-serialized-policy
> Note: In this case, the user agent SHOULD notify developers that a duplicate directive was ignored. A console warning might be appropriate, for example.
### Patches
Depending on what major version you are using, the fixed versions are 6.2.0, 5.1.0, 3.8.0.
### Workarounds
If you are passing user input into the above methods, you could filter out the input:
```ruby
override_content_security_policy_directives(:frame_src, [user_input.gsub(";", " ")])
```
### References
Reported in https://github.com/twitter/secure_headers/issues/418
https://www.w3.org/TR/CSP3/#parse-serialized-policy
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [this repo](https://github.com/twitter/secure_headers/issues/new)
* DM @ndm on twitter | {'CVE-2020-5217'} | 2021-01-08T21:09:32Z | 2020-01-23T02:28:11Z | MODERATE | 4.4 | {'CWE-95'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-5217', 'https://github.com/twitter/secure_headers/issues/418', 'https://github.com/twitter/secure_headers/pull/421', 'https://github.com/twitter/secure_headers/commit/936a160e3e9659737a9f9eafce13eea36b5c9fa3', 'https://github.com/advisories/GHSA-xq52-rv6w-397c', 'https://github.com/twitter/secure_headers/security/advisories/GHSA-xq52-rv6w-397c'} | null | {'https://github.com/twitter/secure_headers/commit/936a160e3e9659737a9f9eafce13eea36b5c9fa3'} | {'https://github.com/twitter/secure_headers/commit/936a160e3e9659737a9f9eafce13eea36b5c9fa3'} |
GHSA | GHSA-25fx-mxc2-76g7 | Unauthorized access to Credit card form exposing payer name and not requiring 3DS | ### Impact
URL to the payment page done after checkout was created with autoincremented payment id (`/pay-with-paypal/{id}`) and therefore it was easy to access for anyone, not even the order's customer. The problem was, the Credit card form has prefilled "credit card holder" field with the Customer's first and last name.
Additionally, the mentioned form did not require a 3D Secure authentication, as well as did not checked the result of the 3D Secure authentication.
### Patches
The problem has been patched in Sylius/PayPalPlugin **1.2.4** and **1.3.1**
### Workarounds
One can override a `sylius_paypal_plugin_pay_with_paypal_form` route and change its URL parameters to (for example) `{orderToken}/{paymentId}`, then override the `Sylius\PayPalPlugin\Controller\PayWithPayPalFormAction` service, to operate on the payment taken from the repository by these 2 values. It would also require usage of custom repository method.
Additionally, one could override the `@SyliusPayPalPlugin/payWithPaypal.html.twig` template, to add `contingencies: ['SCA_ALWAYS']` line in `hostedFields.submit(...)` function call (line 421). It would then have to be handled in the function callback.
### For more information
If you have any questions or comments about this advisory:
- Open an issue in Sylius/PayPalPlugin issues
- Email us at security at sylius dot com
| {'CVE-2021-41120'} | 2021-10-06T17:49:11Z | 2021-10-06T17:49:11Z | HIGH | 7.5 | {'CWE-200'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-41120', 'https://github.com/Sylius/PayPalPlugin/commit/2adc46be2764ccee22b4247139b8056fb8d1afff', 'https://github.com/Sylius/PayPalPlugin/commit/814923c2e9d97fe6279dcee866c34ced3d2fb7a7', 'https://github.com/Sylius/PayPalPlugin/security/advisories/GHSA-25fx-mxc2-76g7', 'https://github.com/advisories/GHSA-25fx-mxc2-76g7'} | null | {'https://github.com/Sylius/PayPalPlugin/commit/2adc46be2764ccee22b4247139b8056fb8d1afff', 'https://github.com/Sylius/PayPalPlugin/commit/814923c2e9d97fe6279dcee866c34ced3d2fb7a7'} | {'https://github.com/Sylius/PayPalPlugin/commit/814923c2e9d97fe6279dcee866c34ced3d2fb7a7', 'https://github.com/Sylius/PayPalPlugin/commit/2adc46be2764ccee22b4247139b8056fb8d1afff'} |
GHSA | GHSA-v3rr-cph9-2g2q | Moderate severity vulnerability that affects rack-ssl | Cross-site scripting (XSS) vulnerability in lib/rack/ssl.rb in the rack-ssl gem before 1.4.0 for Ruby allows remote attackers to inject arbitrary web script or HTML via a URI, which might not be properly handled by third-party adapters such as JRuby-Rack. | {'CVE-2014-2538'} | 2021-09-20T15:02:21Z | 2017-10-24T18:33:36Z | MODERATE | 0 | {'CWE-79'} | {'http://www.securityfocus.com/bid/66314', 'https://nvd.nist.gov/vuln/detail/CVE-2014-2538', 'http://lists.opensuse.org/opensuse-updates/2014-04/msg00032.html', 'https://github.com/advisories/GHSA-v3rr-cph9-2g2q', 'https://github.com/josh/rack-ssl/commit/9d7d7300b907e496db68d89d07fbc2e0df0b487b', 'http://www.openwall.com/lists/oss-security/2014/03/19/20', 'http://secunia.com/advisories/57466'} | null | {'https://github.com/josh/rack-ssl/commit/9d7d7300b907e496db68d89d07fbc2e0df0b487b'} | {'https://github.com/josh/rack-ssl/commit/9d7d7300b907e496db68d89d07fbc2e0df0b487b'} |
GHSA | GHSA-qw93-45r3-p66p | Prototype Pollution in merge-options | All versions of `merge-options` are vulnerable to Prototype Pollution
## Recommendation
Update to version 1.0.1 or greater. | {'CVE-2018-3752'} | 2021-09-16T21:10:32Z | 2018-10-09T00:19:57Z | CRITICAL | 9.8 | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-3752', 'https://www.npmjs.com/advisories/717', 'https://hackerone.com/reports/311336', 'https://github.com/schnittstabil/merge-options/commit/d4a93bc2890455e0931ac0779667023e6cb101d4', 'https://github.com/advisories/GHSA-qw93-45r3-p66p'} | null | {'https://github.com/schnittstabil/merge-options/commit/d4a93bc2890455e0931ac0779667023e6cb101d4'} | {'https://github.com/schnittstabil/merge-options/commit/d4a93bc2890455e0931ac0779667023e6cb101d4'} |
GHSA | GHSA-q58g-455p-8vw9 | In RubyGem excon, interrupted Persistent Connections May Leak Response Data | ### Impact
There was a race condition around persistent connections, where a connection which is interrupted (such as by a timeout) would leave data on the socket. Subsequent requests would then read this data, returning content from the previous response. The race condition window appears to be short, and it would be difficult to purposefully exploit this.
### Patches
The problem has been patched in 0.71.0, users should upgrade to this or a newer version (if one exists).
### Workarounds
Users can workaround the problem by disabling persistent connections, though this may cause performance implications.
### References
See the [patch](https://github.com/excon/excon/commit/ccb57d7a422f020dc74f1de4e8fb505ab46d8a29) for further details.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [excon/issues](https://github.com/excon/excon/issues)
* Email us at [geemus+github@gmail.com](mailto:geemus+github@gmail.com) | {'CVE-2019-16779'} | 2021-10-29T14:10:28Z | 2019-12-16T19:30:17Z | MODERATE | 5.8 | {'CWE-362', 'CWE-664'} | {'https://github.com/excon/excon/security/advisories/GHSA-q58g-455p-8vw9', 'https://github.com/excon/excon/commit/ccb57d7a422f020dc74f1de4e8fb505ab46d8a29', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16779', 'https://lists.debian.org/debian-lts-announce/2020/01/msg00015.html', 'http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00062.html', 'https://github.com/advisories/GHSA-q58g-455p-8vw9', 'http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00021.html'} | null | {'https://github.com/excon/excon/commit/ccb57d7a422f020dc74f1de4e8fb505ab46d8a29'} | {'https://github.com/excon/excon/commit/ccb57d7a422f020dc74f1de4e8fb505ab46d8a29'} |
GHSA | GHSA-j47f-4232-hvv8 | Heap out of bounds read in `RaggedCross` | ### Impact
An attacker can force accesses outside the bounds of heap allocated arrays by passing in invalid tensor values to `tf.raw_ops.RaggedCross`:
```python
import tensorflow as tf
ragged_values = []
ragged_row_splits = []
sparse_indices = []
sparse_values = []
sparse_shape = []
dense_inputs_elem = tf.constant([], shape=[92, 0], dtype=tf.int64)
dense_inputs = [dense_inputs_elem]
input_order = "R"
hashed_output = False
num_buckets = 0
hash_key = 0
tf.raw_ops.RaggedCross(ragged_values=ragged_values,
ragged_row_splits=ragged_row_splits,
sparse_indices=sparse_indices,
sparse_values=sparse_values,
sparse_shape=sparse_shape,
dense_inputs=dense_inputs,
input_order=input_order,
hashed_output=hashed_output,
num_buckets=num_buckets,
hash_key=hash_key,
out_values_type=tf.int64,
out_row_splits_type=tf.int64)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/efea03b38fb8d3b81762237dc85e579cc5fc6e87/tensorflow/core/kernels/ragged_cross_op.cc#L456-L487) lacks validation for the user supplied arguments:
```cc
int next_ragged = 0;
int next_sparse = 0;
int next_dense = 0;
for (char c : input_order_) {
if (c == 'R') {
TF_RETURN_IF_ERROR(BuildRaggedFeatureReader(
ragged_values_list[next_ragged], ragged_splits_list[next_ragged],
features));
next_ragged++;
} else if (c == 'S') {
TF_RETURN_IF_ERROR(BuildSparseFeatureReader(
sparse_indices_list[next_sparse], sparse_values_list[next_sparse],
batch_size, features));
next_sparse++;
} else if (c == 'D') {
TF_RETURN_IF_ERROR(
BuildDenseFeatureReader(dense_list[next_dense++], features));
}
...
}
```
Each of the above branches call a helper function after accessing array elements via a `*_list[next_*]` pattern, followed by incrementing the `next_*` index. However, as there is no validation that the `next_*` values are in the valid range for the corresponding `*_list` arrays, this results in heap OOB reads.
### Patches
We have patched the issue in GitHub commit [44b7f486c0143f68b56c34e2d01e146ee445134a](https://github.com/tensorflow/tensorflow/commit/44b7f486c0143f68b56c34e2d01e146ee445134a).
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-29532'} | 2021-05-21T14:22:17Z | 2021-05-21T14:22:17Z | LOW | 2.5 | {'CWE-125'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-j47f-4232-hvv8', 'https://github.com/tensorflow/tensorflow/commit/44b7f486c0143f68b56c34e2d01e146ee445134a', 'https://github.com/advisories/GHSA-j47f-4232-hvv8', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29532'} | null | {'https://github.com/tensorflow/tensorflow/commit/44b7f486c0143f68b56c34e2d01e146ee445134a'} | {'https://github.com/tensorflow/tensorflow/commit/44b7f486c0143f68b56c34e2d01e146ee445134a'} |
GHSA | GHSA-5v44-7647-xfw9 | Blind SQL injection in PrestaShop productcomments module | ### Impact
An attacker can use a Blind SQL injection to retrieve data or stop the MySQL service.
### Patches
The problem is fixed in 4.2.1 | {'CVE-2020-26248'} | 2022-04-19T19:02:41Z | 2021-01-20T21:33:53Z | LOW | 8.2 | {'CWE-89'} | {'https://github.com/PrestaShop/productcomments/commit/7c2033dd811744e021da8897c80d6c301cd45ffa', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26248', 'https://packagist.org/packages/prestashop/productcomments', 'https://github.com/PrestaShop/productcomments/security/advisories/GHSA-5v44-7647-xfw9', 'https://github.com/advisories/GHSA-5v44-7647-xfw9', 'http://packetstormsecurity.com/files/160539/PrestaShop-ProductComments-4.2.0-SQL-Injection.html', 'https://github.com/PrestaShop/productcomments/releases/tag/v4.2.1'} | null | {'https://github.com/PrestaShop/productcomments/commit/7c2033dd811744e021da8897c80d6c301cd45ffa'} | {'https://github.com/PrestaShop/productcomments/commit/7c2033dd811744e021da8897c80d6c301cd45ffa'} |
GHSA | GHSA-73q9-7pwj-gm46 | icecoder is vulnerable to Cross-site Scripting | icecoder is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') | {'CVE-2021-3862'} | 2022-01-21T23:46:12Z | 2022-01-21T23:46:12Z | MODERATE | 5.4 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-3862', 'https://github.com/icecoder/icecoder/commit/51cf24b2a39138e6a7b5739ef59eb38cd7c39763', 'https://github.com/advisories/GHSA-73q9-7pwj-gm46', 'https://huntr.dev/bounties/5c9c228e-2a39-4643-bb82-2b02a2b0a601'} | null | {'https://github.com/icecoder/icecoder/commit/51cf24b2a39138e6a7b5739ef59eb38cd7c39763'} | {'https://github.com/icecoder/icecoder/commit/51cf24b2a39138e6a7b5739ef59eb38cd7c39763'} |
GHSA | GHSA-77vh-xpmg-72qh | Clarify `mediaType` handling | ### Impact
In the OCI Image Specification version 1.0.1 and prior, manifest and index documents are not self-describing and documents with a single digest could be interpreted as either a manifest or an index.
### Patches
The Image Specification will be updated to recommend that both manifest and index documents contain a `mediaType` field to identify the type of document.
Release [v1.0.2](https://github.com/opencontainers/image-spec/releases/tag/v1.0.2) includes these updates.
### Workarounds
Software attempting to deserialize an ambiguous document may reject the document if it contains both “manifests” and “layers” fields or “manifests” and “config” fields.
### References
https://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/opencontainers/image-spec
* Email us at [security@opencontainers.org](mailto:security@opencontainers.org)
* https://github.com/opencontainers/image-spec/commits/v1.0.2
| null | 2021-11-24T19:43:36Z | 2021-11-18T16:02:41Z | LOW | 3 | {'CWE-843'} | {'https://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m', 'https://github.com/advisories/GHSA-77vh-xpmg-72qh', 'https://github.com/opencontainers/image-spec/commit/693428a734f5bab1a84bd2f990d92ef1111cd60c', 'https://github.com/opencontainers/image-spec/releases/tag/v1.0.2', 'https://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh'} | null | {'https://github.com/opencontainers/image-spec/commit/693428a734f5bab1a84bd2f990d92ef1111cd60c'} | {'https://github.com/opencontainers/image-spec/commit/693428a734f5bab1a84bd2f990d92ef1111cd60c'} |
GHSA | GHSA-9q5w-79cv-947m | Unsafe defaults in `remark-html` | ### Impact
The documentation of `remark-html` has mentioned that it was safe by default. In practise the default was never safe and had to be opted into. This means arbitrary HTML can be passed through leading to potential XSS attacks.
### Patches
The problem has been patched in 13.0.2 and 14.0.1: `remark-html` is now safe by default, and the implementation matches the documentation.
### Workarounds
On older affected versions, pass `sanitize: true`, like so:
```diff
- .use(remarkHtml)
+ .use(remarkHtml, {sanitize: true})
```
### References
n/a
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [`remark-html`](https://github.com/remarkjs/remark-html)
* Email us at [security@unifiedjs.com](mailto:security@unifiedjs.com)
| {'CVE-2021-39199'} | 2022-04-19T19:03:07Z | 2021-09-07T23:10:56Z | CRITICAL | 10 | {'CWE-79'} | {'https://github.com/remarkjs/remark-html/releases/tag/14.0.1', 'https://github.com/remarkjs/remark-html/security/advisories/GHSA-9q5w-79cv-947m', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39199', 'https://www.npmjs.com/package/remark-html', 'https://github.com/advisories/GHSA-9q5w-79cv-947m', 'https://github.com/remarkjs/remark-html/commit/b75c9dde582ad87ba498e369c033dc8a350478c1'} | null | {'https://github.com/remarkjs/remark-html/commit/b75c9dde582ad87ba498e369c033dc8a350478c1'} | {'https://github.com/remarkjs/remark-html/commit/b75c9dde582ad87ba498e369c033dc8a350478c1'} |
GHSA | GHSA-wjw6-2cqr-j4qr | Client metadata path-traversal | ### Impact
In both clients (`tuf/client` and `tuf/ngclient`), there is a path traversal vulnerability that in the worst case can overwrite files ending in `.json` anywhere on the client system on a call to `get_one_valid_targetinfo()`. It occurs because the rolename is used to form the filename, and may contain path traversal characters (ie `../../name.json`).
The impact is mitigated by a few facts:
* It only affects implementations that allow arbitrary rolename selection for delegated targets metadata
* The attack requires the ability to A) insert new metadata for the path-traversing role and B) get the role delegated by an existing targets metadata
* The written file content is heavily restricted since it needs to be a valid, signed targets file. The file extension is always .json.
### Patches
A fix is available in version 0.19 or newer.
### Workarounds
None that do not require code changes. Clients can restrict the allowed character set for rolenames, or they can store metadata in files named in a way that is not vulnerable: neither of these approaches is possible without modifying python-tuf.
### References
- [The issue where this was discovered](https://github.com/theupdateframework/python-tuf/issues/1527)
- [Proof of Concept demonstrating the flaw](https://github.com/jku/path-traversal-poc)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [python-tuf](https://github.com/theupdateframework/python-tuf/issues)
* Contact the maintainers by email or Slack
| {'CVE-2021-41131'} | 2022-04-19T19:03:09Z | 2021-10-19T20:14:36Z | HIGH | 7.5 | {'CWE-22'} | {'https://github.com/advisories/GHSA-wjw6-2cqr-j4qr', 'https://github.com/theupdateframework/python-tuf/commit/4ad7ae48fda594b640139c3b7eae21ed5155a102', 'https://github.com/theupdateframework/python-tuf/issues/1527', 'https://github.com/theupdateframework/python-tuf/security/advisories/GHSA-wjw6-2cqr-j4qr', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41131'} | null | {'https://github.com/theupdateframework/python-tuf/commit/4ad7ae48fda594b640139c3b7eae21ed5155a102'} | {'https://github.com/theupdateframework/python-tuf/commit/4ad7ae48fda594b640139c3b7eae21ed5155a102'} |
GHSA | GHSA-jm56-5h66-w453 | Repository index file allows for duplicates of the same chart entry in helm | ### Impact
During a security audit of Helm's code base, security researchers at Trail of Bits identified a bug in which the a Helm repository can contain duplicates of the same chart, with the last one always used. If a repository is compromised, this lowers the level of access that an attacker needs to inject a bad chart into a repository.
To perform this attack, an attacker must have write access to the index file (which can occur during a MITM attack on a non-SSL connection).
### Patches
This issue has been patched in Helm 3.3.2 and 2.16.11
### Workarounds
- do not install charts from repositories you do not trust
- fetch charts using a secure channel of communication (such as TLS)
- use `helm pull` to fetch the chart, then review the chart’s content (either manually, or with `helm verify` if it has been signed) to ensure it has not been tampered with
- manually review the index file in the Helm repository cache before installing software. | {'CVE-2020-15185'} | 2021-05-24T16:57:06Z | 2021-05-24T16:57:06Z | LOW | 2.2 | {'CWE-74', 'CWE-20', 'CWE-694'} | {'https://github.com/advisories/GHSA-jm56-5h66-w453', 'https://github.com/helm/helm/commit/6aab63765f99050b115f0aec3d6350c85e8da946', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15185', 'https://github.com/helm/helm/commit/055dd41cbe53ce131ab0357524a7f6729e6e40dc', 'https://github.com/helm/helm/security/advisories/GHSA-jm56-5h66-w453'} | null | {'https://github.com/helm/helm/commit/055dd41cbe53ce131ab0357524a7f6729e6e40dc', 'https://github.com/helm/helm/commit/6aab63765f99050b115f0aec3d6350c85e8da946'} | {'https://github.com/helm/helm/commit/6aab63765f99050b115f0aec3d6350c85e8da946', 'https://github.com/helm/helm/commit/055dd41cbe53ce131ab0357524a7f6729e6e40dc'} |
GHSA | GHSA-p7v4-gm6j-cw9m | XSS in Mautic | ### Impact
This is a cross-site scripting vulnerability relating to creating/editing a company which requires the user to be logged in as an administrator to be executed.
This vulnerability was reported by Dardan Prebreza at Bishop Fox.
### Patches
Upgrade to 3.2.4 or 2.16.5.
Link to patch for 2.x versions: https://github.com/mautic/mautic/compare/2.16.4...2.16.5.diff
Link to patch for 3.x versions: https://github.com/mautic/mautic/compare/3.2.2...3.2.4.diff
### Workarounds
None
### References
https://www.mautic.org/blog/community/security-release-all-versions-mautic-prior-2-16-5-and-3-2-4
### For more information
If you have any questions or comments about this advisory:
* Post in https://forum.mautic.org/c/support
* Email us at security@mautic.org | {'CVE-2021-3142'} | 2022-04-19T19:02:44Z | 2021-01-29T20:51:20Z | HIGH | 0 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-3142', 'https://github.com/mautic/mautic/security/advisories/GHSA-p7v4-gm6j-cw9m', 'https://github.com/mautic/mautic/commit/ba31db23e664f889da55a29ff27f797e2ab5cb1b', 'https://www.mautic.org/blog/community/security-release-all-versions-mautic-prior-2-16-5-and-3-2-3', 'https://github.com/mautic/mautic/releases/tag/3.2.4', 'https://github.com/advisories/GHSA-p7v4-gm6j-cw9m'} | null | {'https://github.com/mautic/mautic/commit/ba31db23e664f889da55a29ff27f797e2ab5cb1b'} | {'https://github.com/mautic/mautic/commit/ba31db23e664f889da55a29ff27f797e2ab5cb1b'} |
GHSA | GHSA-wjr4-2jgw-hmv8 | Command Injection in whereis | Versions of `whereis` before 0.4.1 are vulnerable to command injection if untrusted user input is passed into `whereis`.
## Recommendation
Update to version 0.4.1 or later. | {'CVE-2018-3772'} | 2021-01-08T01:56:37Z | 2018-07-31T18:28:53Z | HIGH | 0 | {'CWE-77'} | {'https://github.com/advisories/GHSA-wjr4-2jgw-hmv8', 'https://github.com/vvo/node-whereis/commit/0f64e3780235004fb6e43bfd153ea3e0e210ee2b', 'https://hackerone.com/reports/319476', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3772', 'https://www.npmjs.com/advisories/604'} | null | {'https://github.com/vvo/node-whereis/commit/0f64e3780235004fb6e43bfd153ea3e0e210ee2b'} | {'https://github.com/vvo/node-whereis/commit/0f64e3780235004fb6e43bfd153ea3e0e210ee2b'} |
GHSA | GHSA-ppfm-rj6p-38q6 | Improper Authorization in librenms | Improper Authorization in Packagist librenms/librenms prior to 22.2.0. | {'CVE-2022-0587'} | 2022-02-24T12:14:15Z | 2022-02-16T00:01:53Z | HIGH | 7.1 | {'CWE-285'} | {'https://github.com/advisories/GHSA-ppfm-rj6p-38q6', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0587', 'https://huntr.dev/bounties/0c7c9ecd-33ac-4865-b05b-447ced735469', 'https://github.com/librenms/librenms/commit/95970af78e4c899744a715766d744deef8c505f7', 'https://notes.netbytesec.com/2022/02/multiple-vulnerabilities-in-librenms.html'} | null | {'https://github.com/librenms/librenms/commit/95970af78e4c899744a715766d744deef8c505f7'} | {'https://github.com/librenms/librenms/commit/95970af78e4c899744a715766d744deef8c505f7'} |
GHSA | GHSA-x5m8-2r8v-8f97 | Prototype Pollution in libnested | The package libnested before 1.5.2 are vulnerable to Prototype Pollution via the set function in index.js. **Note:** This vulnerability derives from an incomplete fix for [CVE-2020-28283](https://security.snyk.io/vuln/SNYK-JS-LIBNESTED-1054930) | {'CVE-2022-25352'} | 2022-03-29T22:05:38Z | 2022-03-18T00:01:11Z | CRITICAL | 9.8 | {'CWE-1321'} | {'https://snyk.io/vuln/SNYK-JS-LIBNESTED-2342117', 'https://github.com/dominictarr/libnested/commit/c1129865d75fbe52b5a4f755ad3110ca5420f2e1', 'https://nvd.nist.gov/vuln/detail/CVE-2022-25352', 'https://github.com/dominictarr/libnested/blob/master/index.js%23L22', 'https://github.com/advisories/GHSA-x5m8-2r8v-8f97'} | null | {'https://github.com/dominictarr/libnested/commit/c1129865d75fbe52b5a4f755ad3110ca5420f2e1'} | {'https://github.com/dominictarr/libnested/commit/c1129865d75fbe52b5a4f755ad3110ca5420f2e1'} |
GHSA | GHSA-h58v-g3q6-q9fx | Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in sulu/sulu | ### Impact
_What kind of vulnerability is it? Who is impacted?_
It is an issue when input HTML into the Tag name. The HTML is execute when the tag name is listed in the auto complete form.
Only admin users are affected and only admin users can create tags.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
The problem is patched with Version 1.6.42.
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
Create a custom request listener to avoid that this kind of tags are created.
### References
_Are there any links users can visit to find out more?_
Currently not.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [sulu/sulu repository](https://github.com/sulu/sulu/issues)
* Email us at [security@sulu.io](mailto:security@sulu.io)
| {'CVE-2021-41169'} | 2021-10-22T16:20:53Z | 2021-10-22T16:20:53Z | MODERATE | 6.2 | {'CWE-79'} | {'https://github.com/sulu/sulu/security/advisories/GHSA-h58v-g3q6-q9fx', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41169', 'https://github.com/advisories/GHSA-h58v-g3q6-q9fx', 'https://github.com/sulu/sulu/commit/20007ac70a3af3c9e53a6acb0ef8794b65642445'} | null | {'https://github.com/sulu/sulu/commit/20007ac70a3af3c9e53a6acb0ef8794b65642445'} | {'https://github.com/sulu/sulu/commit/20007ac70a3af3c9e53a6acb0ef8794b65642445'} |
GHSA | GHSA-6whf-q6p5-84wg | Improper Access Control in Webauthn Framework | Webauthn Framework 3.3.x before 3.3.4 has Incorrect Access Control. An attacker that controls a user's system is able to login to a vulnerable service using an attached FIDO2 authenticator without passing a check of the user presence. | {'CVE-2021-38299'} | 2021-10-06T13:23:36Z | 2021-09-29T17:16:07Z | CRITICAL | 9.8 | {'CWE-863'} | {'https://www.fzi.de/en/news/news/detail-en/artikel/fsa-2021-1-fehlende-ueberpruefung-von-user-presence-in-webauthn-framework/', 'https://github.com/web-auth/webauthn-framework/releases', 'https://github.com/web-auth/webauthn-framework/commit/572e239c5702667ca52487faf861abc768a46308', 'https://github.com/web-auth/webauthn-framework/releases/tag/v3.3.4', 'https://github.com/advisories/GHSA-6whf-q6p5-84wg', 'https://nvd.nist.gov/vuln/detail/CVE-2021-38299'} | null | {'https://github.com/web-auth/webauthn-framework/commit/572e239c5702667ca52487faf861abc768a46308'} | {'https://github.com/web-auth/webauthn-framework/commit/572e239c5702667ca52487faf861abc768a46308'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.