Skip to content
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

Jetty Vulnerability CVE-2023-36478 and CVE-2023-40167 #2017

Closed
halprin opened this issue Oct 12, 2023 · 7 comments
Closed

Jetty Vulnerability CVE-2023-36478 and CVE-2023-40167 #2017

halprin opened this issue Oct 12, 2023 · 7 comments

Comments

@halprin
Copy link

halprin commented Oct 12, 2023

Jetty 11.0.15 has two vulnerabilities open against it. This is the version that Javalin 5.6.2 depends on.

Jetty has fixed both of these vulnerabilities in version 11.0.16. Can we release a new Javalin 5 version that uses at least version 11.0.16 of Jetty?

@dzikoysk
Copy link
Member

dzikoysk commented Oct 12, 2023

Sure, would you like to submit a PR? As far as I remember, @zugazagoitia checked that we were not affected by this, but it's good to keep Jetty up-to-date anyway :)

Edit: By the way, there's already an v11.0.17, so I guess we should use that one.

@halprin
Copy link
Author

halprin commented Oct 12, 2023

Oh sure, happy to! I notice that the master branch already has 11.0.16 in it (albeit 11.0.17 has been released), but the javalin-5x branch is still using 11.0.15. Not sure what it takes to get that update moved over to the javalin-5x branch, if I should open a PR directly against the javalin-5x branch, or what the general branching strategy is.

@dzikoysk
Copy link
Member

Yup, just open the new PR for 5.x :) We don't really care about syncing 5.x with 6.x at this point, especially that we'll probably replace Jetty 11 with 12 before the 6.x release.

@halprin
Copy link
Author

halprin commented Oct 12, 2023

Perfect, will do!

@halprin
Copy link
Author

halprin commented Oct 12, 2023

Done. I created a PR against the javalin-5x branch.

@dzikoysk
Copy link
Member

Thanks, now we have to wait for @tipsy :) He's currently slightly busy due to business trip, but it should be merged in the upcoming days.

@zugazagoitia
Copy link
Member

zugazagoitia commented Oct 13, 2023

Sure, would you like to submit a PR? As far as I remember, @zugazagoitia checked that we were not affected by this, but it's good to keep Jetty up-to-date anyway :)

Edit: By the way, there's already an v11.0.17, so I guess we should use that one.

These are both new CVEs, we're affected by both of them.
There's ANOTHER (CVE-2023-44487) extra vulnerability addressed in 11.0.17. I was just about to PR this now 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants