When curl retrieves an HTTP response, it stores the incoming headers so that
they can be accessed later via the libcurl headers API.
However, curl did not have a limit in how many or how large headers it would
accept in a response, allowing a malicious server to stream an endless series
of headers and eventually cause curl to run out of heap memory.
References
Information
Published : 2023-09-15 04:15
Updated : 2023-12-12 21:15
NVD link : CVE-2023-38039
Mitre link : CVE-2023-38039
JSON object : View
Products Affected
fedoraproject
- fedora
haxx
- curl
CWE
CWE-770
Allocation of Resources Without Limits or Throttling
