Описание
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'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.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Advanced Cluster Management for Kubernetes 2 | node-fetch | Fix deferred | ||
| Red Hat Advanced Cluster Management for Kubernetes 2 | acmesolver-container | Fixed | RHEA-2021:0729 | 04.03.2021 |
| Red Hat Advanced Cluster Management for Kubernetes 2 | acm-must-gather-container | Fixed | RHEA-2021:0729 | 04.03.2021 |
| Red Hat Advanced Cluster Management for Kubernetes 2 | acm-operator-bundle-container | Fixed | RHEA-2021:0729 | 04.03.2021 |
| Red Hat Advanced Cluster Management for Kubernetes 2 | application-ui-container | Fixed | RHEA-2021:0729 | 04.03.2021 |
| Red Hat Advanced Cluster Management for Kubernetes 2 | cainjector-container | Fixed | RHEA-2021:0729 | 04.03.2021 |
| Red Hat Advanced Cluster Management for Kubernetes 2 | cert-manager-controller-container | Fixed | RHEA-2021:0729 | 04.03.2021 |
| Red Hat Advanced Cluster Management for Kubernetes 2 | cert-manager-webhook-container | Fixed | RHEA-2021:0729 | 04.03.2021 |
| Red Hat Advanced Cluster Management for Kubernetes 2 | cert-policy-controller-container | Fixed | RHEA-2021:0729 | 04.03.2021 |
| Red Hat Advanced Cluster Management for Kubernetes 2 | clusterlifecycle-state-metrics-container | Fixed | RHEA-2021:0729 | 04.03.2021 |
Показывать по
Дополнительная информация
Статус:
EPSS
5.3 Medium
CVSS3
Связанные уязвимости
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'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.
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'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.
node-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the si ...
The `size` option isn't honored after following a redirect in node-fetch
Уязвимость библиотеки node-fetch прикладного программного обеспечения Аврора Центр, связанная с неконтролируемым расходом ресурсов, позволяющая нарушителю вызвать отказ в обслуживании
EPSS
5.3 Medium
CVSS3