https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 08:02:16 +0000 https://cve.radiocsirt.org/vuln/bdu:2021-02871 bdu:2021-02871 https://cve.radiocsirt.org/vuln/bdu:2021-02871 https://cve.radiocsirt.org/vuln/certfr-2020-avi-757 certfr-2020-avi-757 https://cve.radiocsirt.org/vuln/certfr-2020-avi-757 https://cve.radiocsirt.org/vuln/euvd-2026-42718 EUVD-2026-42718 https://cve.radiocsirt.org/vuln/euvd-2026-42718 https://cve.radiocsirt.org/vuln/fkie_cve-2020-15168 <p>node-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure. For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don&#39;t double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.</p> <p>node-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure. For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don&#39;t double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2020-15168 https://cve.radiocsirt.org/vuln/ghsa-w7rc-rwvf-8q5r <p><strong>Affected:</strong> npm: node-fetch</p> <p>### Impact Node Fetch did not honor the `size` option after following a redirect, which means that when a content size was over the limit, a `FetchError` would never get thrown and the process would end without failure.</p> <p>For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don&#39;t double-check the size of the data after `fetch()` has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.</p> <p>### Patches We released patched versions for both stable and beta channels:</p> <p>- For `v2`: 2.6.1 - For `v3`: 3.0.0-beta.9</p> <p>### Workarounds None, it is strongly recommended to update as soon as possible.</p> <p>### For more information If you have any questions or comments about this advisory: * Open an issue in [node-fetch](https://github.com/node-fetch/node-fetch/issues/new?assignees=&amp;labels=question&amp;template=support-or-usage.md&amp;title=Question%3A+) * Contact one of the core maintainers.</p> <p><strong>Affected:</strong> npm: node-fetch</p> <p>### Impact Node Fetch did not honor the `size` option after following a redirect, which means that when a content size was over the limit, a `FetchError` would never get thrown and the process would end without failure.</p> <p>For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don&#39;t double-check the size of the data after `fetch()` has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.</p> <p>### Patches We released patched versions for both stable and beta channels:</p> <p>- For `v2`: 2.6.1 - For `v3`: 3.0.0-beta.9</p> <p>### Workarounds None, it is strongly recommended to update as soon as possible.</p> <p>### For more information If you have any questions or comments about this advisory: * Open an issue in [node-fetch](https://github.com/node-fetch/node-fetch/issues/new?assignees=&amp;labels=question&amp;template=support-or-usage.md&amp;title=Question%3A+) * Contact one of the core maintainers.</p> https://cve.radiocsirt.org/vuln/ghsa-w7rc-rwvf-8q5r https://cve.radiocsirt.org/vuln/gsd-2020-15168 gsd-2020-15168 https://cve.radiocsirt.org/vuln/gsd-2020-15168 https://cve.radiocsirt.org/vuln/rhea-2021:0729 <p>golang-github-buger-jsonparser: infinite loop via a Delete call node-fetch: size of data after fetch() JS thread leads to DoS helm: Chart.yaml is not properly sanitized lead to injection of unwanted information into chart helm: write access to the index file allows an attacker to inject bad chart into repository helm: plugin names are not sanitized properly helm: write access to the git repository or plugin archive causing causing a local execution attack jsonparser: GET call can lead to a slice bounds out of range redisgraph: NULL pointer dereference because it mishandles an unquoted string</p> <p>golang-github-buger-jsonparser: infinite loop via a Delete call node-fetch: size of data after fetch() JS thread leads to DoS helm: Chart.yaml is not properly sanitized lead to injection of unwanted information into chart helm: write access to the index file allows an attacker to inject bad chart into repository helm: plugin names are not sanitized properly helm: write access to the git repository or plugin archive causing causing a local execution attack jsonparser: GET call can lead to a slice bounds out of range redisgraph: NULL pointer dereference because it mishandles an unquoted string</p> https://cve.radiocsirt.org/vuln/rhea-2021:0729 https://cve.radiocsirt.org/vuln/suse-su-2020:3235-1 <p>Security update for SUSE Manager Server 4.1</p> <p>Security update for SUSE Manager Server 4.1</p> https://cve.radiocsirt.org/vuln/suse-su-2020:3235-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-15168 <p><strong>Affected:</strong> Ubuntu:Pro:18.04:LTS: node-fetch, Ubuntu:20.04:LTS: node-fetch</p> <p>node-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure. For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don&#39;t double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.</p> <p><strong>Affected:</strong> Ubuntu:Pro:18.04:LTS: node-fetch, Ubuntu:20.04:LTS: node-fetch</p> <p>node-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure. For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don&#39;t double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-15168 https://cve.radiocsirt.org/vuln/wid-sec-w-2022-1603 <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM Tivoli Netcool/OMNIbus ausnutzen, um beliebigen Programmcode auszuführen, Informationen offenzulegen, Dateien zu manipulieren oder einen Denial of Service Zustand herbeizuführen.</p> <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM Tivoli Netcool/OMNIbus ausnutzen, um beliebigen Programmcode auszuführen, Informationen offenzulegen, Dateien zu manipulieren oder einen Denial of Service Zustand herbeizuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2022-1603