Описание
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.
| Релиз | Статус | Примечание |
|---|---|---|
| bionic | released | 7.58.0-2ubuntu3.23 |
| devel | released | 7.87.0-2ubuntu1 |
| esm-infra-legacy/trusty | not-affected | |
| esm-infra/bionic | not-affected | 7.58.0-2ubuntu3.23 |
| esm-infra/focal | not-affected | 7.68.0-1ubuntu2.16 |
| esm-infra/xenial | not-affected | |
| focal | released | 7.68.0-1ubuntu2.16 |
| jammy | released | 7.81.0-1ubuntu1.8 |
| kinetic | released | 7.85.0-1ubuntu0.3 |
| lunar | released | 7.87.0-2ubuntu1 |
Показывать по
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