Skip to content

CVE-2016-1000027 Critical in 5.3 but only fixed in > 6.0.0 #30923

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
anand188 opened this issue Jul 21, 2023 · 5 comments
Closed

CVE-2016-1000027 Critical in 5.3 but only fixed in > 6.0.0 #30923

anand188 opened this issue Jul 21, 2023 · 5 comments
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) status: duplicate A duplicate of another issue

Comments

@anand188
Copy link

anand188 commented Jul 21, 2023

CVE-2016-1000027 Pivotal Spring Framework through 5.3.27 suffers from a potential remote code execution (RCE) issue if used for Java deserialization of untrusted data. Depending on how the library is implemented within a product, this issue may or not occur, and authentication may be required.

[Spring Framework] [5.3.27] will there a patch to remove those vulnerable classes like its done on 6.0.0. Much appreciable if the patch is done on 5.3 also

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Jul 21, 2023
@bclozel
Copy link
Member

bclozel commented Jul 21, 2023

Closing as a duplicate of #24434 and countless others.
Please search for issues before creating a new one; the original issue is even pinned at the top of the issues page.

@bclozel bclozel closed this as not planned Won't fix, can't repro, duplicate, stale Jul 21, 2023
@bclozel bclozel added status: duplicate A duplicate of another issue in: web Issues in web modules (web, webmvc, webflux, websocket) and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Jul 21, 2023
@anand188
Copy link
Author

anand188 commented Jul 21, 2023

@bclozel searched the ask it is possible to remove the vulnerability classes in 5.3.X latest release since 6.0.0 has done but its in latest JDK everybody cannot move to latest since we use old JDK is it possible to be fixed in 5.3.X latest version

@bclozel
Copy link
Member

bclozel commented Jul 21, 2023

@anand188 this has been answered and discussed multiple times already in the linked issue. Your application is not vulnerable if those classes aren't used by the application.

@anand188
Copy link
Author

@bclozel the current 5.3.X is vulnerable and not able to convince this is not an issue even though application wont use or invoke this classes it still exists .the problem is if its not used why it should exist can be removed in 5.3.X like its done in 6.0.0 right .instead justifying it wont be invoked its better to be removed that's the only ask

@bclozel
Copy link
Member

bclozel commented Jul 21, 2023

@anand188 See #24434 (comment)

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) status: duplicate A duplicate of another issue
Projects
None yet
Development

No branches or pull requests

3 participants