Thanks Joakim for the clarification.
Have you done any impact analysis and based on that you have reduced the severity ?
If yes, then please provide the impact analysis details.
Thanks in Advance.
> > The CVEs have been fixed, in their appropriate versions.
> Jetty 9.x, 10.x, and 11.x all have fixes, the individual CVEs have details on which versions are impacted, and which versions have the fixes.
There are 3 active developed lines of Jetty, a CVE can cover some or all of the actively maintained lines of Jetty versions, we provide the information you need in the links above.
We cannot narrow it down further for you, you have to read that information yourself and determine for yourself if what you are looking for fits your needs.
> Actually we are just downloading Eclipse Jar from the link below.
> https://www.eclipse.org/downloads/download.php?file=/equinox/drops/R-4.10-201812060815/equinox-SDK-4.10.zip
That is an ancient version of Eclipse Equinox.
Eclipse Jetty is not involved in the construction of that Equinox zip.
> We are unable to understand this P2 repository concept.
> Kindly provide more info to that.
Eclipse projects that use OSGi (Eclipse Jetty is not one of them), put their built bundles in a P2 repository that other Eclipse OSGi based projects use to build their own project
from.
If you are building with OSGi and Equinox, you need to get familiar with the whole P2 repository concept quickly, as the long term effort for your Java 8 based project will depend
on you maintaining your own P2 repository with the changes you need in projects that have moved past Java 8 years ago.
The Eclipse Equinox group tends to not release updates for old versions of Equinox (they are too busy to do that).
If you have a need to stay with that old version of Equinox, then it is on you to download the source for that version, update it yourself, and build it yourself with what you need.
That includes all of the infrastructure to support that build, which means you have to build and maintain on your premises the P2 repositories for this new version of Equinox that
you built, along with all of the supporting dependencies and jars that equinox needs.
What does this mean? How complicated is it? How can we do that?
I don't know. And I'll repeat it again in a different way, the Jetty project is not involved in the building of other Eclipse projects.
If you need help with this effort, you'll need to reach out to the Eclipse Equinox folks, just be patient, as they are very busy.
Advice: Staying with Java 8 means you and your project will have
an exponentially increasing amount of work and effort on your side, as many projects have already moved to Java 11 as their minimum versions for their actively developed and maintained versions of their projects. That means you will have to maintain
versions of your critical dependencies that no longer have updates for Java 8. There is no expectation of maintenance for old versions of the projects you use, if the project has moved on, you will either need to move on as well, or stay with the old version
and all of it's faults, or maintain a fork of that project for your own purposes. Fewer and fewer projects maintain their Java 8 codebases due to the dramatic changes in Java 8 networking over the past few years. (see
https://java.com/en/jre-jdk-cryptoroadmap.html - Oracle, in an effort to stay relevant to the pace of change in SSL/TLS, has had to make dramatic changes to the Java 8 networking implementation
multiple times, and these changes make supporting the networking across Java 8 versions increasingly difficult for many projects).
In short, staying with Java 8 means you will be doing more and more work, eventually you'll have to look at the effort to update to Java 11 and see which one is less work. (many
hundreds of projects have done this analysis and found that moving to Java 11 is less work)
Eclipse Jetty has recent releases (several this year) in the Jetty 9.4.x series (see linked tables above) for Java 8 (see linked tables above).
You have to decide if the CVE (see linked tables above) ...
-
Impacts you currently with your combination of Jetty features, Jetty version, and Java version, that you are using.
-
Has a fixed Jetty version that is appropriate for you and your chosen Java version.
Read the links we've provided for you multiple times now across multiple emails.
The information you seek is there, in the linked tables above, I promise.
We cannot narrow it down or be more precise for you, as it depends on too many factors that only you know.