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

Up-to-date guidelines for serialization-based endpoints [SPR-15317] #19880

Closed
spring-issuemaster opened this issue Mar 6, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@spring-issuemaster
Copy link
Collaborator

commented Mar 6, 2017

Juergen Hoeller opened SPR-15317 and commented

Over the past few years, several incidents were related to exposing serialization-based endpoints to untrusted clients. We need to update our guidelines accordingly, in particular for the HTTP Invoker mechanism. While we generally recommend against Java serialization for external remoting purposes, there are some recent efforts that allow for controlled exposure there, in particular the serialization filter that recently got introduced at JDK level (https://blogs.oracle.com/java-platform-group/entry/incoming_filter_serialization_data_a).


Referenced from: commits 2236262, c4fda0e

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

commented Mar 23, 2017

Juergen Hoeller commented

I've revised our HTTP Invoker class-level javadocs to consistently refer to serialization vulnerabilities and added a corresponding warning to the 4.3.8 version of http://docs.spring.io/spring/docs/current/spring-framework-reference/html/remoting.html#remoting-httpinvoker, also pointing to the recently introduced serialization filter at the core JDK level.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.