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.
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
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.

Status: PUBLISHED
Assigner: hackerone
Published:
Updated: 2025-02-13T17:01:44.367Z
Reserved: 2023-07-12T01:00:11.881Z
Link: CVE-2023-38039

No data.

Status : Modified
Published: 2023-09-15T04:15:10.127
Modified: 2024-11-21T08:12:43.457
Link: CVE-2023-38039


No data.