When an application tells libcurl it wants to allow HTTP/2 server push, and the amount of received headers for the push surpasses the maximum allowed limit (1000), libcurl aborts the server push. When aborting, libcurl inadvertently does not free all the previously allocated headers and instead leaks the memory. Further, this error condition fails silently and is therefore not easily detected by an application. If a server sends many `PUSH_PROMISE` frames with an excessive amount of headers, this can lead to multiple megabytes of memory leaked *per response*. HTTP/2 server push is a relatively rarely used feature. Reference: https://curl.se/docs/CVE-2024-2398.html Upstream patch: https://github.com/curl/curl/commit/deca8039991886a559b67bcd6
Created curl tracking bugs for this issue: Affects: fedora-all [bug 2271824] Created mingw-curl tracking bugs for this issue: Affects: fedora-all [bug 2271825]
This issue has been addressed in the following products: Red Hat JBoss Core Services Via RHSA-2024:2694 https://access.redhat.com/errata/RHSA-2024:2694
This issue has been addressed in the following products: JBoss Core Services on RHEL 7 JBoss Core Services for RHEL 8 Via RHSA-2024:2693 https://access.redhat.com/errata/RHSA-2024:2693
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Extended Update Support Via RHSA-2024:3998 https://access.redhat.com/errata/RHSA-2024:3998
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2024:5529 https://access.redhat.com/errata/RHSA-2024:5529
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2024:5654 https://access.redhat.com/errata/RHSA-2024:5654
This issue has been addressed in the following products: Service Interconnect 1.4 for RHEL 9 Via RHSA-2024:7213 https://access.redhat.com/errata/RHSA-2024:7213
This issue has been addressed in the following products: Service Interconnect 1 for RHEL 9 Via RHSA-2024:7374 https://access.redhat.com/errata/RHSA-2024:7374