|[jersey-dev] security research questions about jersey-guava|
This is NOT a security report - I have a question about an old artifact.
I don’t expect anyone to spend a lot of time with this, but any help would be appreciated.
We currently have a dependency on org.glassfish.jersey.bundles.repackaged.jersey-guava_2.22.1.v20161103-1916 (the Artifact).
The Artifact was flagged by our CVE matching service for CVE-2018-10237 (the CVE).
I believe this is a false positive, because the vulnerable classes for the CVE are AtomicDoubleArray and CompoundOrdering, which are not present in the Artifact.
I’m trying to fill out my understanding of how repackaged-guava was built and am hoping someone here can help me.
I am trying to understand how the Artifact was built such that it does not include the vulnerable classes for the CVE.
The vulnerable classes are present in guava 18.0, which was the version used to build the Artifact.
I read through the pom, but don’t understand why only a subset of classes from guava 18.0 are included in jersey-guava.
I checked out jersey 2.21.x and attempted to build it myself, hoping that would help me understand.
The build failed to complete, but the repackaged module succeeded.
When I inspected jersey-guava-2.22.1.jar, it contained all of the classes from guava 18.0 instead of the subset I was expected based on the Artifact.
Can anyone help me understand how the Artifact was built such that it does not include the vulnerable classes for the CVE?
Back to the top