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

Is jersey2.36 affected by vulnerability CVE-2022-22965? #5316

Closed
Lastoneee opened this issue Apr 27, 2023 · 3 comments
Closed

Is jersey2.36 affected by vulnerability CVE-2022-22965? #5316

Lastoneee opened this issue Apr 27, 2023 · 3 comments
Labels
question Further information is requested

Comments

@Lastoneee
Copy link

Hello!
For details about the CVE-2022-22965 vulnerability, visit Spring Security Advisories at https://spring.io/security/cve-2022-22965.
According to the CVE-2022-22965 vulnerability details, Spring products affected by the CVE-2022-22965 vulnerability are as follows:

· Spring Framework [5.3. 0, 5.3. 17]、[5.2. 0, 5.2. 19] and older versions

Previously, only <spring5.version>5.1.5.RELEASE</spring5.version> was replaced with <spring5.version>5.3.18</spring5.version> in process # 5032.However, no changes have been made to the <spring4.version>4.3.20.RELEASE</spring4.version>. In Jersey 2.36, modules such as ext and examples depend on spring-framework 4.3.20.RELEASE, which is affected by the CVE-2022-22965 vulnerability. Is Jersey 2.36 affected by this vulnerability? Do we need to do something to fix this? Thanks!

@jansupol
Copy link
Contributor

Please understand that versions of Spring in Jersey are our compile-time dependencies. It is perfectly fine to use later versions of Spring in your runtime environment. I assume you are aware that for your compile time, you may exclude Spring from Jersey dependencies, and bring a new Spring dependency to your pom file.

Also, later versions of Jersey use later versions of Spring, the latest 2.39.1 uses Spring 4.3.30.RELEASE, and 5.3.22. But any other compatible version of Spring can be used there in the same way.

@Lastoneee
Copy link
Author

Hi, I understand that you can exclude Spring from Jersey dependencies during compilation and bring new Spring dependencies to the pom file. However, many users do not know this risk and do not actively change the Spring of an earlier version to a later version.
In addition, Spring 4.3.30.RELEASE used by the latest 2.39.1 is also affected by the CVE-2022-22965 vulnerability. Do we need to do something to fix this? thank you.

@jansupol
Copy link
Contributor

jansupol commented May 3, 2023

There is no newer version of Spring 4 than Spring 4.3.30.RELEASE. If there is a CVE in it, Jersey hardly can do anything about it. Version 4 is deprecated and the users who use it need to understand that.

@jansupol jansupol added the question Further information is requested label Jul 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants