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.
[
{
"vendor": "n/a",
"product": "https://github.com/curl/curl",
"versions": [
{
"version": "Fixed in 7.88.0",
"status": "affected"
}
]
}
]
hackerone.com/reports/1826048
lists.debian.org/debian-lts-announce/2023/02/msg00035.html
lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BQKE6TXYDHOTFHLTBZ5X73GTKI7II5KO/
security.gentoo.org/glsa/202310-12
security.netapp.com/advisory/ntap-20230309-0006/
www.debian.org/security/2023/dsa-5365