# CVE-2022-24667: swift-nio-http2 vulnerable to denial of service via mishandled HPACK variable length integer encoding > Remote attackers can crash SwiftNIO HTTP2 applications by sending crafted HPACK headers, causing service disruption. - **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:** 9 Feb 2022 - **Updated:** 3 Aug 2024 - **Also known as:** GHSA-w3f6-pc54-gfw7 ## What is CVE-2022-24667? CVE-2022-24667 is a high-severity denial of service vulnerability in SwiftNIO HTTP2, published on 9 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A program using swift-nio-http2 is vulnerable to a denial of service attack, caused by a network peer sending a specially crafted HPACK-encoded header block. This attack affects all swift-nio-http2 versions from 1.0.0 to 1.19.1. There are a number of implementation errors in the parsing of HPACK-encoded header blocks that allow maliciously crafted HPACK header blocks to cause crashes in processes using swift-nio-http2. Each of these crashes is triggered instead of an integer overflow. A malicious HPACK header block could be sent on any of the HPACK-carrying frames in a HTTP/2 connection (HEADERS and PUSH_PROMISE), at any position. Sending a HPACK header block does not require any special permission, so any HTTP/2 connection peer may send one. For clients, this means any server to which they connect may launch this attack. For servers, anyone they allow to connect to them may launch such an attack. The attack is low-effort: it takes very little resources to send an appropriately crafted field block. The impact on availability is high: receiving a frame carrying this field block immediately crashes the server, dropping all in-flight connections and causing the service to need to restart. It is straightforward for an attacker to repeatedly send appropriately crafted field blocks, so attackers require very few resources to achieve a substantial denial of service. The attack does not have any confidentiality or integrity risks in and of itself: swift-nio-http2 is parsing the field block in memory-safe code and the crash is triggered instead of an integer overflow. However, sudden process crashes can lead to violations of invariants in services, so it is possible that this attack can be used to trigger an error condition that has confidentiality or integrity risks. The risk can be mitigated if untrusted peers can be prevented from communicating with the service. This mitigation is not available to many services. The issue is fixed by rewriting the parsing code to correctly handle all conditions in the function. The principal issue was found by automated fuzzing by oss-fuzz, but several associated bugs in the same code were found by code audit and fixed at the same time Weakness: CWE-190 (Integer Overflow or Wraparound) ## Which versions are affected by CVE-2022-24667? 2 open source packages ship an affected version, including github.com/apple/swift-nio-http2. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/apple/swift-nio-http2` | SwiftURL | From 1.0.0 | 1.19.2 | | `github.com/apple/swift-nio-http2` | SwiftURL | From 1.0.0 | 1.19.2 | Products: Apple Swiftnio Http\/2. ## How do I fix CVE-2022-24667? Upgrade github.com/apple/swift-nio-http2 to 1.19.2 or later. ## Is CVE-2022-24667 being exploited? There is no known exploitation of CVE-2022-24667 in the wild and no public exploit code. ## Other vulnerabilities in SwiftNIO HTTP2 - [CVE-2022-0618](https://insights.sbomify.com/CVE-2022-0618/): Denial of service via HTTP/2 HEADERS frames padding (high 7.5) - [CVE-2022-24666](https://insights.sbomify.com/CVE-2022-24666/): swift-nio-http2 vulnerable to denial of service via invalid HTTP/2 HEADERS frame length (high 7.5) - [CVE-2022-24668](https://insights.sbomify.com/CVE-2022-24668/): swift-nio-http2 vulnerable to denial of service via ALTSVC or ORIGIN frames (high 7.5) - [CVE-2026-64785](https://insights.sbomify.com/CVE-2026-64785/): swift-nio-http2: Missing CR/LF/NUL validation in header values (medium 5.3) - [CVE-2026-28898](https://insights.sbomify.com/CVE-2026-28898/): SwiftNIO HTTP/2: HTTP/2-to-HTTP/1 Request Smuggling via unvalidated :path pseudo-header in HTTP2ToHTTP1Codec (medium 5.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-24667 and fix it if it is affected. What it is: CVE-2022-24667 is a high-severity denial of service vulnerability in SwiftNIO HTTP2, published on 9 Feb 2022. 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-2022-24667 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/apple/swift-nio-http2 (SwiftURL): affected from 1.0.0; fixed in 1.19.2 - github.com/apple/swift-nio-http2 (SwiftURL): affected from 1.0.0; fixed in 1.19.2 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-2022-24667/ (Markdown: https://insights.sbomify.com/CVE-2022-24667/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-24667 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-24667 - OSV: https://osv.dev/vulnerability/CVE-2022-24667 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-24667/ Summaries are generated and may contain mistakes; the official description above is the record.