# CVE-2024-27316: Apache HTTP Server: HTTP/2 DoS by memory exhaustion on endless continuation frames > Attackers can cause memory exhaustion and denial of service by sending endless HTTP/2 continuation frames to Apache HTTP Server. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 4 Apr 2024 - **Updated:** 4 Nov 2025 - **Also known as:** ALPINE-CVE-2024-27316, ALSA-2024:1786, ALSA-2024:1872, ALSA-2024:2564, AZL-40001, AZL-40012, AZL-43978, AZL-44151, BELL-CVE-2024-27316, BIT-apache-2024-27316, CLEANSTART-2026-DF56906, CLSA-2024-1716915132, CLSA-2024-1716923768, CLSA-2024-1716924362, CLSA-2024-1728932179, DEBIAN-CVE-2024-27316, GHSA-5qc4-82jh-h385, OESA-2024-1452, RHSA-2024:1786, RHSA-2024:1872, RHSA-2024:2564, RHSA-2024:2907, RHSA-2024:3402, RHSA-2024:3417, RHSA-2024:4390, RLSA-2024:1786, RLSA-2024:2564, UBUNTU-CVE-2024-27316 ## What is CVE-2024-27316? CVE-2024-27316 is a high-severity denial of service vulnerability in Apache Http Server, published on 4 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description HTTP/2 incoming headers exceeding the limit are temporarily buffered in nghttp2 in order to generate an informative HTTP 413 response. If a client does not stop sending headers, this leads to memory exhaustion. Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling) ## Which versions are affected by CVE-2024-27316? 1 open source package ship an affected version, including apache. It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `apache` | Bitnami | From 2.4.17 | 2.4.59 | | `httpd` | AlmaLinux:8 | All versions | 2.4.37-62.module_el8.9.0+3646+acd210d0 | | `httpd-devel` | AlmaLinux:8 | All versions | 2.4.37-62.module_el8.9.0+3646+acd210d0 | | `httpd-filesystem` | AlmaLinux:8 | All versions | 2.4.37-62.module_el8.9.0+3646+acd210d0 | | `httpd-manual` | AlmaLinux:8 | All versions | 2.4.37-62.module_el8.9.0+3646+acd210d0 | | `httpd-tools` | AlmaLinux:8 | All versions | 2.4.37-62.module_el8.9.0+3646+acd210d0 | | `mod_http2` | AlmaLinux:8 | All versions | 1.15.7-8.module_el8.9.0+3809+48080a14.5.alma.1 | | `mod_ldap` | AlmaLinux:8 | All versions | 2.4.37-62.module_el8.9.0+3646+acd210d0 | | `mod_md` | AlmaLinux:8 | All versions | 1:2.0.8-8.module_el8.6.0+2872+fe0ff7aa | | `mod_md` | AlmaLinux:8 | All versions | 1:2.0.8-8.module_el8.6.0+3031+fb177b09 | | `mod_proxy_html` | AlmaLinux:8 | All versions | 1:2.4.37-62.module_el8.9.0+3646+acd210d0 | | `mod_session` | AlmaLinux:8 | All versions | 2.4.37-62.module_el8.9.0+3646+acd210d0 | | `mod_ssl` | AlmaLinux:8 | All versions | 1:2.4.37-62.module_el8.9.0+3646+acd210d0 | | `mod_http2` | AlmaLinux:9 | All versions | 1.15.19-5.el9_3.1 | | `mod_http2` | AlmaLinux:9 | All versions | 2.0.26-2.el9_4 | | `httpd` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.4.37-62.module+el8.9.0+19699+7a7a2044 | | `httpd-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.4.37-62.module+el8.9.0+19699+7a7a2044 | | `httpd-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.4.37-62.module+el8.9.0+19699+7a7a2044 | | `httpd-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.4.37-62.module+el8.9.0+19699+7a7a2044 | | `httpd-filesystem` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.4.37-62.module+el8.9.0+19699+7a7a2044 | | `httpd-manual` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.4.37-62.module+el8.9.0+19699+7a7a2044 | | `httpd-tools` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.4.37-62.module+el8.9.0+19699+7a7a2044 | | `httpd-tools-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.4.37-62.module+el8.9.0+19699+7a7a2044 | | `mod_http2` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.15.7-8.module+el8.9.0+21652+2dd1200b.5 | | `mod_http2-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.15.7-8.module+el8.9.0+21652+2dd1200b.5 | | `mod_http2-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.15.7-8.module+el8.9.0+21652+2dd1200b.5 | | `mod_ldap` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.4.37-62.module+el8.9.0+19699+7a7a2044 | | `mod_ldap-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.4.37-62.module+el8.9.0+19699+7a7a2044 | | `mod_md` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.0.8-8.module+el8.9.0+19080+567b90f8 | | `mod_md-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.0.8-8.module+el8.9.0+19080+567b90f8 | | `mod_md-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.0.8-8.module+el8.9.0+19080+567b90f8 | | `mod_proxy_html` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.4.37-62.module+el8.9.0+19699+7a7a2044 | | `mod_proxy_html-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.4.37-62.module+el8.9.0+19699+7a7a2044 | | `mod_session` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.4.37-62.module+el8.9.0+19699+7a7a2044 | | `mod_session-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.4.37-62.module+el8.9.0+19699+7a7a2044 | | `mod_ssl` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.4.37-62.module+el8.9.0+19699+7a7a2044 | | `mod_ssl-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:2.4.37-62.module+el8.9.0+19699+7a7a2044 | | `mod_http2` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.15.19-5.el9_3.1 | | `mod_http2` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.0.26-2.el9_4 | | `mod_http2-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.15.19-5.el9_3.1 | Products: Apache Http Server, Fedoraproject Fedora, Netapp Ontap. ## How do I fix CVE-2024-27316? Upgrade apache to 2.4.59 or later. ## Is CVE-2024-27316 being exploited? There is no known exploitation of CVE-2024-27316 in the wild and no public exploit code. Public exploit code: - Proof of concept (PoC) for CVE-2024-27316 (tested), CVE-2024-30255 (untested), CVE-2024-31309 (untested), CVE-2024-28182 (untested), CVE-2024-2653 (untested) and CVE-2024-27919 (untested) (github_poc): https://github.com/lockness-Ko/CVE-2024-27316 - https://github.com/aeyesec/CVE-2024-27316_poc (github_poc): https://github.com/aeyesec/CVE-2024-27316_poc ## Other vulnerabilities in Apache Http Server - [CVE-2021-42013](https://insights.sbomify.com/CVE-2021-42013/): Apache HTTP Server Path Traversal (critical 9.8, exploited in the wild) - [CVE-2024-38475](https://insights.sbomify.com/CVE-2024-38475/): Apache HTTP Server Improper Escaping of Output (critical 9.1, exploited in the wild) - [CVE-2021-40438](https://insights.sbomify.com/CVE-2021-40438/): Apache HTTP Server-Side Request Forgery (SSRF) (critical 9.0, exploited in the wild) - [CVE-2019-0211](https://insights.sbomify.com/CVE-2019-0211/): Apache HTTP Server Privilege Escalation (high 7.8, exploited in the wild) - [CVE-2021-41773](https://insights.sbomify.com/CVE-2021-41773/): Apache HTTP Server Path Traversal (high 7.5, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-27316 and fix it if it is affected. What it is: CVE-2024-27316 is a high-severity denial of service vulnerability in Apache Http Server, published on 4 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-27316 in the wild and no public exploit code. Affected packages and fixed versions: - apache (Bitnami): affected from 2.4.17; fixed in 2.4.59 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-27316/ (Markdown: https://insights.sbomify.com/CVE-2024-27316/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-27316 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-27316 - OSV: https://osv.dev/vulnerability/CVE-2024-27316 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-27316/ Summaries are generated and may contain mistakes; the official description above is the record.