Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
CVE ID: CVE-2021-39205 State: PUBLISHED Published: 2021-09-15T17:15:12 Last Updated: 2024-08-04T01:58:18.260Z Severity: MEDIUM (CVSS 6.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N) Vendors: jitsi Products: jitsi-meet Problem Types: CWE-79, CWE-1321 Description: Jitsi Meet is an open source video conferencing application. Versions prior to 2.0.6173 are vulnerable to client-side cross-site scripting via injecting properties into JSON objects that were not properly escaped. There are no known incidents related to this vulnerability being exploited in the wild. This issue is fixed in Jitsi Meet version 2.0.6173. There are no known workarounds aside from upgrading. Additional Analyst Notes: - C
fixed in Jitsi Meet version 2.0.6173. There are no known workarounds aside from upgrading. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/jitsi/jitsi-meet/security/advisories/GHSA-6582-8v9q-v3fg - https://github.com/jitsi/jitsi-meet/pull/9320 - https://github.com/jitsi/jitsi-meet/pull/9404 - https://hackerone.com/reports/1214493
CVE ID: CVE-2021-39206 State: PUBLISHED Published: 2021-09-09T22:10:15 Last Updated: 2024-08-04T01:58:18.262Z Severity: HIGH (CVSS 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N) Vendors: pomerium Products: pomerium Problem Types: CWE-863 Description: Pomerium is an open source identity-aware access proxy. Envoy, which Pomerium is based on, contains two authorization related vulnerabilities CVE-2021-32777 and CVE-2021-32779. This may lead to incorrect routing or authorization policy decisions. With specially crafted requests, incorrect authorization or routing decisions may be made by Pomerium. Pomerium v0.14.8 and v0.15.1 contain an upgraded envoy binary with these vulnerabilities patched
ay be made by Pomerium. Pomerium v0.14.8 and v0.15.1 contain an upgraded envoy binary with these vulnerabilities patched. This issue can only be triggered when using path prefix based policy. Removing any such policies should provide mitigation. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/envoyproxy/envoy/security/advisories/GHSA-r222-74fw-jqr9 - https://github.com/envoyproxy/envoy/security/advisories/GHSA-6g4j-5vrw-2m8h - https://groups.google.com/g/envoy-announce/c/5xBpsEZZDfE/m/wD05NZBbAgAJ - https://github.com/pomerium/pomerium/security/advisories/GHSA-cfc2-wjcm-c8fm
CVE ID: CVE-2021-39207 State: PUBLISHED Published: 2021-09-10T22:20:09 Last Updated: 2024-08-04T01:58:18.337Z Severity: HIGH (CVSS 8.4 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L) Vendors: facebookresearch Products: ParlAI Problem Types: CWE-502 Description: parlai is a framework for training and evaluating AI models on a variety of openly available dialogue datasets. In affected versions the package is vulnerable to YAML deserialization attack caused by unsafe loading which leads to Arbitary code execution. This security bug is patched by avoiding unsafe loader users should update to version above v1.1.0. If upgrading is not possible then users can change the Loader used to SafeLoader as a
ld update to version above v1.1.0. If upgrading is not possible then users can change the Loader used to SafeLoader as a workaround. See commit 507d066ef432ea27d3e201da08009872a2f37725 for details. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/facebookresearch/ParlAI/security/advisories/GHSA-m87f-9fvv-2mgg - https://github.com/facebookresearch/ParlAI/commit/4374fa2aba383db6526ab36e939eb1cf8ef99879 - https://github.com/facebookresearch/ParlAI/commit/507d066ef432ea27d3e201da08009872a2f37725
CVE ID: CVE-2021-39208 State: PUBLISHED Published: 2021-09-16T14:35:11 Last Updated: 2024-08-04T01:58:18.179Z Severity: MEDIUM (CVSS 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) Vendors: adamhathcock Products: sharpcompress Problem Types: CWE-22 Description: SharpCompress is a fully managed C# library to deal with many compression types and formats. Versions prior to 0.29.0 are vulnerable to partial path traversal. SharpCompress recreates a hierarchy of directories under destinationDirectory if ExtractFullPath is set to true in options. In order to prevent extraction outside the destination directory the destinationFileName path is verified to begin with fullDestinationDirectoryPath. Ho
utside the destination directory the destinationFileName path is verified to begin with fullDestinationDirectoryPath. However, prior to version 0.29.0, it is not enforced that fullDestinationDirectoryPath ends with slash. If the destinationDirectory is not slash terminated like `/home/user/dir` it is possible to create a file with a name thats begins as the destination directory one level up from the directory, i.e. `/home/user/dir.sh`. Because of the file name and destination directory constraints the arbitrary file creation impact is limited and depends on the use case. This issue is fixed in SharpCompress version 0.29.0. Additional Analyst Notes: - CVE Program Container: References: - htt
his issue is fixed in SharpCompress version 0.29.0. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/adamhathcock/sharpcompress/security/advisories/GHSA-jp7f-grcv-6mjf - https://github.com/adamhathcock/sharpcompress/pull/614 - https://github.com/adamhathcock/sharpcompress/releases/tag/0.29.0
CVE ID: CVE-2021-39209 State: PUBLISHED Published: 2021-09-15T15:50:10 Last Updated: 2024-08-04T01:58:18.170Z Severity: HIGH (CVSS 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) Vendors: glpi-project Products: glpi Problem Types: CWE-352 Description: GLPI is a free Asset and IT management software package. In versions prior to 9.5.6, a user who is logged in to GLPI can bypass Cross-Site Request Forgery (CSRF) protection in many places. This could allow a malicious actor to perform many actions on GLPI. This issue is fixed in version 9.5.6. There are no workarounds aside from upgrading. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/glpi-project/glpi/se
from upgrading. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/glpi-project/glpi/security/advisories/GHSA-5qpf-32w7-c56p - https://github.com/glpi-project/glpi/releases/tag/9.5.6
CVE ID: CVE-2021-39210 State: PUBLISHED Published: 2021-09-15T16:40:11 Last Updated: 2024-08-04T01:58:18.270Z Severity: MEDIUM (CVSS 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) Vendors: glpi-project Products: glpi Problem Types: CWE-1004 Description: GLPI is a free Asset and IT management software package. In versions prior to 9.5.6, the cookie used to store the autologin cookie (when a user uses the "remember me" feature) is accessible by scripts. A malicious plugin that could steal this cookie would be able to use it to autologin. This issue is fixed in version 9.5.6. As a workaround, one may avoid using the "remember me" feature. Additional Analyst Notes: - CVE Program Container: Re
6. As a workaround, one may avoid using the "remember me" feature. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/glpi-project/glpi/releases/tag/9.5.6 - https://github.com/glpi-project/glpi/security/advisories/GHSA-hwxq-4c5f-m4v2 - https://huntr.dev/bounties/b2e99a41-b904-419f-a274-ae383e4925f2/
CVE ID: CVE-2021-39211 State: PUBLISHED Published: 2021-09-15T16:55:10 Last Updated: 2024-08-04T01:58:18.247Z Severity: MEDIUM (CVSS 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) Vendors: glpi-project Products: glpi Problem Types: CWE-200 Description: GLPI is a free Asset and IT management software package. Starting in version 9.2 and prior to version 9.5.6, the telemetry endpoint discloses GLPI and server information. This issue is fixed in version 9.5.6. As a workaround, remove the file `ajax/telemetry.php`, which is not needed for usual functions of GLPI. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/glpi-project/glpi/releases/tag/9.5.6 - https://
Analyst Notes: - CVE Program Container: References: - https://github.com/glpi-project/glpi/releases/tag/9.5.6 - https://github.com/glpi-project/glpi/security/advisories/GHSA-xx66-v3g5-w825
CVE ID: CVE-2021-39212 State: PUBLISHED Published: 2021-09-13T00:00:00 Last Updated: 2024-08-04T01:58:18.274Z Severity: MEDIUM (CVSS 4.4 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) Vendors: ImageMagick Products: ImageMagick Problem Types: CWE-668 Description: ImageMagick is free software delivered as a ready-to-run binary distribution or as source code that you may use, copy, modify, and distribute in both open and proprietary applications. In affected versions and in certain cases, Postscript files could be read and written when specifically excluded by a `module` policy in `policy.xml`. ex. <policy domain="module" rights="none" pattern="PS" />. The issue has been resolved in ImageMagick
in `policy.xml`. ex. <policy domain="module" rights="none" pattern="PS" />. The issue has been resolved in ImageMagick 7.1.0-7 and in 6.9.12-22. Fortunately, in the wild, few users utilize the `module` policy and instead use the `coder` policy that is also our workaround recommendation: <policy domain="coder" rights="none" pattern="{PS,EPI,EPS,EPSF,EPSI}" />. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/ImageMagick/ImageMagick/security/advisories/GHSA-qvhr-jj4p-j2qr - https://github.com/ImageMagick/ImageMagick/commit/01faddbe2711a4156180c4a92837e2f23683cc68 - https://github.com/ImageMagick/ImageMagick/commit/35893e7cad78ce461fcaffa56076c11700ba5e4e - h
180c4a92837e2f23683cc68 - https://github.com/ImageMagick/ImageMagick/commit/35893e7cad78ce461fcaffa56076c11700ba5e4e - https://lists.debian.org/debian-lts-announce/2023/05/msg00020.html
CVE ID: CVE-2021-39213 State: PUBLISHED Published: 2021-09-15T17:05:09 Last Updated: 2024-08-04T01:58:18.177Z Severity: MEDIUM (CVSS 6.8 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N) Vendors: glpi-project Products: glpi Problem Types: CWE-74 Description: GLPI is a free Asset and IT management software package. Starting in version 9.1 and prior to version 9.5.6, GLPI with API Rest enabled is vulnerable to API bypass with custom header injection. This issue is fixed in version 9.5.6. One may disable API Rest as a workaround. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/glpi-project/glpi/releases/tag/9.5.6 - https://github.com/glpi-project/glpi/security/ad
References: - https://github.com/glpi-project/glpi/releases/tag/9.5.6 - https://github.com/glpi-project/glpi/security/advisories/GHSA-6w9f-2m6g-5777
CVE ID: CVE-2021-39214 State: PUBLISHED Published: 2021-09-16T15:10:10 Last Updated: 2024-08-04T01:58:18.196Z Severity: HIGH (CVSS 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) Vendors: mitmproxy Products: mitmproxy Problem Types: CWE-444 Description: mitmproxy is an interactive, SSL/TLS-capable intercepting proxy. In mitmproxy 7.0.2 and below, a malicious client or server is able to perform HTTP request smuggling attacks through mitmproxy. This means that a malicious client/server could smuggle a request/response through mitmproxy as part of another request/response's HTTP message body. While a smuggled request is still captured as part of another request's body, it does not appear in t
HTTP message body. While a smuggled request is still captured as part of another request's body, it does not appear in the request list and does not go through the usual mitmproxy event hooks, where users may have implemented custom access control checks or input sanitization. Unless one uses mitmproxy to protect an HTTP/1 service, no action is required. The vulnerability has been fixed in mitmproxy 7.0.3 and above. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/mitmproxy/mitmproxy/security/advisories/GHSA-22gh-3r9q-xf38
CVE ID: CVE-2021-39215 State: PUBLISHED Published: 2021-09-15T17:20:11 Last Updated: 2024-08-04T01:58:18.219Z Severity: HIGH (CVSS 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) Vendors: jitsi Products: jitsi-meet Problem Types: CWE-287 Description: Jitsi Meet is an open source video conferencing application. In versions prior to 2.0.5963, a Prosody module allows the use of symmetrical algorithms to validate JSON web tokens. This means that tokens generated by arbitrary sources can be used to gain authorization to protected rooms. This issue is fixed in Jitsi Meet 2.0.5963. There are no known workarounds aside from updating. Additional Analyst Notes: - CVE Program Container: References: -
63. There are no known workarounds aside from updating. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/jitsi/jitsi-meet/security/advisories/GHSA-45ff-37jm-xjfx - https://github.com/jitsi/jitsi-meet/pull/9319
CVE ID: CVE-2021-39216 State: PUBLISHED Published: 2021-09-17T20:05:11 Last Updated: 2024-08-04T01:58:18.335Z Severity: MEDIUM (CVSS 6.3 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H) Vendors: bytecodealliance Products: wasmtime Problem Types: CWE-416 Description: Wasmtime is an open source runtime for WebAssembly & WASI. In Wasmtime from version 0.19.0 and before version 0.30.0 there was a use-after-free bug when passing `externref`s from the host to guest Wasm content. To trigger the bug, you have to explicitly pass multiple `externref`s from the host to a Wasm instance at the same time, either by passing multiple `externref`s as arguments from host code to a Wasm function, or returning mul
the same time, either by passing multiple `externref`s as arguments from host code to a Wasm function, or returning multiple `externref`s to Wasm from a multi-value return function defined in the host. If you do not have host code that matches one of these shapes, then you are not impacted. If Wasmtime's `VMExternRefActivationsTable` became filled to capacity after passing the first `externref` in, then passing in the second `externref` could trigger a garbage collection. However the first `externref` is not rooted until we pass control to Wasm, and therefore could be reclaimed by the collector if nothing else was holding a reference to it or otherwise keeping it alive. Then, when control w
aimed by the collector if nothing else was holding a reference to it or otherwise keeping it alive. Then, when control was passed to Wasm after the garbage collection, Wasm could use the first `externref`, which at this point has already been freed. We have reason to believe that the effective impact of this bug is relatively small because usage of `externref` is currently quite rare. The bug has been fixed, and users should upgrade to Wasmtime 0.30.0. If you cannot upgrade Wasmtime yet, you can avoid the bug by disabling reference types support in Wasmtime by passing `false` to `wasmtime::Config::wasm_reference_types`. Additional Analyst Notes: - CVE Program Container: References: - https:/
e` to `wasmtime::Config::wasm_reference_types`. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-v4cp-h94r-m7xf - https://github.com/bytecodealliance/wasmtime/commit/101998733b74624cbd348a2366d05760b40181f3 - https://crates.io/crates/wasmtime - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Z2Z33FTXFQ6EOINVEQIP4DFBG53G5XIY/ - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WAVBRYDDUIY2ZR3K3FO4BVYJKIMJ5TP7/
CVE ID: CVE-2021-39217 State: PUBLISHED Published: 2023-01-27T17:57:58.255Z Last Updated: 2025-03-10T21:18:43.503Z Severity: HIGH (CVSS 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) Vendors: OpenMage Products: magento-lts Problem Types: CWE-77 Description: OpenMage LTS is an e-commerce platform. Prior to versions 19.4.22 and 20.0.19, Custom Layout enabled admin users to execute arbitrary commands via block methods. Versions 19.4.22 and 20.0.19 contain patches for this issue. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://github.com/OpenMage/magento-lts/security/advisories/GHSA-c9q3-r4rv-mjm7 - https://github.com/OpenMage/magento-lts/comm
//github.com/OpenMage/magento-lts/security/advisories/GHSA-c9q3-r4rv-mjm7 - https://github.com/OpenMage/magento-lts/commit/289bd4b4f53622138e3e5c2d2cef7502d780086f - https://github.com/OpenMage/magento-lts/releases/tag/v19.4.22 - https://github.com/OpenMage/magento-lts/releases/tag/v20.0.19
CVE ID: CVE-2021-39218 State: PUBLISHED Published: 2021-09-17T20:10:19 Last Updated: 2024-08-04T01:58:18.261Z Severity: MEDIUM (CVSS 6.3 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H) Vendors: bytecodealliance Products: wasmtime Problem Types: CWE-590, CWE-787, CWE-125 Description: Wasmtime is an open source runtime for WebAssembly & WASI. In Wasmtime from version 0.26.0 and before version 0.30.0 is affected by a memory unsoundness vulnerability. There was an invalid free and out-of-bounds read and write bug when running Wasm that uses `externref`s in Wasmtime. To trigger this bug, Wasmtime needs to be running Wasm that uses `externref`s, the host creates non-null `externrefs`, Wasmtime perfo
is bug, Wasmtime needs to be running Wasm that uses `externref`s, the host creates non-null `externrefs`, Wasmtime performs a garbage collection (GC), and there has to be a Wasm frame on the stack that is at a GC safepoint where there are no live references at this safepoint, and there is a safepoint with live references earlier in this frame's function. Under this scenario, Wasmtime would incorrectly use the GC stack map for the safepoint from earlier in the function instead of the empty safepoint. This would result in Wasmtime treating arbitrary stack slots as `externref`s that needed to be rooted for GC. At the *next* GC, it would be determined that nothing was referencing these bogus `ex
s that needed to be rooted for GC. At the *next* GC, it would be determined that nothing was referencing these bogus `externref`s (because nothing could ever reference them, because they are not really `externref`s) and then Wasmtime would deallocate them and run `<ExternRef as Drop>::drop` on them. This results in a free of memory that is not necessarily on the heap (and shouldn't be freed at this moment even if it was), as well as potential out-of-bounds reads and writes. Even though support for `externref`s (via the reference types proposal) is enabled by default, unless you are creating non-null `externref`s in your host code or explicitly triggering GCs, you cannot be affected by this b
you are creating non-null `externref`s in your host code or explicitly triggering GCs, you cannot be affected by this bug. We have reason to believe that the effective impact of this bug is relatively small because usage of `externref` is currently quite rare. This bug has been patched and users should upgrade to Wasmtime version 0.30.0. If you cannot upgrade Wasmtime at this time, you can avoid this bug by disabling the reference types proposal by passing `false` to `wasmtime::Config::wasm_reference_types`. Additional Analyst Notes: - CVE Program Container: References: - https://crates.io/crates/wasmtime - https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-4873-36h9-wv49
https://crates.io/crates/wasmtime - https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-4873-36h9-wv49 - https://github.com/bytecodealliance/wasmtime/commit/398a73f0dd862dbe703212ebae8e34036a18c11c - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Z2Z33FTXFQ6EOINVEQIP4DFBG53G5XIY/ - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WAVBRYDDUIY2ZR3K3FO4BVYJKIMJ5TP7/
CVE ID: CVE-2021-39219 State: PUBLISHED Published: 2021-09-17T20:10:13 Last Updated: 2024-08-04T01:58:18.272Z Severity: MEDIUM (CVSS 6.3 CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H) Vendors: bytecodealliance Products: wasmtime Problem Types: CWE-843 Description: Wasmtime is an open source runtime for WebAssembly & WASI. Wasmtime before version 0.30.0 is affected by a type confusion vulnerability. As a Rust library the `wasmtime` crate clearly marks which functions are safe and which are `unsafe`, guaranteeing that if consumers never use `unsafe` then it should not be possible to have memory unsafety issues in their embeddings of Wasmtime. An issue was discovered in the safe API of `Linker::
ble to have memory unsafety issues in their embeddings of Wasmtime. An issue was discovered in the safe API of `Linker::func_*` APIs. These APIs were previously not sound when one `Engine` was used to create the `Linker` and then a different `Engine` was used to create a `Store` and then the `Linker` was used to instantiate a module into that `Store`. Cross-`Engine` usage of functions is not supported in Wasmtime and this can result in type confusion of function pointers, resulting in being able to safely call a function with the wrong type. Triggering this bug requires using at least two `Engine` values in an embedding and then additionally using two different values with a `Linker` (one at
ng at least two `Engine` values in an embedding and then additionally using two different values with a `Linker` (one at the creation time of the `Linker` and another when instantiating a module with the `Linker`). It's expected that usage of more-than-one `Engine` in an embedding is relatively rare since an `Engine` is intended to be a globally shared resource, so the expectation is that the impact of this issue is relatively small. The fix implemented is to change this behavior to `panic!()` in Rust instead of silently allowing it. Using different `Engine` instances with a `Linker` is a programmer bug that `wasmtime` catches at runtime. This bug has been patched and users should upgrade to
a `Linker` is a programmer bug that `wasmtime` catches at runtime. This bug has been patched and users should upgrade to Wasmtime version 0.30.0. If you cannot upgrade Wasmtime and are using more than one `Engine` in your embedding it's recommended to instead use only one `Engine` for the entire program if possible. An `Engine` is designed to be a globally shared resource that is suitable to have only one for the lifetime of an entire process. If using multiple `Engine`s is required then code should be audited to ensure that `Linker` is only used with one `Engine`. Additional Analyst Notes: - CVE Program Container: References: - https://crates.io/crates/wasmtime - https://github.com/bytecode
al Analyst Notes: - CVE Program Container: References: - https://crates.io/crates/wasmtime - https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-q879-9g95-56mx - https://github.com/bytecodealliance/wasmtime/commit/b39f087414f27ae40c44449ed5d1154e03449bff - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Z2Z33FTXFQ6EOINVEQIP4DFBG53G5XIY/ - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WAVBRYDDUIY2ZR3K3FO4BVYJKIMJ5TP7/
CVE ID: CVE-2021-39220 State: PUBLISHED Published: 2021-10-25T18:55:14 Last Updated: 2024-08-04T01:58:18.216Z Severity: LOW (CVSS 3.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N) Vendors: nextcloud Products: security-advisories Problem Types: CWE-20, CWE-200 Description: Nextcloud is an open-source, self-hosted productivity platform The Nextcloud Mail application prior to versions 1.10.4 and 1.11.0 does by default not render images in emails to not leak the read state or user IP. The privacy filter failed to filter images with a relative protocol. It is recommended that the Nextcloud Mail application is upgraded to 1.10.4 or 1.11.0. There are no known workarounds aside from upgrading. Addit
e Nextcloud Mail application is upgraded to 1.10.4 or 1.11.0. There are no known workarounds aside from upgrading. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/nextcloud/security-advisories/security/advisories/GHSA-6q9v-wm8r-rcv5 - https://github.com/nextcloud/mail/pull/5470 - https://hackerone.com/reports/1308147