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.
References
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
Configuration 4 (hide)
AND |
|
Configuration 5 (hide)
AND |
|
Configuration 6 (hide)
AND |
|
Configuration 7 (hide)
AND |
|
Configuration 8 (hide)
|
Configuration 9 (hide)
|
History
No history.
Information
Published : 2023-02-23 20:15
Updated : 2025-03-12 19:15
NVD link : CVE-2023-23916
Mitre link : CVE-2023-23916
CVE.ORG link : CVE-2023-23916
JSON object : View
Products Affected
netapp
- h300s_firmware
- h700s_firmware
- h410s_firmware
- clustered_data_ontap
- h300s
- h500s
- h410s
- h500s_firmware
- h700s
debian
- debian_linux
fedoraproject
- fedora
splunk
- universal_forwarder
haxx
- curl
CWE
CWE-770
Allocation of Resources Without Limits or Throttling