Yes. org.eclipse.jetty:jetty-servlets (Maven): upgrade to 9.4.52 or later; org.eclipse.jetty.ee10:jetty-ee10-servlets (Maven): upgrade to 12.0.0-beta2 or later; org.eclipse.jetty.ee8:jetty-ee8-servlets (Maven): upgrade to 12.0.0-beta2 or later; org.eclipse.jetty.ee9:jetty-ee9-servlets (Maven): upgrade to 12.0.0-beta2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2023-36479?
Check whether you run org.eclipse.jetty:jetty-servlets (Maven), org.eclipse.jetty.ee10:jetty-ee10-servlets (Maven), org.eclipse.jetty.ee8:jetty-ee8-servlets (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:jetty-servlets (Maven): upgrade to 9.4.52 or later
# set org.eclipse.jetty:jetty-servlets to 9.4.52 in your pom.xml or build.gradle
org.eclipse.jetty.ee10:jetty-ee10-servlets (Maven): upgrade to 12.0.0-beta2 or later
# set org.eclipse.jetty.ee10:jetty-ee10-servlets to 12.0.0-beta2 in your pom.xml or build.gradle
org.eclipse.jetty.ee8:jetty-ee8-servlets (Maven): upgrade to 12.0.0-beta2 or later
# set org.eclipse.jetty.ee8:jetty-ee8-servlets to 12.0.0-beta2 in your pom.xml or build.gradle
org.eclipse.jetty.ee9:jetty-ee9-servlets (Maven): upgrade to 12.0.0-beta2 or later
# set org.eclipse.jetty.ee9:jetty-ee9-servlets to 12.0.0-beta2 in your pom.xml or build.gradle