What is GHSA-9WMC-RG4H-28WV?

GHSA-9WMC-RG4H-28WV is a high-severity security vulnerability in github.com/kumahq/kuma (go), affecting versions >= 2.4.0, < 2.4.3. It is fixed in 2.4.3, 2.3.3, 2.2.4, 2.1.8, 2.0.8.

How severe is GHSA-9WMC-RG4H-28WV?

GHSA-9WMC-RG4H-28WV has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/kumahq/kuma are affected by GHSA-9WMC-RG4H-28WV?

github.com/kumahq/kuma (go) versions >= 2.4.0, < 2.4.3 is affected.

Is there a fix for GHSA-9WMC-RG4H-28WV?

Yes. GHSA-9WMC-RG4H-28WV is fixed in 2.4.3, 2.3.3, 2.2.4, 2.1.8, 2.0.8. Upgrade to this version or later.

Is GHSA-9WMC-RG4H-28WV exploitable, and should I be worried?

Whether GHSA-9WMC-RG4H-28WV is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-9WMC-RG4H-28WV is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-9WMC-RG4H-28WV?

Upgrade: github.com/kumahq/kuma to 2.4.3 or later, github.com/kumahq/kuma to 2.3.3 or later, github.com/kumahq/kuma to 2.2.4 or later, github.com/kumahq/kuma to 2.1.8 or later, github.com/kumahq/kuma to 2.0.8 or later.

GHSA-9WMC-RG4H-28WV in github.com/kumahq/kuma

Q: How severe is GHSA-9WMC-RG4H-28WV?

GHSA-9WMC-RG4H-28WV has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of github.com/kumahq/kuma are affected by GHSA-9WMC-RG4H-28WV?

github.com/kumahq/kuma (go) versions >= 2.4.0, < 2.4.3 is affected.

Q: Is there a fix for GHSA-9WMC-RG4H-28WV?

Yes. GHSA-9WMC-RG4H-28WV is fixed in 2.4.3, 2.3.3, 2.2.4, 2.1.8, 2.0.8. Upgrade to this version or later.

Q: Is GHSA-9WMC-RG4H-28WV exploitable, and should I be worried?

Whether GHSA-9WMC-RG4H-28WV is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-9WMC-RG4H-28WV is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-9WMC-RG4H-28WV?

Upgrade: github.com/kumahq/kuma to 2.4.3 or later, github.com/kumahq/kuma to 2.3.3 or later, github.com/kumahq/kuma to 2.2.4 or later, github.com/kumahq/kuma to 2.1.8 or later, github.com/kumahq/kuma to 2.0.8 or later.

Summary

github.com/kumahq/kuma affected by CVE-2023-44487

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

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.

GHSA-9WMC-RG4H-28WV has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.4.3, 2.3.3, 2.2.4, 2.1.8, 2.0.8); upgrading removes the vulnerable code path.

Affected versions

github.com/kumahq/kuma (>= 2.4.0, < 2.4.3) github.com/kumahq/kuma (>= 2.3.0, < 2.3.3) github.com/kumahq/kuma (>= 2.2.0, < 2.2.4) github.com/kumahq/kuma (>= 2.1.0, < 2.1.8) github.com/kumahq/kuma (< 2.0.8)

Security releases

github.com/kumahq/kuma → 2.4.3 (go) github.com/kumahq/kuma → 2.3.3 (go) github.com/kumahq/kuma → 2.2.4 (go) github.com/kumahq/kuma → 2.1.8 (go) github.com/kumahq/kuma → 2.0.8 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

https://github.com/kumahq/kuma/pull/8023
https://github.com/kumahq/kuma/pull/8001
https://github.com/kumahq/kuma/pull/8034

Frequently Asked Questions

What is GHSA-9WMC-RG4H-28WV? GHSA-9WMC-RG4H-28WV is a high-severity security vulnerability in github.com/kumahq/kuma (go), affecting versions >= 2.4.0, < 2.4.3. It is fixed in 2.4.3, 2.3.3, 2.2.4, 2.1.8, 2.0.8.
How severe is GHSA-9WMC-RG4H-28WV? GHSA-9WMC-RG4H-28WV has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/kumahq/kuma are affected by GHSA-9WMC-RG4H-28WV? github.com/kumahq/kuma (go) versions >= 2.4.0, < 2.4.3 is affected.
Is there a fix for GHSA-9WMC-RG4H-28WV? Yes. GHSA-9WMC-RG4H-28WV is fixed in 2.4.3, 2.3.3, 2.2.4, 2.1.8, 2.0.8. Upgrade to this version or later.
Is GHSA-9WMC-RG4H-28WV exploitable, and should I be worried? Whether GHSA-9WMC-RG4H-28WV is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-9WMC-RG4H-28WV is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-9WMC-RG4H-28WV?
- Upgrade github.com/kumahq/kuma to 2.4.3 or later
- Upgrade github.com/kumahq/kuma to 2.3.3 or later
- Upgrade github.com/kumahq/kuma to 2.2.4 or later
- Upgrade github.com/kumahq/kuma to 2.1.8 or later
- Upgrade github.com/kumahq/kuma to 2.0.8 or later