The initial Rapid-Reset fix for mod_http2 was not sufficient to mitigate reset attacks completely; there is still a potential resource leak. If reset requests are sent on a connection below the rate limit imposed by nghttp2, memory is still consumed per RST and persists until the connection is broken. This "slow drip" of <1000 RST per second is sufficient to disable a single connection.
Created httpd tracking bugs for this issue: Affects: fedora-all [bug 2245071] Created mod_http2 tracking bugs for this issue: Affects: fedora-all [bug 2245070]
During "normal" HTTP/2 use, the probability to hit this bug is very low. The kept memory would not become noticeable before the connection closes or times out.
This issue has been addressed in the following products: JBoss Core Services on RHEL 7 JBoss Core Services for RHEL 8 Via RHSA-2023:7625 https://access.redhat.com/errata/RHSA-2023:7625
This issue has been addressed in the following products: Red Hat JBoss Core Services Via RHSA-2023:7626 https://access.redhat.com/errata/RHSA-2023:7626
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2024:2368 https://access.redhat.com/errata/RHSA-2024:2368
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.8 Extended Update Support Via RHSA-2024:2891 https://access.redhat.com/errata/RHSA-2024:2891
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2024:3121 https://access.redhat.com/errata/RHSA-2024:3121