-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Update security advisory GHSA-qh8g-58pp-2wxh for CVE-2024-6763 #12783
Comments
Jetty 9.x is now at End of Community Support. Nobody should be using Jetty 9.x anymore. |
Note, if you still need support for |
I've started the process at Eclipse CNA to label Jetty 11/10/9/8/7 as EOL on the CVE/Mitre databases. |
@joakime thanks for your feedbacks. I still believe we should update the security advisory even though the version is EOL. All versions eventually reach this EOL stage. If we apply patch 9.4.57.v20241219, it will mitigate CVE-2024-6763 (from an EOL Jetty version). FYI, I’ll inform "my" developers that Jetty 9.x is end-of-life and that they should migrate to 12.x. |
Read CVE-2024-6763, you'll see that you are likely not vulnerable. If you just use Jetty Server or Jetty Client then you are not vulnerable. If you use HttpURI directly AND use it for security features that work with the URI authority, then you are vulnerable. |
Incidentally, the recommendations from CVE/Mitre is to not list fixes for EOL versions of products. |
It seems updating the security advisory is not an option. I'm closing the issue. Thanks. |
You've recently released version 9.4.57.v20241219 that fixes CVE-2024-6763.
Some scanners such as Qualys are not willing to take this version into account until the security advisory GHSA-qh8g-58pp-2wxh is updated (despite we pointed out to the released version). Can you please modify the security advisory to add patched version 9.4.57.v20241219?
Thank you.
The text was updated successfully, but these errors were encountered: