no CVE referenced
CVE details
CVE-2023-23916
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.
Affected ports (1)
| Port | Package | Version | Status | Maintainer |
|---|---|---|---|---|
| ftp/linux-rl9-curl | linux-rl9-curl | 7.76.1_13 | unaddressed | emulation@FreeBSD.org |
VuXML
Template for a VuXML entry
Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.
<vuln vid="FIXME (make newentry)">
<topic>FIXME -- FIXME</topic>
<affects>
<package>
<name>linux-rl9-curl</name>
<range><lt>7.88.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>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.</p>
</body>
</description>
<references>
<cvename>CVE-2023-23916</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2023-23916</url>
</references>
<dates>
<discovery>2023-02-23</discovery>
<entry>2026-10-25</entry>
</dates>
</vuln>