# GHSA-9wmc-rg4h-28wv: github.com/kumahq/kuma affected by CVE-2023-44487 > Attackers can cause denial of service in Kuma service mesh gateways by sending rapid HTTP/2 reset frames, requiring patching or disabling HTTP/2. - **Severity:** Not scored - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 17 Oct 2023 ## What is GHSA-9wmc-rg4h-28wv? GHSA-9wmc-rg4h-28wv is a denial of service vulnerability in github.com/kumahq/kuma, published on 17 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description ### Impact Envoy and Go HTTP/2 protocol stack is vulnerable to the "Rapid Reset" class of exploits, which send a sequence of HEADERS frames optionally followed by RST_STREAM frames. This can be exercised if you use the builtin gateway and receive untrusted http2 traffic. ### Patches https://github.com/kumahq/kuma/pull/8023 https://github.com/kumahq/kuma/pull/8001 https://github.com/kumahq/kuma/pull/8034 ### Workarounds Disable http2 on the gateway listener with a MeshProxyPatch or ProxyTemplate. ### References https://github.com/advisories/GHSA-qppj-fm5r-hxr3 https://github.com/golang/go/issues/63417 https://github.com/envoyproxy/envoy/security/advisories/GHSA-jhv4-f7mr-xx76 https://cloud.google.com/blog/products/identity-security/how-it-works-the-novel-http2-rapid-reset-ddos-attack https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/?sf269548684=1 https://www.envoyproxy.io/docs/envoy/latest/configuration/best_practices/edge ## Which versions are affected by GHSA-9wmc-rg4h-28wv? 10 open source packages ship an affected version, including github.com/kumahq/kuma. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/kumahq/kuma` | Go | All versions | 2.0.8 | | `github.com/kumahq/kuma` | Go | All versions | 2.0.8 | | `github.com/kumahq/kuma` | Go | From 2.1.0 | 2.1.8 | | `github.com/kumahq/kuma` | Go | From 2.1.0 | 2.1.8 | | `github.com/kumahq/kuma` | Go | From 2.2.0 | 2.2.4 | | `github.com/kumahq/kuma` | Go | From 2.2.0 | 2.2.4 | | `github.com/kumahq/kuma` | Go | From 2.3.0 | 2.3.3 | | `github.com/kumahq/kuma` | Go | From 2.3.0 | 2.3.3 | | `github.com/kumahq/kuma` | Go | From 2.4.0 | 2.4.3 | | `github.com/kumahq/kuma` | Go | From 2.4.0 | 2.4.3 | ## How do I fix GHSA-9wmc-rg4h-28wv? Upgrade github.com/kumahq/kuma to a fixed version for your release line: 2.0.8, 2.1.8, 2.2.4 or 2.3.3. ## Is GHSA-9wmc-rg4h-28wv being exploited? There is no known exploitation of GHSA-9wmc-rg4h-28wv in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-9wmc-rg4h-28wv and fix it if it is affected. What it is: GHSA-9wmc-rg4h-28wv is a denial of service vulnerability in github.com/kumahq/kuma, published on 17 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of GHSA-9wmc-rg4h-28wv in the wild and no public exploit code. Affected packages and fixed versions: - github.com/kumahq/kuma (Go): affected all versions; fixed in 2.0.8 - github.com/kumahq/kuma (Go): affected all versions; fixed in 2.0.8 - github.com/kumahq/kuma (Go): affected from 2.1.0; fixed in 2.1.8 - github.com/kumahq/kuma (Go): affected from 2.1.0; fixed in 2.1.8 - github.com/kumahq/kuma (Go): affected from 2.2.0; fixed in 2.2.4 - github.com/kumahq/kuma (Go): affected from 2.2.0; fixed in 2.2.4 - github.com/kumahq/kuma (Go): affected from 2.3.0; fixed in 2.3.3 - github.com/kumahq/kuma (Go): affected from 2.3.0; fixed in 2.3.3 - github.com/kumahq/kuma (Go): affected from 2.4.0; fixed in 2.4.3 - github.com/kumahq/kuma (Go): affected from 2.4.0; fixed in 2.4.3 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/GHSA-9wmc-rg4h-28wv/ (Markdown: https://insights.sbomify.com/GHSA-9wmc-rg4h-28wv/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-9wmc-rg4h-28wv --- From sbomify Insights: https://insights.sbomify.com/GHSA-9wmc-rg4h-28wv/ Summaries are generated and may contain mistakes; the official description above is the record.