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.
2023-09-15T04:15:10.127
2024-11-21T08:12:43.457
Modified
CVSSv3.1: 7.5 (HIGH)
Type | Vendor | Product | Version/Range | Vulnerable? |
---|---|---|---|---|
Application | haxx | curl | < 8.3.0 | Yes |
Operating System | fedoraproject | fedora | 37 | Yes |
Operating System | fedoraproject | fedora | 38 | Yes |
Operating System | fedoraproject | fedora | 39 | Yes |
Operating System | microsoft | windows_10_1809 | < 10.0.17763.5122 | Yes |
Operating System | microsoft | windows_10_21h2 | < 10.0.19044.3693 | Yes |
Operating System | microsoft | windows_10_22h2 | < 10.0.19045.3693 | Yes |
Operating System | microsoft | windows_11_21h2 | < 10.0.22000.2600 | Yes |
Operating System | microsoft | windows_11_22h2 | < 10.0.22621.2715 | Yes |
Operating System | microsoft | windows_11_23h2 | < 10.0.22631.2715 | Yes |
Operating System | microsoft | windows_server_2019 | < 10.0.17763.5122 | Yes |
Operating System | microsoft | windows_server_2022 | < 10.0.20348.2113 | Yes |