Описание
An allocation of resources without limits or throttling vulnerability exists in curl <v7.88.0 based on the "chained" HTTP compression algorithms, meaning that a server response can be compressed multiple times and potentially with differentalgorithms. The number of acceptable "links" in this "decompression chain" wascapped, but the cap was implemented on a per-header basis allowing a maliciousserver to insert a virtually unlimited number of compression steps simply byusing many headers. The use of such a decompression chain could result in a "malloc bomb", making curl end up spending enormous amounts of allocated heap memory, or trying to and returning out of memory errors.
A flaw was found in the Curl package. A malicious server can insert an unlimited number of compression steps. This decompression chain could result in out-of-memory errors.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| .NET Core 3.1 on Red Hat Enterprise Linux | rh-dotnet31-curl | Out of support scope | ||
| Red Hat Enterprise Linux 6 | curl | Out of support scope | ||
| Red Hat Enterprise Linux 7 | curl | Not affected | ||
| Red Hat Enterprise Linux 8 | curl | Fixed | RHSA-2023:1140 | 07.03.2023 |
| Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support | curl | Fixed | RHSA-2023:3460 | 06.06.2023 |
| Red Hat Enterprise Linux 8.4 Telecommunications Update Service | curl | Fixed | RHSA-2023:3460 | 06.06.2023 |
| Red Hat Enterprise Linux 8.4 Update Services for SAP Solutions | curl | Fixed | RHSA-2023:3460 | 06.06.2023 |
| Red Hat Enterprise Linux 8.6 Extended Update Support | curl | Fixed | RHSA-2023:1842 | 18.04.2023 |
| Red Hat Enterprise Linux 9 | curl | Fixed | RHSA-2023:1701 | 11.04.2023 |
| Red Hat Enterprise Linux 9 | curl | Fixed | RHSA-2023:1701 | 11.04.2023 |
Показывать по
Дополнительная информация
Статус:
EPSS
6.5 Medium
CVSS3
Связанные уязвимости
An allocation of resources without limits or throttling vulnerability exists in curl <v7.88.0 based on the "chained" HTTP compression algorithms, meaning that a server response can be compressed multiple times and potentially with differentalgorithms. The number of acceptable "links" in this "decompression chain" wascapped, but the cap was implemented on a per-header basis allowing a maliciousserver to insert a virtually unlimited number of compression steps simply byusing many headers. The use of such a decompression chain could result in a "malloc bomb", making curl end up spending enormous amounts of allocated heap memory, or trying to and returning out of memory errors.
An allocation of resources without limits or throttling vulnerability exists in curl <v7.88.0 based on the "chained" HTTP compression algorithms, meaning that a server response can be compressed multiple times and potentially with differentalgorithms. The number of acceptable "links" in this "decompression chain" wascapped, but the cap was implemented on a per-header basis allowing a maliciousserver to insert a virtually unlimited number of compression steps simply byusing many headers. The use of such a decompression chain could result in a "malloc bomb", making curl end up spending enormous amounts of allocated heap memory, or trying to and returning out of memory errors.
An allocation of resources without limits or throttling vulnerability ...
EPSS
6.5 Medium
CVSS3