Yes. org.eclipse.jetty.http2:http2-common (Maven): upgrade to 9.4.54 or later; org.eclipse.jetty.http2:jetty-http2-common (Maven): upgrade to 12.0.6 or later; org.eclipse.jetty.http3:http3-common (Maven): upgrade to 10.0.20 or later; org.eclipse.jetty.http3:jetty-http3-common (Maven): upgrade to 12.0.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2024-22201?
Check whether you run org.eclipse.jetty.http2:http2-common (Maven), org.eclipse.jetty.http2:jetty-http2-common (Maven), org.eclipse.jetty.http3:http3-common (Maven) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
org.eclipse.jetty.http2:http2-common (Maven): upgrade to 9.4.54 or later
# set org.eclipse.jetty.http2:http2-common to 9.4.54 in your pom.xml or build.gradle
org.eclipse.jetty.http2:jetty-http2-common (Maven): upgrade to 12.0.6 or later
# set org.eclipse.jetty.http2:jetty-http2-common to 12.0.6 in your pom.xml or build.gradle
org.eclipse.jetty.http3:http3-common (Maven): upgrade to 10.0.20 or later
# set org.eclipse.jetty.http3:http3-common to 10.0.20 in your pom.xml or build.gradle
org.eclipse.jetty.http3:jetty-http3-common (Maven): upgrade to 12.0.6 or later
# set org.eclipse.jetty.http3:jetty-http3-common to 12.0.6 in your pom.xml or build.gradle