CVE-2023-23916
Published: 15 February 2023
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.
Notes
Author | Note |
---|---|
mdeslaur | introduced in 7.57.0 |
Priority
Status
Package | Release | Status |
---|---|---|
curl Launchpad, Ubuntu, Debian |
bionic |
Released
(7.58.0-2ubuntu3.23)
|
focal |
Released
(7.68.0-1ubuntu2.16)
|
|
jammy |
Released
(7.81.0-1ubuntu1.8)
|
|
kinetic |
Released
(7.85.0-1ubuntu0.3)
|
|
trusty |
Not vulnerable
|
|
upstream |
Released
(7.88.0)
|
|
xenial |
Not vulnerable
|
|
Patches: upstream: https://github.com/curl/curl/commit/119fb187192a9ea13dc |
Severity score breakdown
Parameter | Value |
---|---|
Base score | 7.5 |
Attack vector | Network |
Attack complexity | Low |
Privileges required | None |
User interaction | None |
Scope | Unchanged |
Confidentiality | None |
Integrity impact | None |
Availability impact | High |
Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |