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.
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
Alpine | edge-main | noarch | curl | < 8.3.0-r0 | UNKNOWN |
Alpine | 3.15-main | noarch | curl | < 8.3.0-r0 | UNKNOWN |
Alpine | 3.16-main | noarch | curl | < 8.3.0-r0 | UNKNOWN |
Alpine | 3.17-main | noarch | curl | < 8.3.0-r0 | UNKNOWN |
Alpine | 3.18-main | noarch | curl | < 8.3.0-r0 | UNKNOWN |
Alpine | 3.19-main | noarch | curl | < 8.3.0-r0 | UNKNOWN |
Alpine | 3.20-main | noarch | curl | < 8.3.0-r0 | UNKNOWN |