-
-
Notifications
You must be signed in to change notification settings - Fork 583
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CVE in Jetty #2340
Comments
I doubt we use it, but let's check |
some downstream consumers may use it, as it is a dependency, and maven does not have a distinction between api & implementation dependencies like gradle does |
For what it is worth, we are running Javalin 6.2.0 with Jetty 11.0.24 |
For
Like you said, it's not affecting us and the chance it's affecting our users is also pretty low - if you'd be digging that deep in the Jetty, you'd probably just use raw Jetty anyway, without Javalin:
We will most likely get rid of it in Javalin 8.x, with Jetty 12: |
hmmm, I see tbh I just opened the issue because my ide was complaining lol |
Currently, there are 2 CVEs present in the version of Jetty used in Javalin 6.3.0.
The second CVE has been patched in the latest snapshot of Javalin, due to updating to Jetty from
11.0.22
->11.0.24
, however no release has been made for this change.Currently, the only fix for CVE-2024-6763 is to update to Jetty ≥12.0.12. Are there any plans to do this in the near future?
The text was updated successfully, but these errors were encountered: