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.
Metrics
Affected Vendors & Products
References
History
No history.
MITRE
Status: PUBLISHED
Assigner: hackerone
Published: 2023-09-15T03:21:54.348Z
Updated: 2024-08-02T17:30:12.356Z
Reserved: 2023-07-12T01:00:11.881Z
Link: CVE-2023-38039
Vulnrichment
No data.
NVD
Status : Modified
Published: 2023-09-15T04:15:10.127
Modified: 2024-11-21T08:12:43.457
Link: CVE-2023-38039
Redhat