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
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
History
No history.
Information
Published : 2023-09-15 04:15
Updated : 2024-04-01 15:45
NVD link : CVE-2023-38039
Mitre link : CVE-2023-38039
CVE.ORG link : CVE-2023-38039
JSON object : View
Products Affected
microsoft
- windows_11_21h2
- windows_server_2022
- windows_10_22h2
- windows_10_21h2
- windows_11_22h2
- windows_server_2019
- windows_11_23h2
- windows_10_1809
fedoraproject
- fedora
haxx
- curl
CWE
CWE-770
Allocation of Resources Without Limits or Throttling